gnome-screensaver-dialog crashed with SIGSEGV in gdk_property_change()

Bug #1123325 reported by Daniel Winzen on 2013-02-12
This bug affects 9 people
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)

Bug Description

My Computer was heavy overloaded with work and gnome-screensaver crashed while dimming the screen and shutting it down. It was a dark screen, but monitor didn't shut down. Moving the mouse or pressing a key on the Keyboard didn't help I switched to another console with CTRL+ALT+F1 and opened top. After a while the music playing in the background turned back and logging in into unity worked again. Then this apport bug-report came up.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-screensaver 3.6.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Tue Feb 12 19:11:55 2013
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-dialog
GnomeSessionIdleInhibited: No
 1: AppId = nautilus, Flags = 5, Reason = Dateien werden verschoben
 2: AppId = nautilus, Flags = 5, Reason = Dateien werden verschoben
 org.gnome.desktop.session idle-delay uint32 60
 org.gnome.desktop.session session-name 'ubuntu'
InstallationDate: Installed on 2012-04-03 (314 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120403)
MarkForUpload: True
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-dialog --status-message= --enable-switch
 PATH=(custom, no user)
 Segfault happened at: 0x7f9424aec180 <gdk_property_change>: mov 0x18(%rdi),%rax
 PC (0x7f9424aec180) 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-screensaver
 gdk_property_change () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/
Title: gnome-screensaver-dialog crashed with SIGSEGV in gdk_property_change()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

information type: Private → Public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-screensaver (Ubuntu):
status: New → Confirmed

 gdk_property_change (window=0x0, property=0x68, type=0x4, format=32, mode=GDK_PROP_MODE_REPLACE, data=0x12866b0 "\204", nelements=10) at /build/buildd/gtk+3.0-3.6.4/./gdk/gdkwindow.c:11348
 _gtk_selection_request (widget=0x1382000, event=0x12b22e0) at /build/buildd/gtk+3.0-3.6.4/./gtk/gtkselection.c:2453
 _gtk_marshal_BOOLEAN__BOXEDv (closure=0x12595d0, return_value=0x7fffdd707e10, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x1259600) at /build/buildd/gtk+3.0-3.6.4/./gtk/gtkmarshalers.c:130
 g_closure_add_marshal_guards (closure=0x7f9423fe8dd0 <g_byte_array_get_type+48>, pre_marshal_data=0xffffffff, pre_marshal_notify=0x0, post_marshal_data=<optimized out>, post_marshal_notify=<optimized out>) at /build/buildd/glib2.0-2.35.8/./gobject/gclosure.c:395
 thread_memory_from_self () at /build/buildd/glib2.0-2.35.8/./glib/gslice.c:500

Changed in gnome-screensaver (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
NoBugs! (luke32j) wrote :

Happening in 13.10 too, it was suspending while updates were installing, and I got this error.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers