| 1 |
On Wed, Jan 30, 2013 at 11:48 AM, Stefan G. Weichinger <lists@×××××.at> wrote: |
| 2 |
> Am 30.01.2013 18:36, schrieb Hinnerk van Bruinehsen: |
| 3 |
> |
| 4 |
>> I've just installed systemd on one of my systems to give it a test and I |
| 5 |
>> had similar problems due to the systemd useflag on policykit being |
| 6 |
>> hardmasked (it also pulled in consolekit because of that). |
| 7 |
>> Since the errors are very similar you may check your useflags on |
| 8 |
>> policykit and - if necessary remove the use-mask of systemd for |
| 9 |
>> policykit. |
| 10 |
|
| 11 |
|
| 12 |
As Hinnerk said, it could be a PolKit problem, but you said that you |
| 13 |
had unmasked the systemd USE flag from PolKit. The new information I |
| 14 |
see in this mail is that you have =gnome-base/gnome-session-9999 |
| 15 |
installed; why do you have a live version? Did you use --autounmask to |
| 16 |
install GNOME? |
| 17 |
|
| 18 |
I think that's the problem: gnome-session has no live version in the |
| 19 |
tree; therefore you are installing it from the GNOME overlay. The live |
| 20 |
version of gnome-session in the GNOME overlay doesn't use a specific |
| 21 |
version, tag or branch to checkout, so depending on when you installed |
| 22 |
it, it's possible you are running gnome-session-3.7.x. |
| 23 |
|
| 24 |
I would keep gnome-session keyworded, but unmasked; that would force |
| 25 |
the install of the 3.6.2 version. Also, if you have more live |
| 26 |
versions, I would recommend downgrading them to the last 3.6.x |
| 27 |
version. GNOME 3.6 is not masked in Gentoo, just keyworded. |
| 28 |
|
| 29 |
> Let me get that straight: |
| 30 |
> |
| 31 |
> I have: |
| 32 |
> |
| 33 |
> # cat profile/package.use.mask |
| 34 |
> |
| 35 |
> media-sound/pulseaudio -systemd |
| 36 |
> net-misc/networkmanager -systemd |
| 37 |
> sys-auth/polkit -systemd |
| 38 |
> sys-fs/udisks -systemd |
| 39 |
> sys-power/upower -systemd |
| 40 |
> |
| 41 |
> because of some older thread or the gentoo wiki for systemd (can't |
| 42 |
> remember right now). |
| 43 |
> |
| 44 |
> This gets me: |
| 45 |
> |
| 46 |
> [I] sys-auth/polkit |
| 47 |
> Available versions: 0.107-r1 0.110 {examples gtk +introspection |
| 48 |
> kde nls pam selinux systemd} |
| 49 |
> Installed versions: 0.110(18:09:30 30.01.2013)(gtk introspection |
| 50 |
> nls pam systemd -examples -kde -selinux) |
| 51 |
> |
| 52 |
> while I have USE= ... -consolekit systemd ... in make.conf. |
| 53 |
> |
| 54 |
> I also get consolekit installed here: |
| 55 |
> |
| 56 |
> [I] sys-auth/consolekit |
| 57 |
> Available versions: 0.4.5_p20120320-r1 {acl debug doc pam |
| 58 |
> policykit selinux test KERNEL="linux"} |
| 59 |
> Installed versions: 0.4.5_p20120320-r1(18:13:50 30.01.2013)(acl |
| 60 |
> pam policykit -debug -doc -selinux -test KERNEL="linux") |
| 61 |
> |
| 62 |
> What exactly do you suggest now? |
| 63 |
|
| 64 |
If you have -consolekit, why it's still installed? What is pulling it |
| 65 |
into your system? Can you do a "equery depends consolekit"? |
| 66 |
|
| 67 |
Regards. |
| 68 |
-- |
| 69 |
Canek Peláez Valdés |
| 70 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 71 |
Universidad Nacional Autónoma de México |
Archives