Ubuntu
gnome-screensaver package

gnome-screensaver crashed with SIGSEGV in g_main_context_dispatch()

Bug #849600 reported by Jim Hunziker on 2011-09-14

582

This bug affects 114 people

Affects		Status	Importance	Assigned to	Milestone
	gnome-screensaver (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

Opening a new bug because this seems to be the first Oneiric beta1 instance of the bug. I run gnome-shell, and I was unable to log back in after the screen locked. Running gnome-shell --replace from a virtual terminal allowed me to unlock the screen. I don't believe it's a security issue because I still was required to enter a password to get back to my session.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-screensaver 3.1.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Tue Sep 13 21:07:00 2011
ExecutablePath: /usr/bin/gnome-screensaver
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fe9827167a0: mov 0x18(%rax),%rdi
PC (0x7fe9827167a0) ok
source "0x18(%rax)" (0xaaaaaaaaaaaaaac2) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-screensaver
StacktraceTop:
?? () from /usr/lib/libgnome-desktop-3.so.2
?? () from /usr/lib/libgnome-desktop-3.so.2
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-screensaver crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Jim Hunziker (landtuna) wrote on 2011-09-14:

Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (814 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (41.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (798 bytes, text/plain; charset="utf-8")
Registers.txt Edit (743 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (725 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.5 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (6.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-14:

StacktraceTop:
update_clock (data=0x216b840) at gnome-wall-clock.c:167
g_datetime_source_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at gnome-datetime-source.c:142
g_main_dispatch (context=0x20798e0) at /build/buildd/glib2.0-2.29.90/./glib/gmain.c:2441
g_main_context_dispatch (context=0x20798e0) at /build/buildd/glib2.0-2.29.90/./glib/gmain.c:3011
g_main_context_iterate (context=0x20798e0, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.29.90/./glib/gmain.c:3089

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-14: Stacktrace.txt

Stacktrace.txt Edit (2.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-14: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (7.0 KiB, text/plain)

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

Launchpad Janitor (janitor) on 2011-09-14

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

Marc Deslauriers (mdeslaur) on 2011-09-14

visibility:

private → public

Revision history for this message

Fabio Duran Verdugo (fabioduran) wrote on 2011-09-14:

This bug could be fixes in https://bugzilla.gnome.org/show_bug.cgi?id=658583

Revision history for this message

blacknight (tasos-1983) wrote on 2011-09-14:

i just now have this bug! i check it Fabio!

Revision history for this message

dmiranda (dmiranda) wrote on 2011-09-15:

gmome screensaver crashed when starting

Apport retracing service (apport) on 2011-09-15

tags:

added: bugpattern-needed

Revision history for this message

Cory Maccarrone (darkstar6262) wrote on 2011-09-16:

I just got this error too after resuming from suspend in gnome-shell. I was able to log in though.

Revision history for this message

Cory Maccarrone (darkstar6262) wrote on 2011-09-16:

And again -- it seems to be repeatable.

Revision history for this message

Saptarshi Ghosh (ghoshsaptarshi7) wrote on 2011-09-16:

#10

Steps to reproduce:
1. Log-in into gnome-shell
2. Leave the gnome-shell so that it gets locked automatically.
3. Try to log-in from the lock window
4. It will crash after a while.
Note:- Requires installtion of package "gnome-shell" from ubuntu's main repo

Revision history for this message

Detlef Lechner (detlef-lechner) wrote on 2011-09-17:

#11

I am affected too after today's dist-upgrade.
~$ uname -a
Linux T61 3.0.0-11-server #18-Ubuntu SMP Wed Sep 14 01:20:37 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message

z3z (z3z) wrote on 2011-09-17:

#12

I'm experiencing similar, however I don't have the screen locked (i.e. I don't need to type in my password after the screensaver has activated). I'm also running Gnome-Shell.

After ten mins or so, my screen blanks (as I don't have any screensaver set). When I move the mouse or touch a key to activate the screen, everything comes back as it should, however soon after an error comes up saying there is a problem with the screensaver.

Revision history for this message

kingtiger01 (mnovick1988) wrote on 2011-09-18:

#13

Same as Rrrrube, although i did have a Screensaver set, Although it never Displayed.

Revision history for this message

Jeffrey Tees (jeff-tees) wrote on 2011-09-18:

#14

No Screensaver set, Screen seems to blank anyway after about ten minutes, no way to switch it off in Settings. When playing a video, even when the player is set to inhibit screensaver during playback it blanks anyway. Don't know if this is related to this crash which occured after swiping the mouse to bring back the screen but it bugs the hell out of me so thought I i'd mention it anyway...

Revision history for this message

Oleg Lee (lee-oleg) wrote on 2011-09-18: Re: [Bug 849600] Re: gnome-screensaver crashed with SIGSEGV in g_main_context_dispatch()

#15

There is one way to temporary fix it.
Start gnome-screensaver in console, and you can lock the screen.
But unfortunatly, screensaver segfault after unlock the screen.
18.09.2011 22:57 пользователь "Jeffrey Tees" <email address hidden>
написал:
> No Screensaver set, Screen seems to blank anyway after about ten
> minutes, no way to switch it off in Settings. When playing a video, even
> when the player is set to inhibit screensaver during playback it blanks
> anyway. Don't know if this is related to this crash which occured after
> swiping the mouse to bring back the screen but it bugs the hell out of
> me so thought I i'd mention it anyway...
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (852053).
> https://bugs.launchpad.net/bugs/849600
>
> Title:
> gnome-screensaver crashed with SIGSEGV in g_main_context_dispatch()
>
> To manage notifications about this bug go to:
>
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/849600/+subscriptions

Revision history for this message

tfmoraes (tfmoraes) wrote on 2011-09-18:

#16

Gnome-screensaver crashes but I'm able to lock the screen.

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2011-09-20:

#17

Is anybody able to reproduce the issue with libgnome desktop 3.1.92 ?

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

Pedro Villavicencio (pedro) on 2011-09-20

tags:	removed: bugpattern-needed
tags:	added: bugpattern-written

Revision history for this message

Fabio Duran Verdugo (fabioduran) wrote on 2011-09-22:

#18

Pedro, I can reproduce with libgnome-desktop-3-2 (3.1.92-0ubuntu1 )

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2011-09-26:

#19

Fabio can reproduce it, we're working on getting a backtrace with latest package.

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

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2011-09-27:

#20

it is now fixed with latest packages , if someone else can reproduce please provide a backtrace as well, thanks.

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

Revision history for this message

wavded (wavded) wrote on 2011-10-08:

#21

Crashed for me. Closed laptop lid, went into suspend. Opened. Froze screen, couldn't use any GUI. Switched to TTY2, viewed top, gnome-screensaver was at 100%, killed it, and then switched back and it was unlocked.

Revision history for this message

wavded (wavded) wrote on 2011-10-08:

#22

Another way this crashes, is anytime it wakes up from a suspend when I have two monitors in use, it doesn't even load back up, just shows a black screen, have to power off machine.

Revision history for this message

Bruno Roost (stenbuk) wrote on 2011-10-20:

#23

Reproduced with 11.10 gnome-shell. Screen Lock forced with CTR-ALT-L. No way to unlock screen respectivly force login mask.
Only switch to tty2, kill gnome-screensaver, switch back helps.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

gnome-bugs #658583
[RESOLVED FIXED] Edit

Bug watches keep track of this bug in other bug trackers.

Ubuntugnome-screensaver package

gnome-screensaver crashed with SIGSEGV in g_main_context_dispatch()

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
gnome-screensaver package