Hi,
plymouth watches for the creation of drm display devices during boot.
If it finds one, it starts a graphical splash and that is that.
However, if the system finishes loading drivers and no drm device is
available, it falls back onto a fbdev-based splash or a text-based
boot. Once it has
Hi,
On Mon, Mar 9, 2015 at 1:21 PM, Tom Gundersen t...@jklm.no wrote:
This sounds like a broken model (even if the problems you outlined
below were fixed). There is no reason to believe that all drm devices
will be available by the time udev has finished coldplug. Devices may
be enumerated at
From: Ray Strode rstr...@redhat.com
The initialization performed by systemd-vconsole-setup is reset
when changing console drivers (say from vgacon to fbcon), so we
need to run it in that case.
See
http://lists.freedesktop.org/archives/systemd-devel/2014-October/023919.html
http
From: Ray Strode rstr...@redhat.com
The initialization performed by systemd-vconsole-setup is reset
when changing console drivers (say from vgacon to fbcon), so we
need to run it in that case.
See
http://lists.freedesktop.org/archives/systemd-devel/2014-October/023919.html
http
Hi,
On Wed, Nov 5, 2014 at 9:53 AM, David Herrmann dh.herrm...@gmail.com wrote:
I had that change locally, but didn't push it because vconsole is
optional. Thus, this rule must be optional, too. I'm now digging into
autoconf+m4 to see how to do this... but I'm getting nowhere so far...
Well
Hi,
On Tue, Oct 21, 2014 at 1:39 PM, Ivan Shapovalov intelfx...@gmail.com wrote:
Please try editing
/usr/lib/systemd/system/systemd-vconsole-setup.service and
remove RemainAfterExit=yes, then regenerate your initramfs image by
running
dracut command. Add back RemainAfterExit=yes
Hi,
On Tue, Oct 16, 2012 at 2:20 PM, Lennart Poettering
lenn...@poettering.net wrote:
I have now commited a fix that achieves the same as yours but doesn't
key this of the static service database: I simply extended the
OpenSession() bus call to inform clients whether they are a new session
or
Hi,
Please test!
Will do.
I did:
$ loginctl show-session $XDG_SESSION_ID
$ su -
# exit
$ loginctl show-session $XDG_SESSION_ID
and in both cases
State=active
So patch seems to work.
Thanks
Ray
___
systemd-devel mailing list
Hi,
Some GDM/gnome-shell users having a rather strange issue where they
can't unlock their screen because logind thinks their session is no
longer active:
https://bugzilla.gnome.org/show_bug.cgi?id=685988
Turns out those users are running
$ su -
and upon typing
# exit
the users' sessions
Hi,
On Sun, Apr 24, 2011 at 5:19 PM, Lennart Poettering
lenn...@poettering.net wrote:
plymouth in Ubuntu 10.04 supports fsck progress report, and also
provides a chance for user to cancel running fsck. How to implement
this feature with systemd and plymouth?
It's actually a really hard
Hi,
On Tue, Apr 26, 2011 at 5:11 PM, Lennart Poettering
lenn...@poettering.net wrote:
I would suggest to leave the parsing of the fsck -C output to fsckd, as
well as the integration of multiple of these streams. fsckd would then
only pass one stream of progress bar information to plymouth. The
Hi,
On Tue, Mar 1, 2011 at 2:16 AM, Andrey Borzenkov arvidj...@gmail.com wrote:
Currently plymouth --wait will wait forever if daemon is not
started. This does not look right - we were asked to wait for
daemon to stop and daemon is obviously stopped. So make it
exit right away in this case.
12 matches
Mail list logo
