gnome-settings-daemon crashed with SIGSEGV in g_strdup()

Bug #965171 reported by Wojciech Myszka
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Medium
Unassigned

Bug Description

No much. Freshly booted system with one application (google-chrome)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.3.92-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Mon Mar 26 13:12:00 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/false
 LANG=pl_PL.UTF-8
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
Title: gnome-settings-daemon crashed with SIGSEGV in g_strdup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Wojciech Myszka (myszka-norka) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_strdup (str=0x1 <Address 0x1 out of bounds>) at /build/buildd/glib2.0-2.31.22/./glib/gstrfuncs.c:355
 schedule_call_in_idle (call_type=CALL_TYPE_NAME_VANISHED, client=0x2035950) at /build/buildd/glib2.0-2.31.22/./gio/gdbusnamewatching.c:193
 do_call (client=0x2035950, call_type=CALL_TYPE_NAME_VANISHED) at /build/buildd/glib2.0-2.31.22/./gio/gdbusnamewatching.c:214
 ffi_call_unix64 () at ../src/x86/unix64.S:75
 ffi_call (cif=0x7fb173ebd5e0, fn=0x7fb17aa0b900 <on_connection_disconnected>, rvalue=<optimized out>, avalue=<optimized out>) at ../src/x86/ffi64.c:486

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
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.