This bug was fixed in the package usplash - 0.5.24
---
usplash (0.5.24) intrepid; urgency=low
* debian/usplash.init, stop(): Call usplash_down if usplash is not already
running. In previous releases, the display manager started it, but in the
modern ConsoleKit world,
On Mon, Oct 06, 2008 at 11:05:45AM -, shane19174 wrote:
Not 100% sure if I'm posting to the right bug, but my issue is the
following: like many others, I initially get text instead of the splash
when shutting down/rebooting (I'm running Intrepid beta with all
updates). The splash does
Matt,
Thanks for the quick reply. So what can one do about this? I don't quite
understand the workaround posted by Martin above, and I'm wondering if
this is something that will be fixed with an update or something that an
end user like myself should try to fix on their own. (I realize that
this
Not 100% sure if I'm posting to the right bug, but my issue is the
following: like many others, I initially get text instead of the splash
when shutting down/rebooting (I'm running Intrepid beta with all
updates). The splash does eventually show up, with an empty progress
bar, following some
I'm wondering if this is something that will be fixed with an update
Yes, it will be. Working on it ASAP...
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: regression
** Tags removed: regression-potential
** Changed in: gnome-session (Ubuntu Intrepid)
Status: Confirmed = Triaged
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification because you are a member of
When this bug is fixed, bug 277058 should be fixed at the same time.
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I played around with this a little bit. Adding the usplash_down call to
/etc/init.d/usplash stop fixes the bug to 80%, you still get some
seconds of a black text screen with a cursor, until usplash kicks in
(the time between killing gdm and calling K01usplash).
Calling usplash_down right before
I'd rename it to K02usplash for safety
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On Thu, Oct 02, 2008 at 10:38:15AM -, Martin Pitt wrote:
I played around with this a little bit. Adding the usplash_down call to
/etc/init.d/usplash stop fixes the bug to 80%, you still get some
seconds of a black text screen with a cursor, until usplash kicks in
(the time between killing
** Changed in: usplash (Ubuntu Intrepid)
Sourcepackagename: gnome-session = usplash
Assignee: (unassigned) = Martin Pitt (pitti)
Status: Triaged = In Progress
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification
Just to add a cat amongst the pigeons this fault is in Kubuntu as well!
same issue but I use KDM.
Cary
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: regression-potential
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
We offer services of World of Warcraft US Power Leveling and World of Warcraft
EU Power Leveling,Lineage2 and EverQuest2, Maple Story US/EU, SilkRoad.
Unexampled WoW Powerleveling service and inexpensive wow Powerleveling. World
of Warcraft Power leveling create for you. AOC Power
I think some of the comments from people who think /etc/init.d/gdm
should call usplash_down are actually about this bug (eg. bug 159262).
Also, the end result seems to be that something else starts usplash much
later in the init sequence, which results in an empty usplash progress
bar at the very
thank matt, the version you mention looks a debian one and not an ubuntu
one, the current intrepid package still have this patch here, that's
weird
** Changed in: gdm (Ubuntu Intrepid)
Importance: Undecided = Medium
Status: New = Incomplete
--
usplash is not started on shutdown/reboot
** Description changed:
Binary package hint: gdm
usplash_down should be invoked by gdm when it is shutting down, so that
the progress bar is displayed for the shutdown sequence. It doesn't
- seem to do this anymore (Intrepid), and the patch which implemented this
-
confirming the issue
** Changed in: gdm (Ubuntu Intrepid)
Status: Incomplete = Confirmed
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I instrumented /sbin/usplash_down and straced gdm, and it's simply never
invoked. Perhaps the code paths changed and the patch no longer has the
intended effect?
--
usplash is not started on shutdown/reboot
https://bugs.launchpad.net/bugs/264696
You received this bug notification because you
I think what's happened is that the actual shutdown process is now
invoked via consolekit rather than from gdm:
5489 ?S 0:00 /usr/lib/policykit/polkitd
5497 ?S 0:00 /bin/sh /usr/lib/ConsoleKit/scripts/ck-system-restart
5498 ?R 0:00 \_ /bin/sh
This ought to be fixed somewhere below gdm, either in gnome-session or
consolekit. gnome-session has:
static void
do_attempt_shutdown (GsmConsolekit *consolekit)
{
if (gsm_consolekit_can_stop (consolekit)) {
gdm_set_logout_action (GDM_LOGOUT_ACTION_NONE);
21 matches
Mail list logo
