gnome-settings-daemon crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
nangaparbat:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu oneiric (development branch)
Release: 11.10
Codename: oneiric
nangaparbat:~$ lsb_release -rd
Description: Ubuntu oneiric (development branch)
Release: 11.10
nangaparbat:~$
nangaparbat:~$ apt-cache policy gnome-settings-
gnome-settings-
Installed: 3.1.3-0ubuntu5
Candidate: 3.1.3-0ubuntu5
Version table:
*** 3.1.3-0ubuntu5 0
500 http://
100 /var/lib/
nangaparbat:~$
When is seen?
This happens right after log in and is repeating.
What else sees this?
Also other bins see the same problem, crashed with SIGABRT in raise(). For example, I have reported one with synaptic package manager. evince is another program that sees this among others.
When was the first time this was seen?
This started happening with the first boot to upgrade to 11.10
This
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-
ProcVersionSign
Uname: Linux 3.0.0-5-generic x86_64
Architecture: amd64
Date: Sun Jul 17 12:18:16 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/false
PATH=(custom, no user)
Signal: 6
SourcePackage: gnome-settings-
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
__assert_fail () from /lib/x86_
_XReply () from /usr/lib/
XSync () from /usr/lib/
Title: gnome-settings-
UpgradeStatus: Upgraded to oneiric on 2011-07-17 (0 days ago)
UserGroups:
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #804221, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.