Send plymouth mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freedesktop.org/mailman/listinfo/plymouth
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of plymouth digest..."
Today's Topics:
1. Plymouth sets ISTRIP making 8-bit character input impossible
(Andrey Borzenkov)
2. GLIB Warning stops Splash (Patrick Kavajin)
3. Plymouth/Upstart integration (Colin Watson)
----------------------------------------------------------------------
Message: 1
Date: Sun, 7 Nov 2010 01:12:08 +0300
From: Andrey Borzenkov <[email protected]>
Subject: Plymouth sets ISTRIP making 8-bit character input impossible
To: [email protected]
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
I hit the following issue using plymouth 0.8.3 together with dracut.
Dracut installs the script that starts plymouth during boot; scripts
looks like
info "Starting plymouth daemon"
[ -x /bin/plymouthd ] && /bin/plymouthd --attach-to-session
/lib/udev/console_init tty0
/bin/plymouth --show-splash 2>&1 | vinfo
Script is always run, whether framebuffer is activated or not and
whether splash is requested or not.
I do not use framebuffer and when I had to break dracut init during
boot for debugging I found that above script sets istrip on console
making 8-bit input (actually, UTF-8) impossible.
Is there any reason for plymouth to set istrip? This looks rather
strange today, given that Linux defaults to Unicode on console for at
least three years I think.
Thank you!
-andrey
------------------------------
Message: 2
Date: Fri, 29 Oct 2010 12:33:07 +0200
From: Patrick Kavajin <[email protected]>
Subject: GLIB Warning stops Splash
To: [email protected]
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Im recieving a warning(glib warning getpwuid_r failed due to unknown user
id) which stops the Splash screen, how to fix that?
where's the code located which stops the splashscreen when a warning is
dropped?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/plymouth/attachments/20101029/ca6fd400/attachment.htm>
------------------------------
Message: 3
Date: Sun, 14 Nov 2010 15:23:25 +0000
From: Colin Watson <[email protected]>
Subject: Plymouth/Upstart integration
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
I've been working on solving the problem whereby users of Ubuntu server
systems (in particular) get no indication that Upstart jobs are
starting. Following suggestions from Scott James Remnant and Ray
Strode, I've written a plymouth-upstart-bridge process which connects to
Upstart's D-Bus interface and provides updates to Plymouth as events
change state. Here's a preliminary patch for review.
This patch depends on
https://code.launchpad.net/~cjwatson/upstart/state-changed and
https://code.launchpad.net/~cjwatson/upstart/goal-changed, which add a
few more features to Upstart's D-Bus interface.
A working Upstart job for this bridge process looks something like this:
# plymouth-upstart-bridge - Bridge Upstart state changes into Plymouth
#
# This helper process receives Upstart state changes over D-Bus and sends
# corresponding messages to Plymouth.
description "Bridge Upstart state changes into Plymouth"
start on (started dbus
or runlevel [06])
stop on stopping plymouth
console output
exec plymouth-upstart-bridge
(Ideally this would have 'start on (started plymouth and started dbus)',
but since the plymouth job is often started in the initramfs and
imported into Upstart's view of the world by means of a gross hack, that
won't work properly until Upstart grows the concept of states.)
Known flaws, which may or may not be critical:
* This still crashes now and again for me, and the output is a bit
messy because it tends to overlap with 'console output' jobs that
write their own progress messages.
* This only tells you when a job has started rather than letting you
know when it's starting, which isn't ideal because you can't see
what the boot process is currently hung up on, but doing otherwise
without crazily confusing overlapping messages requires something a
good deal more sophisticated than just writing to the console.
* The bridge process has some distribution-specific policy in it (the
console output format). Maybe folks can just patch this as
necessary; I'm not sure.
* I think probably plymouth-upstart-bridge ought to link against
libdbus directly rather than having libply.la do so.
* Since I had to use the low-level libdbus, the code is much longer
than I'd have liked.
Still, I think this is far enough along to ask for review. Comments?
Thanks,
--
Colin Watson [[email protected]]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plymouth-upstart.patch
Type: text/x-diff
Size: 52852 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/plymouth/attachments/20101114/73f33068/attachment.patch>
------------------------------
_______________________________________________
plymouth mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/plymouth
End of plymouth Digest, Vol 25, Issue 1
***************************************
