gnome-settings-daemon crashed with SIGSEGV

Bug #197706 reported by emil01
6
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

no idea

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Mar 2 15:00:50 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
NonfreeKernelModules: cdrom
Package: gnome-settings-daemon 2.21.91-0ubuntu5
PackageArchitecture: i386
ProcCmdline: gnome-settings-daemon
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-settings-daemon
Stacktrace:
 #0 0xb6da3be1 in ?? () from /usr/lib/libgnome-desktop-2.so.2
 #1 0xbff588e8 in ?? ()
 #2 0xb6da4990 in ?? () from /usr/lib/libgnome-desktop-2.so.2
 #3 0x080a6a40 in ?? ()
 #4 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /usr/lib/libgnome-desktop-2.so.2
 ?? ()
 ?? () from /usr/lib/libgnome-desktop-2.so.2
 ?? ()
 ?? ()
Title: gnome-settings-daemon crashed with SIGSEGV
Uname: Linux 2.6.24-10-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev vboxusers video

Tags: apport-crash
Revision history for this message
emil01 (emil01) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:screen_info_new (screen=<value optimized out>) at randrwrap.c:606
rw_screen_new (gdk_screen=0x806d0b0, callback=0xb63a0340 <on_randr_event>, data=0x0)
gsd_xrandr_manager_start (manager=0x8077508, error=0xbff58960) at gsd-xrandr-manager.c:114
impl_activate (plugin=0x8085a18) at gsd-xrandr-plugin.c:78
gnome_settings_plugins_engine_activate_plugin (info=0x8083218)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnome-settings-daemon:
importance: Undecided → Medium
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.