** Changed in: systemd (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2004092
Title:
casper fails to add any users because GID 999
>> the next casper upload will regress the current version of the fix
> What is the rationale for reverting this change?
As of yet I think that has't happened. Right now we have 2 caspers
* git casper at https://git.launchpad.net/casper, version 1.478, without this
proposed fix since the MP was
> the next casper upload will regress the current version of the fix
I'm all in favor of a better longer-term fix replacing this one being
tracked in systemd, but an unrelated casper upload regressing this
change prior to a longer-term solution being in place will cause issues
with all amd64 live
** Tags removed: rls-ll-incoming
** Tags added: foundations-todo
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Tagged incoming as while there is a modified casper uploaded, the
matching merge proposal was disapproved
(https://code.launchpad.net/~tsimonq2/casper/+git/casper/+merge/436490),
so the next casper upload will regress the current version of the fix.
A longer term solution is needed.
** Tags
I noticed that the live Lunar Ubuntu Desktop (standard Ubuntu) arrives
at a page that prompts to enter user name and password, in other words,
there is not longer a standard user with a blank password.
This should be considered when we decide how to deal with assigning a
user ID for the live
** Merge proposal linked:
https://code.launchpad.net/~tsimonq2/casper/+git/casper/+merge/436490
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2004092
Title:
casper
** Bug watch added: Debian Bug tracker #1029785
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029785
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029785
Importance: Unknown
Status: Unknown
--
You received this bug notification
Just to catch the bug report up with the IRC discussion:
we got away with it in casper because we knew there weren't going to
be 899 IDs allocated in this range in the installer context, and the casper
user goes away post-install
systemd doesn't statically set them, it allocates them using
> I think it is a bug in systemd to be bypassing the process
> specified in Debian Policy.
Note that systemd specifies its own UID/GID "spec" here:
https://systemd.io/UIDS-GIDS/.
I think assigning 999 to systemd-journald conforms with both systemd's
and Debian's policy, no? The systemd-journal
I should also mention, that I have created a second user 'tester' in
previous versions of persistent live Lubuntu for example to test bug
#2000787 "Live system cannot leave 'Lock Screen' when selected from
menu".
This user had userID number 1000, and it never caused any problem. If I
remember
> It's not clear to me that changing the casper user to use this uid
won't badly confuse the installer when it comes time to create the
actual user account, or at least cause gid 1000 to be skipped.
After some testing with the newly-uploaded casper, I can confirm this is not
the case. I tested
I made a persistent live Lubuntu system with mkusb:dus-iso2usb in a USB-
SSD from today's daily iso (2023-01-29).
This system works as it should (persistent live) also after shut down
and boot (in a Dell Precision M4800).
-o-
lubuntu@lubuntu:~$ df -h
Filesystem Size Used Avail Use%
I cloned Lubuntu Lunar from today's (2023-01-29) daily iso file to a
USB-SSD and booted it in a Dell Precision M4800.
It seems to me that it works correctly to run a live session with the
userID number 1000 for 'lubuntu' :-)
--
You received this bug notification because you are a member of
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
> It's not clear to me that changing the casper user to use this uid
won't badly confuse the installer when it comes time to create the
actual user account, or at least cause gid 1000 to be skipped.
It's not clear to me that it will. Casper doesn't touch the squashfs
that ends up on the installed
This bug was fixed in the package casper - 1.479
---
casper (1.479) lunar; urgency=medium
* Fix adduser, which fails due to systemd taking 999 (LP: #2004092).
-- Simon Quigley Sat, 28 Jan 2023 21:09:53 -0600
** Changed in: casper (Ubuntu)
Status: Fix Committed => Fix
@vorlon I just attempted an installation of Ubuntu Desktop 23.04 using
the latest (broken) ISO. I am able to get to the installer since a setup
wizard has me create a user account to get into the live ISO. I saw
multiple "System program problem detected" warnings appear during the
installation,
> systemd-journald now uses GID 999
Ummm where is this coming from? Debian Policy states:
9.2.2. UID and GID classes
--
[...]
100-999:
Dynamically allocated system users and groups. Packages which need
a user or group, but can have this user or group allocated
19 matches
Mail list logo
