Notebook does not suspend - not a kernel- but a design problem

[dl9sau]

Binary package hint: gnome-power-manager

With jaunty i had and still have several quality issues. One of them is that vlc segfaults after playing one song. Until this will be fixed (bug is reported), I tried not to use it, because it causes my notebook not to suspend-to-ram anymore. But i forgot it, and now again I'm sitting here, ready to go, but can't.

Some of the obviously too complex programs pass messages to each other. I cannot tell wo tells whom what. Gone are the good old days of a comprehensive, deterministic unix system. But back to the problem. The gnome-power-manager icon talks to me "
Anforderung einer Aktion

vlc verhinderte die Ausführung der Aktion: Playing some media.."
(what could, on an english speaking system, may appear as "Demand of an action: vlc prevented the execution of an action: Playing some media.."

There's no vlc running. VLC segfaulted many hours ago. But jaunty still patronizes me, thinking to know it better than I and refuses the suspend process to complete.

Here's an strace of the communication:
strace -fp 8442 -s 2048 -e read,writev
read(15, "l\4\1\1\36\0\0\0~m\0\0\237\0\0\0\1\1o\0008\0\0\0/org/freedesktop/Hal/devices/computer_logicaldev_input_2\0\0\0\0\0\0\0\0\2\1s\0\32\0\0\0org.freedesktop.Hal.Device\0\0\0\0\0\0\3\1s\0\t\0\0\0Condition\0\0\0\0\0\0\0\10\1g\0\2ss\0\7\1s\0\6\0\0\0:1.124\0\0\r\0\0\0ButtonPressed\0\0\0\5\0\0\0sleep\0"..., 2048) = 206
read(15, 0x2749800, 2048) = -1 EAGAIN (Resource temporarily unavailable)
read(3, 0x2456744, 4096) = -1 EAGAIN (Resource temporarily unavailable)
writev(15, [{"l\1\0\1\0\0\0\0\374\22\0\0\231\0\0\0\1\1o\0$\0\0\0/org/freedesktop/ConsoleKit/Session1\0\0\0\0\6\1s\0\32\0\0\0org.freedesktop.ConsoleKit\0\0\0\0\0\0\2\1s\0\"\0\0\0org.freedesktop.ConsoleKit.Session\0\0\0\0\0\0\3\1s\0\10\0\0\0IsActive\0\0\0\0\0\0\0\0"..., 176}, {""..., 0}], 2) = 176
read(15, "l\2\1\1\4\0\0\0\262\2\0\0-\0\0\0\6\1s\0\5\0\0\0:1.24\0\0\0\5\1u\0\374\22\0\0\10\1g\0\1b\0\0\7\1s\0\4\0\0\0:1.1\0\0\0\0\1\0\0\0"..., 2048) = 68
read(15, 0x2749800, 2048) = -1 EAGAIN (Resource temporarily unavailable)
writev(3, [{"(\7\4\0;\0\340\1\252\0\0\0\0\0\0\0"..., 16}, {NULL, 0}, {""..., 0}], 3) = 16
read(3, "\1\1\314T\0\0\0\0+\0\0\1B\4\1\0`\324}\0\0\0\0\0(\0\0\0\0\0\0\0"..., 4096) = 32
read(3, 0x2456744, 4096) = -1 EAGAIN (Resource temporarily unavailable)
writev(11, [{"l\1\0\1\10\1\0\0>\0\0\0\233\0\0\0\1\1o\0\36\0\0\0/org/freedesktop/Notifications\0\0\6\1s\0\35\0\0\0org.freedesktop.Notifications\0\0\0\2\1s\0\35\0\0\0org.freedesktop.Notifications\0\0\0\3\1s\0\6\0\0\0Notify\0\0\10\1g\0\rsusssasa{sv}i\0\0\0\0\0\0"..., 176}, {"\21\0\0\0Energieverwaltung\0\0\0\0\0\0\0\22\0\0\0gtk-dialog-warning\0\0\30\0\0\0Anforderung einer Aktion\0\0\0\0N\0\0\0<b>vlc</b> verhinderte die Ausf\303\274hrung der Aktion: <b>Playing some media.</b>.\0\0\0\0\0\0Q\0\0\0\1\0\0\0x\0\1i\0\0\0\0N\4\0\0\1\0\0\0y\0\1i\0\0\0\0\r\0\0\0\n\0\0\0window-xid\0\1u\0\0\0;\0\340\1\10\0\0\0xdisplay\0\1s\0\4\0\0\0:0.0\0\0\0\0000u\0\0"..., 264}], 2) = 440
read(11, "l\2\1\1\4\0\0\0k\0\0\0.\0\0\0\6\1s\0\5\0\0\0:1.23\0\0\0\5\1u\0>\0\0\0\10\1g\0\1u\0\0\7\1s\0\5\0\0\0:1.14\0\0\0(\0\0\0"..., 2048) = 68
read(11, 0x2716f30, 2048) = -1 EAGAIN (Resource temporarily unavailable)
read(3, 0x2456744, 4096) = -1 EAGAIN (Resource temporarily unavailable)
^CProcess 8442 detached

It's 19:37 MESZ. vlc died:
May 5 00:53:19 tomate kernel: [40366.385813] vlc[25533]: segfault at 7fbfb73c2610 ip 00007fbfb73c2610 sp 00007fbfb7fff108 error 14 in libnss_nis-2.9.so[7fbfb71db000+1ff000
It was started:
May 5 00:49:29 tomate dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.33" (uid=1000 pid=8687 comm="/usr/lib/indicator-applet/indicator-applet --oaf-a") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_reply=0 destination=":1.135" (uid=1000 pid=25521 comm="vlc theseAreTheCommandArgumentsAndItsAPrivacyIssueThatSeveralProgramsMessAuthLogUpWithTheArgumentsOfUsersPrograms")

This will be another day I'll loose all my windows. Well, like - ....

[dl9sau (thomas-x-berg)]

gnome-power-manager 2.24.2-2ubuntu8
ubuntu jaunty 64bit
2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[dl9sau (thomas-x-berg)]

The application gnome-power-manager does not crash.

But it's a malfunction that the crash of another application make the program think that the suspendtoram should not be granted. The crash had no side effects like busy devices or kernel oopses.

I suppose (but I'm not sure) it's a decision of the gnome-power-manager-applet itself, because the strace showed that it gets the "sleep button" event.

This is a bug.The need of reboot of the system just because a program does a wrong decision (becaue it believes the system is in another state) is not a solution.
In my case, I'll have to leave my notebook at home this evening.

[dl9sau (thomas-x-berg)]

I traced now the problem down: there seems no dependency to another problem telling that an application asks for prepending the resume.
Hot-Fix: if you still like to keep your system gnome and like to use the integration with gnome-power-manager:
killall -TERM gnome-power-manager; gnome-power-manager &
gnome-power-manager needs to be fixed.
It seems not to store the situation in any file. If it resist to accept the resume because it thinks it would be wrong (which was'nt, in my case), then the restart of the program helps. The new proces knows anything about the decisions of his ancestors.

[dl9sau (thomas-x-berg)]

After not being able to use vlc during my whole jaunty period, because it segfaulted right after playing the first song, I'm happy to announce that vlc works again with ubuntu karmic.

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you? Thanks in advance.

[dl9sau (thomas-x-berg)]

It was a jaunty bug. Jaunty was the most instable ubuntu version for
me.
Since I upgraded to karmic, this error did not appear (afaik).

On 2010-01-14 21:26:01 -0000, Kamus <email address hidden>
wrote in <email address hidden>:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering if this is still an issue
> for you? Thanks in advance.
>
> --
> Notebook does not suspend - not a kernel- but a design problem
> https://bugs.launchpad.net/bugs/372324
> You received this bug notification because you are a direct subscriber
> of the bug.

[Launchpad Janitor (janitor)]

[Expired for gnome-power-manager (Ubuntu) because there has been no activity for 60 days.]