gnome-settings-daemon crashed with SIGSEGV on try to open gbrainy

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

Bug Description

bug compared when i try to open gbrainy

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic x86_64
Architecture: amd64
Date: Fri Jul 1 21:31:10 2011
Disassembly: => 0x7f37add45b10: Cannot access memory at address 0x7f37add45b10
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110701)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f37add45b10: Cannot access memory at address 0x7f37add45b10
 PC (0x7f37add45b10) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
Stacktrace:
 #0 0x00007f37add45b10 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff02b07438
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
mario catena (mcblackmar02) wrote :
visibility: private → public
tags: added: iso-testing
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007f37add45b10 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff02b07438
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:

libavahi-common3: installed version 0.6.30-3ubuntu3, latest version: 0.6.30-4ubuntu1
libcanberra-gtk3-0-dbg: installed version 0.28-0ubuntu5, latest version: 0.28-0ubuntu7
libpulse0-dbg: installed version 1:0.9.23-0ubuntu1, latest version: 1:0.9.23-0ubuntu2
libpulse-mainloop-glib0-dbg: installed version 1:0.9.23-0ubuntu1, latest version: 1:0.9.23-0ubuntu2
multiarch-support: installed version 2.13-6ubuntu2, latest version: 2.13-8ubuntu2
fontconfig-config: installed version 2.8.0-3, latest version: 2.8.0-3ubuntu1
libcanberra0-dbg: installed version 0.28-0ubuntu5, latest version: 0.28-0ubuntu7
libc-bin: installed version 2.13-6ubuntu2, latest version: 2.13-8ubuntu2
fontconfig: installed version 2.8.0-3, latest version: 2.8.0-3ubuntu1
libpulse-mainloop-glib0: installed version 1:0.9.23-0ubuntu1, latest version: 1:0.9.23-0ubuntu2
libfontconfig1-dbg: installed version 2.8.0-3, latest version: 2.8.0-3ubuntu1
libfontconfig1: installed version 2.8.0-3, latest version: 2.8.0-3ubuntu1
libc6-dbg: installed version 2.13-6ubuntu2, latest version: 2.13-8ubuntu2
libavahi-common-data: installed version 0.6.30-3ubuntu3, latest version: 0.6.30-4ubuntu1
libc6: installed version 2.13-6ubuntu2, latest version: 2.13-8ubuntu2
libpulse0: installed version 1:0.9.23-0ubuntu1, latest version: 1:0.9.23-0ubuntu2
libcanberra0: installed version 0.28-0ubuntu5, latest version: 0.28-0ubuntu7
libavahi-client3: installed version 0.6.30-3ubuntu3, latest version: 0.6.30-4ubuntu1
libcanberra-gtk3-0: installed version 0.28-0ubuntu5, latest version: 0.28-0ubuntu7
gconf2-common: installed version 2.32.4-1ubuntu1, latest version: 2.32.4-1ubuntu2
libgconf2-4: installed version 2.32.4-1ubuntu1, latest version: 2.32.4-1ubuntu2

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-amd64-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.