Warning because an already existing user is tried to be created

Bug #1475094 reported by Sworddragon on 2015-07-16
This bug affects 6 people
Affects Status Importance Assigned to Milestone
adduser (Debian)
Fix Released
adduser (Ubuntu)
systemd (Ubuntu)

Bug Description

I'm using Ubuntu 15.10 dev with systemd/udev 222-1ubuntu4 and on the last upgrades I have noticed that these packages are trying to create users which already exists. On reinstalling them udev shows on setting up "addgroup: The group `input' already exists as a system group. Exiting." and systemd shows on setting up "addgroup: The group `systemd-journal' already exists as a system group. Exiting." and "addgroup: The group `systemd-journal-remote' already exists as a system group. Exiting.". Maybe it could be checked if a user exists to avoid showing a warning.

description: updated
Martin Pitt (pitti) on 2015-07-16
no longer affects: udev (Ubuntu)
Changed in systemd (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Martin Pitt (pitti) wrote :
Changed in systemd (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
status: Triaged → Fix Committed
Martin Pitt (pitti) wrote :

I reverted that patch, as it would again cause fatal errors to be ignored. We should put back --quiet, and fix adduser to not hide errors with --quiet (linked Debian bug).

Changed in systemd (Ubuntu):
status: Fix Committed → Triaged
Changed in adduser (Debian):
status: Unknown → New
Launchpad Janitor (janitor) wrote :
Download full text (4.5 KiB)

This bug was fixed in the package systemd - 222-2ubuntu1

systemd (222-2ubuntu1) wily; urgency=medium

  * Merge with Debian unstable. Remaining Ubuntu changes:
    - Hack to support system-image read-only /etc, and modify files in
      /etc/writable/ instead.
    - Keep our much simpler udev maintainer scripts (all platforms must
      support udev, no debconf).
    - initramfs init-bottom: If LVM is installed, settle udev,
      otherwise we get missing LV symlinks. Workaround for LP #1185394.
    - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
      dependencies to "lvm2" which is handled with udev rules in Ubuntu.
    - Add debian/udev.lvm2.service to avoid running the dummy lvm2 init
    - Provide shutdown fallback for upstart. (LP: #1370329)
    - debian/extra/ifup@.service: Additionally run for "auto" class. We don't
      really support "allow-hotplug" in Ubuntu at the moment, so we need to
      deal with "auto" devices appearing after "/etc/init.d/networking start"
      already ran. (LP: #1374521) Also run ifup in the background during boot,
      to avoid blocking network.target. (LP: #1425376)
    - ifup@.service: Drop dependency on networking.service (i. e.
      /etc/init.d/networking), and merely ensure that /run/network exists.
      This avoids unnecessary dependencies/waiting during boot and dependency
      cycles if hooks wait for other interfaces to come up (like ifenslave
      with bonding interfaces). (LP: #1414544)
    - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
      Ubuntu we currently keep the setting whether the RTC is in local or UTC
      time in /etc/default/rcS "UTC=yes|no", instead of /etc/adjtime.
      (LP: #1377258)
    - Put session scopes into all cgroup controllers. This makes unprivileged
      user LXC containers work under systemd. (LP: #1346734)
    - systemctl: Don't forward telinit u to upstart. This works around
      upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
      that changes to point to systemd during the upgrade. This avoids running
      systemd during a dist-upgrade. (LP: #1430479)
    - Drop hwdb-update dependency from udev-trigger.service, which got
      introduced in v219-stable. This causes udev and plymouth to start too
      late and isn't really needed in Ubuntu yet as we don't support stateless
      systems yet and handle hwdb.bin updates through dpkg triggers. This can
      be dropped again with initramfs-tools 0.117.
    - Lower Breaks: to plymouth version which has the udev inotify fix in
    - Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs.
    - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681)

    Upgrade fixes, keep until 16.04 LTS release:
    - systemd Conflicts/Replaces/Provides systemd-services.
    - Remove obsolete systemd-logind upstart job.
    - Clean up obsolete /etc/udev/rules.d/README.
    - systemd.postinst: Migrate mountall specific fstab options to standard
      util-linux "nofail" option.

  * ifup@.service: Run ifup for "auto" class in ExecStart instead of
    ExecStartPost, as it spawns a long-run...


Changed in systemd (Ubuntu):
status: Triaged → Fix Released
Martin Pitt (pitti) wrote :

The next upload will revert this, so reopening the bug right away.

Changed in systemd (Ubuntu):
status: Fix Released → Triaged
Martin Pitt (pitti) on 2015-09-01
Changed in adduser (Ubuntu):
status: New → Triaged
Changed in systemd (Ubuntu):
assignee: Martin Pitt (pitti) → nobody
Changed in adduser (Ubuntu):
importance: Undecided → Medium
WinEunuchs2Unix (ricklee518) wrote :

Noticed this error for the first time today running `sudo apt upgrade`. Also for the first time (single user account laptop) had to sign on to console (ctrl+alt+F1) and (ctrl+alt+f2) because Ubuntu 16.04 login screen wasn't working due to activating Nvidia 367.44 driver in `Additional Drivers` screen.

Signing into console was necessary for the first time ever in order to restore Intel integrated graphics and using the system normally.

(Kernel version 4.7.5)

Changed in adduser (Debian):
status: New → Fix Released
Changed in adduser (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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