gnome-screensaver crashed with SIGSEGV in XForceScreenSaver()

Bug #1716278 reported by TheMixtureMedia on 2017-09-10
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)

Bug Description


ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-screensaver 3.6.1-7ubuntu6
Uname: Linux 4.13.0-041300rc1-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Sep 10 16:02:00 2017
ExecutablePath: /usr/bin/gnome-screensaver
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
 org.gnome.desktop.session session-name 'gnome'
 org.gnome.desktop.session idle-delay uint32 900
InstallationDate: Installed on 2017-04-18 (145 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
 PATH=(custom, no user)
Signal: 11
SourcePackage: gnome-screensaver
 XForceScreenSaver () from /usr/lib/x86_64-linux-gnu/
 XResetScreenSaver () from /usr/lib/x86_64-linux-gnu/
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
Title: gnome-screensaver crashed with SIGSEGV in XForceScreenSaver()
UpgradeStatus: Upgraded to artful on 2017-04-29 (134 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video

TheMixtureMedia (mpmckinnon) wrote :

 XForceScreenSaver (dpy=0x9a7e52c900, mode=mode@entry=0) at ../../src/FSSaver.c:53
 XResetScreenSaver (dpy=<optimized out>) at ../../src/FSSaver.c:42
 gs_monitor_simulate_user_activity (monitor=0x9a7e584340) at gs-monitor.c:195
 listener_simulate_user_activity_cb (listener=<optimized out>, monitor=0x9a7e584340) at gs-monitor.c:287
 g_closure_invoke (closure=0x9a7e5b4210, return_value=0x0, n_param_values=1, param_values=0x7fff374682c0, invocation_hint=0x7fff37468240) at ../../../../gobject/gclosure.c:804

Changed in gnome-screensaver (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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
Mantas Kriaučiūnas (mantas) wrote :

Gnome-screensaver shouldn't be running on GNOME Shell. It's 5 years old software and is needed only for old GNOME flashback (fallback) session.

Paul Larson (pwlars) wrote :

This is a system that's gone through upgrades from at least xenial through artful. I never manually enabled it, but it could have been included in an older session along the way and carried forward if nothing stopped it.

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

Other bug subscribers