gnome-shell sometimes deadlocks after unlocking the session
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Shell |
New
|
Medium
|
|||
gnome-shell (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Sometimes gnome-shell freezes, soon after I unlock my session after I wake the laptop from suspend.
The symptoms match upstream bug https:/
I produced JS and C stack traces with all the debug symbols in a comment of the upstream bug report.
It appears that this bug is fixed by changing glib to release the cancellable mutex while inside callbacks. The fix almost made it in 2.38, but was reverted at the last minute. It was then reapplied to glib master (commit c8aba61, mentioned in BGO#676759) and will be released with glib 2.40.
It's probably too risky to backport that patch into saucy. What version of glib will trusty have? (Currently it has 2.38.)
Maybe it's possible to work around this in gnome-shell's javascript code (e.g. move the
fileLoad.
It would be sad if this bug remained unfixed in 14.04 LTS.
(Did I mention that this bug ticked me into typing my password into a web form? Could've been an IRC window.)
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-shell 3.8.4-0ubuntu5
ProcVersionSign
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Thu Dec 19 22:57:23 2013
DisplayManager: gdm
EcryptfsInUse: Yes
GsettingsChanges:
b'org.
b'org.
b'org.
InstallationDate: Installed on 2012-07-25 (512 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to saucy on 2013-10-17 (63 days ago)
gdmSessionLog:
/etc/gdm/Xsession: Beginning session setup...
localuser:mg being added to access control list
localuser:mg being added to access control list
Script for cjkv started at run_im.
Script for default started at run_im.
Changed in gnome-shell: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Trusty is tracking the glib 2.39 releases, has been for a while now, are you able to reproduce this issue on trusty?
Also what version were your backtraces from? they are using the old spidermonkey, so i guess it couldnt have been Saucy?