When using Plasma desktop (KDE) under Wayland, workrave crashes on startup before having the chance to bring up its window. It still works fine if X11 is used instead of Wayland.
Created attachment 1783424 [details] gdb stack trace I ran workrave under gdb after installing all of the debug packages, and it showed that the crash happened in xcb_take_socket() in libxcb. Doing a websearch showed https://github.com/prusa3d/PrusaSlicer/issues/2515, which claims the issue can be solved by setting the env var GDK_BACKEND to "x11", though I haven't tried this yet.
I've confirmed that setting GDK_BACKEND to "x11" prevents the crash.
The DE doesn’t seem to matter; it happens to me using Sway. Setting GDK_BACKEND to x11 makes it start, but this way it cannot track idle state which is essential for this app.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.
Can you still reproduce this with 1.10.50 in Fedora 36/37 testing?
Tried updating it with dnf upgrade --enablerepo=updates-testing --refresh workrave but i still have 1.10.49. Any advice on how to upgrade it?
Created attachment 1923484 [details] gdb stacktrace for 1.10.50 Same error happens, attaching backtrace from F37.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Still happens on F38 :( Should i attach a fresh backtrace?
Created attachment 1965168 [details] Backtrace for version 1.10.50-2.fc38.x86_64
FEDORA-2023-75fcfc9d42 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-75fcfc9d42
FEDORA-2023-75fcfc9d42 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-75fcfc9d42` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-75fcfc9d42 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I added the upstream issue link. They have two workarounds: use GDK_BACKEND=x11 which prevents the crash but actually useless (see comment 3 above), and to turn on “Force the use of X11 on Wayland” which doesn’t seem to change anything at all.
FEDORA-2023-75fcfc9d42 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
This issue is not solved. I told in a comment (even though there are workarounds that work with huge limitations), and i even gave negative feedback on Bodhi.
I can confirm that Workrave instantly crashes on Fedora 39 KDE Wayland. “Force the use of X11 on Wayland” does not help.
By the way, you can still use the program in "reading mode" (in this mode it counts the time regardless of activity), so it's not entirely useless.
Another workaround is go to Settings → Applications → Legacy X11 app support and enable any option, for example "Only meta, control, alt, and shift keys".
The developer has fixed the crash in git main branch: https://github.com/rcaelers/workrave/commit/f67805a094748af8f987ca7171ac1845482c8e0c And added ext-idle-notify-v1 Wayland protocol support: https://github.com/rcaelers/workrave/commit/ce6f6764ed5526f8159b2b48853befdc007af0fd Meta-issue: https://github.com/rcaelers/workrave/issues/523