xfce4-screensaver-dialog crashed with SIGSEGV in g_main_context_dispatch()

Bug #2015985 reported by Jonathan Steinert
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xfce4-screensaver (Ubuntu)
New
Undecided
Unassigned

Bug Description

While locked, I find that I have to tap a key (ex. shift) 5-6 times to bring up the password prompt, each tap the screen will flash the password prompt and then immediately turn back off again. I do not know if this is related to the crash, but it is the only other mis-behavior of the lock screen.

Unlocking seems to work fine, and the machine does seem to be behaving otherwise.

$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu Lunar Lobster (development branch)
Release: 23.04

$ apt policy xfce4-screensaver
xfce4-screensaver:
  Installed: 4.16.0-1
  Candidate: 4.16.0-1
  Version table:
 *** 4.16.0-1 500
        500 http://us.archive.ubuntu.com/ubuntu lunar/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: xfce4-screensaver 4.16.0-1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: XFCE
Date: Wed Apr 12 02:02:45 2023
ExecutablePath: /usr/libexec/xfce4-screensaver-dialog
InstallationDate: Installed on 2023-04-10 (2 days ago)
InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
JournalErrors: -- No entries --
ProcCmdline: /usr/libexec/xfce4-screensaver-dialog --monitor=0 --height=1440 --width=2560
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x5599ae415ef1: mov (%rbx),%rdi
 PC (0x5599ae415ef1) ok
 source "(%rbx)" (0x90314d537f7a79d6) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xfce4-screensaver
StacktraceTop:
 ?? ()
 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
 gtk_main () from /lib/x86_64-linux-gnu/libgtk-3.so.0
Title: xfce4-screensaver-dialog crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to lunar on 2023-04-10 (1 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Jonathan Steinert (youhouka) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #2012826, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Jonathan Steinert (youhouka) wrote :

I'm getting errors saying that bug doesn't exist. Please advise on how I should proceed.

Revision history for this message
Jonathan Steinert (youhouka) wrote :

Oh, the system even says duplicate of private bug...

You advise me to read the other bug for workarounds or to supply additional information, but how can I do that if the bug is private?

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.