rcaelers / workrave Goto Github PK

I wanted to use WorkRave on my work computer but I am not sure if it doesn't use any confidential data - please, let me know what kind of data it uses while working on the computer. I will be grateful for your help!

Describe the bug

Branch next points to outdated commit. It is several commits behind the release branch_v1_10 and those commits actually fix important bugs.

We Arch Linux people have this package in AUR that makes a build from the next branch. Either we should remove it or maybe the maintainers could just set next to point to the most recent actual commit, like maybe branch_v1_10.

If next is not used anymore, maybe it could be removed? Then we will think again what to do with the package — maybe clone from some another branch.

Expected behavior
next points to the most recent version of the code.

Issue #103 was how I learned that reading mode existed. It's great that we have that functionality (though I don't know if "Reading Mode" is descriptive enough for users to understand exactly what it entails).

However, the current implementation of the inactivity timer seems a bit one-size-fits-all. It's not hard to imagine going through the work day looking at code and documentation and not knowing when you might end up reading something for a half hour or more - and if you end up reading something longer than you thought you would and you don't bring up workrave and activate reading mode then you won't get prompted to take breaks.

A nice middle-ground would be a configurable inactivity timer. Then a user could set it to some value which exceeds the maximum number of seconds they would ever spend reading a single screen of text. Then they wouldn't need to activate reading mode to continue getting prompts for breaks, but they would still be able to walk away from the computer and have the break timers pause after a couple of minutes. Thanks for your consideration.

Hi, I installed the program through the ppa:rob-caelers/workrave PPA repository, the installation was successful, then, when the program was opened, only 2 icons appeared in the system tray, and the program window itself did not open, i.e. program settings are not available, when you right-click, settings or any actions with the program are also not available, but the program itself works, as far as I can tell, i.e. notifications about breaks come, apparently some standard break patterns

Screenshot

Distribution: Kubuntu
Distribution Version: 16.04.6
Desktop Environment: KDE Plasma 5.8.9
Workrave Version: 1.10.23

It would be practical to allow for some basic key binding for basic actions. For example postpone, or show window. User should not have to use mouse to use workrave.

Hi. Workrave v1_10_20 segfaults on Ubuntu 17.10 (Gnome Shell). It works fine when using my Nvidia card, but crashes while on Intel integrated graphics (prime-select). Tried both modes (after reboots) and problem can be replicated.

dmesg output:
[Tue Nov 7 01:04:11 2017] workrave[5440]: segfault at 0 ip 00007f2471d013ce sp 00007fff4a133560 error 4 in libX11.so.6.3.0[7f2471cc4000+134000]

I can email you the crash log if you like.

Thanks.

I had Workrave installed from the Ubuntu 18.04 repositories. After adding the PPA to install the latest Workrave, I get this error when trying to install workrave-gnome:

Unpacking workrave-gnome (1.10.21-ppa5~bionic1) ...
dpkg: error processing archive /var/cache/apt/archives/workrave-gnome_1.10.21-ppa5~bionic1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/workrave/libworkrave-applet.so', which is also in package workrave 1.10.16-2ubuntu1
Errors were encountered while processing:
 /var/cache/apt/archives/workrave_1.10.21-ppa5~bionic1_amd64.deb
 /var/cache/apt/archives/workrave-gnome_1.10.21-ppa5~bionic1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I guess workrave-gnome should have a breaks/replaces field in the control file for the workrave package older than 1.10.21 (or when this change to the packaging was introduced).

Also, I noticed an error when trying to install the workrave MATE package too, but with the workrave-data package (so workrave-data also needs a breaks/replaces for older versions):

