dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #29136
[Bug 1284017] Re: gnome-shell crashed with SIGABRT in g_thread_abort()
It's worth noting that this bug can no longer occur as it is described
here -- g_mutex_lock() has been rewritten and the new version doesn't
abort.
That said, the underlying issue that was causing the misuse of a mutex
could very well still exist... Unfortunately, it's very difficult to
guess what that may be, at this point.
** Bug watch added: GNOME Bug Tracker #724929
https://bugzilla.gnome.org/show_bug.cgi?id=724929
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to d-conf in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1284017
Title:
gnome-shell crashed with SIGABRT in g_thread_abort()
Status in A simple key-based configuration system:
Unknown
Status in d-conf package in Ubuntu:
New
Bug description:
gnome-shell crashed on system restart.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-shell 3.10.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Feb 24 12:24:40 2014
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2014-02-09 (14 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140121.1)
ProcCmdline: gnome-shell --mode=gdm
ProcEnviron:
SHELL=/bin/false
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
Title: gnome-shell crashed with SIGABRT in g_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1284017/+subscriptions