gnome-settings-daemon crashed with SIGSEGV

Bug #798722 reported by Eliah Kagan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

On the Oneiric i386 20110617 daily-live, this crash in gnome-settings-daemon 3.0.2-1ubuntu3 occurred shortly but not immediately after logging in with a unity-2d session. This is almost certainly the same as Invalid bug 796465. It has the same or similar stack corruption too, which is why I doubt this report will be very useful, but perhaps "Apport retracing service" will be able to do something with it. The bot marked bug 796465 invalid and cited outdated packages--perhaps the situation will be slightly better this time around.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.0.2-1ubuntu3
ProcVersionSignature: Ubuntu 3.0-0.1-generic 3.0.0-rc2
Uname: Linux 3.0-0-generic i686
Architecture: i386
Date: Fri Jun 17 11:48:38 2011
Disassembly: => 0x3104a70: Cannot access memory at address 0x3104a70
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110617)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x3104a70: Cannot access memory at address 0x3104a70
 PC (0x03104a70) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
Stacktrace:
 #0 0x03104a70 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbff2160c
StacktraceTop: ?? ()
Title: gnome-settings-daemon crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x03104a70 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbff2160c
StacktraceTop: ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-settings-daemon (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgl1-mesa-glx: installed version 7.10.3-0ubuntu2, latest version: 7.10.3-0ubuntu3
libx11-xcb1: installed version 2:1.4.3-1ubuntu1, latest version: 2:1.4.3-2ubuntu1
libegl1-mesa: installed version 7.10.3-0ubuntu2, latest version: 7.10.3-0ubuntu3
libx11-xcb1-dbg: installed version 2:1.4.3-1ubuntu1, latest version: 2:1.4.3-2ubuntu1
dpkg: installed version 1.16.0~ubuntu8, latest version: 1.16.0.3ubuntu2
libegl1-mesa-dbg: installed version 7.10.3-0ubuntu2, latest version: 7.10.3-0ubuntu3
libgl1-mesa-glx-dbg: installed version 7.10.3-0ubuntu2, latest version: 7.10.3-0ubuntu3
libx11-6-dbg: installed version 2:1.4.3-1ubuntu1, latest version: 2:1.4.3-2ubuntu1
libx11-data: installed version 2:1.4.3-1ubuntu1, latest version: 2:1.4.3-2ubuntu1
libx11-6: installed version 2:1.4.3-1ubuntu1, latest version: 2:1.4.3-2ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.