Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#56232 - [workrave] workrave doesn't detect input in non-Gnome DEs

Attached to Project: Community Packages
Opened by Jack Kamm (snackattack) - Saturday, 04 November 2017, 09:16 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 07 November 2017, 22:13 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

After the recent workrave 1.10.18-2 update, workrave no longer detects input (keyboard or mouse) in non-Gnome DEs.

DEs I tested where workrave doesn't work: i3, plasma, xfce, lxqt

For these DE's, workrave starts up fine, it simply doesn't detect any input. Workrave appears to work fine in Gnome.

I tried adjusting sensitivity with "gsettings set org.workrave.monitor sensitivity" to no avail.

Here is the upstream bug report:
https://issues.workrave.org/show_bug.cgi?id=1286
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 07 November 2017, 22:13 GMT
Reason for closing:  Fixed
Comment by Doug Newgard (Scimmia) - Saturday, 04 November 2017, 16:19 GMT
Are you running Gnome on Wayland? If so, that would explain the difference.

The upstream ticket was probably a mistake. The difference in -2 was adding non-upstream patch.
Comment by Jack Kamm (snackattack) - Saturday, 04 November 2017, 16:43 GMT
No I tested it in Gnome on Xorg, and that worked fine.

The non-upstream patch has been accepted into the upstream git repo (though not yet in the released tarball). So I think it would still be relevant to them.
Comment by Pieter Frenssen (pfrenssen) - Monday, 06 November 2017, 11:19 GMT
I have the same issue, workrave doesn't notice any keyboard or mouse input so the timers are not advancing. I'm not using Wayland, I'm using Xorg and AwesomeWM.
Comment by Marcin Mielniczuk (marmistrz) - Monday, 06 November 2017, 11:27 GMT
I'm experiencing the same on Cinnamon/Xorg.
Comment by Robert Kusznier (no-cheating) - Monday, 06 November 2017, 13:43 GMT
I'm experiecing the same problem with i3 on Xorg.
Comment by Robert Kusznier (no-cheating) - Monday, 06 November 2017, 15:34 GMT
It's supposed to be fixed: https://github.com/rcaelers/workrave/commit/5f8279ab08d6c3b74a5e974a26d57c765629376c
Comment by Jack Kamm (snackattack) - Tuesday, 07 November 2017, 07:24 GMT
I tested the 1.10.20 release and it works for me.

For the package maintainer: when updating the PKGBUILD, don't forget to remove the patch in 1.10.18-2 as it has been incorporated upstream.
Comment by Sergej Pupykin (sergej) - Tuesday, 07 November 2017, 14:00 GMT
I've pushed it to repo, but removed gconf schema patch

Loading...