Tom Gundersen writes:
> This should now be fixed, please let me know if that is not the case.
>
> Cheers,
>
> Tom
It works for me, now. Thanks!
Abdó.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailm
Daniel Mack writes:
> On 06/02/2015 04:34 PM, Martin Pitt wrote:
>> Merging manually is quite a bit of work, as you have to add a new
>> remote every time, fetch that, and pull from it. But it does keep a
>> cleaner git log history.
>
> Btw, Harald pointed me to this simple alias that makes check
Andrei Borzenkov writes:
> Was not it fixed by
> 693d371d30fee1da58365121801445b404416ada?
No.
The first time it broke was due to the udev manager wanting to be used by a
single process, and was fixed in 040e689654ef08c63.
Then it broke again by the commit you point 693d371d30fee1da58, due to
Hi,
Since the move of udev to sd-event, udevd --daemon is broken again, and breaks
the initramfs on arch linux, for example.
It turns out that sd_event_add_signal (in manager_listen) complains because the
sd_event event loop has moved through a fork.
I assume the intention in sd-event is not su
Hi,
Thanks a lot for your explanations!
> Either use a display manager or simply "update" your existing session's
> tty to graphical temporarily, rather then placing things on a new
> tty. (Note that the Fedora startx script does this implicitly this way)
I figured I could use a systemd unit a
Hi,
> Then, I want to manually launch my window manager, in a new logind session for
> my user, on a different tty.
>
> I tried adding User and PAMName to my window manager unit awesome.service
>
> <...>
>
> The unit fails with message
>
> systemd[21209]: Failed at step GROUP spawning
> /home/ab
Hello,
I'm happily using systemd 204 user instance to handle my desktop (xorg, awesome
wm, mpd, etc.) in Arch. I started experimenting with systemd 206 trying to adapt
my setup to the changes in cgroups, slices, and all that.
In 206, systemd user session is started automatically by pam_systemd w
