[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
Same issue on an MSI b350m bazooka Mobo with Ryzen 5600 and rtx 3090 (proprietary drivers, v550) Fresh install of 24.04 beta I believe this bug is related to render hangs and DE crashes I've been experiencing at login. If the bug is circumvented by changing to a blank password for the keyring, these render errors no longer occur. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2052832] Re: Desktop lock-screen is bypassed after switching to virtual tty on console
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2052832 Title: Desktop lock-screen is bypassed after switching to virtual tty on console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2052832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
Same issue after upgrading from 23.10 on a Lenovo Legion 5 15ARH7H -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
I'm also experiencing this issue, although my keyring still exists under ~/.local/share/keyrings/login.keyring and after authenticating using the popup after logging in, all my passwords can be seen when starting "seahorse". The only problem I'm experiencing is that the keyring doesn't automatically unlock after logging in. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061235] [NEW] Login screen doesn't offer authentication using Yubikey after upgrade 23.10 => 24.04
Public bug reported: I own YubiKey 5 Nano. In Ubuntu 23.10 I had configured a login to Gnome using YubiKey so that when I started OS with YubiKey inserted, clicked on my username in login screen, I was offered to touch YubiKey and when I did it, then a login succeeded ✓. But when I upgraded to Ubuntu 24.04 beta, in login screen I'm prompted by entering of password only and no "touch" method is offered anymore . Note that YubiKey auth works well e.g. for "sudo": --- $ sudo apt update Please touch the device. ... This is my GDM policy configuration /etc/pam.d/gdm-password --- #%PAM-1.0 authrequisite pam_nologin.so authrequiredpam_succeed_if.so user != root quiet_success @include common-u2f @include common-auth authoptionalpam_gnome_keyring.so @include common-account # SELinux needs to be the first session rule. This ensures that any # lingering context has been cleared. Without this it is possible # that a module could execute code in the wrong domain. session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close session requiredpam_loginuid.so # SELinux needs to intervene at login time to ensure that the process # starts in the proper default security context. Only sessions which are # intended to run in the user's context should be run after this. # pam_selinux.so changes the SELinux context of the used TTY and configures # SELinux in order to transition to the user context with the next execve() # call. session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open session optionalpam_keyinit.so force revoke session requiredpam_limits.so session requiredpam_env.so readenv=1 session requiredpam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale @include common-session session optionalpam_gnome_keyring.so auto_start @include common-password /etc/pam.d/common-u2f - auth sufficient pam_u2f.so authfile=/etc/u2f_mappings cue Used SW and HW: --- * HW: laptop Yoga Slim 7 14ARE05 * SW: * Ubuntu 24.04 * kernel 6.8.0-22-generic * gdm3 46.0-2ubuntu1, I'm using default Wayland session * libpam-yubico 2.26-1.1build2 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Description changed: I own YubiKey 5 Nano. In Ubuntu 23.10 I had configured a login to Gnome using YubiKey so that when I started OS with YubiKey inserted, clicked on my username in login screen, I was offered to touch YubiKey and when I did it, then a login succeeded ✓. But when I upgraded to Ubuntu 24.04 beta, in login screen I'm prompted by entering of password only and no "touch" method is offered anymore . Note that YubiKey auth works well e.g. for "sudo": --- $ sudo apt update Please touch the device. - ... - + ... This is my GDM policy configuration /etc/pam.d/gdm-password --- #%PAM-1.0 authrequisite pam_nologin.so auth requiredpam_succeed_if.so user != root quiet_success @include common-u2f @include common-auth authoptionalpam_gnome_keyring.so @include common-account - # SELinux needs to be the first session rule. This ensures that any - # lingering context has been cleared. Without this it is possible + # SELinux needs to be the first session rule. This ensures that any + # lingering context has been cleared. Without this it is possible # that a module could execute code in the wrong domain. session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close session requiredpam_loginuid.so # SELinux needs to intervene at login time to ensure that the process # starts in the proper default security context. Only sessions which are # intended to run in the user's context should be run after this. # pam_selinux.so changes the SELinux context of the used TTY and configures # SELinux in order to transition to the user context with the next execve() # call. session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open session optionalpam_keyinit.so force revoke session requiredpam_limits.so session requiredpam_env.so readenv=1 session requiredpam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale @include common-session session optionalpam_gnome_keyring.so auto_start @include common-password - /etc/pam.d/common-u2f - auth sufficient pam_u2f.so authfile=/etc/u2f_mappings cue - Used SW: - - * Ubuntu 24.04 - * kernel 6.8.0-22-generic - * gdm3 46.0-2ubuntu1, I'm using default Wayland session - * libpam-yubico 2.26-1.1build2 + Used SW and HW: + --- + * HW: laptop Yoga Slim 7 14ARE05 + * SW: + * Ubuntu 24.04 + * kernel 6.8.0-22-generic + * gdm3 46.0-2ubuntu1, I'm using default
[Bug 2061234] [NEW] Created an user w language Italian but language is English
Public bug reported: Ubuntu 24.04 from my user w English language I created another user w language Italian but logging in the created user has language English corradi@corrado-n2-nn-0412:~$ inxi -SMxc System: Host: corrado-n2-nn-0412 Kernel: 6.8.0-22-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 Desktop: GNOME v: 46.0 Distro: Ubuntu 24.04 LTS (Noble Numbat) Machine: Type: Desktop System: Gigabyte product: H510M H v: -CF serial: Mobo: Gigabyte model: H510M H v: x.x serial: UEFI: American Megatrends LLC. v: F14 date: 03/25/2022 corradi@corrado-n2-nn-0412:~$ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46.0.1-1ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 18:45:19 2024 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "Screenshot from 2024-04-13 18-37-31.png" https://bugs.launchpad.net/bugs/2061234/+attachment/5764749/+files/Screenshot%20from%202024-04-13%2018-37-31.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2061234 Title: Created an user w language Italian but language is English To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2061234/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
I've just updated my password (unrelated to the issue) and now I only get one popup to unlock the keyring after login - the gnome full-screen one. The non-gnome-shell one has gone away. Attached is a screenshot of the one that is still there. ** Attachment added: "popup1.png" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+attachment/5764728/+files/popup1.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
This affects me on a Microsoft Surface Pro 7+ which I upgraded in-place from 23.10 to 24.04-beta with `do-release-upgrade -d` yesterday. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061118] Re: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)
** Package changed: gnome-shell (Ubuntu Noble) => gtk4 (Ubuntu Noble) ** Changed in: gtk4 (Ubuntu Noble) Status: New => Triaged ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #10901 https://gitlab.freedesktop.org/mesa/mesa/-/issues/10901 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/10901 Importance: Unknown Status: Unknown ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu Noble) Status: New => Triaged ** Changed in: mesa (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
I have the same issue. Keyring and Login passwords are identical but keyring `Login` does not get unlocked automatically on startup. I noticed it couple of days ago after some updates for my 22.04 devel -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Can we manually add support for Balena Etcher, just like VS Code? Etcher is used by hundreds of thousands of users. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
https://gitlab.com/apparmor/apparmor/-/merge_requests/1212 ** Changed in: wike (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
https://gitlab.com/apparmor/apparmor/-/merge_requests/1209 ** Also affects: wike (Ubuntu) Importance: Undecided Status: New ** Also affects: foliate (Ubuntu) Importance: Undecided Status: New ** Changed in: foliate (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Changed in: wike Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Bug watch added: github.com/hugolabe/Wike/issues #181 https://github.com/hugolabe/Wike/issues/181 ** Also affects: wike via https://github.com/hugolabe/Wike/issues/181 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061211] [NEW] Invalid escape sequences in regexes when installing gedit
Public bug reported:
On a clean install of the 24.04 beta, if you do a "sudo apt install
gedit", you get the following messages at the end of the install:
/usr/lib/x86_64-linux-gnu/gedit/plugins/externaltools/library.py:212:
SyntaxWarning: invalid escape sequence '\-'
RE_KEY = re.compile('^([a-zA-Z_][a-zA-Z0-9_.\-]*)(\[([a-zA-Z_@]+)\])?$')
/usr/lib/x86_64-linux-gnu/gedit/plugins/snippets/substitutionparser.py:162:
SyntaxWarning: invalid escape sequence '\s'
match = re.match('?%s\s*' % self.REG_GROUP, tokens)
So there are 2 issues with regexes.
Bug #2055010 reports the first of these, but not the second, and it also
reports a different issue as "the huger problem" (one that I can't
reproduce). I hope I'm making the right call in opening a new bug report
specifically for these regex issues.
Some more details:
- on the clean install, I did apply all available updates before trying to
install gedit
- you can also reproduce this issue from the live ("try ubuntu") environment
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gedit 46.2-1build1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 08:41:26 2024
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gedit (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/2061211
Title:
Invalid escape sequences in regexes when installing gedit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2061211/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
Yeah, I was just testing something else and did a couple of installs in VirtualBox and the issue didn't come up (agreed that VMs might behave very differently). Could this somehow be vendor related? I'm running a ThinkPad E14 AMD Gen 3 - this could also just be a coincidence and the fact, that ThinkPads are probably pretty popular among the Linux crowd. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060723] Re: gtk4: gnome-calculator shows - instead of =
** Changed in: gtk4 (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-calculator (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/2060723 Title: gtk4: gnome-calculator shows - instead of = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/2060723/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
But it can't be affecting all installations. I installed one or two dailies before the beta. The error appeared after an upgrade. Currently fully upgraded. Maybe just re-install... It's annoying to type the password three times at each login. :D ThinkPad P14s AMD Gen 3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
