Ubuntu
upstart package

[Karmic] After shutdown from CLI system reboots into recovery menue instead of shutting down

Bug #414716 reported by Sokraates
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
bonobo-activation
Incomplete
Undecided
Unassigned
upstart (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Using Kubuntu Netbook remix on an AAO 110. All updates as of 16.08.2009.

Shutting the system down through the console with "sudo shutdown now" (shutdown through menues does not work, see bug 414715) will most of the times lead to the system rebooting into the recovery menue instead of shutting down. Every few attempts the system will shut down, however I have not been able to find a pattern (a.g. certain running apps).

I've experienced this bug with kernels 2.6.31-5 and 2.6.31-6.

I have not had similar problems on this machine running Jaunty UNR and KDE 4.3 (from backports).

Tags: karmic
Revision history for this message
Sokraates (sokraates) wrote :

After having worked around the above mentioned logout-bug (actually a duplicate of bug 410466) I realized that shutdowns from the menue do not lead to reboots.

Further testing shows that only shutdowns from CLI lead to reboots.

This is reproducible when using Konsole or a terminal (I only tried tty1). Having a KDE-session open or not does not affect this bug. I alsways used "sudo shutdown now".

The bug title has been updated accordingly.

summary: - [KNR] System reboots into recovery menue instead of shutting down
+ [Karmic] After shutdown from CLI system reboots into recovery menue
+ instead of shutting down
Revision history for this message
Philip Muškovac (yofel) wrote :

 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. Can you try with the final Ubuntu release? Thanks in advance.

affects: ubuntu → upstart (Ubuntu)
tags: added: karmic
Changed in upstart (Ubuntu):
status: New → Incomplete
Revision history for this message
Katsudon (katsudon) wrote :

Yes, it still affects me, also under GNOME.

Changed in upstart (Ubuntu):
status: Incomplete → New
Revision history for this message
Marián Bača (majoobaca-deactivatedaccount) wrote :

It affected me before, too (kernel 2.6.31.x) and it affects me also now (kernel 2.6.32). I have final release Ubuntu 9.10(gnome) i686. I found this line in /var/log/messages, when i tried to shutdown system using gnome-terminal:"Jan 9 17:26:08 majo-desktop bonobo-activation-server (majo-11135): could not associate with desktop session: Failed to connect to socket /tmp/dbus-Dp2hgWaRvK: Connection refused". If I shutdown system by graphical way, this error doesn't appear.

Revision history for this message
Marián Bača (majoobaca-deactivatedaccount) wrote :

Katsudon, can you submit output of "cat /var/log/messages | grep bonobo" ?

Revision history for this message
Katsudon (katsudon) wrote :

The output of "cat /var/log/messages | grep bonobo" is empty.

Revision history for this message
Marián Bača (majoobaca-deactivatedaccount) wrote :

Try shudown using terminal(I know it does not work) and when you log in try this command again.

Revision history for this message
Katsudon (katsudon) wrote :

If after "sudo shutdown now", the "rescue menu" shows up, the output of "cat /var/log/messages | grep bonobo" is empty (I checked that twice).

After one "sudo shutdown now" the outcome was different: all text consoles were locked and the graphical console shut down. The machine had to be turned down by "Ctrl-Alt-Del". After this reboot the outcome was:

Jan 9 18:23:47 representation bonobo-activation-server (piotr-10916): could not associate with desktop session: Failed to connect to socket /tmp/dbus-Fke4TiRjN7: Connection refused

Marián Bača (majoobaca-deactivatedaccount)
affects: upstart → bonobo-activation
Revision history for this message
Marián Bača (majoobaca-deactivatedaccount) wrote :

It appears to be bonobo-server bug, or it is not compatible with upstart. I am not sure, because I am not developer.

Changed in bonobo-activation:
status: New → Confirmed
Changed in upstart (Ubuntu):
status: New → Confirmed
Revision history for this message
Marián Bača (majoobaca-deactivatedaccount) wrote :

This is strange. I tried to shutdown system via rescue mod and the new rescue mod appeared. But there was no bonobo-server error in logfile.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Closing the Upstart task

Changed in upstart (Ubuntu):
status: Confirmed → Invalid
Marián Bača (majoobaca-deactivatedaccount)
Changed in bonobo-activation:
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.