gnome-settings-daemon crashed with signal 5 in _XReply()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
maybe a duplicate, but all the others are rather old, IMO...
huludesktop not giving title bar and menus,
like if metatcity weren't running
and huludesktop is crashing
and not accepting a bug report on that as not one of ubuntu's...
but maybe that has something to do with this?
anyway, just apt-get update and upgraded recently
so also a possibility, or whatever you find in the crash reports...
this gnome-settings-
hoping not to have problems with it again...
I might do a gconf cleaner type thing to maybe
get rid of stuff. I had a differences on one upgrade
a while back of the conf file, IIRC, and chose the maintainers
version, so maybe some things not known here?
that were lost in the config?
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-
ProcVersionSign
Uname: Linux 3.2.0-5-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Fri Dec 16 10:44:27 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-settings-
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
_XReply () from /usr/lib/
_XGetWindowAtt
XGetWindowAttr
Title: gnome-settings-
UpgradeStatus: Upgraded to precise on 2011-11-25 (20 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
| Jerry (jerrywone) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #903973, 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.