Re: [gentoo-user] systemd and gnome3

[Canek Peláez Valdés]

On Fri, Jul 20, 2012 at 10:54 AM, Peter Alfredsen
<peter.alfredsen@×××××.com> wrote:
> On Fri, Jul 20, 2012 at 5:30 PM, Canek Peláez Valdés <caneko@×××××.com> wrote:
>> On Fri, Jul 20, 2012 at 4:56 AM, Stefan G. Weichinger <lists@×××××.at> wrote:
>>>
>>> Does anyone use systemd on gentoo, with gnome3?
>>>
>>> Would someone share a tarball of /etc/systemd/system with me (off-list)
>>> so I could figure out what services and stuff are needed?
>>>
>>> Tried to follow the wiki-pages, but somehow after logging into gdm the
>>> session hangs ...
>>
>> I'm running GNOME 3 with, systemd 44 and udev 186, the first from my overlay:
>>
>> https://github.com/canek-pelaez/gentoo-systemd-only/
>>
>> However, the ebuilds in my overlay just change some dependencies so I
>> don't need to install OpenRC. Otherwise, they are identical to the
>> ones in the official tree. As Peter, I have the line
>>
>> -session        optional        pam_systemd.so
>>
>> in /etc/pam.d/system-auth. However, I still have consolekit started
>> (no problems whatsoever).
>
> There were some integration issues in upstream Gnome where most
> distros changed abruptly from using consolekit to systemd-logind which
> affected me when I went from systemd-44 to -185 because I ran into
> some race condition with -44. I imagine using consolekit will probably
> work in ~arch with no unmasks if you don't run into those race
> conditions on -44. But you gotta admit, it will probably be easier to
> follow the way Redhat is doing it than starting mixing and matching,
> because you will know that at least your combination works somewhere.

Not really "mix and match". I run systemd/udev/GNOME3  in ~amd64,
that's all, and I don't unmask any hard masked package. It's been
working fine like that since, oh I don't know, when they removed the
mask on GNOME 3?

Again, Stefan has probably a valid problem, and we need more info to
nail it down (hence the petition for $HOME/.xsession-errors). Just
unmasking everything and hoping that will solve the issues is usually
not the best practice; specially since the Gentoo developers haven't
decided how to handle the merge of udev/systemd.

Some want to provide a virtual/udev that systemd satisfy, and others
want to keep things as they were before the merge, with the udev
ebuild simply not installing the systemd parts.

Given that they haven't reached an agreement, I would *highly*
recommend not trying yet systemd/udev >= 186.

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