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

Bug #838670 reported by shachafgo
146
This bug affects 32 people
Affects Status Importance Assigned to Milestone
GNOME Settings Daemon
Fix Released
Critical
gnome-settings-daemon (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

just happened

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.5-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelModules: wl fglrx
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 1 12:06:02 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f10cd5e8199 <gnome_rr_screen_get_dpms_mode+73>: mov 0x18(%rdi),%rax
 PC (0x7f10cd5e8199) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" 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.2
 gnome_rr_screen_set_dpms_mode () from /usr/lib/libgnome-desktop-3.so.2
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode()
UpgradeStatus: Upgraded to oneiric on 2011-08-06 (25 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev root sambashare sudo tape video

Revision history for this message
shachafgo (shachaf-gold) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gnome_rr_screen_get_dpms_mode (screen=0x0, mode=0x7fff1f5282ac, error=0x7fff1f5282f8) at gnome-rr.c:1189
 gnome_rr_screen_set_dpms_mode (screen=0x0, mode=GNOME_RR_DPMS_ON, error=0x7fff1f5282f8) at gnome-rr.c:1251
 do_lid_open_action (manager=0x20df040) at gsd-power-manager.c:2073
 up_client_changed_cb (manager=0x20df040, client=<optimized out>) at gsd-power-manager.c:2160
 up_client_changed_cb (client=<optimized out>, manager=0x20df040) at gsd-power-manager.c:2138

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
Revision history for this message
Pedro Villavicencio (pedro) wrote :

seems to be a libgnome-desktop crash, reassigning.

affects: gnome-settings-daemon (Ubuntu) → gnome-desktop3 (Ubuntu)
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=657924

Changed in gnome-desktop3 (Ubuntu):
status: New → Triaged
Changed in gnome-desktop:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

and back to g-s-d

affects: gnome-desktop3 (Ubuntu) → gnome-settings-daemon (Ubuntu)
affects: gnome-desktop → gnome-settings-daemon
Changed in gnome-settings-daemon:
status: New → Fix Released
Changed in gnome-settings-daemon (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Bill Maxwell (wamaxwell) wrote :

Kinda weird...did not have a single problem or bug in alpha 1, but now have a problem in alpha 2.

Revision history for this message
matti salminen (salmiset) wrote :

Confirming that the bug is back in 12.10 Alpha 2.

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.