Re: [gentoo-user] systemd-197-r1 starts gdm-3.6.2

["Canek Peláez Valdés" <caneko@gmail.com>]

On Wed, Jan 30, 2013 at 11:56 AM, Stefan G. Weichinger <lists@xunil.at> wrote:
> Am 30.01.2013 18:52, schrieb Canek Peláez Valdés:
>> On Wed, Jan 30, 2013 at 11:48 AM, Stefan G. Weichinger <lists@xunil.at> wrote:
>>> Am 30.01.2013 18:36, schrieb Hinnerk van Bruinehsen:
>>>
>>>> I've just installed systemd on one of my systems to give it a test and I
>>>> had similar problems due to the systemd useflag on policykit being
>>>> hardmasked (it also pulled in consolekit because of that).
>>>> Since the errors are very similar you may check your useflags on
>>>> policykit and - if necessary remove the use-mask of systemd for
>>>> policykit.
>>
>>
>> As Hinnerk said, it could be a PolKit problem, but you said that you
>> had unmasked the systemd USE flag from PolKit. The new information I
>> see in this mail is that you have =gnome-base/gnome-session-9999
>> installed; why do you have a live version? Did you use --autounmask to
>> install GNOME?
>>
>> I think that's the problem: gnome-session has no live version in the
>> tree; therefore you are installing it from the GNOME overlay. The live
>> version of gnome-session in the GNOME overlay doesn't use a specific
>> version, tag or branch to checkout, so depending on when you installed
>> it, it's possible you are running gnome-session-3.7.x.
>>
>> I would keep gnome-session keyworded, but unmasked; that would force
>> the install of the 3.6.2 version. Also, if you have more live
>> versions, I would recommend downgrading them to the last 3.6.x
>> version. GNOME 3.6 is not masked in Gentoo, just keyworded.
>
> I have
>
> [I] gnome-base/gnome-session
>      Available versions:  2.32.1-r3 (~)3.4.2.1 (~)3.6.2 (~)3.6.2-r1
> **9999[1] {debug doc gconf ipv6 systemd ELIBC="FreeBSD"}
>      Installed versions:  3.6.2-r1(17:40:19 30.01.2013)(ipv6 systemd
> -debug -doc -gconf ELIBC="-FreeBSD")
>
> -> so 3.6.2-r1 here ....

My mistake; I saw the asterisks and I thought that was the one installed.

>> If you have -consolekit, why it's still installed? What is pulling it
>> into your system? Can you do a "equery depends consolekit"?
>
> sure, did that already .... looks strange, right?
>
>  * These packages depend on sys-auth/consolekit:
> gnome-base/gdm-3.6.2 (consolekit ? sys-auth/consolekit[pam])
> gnome-base/gnome-control-center-3.6.3-r1 (!systemd ? sys-auth/consolekit)
> gnome-base/gnome-session-3.6.2-r1 (!systemd ? sys-auth/consolekit)
> gnome-base/gnome-settings-daemon-3.6.4 (!systemd ? sys-auth/consolekit)
> gnome-base/gnome-shell-3.6.2-r1 (!systemd ? sys-auth/consolekit)
> net-misc/networkmanager-0.9.6.4-r1 (consolekit ? sys-auth/consolekit)
> net-wireless/bluez-4.101-r5 (consolekit ? sys-auth/consolekit)
> sys-apps/accountsservice-0.6.30 (!systemd ? sys-auth/consolekit)
> sys-auth/pambase-20120417-r1 (consolekit ?
>>=sys-auth/consolekit-0.4.5_p2012[pam])
> sys-auth/polkit-0.110 (!systemd ?
>>=sys-auth/consolekit-0.4.5_p2012[policykit])
> x11-apps/xdm-1.1.11-r1 (consolekit ? sys-auth/consolekit)

OK, did you run "emerge --depclean"? All of those packages use
consolekit or systemd, but not both; if after --depclean'ing
consolekit keeps lurking, could you uninstall it and mask it, followed
by a "emerge -uDNvp world"? That would tell us which package is
pulling it.

Also, remeber that you can set USE flags not only in
/etc/portage/make.conf, but also in /etc/portage/package.use (and I
think the latter takes precedence).

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México