Failed to connect, openSuse Tumbleweed

Asked by Grzegorz

Hello there!
trying to run Timekpr-nExT Administration for the very first time after the install I have got:
Failed to connect, Please reopen the application if you are superuser and Timekpr-nExT is running.

I'm using openSuse Tumbleweed 20230816 with GNOME

Question information

Language:
English Edit question
Status:
Answered
For:
Timekpr-nExT Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Eduards Bezverhijs (mjasnik) said :
#1

Please specify version of timekpr you have installed.
Without details it is impossible to help.

Revision history for this message
Grzegorz (heretyk) said :
#2

Hi,

it is 0.5.3, but the same happened on 0.5.1 downloaded from https://software.opensuse.org/package/timekpr-next

Revision history for this message
Eduards Bezverhijs (mjasnik) said :
#3

Please use the version with “(SU)” atvthe start, it should work.
If it does not, maybe timekpr daenonbis not staryed by default in suse.

Revision history for this message
Grzegorz (heretyk) said :
#4

I'm logged as root using "(SU)" version. I can see timekpr.service up and running.

Revision history for this message
Eduards Bezverhijs (mjasnik) said :
#5

So, all good?

Revision history for this message
Grzegorz (heretyk) said :
#6

no, no good, still the same

timekpr.service is up and running in systemctl services, but still when running "(SU)" version I have got "Failed to connect"

Revision history for this message
Eduards Bezverhijs (mjasnik) said (last edit ):
#7

Please gather log files and send them to me. Log file locations are in readme.
Also, try running “sudo timekpra” in terminal, let’s see what comes up.

Revision history for this message
Grzegorz (heretyk) said :
#8

I have logs collected and sent them over to your email

Revision history for this message
Eduards Bezverhijs (mjasnik) said (last edit ):
#9

So, for everyone - the issue and the solution

openSuse, as it turns out, moved files which were needed to get system login/user information to different directory, than the rest.
That's why timekpr does not start, because it looked for file in a well known location and did not find it.

I'll add a search for multiple directories where the file may be and release a fix with next beta and stable version of version 0.5.5.

Revision history for this message
Eduards Bezverhijs (mjasnik) said :
#10

Please check 0.5.5 version in my google drive.

https://mjasnik.gitlab.io/timekpr-next/#installation

Can you help with this problem?

Provide an answer of your own, or ask Grzegorz for more information if necessary.

To post a message you must log in.