[Bug 1975884] Re: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy)
Just noticed the screenlock freeze again, worked fine most of yesterday (mostly only had firefox open), then later installed GSConnect extension (was essential for getting an errand done) and had sublimetext open (around 15 workspaces open). See https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976163 for associated info. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975884 Title: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976163] [NEW] Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) (continuation)
Public bug reported: See earlier discussion https://bugs.launchpad.net/ubuntu/+bug/1975884 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat May 28 13:01:17 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2021-07-15 (316 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-02 (26 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976163 Title: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) (continuation) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975884] Re: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy)
Got it, thanks. I haven't tried to 'remove all' unsupported extensions per your instructions yet, but did disable all non-system extensions via the 'Extensions Manager' app and still noticed the issue (without logging in again). Will now try removing all per your instructions, logging in again/rebooting and see. EDIT: haven't logged out or rebooted yet, but noticing a slight (not as much) delay still. Could be associated with having a large number of apps/browser tabs open. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975884 Title: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975884] Re: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy)
** Description changed: As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1769981/comments/25 , I've been observing an issue when unlocking my computer (usually from a screen lock state, not hibernation/sleep) where after entering the first few characters of my password the screen freezes for 10-20 seconds before I can do any type of input (mouse, touch, keyboard). I've largely been noticing this since upgrading from Ubuntu 21.10 to 22.04. It doesn't happen all the time, but often enough to file an issue for. So far I've tried: - Disabling the 'blur my shell' extension - still encountered the issue again eventually. - Looking for anything associated with this in /var/crash - couldn't find anything. - Looking for anything associated at errors.ubuntu.com for my id. + + What I may eventually try: + - Seeing if this may depend on having too many browser tabs / apps open. Currently not in a position to do this. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 19:19:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (315 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago) ** Description changed: As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1769981/comments/25 , I've been observing an issue when unlocking my computer (usually from a screen lock state, not hibernation/sleep) where after entering the first few characters of my password the screen freezes for 10-20 seconds before I can do any type of input (mouse, touch, keyboard). + + I've also seen it happen when having touch / gesture input switch + between displaying the user name and the password field - where the + screen can get stuck in the animation in an interstitial state for a + number of seconds. I've largely been noticing this since upgrading from Ubuntu 21.10 to 22.04. It doesn't happen all the time, but often enough to file an issue for. So far I've tried: - Disabling the 'blur my shell' extension - still encountered the issue again eventually. - Looking for anything associated with this in /var/crash - couldn't find anything. - Looking for anything associated at errors.ubuntu.com for my id. What I may eventually try: - Seeing if this may depend on having too many browser tabs / apps open. Currently not in a position to do this. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 19:19:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (315 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975884 Title: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975884] [NEW] Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy)
Public bug reported: As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1769981/comments/25 , I've been observing an issue when unlocking my computer (usually from a screen lock state, not hibernation/sleep) where after entering the first few characters of my password the screen freezes for 10-20 seconds before I can do any type of input (mouse, touch, keyboard). I've largely been noticing this since upgrading from Ubuntu 21.10 to 22.04. It doesn't happen all the time, but often enough to file an issue for. So far I've tried: - Disabling the 'blur my shell' extension - still encountered the issue again eventually. - Looking for anything associated with this in /var/crash - couldn't find anything. - Looking for anything associated at errors.ubuntu.com for my id. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 19:19:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (315 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975884 Title: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769981] Re: Temporary screen freeze when coming back from screen standby
I've been having an issue similar to this on 22.04 (jammy) and don't recall experiencing it on 21.10. It's actually happened not just from standby but from just being on (with display off) as well. I'm still testing, but it could be extensions like 'blur my shell' causing an issue. Couldn't find anything associated with this in /var/crash or in errors.ubuntu.com for my id. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769981 Title: Temporary screen freeze when coming back from screen standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973386] Re: 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work
This issue is most likely related to this gnome issue fixed in gnome 42.1 - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5273 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5273 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5273 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973386 Title: 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973386] Re: 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work
** Description changed: Several people on reddit (many surface pro / go users, and myself as an HP tablet pc user) have been experiencing an issue on Ubuntu 22.04 (jammy jellyfish) where the gnome lockscreen on-screen keyboard is not functional, but the main ubuntu loginscreen on-screen keyboard is functional. https://www.reddit.com/r/SurfaceLinux/comments/umeiqx/onscreen_keyboard_doesnt_register_key_presses_in/ Steps to reproduce: 0) Ensure you have Screen Keyboard enabled in the accessibility menu. 1) From a logged-in state, Go to upper right corner and click Lock 2) Turn device back on so 'user lockscreen' comes back on, try to log in using touchscreen on-screen keyboard. 3) Observe key presses don't work. 4) Try to close login password prompt such that switch user login button appears. - 5) Touch switch user login button, leading to 'login screen' (black with ubuntu logo) + 5) Touch switch user login button, leading to 'login screen' (black with ubuntu logo) 6) Select user, try to log in using touchscreen on-screen keyboard and observe it works. See demo video: https://youtu.be/RjfRZOmwsgs (NOTE: In the video there's another separate issue here in regards to the 'login screen' not having awareness of tablet screen orientation) + + This was observed on 22.04, I didn't experience this issue on 21.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973386 Title: 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973386] [NEW] 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work
Public bug reported: Several people on reddit (many surface pro / go users, and myself as an HP tablet pc user) have been experiencing an issue on Ubuntu 22.04 (jammy jellyfish) where the gnome lockscreen on-screen keyboard is not functional, but the main ubuntu loginscreen on-screen keyboard is functional. https://www.reddit.com/r/SurfaceLinux/comments/umeiqx/onscreen_keyboard_doesnt_register_key_presses_in/ Steps to reproduce: 0) Ensure you have Screen Keyboard enabled in the accessibility menu. 1) From a logged-in state, Go to upper right corner and click Lock 2) Turn device back on so 'user lockscreen' comes back on, try to log in using touchscreen on-screen keyboard. 3) Observe key presses don't work. 4) Try to close login password prompt such that switch user login button appears. 5) Touch switch user login button, leading to 'login screen' (black with ubuntu logo) 6) Select user, try to log in using touchscreen on-screen keyboard and observe it works. See demo video: https://youtu.be/RjfRZOmwsgs (NOTE: In the video there's another separate issue here in regards to the 'login screen' not having awareness of tablet screen orientation) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973386 Title: 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
Just to summarize above, I suspect this is related to touch input event handling rather than earlier thoughts around bluetooth or screen orientation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
Thanks. After experiencing this issue 2-3 times last night, I realized this may possibly be related to tablet screen rotation (not sure if the gnome-shell logs delve into this, tried looking and didn't see anything that seemed relevant) - Generally when I've noticed this bug I was using the device in portrait mode. Screen orientation done via physically rotating device + using internal sensor. My setup/experience in this last encounter was: - Had 3rd party gnome shell extensions (including wandering pixel) disabled beforehand - only "Desktop Icons NG" enabled. - Turned off bluetooth as well, to try and dispell earlier ideas of it being related to the bluetooth keyboard connection. Steps: - Rotated screen to portrait, had firefox and a gnome files window open. - Started using the device, might've rotated back to landscape once or twice quickly to see what happens. - Observed when issue happens (while in portrait mode), just beforehand active window I had open (gnome files) suddenly moved maybe 50-100px up, like it was correcting for a orientation change even though I was felt like I was just using device normally laid down in portrait mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938623] Re: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers
Realizing this likely has more to do with the lack of driver support for usb-c hubs on linux - per pulseaudio's documentation ( https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#module- switch-on-port-available ) : "# module-switch-on-connect Earlier this module was required to automatically switch to a newly plugged in USB sound card, but nowadays USB sound cards have higher priority than internal sound cards, so they automatically become the default sink (unless you have manually configured the default sink to be something else) and the need for this module is greatly reduced." "#module-switch-on-port-available (not on USB sound cards, though, since they don't support jack detection)" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938623 Title: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1938623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938623] Re: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers
realized this has more to do with pulseaudio settings ** Changed in: ubuntu Status: New => Opinion ** Package changed: ubuntu => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938623 Title: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1938623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938623] [NEW] Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers
Public bug reported: I'm using Ubuntu 21.04 with an intel tablet and a lenovo usb-c hub that has an audio adapter: See https://linux-hardware.org/?probe=09f8c72d80/ I never have anything hooked into the audio jack on usb-c hub, yet every time I plug my tablet into the usb-c hub the sound output switches to the usb-c hub instead of staying routed to the tablet speakers. I then have to go either into settings or use a sound output extension to switch it back to the speakers. This issue does not happen when using Windows 10 - audio stays routed through the tablet speakers - my guess is that it goes a step further and detects whether an audio jack actually has a cable plugged in or not. What package handles determining default audio routing for Ubuntu 21.04 / Gnome 3.38.5? I'd like to file a bug about this / possibly see if I can help make the defaults work better. See also OS confusion about default audio sink - pulse: https://askubuntu.com/questions/1231935/os-confusion-about-default- audio-sink-pulse ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938623 Title: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1938623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
fwiw in addition to earlier experiencing this with no extensions, I've also experienced it while running the 'wandering pixel' extension ( https://extensions.gnome.org/extension/4028/wandering-pixel/ ) intended to workaround another application hang issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938435] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with
** Summary changed: - gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with 3rd party extensions disabled) + [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with 3rd party extensions disabled) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938435 Title: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with 3rd party extensions disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
** Summary changed: - gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input + [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
Done, issue observed again (without extensions) in https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938435 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938435] [NEW] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with 3rd part
Public bug reported: filed for new attachments - see https://bugs.launchpad.net/gnome- shell/+bug/1938352 & https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4508 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 29 06:12:21 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (13 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938435 Title: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with 3rd party extensions disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
@vanvugt the issue goes away when I log out. To clarify, do you want me to try: A: Leaving the above extensions enabled, try to disable them when the issue occurs, then see if the problem stops occurring? B: Turn off those extensions now, then see if I observe the issue happen again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] [NEW] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
Public bug reported: Further detailed information filed in gnome-shell bug filing: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4508#note_1213365 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 28 17:56:57 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (13 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