Unpacking workrave (1.10.21-ppa5~bionic1) over (1.10.16-2ubuntu1) ...
dpkg: error processing archive /var/cache/apt/archives/workrave_1.10.21-ppa5~bionic1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/appdata/workrave.appdata.xml', which is also in package workrave-data 1.10.16-2ubuntu1
Preparing to unpack .../workrave-data_1.10.21-ppa5~bionic1_all.deb ...
Unpacking workrave-data (1.10.21-ppa5~bionic1) over (1.10.16-2ubuntu1) ...
Selecting previously unselected package workrave-mate.
Preparing to unpack .../workrave-mate_1.10.21-ppa5~bionic1_amd64.deb ...
Unpacking workrave-mate (1.10.21-ppa5~bionic1) ...
dpkg: error processing archive /var/cache/apt/archives/workrave-mate_1.10.21-ppa5~bionic1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/mate-applets/workrave-applet', which is also in package workrave 1.10.16-2ubuntu1
Errors were encountered while processing:
 /var/cache/apt/archives/workrave_1.10.21-ppa5~bionic1_amd64.deb
 /var/cache/apt/archives/workrave-mate_1.10.21-ppa5~bionic1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

autoreconf -fi
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:957: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its use is discouraged.
configure.ac:957: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead,
configure.ac:957: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files.
configure.ac:139: installing './compile'
configure.ac:30: installing './missing'
backend/src/Makefile.am: installing './depcomp'

configure error, showing the last few lines:

config.status: executing libtool commands
config.status: executing po-directories commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
config.status: executing po/stamp-it commands
config.status: error: po/Makefile.in.in was not created by intltoolize.

Describe the bug
On a rest break, when selecting a value from the "Lock..."-Dropdown Box, the options "Lock" and "Shutdown" are dangerously close together. It happened to me several times, that I accidentally shutdown my computer although I just wanted to lock the screen.

To Reproduce
Steps to reproduce the behavior:

1. Go to the "Rest Break"-Window
2. Select the "Lock..."-Dropdown-Box
3. While trying to select "Lock", slip a little and click on "Shutdown"

Expected behavior
Option 1): Separate the Lock and Shutdown option into two different Dropdown-Boxes
Option 2): Add an "Are you sure?"-Dialog when clicking on the "Shutdown"-Option

Screenshots

Is it possible to start distribution/packaging as AppImage, if yes, so when?

When Workrave begins a break, it abruptly blocks the screen. A fade out effect (3 seconds) would make starting a break more pleasant. It would be a good feature to make Workrave even better.

I'd like to experiment with having workrave modify its breaks based on keyboard and mouse activity. I find that a combination of time and number of mouse clicks and especially number of keys typed changes the load on my arms quite a bit--I need more breaks when I'm typing quickly than when I'm browsing the web.

What class/module decides whether it's time for a break? I think if I have that as a starting point I can figure it out from there.

I work on Ubuntu 16.04, uname -a give me this:

Linux ThinkPad-P50 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

When I turn on Always On Top, it will stop timing.

Especially if I had switched to other application window.

Describe the bug
The tagged releases available by following Github's "Creating releases" are dynamically generated and can (and have) change. This breaks checksums.

To Reproduce
The Github tarballs currently available were produced by the Github "creating releases" process. It generates a tarball on the fly when a user downloads. More background can be found at: https://marc.info/?l=openbsd-misc&m=153492430016386&w=2

