** Description changed: Binary package hint: gnome-settings-daemon This crash in gnome-settings-daemon 3.0.2-1ubuntu3 occurred twice (nearly identical, not very informative stack traces) in succession after logging in to a unity-2d session on a recently updated Oneiric - i386 system. I think this crash may have occurred before the updates (if - so, I don't think I reported it then). My other Oneiric i386 system, - installed on identical (virtual) hardware and also fully updated, does - not appear to be affected by this bug. + i386 system. I think this crash may have occurred before the updates as + well (if so, I don't think I reported it then). My other Oneiric i386 + system, installed on identical (virtual) hardware and also fully + updated, does not appear to be affected by this bug. This might be bug 788710. I was able to produce that bug on this same system, by running gnome-settings-daemon in a Terminal after the two instances of this crash. But I suspect they are not really the same bug, because they both occurred in the same session without any package management operations performed in between them, yet the stack trace in this bug is much worse. Furthermore, right now it looks like the crash in bug 788710 occurs whenever a second concurrent instance of gnome- settings-daemon is launched (see https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/788710/comments/15, and also bug 796497, which is a duplicate of bug 788710). This bug looks cursorily similar to bug 779878, since they are both SIGSEGV crashes in gnome-settings-daemon with no function name (and thus have the same apport-generated title). Since bug 779878's stack trace has no symbol names or addresses and this stack trace has only the address where the segfault occurred and no other information, they cannot really be compared. Since there are no positive similarities besides occurring spontaneously (other than that, all the similarities between the two bugs are in the information that is *not* available about them), and bug 779878 occurred in Maverick while this bug occurred in Oneiric, I doubt they are the same bug. Due to stack corruption, the stack trace here is very bad--hopefully "Apport retracing service" will be able to process it and the core dump, and yield better information. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-settings-daemon 3.0.2-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39 Uname: Linux 2.6.39-3-generic i686 Architecture: i386 Date: Mon Jun 13 02:00:54 2011 Disassembly: => 0x4bfda70: Cannot access memory at address 0x4bfda70 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110610) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x4bfda70: Cannot access memory at address 0x4bfda70 PC (0x04bfda70) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: gnome-settings-daemon Stacktrace: #0 0x04bfda70 in ?? () No symbol table info available. Cannot access memory at address 0xbfdade4c StacktraceTop: ?? () Title: gnome-settings-daemon crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/796465 Title: gnome-settings-daemon crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/796465/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
