Public bug reported:
## Package and environment
- Ubuntu 26.04 LTS (resolute), amd64
- Package: `timekpr-next`
- Installed/candidate version: `0.5.4-3build1` from `resolute/universe`
- Desktop: Ubuntu GNOME, Wayland
- Python: 3.13.13
## Description
After installing `timekpr-next` from the Ubuntu 26.04 archive, neither
the normal nor the `(SU) Timekpr-nExT Control Panel` desktop launcher
opens a window. The system daemon also starts and immediately exits
successfully.
The desktop files themselves point to the expected executable:
```text
/usr/share/applications/timekpr-admin-su.desktop:
Exec=pkexec /usr/bin/timekpra
/usr/share/applications/timekpr-admin.desktop:
Exec=/usr/bin/timekpra
```
However, all three entry-point programs installed in `/usr/bin` contain
only a shebang and no Python application code:
```console
$ wc -c /usr/bin/timekpra /usr/bin/timekprc /usr/bin/timekprd
20 /usr/bin/timekpra
20 /usr/bin/timekprc
20 /usr/bin/timekprd
60 total
$ head -n 2 /usr/bin/timekpra
#! /usr/bin/python3
$ /usr/bin/timekpra; echo $?
0
```
This content is recorded by the installed package, so it is not local
file corruption:
```console
$ md5sum /usr/bin/timekpra /usr/bin/timekprc /usr/bin/timekprd
e5a95e7ea0fb62c0dfb31d5c3c2cca9b /usr/bin/timekpra
e5a95e7ea0fb62c0dfb31d5c3c2cca9b /usr/bin/timekprc
e5a95e7ea0fb62c0dfb31d5c3c2cca9b /usr/bin/timekprd
$ grep 'usr/bin/timekpr' /var/lib/dpkg/info/timekpr-next.md5sums
e5a95e7ea0fb62c0dfb31d5c3c2cca9b usr/bin/timekpra
e5a95e7ea0fb62c0dfb31d5c3c2cca9b usr/bin/timekprc
e5a95e7ea0fb62c0dfb31d5c3c2cca9b usr/bin/timekprd
```
The actual entry-point source files are present and nonempty under
`dist-packages`:
```console
$ wc -c /usr/lib/python3/dist-packages/timekpr/client/timekpra.py \
/usr/lib/python3/dist-packages/timekpr/client/timekprc.py \
/usr/lib/python3/dist-packages/timekpr/server/timekprd.py
958 /usr/lib/python3/dist-packages/timekpr/client/timekpra.py
888 /usr/lib/python3/dist-packages/timekpr/client/timekprc.py
1984 /usr/lib/python3/dist-packages/timekpr/server/timekprd.py
```
The service journal is consistent with a no-op executable:
```text
systemd[1]: Started timekpr.service - Timekpr-nExT daemon service.
systemd[1]: timekpr.service: Deactivated successfully.
```
Purging and reinstalling `timekpr-next 0.5.4-3build1` reproduces the
same result.
## Steps to reproduce
1. Install Ubuntu 26.04 LTS amd64 with the `resolute/universe` archive enabled.
2. Run `sudo apt install timekpr-next`.
3. Launch `(SU) Timekpr-nExT Control Panel` from the desktop menu.
4. Observe that authentication may occur, but no control-panel window opens.
5. Run `wc -c /usr/bin/timekpra /usr/bin/timekprc /usr/bin/timekprd`.
## Expected result
The admin control panel opens, the user client can run, and
`timekpr.service` remains active.
## Actual result
All three `/usr/bin` entry points silently return exit status 0 because
each contains only a shebang. No control panel opens, the client does
not run, and the daemon deactivates immediately.
## Workaround
Copying the real Python entry-point files over the empty launchers,
adding a Python 3 shebang, and restarting the service makes the entry
points runnable:
```bash
sudo install -m 755 /usr/lib/python3/dist-packages/timekpr/client/timekpra.py
/usr/bin/timekpra
sudo install -m 755 /usr/lib/python3/dist-packages/timekpr/client/timekprc.py
/usr/bin/timekprc
sudo install -m 755 /usr/lib/python3/dist-packages/timekpr/server/timekprd.py
/usr/bin/timekprd
sudo sed -i '1i#!/usr/bin/python3' /usr/bin/timekpra
sudo sed -i '1i#!/usr/bin/python3' /usr/bin/timekprc
sudo sed -i '1i#!/usr/bin/python3' /usr/bin/timekprd
sudo systemctl restart timekpr
```
Any package reinstall or upgrade can overwrite this workaround.
## Packaging assessment
This appears to be a binary-package generation error rather than a
desktop, polkit, or Wayland problem. The fix should ensure that the
built `.deb` contains functional entry points (or wrappers
importing/calling the corresponding modules), and should add a package
build/autopkgtest that verifies the three installed launchers are not
shebang-only.
There is a separate Ubuntu 26.04 report concerning `timekpr-next 0.5.4`
and Python/configparser (`LP: #2158741`). That issue may appear after
these no-op entry points are repaired, but it does not explain the
current silent exit: the Python application code is never executed here.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: timekpr-next 0.5.4-3build1
ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12
Uname: Linux 7.0.0-29-generic x86_64
ApportVersion: 2.34.1-0ubuntu0.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 11 09:47:02 2026
InstallationDate: Installed on 2026-08-08 (3 days ago)
InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: timekpr-next
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: timekpr-next (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug resolute wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2163263
Title:
timekpr-next 0.5.4-3build1 installs shebang-only
timekpra/timekprc/timekprd, so GUI and daemon exit immediately
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/timekpr-next/+bug/2163263/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