When Github changes how they are generated, the OpenBSD port (which I'm attempting to update from 1.10.1) will break, as it verifies the checksum of the source tarball.

Expected behavior
Checksums will match because we are downloading a static tarball.

The postpone (alt+p) and skip (alt+s) buttons in the "rest break" dialog have hotkeys.
Could you add a hotkey for locking the screen? Maybe ctrl+l?

PS: Workrave is a great tool!

Currently timers show minutes and seconds. Passing seconds could be distraction.
It could be possible to select showing only minutes.

Describe the bug
Workrave is an invaluable tool and helps keep me healthy. I'd like to help sponsor development somehow.

To Reproduce
Steps to reproduce the behavior:

1. Enjoy Workrave
2. Search for ways to help sponsor development
3. Find no ways

Expected behavior
Find a Patreon, GitHub Sponsors, etc.

Screenshots
<you probably don't want a picture of my arm tendons>

Additional context
Thank you!

Hi and thanks for the great work!

When I want to download workrave tarball, I see "Download Forbidden" message (because of US sanctions against Iran).
Can you please use another service for downloading the software in workrave.com?
Or change your sourceforge account settings to allow everyone to download it (If i'm not wrong about that settings).

Thanks again :)

Description:

The program crashes on startup. It does create the directory ~/.workrave, but nothing else happens as far as I can see.

The problem is solved by adding an explicit display option, like this:

% workrave --display="$DISPLAY"

I think this may be a reiteration of a long standing issue: #88 — that has been closed without resolution. Notice though that I use a completely different video card and driver.

From the description, and taking a brief look at gdb output, my guess would be that the problem is in the code that calls for X11 to initialize the window.

Expected behaviour:

The program starts normally without extraneous arguments and respects $DISPLAY environment variable.

Try it yourself:

% gdb workrave <<< run
...
(gdb) Starting program: /usr/bin/workrave 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7ffff39ac700 (LWP 31895)]
[New Thread 0x7ffff31ab700 (LWP 31896)]
[New Thread 0x7ffff29aa700 (LWP 31897)]
[New Thread 0x7ffff21a7700 (LWP 31898)]

Thread 1 "workrave" received signal SIGSEGV, Segmentation fault.
0x00007ffff6a83199 in XQueryExtension () from /usr/lib/libX11.so.6

Versions:

• Distribution: Arch Linux

• Distribution Version: Up to date.

• Desktop Environment: Wayland/sway and X11/i3.

• Workrave Version: next current, via AUR package.

• Video controller:

   04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev d0)
       DeviceName: Onboard IGD
       Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
       Kernel driver in use: amdgpu
  

Describe the bug
On gnome 3.32 I can't enable workrave extension.
Gnome tweaks says "Error loading extension".

** Linux (please complete the following information in case you encountered the bug on Linux):**

• Distribution: Arch Linux
• Distribution Version: rolling release
• Desktop Environment: Gnome 3.32
• Workrave Version 1.10.23-2

Hello !
First of all - thanks for a great app !

I am trying to compile for Mac Sierra 10.12.6.

at compilation produces error :
In file included from OSXGtkMenu.cc:31: ./OSXGtkMenu.hh:51:28: error: unknown type name 'GtkMacDock' static void dock_clicked(IgeMacDock *dock, void *data); ^ ./OSXGtkMenu.hh:35:20: note: expanded from macro 'IgeMacDock' #define IgeMacDock GtkMacDock

gtk-mac-integration installed using brew

Describe the bug
I think I have messed up my settings and timers; I would like to reset my settings.

To Reproduce
N/A

Expected behavior
A button on the settings dialog to reset (and restart) settings of workrave.

Screenshots
N/A

** Linux (please complete the following information in case you encountered the bug on Linux):**

• Distribution: Ubuntu
• Distribution Version: N/A
• Desktop Environment: KDE
• Workrave Version: 1.10.34

** Windows (please complete the following information in case you encountered the bug on Windows):
N/A

Additional context
None

Description:

next branch does not build in an obvious way.

See for yourself:

% cd src/workrave-next-gtk3-git/
% git describe --long
v1_10_29-655-g36786eb7
% cd build
% cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr -DWITH_UI=Gtk+3 -DWITH_DBUS=false ..
...
% make
[ 73%] Building CXX object ui/apps/gtkmm/src/CMakeFiles/workrave.dir/unix/UnixGrab.cc.o
.../src/workrave-next-gtk3-git/ui/apps/gtkmm/src/unix/UnixGrab.cc: In member function ‘virtual void UnixGrab::grab(GdkWindow*)’:
.../src/workrave-next-gtk3-git/ui/apps/gtkmm/src/unix/UnixGrab.cc:52:9: error: ‘GtkUtil’ has not been declared
   52 |   if (! GtkUtil::running_on_wayland())
      |         ^~~~~~~
