Cannot shutdown via UI

Bug #871850 reported by Michael Nelson on 2011-10-10
60
This bug affects 13 people
Affects Status Importance Assigned to Milestone
Ubuntu
Low
Unassigned

Bug Description

STR: Click on the top-right menu widget and select 'Shut Down...'
ER: machine shuts down
AR: I'm logged out and returned to the lightdm screen. Selecting Shut down from the menu there brings up a confirmation dialog, but confirming that leaves the system unchanged (ie. on the lightdm screen).

Note: I then tried switching to a tty and doing `sudo shutdown 0` which started shutting down, but dropped me to a root prompt. Details: http://paste.ubuntu.com/705461/

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: upstart 1.3-0ubuntu10
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Mon Oct 10 17:44:19 2011
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: upstart
UpgradeStatus: Upgraded to oneiric on 2011-09-20 (20 days ago)

Michael Nelson (michael.nelson) wrote :
James Hunt (jamesodhunt) wrote :

Upstart bug split out to new bug 871860.

James Hunt (jamesodhunt) wrote :

The primary issue here I think is not with Upstart but with gnome/unity.

James Hunt (jamesodhunt) wrote :

Menu logout issues appear to be a unity issue.

affects: upstart (Ubuntu) → unity (Ubuntu)
Paul Sladen (sladen) on 2011-10-10
affects: unity (Ubuntu) → indicator-session (Ubuntu)
Ted Gould (ted) on 2011-10-13
affects: indicator-session (Ubuntu) → gnome-session (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-session (Ubuntu):
status: New → Confirmed

ApportVersion: 1.23-0ubuntu3
Architecture: amd64
CheckboxSubmission: f98186557c4fce5b597251bb5c2615ec
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
DistroRelease: Ubuntu 11.10
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
Package: gnome-session 3.2.0-0ubuntu3
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Tags: oneiric running-unity
Uname: Linux 3.0.0-12-generic x86_64
UpgradeStatus: Upgraded to oneiric on 2011-10-01 (19 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

tags: added: apport-collected

apport information

apport information

Sebastien Bacher (seb128) wrote :

thank you for your bug report, could you switch to a vt and type "ck-list-sessions > log" when you get the issue and add log to the bug?

Changed in gnome-session (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
affects: gnome-session (Ubuntu) → ubuntu
Changed in ubuntu:
status: Incomplete → Confirmed
Dmitry Shachnev (mitya57) wrote :

Huh, I'm able to reproduce it!

Do you have PPA version of liboverlay-scrollbar installed?

Changed in ubuntu:
status: Confirmed → Incomplete

No, I have not installed liboverlay-scrollbar.

Changed in ubuntu:
status: Incomplete → Confirmed
Dmitry Shachnev (mitya57) wrote :

What I get is definitely related to liboverlay-scrollbar.

Can you please reproduce this bug, login and attach here:
- Your ~/.xsession-errors and ~/.xsession-errors.old (these are hidden files)
- Output of "dmesg" command

Changed in ubuntu:
status: Confirmed → Incomplete
Changed in ubuntu:
status: Incomplete → Confirmed
Dmitry Shachnev (mitya57) wrote :

Thanks!
Unfortunately, these files don't contain any information about gnome-session crash, as mine do.

I will continue my investigations.

I think this bug is caused by Unity starting 2 sessions as seen in #10. May be causing other bugs.

My /etc/lightdm/lightdm.conf contained autologin-user=<user>.

Commenting out this line solved this issue for me. Autologin was not active - I had to login with password, and I never selected autologin.

Helipilot (huckleberry) wrote :

Thanks, Lazlo, that worked! :)

Fernando Sancho (toptnc) wrote :

I have solved it by adding "acpi=force" to boot options in grub.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers