[Pkg-xfce-devel] Bug#526009: Bug#526009: Attempt to summarize
On 04/28/09 15:47, Yves-Alexis Perez wrote:
> Ok. I've tested and we have indeed propagation problems. I'm not sure
> how it's supposed to be handled, but I think it's a bug in consolekit. I
> don't exactly know how it should be done, but:
>
> - either the authentication propagates from console to X
> - either the 90consolekit shouldn't prevent ck-launch
>
> What do you think?
I think someone who has more intimate knowledge of consolekit should be
consulted to clarify the propagation issue. If, in fact, propagation
does not occur, then it may be best to leave libpam-ck-connector
uninstalled, unless there is some pressing reason it would be needed in
a text terminal-only environment.
However, I also found this method to fix the issue:
- libpam-ck-connector can be installed or not, doesn't matter
- don't use a $HOME/.xsession file
- put the following in $HOME/.config/xfce4/xinitrc:
#!/bin/sh
exec ck-launch-session /etc/xdg/xfce4/xinitrc
- chmod +x $HOME/.config/xfce4/xinitrc
Now you can start xfce with 'startxfce4' instead of 'startx', and
everything works fine, regardless of libpam-ck-connector. This method
just over-rides the default exec at the very end of /usr/bin/startxfce4,
inserting ck-launch-session before calling /etc/xdg/xfce/xinitrc. I'm
sure that the upstream xfce developers will run across this consolekit
problem soon (if they haven't already), and may patch
/usr/bin/startxfce4 appropriately anyway.
So, that makes two fairly simple methods which work fine (one for the
'debian way' and one for the 'xfce way'), but you and the other
maintainers will need to determine which is best.
--
Scott Barker scott at mostlylinux.ca
Linux Consultant http://www.mostlylinux.ca/scott
Reply to: