[Bug 1901017] Re: Desktop gradually increases response lag to clicks in 20.04 (Fixed by Alt+F2, "r"))
[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/1901017 Title: Desktop gradually increases response lag to clicks in 20.04 (Fixed by Alt+F2, "r")) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions
Excellent, thanks! Then let's consider both the uploads verified. ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-focal verification-done-groovy -- 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/1899206 Title: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1899206/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions
Sorry, yes I should have said. I tested on both 20.04 and 20.10. -- 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/1899206 Title: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1899206/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions
On 2020-12-24 19:35, Matthew Wilson wrote: > Tested with my bluetooth mouse and it seems to work correctly now. Did you test on 20.04 or 20.10? -- 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/1899206 Title: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1899206/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions
Tested with my bluetooth mouse and it seems to work correctly now. Thanks! -- 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/1899206 Title: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1899206/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1908801] Re: Acer laptop internal keyboard & touchpad not working
** Description changed: A fresh install of 20.04 from the live USB doesn't see internal keyboard or touchpad input on my Acer Aspire E15 E5-511-POBM. After much private investigation to no avail (https://askubuntu.com/questions/1275809/ubuntu-20-04-lts-laptop- internal-keyboard-and-touchpad-no-longer-work), I am prepared to assert this as a bug. I'll restate the relevant info here, but see the link for a more chronological account. And I guess, for what it's worth, I would also assert that this is reproducible by installing 20.04 on my specific laptop model. So, I boot up the laptop. I'm presented with GRUB boot menu. At this point the keyboard works, and if I choose advanced options and boot into a root shell I can type commands and do things that way as a last resort. However, all the problems seem to begin right from the start of the graphical session, even the login screen. This, in accordance with the instruction of https://wiki.ubuntu.com/Bugs/FindRightPackage#At_the_login_screen, is why I've filed this as a bug in gdm3. As I couldn't run the graphical bug program in Ubuntu, I ran the CLI in the root shell and attached the apport file here. I've tried to follow the relevant steps, but this is my first bug report so apologies if something is wrong. I first noticed this problem a few weeks after upgrading 18.04 to 20.04. Yes, for the first few weeks of using 20.04, there were no problems. And then, one day, I booted up and the keyboard and touchpad spontaneously stopped working. This was mysterious because to my memory I hadn't done any major upgrade or change to any part of the system the previous day. When the system is asleep / suspended, pressing a key or the touchpad easily wakes it up -- after which, they refuse to work again. The brightness key combos (Fn+←/→) and one that turns off the screen (Fn+F6) do work, but others such as volume (Fn+↑/↓) do not work. I see all expected key output when I run `sudo libinput debug-events --device /dev/input/event4 --show-keycodes` and type keys. When I plug in an external USB keyboard and mouse, they work correctly while the internal keyboard and touchpad remain the same. Outside of those specific situations, absolutely no internal keyboard input -- not even Ctrl+Alt+Del or Ctrl+Alt+F2 VT switching, let alone ordinary typing -- has any effect, and same with the touchpad. When I haven't had an external keyboard available I've used the on- screen keyboard to painstakingly run terminal commands by clicking each letter. However, sometimes the on-screen keyboard also stops sending keystrokes. The only concrete situation I can report is what I saw after resuming the system from sleep by opening the lid: at the login prompt on the lock screen, the onscreen keyboard came up, but didn't do anything when keys were clicked, forcing me to reboot. I had the following message in my `journalctl -b` logs: ``` The XKEYBOARD keymap compiler (xkbcomp) reports: Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Warning: Unsupported maximum keycode 569, clipping. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > X11 cannot support keycodes above 255. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Internal error: Could not resolve keysym Invalid Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: Errors from xkbcomp are not fatal to the X server ``` This looks like it should have something to do with the keyboard issue. If it doesn't, then what is its significance? - When I investigated, I was on kernel 5.0.47. When I selected 4.15.0-112 - in the boot menu, everything was fine again; keyboard and touchpad - working. I also found everything working fine on the install USB demo. - Yet when I did a fresh reinstall of Ubuntu from the USB, the keyboard - and touchpad did not work. + When I first investigated, I was on kernel 5.0.47. When I selected + 4.15.0-112 in the boot menu, everything was fine again; keyboard and + touchpad working. I also found everything working fine on the install + USB demo. Yet when I did a fresh reinstall of Ubuntu from the USB, the + keyboard and touchpad did not work. This was now kernel 5.4.0-54. + + Fortunately, switching down to 5.4.0-42 fixes my keyboard and touchpad + problems, but I've no idea how long this will last (whether the problem + is intermittent or can be relied upon to stay this way). Also, this was + after my reinstall -- I did try this kernel on my previous install, and + back then it only fixed the keyboard without the touchpad! + + After installing lightdm alongside gdm, I see that lightdm actually sees + my touchpad on 5.4.0-54, but still not my keyboard. How can it be OK in the Live USB Demo but not the OS it installs? And - why did switching down to that old kernel version fix my problem if the - problems only happened in the GUI and
Re: [Bug 1907904] Re: gnome-shell 20.10 crashes with Wayland
Hello ! No crash in /var/crash For Whoopsie, I found several links in the page https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4 Thanks. Merry Christmas. -- Jean-Paul Le 15/12/2020 à 04:34, Daniel van Vugt a écrit : > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. > > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a security > risk for yourself. > > ** Tags added: groovy > > ** Changed in: gnome-shell (Ubuntu) > Status: New => Incomplete > -- 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/1907904 Title: gnome-shell 20.10 crashes with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1907904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1908801] Re: Acer laptop internal keyboard & touchpad not working
** Description changed: A fresh install of 20.04 from the live USB doesn't see internal keyboard or touchpad input on my Acer Aspire E15 E5-511-POBM. After much private investigation to no avail (https://askubuntu.com/questions/1275809/ubuntu-20-04-lts-laptop- internal-keyboard-and-touchpad-no-longer-work), I am prepared to assert this as a bug. I'll restate the relevant info here, but see the link for a more chronological account. And I guess, for what it's worth, I would also assert that this is reproducible by installing 20.04 on my specific laptop model. So, I boot up the laptop. I'm presented with GRUB boot menu. At this point the keyboard works, and if I choose advanced options and boot into a root shell I can type commands and do things that way as a last resort. However, all the problems seem to begin right from the start of the graphical session, even the login screen. This, in accordance with the instruction of https://wiki.ubuntu.com/Bugs/FindRightPackage#At_the_login_screen, is why I've filed this as a bug in gdm3. As I couldn't run the graphical bug program in Ubuntu, I ran the CLI in the root shell and attached the apport file here. I've tried to follow the relevant steps, but this is my first bug report so apologies if something is wrong. I first noticed this problem a few weeks after upgrading 18.04 to 20.04. Yes, for the first few weeks of using 20.04, there were no problems. And then, one day, I booted up and the keyboard and touchpad spontaneously stopped working. This was mysterious because to my memory I hadn't done any major upgrade or change to any part of the system the previous day. When the system is asleep / suspended, pressing a key or the touchpad easily wakes it up -- after which, they refuse to work again. The brightness key combos (Fn+←/→) and one that turns off the screen (Fn+F6) do work, but others such as volume (Fn+↑/↓) do not work. I see all expected key output when I run `sudo libinput debug-events --device /dev/input/event4 --show-keycodes` and type keys. When I plug in an external USB keyboard and mouse, they work correctly while the internal keyboard and touchpad remain the same. Outside of those specific situations, absolutely no internal keyboard input -- not even Ctrl+Alt+Del or Ctrl+Alt+F2 VT switching, let alone ordinary typing -- has any effect, and same with the touchpad. When I haven't had an external keyboard available I've used the on- screen keyboard to painstakingly run terminal commands by clicking each letter. However, sometimes the on-screen keyboard also stops sending keystrokes. The only concrete situation I can report is what I saw after resuming the system from sleep by opening the lid: at the login prompt on the lock screen, the onscreen keyboard came up, but didn't do anything when keys were clicked, forcing me to reboot. I had the following message in my `journalctl -b` logs: ``` The XKEYBOARD keymap compiler (xkbcomp) reports: Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Warning: Unsupported maximum keycode 569, clipping. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > X11 cannot support keycodes above 255. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Internal error: Could not resolve keysym Invalid Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: Errors from xkbcomp are not fatal to the X server ``` This looks like it should have something to do with the keyboard issue. If it doesn't, then what is its significance? When I investigated, I was on kernel 5.0.47. When I selected 4.15.0-112 in the boot menu, everything was fine again; keyboard and touchpad working. I also found everything working fine on the install USB demo. Yet when I did a fresh reinstall of Ubuntu from the USB, the keyboard and touchpad did not work. How can it be OK in the Live USB Demo but not the OS it installs? And why did switching down to that old kernel version fix my problem if the problems only happened in the GUI and not the root console? What on earth is the connection between the kernel and GNOME's input handling ... on top of an apparently working libinput?? Ideally I'd want to know the different stages in the lifecycle of a keystroke (post-libinput) and to find out at which stage the key event is getting discarded. I literally went digging through the source code of various GNOME packages and programs, xkb tools, etc. I got as far as vaguely learning about Mutter or Clutter or something before deciding I had better things to do with my evenings. I am lost and I need someone who knows more about this. One person on Ask Ubuntu gave some pessimistic sympathy, describing the issue as "just a thing we have to live with" on this particular laptop model. This is unacceptable, and I am able and willing to spend more
[Bug 1909220] [NEW] gnome-screensaver-command -l crash
Public bug reported: After migration on 20.04, "gnome-screensaver-command -l" is not working. On my test, "nome-screensaver-command -a" is working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver 3.6.1-11ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 24 12:25:50 2020 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 0 InstallationDate: Installed on 2020-09-05 (110 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1909220 Title: gnome-screensaver-command -l crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1909220/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
