Package Details: clockify-desktop 2.0.3-2

Git Clone URL: (read-only, click to copy)
Package Base: clockify-desktop
Description: Truly free time tracker for teams, Desktop App
Upstream URL:
Licenses: custom
Submitter: elmo-space
Maintainer: jankoh
Last Packager: jankoh
Votes: 13
Popularity: 0.78
First Submitted: 2019-01-14 10:32 (UTC)
Last Updated: 2022-02-13 13:05 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

kohane27 commented on 2022-08-25 04:52 (UTC)

Could anyone help?

When I launch clockify I have a the window open. But there's no input field for account name and password; only the blue "LOG IN" button. As suggested, I change my default web browser to Firefox but the same issue persists:

❯ xdg-settings get default-web-browser

❯ echo $BROWSER

Any input is much appreciated. Thank you!

jankoh commented on 2022-05-21 07:19 (UTC) (edited on 2022-05-21 07:23 (UTC) by jankoh)

@gustaphe, please see @locallylandys comment and change default browser to FF. I'm not really sure why Chrome(ium) does not work. IIRC, it doesn't work in Pop-OS/Ubuntu, either; I suppose upstream broke something but does not update the package.

Edit: See

gustaphe commented on 2022-05-16 08:52 (UTC)

I have the login issues in 2.0.3-2. My browser (Brave (Chromium based)) simply opens a new, empty, window instead of returning to the desktop app. I was at one point asked "open with xdg-open?" and I accidentally hit "every time", so I can't see which mime type/link format it's trying to open. But running XDG_UTILS_DEBUG_LEVEL=10 brave and then pressing the login button says

Selected DE generic
Checking /home/*/.config/mimeapps.list
Checking /home/*/.local/share/applications/defaults.list and /home/*/.local/share/applications/mimeinfo.cache
Checking /home/*/.local/share/applications/defaults.list and /home/*/.local/share/applications/mimeinfo.cache
Checking /usr/local/share//applications/defaults.list and /usr/local/share//applications/mimeinfo.cache
Checking /usr/local/share//applications/defaults.list and /usr/local/share//applications/mimeinfo.cache
Checking /usr/share//applications/defaults.list and /usr/share//applications/mimeinfo.cache
/usr/bin/xdg-open: line 811: : command not found

so if I could figure out what mimetype it is I could probably sort it (application/clockify was not it sadly).

lucassylandy commented on 2021-09-17 17:59 (UTC)

For those who are having login problems, I solved it by changing the default browser of my system from Chrome to Firefox, and I could login successfully. For some reason, Chrome is not working.

jankoh commented on 2021-07-30 16:46 (UTC)

Hey Nek.12,

the package unfortunately is not out-of-date, but broken upstream. They (accidentally?) release an updated broken 2.0.2 version. Since there's only an S3 bucket containing the current release, I don't have any possibillity to switch back or hold any working version. I have been in contact with upstream (see my last comments), the only information I got was, they cannot/won't switch back, and did not get error reports except mine. But accoring to them, they are working on an updated version, and they wanted to get back to me when it's released. Unfortunately nothing new was released since then.

Since I cannot hold any version (the package simply won't build, if they release anything new), and the original error was /tmp noexec related , I updated the package, so at least the package can be built. I know, there is this login problem (I had it also on an ubuntu I used for testing purposes, so it's not related to the packaging done here), but again, I cannot d anything about it. Feel free to report the error upstream, if there's more users than me reporting problems, maybe they'll speed up a correction release...

Release 2.0.3 is not yet available as a deb package.

Best, Jan

Nek.12 commented on 2021-07-29 07:38 (UTC) (edited on 2021-07-30 13:17 (UTC) by Nek.12)

I'm not able to log in to clockify, though I'm not sure the issue is related to the package. After pressing "Log In" I'm redirected to the browser with link, and after that, to http://clockify//accessToken=blah... and my browser just errors out with ERR_NAME_NOT_RESOLVED obviously, because this is a strange link. I tried to fix the link to be compatible with xdg-open, but to no avail. Tried changing the link to look like clockify:accessToken=... and it uses xdg-open but unfortunately this does not log me in, just shows the login screen again (nothing happens)

UPD: I contacted developers and they've fixed the issue in version 2.0.3

jankoh commented on 2021-06-18 20:19 (UTC)


I figured the new 2.0.2 upstream only throws said startup error when using noexec /tmp. As current FSH standards don't recommend a noexec /tmp, I uploaded the updated version So please make sure you don't have the noexec mount option set on /tmp.

jankoh commented on 2021-06-11 23:30 (UTC)

Hey @Nek.12

as written in the previous comment: The package is broken by upstream at the moment. They (accidentally?) released another version of 2.0.2 that is broken. I can update the package using the new checksums but that will break existing installations as the broken version will not start but throw the mentioned json error at startup. I'm in contact with upstream and have been told a new version will be released soon that will hopefully fix the issue. I can only recommend to stay patient while they fix the issue.

Nek.12 commented on 2021-06-10 18:53 (UTC)

==> ERROR: One or more files did not pass the validity check!
error downloading sources: clockify-desktop

Deleting the cache did not help

jankoh commented on 2021-06-05 12:50 (UTC)

Hey there,

the package fails to build at the moment since upstream changed something in the package. I can provide an updated package, but a newly built one fails to run giving the error message:

A JavaScript error occurred in the main process Uncaught Exception: Error: /tmp/.org.chromium.Chromium.su4vxk: failed to map segment from shared object at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:160:31) at Object.Module._extensions..node (internal/modules/cjs/loader.js:722:18) at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:169:18) at Module.load (internal/modules/cjs/loader.js:602:32) at tryModuleLoad (internal/modules/cjs/loader.js:541:12) at Function.Module._load (internal/modules/cjs/loader.js:533:3) at Module.require (internal/modules/cjs/loader.js:640:17) at require (internal/modules/cjs/helpers.js:20:18) at Object.<anonymous> (/opt/Clockify/resources/app.asar/node_modules/active-windows/index.js:1:178) at Object.<anonymous> (/opt/Clockify/resources/app.asar/node_modules/active-windows/index.js:5:3)

I contacted upstream about the issue and waiting for response. As on now (2021-06-05) do not rebuild the package; it will fail.