From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 6ED9D1381F3 for ; Thu, 16 May 2013 10:10:26 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9CAAAE0857; Thu, 16 May 2013 10:10:15 +0000 (UTC) Received: from mail-ie0-f177.google.com (mail-ie0-f177.google.com [209.85.223.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 63D29E082F for ; Thu, 16 May 2013 10:10:14 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id 9so6008452iec.22 for ; Thu, 16 May 2013 03:10:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=himYRbNdD5RlOtQ5EAAXBfC+Sa7QtFOotEsk4ZFpXus=; b=mOigcxzw5R00U/Lqee0issZDzYWtZc7tRSKvT0ojQL1qcS8Bi9Ivt5gEsntlQ9yfU1 zmXdLyZQ9iYE5bBFHUeB0yNhP/VHxPzhkj7f4/ELR0rCL/rcr2jPmuFCpDD0iyXHUvYP lkpmcq/c2qRoez8NCc2H21Ytzo6AMrR2aONjO1GhZS/KtgKlW5AAUFOUTCtVl0MOTTW2 SCfIp8HhWmoWdxJ7P1ElO6RcG+wO2Rumi+cuMafyS+dPpHvnJvJN+W3Fq8lKYZsn3F+P EqbwYcr8juXfglpz7i47C62eQ44/nItD31dSnCVcVSElIfKg2IgGyTCh0SKl1OkMveyz 2ORg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.50.3.38 with SMTP id 6mr8699418igz.44.1368699013247; Thu, 16 May 2013 03:10:13 -0700 (PDT) Received: by 10.50.100.1 with HTTP; Thu, 16 May 2013 03:10:13 -0700 (PDT) In-Reply-To: <1696.1368682359@ccs.covici.com> References: <10356.1368443162@ccs.covici.com> <20130515182710.GB27396@waltdnes.org> <27382.1368666609@ccs.covici.com> <1696.1368682359@ccs.covici.com> Date: Thu, 16 May 2013 18:10:13 +0800 Message-ID: Subject: Re: [gentoo-user] gnome not working From: Mark David Dumlao To: gentoo-user@lists.gentoo.org Content-Type: multipart/mixed; boundary=089e013c684e7d39b204dcd31274 X-Archives-Salt: 1d90c2c6-d725-4691-ab1c-0eb5b625d03e X-Archives-Hash: b16dee12f1f0312af2816f2cbd5d0f64 --089e013c684e7d39b204dcd31274 Content-Type: text/plain; charset=ISO-8859-1 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 are expected to have lines with pam_systemd rather than pam_ck_connector, as per Gentoo wiki on systemd. http://wiki.gentoo.org/wiki/Systemd might I add that unity looks marvelous on Gentoo. --089e013c684e7d39b204dcd31274 Content-Type: application/octet-stream; name=systemd-logind Content-Disposition: attachment; filename=systemd-logind Content-Transfer-Encoding: base64 X-Attachment-Id: f_hgrruz5j0 IyEvc2Jpbi9ydW5zY3JpcHQKIyBDb3B5cmlnaHQgMTk5OS0yMDExIEdlbnRvbyBGb3VuZGF0aW9u CiMgRGlzdHJpYnV0ZWQgdW5kZXIgdGhlIHRlcm1zIG9mIHRoZSBHTlUgR2VuZXJhbCBQdWJsaWMg TGljZW5zZSwgdjIgb3IgbGF0ZXIKIyAkSGVhZGVyOiAvdmFyL2N2c3Jvb3QvZ2VudG9vLXg4Ni9z eXMtYXBwcy9kYnVzL2ZpbGVzL2RidXMuaW5pdGQsdiAxLjEgMjAxMS8xMS8wNSAxMzo1NjoxMCBz c3VvbWluZW4gRXhwICQKCmRlcGVuZCgpIHsKCW5lZWQgZGJ1cwoJYWZ0ZXIgYm9vdG1pc2MKfQoK c3RhcnQoKSB7CgllYmVnaW4gIlN0YXJ0aW5nIHN5c3RlbWQtbG9naW5kIgoJc3RhcnQtc3RvcC1k YWVtb24gLS1zdGFydCAtLXBpZGZpbGUgL3Zhci9ydW4vc3lzdGVtZC1sb2dpbmQucGlkIC0tZXhl YyAvdXNyL2xpYi9zeXN0ZW1kL3N5c3RlbWQtbG9naW5kCgllZW5kICQ/Cn0KCnN0b3AoKSB7Cgll YmVnaW4gIlN0b3BwaW5nIEQtQlVTIHN5c3RlbSBtZXNzYWdlYnVzIgoJc3RhcnQtc3RvcC1kYWVt b24gLS1zdG9wIC0tcGlkZmlsZSAvdmFyL3J1bi9zeXN0ZW1kLWxvZ2luZC5waWQKCWVlbmQgJD8K fQo= --089e013c684e7d39b204dcd31274--