Re: [gentoo-user] gnome not working
TLDR: because systemd replaces consolekit with logind, programs that depend on consolekit to determine which "session" they're in may fail to do so unless they are also built with systemd support and the relevant pam session lines are enabled. This causes several silent failures and may prevent your desktop from starting. Possible Cause: If you're using systemd, you may have built some gnome components with systemd support. This _disables_ consolekit support on those components, hence failures when booting outside of systemd. Try rebuilding polkit-gnome and any other gnome components with systemd support. This makes them use systemd-logind instead of consolekit. I don't use my system without systemd, but I suspect that you also have to start dbus and the (HORROR) systemd-logind service. _Someone ought to write a systemd-logind init script for enterprising gentoo users_. As it doesn't accept any arguments, I expect that it's as easy as the _completely untested_ one I have attached. Have fun! I can't wait to hear the excitement on this list on that, haha - but logind, like udev, should be able to work without systemd, which is why ubuntu is considering it. - http://www.phoronix.com/scan.php?page=news_item&px=MTMyMDE === BEGIN ADVENTURES I just recently fixed some woes I was having with starting an X session from lightdm. I am also on systemd. I got similar errors to the top post, X logs ending with "server terminator successfully" immediately after I perform a login attempt. I _also_ noticed that my X server died every time I switched virtual terminals, and I was unable to go back. This started a painstaking process of blind debugging, following this path: 1) start Xorg manually. is successful. === Xorg === note: dies when I VT switch back. 2) start Xorg manually and run a program in it. is successful. === export DISPLAY=:0 Xorg & terminator === note: also dies when I VT switch back. I suspected that this had something to do with multiseat support. The idea was that my system "does something" when I VT switch, and I suspected that whatever it was killed my X. 3) start Xorg manually and run a session in it. is successful. === export DISPLAY=:0 Xorg & gnome-session --session=unity === notes: - unity downloaded from unity-gentoo overlay. - have not been able to completely emerge -uDNtv && emerge -ctav in a week or so, so I expected problems. - dies when I VT switch back - mounting external hard disks fail with "Not authorized to perform action" - changing settings on Network manager also failed. I expected there to be a login prompt, but no prompt appeared. I'd experienced "Not authorized to perform action" before. It was a message that I got from policykit. So I suspected that my programs were failing to connect to policykit. (Not really experienced with polkit). After reading some manual pages [1][2][3][4][5] in policykit, I prepared another test. [1] polkit(8) [2] pkaction(1) [3] pkcheck(1) [4] pkexec(1) [5] pkttyagent(1) 4) Try running the failing commands using pkcheck/pkexec. They still fail. /usr/share/polkit-1/actions contains a list of actions available to policykit. You can also get a list of actions by running "pkaction" I determined that the relevant policy kit action to mount hard disks was org.freedesktop.udisks2.filesystem-mount To test the mount command, I used pkcheck, then pkexec. pkcheck tries to perform a policykit action directly and reports success or failure based on exit status. It needs a policykit action name and the PID of the session. === pkcheck --action-id org.freedesktop.udisks2.filesystem-mount --process $(pgrep gnome-session) === pkcheck complains that Authorization requires authentication and -u wasn't passed. Upon passing -u, pkcheck then complains that no authentication agent was available. An authentication agent is the program that generates a popup requiring login. I found this part suspicious, so I tried to activate an authentication agent. 5) Try running the failing commands with a dummy authentication agent. They now succeed. policykit comes with a builtin authentication agent. pkcheck has a --enable-internal-agent option which automatically produces a password prompt. Alternatively, you can run pkttyagent --process PID_OF_SOME_BASH_SESSION in one terminal, and any pkexec'd commands in that terminal will produce a login prompt on the pkttyagent terminal. === pkcheck --action-id org.freedesktop.udisks2.filesystem-mount --process $(pgrep gnome-session) --enable-internal-agent --allow-user-interaction === A login prompt appears, asking me what username I wish to login as. This suggests that _policykit is working_, but _gnome's policykit agent_ isn't. 6) Try to do everything again after emerging polkit-gnome is emerged with systemd support. They now succeed. I still can't get lightdm to work (still recompiling stuff)... but gdm now works just fine, and now I have my desktop working. Note that your /etc/pam.d/system-auth and system-session
Re: [gentoo-user] gnome not working
Canek Peláez Valdés wrote: > On Wed, May 15, 2013 at 8:10 PM, wrote: > > waltd...@waltdnes.org wrote: > > > >> On Mon, May 13, 2013 at 07:06:02AM -0400, cov...@ccs.covici.com wrote > >> > When I start gdm, I get a message on the screen which says oh no, > >> > something has gone wrong. The log file is at > >> > http://pastebin.com/qwNE7ee6 -- I would appreciate any help. > >> > > >> > I am running gentoo testing with the 3.8 unmasked. > >> > >> Direct from the "Making systemd more accessible to "normal" users" > >> flamewar on gentoo-dev... > >> > >> > And now that GNOME 3.8 is out, the game starts over again: logind > >> > is a hard requirement, logind is part of systemd, starting logind > >> > (which replaces consolekit) is not that trivial as you may think > >> > (and is the thing I started to work on anyway). > >> > > >> > And if this wasn't enough, it means that if you want GNOME 3.8, > >> > you need to get logind, which may or not may get included in our > >> > udev ebuild and if it won't, it means that you will be forced to use > >> > systemd as device manager if you want GNOME 3.8, which is believe > >> > it or not, the thing that Ubuntu did. > >> > >> Do you have systemd/logind installed? > > > > Nope, sure don't. None of the ebuilds pulled it in. But what about > > startx? Would I need logind to do that? > > When you use startx, what does your .xinitrc have? Try with only > > exec gnome-session My startx is: #!/bin/sh # # This is just a sample implementation of a slightly less primitive # interface than xinit. It looks for user .xinitrc and .xserverrc # files, then system xinitrc and xserverrc files, else lets xinit choose # its default. The system xinitrc should probably do things like check # for .Xresources files and merge them in, start up a window manager, # and pop a clock and several xterms. # # Site administrators are STRONGLY urged to write nicer versions. # unset DBUS_SESSION_BUS_ADDRESS unset SESSION_MANAGER userclientrc=$HOME/.xinitrc sysclientrc=/etc/X11/xinit/xinitrc userserverrc=$HOME/.xserverrc sysserverrc=/etc/X11/xinit/xserverrc defaultclient=xterm defaultserver=/usr/bin/X defaultclientargs="" defaultserverargs="" defaultdisplay=":0" clientargs="" serverargs="" enable_xauth=1 # Automatically determine an unused $DISPLAY d=0 while true ; do [ -e /tmp/.X$d-lock ] || break d=$(($d + 1)) done defaultdisplay=":$d" unset d whoseargs="client" while [ x"$1" != x ]; do case "$1" in # '' required to prevent cpp from treating "/*" as a C comment. /''*|\./''*) if [ "$whoseargs" = "client" ]; then if [ x"$client" = x ] && [ x"$clientargs" = x ]; then client="$1" else clientargs="$clientargs $1" fi else if [ x"$server" = x ] && [ x"$serverargs" = x ]; then server="$1" else serverargs="$serverargs $1" fi fi ;; --) whoseargs="server" ;; *) if [ "$whoseargs" = "client" ]; then clientargs="$clientargs $1" else # display must be the FIRST server argument if [ x"$serverargs" = x ] && \ expr "$1" : ':[0-9][0-9]*$' > /dev/null 2>&1; then display="$1" else serverargs="$serverargs $1" fi fi ;; esac shift done # process client arguments if [ x"$client" = x ]; then client=$defaultclient # For compatibility reasons, only use startxrc if there were no client command line arguments if [ x"$clientargs" = x ]; then if [ -f "$userclientrc" ]; then client=$userclientrc elif [ -f "$sysclientrc" ]; then client=$sysclientrc fi fi fi # if no client arguments, use defaults if [ x"$clientargs" = x ]; then clientargs=$defaultclientargs fi # process server arguments if [ x"$server" = x ]; then server=$defaultserver # For compatibility reasons, only use xserverrc if there were no server command line arguments if [ x"$serverargs" = x -a x"$display" = x ]; then if [ -f "$userserverrc" ]; then server=$userserverrc elif [ -f "$sysserverrc" ]; then server=$sysserverrc fi fi fi # if no server arguments, use defaults if [ x"$serverargs" = x ]; then serverargs=$defaultserverargs fi # if no display, use default if [ x"$display" = x ]; then display=$defaultdisplay fi if [ x"$enable_xauth" = x1 ] ; then if [ x"$XAUTHORITY" = x ]; then XAUTHORITY=$HOME/.Xauthority export XAUTHORITY fi removelist= # set up default Xauth info for this machine case `uname` in Linux*) if [ -z "`hostname --version 2>&1 | grep GNU`" ]; then hostname=`hostname -f` else hostname=`hostname` fi ;; *) hostname=`ho
Re: [gentoo-user] gnome not working
On Wed, May 15, 2013 at 8:10 PM, wrote: > waltd...@waltdnes.org wrote: > >> On Mon, May 13, 2013 at 07:06:02AM -0400, cov...@ccs.covici.com wrote >> > When I start gdm, I get a message on the screen which says oh no, >> > something has gone wrong. The log file is at >> > http://pastebin.com/qwNE7ee6 -- I would appreciate any help. >> > >> > I am running gentoo testing with the 3.8 unmasked. >> >> Direct from the "Making systemd more accessible to "normal" users" >> flamewar on gentoo-dev... >> >> > And now that GNOME 3.8 is out, the game starts over again: logind >> > is a hard requirement, logind is part of systemd, starting logind >> > (which replaces consolekit) is not that trivial as you may think >> > (and is the thing I started to work on anyway). >> > >> > And if this wasn't enough, it means that if you want GNOME 3.8, >> > you need to get logind, which may or not may get included in our >> > udev ebuild and if it won't, it means that you will be forced to use >> > systemd as device manager if you want GNOME 3.8, which is believe >> > it or not, the thing that Ubuntu did. >> >> Do you have systemd/logind installed? > > Nope, sure don't. None of the ebuilds pulled it in. But what about > startx? Would I need logind to do that? When you use startx, what does your .xinitrc have? Try with only exec gnome-session Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] gnome not working
waltd...@waltdnes.org wrote: > On Mon, May 13, 2013 at 07:06:02AM -0400, cov...@ccs.covici.com wrote > > When I start gdm, I get a message on the screen which says oh no, > > something has gone wrong. The log file is at > > http://pastebin.com/qwNE7ee6 -- I would appreciate any help. > > > > I am running gentoo testing with the 3.8 unmasked. > > Direct from the "Making systemd more accessible to "normal" users" > flamewar on gentoo-dev... > > > And now that GNOME 3.8 is out, the game starts over again: logind > > is a hard requirement, logind is part of systemd, starting logind > > (which replaces consolekit) is not that trivial as you may think > > (and is the thing I started to work on anyway). > > > > And if this wasn't enough, it means that if you want GNOME 3.8, > > you need to get logind, which may or not may get included in our > > udev ebuild and if it won't, it means that you will be forced to use > > systemd as device manager if you want GNOME 3.8, which is believe > > it or not, the thing that Ubuntu did. > > Do you have systemd/logind installed? Nope, sure don't. None of the ebuilds pulled it in. But what about startx? Would I need logind to do that? > > -- > Walter Dnes > I don't run "desktop environments"; I run useful applications -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] gnome not working
Am 16.05.2013 00:28, schrieb Canek Peláez Valdés: > systemd 201 is targeted to be stabilized soon: > > https://bugs.gentoo.org/show_bug.cgi?id=465870 > > The LVM issue is mentioned, but it's not yet on the block list. I didn't read all this thread ... but I still face issues with lvm2 & systemd here. Sometimes the VG is activated, sometimes not ... Using overlay "systemd-love" here and I am already in contact with the dev there. (and right now, after booting w/ systemd-204, the LVs are there as they should be) Stefan
Re: [gentoo-user] gnome not working
On Wed, May 15, 2013 at 4:44 PM, Michael Hampicke wrote: > > Am 15.05.2013 20:27, schrieb waltd...@waltdnes.org: > > > > Direct from the "Making systemd more accessible to "normal" users" > > flamewar on gentoo-dev... > > > >> And now that GNOME 3.8 is out, the game starts over again: logind > >> is a hard requirement, logind is part of systemd, starting logind > >> (which replaces consolekit) is not that trivial as you may think > >> (and is the thing I started to work on anyway). > >> > >> And if this wasn't enough, it means that if you want GNOME 3.8, > >> you need to get logind, which may or not may get included in our > >> udev ebuild and if it won't, it means that you will be forced to use > >> systemd as device manager if you want GNOME 3.8, which is believe > >> it or not, the thing that Ubuntu did. > > > > Do you have systemd/logind installed? > > > > I read that too on gentoo-dev. I have systemd installed, but currently I > do not use it as init. I have tried it with systemd as init, but it has > problems with mounting my lvm volumes (after failing it's stuck, > ctrl+alt+del has no effect, and magic sysrq seems to be deactived?). I > think a saw a bug report regarding systemd/lvm. > > I may try it again in a few days. There have been some updates to > systemd lately. systemd 201 is targeted to be stabilized soon: https://bugs.gentoo.org/show_bug.cgi?id=465870 The LVM issue is mentioned, but it's not yet on the block list. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] gnome not working
Am 15.05.2013 20:27, schrieb waltd...@waltdnes.org: > > Direct from the "Making systemd more accessible to "normal" users" > flamewar on gentoo-dev... > >> And now that GNOME 3.8 is out, the game starts over again: logind >> is a hard requirement, logind is part of systemd, starting logind >> (which replaces consolekit) is not that trivial as you may think >> (and is the thing I started to work on anyway). >> >> And if this wasn't enough, it means that if you want GNOME 3.8, >> you need to get logind, which may or not may get included in our >> udev ebuild and if it won't, it means that you will be forced to use >> systemd as device manager if you want GNOME 3.8, which is believe >> it or not, the thing that Ubuntu did. > > Do you have systemd/logind installed? > I read that too on gentoo-dev. I have systemd installed, but currently I do not use it as init. I have tried it with systemd as init, but it has problems with mounting my lvm volumes (after failing it's stuck, ctrl+alt+del has no effect, and magic sysrq seems to be deactived?). I think a saw a bug report regarding systemd/lvm. I may try it again in a few days. There have been some updates to systemd lately. signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] gnome not working
On Mon, May 13, 2013 at 07:06:02AM -0400, cov...@ccs.covici.com wrote > When I start gdm, I get a message on the screen which says oh no, > something has gone wrong. The log file is at > http://pastebin.com/qwNE7ee6 -- I would appreciate any help. > > I am running gentoo testing with the 3.8 unmasked. Direct from the "Making systemd more accessible to "normal" users" flamewar on gentoo-dev... > And now that GNOME 3.8 is out, the game starts over again: logind > is a hard requirement, logind is part of systemd, starting logind > (which replaces consolekit) is not that trivial as you may think > (and is the thing I started to work on anyway). > > And if this wasn't enough, it means that if you want GNOME 3.8, > you need to get logind, which may or not may get included in our > udev ebuild and if it won't, it means that you will be forced to use > systemd as device manager if you want GNOME 3.8, which is believe > it or not, the thing that Ubuntu did. Do you have systemd/logind installed? -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] gnome not working
Michael Hampicke wrote: > Am 13.05.2013 13:06, schrieb cov...@ccs.covici.com: > > When I start gdm, I get a message on the screen which says oh no, > > something has gone wrong. The log file is at > > http://pastebin.com/qwNE7ee6 -- I would appreciate any help. > > > > I am running gentoo testing with the 3.8 unmasked. > > > > Today I spotted some updated gnome (3.8) packages in the tree. Maybe the > updated versions will work for you. OK, thanks. Maybe I will just try that, but it would be better to know what is the matter. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] gnome not working
Am 13.05.2013 13:06, schrieb cov...@ccs.covici.com: > When I start gdm, I get a message on the screen which says oh no, > something has gone wrong. The log file is at > http://pastebin.com/qwNE7ee6 -- I would appreciate any help. > > I am running gentoo testing with the 3.8 unmasked. > Today I spotted some updated gnome (3.8) packages in the tree. Maybe the updated versions will work for you. signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] gnome not working
J. Roeleveld wrote: > On Mon, May 13, 2013 13:06, cov...@ccs.covici.com wrote: > > When I start gdm, I get a message on the screen which says oh no, > > something has gone wrong. The log file is at > > http://pastebin.com/qwNE7ee6 -- I would appreciate any help. > > Please attach logfiles to the list. > Using sites like pastebin makes archives useless. OK, I didn't know that. I also had the same problem when using startx, so I will attach my .xsession-errors along with the Xorg.0.log file. [ 79107.259] X.Org X Server 1.14.1 Release Date: 2013-04-17 [ 79107.260] X Protocol Version 11, Revision 0 [ 79107.260] Build Operating System: Linux 3.6.2-gentoo x86_64 Gentoo [ 79107.261] Current Operating System: Linux ccs.covici.com 3.6.2-gentoo #4 SMP PREEMPT Sat Mar 2 02:33:27 EST 2013 x86_64 [ 79107.261] Kernel command line: BOOT_IMAGE=3.6.2-gentoo ro root=100 init=/linuxrc ramdisk=8192 real_root=/dev/mapper/linux--files-64--root udev video=uvesafb:1280x1024 speakup.synth=spkout vmalloc=256M dolvm rootfstype=ext4 [ 79107.262] Build Date: 11 May 2013 07:28:12PM [ 79107.262] [ 79107.263] Current version of pixman: 0.30.0 [ 79107.264]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 79107.264] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 79107.266] (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 13 06:28:19 2013 [ 79107.266] (==) Using config file: "/etc/X11/xorg.conf" [ 79107.267] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 79107.267] (==) ServerLayout "Default Layout" [ 79107.267] (**) |-->Screen "Default Screen" (0) [ 79107.267] (**) | |-->Monitor "Generic Monitor" [ 79107.267] (**) | |-->Device "NVIDIA Corporation NV34 [GeForce FX 5500]" [ 79107.267] (**) |-->Input Device "Generic Keyboard" [ 79107.267] (**) |-->Input Device "Configured Mouse" [ 79107.267] (==) Automatically adding devices [ 79107.267] (==) Automatically enabling devices [ 79107.267] (==) Automatically adding GPU devices [ 79107.267] (WW) The directory "/usr/share/fonts/X11/misc" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/lib/X11/fonts/misc" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/lib/X11/fonts/100dpi/" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/lib/X11/fonts/75dpi/" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/lib/X11/fonts/Type1" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/share/fonts/X11/CID" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/lib/X11/fonts/CID" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/lib/X11/fonts/100dpi" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/lib/X11/fonts/75dpi" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/share/fonts/misc/" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/share/fonts/TTF/" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/share/fonts/OTF/" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/share/fonts/Type1/" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/share/fonts/100dpi/" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (WW) The directory "/usr/share/fonts/75dpi/" does not exist. [ 79107.267]Entry deleted from font path. [ 79107.267] (**) FontPath set to: unix/:7100 [ 79107.267] (**) ModulePath set to "/usr/lib64/xorg/modules,/usr/lib64/xorg/modules/extensions,/usr/lib64/xorg/opengl/xorg-x11,/usr/lib64/xorg/opengl/xorg-x11/extensions" [ 79107.267] (**) Extension "Composite" is disabled [ 79107.267] (**) Extension "RENDER" is enabled [ 79107.267] (WW) Hotplugging is on, devices using drivers 'kbd
Re: [gentoo-user] gnome not working
On Mon, May 13, 2013 13:06, cov...@ccs.covici.com wrote: > When I start gdm, I get a message on the screen which says oh no, > something has gone wrong. The log file is at > http://pastebin.com/qwNE7ee6 -- I would appreciate any help. Please attach logfiles to the list. Using sites like pastebin makes archives useless. -- Joost
[gentoo-user] gnome not working
When I start gdm, I get a message on the screen which says oh no, something has gone wrong. The log file is at http://pastebin.com/qwNE7ee6 -- I would appreciate any help. I am running gentoo testing with the 3.8 unmasked. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
