gnome-screensaver crashed with SIGSEGV in gtk_style_context_get_valist()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-screensaver (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
~$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
~$ apt-cache policy gnome-screensaver
gnome-screensaver:
Installed: 3.2.1-0ubuntu1
Candidate: 3.2.1-0ubuntu1
Version table:
*** 3.2.1-0ubuntu1 0
500 http://
100 /var/lib/
When my screen goes to sleep, sometimes it doesn't wake up correctly. The whole screen is black except the mouse pointer which I can move around. If I vnc or teamview in to my box I can see the entire screen fine. I've found if I then start nvidia-settings, my screen comes back to life. Before I found this trick, I had to kill my session to be able to see my screen again.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-screensaver 3.2.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Feb 26 15:39:37 2012
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GsettingsGnomeS
org.gnome.
org.gnome.
ProcCmdline: gnome-screensaver
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f4d3d48a3a7 <gtk_style_
PC (0x7f4d3d48a3a7) ok
source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-screensaver
StacktraceTop:
gtk_style_
gtk_style_
gtk_style_
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
Title: gnome-screensaver crashed with SIGSEGV in gtk_style_
UpgradeStatus: Upgraded to precise on 2012-02-26 (0 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare
WindowManager: No value set for `/desktop/
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #926936, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.