Your message dated Mon, 1 Jun 2026 15:07:58 +0100
with message-id <[email protected]>
and subject line Re: Bug#1126595: dbus-system-bus-common: fatal: The user
`messagebus' already exists and has a password
has caused the Debian Bug report #1126595,
regarding dbus-system-bus-common: fatal: The user `messagebus' already exists
and has a password
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1126595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126595
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dbus-system-bus-common
Version: 1.16.2-2
Control: affects -1 src:biometryd src:buteo-syncfw-qml src:callaudiod
src:certmonger src:click src:crmsh src:dbus-test-runner src:dee src:dioptas
src:gcp src:gmenuharness src:guidata src:hfd-service src:ippsample
src:libaccounts-glib src:libayatana-appindicator-glib src:libqtdbusmock
src:libqtdbustest src:libusermetrics src:lomiri-account-polld
src:lomiri-action-api src:lomiri-api src:lomiri-app-launch
src:lomiri-download-manager src:lomiri-indicator-network
src:lomiri-indicator-transfer-buteo src:lomiri-location-service
src:lomiri-notifications src:lomiri-online-accounts src:lomiri-push-qml src:mir
src:pydbus src:pymca src:python-renardo-lib src:python-vispy src:qmenumodel
src:repowerd src:ruby-dbus src:telepathy-glib src:telepathy-logger src:u1db-qt
Severity: serious
Tags: forky sid ftbfs
Dear maintainer:
During a rebuild of all packages in unstable using the nocheck build profile,
all the above packages failed to build. The root cause is probably the same,
so I'm filing a single bug for all of them, which is easy to reassign,
initially against dbus-system-bus-common.
This is the way it fails:
Setting up dbus-system-bus-common (1.16.2-2) ...
fatal: The user `messagebus' already exists and has a password. Exiting.
dpkg: error processing package dbus-system-bus-common (--configure):
old dbus-system-bus-common package postinst maintainer script subprocess
failed with exit status 13
I've put full build logs for all the packages here:
https://people.debian.org/~sanvila/build-logs/202601/
Maybe this is related to this other bug in the shadow package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124795
but I'm not really sure. If the bugs are really the same and they have to be
merged,
please keep the affects.
(I've put Chris in x-debbugs-cc).
Thanks.
--- End Message ---
--- Begin Message ---
Version: 3.155
On Mon, 01 Jun 2026 at 15:19:17 +0200, Marc Haber wrote:
On Sat, Jan 31, 2026 at 11:49:47AM +0000, Simon McVittie wrote:
This appears to have been fixed in adduser git already, by commit
debian/3.154-13-gd5820ae "rework EXISTING_ and existing_user_status", so the
next adduser upload can presumably close this bug report.
Did it get fixed?
I did provide steps to reproduce that don't require specific dependent
packages (like dbus-system-bus-common in Santiago's original report). I
confirm that they now work.
The bug was to do with systemd-sysusers creating a user with encrypted
password "!*", and older adduser --system not accepting that as a valid
locked system user:
$ podman run --rm -it debian:forky-slim
# apt update && apt upgrade
# apt install adduser
...
Setting up adduser (3.155) ...
# adduser --system _star
# adduser --system _bang
# adduser --system _bangstar
# echo '_star:*' | chpasswd -e
# echo '_bang:!' | chpasswd -e
# echo '_bangstar:!*' | chpasswd -e
# adduser --system _bang
# adduser --system _star
# adduser --system _bangstar
The last line (second `adduser --system _bangstar`) is the one that
previously failed.
Alternatively,
$ podman run --rm -it debian:forky-slim
# apt update && apt upgrade
# apt install adduser systemd-standalone-sysusers
# systemd-sysusers - <<EOF
u _bangstar
EOF
# adduser --system _bangstar
also reproduced this bug in the past, and also now works.
In both cases `getent shadow _bangstar` should start with:
_bangstar:!*:...
Thanks,
smcv
--- End Message ---
