Ah, that's what I was looking for, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971559
Title:
After Ugrade, Jammy requires me to create a new user, although users
are present
To manage
Indeed that's quite a special case. Checking upstream another available
workaround that doesn't involve adding a local account is to edit
/etc/gdm3/custom.conf to set
[daemon]
InitialSetupEnable=false
https://gitlab.gnome.org/GNOME/gdm/-/blob/main/daemon/gdm-
display.c#L1690
** Changed in:
> Non system accounts flagged as systemuser should perhaps could as an
existing user in that logic even if they aren't explicitly displayed?
I'd expect that to depend very much on the installation at hand (in our
case it would), but that can't be decided programmatically. I'd opt for
a way of
Sebastien, thanks for your reply.
First of all, considering that this is a somewhat special (though not unlikely)
setup on our side, you may demote this bug from importance high to lower. This
is to remove strain on you developers, this bug will only concern special
institutional setups like
Thanks for the details, you got me slightly confused now though. Was
'linadmin' that user and did it got somewhat flagged as system user on
upgrade? Or did the user you created back then got removed somehow? It
sounds like you had workarounded the problem in 20.04 and that the
workaround should
Behaviour in 20.04 was like it is in 22.04: Once I went through the
dialog and created one no-system user, the login screen shows all
accounts not listed as "system". I.e. all of our LDAP users (which are
the only ones relevant to our users).
I manually marked those accounts as system, to have
What was the behaviour in 20.04? Was any user being listed? How did you
mark those accounts as SystemAccount=true?
If you don't want usernames to be listed the standard way would be to follow
the steps there
https://help.gnome.org/admin/system-admin-guide/stable/login-userlist-disable.html.en
Indeed, all local accounts are marked as system accounts, because they
all serve administrative uses in one way or the other, and shall not be
seen by normal users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
root@rechner2-3-12:~# /usr/libexec/accounts-daemon --debug
(accounts-daemon:9005): DEBUG: entering main loop
(accounts-daemon:9005): DEBUG: Changing permission of
/var/lib/AccountsService/users/vorlage to 0600
(accounts-daemon:9005): DEBUG: Changing permission of
root@rechner2-3-12:~# cat /var/lib/AccountsService/users/linadmin
# do not show user in greeter
[User]
SystemAccount=true
Ah! This could be it! lindamin is marked as SystemAccount, because our users
shall not see it in the list of accounts on the login screen …
--
You received this bug
doing
$ sudo /usr/libexec/accounts-daemon --debug
should help figuring out why the user is filtered out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971559
Title:
After Ugrade, Jammy requires
Do you have a /var/lib/AccountsService/users/linadmin and if so does it
have a SystemAccount= key and what is its value?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971559
Title:
After Ugrade,
Don't know if this helps:
root@rechner2-3-12:~# ps -ef|grep initial
gnome-i+20441829 0 08:20 tty1 00:00:00 /usr/libexec/gdm-x-session
dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart
--session gnome-initial-setup
gnome-i+20812044 0 08:20 tty1
linadmin is definitely a user with ultimate sudo rights:
root@rechner2-3-12:~# sudo -U linadmin --list
Passende Defaults-Einträge für linadmin auf rechner2-3-12:
env_reset, mail_badpass,
secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin\:/snap/bin
Der Benutzer
Yes, system is still in this state. I went through the dialog once and created
a user. After that the machine booted into th login screen and worked. Then I
removed the new user with "deluser" and at next boot I was back at the dialog.
So, yes, it appears the code does not detect that there are
/bin/bash is availble, I can su to linadmin and even connect as linadmin
by ssh.
Journal is attached.
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+attachment/5587019/+files/journal
--
You received this bug notification because
oh also, do you still have the system in a state showing the issue?
because otherwise poking at the current state of things isn't going to
help us understand what was wrong
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
and you have /bin/bash available?
could you add the 'journalctl -b 0' log from the system to the report?
what's the output of
$ dbus-send --system --type=method_call --print-reply
--dest=org.freedesktop.Accounts /org/freedesktop/Accounts
org.freedesktop.Accounts.ListCachedUsers
--
You
root@rechner2-3-12:~# grep linadmin /etc/passwd
linadmin:x:1000:1000:Linux-Administrator,,,:/home/linadmin:/bin/bash
/home/linadmin is a local directory and linadmin is a locally configured
user, no LDAP account.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Was /home pointing somewhere that doesn't exist anymore? Or is it an
LDAP problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971559
Title:
After Ugrade, Jammy requires me to create a new user,
could you share the output of
$ grep linadmin /etc/passwd
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971559
Title:
After Ugrade, Jammy requires me to create a new user, although users
are
The local user with sudo rights has uid 1000:
root@rechner2-3-12:~# id linadmin
uid=1000(linadmin) gid=1000(linadmin)
Gruppen=4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare),1000(linadmin)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "image20220505_082109516.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+attachment/5586888/+files/image20220505_082109516.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That's the dialog.
** Attachment added: "image20220505_082026251.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+attachment/5586887/+files/image20220505_082026251.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: jammy
** Package changed: gdm3 (Ubuntu) => gnome-initial-setup (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971559
Title:
After Ugrade, Jammy requires me to create a new
Sorry, I'm far from that machine at the moment, but I'll try describing:
- Desktop environment: GNOME (standard Ubuntu Desktop)
- I don't see the login screen, Ubuntu boots through to the desktop and shows
the dialog.
- dialog fills almost the whole desktop and nothing can be done except
** Package changed: ubiquity (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971559
Title:
After Ugrade, Jammy requires me to create a new user, although users
are
Could you take a photo of the dialog? Is that the initial setup started
on the login screen?
Which desktop environment do you use?
It could that the code doesn't detect you have an user, is that a normal
local user? what is the uid?
** Changed in: ubiquity (Ubuntu)
Importance: Undecided =>
Not sure if ubiquoty package is the right place, please change if
necessary.
** Package changed: ubuntu => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971559
Title:
After
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
30 matches
Mail list logo
