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

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

Bug Description

Just booting Quantal Alpha2 Live Version on a Dell Inspiron 1520

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-settings-daemon 3.4.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4
Uname: Linux 3.5.0-2-generic i686
ApportVersion: 2.2.5-0ubuntu1
Architecture: i386
CasperVersion: 1.318
Date: Thu Jun 28 11:58:46 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120627)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=
 TERM=linux
 PATH=(custom, no user)
 LANG=
SegvAnalysis:
 Segfault happened at: 0xb76f44b0 <gnome_rr_screen_get_dpms_mode+96>: mov 0xc(%eax),%eax
 PC (0xb76f44b0) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 gnome_rr_screen_get_dpms_mode () from /usr/lib/libgnome-desktop-3.so.4
 gnome_rr_screen_set_dpms_mode () from /usr/lib/libgnome-desktop-3.so.4
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 g_cclosure_marshal_VOID__VOIDv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Paolo Sammicheli (xdatap1) wrote :
visibility: private → public
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1018778

tags: added: iso-testing
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop: ?? ()

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):
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 a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgtk-3-common version 3.5.4-0ubuntu1 required, but 3.5.6-0ubuntu2 is available
libglib2.0-0 version 2.33.2-1 required, but 2.33.3-2 is available
gnome-desktop3-data version 3.5.2-0ubuntu3 required, but 3.5.3-0ubuntu1 is available
libgnome-desktop-3-4 version 3.5.2-0ubuntu3 required, but 3.5.3-0ubuntu1 is available
outdated debug symbol package for libgnome-desktop-3-4: package version 3.5.3-0ubuntu1 dbgsym version 3.5.2-0ubuntu3
libatk1.0-0 version 2.4.0-2 required, but 2.5.3-0ubuntu1 is available
outdated debug symbol package for libatk1.0-0: package version 2.5.3-0ubuntu1 dbgsym version 2.4.0-2
libgtk-3-0 version 3.5.4-0ubuntu1 required, but 3.5.6-0ubuntu2 is available
libatk1.0-data version 2.4.0-2 required, but 2.5.3-0ubuntu1 is available
outdated debug symbol package for libatk1.0-0: package version 2.5.3-0ubuntu1 dbgsym version 2.4.0-2
outdated debug symbol package for libsyncdaemon-1.0-1: package version 3.99.1-0ubuntu1 dbgsym version 3.99.0-0ubuntu1
outdated debug symbol package for gvfs-libs: package version 1.13.2-0ubuntu1 dbgsym version 1.13.1-0ubuntu1

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.