.../src/workrave-next-gtk3-git/ui/apps/gtkmm/src/unix/UnixGrab.cc: In member function ‘virtual void UnixGrab::ungrab()’:
.../src/workrave-next-gtk3-git/ui/apps/gtkmm/src/unix/UnixGrab.cc:137:9: error: ‘GtkUtil’ has not been declared
  137 |   if (! GtkUtil::running_on_wayland())
      |         ^~~~~~~
make[2]: *** [ui/apps/gtkmm/src/CMakeFiles/workrave.dir/build.make:544: ui/apps/gtkmm/src/CMakeFiles/workrave.dir/unix/UnixGrab.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1501: ui/apps/gtkmm/src/CMakeFiles/workrave.dir/all] Error 2
make: *** [Makefile:152: all] Error 2

Expected behaviour:

Everything builds fine.

My solution:

Applying the following patch will lead to the build succeeding:

% cat GtkUtil.patch
diff --git a/ui/apps/gtkmm/src/unix/UnixGrab.cc b/ui/apps/gtkmm/src/unix/UnixGrab.cc
index 6e48f40e..7d055d1d 100644
--- a/ui/apps/gtkmm/src/unix/UnixGrab.cc
+++ b/ui/apps/gtkmm/src/unix/UnixGrab.cc
@@ -49,7 +49,7 @@ UnixGrab::can_grab()
 void
 UnixGrab::grab(GdkWindow *window)
 {
-  if (! GtkUtil::running_on_wayland())
+  if (! Platform::running_on_wayland())
     {
       grab_wanted = true;
       if (!grabbed)
@@ -134,7 +134,7 @@ UnixGrab::grab_internal()
 void
 UnixGrab::ungrab()
 {
-  if (! GtkUtil::running_on_wayland())
+  if (! Platform::running_on_wayland())
     {
       grabbed = false;
       grab_wanted = false;

Unfortunately, I still get a segmentation fault when running the program, but that may be for any
other reason.

My operating system:

Arch Linux, recently updated.

I recently installed workrave on Ubuntu 17.04 (via the rob-caelers/workrave PPA). However, the applet did not show in the task bar, and as a result I was unable to access the settings/preferences.

I was able to fix the solution by following https://askubuntu.com/questions/766601/workrave-applet-blank-in-ubuntu-16-04:

1. sudo apt install workrave-data workrave-unity
2. unity --replace

In order to make life easier for future Ubuntu users, could you please document these steps somewhere (e.g. README.md, http://workrave.org)?

Describe the bug
The network settings can be changed by users. However, in a professional environment, this might be a setting that should only be changed by IT administrators.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Preferences'
2. Click on 'Network'

Expected behavior
I would expect that network settings can only be set by the computer administrator. There are different ways to make that possible, like for instance:

1. Network settings can only be changed when being a computer administrator.
2. Network settings are to be set in an configuration file which can be made read-only or which are only accessible by computer administrators.

Windows
• Windows Version: Windows 10
• Workrave Version: latest

Additional context
The request is especially interesting for companies with strict security rules. If this feature request is being taken into account it could boost the use of Workrave and thus attract more open source developers who are willing to contribute.

During the build process, a Python 2 script is used to generate D-Bus binding:
https://github.com/rcaelers/workrave/blob/782d4581eb19d8d0d62e067084512d9a3da3776c/common/bin/dbusgen.py

Since Python 2 will be retired soon, please port this code to Python 3.

hi,

It would be great to have the possibility to launch an external script when a break is triggered.

thanks!

I'm getting multiple icons for workrave in my tray. I'm using LXDE on Gentoo.

There are two workrave icons in the tray left of the wifi symbol and two "empty" icons right of the wifi symbol.

Any idea what's going wrong there? Attaching an image to show how it looks:

(This should be labeled as a feature-request.)

Redshift have a very useful feature: The ability to suspend it for x minutes/hours:

Very useful to see movies/series. Would be great to have same feature on Workrave. Very often I suspend/quiet (BTW, one of them could be removed) and then forget to enable it again.

Describe the bug

Running autogen i got

configure.ac:897: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its use is discouraged.
configure.ac:897: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead,
configure.ac:897: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files.

To Reproduce
Run autogen on git cloned repo source code

Expected behavior
Not get a deprecated message as warning

Linux

• Distribution: Debian

Describe the bug
I get a compiler error when building the last version from the sources. I have tried with the last 1.10 branch and also checking out v1_10_20 tag with the same result.

The first error to shown is:

v4/WorkraveApplet.c:441:3: error: too few arguments to function ‘panel_applet_setup_menu_from_file’
   panel_applet_setup_menu_from_file(PANEL_APPLET(applet), ui_path, applet->priv->action_group);

Others follow that one, but seems related to it.

See at the attached make.out file for the complete output.

To Reproduce

1. I attach my configure.ac file that should be put in place of the original configure.ac. The differences are basically that I enable gnome3 configuration and lib_panelapplet4.

2. run ./autogen.sh

3. run ./configure.sh

4. run make

Expected behavior
Successful compilation

** Linux (please complete the following information in case you encountered the bug on Linux):**

• Distribution: Ubuntu
• Distribution Version: 18.04
• Desktop Environment: Gnome
• Workrave Version 1.10/1.10.20

report.tar.gz

I often find myself moving my hand to my mouse, moving my mouse up to the tray icon and right-clicking to check whether or not workrave is currently in Reading Mode.

This extra activity could easily be avoided by modifying the tray icon to indicate when workrave is/isn't in Reading Mode.

(Thank you for workrave, I use it every day and love it!)

The newest version on SF is 1.10.1, while GitHub has releases up to 1.10.20.

Being able to retrieve hourly or per-minute activity stats would be really handy for those of us that like to graph out our personal statistics. Day to day is nice, but having a more granular look would be great for breaking down our days.

Similarly, being able to see aggregate stats (ie. an entire month) instead of a single day would be nice.

Describe the bug
Chrome 68.0.3440.106 on Windows warns that Workrave is an incompatible appllication.
This has been announced here and is apparently related to code injection:
https://www.bleepingcomputer.com/news/google/google-chrome-showing-alerts-about-incompatible-applications/

To Reproduce
Steps to reproduce the behavior:

1. Start Chrome
2. Notice that it opens at chrome://settings/incompatibleApplications
3. See error

Expected behavior
Workrave not to cause warnings in Chrome

Screenshots

** Windows (please complete the following information in case you encountered the bug on Windows):

• Windows Version: 10 (build 1803)
• Workrave Version: 1.10

Hi, very nice app.

While I´m reading documents the timer for next break restarts as sometimes I do not use keyboard neither mouse for a while. But it would be better for my eyes if I was rembered to take a pause.
Whould be nice to be able to configure this in the settings.

After system update, workrave crashes unity desktop, then the workrave process still live on. Not this may be hard to reproduce. But it occur on my machine 100%.

Describe the bug

GNOME Shell gets stuck as if the Windows key was pressed, and only remedy is to close user session and start it again.

To Reproduce
Steps to reproduce the behavior:

I haven't been able to figure out what triggers it. Sometimes it triggers when the session is in use, but most of the time I find that after unlocking the laptop after idling, the sessions is corrupt in this way. journal says:

d’ag. 08 15:59:41 penyagolosa workrave[28079]: g_bus_watch_name_on_connection: assertion 'g_dbus_is_name (name)' failed d’ag. 08 15:59:41 penyagolosa gnome-shell[27894]: Object St.BoxLayout (0x55872e0d7450), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroye d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: == Stack trace for context 0x55872bdac340 == d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #0 0x55872e61a238 i resource:///org/gnome/shell/ui/popupMenu.js:717 (0x7fd512623ef0 @ 22) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #1 0x7fff4c324650 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #2 0x7fff4c324700 b resource:///org/gnome/shell/ui/popupMenu.js:735 (0x7fd512626230 @ 23) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #3 0x7fff4c3247c0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #4 0x55872e61a140 i /usr/share/gnome-shell/extensions/[email protected]/extension.js:271 (0x7fd5109bf5e8 @ 32) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #5 0x55872e61a0b0 i /usr/share/gnome-shell/extensions/[email protected]/extension.js:148 (0x7fd51098dd58 @ 177) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #6 0x55872e61a020 i /usr/share/gnome-shell/extensions/[email protected]/extension.js:110 (0x7fd51098dbc0 @ 43) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #7 0x7fff4c3254c0 b self-hosted:916 (0x7fd5242f1230 @ 367) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #8 0x55872c1682c8 i resource:///org/gnome/shell/ui/panelMenu.js:192 (0x7fd512676ef0 @ 74) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #9 0x7fff4c327990 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #10 0x55872c168250 i /usr/share/gnome-shell/extensions/[email protected]/extension.js:351 (0x7fd5109bf6f8 @ 12) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #11 0x55872c168190 i resource:///org/gnome/shell/ui/extensionSystem.js:82 (0x7fd512654d58 @ 431) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #12 0x55872c168110 i resource:///org/gnome/shell/ui/extensionSystem.js:344 (0x7fd51265c890 @ 13) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #13 0x7fff4c3286c0 b self-hosted:251 (0x7fd5242c4ab0 @ 223) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #14 0x55872c168090 i resource:///org/gnome/shell/ui/extensionSystem.js:343 (0x7fd51265c808 @ 64) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #15 0x55872c168010 i resource:///org/gnome/shell/ui/extensionSystem.js:361 (0x7fd51265c918 @ 87) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #16 0x7fff4c329b90 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5242d2230 @ 386) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #17 0x7fff4c32a380 b resource:///org/gnome/shell/ui/sessionMode.js:204 (0x7fd51236a670 @ 254) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #18 0x55872c167eb0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #19 0x55872c167e28 i resource:///org/gnome/shell/ui/sessionMode.js:166 (0x7fd51236a450 @ 40) d’ag. 08 15:59:41 penyagolosa gnome-shell[27894]: Object St.BoxLayout (0x55872e0d7450), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroye d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #20 0x55872c167d80 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #21 0x55872c167cd8 i resource:///org/gnome/shell/ui/screenShield.js:1279 (0x7fd51234fbc0 @ 188) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #22 0x55872c167c30 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #23 0x55872c167ba8 i resource:///org/gnome/shell/ui/screenShield.js:899 (0x7fd51234ecd0 @ 18) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #24 0x55872c167b00 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #25 0x55872c167a40 i self-hosted:916 (0x7fd5242f1230 @ 367) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #26 0x55872c167970 i resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5242d2230 @ 386) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #27 0x55872c1678f0 i resource:///org/gnome/shell/ui/lightbox.js:186 (0x7fd51263e560 @ 29) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #28 0x55872c167850 i resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fd5242d2b38 @ 54) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #29 0x55872c167730 i resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fd5242d2bc0 @ 1626) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #30 0x55872c1676a0 i resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fd5242d2c48 @ 100) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #31 0x55872c167628 i resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fd5242d2cd0 @ 10) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #32 0x55872c167558 i resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5242d2230 @ 386) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #33 0x55872c1674c8 i resource:///org/gnome/shell/ui/tweener.js:244 (0x7fd5242cf808 @ 159) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #34 0x55872c167420 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #35 0x55872c1673a0 i resource:///org/gnome/shell/ui/tweener.js:219 (0x7fd5242cf780 @ 15)

I haven't been able to pinpoint what update caused this either.

Expected behavior

GNOME Shell and workrave are good buddies and don't fight.

** Linux (please complete the following information in case you encountered the bug on Linux):**

• Distribution: Debian
• Distribution Version: current unstable
• Desktop Environment: GNOME 3.28
• Workrave Version: 1.10 as distributed by Debian

Dear @rcaelers,

Would it be possible to add a command-line option for workrave to return the remaining daily limit using the Linux command-line? 🙂👍

Thanks!

Workrave should have password protection to prevent users (adults, kids) from tampering with settings. A password would help reduce repetitive injuries and computer addiction by not letting a user quit the program. Also, an option to disable Task Manager or not show Workrave in Task Manager.

Will Wayland be supported (Ubuntu 17.10)?

Currently daily limit is timer. It would be good if it can prompt the user to shutdown at custom time set by user.

Description

Trying to specify the location of the workrave indicator window using the standard option -geometry (from the command line, but potentially to specify it in the file starting it in /config/autostart), the program prints the error message: Failed to initialize: Unknown option -geometry

To Reproduce

xterm -geometry 50x50-50+50
does open a terminal at the location and with the size specified
workrave -geometry 50x50-50+50
Failed to initialize: Unknown option -geometry

Expected behavior

The workrave window should open at the location and with the size specified.

** Linux (please complete the following information in case you encountered the bug on Linux):**

• Distribution: Debian
• Distribution Version: Debian 4.9.1 68-1 (2019-04-12)
• Desktop Environment: xfce
• Workrave Version: 1.10.16/0

Describe the bug
If Chrome (Chromium) is in fullscreen mode, and the Rest Break is started, the dialog is not shown.
This results that I cannot Skip or Postpone.

To Reproduce
Steps to reproduce the behavior:

1. Open Chromium, F11 to fullscreen mode
2. Wait for Workrave Rest Break
3. Rest Break started, but cannot see the dialog, and nothing can be clicked and keyboard has no response. Can only wait until the break ended.

Expected behavior
Rest Break should always on top, so that can be Skipped or Postponed.

Linux

• Distribution: Arch Linux
• Distribution Version: Kernel 4.19.49-1-lts
• Desktop Environment: Openbox 3.6.1, tint2 16.6.1
• Workrave Version 1.10.31

The latest release of Workrave was tagged on the 'debian-packaging' branch instead of on the 'branch_v1_10' branch.

To Reproduce

1. Configure with

--disable-gsettings --disable-gconf --enable-gnome3 \
--disable-indicator --enable-dbus --enable-gstreamer \
--disable-xfce --disable-mate --enable-pulse \
--disable-debug --disable-distribution --enable-experimental \
--enable-exercises --disable-tests --disable-tracing --enable-xml

2. Run make

Expected behavior
Should be built just fine.

Actual behavior
Fails with

libtool: link: gcc -shared  -fPIC -DPIC  v5/.libs/libworkrave_applet_la-WorkraveApplet.o .libs/libworkrave_applet_la-workrave-gnome-applet-generated.o   -lpanel-applet -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -L./../../common/src -lworkrave-private-1.0  -pthread -g -O2   -pthread -Wl,-soname -Wl,libworkrave-applet.so -o .libs/libworkrave-applet.so
/usr/bin/x86_64-linux-gnu-ld: cannot find -lworkrave-private-1.0
collect2: error: ld returned 1 exit status
Makefile:637: recipe for target 'libworkrave-applet.la' failed

Enabling indicator makes it buildable again.

Linux:

• Distribution: Ubuntu
• Distribution Version: 18.04.1
• Desktop Environment: Gnome 3
• Workrave Version: commit f1f589d

When the Reading mode is on, workrave keeps asking for breaks indefinitely even if there is nothing to read on the screen and the user stopped all mouse/keyboard activity some time ago.

Workrave can check if the screen is readable before initiating a break. If the screen is not readable, check again after some time (a percentage of the shortest interval between enabled breaks perhaps).

For example, on GNU/Linux xset q can be used to query the current display state. Unfortunately, it is probably unfeasible for workrave to support all the different screen lockers. But I think some checks (the display state at least) is better than no detection at all.

#120 proposes an alternative manual way to address this issue - by configuring the inactivity timer.

Trying to build the archive workrave-1_10_20, after autogen.sh the command ./configure fails with the error below.

$ ./autogen.sh 
Copying file config.rpath
Copying file m4/codeset.m4
Copying file m4/gettext.m4
Copying file m4/glibc2.m4
Copying file m4/glibc21.m4
Copying file m4/iconv.m4
Copying file m4/intdiv0.m4
Copying file m4/intl.m4
Copying file m4/intldir.m4
Copying file m4/intlmacosx.m4
Copying file m4/intmax.m4
Copying file m4/inttypes-pri.m4
Copying file m4/inttypes_h.m4
Copying file m4/lcmessage.m4
Copying file m4/lib-ld.m4
Copying file m4/lib-link.m4
Copying file m4/lib-prefix.m4
Copying file m4/lock.m4
Copying file m4/longlong.m4
Copying file m4/nls.m4
Copying file m4/po.m4
Copying file m4/printf-posix.m4
Copying file m4/progtest.m4
Copying file m4/size_max.m4
Copying file m4/stdint_h.m4
Copying file m4/uintmax_t.m4
Copying file m4/visibility.m4
Copying file m4/wchar_t.m4
Copying file m4/wint_t.m4
Copying file m4/xsize.m4
Copying file po/Makefile.in.in
Copying file po/Makevars.template
/usr/share/aclocal/gtk.m4:7: warning: underquoted definition of AM_PATH_GTK
/usr/share/aclocal/gtk.m4:7:   run info Automake 'Extending aclocal'
/usr/share/aclocal/gtk.m4:7:   or see http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
/usr/share/aclocal/gtk.m4:7: warning: underquoted definition of AM_PATH_GTK
/usr/share/aclocal/gtk.m4:7:   run info Automake 'Extending aclocal'
/usr/share/aclocal/gtk.m4:7:   or see http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
configure.ac:953: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its use is discouraged.
configure.ac:953: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead,
configure.ac:953: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files.
configure.ac:143: installing './ar-lib'
configure.ac:139: installing './compile'
configure.ac:23: installing './config.guess'
configure.ac:23: installing './config.sub'
configure.ac:30: installing './install-sh'
configure.ac:30: installing './missing'
backend/src/Makefile.am: installing './depcomp'
$ ./configure
[…]
checking for X11SM... yes
checking for GTKMM... ./configure: line 20329: syntax error near unexpected token `noext'
./configure: line 20329: `	 AX_CXX_COMPILE_STDCXX_11(noext)'

Describe the bug
Some translations broken when workrave gnome-shell extension enabled.

To Reproduce
Steps to reproduce the behavior:

1. Use a non-English language that has full gnome-shell translations
2. Enable workrave extentions
3. See untranslated dialogs when elevating user privileges or unlocking the lock screen

Expected behavior
gnome-shell translations continue to work

Screenshots
with and without workrave enabled

** Linux:**

• Distribution: Ubuntu
• Distribution Version: 18.04 LTS
• Desktop Environment: Gnome
• Workrave Version: 1.10(.16-2ubuntu1)

Hi,
i want to help and put more exercices. how can i add and update the exercises? With more exercises images and descriptions?
It's is possible and animated gif instead static .png images?
This is one of the examples that i want to put.

https://www.instagram.com/p/Bo1YIQalBGA/

https://www.instagram.com/p/Bm0xdMElwwE/

Regards,
João