[Desktop-packages] [Bug 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
@Daniel, I installed deb package for "performance" fix, you have written in #22. But since 18th November freeze did not appear anymore. If it does I will try to collect info from #22. @Vinod, did you try to install deb package from bug 1849142 from #14. Download deb file and execute from termina: sudo dpkg -i If freeze reappears can you please collect info requested in #22 of this thread. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898910] Re: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from Des
Also note: Comment #7 is bug 1898005, not this one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898910 Title: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed() Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 --- Ubuntu on Wayland crashes when you try to change the resolution even if your display supports the Version: 3.38.0-1ubuntu2 Release: 20.10 Groovy Gorilla (development branch) What I expected to happen 1. Login to Wayland 2. Change the resolution 3. Go on with my day What actually happened 1. Login to Wayland 2. Change the resolution 3. Wait a minute to get kicked to the gdm login screen 4. Now I am here. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 7 12:55:35 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-10-07 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
Thanks. That shows you still have the Ubuntu Dock enabled. Please disable it in the Extensions app and then tell us if this bug still occurs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
I'm going to sleep. Thank you again. ** Attachment added: "shellsettings40.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+attachment/5437373/+files/shellsettings40.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
OK, thanks. I forgot something... Now that you only have Ubuntu extensions installed please start disabling those via the Extensions app. Log out and in again afterwards to be sure. Then when you're using gnome-shell without any extensions does the bug still occur? If so then please run: gsettings list-recursively org.gnome.shell > shellsettings40.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
OK, thanks. If you log out and in again now and the problem still occurs then I think we're done. At least in confirming the correct project is 'gnome-shell'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
** Attachment added: "packages.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+attachment/5437369/+files/packages.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
Ok, sorry. ** Attachment added: "localext34.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+attachment/5437367/+files/localext34.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
Please also run: dpkg -l | grep gnome-shell > packages.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
I'm not convinced you have a clean setup yet. Please don't install Dash to Dock, or any extensions, while working on this bug. Please delete it all again: cd ~/.local/share/gnome-shell rm -rf extensions and then log out and in again. Do not install any extensions. Now does the bug still occur after you have logged out and in again? If it does then please run: ls ~/.local/share/gnome-shell/extensions/ >& localext34.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
The impression I have is: maybe some extension (possibly hide top bar) or configuration changed something more intrinsic to the system, which was preserved even after the reset etc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
Okay. The same problem with the flashing dock happened in all cases. Before I reinstalled "Dash to Dock", I managed to reproduce the problem as in the video above. Then, I installed the aforementioned extension (I disabled the Ubuntu dock previously to avoid conflicts) and tested both Dash to Dock on my own and Ubuntu Dock. Both had the same problem. Attached is the information requested. ** Attachment added: "localext29.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+attachment/5437366/+files/localext29.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
** Attachment added: "VID_20201124_022429636.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+attachment/5437365/+files/VID_20201124_022429636.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
The extensions folder no longer exists... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
There, I executed the commands. The "extensions" folder disappears afterwards, right? When installing the dash to dock, to avoid conflict between the docks, what would be the appropriate procedure? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
Your shellsettings/gsettings actually are not a problem anymore. The last problem I can see is that you have local extensions installed in your home directory, which is not part of your "settings". Please wipe them by running: cd ~/.local/share/gnome-shell rm -rf extensions and then log out and in again. Does the bug still happen? If so then please run: ls ~/.local/share/gnome-shell/extensions/ > localext29.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
Okay, I've made significant progress. With the reset I was able to remove the traces from the extensions. I will resend the new "shellsettings22.txt". I add that I found on the internet something similar to the problem I have: https://github.com/micheleg/dash-to-dock/issues/298 The difference is that my problem persists in different programs (firefox, evince)... ** Bug watch added: github.com/micheleg/dash-to-dock/issues #298 https://github.com/micheleg/dash-to-dock/issues/298 ** Attachment added: "shellsettings22.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+attachment/5437356/+files/shellsettings22.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
The attachment in comment #25 shows you still have local extensions installed. Please wipe them by running: cd ~/.local/share/gnome-shell rm -rf extensions and then log out and in again. Does the bug still happen? If for any reason you want to reset ALL your settings to the "factory defaults" then the easiest way to do that is: dconf reset -f / That will reset all your settings, but it won't affect your personal files. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
I uninstalled all extensions. They don't appear anywhere: "tweak tools"; "gnome extensions" website or "extensions". I tried to find the extension files inside ".local> share> gnome-shell> extensions" and I didn't find anything either, even with the function to see hidden files... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
Is there any way to reset gnome? I have no idea what's going on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
** Attachment added: "local22.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+attachment/5437349/+files/local22.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
** Attachment added: "shellsettings22.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+attachment/5437348/+files/shellsettings22.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905287] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1905287 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905287 Title: Phantom mouse wheel events without user input Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Bug description: This doesn't occur with Firefox. But it occurs with Chrome AND gnome- terminal. What happens is that if I have more than one tab in focus, it moves to the last tabs by itself. Here is a screen capture of what happens. I am running ubuntu 18.04.5 LTS, i have never had this issue before. Issue started happening since yesterday. This morning I applied my updates hoping that this will fix it, but even then nothing happened. I have known this to happen in another older laptop running an older version of ubuntu as well. journalctl -f gives me ths following: ``` Nov 23 15:28:36 xxxmymachinenamexxx gnome-shell[4051]: pushModal: invocation of begin_modal failed ``` Note that this error entry from the journalctl does not always appear when the tabs cycle through like in the video, might be unrelated. My graphics card is: lspci |grep VGA ``` 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) ``` I thought initially it might be some key that is being pressed, so i ran screenkey when this happens, there was no key appearing, so it does not seem that this is a key being pressed. I tail -f /var/log/syslog and /var/log/Xorg.0.log when i click on the tabs and it does this weirdness, nothing happens. So i don't have much information to give on this issue. Please get in touch with me if you want any information. I cannot push all my logs since it is a professional laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1905287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905270] Re: On any external monitors, wayland session has a white block on most part of the screen.
Please try logging into 'Ubuntu' instead of 'Ubuntu on Wayland' and tell us if that has the same issue. Please also then run: lspci -kv > lspci.txt xrandr --verbose > xrandr.txt journalctl -b0 > journal.txt and attach the resulting text files here. ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905270 Title: On any external monitors, wayland session has a white block on most part of the screen. Status in Mutter: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: on any external monitors, wayland session has a white block on most part of the screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mutter 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 20:16:15 2020 InstallationDate: Installed on 2020-09-16 (67 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1905270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1905270] Re: wayland external monitor display issue
It seems that wayland is incompatible with the amdgpu renoir integrated gpu. On Tue, Nov 24, 2020, 11:08 v f wrote: > Through hdmi port or usb c port. I don't use displaylink. > > On Tue, Nov 24, 2020, 11:05 Daniel van Vugt <1905...@bugs.launchpad.net> > wrote: > >> When you say "external monitors" do you mean via a DisplayLink adapter? >> >> ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1543 >>https://gitlab.gnome.org/GNOME/mutter/-/issues/1543 >> >> ** Also affects: mutter via >>https://gitlab.gnome.org/GNOME/mutter/-/issues/1543 >>Importance: Unknown >>Status: Unknown >> >> ** Summary changed: >> >> - wayland external monitor display issue >> + On any external monitors, wayland session has a white block on most >> part of the screen. >> >> ** Tags added: multimonitor >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1905270 >> >> Title: >> On any external monitors, wayland session has a white block on most >> part of the screen. >> >> Status in Mutter: >> Unknown >> Status in mutter package in Ubuntu: >> New >> >> Bug description: >> on any external monitors, wayland session has a white block on most >> part of the screen. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 20.10 >> Package: mutter 3.38.1-1ubuntu1 >> ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 >> Uname: Linux 5.8.0-29-generic x86_64 >> ApportVersion: 2.20.11-0ubuntu50.1 >> Architecture: amd64 >> CasperMD5CheckResult: skip >> CurrentDesktop: ubuntu:GNOME >> Date: Mon Nov 23 20:16:15 2020 >> InstallationDate: Installed on 2020-09-16 (67 days ago) >> InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 >> (20200910) >> SourcePackage: mutter >> UpgradeStatus: No upgrade log present (probably fresh install) >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/mutter/+bug/1905270/+subscriptions >> > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905270 Title: On any external monitors, wayland session has a white block on most part of the screen. Status in Mutter: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: on any external monitors, wayland session has a white block on most part of the screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mutter 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 20:16:15 2020 InstallationDate: Installed on 2020-09-16 (67 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1905270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1905270] Re: wayland external monitor display issue
Through hdmi port or usb c port. I don't use displaylink. On Tue, Nov 24, 2020, 11:05 Daniel van Vugt <1905...@bugs.launchpad.net> wrote: > When you say "external monitors" do you mean via a DisplayLink adapter? > > ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1543 >https://gitlab.gnome.org/GNOME/mutter/-/issues/1543 > > ** Also affects: mutter via >https://gitlab.gnome.org/GNOME/mutter/-/issues/1543 >Importance: Unknown >Status: Unknown > > ** Summary changed: > > - wayland external monitor display issue > + On any external monitors, wayland session has a white block on most part > of the screen. > > ** Tags added: multimonitor > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1905270 > > Title: > On any external monitors, wayland session has a white block on most > part of the screen. > > Status in Mutter: > Unknown > Status in mutter package in Ubuntu: > New > > Bug description: > on any external monitors, wayland session has a white block on most > part of the screen. > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: mutter 3.38.1-1ubuntu1 > ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 > Uname: Linux 5.8.0-29-generic x86_64 > ApportVersion: 2.20.11-0ubuntu50.1 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Mon Nov 23 20:16:15 2020 > InstallationDate: Installed on 2020-09-16 (67 days ago) > InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) > SourcePackage: mutter > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mutter/+bug/1905270/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905270 Title: On any external monitors, wayland session has a white block on most part of the screen. Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: on any external monitors, wayland session has a white block on most part of the screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mutter 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 20:16:15 2020 InstallationDate: Installed on 2020-09-16 (67 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1905270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905287] Re: chrome and gnome-terminal tabs moves to the last by itself
It sounds like you have a peripheral that's generating unwanted mouse wheel events. If the problem is still happening then please run 'xev' in a Terminal window and move the mouse pointer over the little white window. Now do you see new events being logged in the Terminal window? ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Summary changed: - chrome and gnome-terminal tabs moves to the last by itself + Phantom mouse wheel events without user input -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905287 Title: Phantom mouse wheel events without user input Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: This doesn't occur with Firefox. But it occurs with Chrome AND gnome- terminal. What happens is that if I have more than one tab in focus, it moves to the last tabs by itself. Here is a screen capture of what happens. I am running ubuntu 18.04.5 LTS, i have never had this issue before. Issue started happening since yesterday. This morning I applied my updates hoping that this will fix it, but even then nothing happened. I have known this to happen in another older laptop running an older version of ubuntu as well. journalctl -f gives me ths following: ``` Nov 23 15:28:36 xxxmymachinenamexxx gnome-shell[4051]: pushModal: invocation of begin_modal failed ``` Note that this error entry from the journalctl does not always appear when the tabs cycle through like in the video, might be unrelated. My graphics card is: lspci |grep VGA ``` 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) ``` I thought initially it might be some key that is being pressed, so i ran screenkey when this happens, there was no key appearing, so it does not seem that this is a key being pressed. I tail -f /var/log/syslog and /var/log/Xorg.0.log when i click on the tabs and it does this weirdness, nothing happens. So i don't have much information to give on this issue. Please get in touch with me if you want any information. I cannot push all my logs since it is a professional laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1905287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905270] Re: wayland external monitor display issue
When you say "external monitors" do you mean via a DisplayLink adapter? ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1543 https://gitlab.gnome.org/GNOME/mutter/-/issues/1543 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1543 Importance: Unknown Status: Unknown ** Summary changed: - wayland external monitor display issue + On any external monitors, wayland session has a white block on most part of the screen. ** Tags added: multimonitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905270 Title: On any external monitors, wayland session has a white block on most part of the screen. Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: on any external monitors, wayland session has a white block on most part of the screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mutter 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 20:16:15 2020 InstallationDate: Installed on 2020-09-16 (67 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1905270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905287] Re: chrome and gnome-terminal tabs moves to the last by itself
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905287 Title: Phantom mouse wheel events without user input Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: This doesn't occur with Firefox. But it occurs with Chrome AND gnome- terminal. What happens is that if I have more than one tab in focus, it moves to the last tabs by itself. Here is a screen capture of what happens. I am running ubuntu 18.04.5 LTS, i have never had this issue before. Issue started happening since yesterday. This morning I applied my updates hoping that this will fix it, but even then nothing happened. I have known this to happen in another older laptop running an older version of ubuntu as well. journalctl -f gives me ths following: ``` Nov 23 15:28:36 xxxmymachinenamexxx gnome-shell[4051]: pushModal: invocation of begin_modal failed ``` Note that this error entry from the journalctl does not always appear when the tabs cycle through like in the video, might be unrelated. My graphics card is: lspci |grep VGA ``` 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) ``` I thought initially it might be some key that is being pressed, so i ran screenkey when this happens, there was no key appearing, so it does not seem that this is a key being pressed. I tail -f /var/log/syslog and /var/log/Xorg.0.log when i click on the tabs and it does this weirdness, nothing happens. So i don't have much information to give on this issue. Please get in touch with me if you want any information. I cannot push all my logs since it is a professional laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1905287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
OK, I want to be completely sure the extensions have been cleaned out. Please now run: gsettings list-recursively org.gnome.shell > shellsettings22.txt ls ~/.local/share/gnome-shell/ > local22.txt and attach the resulting text files. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905142] Re: When entering sleep mode the monitors turn off then immediately turn back on
OK, let's make this bug about sleep mode not working. Not about the window placement. ** Summary changed: - When vblank is send the monitors turn off then immediatly turn back on + When entering sleep mode the monitors turn off then immediately turn back on ** Description changed: every time that happens the following message is shown in syslog: /usr/libexec/gdm-x-session[3330]: (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter - - Also, the monitors turn on one by one which means that all windows are - moved to the one that turns on first. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17 Uname: Linux 5.8.0-30-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 BootLog: - + CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 21 18:38:27 2020 DistUpgraded: 2020-11-18 01:07:32,653 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) -Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1458:2316] + Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) + Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1458:2316] MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming ProcEnviron: - LANGUAGE=en_IE:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_IE.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_IE:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IE.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-30-generic root=UUID=556540f5-c271-4a31-8207-81a7fcaac401 ro amdgpu.dc=1 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-11-18 (3 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50a dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: - # set this to 0 to disable apport, or to 1 to enable it - # you can temporarily override this with - # sudo service apport start force_start=1 - enabled=0 + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 mtime.conffile..etc.default.apport: 2016-03-16T23:17:19.931496 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 17 23:04:32 2020 xserver.configfile: default xserver.errors: - open /dev/dri/card0: No such file or directory - open /dev/dri/card0: No such file or directory - Screen 0 deleted because of no matching config section. + open /dev/dri/card0: No such file or directory + open /dev/dri/card0: No such file or directory + Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - + xserver.version: 2:1.20.8-2ubuntu2.4 ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in
[Desktop-packages] [Bug 1905142] Re: When entering sleep mode the monitors turn off then immediately turn back on
If you choose 'Ubuntu on Wayland' on the login screen does the problem still occur? ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1905142 Title: When entering sleep mode the monitors turn off then immediately turn back on Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: every time that happens the following message is shown in syslog: /usr/libexec/gdm-x-session[3330]: (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17 Uname: Linux 5.8.0-30-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 21 18:38:27 2020 DistUpgraded: 2020-11-18 01:07:32,653 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1458:2316] MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-30-generic root=UUID=556540f5-c271-4a31-8207-81a7fcaac401 ro amdgpu.dc=1 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-11-18 (3 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50a dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-03-16T23:17:19.931496 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 17 23:04:32 2020 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1905142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905158] Re: special characters ctrl+shift+u not allowed in login form
The login GUI is gnome-shell, not gdm3. gdm3 is just its parent/manager. ** Tags added: focal ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905158 Title: special characters ctrl+shift+u not allowed in login form Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 20.04.1 64 bit login form doesn't allow use ctrl+shift+u to insert special characters in password field. Account manager allows to do it. Installer from 18.04 and login form 18.04 allow to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904777] Re: Xorg randomly crashes under xrdp
>From what I remember it's not uncommon for bug 1861609 to not leave a trace. :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1904777 Title: Xorg randomly crashes under xrdp Status in xorg-server package in Ubuntu: Incomplete Bug description: I'm using xrdp to log into a remote machine. Since upgrading it to 20.04, my sessions started failing randomly. They would either not start at all, or get interrupted hours later. Here's a backtrace I found in a .xorgxrdp.log [ 92697.914] rdpkeybChangeKeyboardControl: autoRepeat off [ 92697.915] rdpInDeferredRepeatCallback: [ 92697.916] rdpkeybChangeKeyboardControl: [ 92697.916] rdpkeybChangeKeyboardControl: autoRepeat off [ 92712.569] (EE) [ 92712.586] (EE) Backtrace: [ 92712.601] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5559b013811c] [ 92712.605] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7ffa5424f41f] [ 92712.608] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7ffa5408c18b] [ 92712.611] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7ffa5406b859] [ 92712.612] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 92712.612] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7ffa5406b71a] [ 92712.614] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7ffa5407cf36] [ 92712.615] (EE) 6: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc15) [0x5559b0103095] [ 92712.615] (EE) 7: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa2) [0x5559b01046e2] [ 92712.616] (EE) 8: /usr/lib/xorg/Xorg (DRI2GetParam+0x944) [0x5559b0105aa4] [ 92712.616] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5559affd6f34] [ 92712.617] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5559affdafc4] [ 92712.617] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7ffa5406d0b3] [ 92712.618] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x5559affc4a2e] [ 92712.621] (EE) [ 92712.621] (EE) Fatal server error: [ 92712.621] (EE) Caught signal 6 (Aborted). Server aborting [ 92712.621] (EE) [ 92712.623] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 92712.623] (EE) Please also check the log file at ".xorgxrdp.16.log" for additional information. [ 92712.623] (EE) [ 92712.627] rdpmouseControl: what 4 [ 92712.627] rdpkeybControl: what 4 [ 92712.629] rdpLeaveVT: [ 92712.634] (EE) Server terminated with error (1). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.4 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 18 20:07:37 2020 DistUpgraded: 2020-11-10 20:20:36,496 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company ProLiant MicroServer N36L [103c:1609] MachineType: HP ProLiant MicroServer ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=62bd3629-e229-4962-b11f-695a62533e9d ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to focal on 2020-11-10 (7 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 07/29/2011 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd07/29/2011:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.product.sku: 664447-425 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1904939] Re: Monitor Settings Don't Get Applied in Wayland
OK, thanks. It looks like the problem is in gnome-shell: JS ERROR: TypeError: this.actor is null vfunc_set_actor/this._monitorsChangedId<@resource:///org/gnome/shell/ui/layout.js:103:25 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:548:14 _onFailure@resource:///org/gnome/shell/ui/windowManager.js:107:18 ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Monitor Settings Don't Get Applied in Wayland + Monitor Settings Don't Get Applied in Wayland [JS ERROR: TypeError: this.actor is null -- vfunc_set_actor/this._monitorsChangedId<@resource:///org/gnome/shell/ui/layout.js:103:25] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1904939 Title: Monitor Settings Don't Get Applied in Wayland [JS ERROR: TypeError: this.actor is null -- vfunc_set_actor/this._monitorsChangedId<@resource:///org/gnome/shell/ui/layout.js:103:25] Status in gnome-control-center package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: When configuring a 1080p monitor and a 4k monitor in extended screen mode while using Wayland, when trying to change the screen positions or which screen is the primary screen in the Monitor Settings, the settings reset to default when Apply is clicked. Choosing to "Revert the Settings" during the 15-second timer causes it to apply the changed settings, but this resets whenever a pop-up message appears or when returning to the Monitor Settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 16:47:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:08ac] Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac] InstallationDate: Installed on 2020-11-18 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Precision 5530 2-in-1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.10 dmi.board.name: 02TH5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 2-in-1 dmi.product.sku: 08AC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1904939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1303316] Re: Digital S/PDIF output is not present in 5.1 mode
** Tags removed: trusty ** Tags added: groovy ** Tags removed: precise ** Changed in: pulseaudio (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1303316 Title: Digital S/PDIF output is not present in 5.1 mode Status in pulseaudio package in Ubuntu: New Bug description: I have the sound connected through digital S / PDIF Sound works properly selecting stereo, but can not get it to work using 5.1 When I select stereo sound, appears on the tab below to phonon spdif output option. When I select Output 5.1, that option does not appear. I imagine the error will also occur selecting 7.1 Deputy screenshots. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: phonon 4:4.7.0really4.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Apr 6 13:12:42 2014 InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: phonon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Coiby Xu (coiby) Yes, that summarizes my findings nicely. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO ---
[Desktop-packages] [Bug 1905346] [NEW] USB devices, Headphones drives. And others like webcam not detected, as well as failing to powerdown
Public bug reported: https://askubuntu.com/questions/1294526/unbunti-20-04-01-kernal-5-4-0-54 -generic-amd-3700-u-issue-of-not-shutting-down-a this is explanation of main issue, I feel the usb headphones and drives not being detected is a symptom. Also webcam is not detected as well, and sound won't work at all sometimes. Meaning that it is started off random and rebooting would fix, but over last month the problem has gotten worse to happen multiple times a day. to where the problem is not more normal state. booting into recovery mode seems to do nothing. it's not hardware as windows 10 is dual booted on my machine (asus zenbook um433d ryzen 7 3700U AMD) works fine, I've reinstalled ubuntu which first install had similar problems everything is fine first month then problems start happening. It happened similarly here. running usb version to test older version of unbuntu like 20.10 and 18.04 off usb stick sound and web cam work. However not sure if this indicative of initial problem or not. But computer will not come out of suspend in any version. The problem is getting worse and I haven't found any real solution other than upgrade the kernal because, or try a different distro. Please help and let me know if I can provide additional data to aid in this problem. My background is in Science, IT, and now entering web development. Thank you, Topher Judd gnrforl...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: topher 2392 F pulseaudio /dev/snd/controlC0: topher 2392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 09:00:55 2020 InstallationDate: Installed on 2020-10-03 (51 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434DA_UM433DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434DA_UM433DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1905346 Title: USB devices, Headphones drives. And others like webcam not detected, as well as failing to powerdown Status in alsa-driver package in Ubuntu: New Bug description: https://askubuntu.com/questions/1294526/unbunti-20-04-01-kernal-5-4-0-54 -generic-amd-3700-u-issue-of-not-shutting-down-a this is explanation of main issue, I feel the usb headphones and drives not being detected is a symptom. Also webcam is not detected as well, and sound won't work at all sometimes. Meaning that it is started off random and rebooting would fix, but over last month the problem has gotten worse to happen multiple times a day. to where the problem is not more normal state. booting into recovery mode seems to do nothing. it's not hardware as windows 10 is dual booted on my machine (asus zenbook um433d ryzen 7 3700U AMD) works fine, I've reinstalled ubuntu which first install had similar problems everything is fine first month then problems start happening. It happened similarly here. running usb version to test older version of unbuntu like 20.10 and 18.04 off usb stick sound and web cam work. However not sure if this indicative of initial problem or not. But computer will not come out of suspend in any version. The problem is getting worse and I haven't found any real solution other than upgrade the kernal because, or try a different distro. Please help and let me know if I can provide additional data to aid in this problem. My background is in Science, IT, and now entering web development. Thank you, Topher Judd gnrforl...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion:
[Desktop-packages] [Bug 1905330] Re: Backport Wayland frame callback fix for 3.28 for Firefox testing infrastructure
I don't have authority to target bionic immediately, but I have requested authorization for a bionic fix. ** Tags added: bionic ** Tags added: fixed-in-3.35.1 fixed-upstream ** Also affects: mutter (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Focal) Status: New => Fix Released ** Changed in: mutter (Ubuntu Groovy) Status: New => Fix Released ** Changed in: mutter (Ubuntu Hirsute) Status: New => Fix Released ** Tags added: rls-bb-incoming ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #457 https://gitlab.gnome.org/GNOME/mutter/-/issues/457 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/457 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905330 Title: Backport Wayland frame callback fix for 3.28 for Firefox testing infrastructure Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Released Status in mutter source package in Hirsute: Fix Released Bug description: The Firefox testing infrastructure is based on Ubuntu 18.04. In order to enable the Wayland backend by default, we need to also run test on that. There is one particular bug in Mutter 3.28 that I'd like to see fixed for that, thus requesting a backport of a patch. It's already in the upstream repo, but as 3.28 is not supported upstream any more, I request it here explicitly: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1570 @vanvugt @3v1n0 this would be super helpful for us, I hope I can convince you about that, even if Ubuntu 18.04 doesn't support Wayland officially. It can be tested by running Firefox with `MOZ_ENABLE_WAYLAND=1` and setting `widget.wayland_vsync.enabled:1` in the config (soon to be enabled by default). If, after launching Firefox again, everything works as expected - well, then it works. Bonus: the patch also affects a number of other Wayland applications, so some users might be happy to see it as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1905330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905344] [NEW] [snap] thunderbird seccomp profile missing a few syscalls
Public bug reported: Launching thunderbird's snap result in the following logs: Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 audit(1606180057.636:655): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5 Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 audit(1606180057.640:656): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5 Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 audit(1606180057.640:657): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5 Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 audit(1606180057.640:658): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5 Nov 23 20:07:38 simon-lemur kernel: audit: type=1326 audit(1606180058.356:659): auid=1000 uid=1000 gid=1000 ses=2 pid=8512 comm=64636F6E6620776F726B6572 exe="/snap/thunderbird/95/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7f19894aa959 code=0x5 $ aa-decode 64636F6E6620776F726B6572 Decoded: dconf worker So syscall 203 (sys_sched_setaffinity?) and 314 (sys_sched_setattr?) are not permitted. Additional information: $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ uname -a Linux simon-lemur 5.4.0-53-generic #59~18.04.1-Ubuntu SMP Wed Oct 21 12:14:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ snap info thunderbird name: thunderbird summary: Mozilla Thunderbird email application publisher: Canonical✓ store-url: https://snapcraft.io/thunderbird contact: https://launchpad.net/distros/ubuntu/+source/thunderbird license: unset description: | Thunderbird is a free and open source email, newsfeed, chat, and calendaring client, that’s easy to set up and customize. One of the core principles of Thunderbird is the use and promotion of open standards - this focus is a rejection of our world of closed platforms and services that can’t communicate with each other. We want our users to have freedom and choice in how they communicate. commands: - thunderbird snap-id: k1Ml1O9GzSO2QftV0ZlWSbUfQ78nN460 tracking: latest/stable refresh-date: today at 20:00 EST channels: latest/stable:78.5.0 2020-11-18 (95) 69MB - latest/candidate: ↑ latest/beta: ↑ latest/edge: 78.5.0 2020-11-18 (95) 69MB - installed: 78.5.0(95) 69MB - ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1905344 Title: [snap] thunderbird seccomp profile missing a few syscalls Status in thunderbird package in Ubuntu: New Bug description: Launching thunderbird's snap result in the following logs: Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 audit(1606180057.636:655): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5 Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 audit(1606180057.640:656): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5 Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 audit(1606180057.640:657): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5 Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 audit(1606180057.640:658): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5 Nov 23 20:07:38 simon-lemur kernel: audit: type=1326 audit(1606180058.356:659): auid=1000 uid=1000 gid=1000 ses=2 pid=8512 comm=64636F6E6620776F726B6572 exe="/snap/thunderbird/95/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7f19894aa959 code=0x5 $ aa-decode 64636F6E6620776F726B6572 Decoded: dconf worker So syscall 203 (sys_sched_setaffinity?) and 314 (sys_sched_setattr?) are not permitted. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 $ uname -a Linux simon-lemur 5.4.0-53-generic #59~18.04.1-Ubuntu SMP Wed Oct 21 12:14:56
[Desktop-packages] [Bug 1905337] [NEW] Scaling of Firefox doesn't adjust when moved across Monitors with Different DPis
Public bug reported: Firefox doesn't automatically scale up/down when dragged across screens with different DPis like other apps and keeps the Scaling of the monitor it was opened on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick1854 F pulseaudio /dev/snd/controlC0: patrick1854 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 18:40:44 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-11-18 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.11 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=83.0/20201112153044 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.10 dmi.board.name: 02TH5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 2-in-1 dmi.product.sku: 08AC dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1905337 Title: Scaling of Firefox doesn't adjust when moved across Monitors with Different DPis Status in firefox package in Ubuntu: New Bug description: Firefox doesn't automatically scale up/down when dragged across screens with different DPis like other apps and keeps the Scaling of the monitor it was opened on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick1854 F pulseaudio /dev/snd/controlC0: patrick1854 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 18:40:44 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-11-18 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.11 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Thanks @hui.wang. Upgrading to Groovy didn't fix the issue for me with an AX200 card, but installing rtl8821ce-dkms made it work great. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901552] Re: Unrecoverable failure in required component org.gnome.Shell.desktop
*** This bug is a duplicate of bug 1775392 *** https://bugs.launchpad.net/bugs/1775392 Re-Actually , we kept getting the failure to login and the gnome crash even by restarting sssd regularly. I finally isolated my problem to be a duplicate of this bug https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392 ** Tags removed: cpe-onsite ** This bug has been marked a duplicate of bug 1775392 at-spi-bus-launcher makes Xorg crash when resuming from suspend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1901552 Title: Unrecoverable failure in required component org.gnome.Shell.desktop Status in gnome-settings-daemon package in Ubuntu: New Bug description: A Lenovo P53 is installed with ubuntu 18.04.5 LTS. Graphics Intel UHD Graphics 630 (main display), nvidia quadro RTX 5000 also installed but not used for main display. Laptop is domain joined. When logging to the local ubuntu user, there is no problem detected. Then, if we log out and try to login with a domain user, gnome crashes. From what I can see in the logs, the user is authenticated correctly, but then in the instantiation of the session, gnome.shell.desktop faces an unrecoverable failure. From auth.log ``` pam_sss(gdm-password:auth): authentication success; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=u...@na.cie.com Oct 23 16:27:28 WLLNXPFX gdm-password]: pam_unix(gdm-password:session): session opened for user u...@na.cie.com by (uid=0) Oct 23 16:27:28 WLLNXPFX systemd-logind[1200]: New session 17 of user u...@na.cie.com. ``` From syslog ``` Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: after 21 requests (21 known processed) with 0 events remaining. ``` I will include the full syslog and auth.log to this bug. Please let me know if any other log could be useful to troubleshoot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904939] Re: Monitor Settings Don't Get Applied in Wayland
Problem still occurs with Extensions disabled. ** Attachment added: "journalctlout.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1904939/+attachment/5437319/+files/journalctlout.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1904939 Title: Monitor Settings Don't Get Applied in Wayland Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When configuring a 1080p monitor and a 4k monitor in extended screen mode while using Wayland, when trying to change the screen positions or which screen is the primary screen in the Monitor Settings, the settings reset to default when Apply is clicked. Choosing to "Revert the Settings" during the 15-second timer causes it to apply the changed settings, but this resets whenever a pop-up message appears or when returning to the Monitor Settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 16:47:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:08ac] Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac] InstallationDate: Installed on 2020-11-18 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Precision 5530 2-in-1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.10 dmi.board.name: 02TH5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 2-in-1 dmi.product.sku: 08AC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1904939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
Same bug seen on Ubuntu Bionic 18.04.5 LTS with Lenovo P53. In my case, the bug seen when attempting a domain login in ubuntu. About 75% of the time, the login hangs for several minutes, then the screen turns black, and returns to the greater. Once in a while, the user is able to login. The workaround of removing the at-spi2-core package effectively stops the crashes -- but this removes also other functionalities. For example, nautilus is removed. Is there a patch available, or did anyone report the bug upstream yet ? Logs of the error : Nov 20 15:44:47 HOSTNAME gnome-session[5658]: gnome-session-binary[5658]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Nov 20 15:44:47 HOSTNAME gnome-session[5658]: gnome-session-binary[5658]: CRITICAL: We failed, but the fail whale is dead. Sorry Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: Unrecoverable failure in required component org.gnome.Shell.desktop Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: CRITICAL: We failed, but the fail whale is dead. Sorry Nov 20 15:44:47 HOSTNAME at-spi-bus-launcher[5774]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" Nov 20 15:44:47 HOSTNAME at-spi-bus-launcher[5774]: after 21 requests (21 known processed) with 0 events remaining. ** Tags added: cpe-onsite -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend Status in at-spi2-core package in Ubuntu: Confirmed Bug description: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904930] Re: USB Mouse removed and added intermittently
Hence, this issue can be closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1904930 Title: USB Mouse removed and added intermittently Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: When installing 20.04.1 on my workstation I experienced that there was some lag or stutter when using the mouse when navigating the desktop, and even more while playing a game where reliance on the mouse is quite extensive. I opened my log and saw these messages where the device was removed and added anew due to that Ubuntu diagnoses it as removed, and re-adds it again. See the log below. I also tried to reinstall with Ubuntu 20.10 which I'm now running, hoping that the issue wouldn't be present in a later release with a newer kernel and surrounding packages. But to my disappointment it unfortunately had the same flaw. This issue has never been present in Fedora 32, nor in previous versions that I've been using prior to my newfound acquaintance with Ubuntu, so it would suggest the problem is with Ubuntu and not the hardware. I have also put this issue up on askubuntu prior to posting it as a bug, but from my perspective it sure looks like it. https://askubuntu.com/questions/1286301/ubuntu-20-04-1-lts-mouse-removed-and-added-intermittently System information Description: Ubuntu 20.10 Release: 20.10 xserver-xorg-input-libinput: Installed: 0.30.0-1 Candidate: 0.30.0-1 Version table: *** 0.30.0-1 500 500 http://se.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status dmesg: [ 1088.975507] usb 2-1.6: USB disconnect, device number 8 [ 1089.257584] usb 2-1.6: new full-speed USB device number 9 using ehci-pci [ 1089.376858] usb 2-1.6: New USB device found, idVendor=046d, idProduct=c245, bcdDevice=69.00 [ 1089.376862] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1089.376873] usb 2-1.6: Product: Gaming Mouse G400 [ 1089.376874] usb 2-1.6: Manufacturer: Logitech [ 1089.378986] input: Logitech Gaming Mouse G400 as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:046D:C245.000A/input/input23 [ 1089.437806] hid-generic 0003:046D:C245.000A: input,hidraw1: USB HID v1.10 Mouse [Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input0 [ 1089.439108] hid-generic 0003:046D:C245.000B: hiddev0,hidraw2: USB HID v1.10 Device [Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input1 journalctl: kernel: usb 2-1.6: USB disconnect, device number 5 /usr/libexec/gdm-x-session[10696]: (II) config/udev: removing device Logitech Gaming Mouse G400 /usr/libexec/gdm-x-session[10696]: (**) Option "fd" "50" /usr/libexec/gdm-x-session[10696]: (II) event3 - Logitech Gaming Mouse G400: device removed /usr/libexec/gdm-x-session[10696]: (II) UnloadModule: "libinput" /usr/libexec/gdm-x-session[10696]: (II) systemd-logind: releasing fd for 13:67 kernel: usb 2-1.6: new full-speed USB device number 8 using ehci-pci kernel: usb 2-1.6: New USB device found, idVendor=046d, idProduct=c245, bcdDevice=69.00 kernel: usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 kernel: usb 2-1.6: Product: Gaming Mouse G400 kernel: usb 2-1.6: Manufacturer: Logitech kernel: input: Logitech Gaming Mouse G400 as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:046D:C245.0008/input/input22 kernel: hid-generic 0003:046D:C245.0008: input,hidraw1: USB HID v1.10 Mouse [Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input0 kernel: hid-generic 0003:046D:C245.0009: hiddev0,hidraw2: USB HID v1.10 Device [Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input1 mtp-probe[21570]: checking bus 2, device 8: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6" mtp-probe[21570]: bus: 2, device: 8 was not an MTP device /usr/libexec/gdm-x-session[10696]: (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/mouse0) /usr/libexec/gdm-x-session[10696]: (II) No input driver specified, ignoring this device. /usr/libexec/gdm-x-session[10696]: (II) This device may have been added with another device file. /usr/libexec/gdm-x-session[10696]: (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/event3) /usr/libexec/gdm-x-session[10696]: (**) Logitech Gaming Mouse G400: Applying InputClass "libinput pointer catchall" /usr/libexec/gdm-x-session[10696]: (II) Using input driver 'libinput' for 'Logitech Gaming Mouse G400' mtp-probe[21579]: checking bus 2, device 8: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6" mtp-probe[21579]: bus: 2, device: 8 was not an MTP device /usr/libexec/gdm-x-session[10696]: (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 90 paused 0 /usr/libexec/gdm-x-session[10696]: (**)
[Desktop-packages] [Bug 1904930] Re: USB Mouse removed and added intermittently
The issue seems not to be a software problem at all, and that the issue started when I installed Ubuntu over Fedora was merely a coincidence and not a problem with Ubuntu itself. How to fix the issue with Logitech G400: https://www.youtube.com/watch?v=_L9Tv65gVYA -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1904930 Title: USB Mouse removed and added intermittently Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: When installing 20.04.1 on my workstation I experienced that there was some lag or stutter when using the mouse when navigating the desktop, and even more while playing a game where reliance on the mouse is quite extensive. I opened my log and saw these messages where the device was removed and added anew due to that Ubuntu diagnoses it as removed, and re-adds it again. See the log below. I also tried to reinstall with Ubuntu 20.10 which I'm now running, hoping that the issue wouldn't be present in a later release with a newer kernel and surrounding packages. But to my disappointment it unfortunately had the same flaw. This issue has never been present in Fedora 32, nor in previous versions that I've been using prior to my newfound acquaintance with Ubuntu, so it would suggest the problem is with Ubuntu and not the hardware. I have also put this issue up on askubuntu prior to posting it as a bug, but from my perspective it sure looks like it. https://askubuntu.com/questions/1286301/ubuntu-20-04-1-lts-mouse-removed-and-added-intermittently System information Description: Ubuntu 20.10 Release: 20.10 xserver-xorg-input-libinput: Installed: 0.30.0-1 Candidate: 0.30.0-1 Version table: *** 0.30.0-1 500 500 http://se.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status dmesg: [ 1088.975507] usb 2-1.6: USB disconnect, device number 8 [ 1089.257584] usb 2-1.6: new full-speed USB device number 9 using ehci-pci [ 1089.376858] usb 2-1.6: New USB device found, idVendor=046d, idProduct=c245, bcdDevice=69.00 [ 1089.376862] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1089.376873] usb 2-1.6: Product: Gaming Mouse G400 [ 1089.376874] usb 2-1.6: Manufacturer: Logitech [ 1089.378986] input: Logitech Gaming Mouse G400 as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:046D:C245.000A/input/input23 [ 1089.437806] hid-generic 0003:046D:C245.000A: input,hidraw1: USB HID v1.10 Mouse [Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input0 [ 1089.439108] hid-generic 0003:046D:C245.000B: hiddev0,hidraw2: USB HID v1.10 Device [Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input1 journalctl: kernel: usb 2-1.6: USB disconnect, device number 5 /usr/libexec/gdm-x-session[10696]: (II) config/udev: removing device Logitech Gaming Mouse G400 /usr/libexec/gdm-x-session[10696]: (**) Option "fd" "50" /usr/libexec/gdm-x-session[10696]: (II) event3 - Logitech Gaming Mouse G400: device removed /usr/libexec/gdm-x-session[10696]: (II) UnloadModule: "libinput" /usr/libexec/gdm-x-session[10696]: (II) systemd-logind: releasing fd for 13:67 kernel: usb 2-1.6: new full-speed USB device number 8 using ehci-pci kernel: usb 2-1.6: New USB device found, idVendor=046d, idProduct=c245, bcdDevice=69.00 kernel: usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 kernel: usb 2-1.6: Product: Gaming Mouse G400 kernel: usb 2-1.6: Manufacturer: Logitech kernel: input: Logitech Gaming Mouse G400 as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:046D:C245.0008/input/input22 kernel: hid-generic 0003:046D:C245.0008: input,hidraw1: USB HID v1.10 Mouse [Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input0 kernel: hid-generic 0003:046D:C245.0009: hiddev0,hidraw2: USB HID v1.10 Device [Logitech Gaming Mouse G400] on usb-:00:1d.0-1.6/input1 mtp-probe[21570]: checking bus 2, device 8: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6" mtp-probe[21570]: bus: 2, device: 8 was not an MTP device /usr/libexec/gdm-x-session[10696]: (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/mouse0) /usr/libexec/gdm-x-session[10696]: (II) No input driver specified, ignoring this device. /usr/libexec/gdm-x-session[10696]: (II) This device may have been added with another device file. /usr/libexec/gdm-x-session[10696]: (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/event3) /usr/libexec/gdm-x-session[10696]: (**) Logitech Gaming Mouse G400: Applying InputClass "libinput pointer catchall" /usr/libexec/gdm-x-session[10696]: (II) Using input driver 'libinput' for 'Logitech Gaming Mouse G400' mtp-probe[21579]: checking bus 2, device 8:
[Desktop-packages] [Bug 1772683] Re: [snap] Cannot sign a document, gpg keys are not listed
I have the same problem: Ubuntu 20.04 LibreOffice (snap) 7.0.2.2 If I use the Appimage provided by LibreOffice (https://www.libreoffice.org/download/appimage/), version standard, fresh, the digital signing works fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1772683 Title: [snap] Cannot sign a document, gpg keys are not listed Status in LibreOffice: Won't Fix Status in libreoffice package in Ubuntu: Triaged Bug description: (initially reported on the forum: https://forum.snapcraft.io/t /libreoffice-snap-missing-features-and-known-bugs/3920/10) Libreoffice 6.0.4.2 (64, candidate channel). Steps to reproduce: 1) snap run libreoffice.writer 2) write something, then save the document (anywhere) on disk 3) Open the File menu, then Digital Signatures > Digital Signatures… 4) in the dialog, click "Sign Document…" Expected result: your GPG keys are listed Current result: no keys are listed To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
Last week I updated ubuntu from 20.04 to 18.04. Now I have Remmina freezing after inactivity and will unfreeze after a while like 3-4 minutes. Won't take any keystrokes and all icons are greyed out. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903710] Re: ubuntu freezes when using remmina
*** This bug is a duplicate of bug 1903986 *** https://bugs.launchpad.net/bugs/1903986 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: remmina (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1903710 Title: ubuntu freezes when using remmina Status in remmina package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 I have been using Remmina for whole day (actually several days without issue), but suddenly Remmina froze and I was in full screen mode. Mouse pointer was moving OK, but no click was accepted. Also musing playing in the background on Ubuntu was playing normally, so Ubuntu hasn't froze up, probably just Remmina. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 13:51:53 2020 InstallationDate: Installed on 2019-10-23 (384 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (87 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1903710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902051] Re: Remmina frozen and whole Ubuntu not responsive
*** This bug is a duplicate of bug 1903986 *** https://bugs.launchpad.net/bugs/1903986 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: remmina (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1902051 Title: Remmina frozen and whole Ubuntu not responsive Status in remmina package in Ubuntu: Confirmed Bug description: I am working with Remmina for years, but today when I was on Remote Desktop using Windows suddenly Remmina has frozen - mouse pointer disappeared and no keyboard response. In Remmina I have set (CTRL+R) to send all keyboard keystrokes to Remmina. I have had music listening in the background, so Ubuntu has not frozen. The only way I could solved the problem was to hard press laptop power button to force poweroff machine. Remmina is very important program to me, now when I am working from home. Hope there is something in log files that can be traced and fixed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 13:15:30 2020 InstallationDate: Installed on 2019-10-23 (372 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (75 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1902051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904622] Re: boto3+s3 bucket fails
Apologies for the wild goose chase, you are, expectedly, correct. I had seen the boto/S3 sections in the man page, however I never connected the dots that between the boto -> boto3 transition, the hostname of the s3 url was deprecated in favor of specifying only the bucket name. I merely transitioned my bucket URL from s3://s3.amazonaws.com/$bucket to boto3+s3://s3.amazonaws.com/$bucket , but boto3+s3://$bucket is in fact the correct syntax. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1904622 Title: boto3+s3 bucket fails Status in Duplicity: Invalid Status in duplicity package in Ubuntu: Incomplete Bug description: I have a duplicity job that runs on multiple hosts, and am now having failures on my 20.04 hosts. The syntax for the job (as I am currently testing to debug) is: duplicity --dry-run list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Using the duplicity packages from focal/main duplicity=0.8.11.1612-1 And I installed the boto packages from focal/universe python3-boto3=1.9.253-1 python3-botocore=1.14.14+repack-1 This runs into the error: Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir Traceback (innermost last): File "/usr/bin/duplicity", line 106, in with_tempdir(main) File "/usr/bin/duplicity", line 92, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 85, in __init__ self.reset_connection() File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 96, in reset_connection self.s3.meta.client.head_bucket(Bucket=self.bucket_name) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call return self._make_api_call(operation_name, kwargs) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 676, in _make_api_call raise error_class(parsed_response, operation_name) botocore.exceptions.ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I then tried the duplicity snap from the snap store, both the stable and edge builds, with the same issue: Main action: list-current duplicity 0.8.17 Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden Main action: list-current duplicity 0.8.18.dev11 Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I also tried to update the boto3/botocore packages by way of pip3: pip3 freeze | grep boto boto3==1.16.19 botocore==1.19.19 And lastly as a last ditch, I tried to pull the packages from the groovy/universe repo, bringing them to: python3-boto3 1.13.14-1 python3-botocore 1.17.22+repack-1_all I have also tried in a 20.10
[Desktop-packages] [Bug 1905100] Re: Cover art not shown for file which has a cover art
Yes, that fixed it! They regenerated! I don't know what caused the issue. Should i reply here if the next time i save files in Picard and they don't generate a thumbnail? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1905100 Title: Cover art not shown for file which has a cover art Status in nautilus package in Ubuntu: Incomplete Bug description: Hello! There is one file in my music folder for which a thumbnail is not shown by Nautilus, although it does have a cover art. Gnome Videos shows the cover art, as well as VLC media payer. I will upload the file here. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Nov 21 00:55:59 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2020-02-08 (286 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-10-23 (28 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905330] [NEW] Backport Wayland frame callback fix for 3.28 for Firefox testing infrastructure
Public bug reported: The Firefox testing infrastructure is based on Ubuntu 18.04. In order to enable the Wayland backend by default, we need to also run test on that. There is one particular bug in Mutter 3.28 that I'd like to see fixed for that, thus requesting a backport of a patch. It's already in the upstream repo, but as 3.28 is not supported upstream any more, I request it here explicitly: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1570 @vanvugt @3v1n0 this would be super helpful for us, I hope I can convince you about that, even if Ubuntu 18.04 doesn't support Wayland officially. It can be tested by running Firefox with `MOZ_ENABLE_WAYLAND=1` and setting `widget.wayland_vsync.enabled:1` in the config (soon to be enabled by default). If, after launching Firefox again, everything works as expected - well, then it works. Bonus: the patch also affects a number of other Wayland applications, so some users might be happy to see it as well. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: wayland ** Tags added: wayland ** Description changed: The Firefox testing infrastructure is based on Ubuntu 18.04. In order to - enable the Wayland backend by default, we need to enable it for the - Wayland backend first. + enable the Wayland backend by default, we need to also run test on that. There is one particular bug in Mutter 3.28 that I'd like to see fixed for that, thus requesting a backport of a patch. It's already in the upstream repo, but as 3.28 is not supported upstream any more, I request it here explicitly: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1570 @vanvugt @3v1n0 this would be super helpful for us, I hope I can convince you about that, even if Ubuntu 18.04 doesn't support Wayland officially. It can be tested by running Firefox with `MOZ_ENABLE_WAYLAND=1` and setting `widget.wayland_vsync.enabled:1` in the config (soon to be enabled by default). If, after launching Firefox again, everything works as expected - well, then it works. Bonus: the patch also affects a number of other Wayland applications, so some users might be happy to see it as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905330 Title: Backport Wayland frame callback fix for 3.28 for Firefox testing infrastructure Status in mutter package in Ubuntu: New Bug description: The Firefox testing infrastructure is based on Ubuntu 18.04. In order to enable the Wayland backend by default, we need to also run test on that. There is one particular bug in Mutter 3.28 that I'd like to see fixed for that, thus requesting a backport of a patch. It's already in the upstream repo, but as 3.28 is not supported upstream any more, I request it here explicitly: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1570 @vanvugt @3v1n0 this would be super helpful for us, I hope I can convince you about that, even if Ubuntu 18.04 doesn't support Wayland officially. It can be tested by running Firefox with `MOZ_ENABLE_WAYLAND=1` and setting `widget.wayland_vsync.enabled:1` in the config (soon to be enabled by default). If, after launching Firefox again, everything works as expected - well, then it works. Bonus: the patch also affects a number of other Wayland applications, so some users might be happy to see it as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905322] Re: LibreOffice crashes under load.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1905322 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: New Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1905322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904478] Re: [SRU] libreoffice 7.0.3 for groovy
The 7.0.3 package was built for all architectures in the libreoffice- prereleases ppa (1:7.0.3-0ubuntu0.20.10.1~lo2): https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice- prereleases This is where the autopkgtests were run as well (links to test results in the bug description). After all of the autopkgtests passed, the package was rebuilt with just the changelog changing and uploaded to a different ppa just for passing around the final build: https://launchpad.net/~hellsworth/+archive/ubuntu/lo-dummy-repo-2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1904478 Title: [SRU] libreoffice 7.0.3 for groovy Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Groovy: In Progress Bug description: [Impact] * LibreOffice 7.0.3 is in its third bugfix release of the 7.0 line: https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.3_release * Version 7.0.2 is currently released in groovy. For a list of fixed bugs compared to 7.0.2 see the list of bugs fixed in the release candidate (that's a total of 92 bugs): https://wiki.documentfoundation.org/Releases/7.0.3/RC1#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_70/1450/ * More information about the upstream QA testing can be found here: * Automated tests - https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests - https://wiki.documentfoundation.org/Development/UITests * Regression tests - https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests - https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/amd64/libr/libreoffice/20201110_032638_c4409@/log.gz * [arm64] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/arm64/libr/libreoffice/20201110_220300_5fc9e@/log.gz * [armhf] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/armhf/libr/libreoffice/20201110_083102_d4dab@/log.gz * [ppc64el] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/ppc64el/libr/libreoffice/20201110_054031_89cb8@/log.gz * [s390x] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/s390x/libr/libreoffice/20201110_020527_366f6@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 92 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1904478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905322] [NEW] LibreOffice crashes under load.
Public bug reported: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: New Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1905322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c
** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870356 Title: Can't connect to paired bluetooth devices via g-c-c Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Fix Released Bug description: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use blueman-manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-02-26 (400 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-control-center 1:3.36.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Tags: focal uec-images wayland-session third-party-packages Uname: Linux 5.4.0-20-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo utah _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1870356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904859] Re: [snap] cannot send file from Nautilus
** Changed in: nautilus-sendto (Ubuntu) Status: In Progress => Fix Committed ** Description changed: + * Impact + Nautilus->sendto fails to use the thunderbird snap command + + * Test case + On a Ubuntu default session + $ snap install thunderbird + $ nautilus + $ right click on a file and select the sendto entry + + -> thunderbird should be started with a composer dialog and the selected + attachment included + + * Regression potential + The patch removes an old hack that parsed and changed the thunderbird command, verify that thunderbird is still correctly start using it from different source (snap, deb, flatpak?) + + - + + TB 78.5.0 snap Focal Nothing happens when I right-click on a file (using Nautilus) from my home and choose 'send to'. I did not have such a problem using TB deb. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-sendto in Ubuntu. https://bugs.launchpad.net/bugs/1904859 Title: [snap] cannot send file from Nautilus Status in nautilus-sendto package in Ubuntu: Fix Committed Bug description: * Impact Nautilus->sendto fails to use the thunderbird snap command * Test case On a Ubuntu default session $ snap install thunderbird $ nautilus $ right click on a file and select the sendto entry -> thunderbird should be started with a composer dialog and the selected attachment included * Regression potential The patch removes an old hack that parsed and changed the thunderbird command, verify that thunderbird is still correctly start using it from different source (snap, deb, flatpak?) - TB 78.5.0 snap Focal Nothing happens when I right-click on a file (using Nautilus) from my home and choose 'send to'. I did not have such a problem using TB deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/1904859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905136] Re: libreoffice doesn't decrypt my gpg encrypted files
I use the build-in function "Save as..." -> "Encrypt with GPG key" to encrypt the file. But after saving I can't open the file anymore. As i am curious I tried to open the file with libreoffice on Windows (after setting up gpg :-) and it works fine. So I draw the conclusion that decryption might be broken in the ubuntu-package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1905136 Title: libreoffice doesn't decrypt my gpg encrypted files Status in libreoffice package in Ubuntu: Incomplete Bug description: - Encrypting files with gpg key works - Decrypting does not work, as libreoffice asks for the password but always prompts "wrong password" (Decrypting the file with libreoffice on Windows does work, so I guess the setup of gpg and the password is correct) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-calc 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Nov 21 17:09:27 2020 InstallationDate: Installed on 2020-08-11 (102 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1905136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804359] Re: tutorial doesn't work
I'm no longer sure h brings up the tutorial after installing common-non-dfsg. The first lines displayed after pressing h in info are: Next: Help, Up: Getting Started 1.1 Starting Info on a Small Screen === Since your terminal has a relatively small number of lines on its ... While this book https://tldp.org/LDP/intro-linux/html/sect_02_03.html says the tutorial starts with: File: info.info, Node: Top, Next: Getting Started, Up: (dir) Info: An Introduction * Info is a program, which you are using now, for reading ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1804359 Title: tutorial doesn't work Status in texinfo package in Ubuntu: Confirmed Bug description: Running `info` and pressing `h` doesn't bring up promised tutorial: ---cut--- File: dir, Node: Top, This is the top of the INFO tree. This is the Info main menu (aka directory node). A few useful Info commands: 'q' quits; 'H' lists all Info commands; 'h' starts the Info tutorial; 'mTexinfo RET' visits the Texinfo manual, etc. ---cut--- The error message displayed is "Cannot find node '(info)Help'" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: info 6.5.0.dfsg.1-4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: i3 Date: Wed Nov 21 07:16:55 2018 InstallationDate: Installed on 2018-11-01 (19 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: texinfo UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1804359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905100] Re: Cover art not shown for file which has a cover art
You could try removing ~/.cache/thumbnails/fail and see if the others correctly got regenerated or fail again -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1905100 Title: Cover art not shown for file which has a cover art Status in nautilus package in Ubuntu: Incomplete Bug description: Hello! There is one file in my music folder for which a thumbnail is not shown by Nautilus, although it does have a cover art. Gnome Videos shows the cover art, as well as VLC media payer. I will upload the file here. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Nov 21 00:55:59 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2020-02-08 (286 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-10-23 (28 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804359] Re: tutorial doesn't work
Same problem here. Ubuntu 19.10. Info 6.6.0.dfsg.1-2ubuntu2. Following advice from https://unix.stackexchange.com/questions/588026/cannot-start-the-info-tutorial-in-debian-9-stretch I installed emacs-common-non-dfsg. After that pressing h inside info brings up the tutorial but the command info info still results in: info: No menu item 'info-stnd' in node '(dir)Top' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1804359 Title: tutorial doesn't work Status in texinfo package in Ubuntu: Confirmed Bug description: Running `info` and pressing `h` doesn't bring up promised tutorial: ---cut--- File: dir, Node: Top, This is the top of the INFO tree. This is the Info main menu (aka directory node). A few useful Info commands: 'q' quits; 'H' lists all Info commands; 'h' starts the Info tutorial; 'mTexinfo RET' visits the Texinfo manual, etc. ---cut--- The error message displayed is "Cannot find node '(info)Help'" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: info 6.5.0.dfsg.1-4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: i3 Date: Wed Nov 21 07:16:55 2018 InstallationDate: Installed on 2018-11-01 (19 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: texinfo UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1804359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903893] Re: [snap] Notifications do not show a custom icon
Chromium doesn't use libnotify, it invokes the org.freedesktop.Notifications D-Bus API directly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1903893 Title: [snap] Notifications do not show a custom icon Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi, Notification coming from Chromium web browser ( as a snap ) show generic icon instead of favicon or website icon or any website picture. For reference ⋅ https://forum.snapcraft.io/t/notifications-in-chromium-show-generic-icon/21079 ⋅ https://github.com/solus-project/budgie-desktop/pull/2000#issuecomment-653833784 ⋅ https://discourse.ubuntubudgie.org/t/notification-issues/434 It's *not* specific to ( Ubuntu ) Budgie. And to some extent might affect any chromium snap based web browser. Interesting insight in second link, quoting : « Chromium based browser notifications pop up with broken icon images. This is due to the fact these browsers prefix the icon name in the notification with "file:///". Furthermore, snap based chromium browsers save the temporary icon in the snap, and don't pass the correct path to Raven. If the icon names start with "file:///", clearing the icon name fixes both of these issues by allowing the browsers to show the correct image (same as Firefox does), and allows the snaps to default to the fallback "mail-unread-symbolic" icon, instead of showing a broken image icon. This fix also should have absolutely no effect on any other notifications. » Attachment : top right is the actual notification ( with unread mail icon ) it should show : ⋅ ideally, picture from site ( cover art in that case, it's a music streaming site, as done in Firefox in same situation ) ⋅ or (fav)icon for the site ( deezer here, which icon is shown a bit above in workspaces applet in top panel ) ⋅ or web browser icon ( chromium ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1903893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904079] Re: Wrong keyboard behavior only inside chromium snap
Thanks for the report Kemel. I've just tested this on my 20.10 desktop, and I can confirm that acute+C results in an accented c <ć>, but not just in the chromium snap, in every application, including non-snap ones. So I'm wondering whether there's some special configuration on your machine that enables the acute+C => ç ? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Summary changed: - Wrong keyboard behavior only inside chromium snap + acute+C on US international with dead keys layout should produce cedilla sign (ç) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1904079 Title: acute+C on US international with dead keys layout should produce cedilla sign (ç) Status in chromium-browser package in Ubuntu: Incomplete Bug description: I've been facing a really strange bug in Ubuntu 20.04. My laptop has Brazilian Portuguese layout (ABNT-2) but my external keyboard has a US layout. So, in order to get a cedilla sign <ç> on those keyboards, I have to change layout to US International with Dead Keys and use an acute accent plus C <'+c>. Everything works fine unless inside the Chromium (installed from snap). In this case I get an accented c <ć>. So, I don't have a way to get a ç inside chrome, which is used in Portuguese. I'm using chromium from stable channel. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 22:24:50 2020 InstallationDate: Installed on 2020-11-07 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Snap: chromium 86.0.4240.198 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1904079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873052] Re: Showing two cursors after login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873052] Re: Showing two cursors after login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873052] Re: Showing two cursors after login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873052] Re: Showing two cursors after login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905287] Re: chrome and gnome-terminal tabs moves to the last by itself
Note, even disabling the touchpad, or unloading the kernel touchpad drivers didn't solve it. I had to plug in a mouse and remove it to stop having this problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905287 Title: chrome and gnome-terminal tabs moves to the last by itself Status in gnome-shell package in Ubuntu: New Bug description: This doesn't occur with Firefox. But it occurs with Chrome AND gnome- terminal. What happens is that if I have more than one tab in focus, it moves to the last tabs by itself. Here is a screen capture of what happens. I am running ubuntu 18.04.5 LTS, i have never had this issue before. Issue started happening since yesterday. This morning I applied my updates hoping that this will fix it, but even then nothing happened. I have known this to happen in another older laptop running an older version of ubuntu as well. journalctl -f gives me ths following: ``` Nov 23 15:28:36 xxxmymachinenamexxx gnome-shell[4051]: pushModal: invocation of begin_modal failed ``` Note that this error entry from the journalctl does not always appear when the tabs cycle through like in the video, might be unrelated. My graphics card is: lspci |grep VGA ``` 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) ``` I thought initially it might be some key that is being pressed, so i ran screenkey when this happens, there was no key appearing, so it does not seem that this is a key being pressed. I tail -f /var/log/syslog and /var/log/Xorg.0.log when i click on the tabs and it does this weirdness, nothing happens. So i don't have much information to give on this issue. Please get in touch with me if you want any information. I cannot push all my logs since it is a professional laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905287] Re: chrome and gnome-terminal tabs moves to the last by itself
Even after multiple restart the issue was not fixed. Turns out it was affecting every application that involved mouse wheel down. when I pressed ctrl, it would zoom out etc. User level FIX: Weirdly, after I plugged in a USB mouse, and plugged it out. The issue stopped. Yep, just like that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905287 Title: chrome and gnome-terminal tabs moves to the last by itself Status in gnome-shell package in Ubuntu: New Bug description: This doesn't occur with Firefox. But it occurs with Chrome AND gnome- terminal. What happens is that if I have more than one tab in focus, it moves to the last tabs by itself. Here is a screen capture of what happens. I am running ubuntu 18.04.5 LTS, i have never had this issue before. Issue started happening since yesterday. This morning I applied my updates hoping that this will fix it, but even then nothing happened. I have known this to happen in another older laptop running an older version of ubuntu as well. journalctl -f gives me ths following: ``` Nov 23 15:28:36 xxxmymachinenamexxx gnome-shell[4051]: pushModal: invocation of begin_modal failed ``` Note that this error entry from the journalctl does not always appear when the tabs cycle through like in the video, might be unrelated. My graphics card is: lspci |grep VGA ``` 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) ``` I thought initially it might be some key that is being pressed, so i ran screenkey when this happens, there was no key appearing, so it does not seem that this is a key being pressed. I tail -f /var/log/syslog and /var/log/Xorg.0.log when i click on the tabs and it does this weirdness, nothing happens. So i don't have much information to give on this issue. Please get in touch with me if you want any information. I cannot push all my logs since it is a professional laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905122] Re: firefox xubuntu.20.04.1 don`t work localization
No problem. $ dpkg -l | grep firefox ii firefox 83.0+build2-0ubuntu0.20.04.1 amd64Safe and easy web browser from Mozilla ii firefox-locale-ru 83.0+build2-0ubuntu0.20.04.1 amd64Russian language pack for Firefox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1905122 Title: firefox xubuntu.20.04.1 don`t work localization Status in firefox package in Ubuntu: Incomplete Bug description: When I install Xubuntu-20-04-1.iso with russian language for OS jn Virtualbox Computer, Firefox don`t have russian locale. I install all localization files and set in Firefox russian language manually. But anytime when I install firefox updates language settings automatically sets to english. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olex782 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Sat Nov 21 12:33:07 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-11-21 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=83.0/20201112153044 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1905122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881423] Re: error channel closing too late to send/recv
This is a problem because the errors also spew to the terminal -- corrupting whatever the user is doing now in the terminal. Firefox is started with a terminal if the user runs (possibly indirectly through a script) something which uses xdg-open, for example, on a file when firefox is the handler for it. ###!!! [Child][MessageChannel] Error: (msgtype=0x3A0146,name=PContent::Msg_ScriptError) Channel closing: too late to send/recv, messages will be lost -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1881423 Title: error channel closing too late to send/recv Status in firefox package in Ubuntu: Confirmed Bug description: I saw the following in my logs on a fresh install of 18.04.4: May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Sat May 30 12:57:41 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1881423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904622] Re: boto3+s3 bucket fails
** Changed in: duplicity Importance: Medium => Undecided ** Changed in: duplicity Status: In Progress => Invalid ** Changed in: duplicity Milestone: 0.8.18 => None -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1904622 Title: boto3+s3 bucket fails Status in Duplicity: Invalid Status in duplicity package in Ubuntu: Incomplete Bug description: I have a duplicity job that runs on multiple hosts, and am now having failures on my 20.04 hosts. The syntax for the job (as I am currently testing to debug) is: duplicity --dry-run list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Using the duplicity packages from focal/main duplicity=0.8.11.1612-1 And I installed the boto packages from focal/universe python3-boto3=1.9.253-1 python3-botocore=1.14.14+repack-1 This runs into the error: Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir Traceback (innermost last): File "/usr/bin/duplicity", line 106, in with_tempdir(main) File "/usr/bin/duplicity", line 92, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 85, in __init__ self.reset_connection() File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 96, in reset_connection self.s3.meta.client.head_bucket(Bucket=self.bucket_name) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call return self._make_api_call(operation_name, kwargs) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 676, in _make_api_call raise error_class(parsed_response, operation_name) botocore.exceptions.ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I then tried the duplicity snap from the snap store, both the stable and edge builds, with the same issue: Main action: list-current duplicity 0.8.17 Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden Main action: list-current duplicity 0.8.18.dev11 Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I also tried to update the boto3/botocore packages by way of pip3: pip3 freeze | grep boto boto3==1.16.19 botocore==1.19.19 And lastly as a last ditch, I tried to pull the packages from the groovy/universe repo, bringing them to: python3-boto3 1.13.14-1 python3-botocore 1.17.22+repack-1_all I have also tried in a 20.10 system as well to see if any changes there, but same results. Hoping for something I can look at to get this back working as it was in 18.04 since 14.04. For good measure, I verified in a bionic build that using the same arguments as above with
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Azizkhan (injkgz) I don't think it is, I believe the for-next branch in linux-gpio will only be integrated in 5.11, but @Coiby Xu (coiby) should be able to confirm that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku:
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
The problem persists, btw. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
I tried to perform with administrator privileges on both "Ubuntu" (default) and "GNOME Xorg". In both it was not possible. But I managed to do it without being an admin, even though nothing came up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 565971] Re: I cannot mount my ipod shuffle. It shows up with the system>administration>disk utility; but it doesn't have any mountable partitions. (It actually does)
just stumbled on this bug while trying to revive an ancient ipod shuffle 1st gen. So... confirmed that this is still an issue on Ubuntu 20.04.1 LTS. (removing libgpod-common is the workaround) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgpod in Ubuntu. https://bugs.launchpad.net/bugs/565971 Title: I cannot mount my ipod shuffle. It shows up with the system>administration>disk utility; but it doesn't have any mountable partitions. (It actually does) Status in libgpod package in Ubuntu: Confirmed Bug description: I did not have this problem when I was using jaunty jackalope. My ipod was automatically detected and mounted. apt-cache policy libipoddevice0: Installed: 0.5.3-3.2ubuntu2 Candidate: 0.5.3-3.2ubuntu2 Version table: *** 0.5.3-3.2ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libipoddevice0 0.5.3-3.2ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 Architecture: amd64 Date: Sun Apr 18 09:43:03 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100317.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: libipoddevice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpod/+bug/565971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1904777] Re: Xorg randomly crashes under xrdp
>journalctl -b-1 | grep dixGetPrivateAddr This yields empty, I've searched over periods that I know the server crashed, but nothing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1904777 Title: Xorg randomly crashes under xrdp Status in xorg-server package in Ubuntu: Incomplete Bug description: I'm using xrdp to log into a remote machine. Since upgrading it to 20.04, my sessions started failing randomly. They would either not start at all, or get interrupted hours later. Here's a backtrace I found in a .xorgxrdp.log [ 92697.914] rdpkeybChangeKeyboardControl: autoRepeat off [ 92697.915] rdpInDeferredRepeatCallback: [ 92697.916] rdpkeybChangeKeyboardControl: [ 92697.916] rdpkeybChangeKeyboardControl: autoRepeat off [ 92712.569] (EE) [ 92712.586] (EE) Backtrace: [ 92712.601] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5559b013811c] [ 92712.605] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7ffa5424f41f] [ 92712.608] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7ffa5408c18b] [ 92712.611] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7ffa5406b859] [ 92712.612] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 92712.612] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7ffa5406b71a] [ 92712.614] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7ffa5407cf36] [ 92712.615] (EE) 6: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc15) [0x5559b0103095] [ 92712.615] (EE) 7: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa2) [0x5559b01046e2] [ 92712.616] (EE) 8: /usr/lib/xorg/Xorg (DRI2GetParam+0x944) [0x5559b0105aa4] [ 92712.616] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5559affd6f34] [ 92712.617] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5559affdafc4] [ 92712.617] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7ffa5406d0b3] [ 92712.618] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x5559affc4a2e] [ 92712.621] (EE) [ 92712.621] (EE) Fatal server error: [ 92712.621] (EE) Caught signal 6 (Aborted). Server aborting [ 92712.621] (EE) [ 92712.623] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 92712.623] (EE) Please also check the log file at ".xorgxrdp.16.log" for additional information. [ 92712.623] (EE) [ 92712.627] rdpmouseControl: what 4 [ 92712.627] rdpkeybControl: what 4 [ 92712.629] rdpLeaveVT: [ 92712.634] (EE) Server terminated with error (1). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.4 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 18 20:07:37 2020 DistUpgraded: 2020-11-10 20:20:36,496 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company ProLiant MicroServer N36L [103c:1609] MachineType: HP ProLiant MicroServer ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=62bd3629-e229-4962-b11f-695a62533e9d ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to focal on 2020-11-10 (7 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 07/29/2011 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd07/29/2011:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.product.sku: 664447-425 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
[Desktop-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement
This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.11 --- pulseaudio (1:11.1-1ubuntu7.11) bionic-security; urgency=medium * SECURITY UPDATE: don't rely on SCM_CREDENTIALS to detect snap confined clients (LP: #1895928) - d/p/0409-pa-client-peer-credentials.patch: drop patch - d/p/0409-fix-arg-parsing-after-async-hook.patch: remains of old 0409 patch not related to pa_creds. - d/p/0410-pa-client-peer-apparmor-label.patch: new patch, records AppArmor label in pa_client struct for native connections using aa_getpeercon. - d/p/0702-add-snappy-policy-module.patch: use the AppArmor label in the pa_client rather than looking it up via the process ID from SCM_CREDENTIALS. - CVE-2020-16123 * Don't block classic snaps from module loading/unloading (LP: #1886854) - d/p/0702-add-snappy-policy-module.patch: replace deny_to_snaps_hook with a version that allows classic snaps. -- James Henstridge Tue, 22 Sep 2020 12:30:20 +0800 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: Fix Released Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes the following run the snap to fail again. EXPECTED BEHAVIOUR
Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Pedro Ribeiro (pedrib) On Sun, Nov 22, 2020 at 07:48:27AM -, Pedro Ribeiro wrote: >@Coiby Xu (coiby) > >I build the next branch of linux-gpio (which contains the patch you mentioned >in #251), and the trackpad works just fine without the hid polling on the >kernel command line. >You can contact me if you'd like further testing, my email is >pedrib_at_gmail_dot_com Thank you for testing the patch! I'll put you in the Cc list next time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05
[Desktop-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.8 --- pulseaudio (1:13.99.1-1ubuntu3.8) focal-security; urgency=medium * SECURITY UPDATE: don't rely on SCM_CREDENTIALS to detect snap confined clients (LP: #1895928) - d/p/0409-pa-client-peer-credentials.patch: drop patch - d/p/0409-fix-arg-parsing-after-async-hook.patch: remains of old 0409 patch not related to pa_creds. - d/p/0410-pa-client-peer-apparmor-label.patch: new patch, records AppArmor label in pa_client struct for native connections using aa_getpeercon. - d/p/0702-add-snappy-policy-module.patch: use the AppArmor label in the pa_client rather than looking it up via the process ID from SCM_CREDENTIALS. - CVE-2020-16123 * Don't block classic snaps from module loading/unloading (LP: #1886854) - d/p/0702-add-snappy-policy-module.patch: replace deny_to_snaps_hook with a version that allows classic snaps. -- James Henstridge Thu, 15 Oct 2020 17:23:31 -0400 ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: Fix Released Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes
[Desktop-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement
This bug was fixed in the package pulseaudio - 1:13.99.2-1ubuntu2.1 --- pulseaudio (1:13.99.2-1ubuntu2.1) groovy-security; urgency=medium * SECURITY UPDATE: don't rely on SCM_CREDENTIALS to detect snap confined clients (LP: #1895928) - d/p/0409-pa-client-peer-credentials.patch: drop patch - d/p/0409-fix-arg-parsing-after-async-hook.patch: remains of old 0409 patch not related to pa_creds. - d/p/0410-pa-client-peer-apparmor-label.patch: new patch, records AppArmor label in pa_client struct for native connections using aa_getpeercon. - d/p/0702-add-snappy-policy-module.patch: use the AppArmor label in the pa_client rather than looking it up via the process ID from SCM_CREDENTIALS. - CVE-2020-16123 * Don't block classic snaps from module loading/unloading (LP: #1886854) - d/p/0702-add-snappy-policy-module.patch: replace deny_to_snaps_hook with a version that allows classic snaps. -- James Henstridge Thu, 05 Nov 2020 16:46:59 -0500 ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16123 ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: Fix Released Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first
Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Mike Boruta (maridius) On Sun, Nov 15, 2020 at 08:34:03PM -, Mike Boruta wrote: >@Coiby Xu (coiby) > >It seems that the patch in 171 does not work (i.e. touchpad is still >dead) on kernels older than 5.8. I tried 5.4.75, 5.7.19, and 5.8.18. I >don't really want to look into this further since I'm fine with the >newer kernel, but wanted to give you and any other users a heads up in >case they find themselves in a similar situation. The kernels I was >testing were taken straight from Ubuntu's mainline kernel page, and had >only the following changes: CONFIG_PINCTRL_AMD was made into a module, >specified line in pinctrl-amd.c was commented out. > So the patch in 171 works on kernels >=5.8 but doesn't work for older version like 5.7.19? >Thanks again for all of your help in making the linux experience with >this class of laptop much more enjoyable! > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1887190 > >Title: > MSFT Touchpad not working on Lenovo Legion-5 15ARH05 > >Status in Pop!_OS: > New >Status in linux package in Ubuntu: > Confirmed >Status in xserver-xorg-input-libinput package in Ubuntu: > Confirmed >Status in linux package in Arch Linux: > Fix Committed >Status in linux package in Fedora: > Confirmed >Status in linux package in openSUSE: > New > >Bug description: > Hello > > The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at > all (pointer and click never move when touchpad is touched). This has been > reported by other users in various websites, with various linux systems > including other Ubuntu systems, but I saw no launchpad bug so I post one. > Example of websites covering the issue : > - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly > the same laptop) > - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar > laptop) > > xinput indentifies it as MSFT0001:00 04F3:3140 > > Virtual core pointer id=2[master pointer (3)] > ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer > (2)] > ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer > (2)] > ⎜ ↳ MSFT0001:00 04F3:3140 Mouseid=16 [slave pointer > (2)] > ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Control id=12 [slave > pointer (2)] > ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer > (2)] > ⎣ Virtual core keyboard id=3[master keyboard (2)] > ↳ Virtual core XTEST keyboardid=5[slave > keyboard (3)] > ↳ Ideapad extra buttons id=15 [slave > keyboard (3)] > ↳ Power Button id=6[slave > keyboard (3)] > ↳ Integrated Camera: Integrated Cid=10 [slave > keyboard (3)] > ↳ Video Bus id=7[slave > keyboard (3)] > ↳ ITE Tech. Inc. ITE Device(8910) Consumer Control id=19 [slave > keyboard (3)] > ↳ Power Button id=9[slave > keyboard (3)] > ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave > keyboard (3)] > ↳ ITE Tech. Inc. ITE Device(8910) Keyboard id=14 [slave > keyboard (3)] > ↳ AT Translated Set 2 keyboard id=18 [slave > keyboard (3)] > ↳ Video Bus id=8[slave > keyboard (3)] > > Thanks a lot for your time. It does not help, but I can confirm what > was reported on askubuntu by another user : the touchpad does work on > Windows. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-40-generic 5.4.0-40.44 > ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 > Uname: Linux 5.4.0-40-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu27.3 > Architecture: amd64 > AudioDevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC0: nicolas1567 F pulseaudio > /dev/snd/controlC1: nicolas1567 F pulseaudio > /dev/snd/controlC2: nicolas1567 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Fri Jul 10 20:14:25 2020 > InstallationDate: Installed on 2020-07-02 (8 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) > MachineType: LENOVO 82B5 > ProcEnviron: > TERM=xterm-256color > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=fr_FR.UTF-8 > SHELL=/bin/bash > ProcFB: 0 EFI VGA > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic > root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 > RelatedPackageVersions: > linux-restricted-modules-5.4.0-40-generic N/A > linux-backports-modules-5.4.0-40-generic N/A > linux-firmware
[Desktop-packages] [Bug 1905158] Re: special characters ctrl+shift+u not allowed in login form
** Package changed: ubuntu => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1905158 Title: special characters ctrl+shift+u not allowed in login form Status in gdm3 package in Ubuntu: New Bug description: Ubuntu 20.04.1 64 bit login form doesn't allow use ctrl+shift+u to insert special characters in password field. Account manager allows to do it. Installer from 18.04 and login form 18.04 allow to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1905158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876879] Re: gnome-software cannot install classic snaps if a channel is selected
Bug also occurs on gnome software in groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: I tried installing Android Studio from gnome-software. In the top right dropdown, it asks for the source. For Andoid Studio it displays Ubuntu. I was suspicious of it being a deb and not a snap. So I clicked on it and it shown me 3 Snap channel options. I selected latest/stable. The source changed according to my selection. Then I tried installing it but it failed saying: Unable to install "Android Studio": snap "android-studio" requires classic confinement I was puzzled. So I went back to the search menu, I clicked again on Android Studio and the source was now again on Ubuntu (note that this is not an option available in the dropdown). I checked the details and indeed it's the snap package from channel latest/stable, just the source is somehow misleading. Now it installed the software without issues. What doesn't work: - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel - Selecting a channel breaks the install functionality for classic snaps (it seems like it attempts to install them without --classic) Workaround: Do not select any channel, just use what is provided, and it works. If needing to use a different channel, use the command line (or perhaps check if this works in the Snap Store, if it has not the same issue). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 11:09:26 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1876879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi @Maxim (pavlenkoms), Is your laptop also a Lenovo Legion-5 model? On Thu, Nov 12, 2020 at 09:02:54AM -, Maxim wrote: >Hi @Coiby Xu (coiby) >I tried #189 and #211 (different combinations) on mate-ubuntu 20.04 with >custom kernels 5.8 and 5.9 >I tried to install Manjaro with kernel 5.8.18, and after that I rebuilt custom >kernel again with all patches >But result is only one: touchpad still doesn't work. Is there any way to debug >or figure out what exactly went wrong? > >And here is an interresting detail. Touchpad devices disappearing in >xinput output from time to time, and could not work even in uefi menu. Do you mean the touchpad works sometimes after the booting the system but would fail when booting system next time? > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO
[Desktop-packages] [Bug 1905158] [NEW] special characters ctrl+shift+u not allowed in login form
You have been subscribed to a public bug: Ubuntu 20.04.1 64 bit login form doesn't allow use ctrl+shift+u to insert special characters in password field. Account manager allows to do it. Installer from 18.04 and login form 18.04 allow to do it. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- special characters ctrl+shift+u not allowed in login form https://bugs.launchpad.net/bugs/1905158 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
Scratch #38. It needed a reboot and now everything works fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: Fix Released Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I installed the Groovy-proposed updates, including: Package mutter: p A 3.38.1-1ubuntu1 groovy500 i A 3.38.1-2ubuntu1 100 Running a Snap results in the same error: $ joplin-james-carroll.joplin (joplin:40222): Gtk-WARNING **: 07:02:09.027: cannot open display: :0 $ chromium [43799:43799:1123/070612.587261:ERROR:browser_main_loop.cc(1434)] Unable to open X display. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: Fix Released Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905287] Re: chrome and gnome-terminal tabs moves to the last by itself
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905287 Title: chrome and gnome-terminal tabs moves to the last by itself Status in gnome-shell package in Ubuntu: New Bug description: This doesn't occur with Firefox. But it occurs with Chrome AND gnome- terminal. What happens is that if I have more than one tab in focus, it moves to the last tabs by itself. Here is a screen capture of what happens. I am running ubuntu 18.04.5 LTS, i have never had this issue before. Issue started happening since yesterday. This morning I applied my updates hoping that this will fix it, but even then nothing happened. I have known this to happen in another older laptop running an older version of ubuntu as well. journalctl -f gives me ths following: ``` Nov 23 15:28:36 xxxmymachinenamexxx gnome-shell[4051]: pushModal: invocation of begin_modal failed ``` Note that this error entry from the journalctl does not always appear when the tabs cycle through like in the video, might be unrelated. My graphics card is: lspci |grep VGA ``` 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) ``` I thought initially it might be some key that is being pressed, so i ran screenkey when this happens, there was no key appearing, so it does not seem that this is a key being pressed. I tail -f /var/log/syslog and /var/log/Xorg.0.log when i click on the tabs and it does this weirdness, nothing happens. So i don't have much information to give on this issue. Please get in touch with me if you want any information. I cannot push all my logs since it is a professional laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905287] [NEW] chrome and gnome-terminal tabs moves to the last by itself
You have been subscribed to a public bug: This doesn't occur with Firefox. But it occurs with Chrome AND gnome- terminal. What happens is that if I have more than one tab in focus, it moves to the last tabs by itself. Here is a screen capture of what happens. I am running ubuntu 18.04.5 LTS, i have never had this issue before. Issue started happening since yesterday. This morning I applied my updates hoping that this will fix it, but even then nothing happened. I have known this to happen in another older laptop running an older version of ubuntu as well. journalctl -f gives me ths following: ``` Nov 23 15:28:36 xxxmymachinenamexxx gnome-shell[4051]: pushModal: invocation of begin_modal failed ``` Note that this error entry from the journalctl does not always appear when the tabs cycle through like in the video, might be unrelated. My graphics card is: lspci |grep VGA ``` 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) ``` I thought initially it might be some key that is being pressed, so i ran screenkey when this happens, there was no key appearing, so it does not seem that this is a key being pressed. I tail -f /var/log/syslog and /var/log/Xorg.0.log when i click on the tabs and it does this weirdness, nothing happens. So i don't have much information to give on this issue. Please get in touch with me if you want any information. I cannot push all my logs since it is a professional laptop. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- chrome and gnome-terminal tabs moves to the last by itself https://bugs.launchpad.net/bugs/1905287 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905054] Re: Firefox 83 Breaks WebGL
Thanks for the ideas. drm driver as listed from lsmod: drm 491520 9 drm_kms_helper,i915 I tried the snap and it behaved the same way, the exact same console output. The snap was version 83.0-2 via snapcraft.io. I assume by "xrg" you mean "xorg"? I have not tried under an xorg session. So, it doesn't look like a packaging issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL Status in firefox package in Ubuntu: Confirmed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1905054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905100] Re: Cover art not shown for file which has a cover art
** Attachment added: "Screenshot from 2020-11-23 16-38-11.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905100/+attachment/5437242/+files/Screenshot%20from%202020-11-23%2016-38-11.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1905100 Title: Cover art not shown for file which has a cover art Status in nautilus package in Ubuntu: Incomplete Bug description: Hello! There is one file in my music folder for which a thumbnail is not shown by Nautilus, although it does have a cover art. Gnome Videos shows the cover art, as well as VLC media payer. I will upload the file here. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Nov 21 00:55:59 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2020-02-08 (286 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-10-23 (28 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905100] Re: Cover art not shown for file which has a cover art
Once i copied the file it is now shown correctly in the new location (the Desktop). But i have a hell of a lot more files in the main Music folder which do have a cover shown inside Gnome Videos while Nautilus doesn't show covers for them. I am using MusicBrainz Picard from Ubuntu repos for saving the cover photos. No idea why some cover images show up and some do not. The file which i attached is one of those that are not showing in their original folder. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1905100 Title: Cover art not shown for file which has a cover art Status in nautilus package in Ubuntu: Incomplete Bug description: Hello! There is one file in my music folder for which a thumbnail is not shown by Nautilus, although it does have a cover art. Gnome Videos shows the cover art, as well as VLC media payer. I will upload the file here. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Nov 21 00:55:59 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2020-02-08 (286 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-10-23 (28 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Or this ppa https://launchpad.net/~mozillateam/+archive/ubuntu/ppa To avoid snap and its problems -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: In Progress Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896138] Re: nautilus doesn't display thumbnails on network share
thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1896138 Title: nautilus doesn't display thumbnails on network share Status in nautilus package in Ubuntu: New Bug description: I've got nautilus configured to display thumbnails on network shares (prefs -> search -> thumbnails -> all files), but in 20.04 it never shows thumbnails on my samba network shares. Not sure what broke since previous ubuntu releases, but it's definitely not working now. local thumbnail generation and display works fine still, so there isn't an issue with the thumbnail generation itself as far as I can tell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 17 17:22:15 2020 InstallationDate: Installed on 2020-07-15 (64 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1896138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896138] Re: nautilus doesn't display thumbnails on network share
and per your suggestion, here's the upstream bug I just filed: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1678 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1678 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1678 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1896138 Title: nautilus doesn't display thumbnails on network share Status in nautilus package in Ubuntu: New Bug description: I've got nautilus configured to display thumbnails on network shares (prefs -> search -> thumbnails -> all files), but in 20.04 it never shows thumbnails on my samba network shares. Not sure what broke since previous ubuntu releases, but it's definitely not working now. local thumbnail generation and display works fine still, so there isn't an issue with the thumbnail generation itself as far as I can tell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 17 17:22:15 2020 InstallationDate: Installed on 2020-07-15 (64 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1896138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901286] Re: gnome-disk-image-mounter fails after upgrade to 20.10
filed an upstream bug for this one as well: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1901286 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1901286 Title: gnome-disk-image-mounter fails after upgrade to 20.10 Status in gnome-disk-utility package in Ubuntu: New Bug description: after upgrading to 20.10, mounting ISOs fails after a bit over 20s, with a GTK dialogue that reads: ``` Error attaching disk image: GDBus.Error:org.freedesktop.UDisks2.Error.Fails: Error waiting for loop object after creating '/dev/loop5': Timed out waiting for object (udisks-error-quark, 0) ``` note that the loop device named increases on every attempt, it doesn't appear to be freeing previously allocated devices. here's the only output when run from the shell: ``` $ time gnome-disk-image-mounter some.iso real 0m23.141s user 0m0.144s sys 0m0.019s ``` ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-disk-utility 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-lowlatency 5.8.14 Uname: Linux 5.8.0-25-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 23 23:42:34 2020 InstallationDate: Installed on 2020-07-15 (101 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1901286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901609] Re: signond causes qprocess crash
** Description changed: - I'm reporting this bug upstream from where I found it, since I've - learned that the signond package in KDE Neon is sourced from Ubuntu - focal. + [Impact] + + Without the patch users are unable to add google accounts because signond crashes. + This prevents users from using KDE's online accounts feature for google. + The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. + + [Test Case] + + - in a plasma session + - install kio-gdrive + - run `systemsettings5 kcm_kaccounts` + - add a new account + - click on google + - wait for login window to appear + - signond shouldn't be crashing + + [Where problems could occur] + + Cannot think of any. It simply adds type info to the objects. Also + upstream has rtti disabled for months and I'm not aware of any problems. + + [Other Info] + + This is a fairly grave issue as far as user experience is concerned. + + + + + + I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) - Expected behaviour: + Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. - Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 ** Also affects: signon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: signon (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: signon (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: New Status in signon source package in Focal: New Status in signon source package in Groovy: New Status in signon source package in Hirsute: New Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to:
