[Bug 1385572] Re: gnome-session not shutting down cleanly

Tim tim at feathertop.org
Tue Mar 10 04:36:50 UTC 2015


** Description changed:

- We have had reports going back to 13.10 that gnome-shell extensions are
- disabled after restart (LP: #1236749), I've only just managed to
- reproduce this and have discovered that gnome-session is not shutting
- down cleanly.
+ [Impact]
+ We have had reports going back to 13.10 that gnome-shell extensions are disabled after restart (LP: #1236749), this has probably been our #1 unresolved bug for the last few cycles. While this is the main user visible bug probably other bugs caused by this for example (BGO: #745707)
  
- Basically, X gets shutdown, which causes gnome-shell to abort, following
- this gnome-session tries to respawn gnome-shell which fails and due to
- this failure disables all shell extensions. I don't know enough about
- upstart to really understand what is going on but it appears this also
- affects unity and it just hasnt been noticed since there are probably no
- such side-effects happening there.
+ The cause was tracked down to gnome-session not shutting down cleanly
+ under upstart. Although the underlying issue seems to be the order in
+ which upstart takes down the various components in a user session, the
+ side-effects themselves appear to be caused by gnome-session continuing
+ to run when it should in fact be shutdown
  
- Filing this against upstart since this is not reproducible when using
- systemd init, though it may well be a bug in gnome-session, but related
- to upstart user sessions.
+ The fix updates the 103_kill_the_fail_whale.patch to force shutdown of
+ gnome-session. This is inline with the fix upstream for (BGO: #745707)
+ also.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 15.04
- Package: upstart 1.13.2-0ubuntu2
- ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
- Uname: Linux 3.16.0-22-generic x86_64
- NonfreeKernelModules: nvidia
- ApportVersion: 2.14.7-0ubuntu8
- Architecture: amd64
- CurrentDesktop: GNOME
- Date: Sat Oct 25 14:05:24 2014
- InstallationDate: Installed on 2012-09-23 (762 days ago)
- InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922)
- SourcePackage: upstart
- UpgradeStatus: No upgrade log present (probably fresh install)
- UpstartBugCategory: Session
- UpstartRunningSessionCount: 1
- UpstartRunningSessionVersion: upstart 1.13.2
- UpstartRunningSystemVersion: init (upstart 1.13.2)
+ [ Test Case ]
+ 1. Load gdm
+ 2. Login to gnome-shell using GNOME from the session list
+ 3. enable some extensions
+ 4. reboot system from user menu.
+ 5. login again to find extensions disabled.
+ 
+ [ Regression Potential ] 
+ Very low, the fail whale is meant to be fatal. The upstream dialog that is disabled in ubuntu does in fact cause gnome-session to get shutdown.

** Description changed:

  [Impact]
  We have had reports going back to 13.10 that gnome-shell extensions are disabled after restart (LP: #1236749), this has probably been our #1 unresolved bug for the last few cycles. While this is the main user visible bug probably other bugs caused by this for example (BGO: #745707)
  
  The cause was tracked down to gnome-session not shutting down cleanly
  under upstart. Although the underlying issue seems to be the order in
  which upstart takes down the various components in a user session, the
  side-effects themselves appear to be caused by gnome-session continuing
  to run when it should in fact be shutdown
  
  The fix updates the 103_kill_the_fail_whale.patch to force shutdown of
  gnome-session. This is inline with the fix upstream for (BGO: #745707)
  also.
  
  [ Test Case ]
+ Note: This is only reproducible under upstart init.
  1. Load gdm
  2. Login to gnome-shell using GNOME from the session list
  3. enable some extensions
  4. reboot system from user menu.
  5. login again to find extensions disabled.
  
- [ Regression Potential ] 
+ [ Regression Potential ]
  Very low, the fail whale is meant to be fatal. The upstream dialog that is disabled in ubuntu does in fact cause gnome-session to get shutdown.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1385572

Title:
  gnome-session not shutting down cleanly

Status in Ubuntu GNOME:
  New
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  We have had reports going back to 13.10 that gnome-shell extensions are disabled after restart (LP: #1236749), this has probably been our #1 unresolved bug for the last few cycles. While this is the main user visible bug probably other bugs caused by this for example (BGO: #745707)

  The cause was tracked down to gnome-session not shutting down cleanly
  under upstart. Although the underlying issue seems to be the order in
  which upstart takes down the various components in a user session, the
  side-effects themselves appear to be caused by gnome-session
  continuing to run when it should in fact be shutdown

  The fix updates the 103_kill_the_fail_whale.patch to force shutdown of
  gnome-session. This is inline with the fix upstream for (BGO: #745707)
  also.

  [ Test Case ]
  Note: This is only reproducible under upstart init.
  1. Load gdm
  2. Login to gnome-shell using GNOME from the session list
  3. enable some extensions
  4. reboot system from user menu.
  5. login again to find extensions disabled.

  [ Regression Potential ]
  Very low, the fail whale is meant to be fatal. The upstream dialog that is disabled in ubuntu does in fact cause gnome-session to get shutdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1385572/+subscriptions



More information about the Ubuntu-sponsors mailing list