** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1984031
Title:
The username 'at' cannot list on logon screen
To manage notifications about this bug go to:
Public bug reported:
OS: Ubuntu 20.04.x LTS (Desktop)
Problem description:
When I try to use 'at' as my username, after rebooting, gnome-initial-setup
reappears and asks to create a new user.
Re-produce procedures (1):
1. Del all other users from terminal
2. Reboot to OS.
3. Add a user by
According to the analysis by Milan Crha at GNOME (see the link in the
bug description) this appears to be associated with the use of Xorg and
doesn't occur under Wayland. It seems that although Wayland is the
default X server in Ubuntu-22.04, The desktop session for MATE isn't
supported on
ACK on the debdiff in comment #3. It is building in the security team
PPA here:
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages
Once it has finished building, please test it and detail the testing
performed in this bug, and we will release it as a security update.
ACK on the debdiff in comment #2. It is building in the security team
PPA here:
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages
Once it has finished building, please test it and detail the testing
performed in this bug, and we will release it as a security update.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evolution (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
Public bug reported:
When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty
much always) a crash from tracker-extract, as described in the following
error report:
https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0
The crash occurs during the upgrade, which
** Attachment added: "scenario_3_installer.zip"
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607336/+files/scenario_3_installer.zip
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in
** Attachment added: "scenario_2_appstream.txt"
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607337/+files/scenario_2_appstream.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in
** Attachment added: "scenario_2_installer.zip"
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607335/+files/scenario_2_installer.zip
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in
** Attachment added: "scenario_1_installer.zip"
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607334/+files/scenario_1_installer.zip
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in
Reuploading previous attachments after redacting sensitive information.
Original comment copied below:
Okay, I've gone down the rabbit hole with this one. It's possible this
is 2 separate issues.
I tested 3 scenarios:
Scenario 1 - Performed a clean Ubuntu Server install (interactive), and
** Attachment removed: "installer logs for Scenario 1"
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607134/+files/scenario_1_installer.zip
** Attachment removed: "scenario_2_installer.zip"
13 matches
Mail list logo
