Timekpr failed to install on Ubuntu 20.04, stuck on post install script at 60%

Bug #1893280 reported by Mike
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Timekpr-nExT
Invalid
Undecided
Eduards Bezverhijs

Bug Description

Hello,

I just did a fresh install of 20.04 and the installation get stuck in the post install script at 60%. Right after enabling the systemd unit.

If I switch to a new terminal, the service is not started. When I try to start it manually it just get stuck.

I can open the gui application but it does not connect to the darmon.
However I can run the timekprd on a terminal to make the gui work.

Thanks.

Revision history for this message
Eduards Bezverhijs (mjasnik) wrote :

Hi,
this doesn't look right. What version of timekpr are You using?
There was an issue with packaging some time ago, I believe it's fixed.
Try reboot and re-install again.

Changed in timekpr-next:
assignee: nobody → Eduards Bezverhijs (mjasnik)
Revision history for this message
Mike (ark987) wrote :
Download full text (4.2 KiB)

A reboot did not work.
Here is the version that I'm using:

timekpr-next/focal,now 0.4.1-2ubuntu1~ppa1~ubuntu20.04.1 amd64 [installed]

Here is the details of the system:

Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal

Here is the sources in the system:

/etc/apt/sources.list:deb http://do.archive.ubuntu.com/ubuntu/ focal main restricted
/etc/apt/sources.list:deb http://do.archive.ubuntu.com/ubuntu/ focal-updates main restricted
/etc/apt/sources.list:deb http://do.archive.ubuntu.com/ubuntu/ focal universe
/etc/apt/sources.list:deb http://do.archive.ubuntu.com/ubuntu/ focal-updates universe
/etc/apt/sources.list:deb http://do.archive.ubuntu.com/ubuntu/ focal multiverse
/etc/apt/sources.list:deb http://do.archive.ubuntu.com/ubuntu/ focal-updates multiverse
/etc/apt/sources.list:deb http://do.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse
/etc/apt/sources.list:deb http://security.ubuntu.com/ubuntu focal-security main restricted
/etc/apt/sources.list:deb http://security.ubuntu.com/ubuntu focal-security universe
/etc/apt/sources.list:deb http://security.ubuntu.com/ubuntu focal-security multiverse
/etc/apt/sources.list.d/google-chrome.list:deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
/etc/apt/sources.list.d/mjasnik-ubuntu-ppa-focal.list:deb http://ppa.launchpad.net/mjasnik/ppa/ubuntu focal main

Here is the CLI output of installation:

michael@michael-OptiPlex-7010:~/Source/Timekpr-nExT$ sudo apt-get remove --purge timekpr-next

Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'timekpr-next' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

michael@michael-OptiPlex-7010:~/Source/Timekpr-nExT$ sudo apt update

Hit:1 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:2 http://ppa.launchpad.net/mjasnik/ppa/ubuntu focal InRelease
Hit:3 http://do.archive.ubuntu.com/ubuntu focal InRelease
Hit:4 http://do.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:5 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:6 http://do.archive.ubuntu.com/ubuntu focal-backports InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

michael@michael-OptiPlex-7010:~/Source/Timekpr-nExT$ sudo apt install timekpr-next

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  gir1.2-appindicator3-0.1 python3-psutil
Suggested packages:
  python-psutil-doc espeak python3-espeak
The following NEW packages will be installed:
  gir1.2-appindicator3-0.1 python3-psutil timekpr-next
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/363 kB of archives.
After this operation, 2,438 kB of additional disk space will be used.
Do you want to continue? [Y/n] y

Selecting previously unselected package gir1.2-appindicator3-0.1.
(Reading dat...

Read more...

Revision history for this message
Eduards Bezverhijs (mjasnik) wrote :

OK, that's strange...
Lets try to figure out what exactly does not work...
Please run this and post the results:
    sudo systemctl status timekpr

Revision history for this message
Eduards Bezverhijs (mjasnik) wrote :

I tried to install timekpr-next as You did but at this moment I had Ubuntu 18.04, that wen't well and no issues.

So, I added verbose output to timekpr-next installation, after some hours a beta version will be ready and published to my ppa.

Please install timekpr-beta (the version should be 0.4.2-4ubuntu1~ppa1) and post the output here, then we'll see where it gets stuck.

Revision history for this message
Mike (ark987) wrote :

I'll wait for the beta version and get back to you.

At this moment the unit service is dead if I try to start it get stuck and does not return to the command prompt, the terminal gets locked starting the service.

Revision history for this message
Eduards Bezverhijs (mjasnik) wrote :

The beta is ready.
Anyhow, dead or not, please post the output of unit status too:
    sudo systemctl status timekpr

Revision history for this message
Eduards Bezverhijs (mjasnik) wrote :

I have it installed in 20.04.1 too, no issues whatsoever.
Let's see what verbose debug will show us.

Previous comment has a slight error, You need to install timekpr-next-beta ;)

Revision history for this message
Mike (ark987) wrote :

Thanks for following up, I've manage to get it working. But I don't think it worth spending more time on digging into this issue unless it affects more people.

Long story short, I've reinstalled Ubuntu 20.04 with Nvidia proprietary drivers with the legacy BIOS mode.
For some reason in UEFI mode timekpr service starts randomly on boots, sometimes is starts sometimes it wont.

In my last reinstall with BIOS mode and nvidia proprietary driver the install was stuck on Enabling the systemd unit, but after the restart I had to run the dpkg reconfigure command to complete the apt installation and then the service was able to start normally on subsequent reboot.

I've installed a VM aside to test and it just works, no issues there...

Revision history for this message
Eduards Bezverhijs (mjasnik) wrote :

Ok, thanks for followup, glad that it worked.

P.S. I'll leave verbose output in place.

Changed in timekpr-next:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.