FS#78043 - [mutter] 43.4-1: Broken focus for /usr/lib/seahorse/ssh-askpass
Attached to Project:
Arch Linux
Opened by Pascal Ernster (hardfalcon) - Thursday, 30 March 2023, 09:31 GMT
Last edited by Toolybird (Toolybird) - Friday, 02 June 2023, 07:25 GMT
Opened by Pascal Ernster (hardfalcon) - Thursday, 30 March 2023, 09:31 GMT
Last edited by Toolybird (Toolybird) - Friday, 02 June 2023, 07:25 GMT
|
Details
Since upgrading to mutter 43.4-1 and restarting my GNOME
session with that new mutter version, the entry focus when
calling /usr/lib/seahorse/ssh-askpass is broken: Whilst with
mutter 43.3-2, I only had to press the enter key twice to
confirm the dialog, with mutter 43.4-1, pressing the enter
key only confirms the first "Allow inhibiting shortcuts"
dialog, but does not work for the subsequent "Enter your
Secure Shell passphrase" dialog, unless I manually click
that dialog with the mouse.
Additionally, I have also had multiple crashes of the whole GNOME session with mutter 43.4-1, and although I haven't yet been able to find out exactly what's happening there or how exactly to trigger these crashes, it seems that these crashes don't occur anymore after downgrading to mutter 43.3-2. |
This task depends upon
Closed by Toolybird (Toolybird)
Friday, 02 June 2023, 07:25 GMT
Reason for closing: Upstream
Additional comments about closing: See comments
Friday, 02 June 2023, 07:25 GMT
Reason for closing: Upstream
Additional comments about closing: See comments
Sounds like an upstream issue. Have you reported upstream?
> multiple crashes
No logs or backtraces provided?
At least for the focus issue there seems to be a bug report upstream, though I haven't tried yet if reverting the commit named in the comments solves my issue:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2690
Over the last hours, I've also seen a few crashes with both mutter and gnome-shell downgraded to their respective version from before 2023-03-29, so I'm currently inclined to assume that the crashes are not related to the new versions of mutter and gnome-shell.
//EDIT: I've had another crash, so gdm 44.0 + commit b29510dbc51ccf71a7c0ed656d21634a83766c0c doesn't solve this either. I begin to suspect this might be related to either of the following two things:
- my nonstandard/unsupported GNOME setup with gnome-keyring manually ripped out to replace it with KeepassXC, or
- my custom kernel which is based on linux-hardened, but adds (among other things) the following patch on top: https://www.openwall.com/lists/oss-security/2023/03/24/4
There seems to be a pattern of the crashes mostly occuring while I'm scrolling or copy-pasting inside a tmux session inside an SSH session.
So in either case, the crashes are probably not relevant for Archlinux, sorry for the noise.
With systemd 253.2-1 installed and running, when I execute "systemctl daemon-reexec", my GNOME session crashes either immediately or as soon as I press Ctrl+C inside a terminal, even after the "systemctl daemon-reexec" command has finished/returned successfully and there is no process to be killed/cancelled by pressing Ctrl+C. When I downgrade to 253.1-3, my GNOME session crashes again due to "systemctl daemon-reexec" being executed as part of the package's post-install hook and because systemd 253.2-1 is still running, but after that, I can execute "systemctl daemon-reexec" inside a GNOME session without causing that GNOME session to crash.
I've opened a separate issue for this: https://bugs.archlinux.org/task/78097