xdm fails to start on Sundays
Bug #1923472 reported by
Michael Rutter
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| xdm (Debian) |
Confirmed
|
Unknown
|
|||
| xdm (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
On the first login of the week, xdm (1.1.11-3ubuntu2) fails to start on Ubuntu 20.04.
More correctly, it does start, but exits almost immediately on signal 12. It leaves /var/run/xdm.pid behind, and also a running X server with no clients. This makes it hard to restart, for one needs to kill the X server and remove the pid file first.
The cause is logrotate running during startup and killing xdm before xdm installs a handler for SIGUSR2. The issue is more fully described upstream at https:/
In passing I would comment that running logrotate so early during startup seems strange to me. Startup would surely be faster if these sort of "cron" jobs were left until it had finished?
| affects: | systemd (Ubuntu) → xdm (Ubuntu) |
| Changed in xdm (Debian): | |
| status: | Unknown → Confirmed |
To post a comment you must log in.
