workrave segfault launch on Wayland

Bug #1997349 reported by Marcos Dione
This bug affects 1 person
Affects Status Importance Assigned to Milestone
workrave (Debian)
workrave (Ubuntu)

Bug Description

workrave just crashes with almost no output. I think the issues appeared ever since I upgraded to 22.10. Here's a backtrace:

Thread 1 "workrave" received signal SIGSEGV, Segmentation fault.
0x000055555579ae80 in ?? ()
(gdb) bt
#0 0x000055555579ae80 in ?? ()
#1 0x00007ffff7cf8b15 in XQueryExtension (dpy=0x5555557980d0, name=0x7ffff7f92000 "MIT-SCREEN-SAVER", major_opcode=0x7fffffffd7c4,
    first_event=0x7fffffffd7c8, first_error=0x7fffffffd7cc) at ../../src/QuExt.c:48
#2 0x00007ffff7cecb46 in XInitExtension (dpy=dpy@entry=0x5555557980d0, name=name@entry=0x7ffff7f92000 "MIT-SCREEN-SAVER") at ../../src/InitExt.c:47
#3 0x00007ffff6308821 in XextAddDisplay (extinfo=0x7ffff7f94130 <_screen_saver_info_data>, dpy=0x5555557980d0,
    ext_name=ext_name@entry=0x7ffff7f92000 "MIT-SCREEN-SAVER", hooks=hooks@entry=0x7ffff7f940c0 <screen_saver_extension_hooks>,
    nevents=nevents@entry=1, data=data@entry=0x0) at ../../src/extutil.c:110
#4 0x00007ffff7f91370 in find_display (dpy=<optimized out>) at ../../src/XScrnSaver.c:77
#5 0x00007ffff7f91535 in XScreenSaverQueryExtension (dpy=<optimized out>, event_base_return=0x7fffffffd87c, error_base_return=0x7fffffffd878)
    at ../../src/XScrnSaver.c:158
#6 0x00005555556b316c in XScreenSaverMonitor::init (this=0x55555583fa90) at ../../../backend/src/unix/
#7 0x00005555556b21e1 in UnixInputMonitorFactory::get_monitor (this=0x5555559114e0, capability=<optimized out>)
    at ../../../backend/src/unix/
#8 0x00005555556b734d in InputMonitorFactory::get_monitor (capability=IInputMonitorFactory::CAPABILITY_ACTIVITY)
    at ../../../backend/src/
#9 ActivityMonitor::ActivityMonitor (this=<optimized out>, this=<optimized out>) at ../../../backend/src/
#10 0x000055555568fa1b in Core::init_monitor (this=0x5555558d9170, display_name=<optimized out>) at ../../../backend/src/
#11 0x000055555568fce9 in Core::init (this=0x5555558d9170, argc=<optimized out>, argv=<optimized out>, app=<optimized out>,
    display_name=0x7fffffffead0 "wayland-0") at ../../../backend/src/
#12 0x0000555555645984 in GUI::init_core (this=0x5555557560c0) at ./frontend/gtkmm/src/
#13 0x000055555562f09f in GUI::main (this=0x5555557560c0) at ./frontend/gtkmm/src/
#14 0x000055555566de0f in run (argc=1, argv=0x7fffffffdcd8) at ./frontend/gtkmm/src/
#15 0x00007ffff6023510 in __libc_start_call_main (main=main@entry=0x55555562f1e0 <main(int, char**)>, argc=argc@entry=1,
    argv=argv@entry=0x7fffffffdcd8) at ../sysdeps/nptl/libc_start_call_main.h:58
#16 0x00007ffff60235c9 in __libc_start_main_impl (main=0x55555562f1e0 <main(int, char**)>, argc=1, argv=0x7fffffffdcd8, init=<optimized out>,
    fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdcc8) at ../csu/libc-start.c:381
#17 0x00005555556327b5 in _start ()

The desktop is KDE/wayland. So far this is the only app I noticed that crashes. Firefox works fine, the rest are all KDE/Qt apps.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: workrave 1.10.50-2
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Nov 22 10:28:58 2022
 # This is a distribution channel descriptor
 # For more information see
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-04-27 (1669 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
SourcePackage: workrave
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Marcos Dione (mdione) wrote :
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for reporting.

Since you mention running wayland, could you check if the crash also happens with Xorg session? I found a bug report in Debian which mentions that workrave lacks wayland support ( so this might be the root cause.

Revision history for this message
Marcos Dione (mdione) wrote :

I just went back to Plasma/X11 and workrave is working, so I'm going to stay here :) still, I think a SIGSEGV is not the best way to fail.

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

>I think a SIGSEGV is not the best way to fail.

Zero arguments here :) I'm just checking if it was the same issue or different seg fault. I'll add a bug watch so that this will be automatically updated if something happens in the Debian report.

summary: - workrave segfault launch
+ workrave segfault launch on Wayland
Changed in workrave (Debian):
status: Unknown → Confirmed
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.