You are not logged in.
I use xfce4 without a login manager. Ever since, I switched to the native systemd configuration (no initscripts and sysvinit), 'restart' icon is greyed out, automount doesn't work without root priveleges and if I shutdown by the GUI, it just exits xfce4. I understand that there is probably some issue with the polkit but can't find the solution. systemd-sysvcompat and polkit-kde are installed.
I followed the instructions provided on https://wiki.archlinux.org/index.php/Ge … ermissions
and
loginctl show-session $XDG_SESSION_IDgave the following output.
$ loginctl show-session $XDG_SESSION_ID
ControlGroupHierarchy=/user
ResetControllers=cpu
NAutoVTs=6
KillExcludeUsers=root
KillUserProcesses=no
IdleHint=yes
IdleSinceHint=0
IdleSinceHintMonotonic=0
DelayInhibited=sleep
InhibitDelayMaxUSec=5s
HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
PreparingForShutdown=no
PreparingForSleep=noThe site mentions that 'Remote=no' and 'Active=yes' shoude be in the output, which is not. So I tried all the steps mentioned in https://wiki.archlinux.org/index.php/Xi … he_session
but the output didn't change.
This is what my ~/.xinitrc looks like:
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
exec startxfce4
#exec ck-launch-session dbus-launch startxfce4
# exec gnome-session
# exec startkde
# ...or the Window Manager of your choiceI am currently booting from runlevel3 (have enabled multiuser.target)
It is possible that I have missed something quite obvious, but I have been at it for a while but haven't been able to solve it yet.
Any help will be appreciated. Thanks.
Last edited by Flicker (2012-12-14 14:39:07)
Offline
if you upgraded from sysvinit to systemd, you might need to add a kernel param, see installation's part in systemd wiki.
* PC: Intel Core 2 DUO E6550 @ 2.33 GHz with 2 GB RAM: Archlinux-i686 with xfce4.
* Laptop: Intel Core 2 DUO T6600 @ 2.20 GHz with 4 GB RAM: Archlinux-x86-64 with xfce4.
* AUR contributor.
Offline
The output you're seeing is what you get when you issue showsession without specifying a session number. Try loginctl list-sessions.
Offline
@Joel:
The wiki says the kernel parameter is optional. I had removed it after installing systemd-sysvcompat Just to be sure I added the parameter again after your reply but no change.This is what my grub.cfg looks like:
@Scimmia:
loginctl list-sessionsgave the following output:
loginctl list-sessions
SESSION UID USER SEAT
0 sessions listed.Not sure what to do now?
Last edited by Flicker (2012-12-13 08:30:04)
Offline
next you check the journal and see if you can figure out why logind isn't creating a session. hopefully "sudo journalctl -b | grep logind" will get you something.
Offline
Scimmia: This is the output:
$ sudo journalctl -b | grep logind
Jan 01 06:53:00 T systemd-logind[250]: Watching system buttons on /dev/input/event4 (Power Button)
Jan 01 06:53:00 T systemd-logind[250]: Watching system buttons on /dev/input/event1 (Video Bus)
Jan 01 06:53:00 T systemd-logind[250]: Watching system buttons on /dev/input/event6 (Sony Vaio Keys)
Jan 01 06:53:00 T systemd-logind[250]: Watching system buttons on /dev/input/event7 (Sony Vaio Jogdial)
Jan 01 06:53:00 T systemd-logind[250]: Watching system buttons on /dev/input/event2 (Power Button)
Jan 01 06:53:00 T systemd-logind[250]: Watching system buttons on /dev/input/event3 (Lid Switch)I found https://bugzilla.redhat.com/show_bug.cgi?id=806491 to be similar to my problem. Trying to understand it. Might be mistaken.
Any inputs?
Offline
I use SLiM and XFCE successfully with systemd. Some things to check:
/home/~/.xinitrc
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
if [ -f $HOME/.Xmodmap ]; then
/usr/bin/xmodmap $HOME/.Xmodmap
fi
# exec gnome-session
# exec startkde
exec startxfce4
# ...or the Window Manager of your choice
# exec ck-launch-session dbus-launch startxfce4/etc/slim.conf
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path /bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
#
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
login_cmd exec /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
#
# sessionstart_cmd some command
# sessionstop_cmd some command
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions xfce4,icewm-session,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg Session:
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
#default_user simone
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
#focus_password no
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login no
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme default
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.logNo /etc/initab
No /etc/rc.conf
No /etc/rc.local
Have pm-utils installed.
Have your normal user belong to the 'powers' group.
Offline
I never bothered to get the shutdown/restart/etc. working in the XFCE logout menu, but they spontaneously started working some time after the transition to systemd.
Some details about my setup
Belong to groups: kvm optical users vboxusers beep
Auto-login to console via autologin.service
Auto-login to X via line at the end of .bashrc:
[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && startxContents of .xinitrc:
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
setxkbmap carpalx
redshift -l 37.11:-76.16 -b 1.0 -g 1.0 -t 6500:3800 -m randr &
exec startxfce4But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
FTR, here is my /home/~/bash.rc
#
# ~/.bashrc
#
# If not running interactively, don't do anything
[[ $- != *i* ]] && return
alias ls='ls --color=auto'
PS1='[\u@\h \W]\$ 'Offline
I remember another case where loginctl didn't create a session. The problem was that the pam config was screwed up (/etc/pam.d/). You may want to reinstall pambase, although I'm not sure if this is actually the package responsible for login authentication. Also make sure you deal with pacnew files if there are any in /etc/pam.d/.
Offline
65kid: Thanks a ton. Had to set the loging.pacnew file (/etc/pam.d/login.pacnew) to the login file. And everything is back to normal :-)
Thanks everyone for the replies.
Offline