[Desktop-packages] [Bug 1924606] Re: gnome-shell somethimes freeze and crash
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1924606 Title: gnome-shell somethimes freeze and crash Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell somethimes freeze and crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 22:03:14 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (194 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 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/gnome-shell/+bug/1924606/+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 1924753] Re: gnome-shell repeatedly crashing and core dumping
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1924753 Title: gnome-shell repeatedly crashing and core dumping Status in gnome-shell package in Ubuntu: New Bug description: This is a repeat of bug 1886059 with "MUTTER_SYNC=1" added to /etc/environment. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 06:26:22 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-31 (625 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-09 (341 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1924753/+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 1920719] Re: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:269: poll_for_event: Assertiva \342\200\234!xcb_xlib_threads_sequence_lost\342\200\235 falhou.
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1920719 Title: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:269: poll_for_event: Assertiva \342\200\234!xcb_xlib_threads_sequence_lost\342\200\235 falhou. Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.3-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/42cfd76250a81cca07f8c548ec27e245315b5e01 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920719/+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 1935744] Re: After a startup and login by lightdm it gave me this message: Sorry, Ubuntu 20.04 Has Expirienced An Internel Error
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1935744 Title: After a startup and login by lightdm it gave me this message: Sorry, Ubuntu 20.04 Has Expirienced An Internel Error Status in gnome-shell package in Ubuntu: New Bug description: It seems like gnome-shell did it but that's all i know Description: Ubuntu 20.04.2 LTS Release: 20.04 Gnome-shell version 3.36.9-0ubuntu0.20.04.2 i expected it to work fine. like before but it gave me this error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 19:06:58 2021 DisplayManager: lightdm InstallationDate: Installed on 2021-07-08 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 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/gnome-shell/+bug/1935744/+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 1924625] Re: gnome-shell repeatedly restarting and core dumping
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1924625 Title: gnome-shell repeatedly restarting and core dumping Status in gnome-shell package in Ubuntu: New Bug description: Yesterday (2021-04-14) I ran apt update/upgrade, then rebooted my laptop overnight. With the upgrade Linux 5.4.0-71 was installed. Now I have an issue where gnome-shell restarts repeatedly. Looking in the logs, I see that gnome-shell is core dumping when this occurs. I have not (yet) identified any behavior that causes the problem. I disabled extensions with the Gnome Tweak Tool and rebooted into the previous Linux version but the problem remains. This may be related to https://bugs.launchpad.net/bugs/1923864 and https://bugs.launchpad.net/bugs/1924606 as the symptoms are similar and both have been reported in within the correct time frame. The contents of the log file from an instance of this occurring is attached. I am using Ubuntu 20.04.2 gnome-shell version is 3.36.7-0ubuntu0.20.04.1 Please let me know if you have any questions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 17:37:46 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-31 (624 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-09 (341 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1924625/+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 1918434] Re: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:269: poll_for_event: \320\237\321\200\320\276\320\262\320\265\321\200\320\276\321\207\320\275\320\276\320\265
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1918434 Title: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:269: poll_for_event: \320\237\321\200\320\276\320\262\320\265\321\200\320\276\321\207\320\275\320\276\320\265 \321\203\321\202\320\262\320\265\321\200\320\266\320\264\320\265\320\275\320\270\320\265 \302\253!xcb_xlib_threads_sequence_lost\302\273 \320\275\320\265 \320\262\321\213\320\277\320\276\320\273\320\275\320\265\320\275\320\276. Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e3f9ab8232005403e935c6038edd99f13e609e01 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918434/+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 1905759] Re: gnome-shell crashed with SIGABRT in GI_raise()
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1905759 Title: gnome-shell crashed with SIGABRT in GI_raise() Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.10 Release: 20.10 In the middle of work screen will randomly glitch green then revert to the login screen - behaviour with both Wayland and not Wayland. Apport.log shows: ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: called for pid 2318, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: debug: session gdbus call: (true,) ERROR: apport (pid 11042) Thu Nov 26 11:51:51 2020: wrote report /var/crash/_usr_bin_gnome-shell.1000.crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905759/+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 1924613] Re: gnome-shell assert failure: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1924613 Title: gnome-shell assert failure: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-shell: Installed: 3.36.7-0ubuntu0.20.04.1 Candidate: 3.36.7-0ubuntu0.20.04.1 Version table: *** 3.36.7-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.4-1ubuntu1~20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 3.36.1-5ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages mutter 3.36.7 Description of issue: The GUI seems to freeze/reload/refresh instantly. It happens when I e.g. click on the docker panel and/or just move the mouse cursor around, click on apps and do something GUI related, open folders. The GUI reload/refresh crash lasts for about 2 seconds, it suddenly/instantly repositions my mouse cursor to the lower right corner of the screen and my laptop's fan works harder at those 2 seconds. The issue started after I updated and, at a later time, rebooted the machine. Below are the gnome-related upgrades that I did (`cat /var/log/dpkg.log | grep gnome`): 2021-04-15 17:50:29 status triggers-pending gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 17:50:30 upgrade libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:30 status half-configured libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 2021-04-15 17:50:30 status unpacked libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 2021-04-15 17:50:30 status half-installed libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 2021-04-15 17:50:30 status unpacked libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 configure libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 status unpacked libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 status half-configured libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 status installed libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:57 trigproc gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 17:50:57 status half-configured gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 17:50:57 status installed gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 status triggers-pending gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 trigproc gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 status half-configured gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 status installed gnome-menus:amd64 3.36.0-1ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AssertionMessage: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 22:04:15 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1608008084 InstallationDate: Installed on 2021-01-17 (88 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/freekostageo RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7feadaaeb588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7feada528858 "!xcb_xlib_threads_sequence_lost", file=0x7feada5286c3 "../../src/xcb_io.c", line=260, function=) at assert.c:92 __GI___assert_fail (assertion=0x7feada528858 "!xcb_xlib_threads_sequence_lost", file=0x7feada5286c3 "../../src/xcb_io.c", line=260, function=0x7feada528b10 "poll_for_event") at assert.c:101 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 Title: gnome-shell assert failure: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. UpgradeStatus:
[Desktop-packages] [Bug 1886060] Re: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: P\305\231edpoklad \342\200\236!xcb_xlib_threads_sequence_lost\342\200\234 nespln\304\233n
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1886060 Title: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: P\305\231edpoklad \342\200\236!xcb_xlib_threads_sequence_lost\342\200\234 nespln\304\233n. Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu1~20.04.2, the problem page at https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886060/+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 1886125] Re: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260\357\274\232poll_for_event: \345\201\207\350\256\276 \342\200\230!xcb_xlib_threads_sequence_lost\342\200\23
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1886125 Title: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260\357\274\232poll_for_event: \345\201\207\350\256\276 \342\200\230!xcb_xlib_threads_sequence_lost\342\200\231 \345\244\261\350\264\245\343\200\202 Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu1~20.04.2, the problem page at https://errors.ubuntu.com/problem/65e7872c90aaee8e9c1f64081a7e0be3ad4df60e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886125/+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 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in libx11 package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Invalid Status in libx11 source package in Focal: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Similar errors: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd https://errors.ubuntu.com/problem/e3f9ab8232005403e935c6038edd99f13e609e01 https://errors.ubuntu.com/problem/9d421ecaba25357f5c3ef73f438313e40ac24e77 https://errors.ubuntu.com/problem/42cfd76250a81cca07f8c548ec27e245315b5e01 --- Anyone experiencing this crash reliably, please help us to find its root cause by editing your /etc/environment and adding a line: MUTTER_SYNC=1 and then reboot. Then next time a crash happens please tell us (here) the bug ID or error URL of the new crash. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1886059/+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 1878569] Re: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: \320\237\321\200\320\276\320\262\320\265\321\200\320\276\321\207\320\275\320\276\320\265
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1878569 Title: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: \320\237\321\200\320\276\320\262\320\265\321\200\320\276\321\207\320\275\320\276\320\265 \321\203\321\202\320\262\320\265\321\200\320\266\320\264\320\265\320\275\320\270\320\265 \302\253!xcb_xlib_threads_sequence_lost\302\273 \320\275\320\265 \320\262\321\213\320\277\320\276\320\273\320\275\320\265\320\275\320\276. Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.1-5ubuntu2, the problem page at https://errors.ubuntu.com/problem/4b78bc9730e8681f0c42fc2ecea14d03544394f0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878569/+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 1918435] Re: gnome-shell crashes in ../../src/xcb_io.c:269: poll_for_event → Assertion `!xcb_xlib_threads_sequence_lost'' failed
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1918435 Title: gnome-shell crashes in ../../src/xcb_io.c:269: poll_for_event → Assertion `!xcb_xlib_threads_sequence_lost'' failed Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.3-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/9d421ecaba25357f5c3ef73f438313e40ac24e77 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Other: https://errors.ubuntu.com/problem/e3f9ab8232005403e935c6038edd99f13e609e01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918435/+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 1877092] Re: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Zusicherung \302\273!xcb_xlib_threads_sequence_lost\302\253 nicht erf\303\274llt.
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1877092 Title: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Zusicherung \302\273!xcb_xlib_threads_sequence_lost\302\253 nicht erf\303\274llt. Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.1-5ubuntu2, the problem page at https://errors.ubuntu.com/problem/2251b638f7a6167772f922dc5916740522c5c22b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877092/+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 1878568] Re: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: asserzione \"!xcb_xlib_threads_sequence_lost\" non riuscita.
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1878568 Title: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: asserzione \"!xcb_xlib_threads_sequence_lost\" non riuscita. Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.1-5ubuntu2, the problem page at https://errors.ubuntu.com/problem/943838b8a80c1da4f8df584b7d2ad3a13361fdd7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878568/+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 1877075] Re: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug is no longer a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1877075 Title: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed 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 Bug description: [Impact] This is the #1 crasher of gnome-shell in Ubuntu 20.04, though it's duplicated across multiple problem reports according to locale: https://errors.ubuntu.com/problem/4de3d315d9df1c9699bda54beafa8d52053c https://errors.ubuntu.com/problem/2251b638f7a6167772f922dc5916740522c5c22b https://errors.ubuntu.com/problem/943838b8a80c1da4f8df584b7d2ad3a13361fdd7 https://errors.ubuntu.com/problem/4b78bc9730e8681f0c42fc2ecea14d03544394f0 [Test Case] None known. The plan is to just continue monitoring crash reports. Still, we are confident this is the fix because: * The offending source code in libx11 tells us it is :) and * The crash only started in Ubuntu with gnome-shell 3.34, which is the exact release in which XInitThreads was removed from mutter. [Regression Potential] Low. We add a single function call that tells libX11 to enable thread safety. This is the same as what we had in bionic, cosmic and disco, so it's well tested. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1877075/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
It's the top crasher of gnome-shell in focal, but I don't know a test case... https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=gnome- shell&period=month -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least r
[Desktop-packages] [Bug 1943240] Re: libreoffice 7.2.0.4 Error "Image filter not found" when trying to insert JPG
Bug was reported for Snap and is not reproducible with normal LO installation. https://bugs.documentfoundation.org/show_bug.cgi?id=144385 has status Moved from NotOurBug. ** Bug watch added: Document Foundation Bugzilla #144385 https://bugs.documentfoundation.org/show_bug.cgi?id=144385 -- 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/1943240 Title: libreoffice 7.2.0.4 Error "Image filter not found" when trying to insert JPG Status in libreoffice package in Ubuntu: New Bug description: Description: JPG files can't be inserted into LibreOffice writer document. Files already containing JPG files only show blank containers. LibreOffice Writer 7.2.0.4 from current Ubuntu Snap repository on Ubuntu 20.04 LTS Steps to Reproduce: 1) Start LibreOffice Writer 2) Create new file 3) Insert -> Image -> Select a JPG file Actual Results: Error "Image filter not found" and no image inserted Expected Results: JPG image should be inserted Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Inserting a PNG image works though [Information automatically included from LibreOffice] Locale: us Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes LibreOffice Writer 7.2.0.4 from current Ubuntu Snap repository Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1943240/+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 1930188] Re: Acer Aspire 5 sound driver issues
@Bijay, This change is consistent to the Legacy HDA audio, the Capture Volume and Mic boost are bond together when changing the input volume from UI. With this change, you could get "mic volume on 100% and mic boost on 20db gain" through adjusting input volume from UI (capture volume is changed first, after it is 100%, then start to change mic boost). I will upload a new debdiff for focal, then you could manually change /usr/share/alsa/ucm2/sof-hda-dsp/HiFi.conf as the debdiff, reboot and test. -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch
[Desktop-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This is an updated debdiff of alsa-ucm-conf for focal. Please ignore the previous one (I hide the previous one). thx. ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.11.debdiff" https://bugs.launchpad.net/ubuntu/hirsute/+source/linux/+bug/1930188/+attachment/5525090/+files/alsa-ucm-conf_1.2.2-1ubuntu0.11.debdiff -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which
[Desktop-packages] [Bug 1943240] Re: libreoffice 7.2.0.4 Error "Image filter not found" when trying to insert JPG
Thanks, it was discussed on https://forum.snapcraft.io/t/last- libreoffice-snap-7-2-0-4-not-able-to-import-jpeg/ ** Changed in: libreoffice (Ubuntu) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed ** Summary changed: - libreoffice 7.2.0.4 Error "Image filter not found" when trying to insert JPG + libreoffice 7.2.0.4 snap Error "Image filter not found" when trying to insert JPG ** Tags added: snap -- 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/1943240 Title: libreoffice 7.2.0.4 snap Error "Image filter not found" when trying to insert JPG Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: JPG files can't be inserted into LibreOffice writer document. Files already containing JPG files only show blank containers. LibreOffice Writer 7.2.0.4 from current Ubuntu Snap repository on Ubuntu 20.04 LTS Steps to Reproduce: 1) Start LibreOffice Writer 2) Create new file 3) Insert -> Image -> Select a JPG file Actual Results: Error "Image filter not found" and no image inserted Expected Results: JPG image should be inserted Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Inserting a PNG image works though [Information automatically included from LibreOffice] Locale: us Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes LibreOffice Writer 7.2.0.4 from current Ubuntu Snap repository Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1943240/+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 1942542] Re: gedit causes loss of extended attributes (xattrs)
https://gitlab.gnome.org/GNOME/gedit/-/issues/464 ** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #464 https://gitlab.gnome.org/GNOME/gedit/-/issues/464 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1942542 Title: gedit causes loss of extended attributes (xattrs) Status in gedit package in Ubuntu: New Bug description: Ubuntu 21.04 hirsute gedit 3.38.1-1 If a file with extended attributes (xattrs) is edited and saved with gedit, the xattrs are lost. This problem - as well as the loss of birth time, reported in https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1940758 - seems to be caused by gedit creating a new file when saving. Compare this with nano, which does not destroy xattrs. Steps to reproduce: 1 echo testing > testfile.txt 2 setfattr -n user.test -v "this is my test xattr" testfile.txt 3 getfattr -d testfile.txt # file: testfile.txt user.test="this is my test xattr" 4 gedit testfile.txt make edit and save 5 getfattr -d testfile.txt no output This bug also causes a loss of ACLs for the edited file, as they are stored as extended attributes. Because of this I am marking this bug as a security vulnerability. This bug is not limited to gedit; it applies to a number of other text editors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1942542/+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 1930188] Re: Acer Aspire 5 sound driver issues
If it works as you say then I think it's fine. I will test it out using the Hifi.conf diff and report later. Thanks. -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp
[Desktop-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Confirmed on Ubuntu 18.04.6 LTS i686. ** Tags added: i686 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1943558] [NEW] Regression: Gnome shell has red tint after installation of Nvidia proprietary drivers
Public bug reported: Upstream report of this issue: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4071 A colleague tested the latest daily of Ubuntu 21.10 and had a red tint after installing the proprietary nvidia drivers. Did not happen with gnome-shell versions < 40. Changing display refresh rate made the red tint go away. This report should serve as a reminder to fix this bug before it hits the masses after release. If you need more specific info I'll request it from my colleague, he did not want to bother reporting the bug himself. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: impish regression-release -- 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/1943558 Title: Regression: Gnome shell has red tint after installation of Nvidia proprietary drivers Status in gnome-shell package in Ubuntu: New Bug description: Upstream report of this issue: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4071 A colleague tested the latest daily of Ubuntu 21.10 and had a red tint after installing the proprietary nvidia drivers. Did not happen with gnome-shell versions < 40. Changing display refresh rate made the red tint go away. This report should serve as a reminder to fix this bug before it hits the masses after release. If you need more specific info I'll request it from my colleague, he did not want to bother reporting the bug himself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943558/+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 1909884] Re: tracker-extract crashes with SIGSYS when adding pdf to filesystem
Closing due to inactivity. ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid ** Changed in: tracker-miners (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1909884 Title: tracker-extract crashes with SIGSYS when adding pdf to filesystem Status in linux-raspi package in Ubuntu: Invalid Status in tracker-miners package in Ubuntu: Invalid Bug description: Almost daily, _usr_libexec_tracker-extract.1000.crash shows up in /var/crash. I'm using Raspberry Pi 4B 8GB with Ubuntu 20.10 Desktop and lxqt as Desktop. uname -a: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I saw in a previous backtrace that a pdf was the problem. So i downloaded some pdf with firefox to /home/username/Documents. In my case it was https://www.who.int/ceh/capacity/sanitation_hygiene.pdf After doing that, a crash-report was dumped by apport to /var/crash. A backtrace and full backtrace is in the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909884/+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 1844453]
*** Bug 144460 has been marked as a duplicate of this bug. ***
--
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/1844453
Title:
[upstream] Access to the Google remote account does not work
Status in LibreOffice:
In Progress
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+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 897222]
Repro 7.3+ for DOC. MSO created DOCX OK. -- 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/897222 Title: [Upstream] Picture moves to left importing Word .doc Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897222/+attachment/2611229/+files/Test%20case.doc -O testcase.doc && lowriter -nologo testcase.doc is the "X" picture in the top right on the document remains in the same place importing from Word (Word screenshot https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897222/+attachment/2611268/+files/Test%20case.jpg ). 4) What happens is the X moves to the left (LO screenshot https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897222/+attachment/2611239/+files/Libreoffice.png ). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libreoffice-writer 1:3.4.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Mon Nov 28 14:24:02 2011 ProcEnviron: LANGUAGE=pl_PL:pl:en_GB:en PATH=(custom, user) LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to oneiric on 2011-10-18 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/897222/+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 1393688] Re: open *.ppt file in libreoffice Impress is abnormal
This was old report which should've gone to upstream LO. Repro up to LO 7.0 but not with LO 7.1. Fixed in https://bugs.documentfoundation.org/show_bug.cgi?id=131269. So I mark "Fix Released". ** Bug watch added: Document Foundation Bugzilla #131269 https://bugs.documentfoundation.org/show_bug.cgi?id=131269 -- 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/1393688 Title: open *.ppt file in libreoffice Impress is abnormal Status in libreoffice package in Ubuntu: Triaged Bug description: I have a *.ppt fromat file , use other office software is correct, but open with libreoffice impress is abnormal. the ppt file has thirty pages in it , but in libreoffice impress show one page, and the content is uncomplete. OS: Ubuntu /Ubuntu Kylin 14.10 and Ubuntu Kylin 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1393688/+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 1943569] [NEW] Sometimes distorted sound in or after Firefox
Public bug reported: Sometimes when I open Firefox and play a video or start Plex Media Player or start to play a game I get a distorted audio/sound. I modified the Pulse Audio daemon.conf by this tutorial https://medium.com/@gamunu/enable-high-quality-audio-on- linux-6f16f3fe7e1f to improve the sound in Linux. The deamon.conf should be attached. When I get this issue I have to open a terminal and enter »pulseaudio -k«. After this it's normal again. Here's a complete hwinfo: https://gist.github.com/Johnnii360/1cbdbb0f27180013652a01f21c2f4792 My sound card is a Creative SoundBlaster X-Fi Titanium Fatal1ty (EMU20k2). Kernel version: 5.4.0-84-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 14 12:25:30 2021 InstallationDate: Installed on 2019-11-10 (674 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.40 dmi.board.name: Z390 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-05-31T09:26:29.202354 mtime.conffile..etc.pulse.daemon.conf: 2020-12-26T09:12:04.962975 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1943569 Title: Sometimes distorted sound in or after Firefox Status in pulseaudio package in Ubuntu: New Bug description: Sometimes when I open Firefox and play a video or start Plex Media Player or start to play a game I get a distorted audio/sound. I modified the Pulse Audio daemon.conf by this tutorial https://medium.com/@gamunu/enable-high-quality-audio-on- linux-6f16f3fe7e1f to improve the sound in Linux. The deamon.conf should be attached. When I get this issue I have to open a terminal and enter »pulseaudio -k«. After this it's normal again. Here's a complete hwinfo: https://gist.github.com/Johnnii360/1cbdbb0f27180013652a01f21c2f4792 My sound card is a Creative SoundBlaster X-Fi Titanium Fatal1ty (EMU20k2). Kernel version: 5.4.0-84-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 14 12:25:30 2021 InstallationDate: Installed on 2019-11-10 (674 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.40 dmi.board.name: Z390 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be F
[Desktop-packages] [Bug 1943569] Re: Sometimes distorted sound in or after Firefox
** Attachment added: "daemon.conf" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1943569/+attachment/5525159/+files/daemon.conf -- 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/1943569 Title: Sometimes distorted sound in or after Firefox Status in pulseaudio package in Ubuntu: New Bug description: Sometimes when I open Firefox and play a video or start Plex Media Player or start to play a game I get a distorted audio/sound. I modified the Pulse Audio daemon.conf by this tutorial https://medium.com/@gamunu/enable-high-quality-audio-on- linux-6f16f3fe7e1f to improve the sound in Linux. The deamon.conf should be attached. When I get this issue I have to open a terminal and enter »pulseaudio -k«. After this it's normal again. Here's a complete hwinfo: https://gist.github.com/Johnnii360/1cbdbb0f27180013652a01f21c2f4792 My sound card is a Creative SoundBlaster X-Fi Titanium Fatal1ty (EMU20k2). Kernel version: 5.4.0-84-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 14 12:25:30 2021 InstallationDate: Installed on 2019-11-10 (674 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.40 dmi.board.name: Z390 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-05-31T09:26:29.202354 mtime.conffile..etc.pulse.daemon.conf: 2020-12-26T09:12:04.962975 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1943569/+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 1732117] Re: PPA for stable ("still") versions
This exists, see https://launchpad.net/~libreoffice/+archive/libreoffice-still.
So I mark "Fix Released".
Please correct if wrong.
--
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/1732117
Title:
PPA for stable ("still") versions
Status in libreoffice package in Ubuntu:
Triaged
Bug description:
I would like to have a PPA that follows the stable ("still")
LibreOffice version.
The "still" LibreOffice version is encouraged for users that want
stability. According to LibreOffice.org :
"If you deploy LibreOffice in an enterprise or corporate environment
or are a conservative user, please choose this version."
I am not a corporate user, but I prefer stable packages, as I have hit
the occasional bug in the "fresh" version.
Therefore, I am using LibreOffice 5.3 at the moment. I was shocked to
find out that the last maintenance update has been released around Oct
29, 2017, and the "End of Life" is coming as quickly as November 26,
2017. That's less than a month to manually upgrade all my PCs to the
5.4 version. A "still" PPA is something I can install and forget.
Actually, using PPAs for fixed versions, like 5.2, should be
discouraged on this website, as they are no longer receiving security
updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1732117/+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 1882879] Re: Filled out form fields disappear after saving to docx/doc with LibreOffice writer.
Not sure why you reported this if already resolved. Please close. -- 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/1882879 Title: Filled out form fields disappear after saving to docx/doc with LibreOffice writer. Status in libreoffice package in Ubuntu: New Bug description: Ubuntu Version: Ubuntu 20.04 LTS Package version: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1amd64 Steps to reproduce: === 1. Open a docx containing forms such as the attached IPR declaration form. 2. Fill out some of the form fields. 3. Save the file and reopen it with LibreOffice writer. 4. Form fields that have been filled out are no longer visible. Fix: - Updating LibreOffice to 6.4.4 (either from the official site or from ppa:libreoffice/ppa fixes this problem. Further Notes: == - The form data can actually be recovered by opening the file with AbiWord (to my best knowledge, neighter Microsoft Word nor the fixed version of LibreOffice are able to recover the data). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 07:42:44 2020 SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-04-13 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1882879/+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 1732117] Re: PPA for stable ("still") versions
It's true, the "still" PPA is finally there!
--
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/1732117
Title:
PPA for stable ("still") versions
Status in libreoffice package in Ubuntu:
Triaged
Bug description:
I would like to have a PPA that follows the stable ("still")
LibreOffice version.
The "still" LibreOffice version is encouraged for users that want
stability. According to LibreOffice.org :
"If you deploy LibreOffice in an enterprise or corporate environment
or are a conservative user, please choose this version."
I am not a corporate user, but I prefer stable packages, as I have hit
the occasional bug in the "fresh" version.
Therefore, I am using LibreOffice 5.3 at the moment. I was shocked to
find out that the last maintenance update has been released around Oct
29, 2017, and the "End of Life" is coming as quickly as November 26,
2017. That's less than a month to manually upgrade all my PCs to the
5.4 version. A "still" PPA is something I can install and forget.
Actually, using PPAs for fixed versions, like 5.2, should be
discouraged on this website, as they are no longer receiving security
updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1732117/+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 1883174] Re: Some (or all) desktop icons are missing
Hello, This issue is still on, and even if it's «low» issue, it's really disturbing because 20.04 is LTS. I planned to move dozens of computers from 18.04 to 20.04, but seeing how my users rely on desktop to keep many files, I can see how painful it will be to move on 20.04, even though alt F2 + r works fine. Is there anything, besides coding, that could be done to help taking down this issue ? Thanks, -- 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/1883174 Title: Some (or all) desktop icons are missing Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+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 1943593] [NEW] Drop-down menus cannot be opened in Firefox add-ons in Wayland session
Public bug reported: Drop-down menus in add-ons such as Bitwarden and Joplin Notes cannot be opened/expanded in Firefox 92.0+build3-0ubuntu0.21.04.1 under Wayland with AMD graphics. This issue is not present in an Xorg session. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 92.0+build3-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kamil 314232 F pulseaudio /dev/snd/controlC2: kamil 314232 F pulseaudio /dev/snd/controlC0: kamil 314232 F pulseaudio BuildID: 20210903235534 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Sep 14 21:24:14 2021 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:358 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-04-24 (143 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.249 metric 100 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:358 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=92.0/20210903235534 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS PRO AX 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.:bvrF1:bd08/04/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSPROAX:pvrDefaultstring:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSPROAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS PRO AX dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1943593 Title: Drop-down menus cannot be opened in Firefox add-ons in Wayland session Status in firefox package in Ubuntu: New Bug description: Drop-down menus in add-ons such as Bitwarden and Joplin Notes cannot be opened/expanded in Firefox 92.0+build3-0ubuntu0.21.04.1 under Wayland with AMD graphics. This issue is not present in an Xorg session. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 92.0+build3-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kamil 314232 F pulseaudio /dev/snd/controlC2: kamil 314232 F pulseaudio /dev/snd/controlC0: kamil 314232 F pulseaudio BuildID: 20210903235534 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Sep 14 21:24:14 2021 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:358 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate
[Desktop-packages] [Bug 1943240] Re: libreoffice 7.2.0.4 snap Error "Image filter not found" when trying to insert JPG
It should be fixed in the current stable version by https://github.com/ubuntu/libreoffice/commit/ce769e30 ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released -- 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/1943240 Title: libreoffice 7.2.0.4 snap Error "Image filter not found" when trying to insert JPG Status in libreoffice package in Ubuntu: Fix Released Bug description: Description: JPG files can't be inserted into LibreOffice writer document. Files already containing JPG files only show blank containers. LibreOffice Writer 7.2.0.4 from current Ubuntu Snap repository on Ubuntu 20.04 LTS Steps to Reproduce: 1) Start LibreOffice Writer 2) Create new file 3) Insert -> Image -> Select a JPG file Actual Results: Error "Image filter not found" and no image inserted Expected Results: JPG image should be inserted Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Inserting a PNG image works though [Information automatically included from LibreOffice] Locale: us Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes LibreOffice Writer 7.2.0.4 from current Ubuntu Snap repository Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1943240/+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 1883174] Re: Some (or all) desktop icons are missing
As a patch, is there way that the "r" command could be automatically issued at the end of the boot sequence? I briefly tried to get that to work, but didn't have any luck. On 9/14/2021 5:52 AM, Florian wrote: > Hello, > > This issue is still on, and even if it's «low» issue, it's really > disturbing because 20.04 is LTS. I planned to move dozens of computers > from 18.04 to 20.04, but seeing how my users rely on desktop to keep > many files, I can see how painful it will be to move on 20.04, even > though alt F2 + r works fine. > > Is there anything, besides coding, that could be done to help taking > down this issue ? > > Thanks, > -- 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/1883174 Title: Some (or all) desktop icons are missing Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+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 1943593] Re: Drop-down menus cannot be opened in Firefox add-ons in Wayland session
** Attachment removed: "Profile0Prefs.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1943593/+attachment/5525203/+files/Profile0Prefs.txt -- 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/1943593 Title: Drop-down menus cannot be opened in Firefox add-ons in Wayland session Status in firefox package in Ubuntu: New Bug description: Drop-down menus in add-ons such as Bitwarden and Joplin Notes cannot be opened/expanded in Firefox 92.0+build3-0ubuntu0.21.04.1 under Wayland with AMD graphics. This issue is not present in an Xorg session. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 92.0+build3-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kamil 314232 F pulseaudio /dev/snd/controlC2: kamil 314232 F pulseaudio /dev/snd/controlC0: kamil 314232 F pulseaudio BuildID: 20210903235534 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Sep 14 21:24:14 2021 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:358 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-04-24 (143 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.249 metric 100 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:358 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=92.0/20210903235534 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS PRO AX 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.:bvrF1:bd08/04/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSPROAX:pvrDefaultstring:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSPROAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS PRO AX dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1943593/+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 1883174] Re: Some (or all) desktop icons are missing
I think that the only solution is to uninstall Desktop Icons and install Desktop Icons NG. Although current versions are for Gnome Shell 3.38 and later, there are active versions in extensions.gnome.org that do work with Gnome Shell 3.36. -- 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/1883174 Title: Some (or all) desktop icons are missing Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+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 1943593] Re: Drop-down menus cannot be opened in Firefox add-ons in Wayland session
** Description changed: - Drop-down menus in add-ons such as Bitwarden and Joplin Notes cannot be - opened/expanded in Firefox 92.0+build3-0ubuntu0.21.04.1 under Wayland - with AMD graphics. This issue is not present in an Xorg session. + Drop-down menus in add-ons such as Bitwarden and Joplin Notes Web + Clipper cannot be opened/expanded in Firefox + 92.0+build3-0ubuntu0.21.04.1 under Wayland with AMD graphics. This issue + is not present in an Xorg session. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 92.0+build3-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: kamil 314232 F pulseaudio - /dev/snd/controlC2: kamil 314232 F pulseaudio - /dev/snd/controlC0: kamil 314232 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: kamil 314232 F pulseaudio + /dev/snd/controlC2: kamil 314232 F pulseaudio + /dev/snd/controlC0: kamil 314232 F pulseaudio BuildID: 20210903235534 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Sep 14 21:24:14 2021 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:358 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-04-24 (143 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: - default via 192.168.1.1 dev eno1 proto dhcp metric 100 - 169.254.0.0/16 dev eno1 scope link metric 1000 - 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.249 metric 100 + default via 192.168.1.1 dev eno1 proto dhcp metric 100 + 169.254.0.0/16 dev eno1 scope link metric 1000 + 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.249 metric 100 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:358 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: - Profile1 (Default) - LastVersion=None/None (Out of date) - Profile0 - LastVersion=92.0/20210903235534 (In use) + Profile1 (Default) - LastVersion=None/None (Out of date) + Profile0 - LastVersion=92.0/20210903235534 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS PRO AX 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.:bvrF1:bd08/04/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSPROAX:pvrDefaultstring:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSPROAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS PRO AX dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- 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/1943593 Title: Drop-down menus cannot be opened in Firefox add-ons in Wayland session Status in firefox package in Ubuntu: New Bug description: Drop-down menus in add-ons such as Bitwarden and Joplin Notes Web Clipper cannot be opened/expanded in Firefox 92.0+build3-0ubuntu0.21.04.1 under Wayland with AMD graphics. This issue is not present in an Xorg session. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 92.0+build3-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kamil 31
[Desktop-packages] [Bug 1943593] Re: Drop-down menus cannot be opened in Firefox add-ons in Wayland session
** Description changed: Drop-down menus in add-ons such as Bitwarden and Joplin Notes Web Clipper cannot be opened/expanded in Firefox 92.0+build3-0ubuntu0.21.04.1 under Wayland with AMD graphics. This issue is not present in an Xorg session. + + Observed behaviour: + Clicking on the displayed menu item or down-arrow does not respond at all and does not reveal menu options. + + Expected behaviour: + Drop-down menu opens and shows all menu options. + + Workaround: + Click on menu item and use keyboard arrow keys to choose desired option + ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 92.0+build3-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kamil 314232 F pulseaudio /dev/snd/controlC2: kamil 314232 F pulseaudio /dev/snd/controlC0: kamil 314232 F pulseaudio BuildID: 20210903235534 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Sep 14 21:24:14 2021 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:358 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-04-24 (143 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.249 metric 100 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:358 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=92.0/20210903235534 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS PRO AX 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.:bvrF1:bd08/04/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSPROAX:pvrDefaultstring:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSPROAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS PRO AX dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- 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/1943593 Title: Drop-down menus cannot be opened in Firefox add-ons in Wayland session Status in firefox package in Ubuntu: New Bug description: Drop-down menus in add-ons such as Bitwarden and Joplin Notes Web Clipper cannot be opened/expanded in Firefox 92.0+build3-0ubuntu0.21.04.1 under Wayland with AMD graphics. This issue is not present in an Xorg session. Observed behaviour: Clicking on the displayed menu item or down-arrow does not respond at all and does not reveal menu options. Expected behaviour: Drop-down menu opens and shows all menu options. Workaround: Click on menu item and use keyboard arrow keys to choose desired option ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 92.0+build3-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kamil 314232 F pulseaudio /dev/snd/controlC2: kamil 314232 F pulseaudio /dev/snd/controlC0: kamil 314232
[Desktop-packages] [Bug 1244714] Re: pppd on new Precise HWE kernels fails, but works on 3.2
This bug is probably fixed but I'll mark it as incomplete hoping that someone would take the time to test it with supported versions. ** Changed in: ppp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1244714 Title: pppd on new Precise HWE kernels fails, but works on 3.2 Status in ppp package in Ubuntu: Incomplete Bug description: Connecting to an IPsec/L2TP tunnel works when using the 3.2 kernel shipped with Precise 12.04 but fails with the most recent HWE kernel (3.8 from 12.04.3). With the 3.8 kernel here is how pppd dies: Oct 25 11:31:24 l2tp-udesktop pppd[2758]: Plugin pppol2tp.so loaded. Oct 25 11:31:24 l2tp-udesktop pppd[2758]: pppd options in effect: Oct 25 11:31:24 l2tp-udesktop pppd[2758]: debug debug#011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: nodetach#011#011# (from command line) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: idle 72000#011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: ktune#011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: dump#011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: plugin pppol2tp.so#011#011# (from command line) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: noauth#011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: refuse-chap#011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: refuse-mschap#011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: refuse-mschap-v2#011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: refuse-eap#011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: name myname#011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: password ??#011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop pppd[2758]: remotename #011#011# (from /etc/ppp/Checkpoint.options.xl2tpd) Oct 25 11:31:24 l2tp-udesktop kernel: [ 246.621763] pppd[2758]: segfault at 0 ip 0041f1d0 sp 7fff1da9bf10 error 4 in pppd[40+49000] Information about the affected system: root@l2tp-udesktop:~# lsb_release -rd Description:Ubuntu 12.04.3 LTS Release:12.04 root@l2tp-udesktop:~# apt-cache policy ppp ppp: Installed: 2.4.5-5ubuntu1 Candidate: 2.4.5-5ubuntu1 Version table: *** 2.4.5-5ubuntu1 0 500 http://ca.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status root@l2tp-udesktop:~# dpkg -l| grep linux-image ii linux-image-3.2.0-54-virtual3.2.0-54.82 Linux kernel image for version 3.2.0 on 64 bit x86 Virtual Guests ii linux-image-3.8.0-30-generic3.8.0-30.44~precise1 Linux kernel image for version 3.8.0 on 64 bit x86 SMP ii linux-image-generic-lts-raring 3.8.0.30.30 Generic Linux kernel image ii linux-image-virtual 3.2.0.54.64 Linux kernel image for virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1244714/+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 1943417] Re: Xorg freeze
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943417 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: ubuntu freezes frequently. can't even able to shutdown the system so i have to press the power button ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 13 11:36:03 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics [103c:85f1] InstallationDate: Installed on 2021-08-24 (19 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 30c9:0035 Luxvisions Innotech Limited HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 2, Class=Application Specific Interface, Driver=, 480M MachineType: HP HP Laptop 15s-du1xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=b978107e-eaec-49de-9940-8be83bba3111 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2021 dmi.bios.release: 15.43 dmi.bios.vendor: Insyde dmi.bios.version: F.43 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85F1 dmi.board.vendor: HP dmi.board.version: 37.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.28 dmi.modalias: dmi:bvnInsyde:bvrF.43:bd03/31/2021:br15.43:efr37.28:svnHP:pnHPLaptop15s-du1xxx:pvrType1ProductConfigId:sku25U57PA#ACJ:rvnHP:rn85F1:rvr37.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-du1xxx dmi.product.sku: 25U57PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1943417/+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 1943328] Re: display 1920x1080 not showing in setting
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943328 Title: display 1920x1080 not showing in setting Status in xorg package in Ubuntu: New Bug description: display 1920x1080 not showing in setting. i cant change my display. everything looks bigger and ugly ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 11 19:27:58 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Generation Core Processor Family Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2021-09-10 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=bb5421d7-dc24-45ad-8107-199e6e049a18 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd07/10/2018:br4.6:svnMSI:pnMS-7817:pvr1.0:skuTobefilledbyO.E.M.:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 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/xorg/+bug/1943328/+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 1943614] Re: ubuntu-drivers crashes in python3-click when ubiquity runs the Polish language (locale)
This is not an issue in later Ubuntu releases due to a behavior change in python itself: it will apparently now fall back to C.UTF-8 if the locale is invalid. ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943614 Title: ubuntu-drivers crashes in python3-click when ubiquity runs the Polish language (locale) Status in ubiquity package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in ubiquity source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: New Bug description: [Impact] Ok, first of all - I am unsure if this is a regression or not, since I did not test extra drivers with old images. I'm testing this on kvm now. So far this bug appeared for me when I was running ubiquity with secureboot enabled on a NVidia GPU machine. Note: this only happens when the language selection is done on the Ubiquity screen. If you get the language right in the isolinux menu, everything works. Basically when installing Ubuntu desktop on a system that uses ubuntu- drivers but using a non-standard locale (like in my case, the Polish language from the language selector), ubuntu-drivers will crash with: ` Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 480, in greet() File "/usr/lib/python3/dist-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 676, in main _verify_python3_env() File "/usr/lib/python3/dist-packages/click/_unicodefun.py", line 118, in _verify_python3_env 'for mitigation steps.' + extra) RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps. This system supports the C.UTF-8 locale which is recommended. You might be able to resolve your issue by exporting the following environment variables: export LC_ALL=C.UTF-8 export LANG=C.UTF-8 Click discovered that you exported a UTF-8 locale but the locale system could not pick up from it because it does not exist. The exported locale is "pl_PL.UTF-8" but it is not supported ubuntu-drivers autoinstall failed with code: 1 ` [Test Case] * Download latest 18.04.6 candidate image for ubuntu-desktop * In language selector, select Polish (Polski) * Proceed with the installation and checking "Install third-party software..." * Boot into the installed system * Check if `ubuntu-drivers install ...` succeeded during installation, checking the installer syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943614/+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 1940504] Re: Support Alder Lake P graphics
Hello Timo, or anyone else affected,
Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.17 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: linux-firmware (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1940504
Title:
Support Alder Lake P graphics
Status in libdrm package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in mesa package in Ubuntu:
Fix Released
Status in libdrm source package in Focal:
Fix Committed
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
New
Status in mesa source package in Focal:
Fix Committed
Bug description:
[SRU Justification:linux-firmware]
[Impact]
It shows the firmware is missing, and runtime power management has been
disabled:
i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.
[Fix]
Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").
[Test Case]
Verified on Intel ADL-M/ADL-P RVPs.
[Where problems could occur]
It's a new firmware for new GPU, not possible to introduce
regressions.
[Other Info]
Impish has this already. And while ADL-P/M support begins since v5.14,
only focal (for oem-5.14) is being nominated.
=
[SRU Justification:mesa,libdrm]
NOTE: this is for focal only, hirsute/impish do not and will not have
kernel support for this.
[Impact]
ADL-P machines need to use the native driver.
[Fix]
Backport support from upstream.
libdrm: a single patch from 2.4.107
mesa: three commits to add pci-id's and a workaround
kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
[Test case]
Boot a machine and check that it's using the native driver and that the usual
workloads are fine.
[Where things could go wrong]
For older gpu's there's little to go wrong, since the commits are for ADL-P
only.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer
Okay today it really happened again after standby mode. I got nothing about a crash in /var/crash and in my https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4 isn't something either. Magic SysRq couldn't be used because the system was completely frozen. This is the only thing I can offer you, but maybe it will not help you: 20:16:17 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps 20:12:43 gvfsd-dnssd: Error calling org.gtk.vfs.MonitorClient.Changed(): Zeitüberschreitung wurde erreicht (g-io-error-quark, 24) 20:12:43 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps 20:12:13 Xorg: (II) event1 - Power Button: device is a keyboard 20:12:13 gnome-shell: cr_declaration_parse_list_from_buf: assertion 'parser' failed 20:12:13 Xorg: (II) event8 - Logitech Gaming Mouse G502 Keyboard: device is a keyboard 20:12:13 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps 20:12:13 Xorg: (II) systemd-logind: got resume for 13:69 20:12:12 psensor: [2021-09-14T18:12:12] [ERR] nvctrl: Failed to retrieve measure of type 20204 for NVIDIA GPU 1 20:12:12 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps 19:14:29 Xorg: (II) systemd-logind: got pause for 13:65 19:14:28 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps -- 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/1930192 Title: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter- offscreen-effect.c:213: Unable to create an Offscreen buffer Status in mutter package in Ubuntu: Incomplete Bug description: Addition for bug report 1930128 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Sat May 29 12:20:21 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1608008084 GsettingsChanges: b'org.gnome.desktop.background' b'show-desktop-icons' b'true' b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true' b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false' b'org.gnome.desktop.session' b'idle-delay' b'uint32 0' InstallationDate: Installed on 2019-11-10 (566 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /var/lib/gdm3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930192/+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 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer
Ooookay... I've seen a comment in the Ubuntu Software Center at the Firefox that the Firefox cause this weird freezes. -- 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/1930192 Title: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter- offscreen-effect.c:213: Unable to create an Offscreen buffer Status in mutter package in Ubuntu: Incomplete Bug description: Addition for bug report 1930128 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Sat May 29 12:20:21 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1608008084 GsettingsChanges: b'org.gnome.desktop.background' b'show-desktop-icons' b'true' b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true' b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false' b'org.gnome.desktop.session' b'idle-delay' b'uint32 0' InstallationDate: Installed on 2019-11-10 (566 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /var/lib/gdm3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930192/+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 1898601] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 l
[Desktop-packages] [Bug 1898601] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g
[Desktop-packages] [Bug 1898601] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 lib
[Desktop-packages] [Bug 1898601] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g
[Desktop-packages] [Bug 1914374] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in OEM Priority Project: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubiquity source package in Groovy: Won't Fix Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+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 1931514] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Fix Committed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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 1931514] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Fix Committed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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 1914374] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in OEM Priority Project: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubiquity source package in Groovy: Won't Fix Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+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 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Tags removed: verification-needed-bionic ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in OEM Priority Project: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubiquity source package in Groovy: Won't Fix Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+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 1931514] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Fix Committed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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 1914374] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in OEM Priority Project: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubiquity source package in Groovy: Won't Fix Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+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 1914051] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914051 Title: `ubuntu-drivers list-oem --package-list` is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: This is the call Ubiquity is making to decide what OEM packages to install. With the current focal-updates version root@ubuntu-drivers-common-test:~# apt policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.3~0.20.04.2 Candidate: 1:0.8.6.3~0.20.04.2 Version table: *** 1:0.8.6.3~0.20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo Usage: ubuntu-drivers list-oem [OPTIONS] [LIST_OEM]... Try "ubuntu-drivers list-oem -h" for help. Error: no such option: --package-list With the focal release version: root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo root@ubuntu-drivers-common-test:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1914051/+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 1931514] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Fix Committed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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 1913651] Re: /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu-drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Tags removed: verification-needed-bionic ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1913651 Title: /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu- drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-drivers-common. This problem was most recently seen with package version 1:0.8.6.3~0.20.10.1, the problem page at https://errors.ubuntu.com/problem/a5320fbf71298787ff2595cc2b8227783b068dae contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. There is also this bucket: https://errors.ubuntu.com/problem/fb18ad88544e0c025b2c9ec591b91c080d23401d If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1913651/+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 1914051] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914051 Title: `ubuntu-drivers list-oem --package-list` is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: This is the call Ubiquity is making to decide what OEM packages to install. With the current focal-updates version root@ubuntu-drivers-common-test:~# apt policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.3~0.20.04.2 Candidate: 1:0.8.6.3~0.20.04.2 Version table: *** 1:0.8.6.3~0.20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo Usage: ubuntu-drivers list-oem [OPTIONS] [LIST_OEM]... Try "ubuntu-drivers list-oem -h" for help. Error: no such option: --package-list With the focal release version: root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo root@ubuntu-drivers-common-test:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1914051/+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 1913651] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1913651 Title: /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu- drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-drivers-common. This problem was most recently seen with package version 1:0.8.6.3~0.20.10.1, the problem page at https://errors.ubuntu.com/problem/a5320fbf71298787ff2595cc2b8227783b068dae contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. There is also this bucket: https://errors.ubuntu.com/problem/fb18ad88544e0c025b2c9ec591b91c080d23401d If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1913651/+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 1913651] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1913651 Title: /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu- drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-drivers-common. This problem was most recently seen with package version 1:0.8.6.3~0.20.10.1, the problem page at https://errors.ubuntu.com/problem/a5320fbf71298787ff2595cc2b8227783b068dae contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. There is also this bucket: https://errors.ubuntu.com/problem/fb18ad88544e0c025b2c9ec591b91c080d23401d If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1913651/+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 1914051] Re: `ubuntu-drivers list-oem --package-list` is broken
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Tags removed: verification-needed-bionic ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914051 Title: `ubuntu-drivers list-oem --package-list` is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: This is the call Ubiquity is making to decide what OEM packages to install. With the current focal-updates version root@ubuntu-drivers-common-test:~# apt policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.3~0.20.04.2 Candidate: 1:0.8.6.3~0.20.04.2 Version table: *** 1:0.8.6.3~0.20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo Usage: ubuntu-drivers list-oem [OPTIONS] [LIST_OEM]... Try "ubuntu-drivers list-oem -h" for help. Error: no such option: --package-list With the focal release version: root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo root@ubuntu-drivers-common-test:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1914051/+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 1931514] Re: SRU: The NVIDIA X server Settings is blank when under Intel mode
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Tags removed: verification-needed-bionic ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Fix Committed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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 1913651] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1913651 Title: /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu- drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-drivers-common. This problem was most recently seen with package version 1:0.8.6.3~0.20.10.1, the problem page at https://errors.ubuntu.com/problem/a5320fbf71298787ff2595cc2b8227783b068dae contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. There is also this bucket: https://errors.ubuntu.com/problem/fb18ad88544e0c025b2c9ec591b91c080d23401d If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1913651/+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 1914051] Proposed package removed from archive
The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914051 Title: `ubuntu-drivers list-oem --package-list` is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: This is the call Ubiquity is making to decide what OEM packages to install. With the current focal-updates version root@ubuntu-drivers-common-test:~# apt policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.3~0.20.04.2 Candidate: 1:0.8.6.3~0.20.04.2 Version table: *** 1:0.8.6.3~0.20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo Usage: ubuntu-drivers list-oem [OPTIONS] [LIST_OEM]... Try "ubuntu-drivers list-oem -h" for help. Error: no such option: --package-list With the focal release version: root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo root@ubuntu-drivers-common-test:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1914051/+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 1943614] Re: ubuntu-drivers crashes in python3-click when ubiquity runs the Polish language (locale)
Hello Łukasz, or anyone else affected, Accepted ubuntu-drivers-common into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.8.6.3~0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943614 Title: ubuntu-drivers crashes in python3-click when ubiquity runs the Polish language (locale) Status in ubiquity package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in ubiquity source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: [Impact] Ok, first of all - I am unsure if this is a regression or not, since I did not test extra drivers with old images. I'm testing this on kvm now. So far this bug appeared for me when I was running ubiquity with secureboot enabled on a NVidia GPU machine. Note: this only happens when the language selection is done on the Ubiquity screen. If you get the language right in the isolinux menu, everything works. Basically when installing Ubuntu desktop on a system that uses ubuntu- drivers but using a non-standard locale (like in my case, the Polish language from the language selector), ubuntu-drivers will crash with: ` Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 480, in greet() File "/usr/lib/python3/dist-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 676, in main _verify_python3_env() File "/usr/lib/python3/dist-packages/click/_unicodefun.py", line 118, in _verify_python3_env 'for mitigation steps.' + extra) RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps. This system supports the C.UTF-8 locale which is recommended. You might be able to resolve your issue by exporting the following environment variables: export LC_ALL=C.UTF-8 export LANG=C.UTF-8 Click discovered that you exported a UTF-8 locale but the locale system could not pick up from it because it does not exist. The exported locale is "pl_PL.UTF-8" but it is not supported ubuntu-drivers autoinstall failed with code: 1 ` [Test Case] * Download latest 18.04.6 candidate image for ubuntu-desktop * In language selector, select Polish (Polski) * Proceed with the installation and checking "Install third-party software..." * Boot into the installed system * Check if `ubuntu-drivers install ...` succeeded during installation, checking the installer syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943614/+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 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state
This worked for me Thank you David Henningsson (diwic)
Sorry if i post wrong, is my first comment
Change /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
from:
[Jack Front Headphone]
required-any = any
[Jack Headphone]
required-any = any
to :
# [Jack Front Headphone]
# required-any = any
# [Jack Headphone]
# required-any = any
...restart pulseaudio (or the computer) for changes to take effect.
--
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/874535
Title:
Volume Slider Jumps, due to rapidly changing hardware jack sense state
Status in alsa-driver package in Ubuntu:
Triaged
Bug description:
In Oneiric Release, The volume slider randomly jump down a notch or
two for fraction of a second, even when there is no audio playing on
the system. If mute is selected, the menu will quickly flip out of
mute mode and back again. This change actually affects the audio
output, resulting in pops correlated with the volume changes.
nVidia GF106 Audio Controller
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jfrorie9959 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54'
Mixer name : 'Realtek ALC892'
Components : 'HDA:10ec0892,1462522c,00100302'
Controls : 35
Simple ctrls : 20
Card2.Amixer.info:
Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card2.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Package: pulseaudio 1:1.0-0ubuntu3.1
PackageArchitecture: amd64
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Tags: oneiric running-unity
Uname: Linux 3.0.0-14-generic x86_64
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/16/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V25.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: X58A-GD45 (MS-7522)
dmi.board.vendor: MSI
dmi.board.version: 5.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 5.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/16/2010:svnMSI:pnMS-7522:pvr5.0:rvnMSI:rnX58A-GD45(MS-7522):rvr5.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr5.0:
dmi.product.name: MS-7522
dmi.product.version: 5.0
dmi.sys.vendor: MSI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/+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 1939938] Re: dialog asking for restart appears on close of rhythmbox
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox-plugin-alternative-toolbar in Ubuntu. https://bugs.launchpad.net/bugs/1939938 Title: dialog asking for restart appears on close of rhythmbox Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu: Fix Committed Bug description: following last update to rhythmbox dialog box now appears at every closure of rhythmbox from top bar Ubuntu 21.10 image from 13/08 lenovo thinkpad T430 250gb ssd 16gb ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1939938/+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 1943637] [NEW] Screensaver is invisible when activated by lid close
Public bug reported: My power management settings are set to lock screen when the lid is closed. When this happens, the screensaver activates, but is not visible (desktop can't be interacted with, typing password and pressing enter unlocks it). I'm running Xubuntu and have tried: * xscreensaver instead of xfce4-screensaver * slick-greeter instead of lightdm-gtk-greeter Which made no difference. I'm now using sddm instead of lightdm and no longer having this problem, so I believe the bug is in lightdm. This is possible a duplicate of #1853709, but I'm unsure as that one is specifically talking about suspend, mine is set to lock, not suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1 Uname: Linux 5.13.0-1012-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 14 21:10:01 2021 InstallationDate: Installed on 2021-07-01 (75 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: My power management settings are set to lock screen when the lid is closed. When this happens, the screensaver activates, but is not visible (desktop can't be interacted with, typing password and pressing enter unlocks it). - I'm running Xubuntu and have tried: * xscreensaver instead of xfce4-screensaver * slick-greeter instead of lightdm-gtk-greeter Which made no difference. I'm now using sddm instead of lightdm and no - longer having this problem, so I believe the bug is in lightdm. + longer having this problem, so I believe the bug is in lightdm. This is + possible a duplicate of #1853709, but I'm unsure as that one is + specifically talking about suspend, mine is set to lock, not suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1 Uname: Linux 5.13.0-1012-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 14 21:10:01 2021 InstallationDate: Installed on 2021-07-01 (75 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1943637 Title: Screensaver is invisible when activated by lid close Status in lightdm package in Ubuntu: New Bug description: My power management settings are set to lock screen when the lid is closed. When this happens, the screensaver activates, but is not visible (desktop can't be interacted with, typing password and pressing enter unlocks it). I'm running Xubuntu and have tried: * xscreensaver instead of xfce4-screensaver * slick-greeter instead of lightdm-gtk-greeter Which made no difference. I'm now using sddm instead of lightdm and no longer having this problem, so I believe the bug is in lightdm. This is possible a duplicate of #1853709, but I'm unsure as that one is specifically talking about suspend, mine is set to lock, not suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1 Uname: Linux 5.13.0-1012-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 14 21:10:01 2021 InstallationDate: Installed on 2021-07-01 (75 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1943637/+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 1943534] [NEW] Properties of the OS show the kernel version
You have been subscribed to a public bug: [08:37:46] Is it too much to ask that the properties of the OS would also show the kernel version? I have 20.04 LTS. Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-gnome-desktop (not installed) ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 14 08:58:52 2021 InstallationDate: Installed on 2020-04-23 (508 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubuntu-gnome-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Properties of the OS show the kernel version https://bugs.launchpad.net/bugs/1943534 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center 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 1943534] Re: Properties of the OS show the kernel version
Already reported directly to the GNOME developers: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1112 ** Package changed: ubuntu-gnome-meta (Ubuntu) => gnome-control-center (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1112 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1112 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1112 Importance: Unknown Status: Unknown ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed ** Summary changed: - Properties of the OS show the kernel version + Add kernel version to 'About' page in Settings -- 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/1943534 Title: Add kernel version to 'About' page in Settings Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Bug description: [08:37:46] Is it too much to ask that the properties of the OS would also show the kernel version? I have 20.04 LTS. Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-gnome-desktop (not installed) ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 14 08:58:52 2021 InstallationDate: Installed on 2020-04-23 (508 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubuntu-gnome-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1943534/+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 1939938] Re: dialog asking for restart appears on close of rhythmbox
This bug was fixed in the package rhythmbox-plugin-alternative-toolbar - 0.20.1-0ubuntu1 --- rhythmbox-plugin-alternative-toolbar (0.20.1-0ubuntu1) impish; urgency=medium * Bug fix release - revert plugin settings restart info introduced in 0.20.0 since this caused a dialog repeatedly being asked on exit (LP: #1939938) - Latest translations from the impish track on launchpad -- David Mohammed Tue, 14 Sep 2021 19:56:20 +0100 ** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox-plugin-alternative-toolbar in Ubuntu. https://bugs.launchpad.net/bugs/1939938 Title: dialog asking for restart appears on close of rhythmbox Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu: Fix Released Bug description: following last update to rhythmbox dialog box now appears at every closure of rhythmbox from top bar Ubuntu 21.10 image from 13/08 lenovo thinkpad T430 250gb ssd 16gb ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1939938/+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 1943614] Re: ubuntu-drivers crashes in python3-click when ubiquity runs the Polish language (locale)
I tested this using Steve's more minimal test case from #ubuntu-release (https://irclogs.ubuntu.com/2021/09/14/%23ubuntu-release.html#t16:25) and did not receive a crash with the version of ubuntu-drivers-common from -proposed. Setting up ubuntu-drivers-common (1:0.8.6.3~0.18.04.2) ... Processing triggers for libc-bin (2.27-3ubuntu1.4) ... (bionic-amd64)root@impulse:/home/bdmurray/# LANG=pl_PL.UTF-8 ubuntu-drivers autoinstall WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid Support Legacyheader, cannot determine support level Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943614 Title: ubuntu-drivers crashes in python3-click when ubiquity runs the Polish language (locale) Status in ubiquity package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in ubiquity source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: [Impact] Ok, first of all - I am unsure if this is a regression or not, since I did not test extra drivers with old images. I'm testing this on kvm now. So far this bug appeared for me when I was running ubiquity with secureboot enabled on a NVidia GPU machine. Note: this only happens when the language selection is done on the Ubiquity screen. If you get the language right in the isolinux menu, everything works. Basically when installing Ubuntu desktop on a system that uses ubuntu- drivers but using a non-standard locale (like in my case, the Polish language from the language selector), ubuntu-drivers will crash with: ` Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 480, in greet() File "/usr/lib/python3/dist-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 676, in main _verify_python3_env() File "/usr/lib/python3/dist-packages/click/_unicodefun.py", line 118, in _verify_python3_env 'for mitigation steps.' + extra) RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps. This system supports the C.UTF-8 locale which is recommended. You might be able to resolve your issue by exporting the following environment variables: export LC_ALL=C.UTF-8 export LANG=C.UTF-8 Click discovered that you exported a UTF-8 locale but the locale system could not pick up from it because it does not exist. The exported locale is "pl_PL.UTF-8" but it is not supported ubuntu-drivers autoinstall failed with code: 1 ` [Test Case] * Download latest 18.04.6 candidate image for ubuntu-desktop * In language selector, select Polish (Polski) * Proceed with the installation and checking "Install third-party software..." * Boot into the installed system * Check if `ubuntu-drivers install ...` succeeded during installation, checking the installer syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943614/+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 1943645] [NEW] Please remove gnome-getting-started-docs from impish
Public bug reported: It was just removed from unstable — see Debian bug — but due to Ubuntu's language split it probably needs to be removed manually here. $ apt rdepends gnome-getting-started-docs* gnome-getting-started-docs Reverse Depends: Depends: gnome-getting-started-docs-as (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-zh-tw (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-zh-hk (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-uk (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-te (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ta (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-sv (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-sr (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-sk (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ru (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ro (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-pt (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-pl (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-pa (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-nl (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-mr (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-lv (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-lt (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ko (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-kn (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ja (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-it (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-id (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-hu (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-hr (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-hi (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-he (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-gu (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-gl (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-fr (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-fi (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-fa (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-es (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-eo (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-el (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-de (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-da (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-cs (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ca (= 3.36.2+git20201004.1-0ubuntu1) gnome-getting-started-docs-as Reverse Depends: gnome-getting-started-docs-ca Reverse Depends: gnome-getting-started-docs-cs Reverse Depends: gnome-getting-started-docs-da Reverse Depends: gnome-getting-started-docs-de Reverse Depends: gnome-getting-started-docs-el Reverse Depends: gnome-getting-started-docs-eo Reverse Depends: gnome-getting-started-docs-es Reverse Depends: gnome-getting-started-docs-fa Reverse Depends: gnome-getting-started-docs-fi Reverse Depends: gnome-getting-started-docs-fr Reverse Depends: gnome-getting-started-docs-gl Reverse Depends: gnome-getting-started-docs-gu Reverse Depends: gnome-getting-started-docs-he Reverse Depends: gnome-getting-started-docs-hi Reverse Depends: gnome-getting-started-docs-hr Reverse Depends: gnome-getting-started-docs-hu Reverse Depends: gnome-getting-started-docs-id Reverse Depends: gnome-getting-started-docs-it Reverse Depends: gnome-getting-started-docs-ja Reverse Depends: gnome-getting-started-docs-kn Reverse Depends: gnome-getting-started-docs-ko Reverse Depends: gnome-getting-started-docs-lt Reverse Depends: gnome-getting-started-docs-lv Reverse Depends: gnome-getting-started-docs-mr Reverse Depends: gnome-getting-started-docs-nl Reverse Depends: gnome-getting-started-docs-pa Reverse Depends: gnome-getting-started-docs-pl Reverse Depends: gnome-getting-started-docs-pt Reverse Depends: gnome-getting-started-docs-ro Reverse Depends: gnome-getting-started-docs-ru Reverse Depends: gnome-getting-started-docs-sk Reverse Depends: gnome-getting-started-docs-sr Reverse Depends: gnome-getting-started-docs-sv Reverse Depends: gnome-getting-started-docs-ta Reverse Depends: gnome-getting-started-docs-te Reverse Depends: gnome-getting-started-docs-uk Reverse Depends: gnome-getting-started-docs-zh-hk Reverse Depends: gnome-getting-started-docs-zh-tw R
[Desktop-packages] [Bug 1943645] Re: Please remove gnome-getting-started-docs from impish
** Changed in: gnome-getting-started-docs (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-getting-started-docs in Ubuntu. https://bugs.launchpad.net/bugs/1943645 Title: Please remove gnome-getting-started-docs from impish Status in gnome-getting-started-docs package in Ubuntu: New Status in gnome-getting-started-docs package in Debian: Fix Released Bug description: It was just removed from unstable — see Debian bug — but due to Ubuntu's language split it probably needs to be removed manually here. $ apt rdepends gnome-getting-started-docs* gnome-getting-started-docs Reverse Depends: Depends: gnome-getting-started-docs-as (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-zh-tw (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-zh-hk (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-uk (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-te (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ta (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-sv (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-sr (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-sk (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ru (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ro (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-pt (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-pl (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-pa (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-nl (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-mr (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-lv (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-lt (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ko (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-kn (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ja (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-it (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-id (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-hu (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-hr (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-hi (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-he (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-gu (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-gl (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-fr (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-fi (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-fa (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-es (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-eo (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-el (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-de (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-da (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-cs (= 3.36.2+git20201004.1-0ubuntu1) Depends: gnome-getting-started-docs-ca (= 3.36.2+git20201004.1-0ubuntu1) gnome-getting-started-docs-as Reverse Depends: gnome-getting-started-docs-ca Reverse Depends: gnome-getting-started-docs-cs Reverse Depends: gnome-getting-started-docs-da Reverse Depends: gnome-getting-started-docs-de Reverse Depends: gnome-getting-started-docs-el Reverse Depends: gnome-getting-started-docs-eo Reverse Depends: gnome-getting-started-docs-es Reverse Depends: gnome-getting-started-docs-fa Reverse Depends: gnome-getting-started-docs-fi Reverse Depends: gnome-getting-started-docs-fr Reverse Depends: gnome-getting-started-docs-gl Reverse Depends: gnome-getting-started-docs-gu Reverse Depends: gnome-getting-started-docs-he Reverse Depends: gnome-getting-started-docs-hi Reverse Depends: gnome-getting-started-docs-hr Reverse Depends: gnome-getting-started-docs-hu Reverse Depends: gnome-getting-started-docs-id Reverse Depends: gnome-getting-started-docs-it Reverse Depends: gnome-getting-started-docs-ja Reverse Depends: gnome-getting-started-docs-kn Reverse Depends: gnome-getting-started-docs-ko Reverse Depends: gnome-getting-started-docs-lt Reverse Depends: gnome-getting-started-docs-lv Reverse Depends: gnome-getting-started-docs-mr Reverse
[Desktop-packages] [Bug 27867]
(In reply to ksharief from comment #42) > You can find the option here: > https://bugs.edge.launchpad.net/firefox/+bug/27867 > > Thanks > > Ksharief > https://www.fieldengineer.com/ Your approach to teaching inspires me. good luck have [fun](https://fun888.co/) with ur work everyday <3 -- 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/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+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 1930937] Proposed package removed from archive
The version of screen-resolution-extra in the proposed pocket of Hirsute that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Confirmed Status in screen-resolution-extra source package in Groovy: Fix Committed Status in screen-resolution-extra source package in Hirsute: Confirmed Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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 1930937] Proposed package removed from archive
The version of screen-resolution-extra in the proposed pocket of Hirsute that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Confirmed Status in screen-resolution-extra source package in Groovy: Fix Committed Status in screen-resolution-extra source package in Hirsute: Confirmed Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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 1930937] Proposed package removed from archive
The version of screen-resolution-extra in the proposed pocket of Focal that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. ** Changed in: screen-resolution-extra (Ubuntu Focal) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Confirmed Status in screen-resolution-extra source package in Groovy: Fix Committed Status in screen-resolution-extra source package in Hirsute: Confirmed Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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 1930937] Proposed package removed from archive
The version of screen-resolution-extra in the proposed pocket of Hirsute that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Confirmed Status in screen-resolution-extra source package in Groovy: Fix Committed Status in screen-resolution-extra source package in Hirsute: Confirmed Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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 1930937] Proposed package removed from archive
The version of screen-resolution-extra in the proposed pocket of Hirsute that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. ** Changed in: screen-resolution-extra (Ubuntu Hirsute) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Confirmed Status in screen-resolution-extra source package in Groovy: Fix Committed Status in screen-resolution-extra source package in Hirsute: Confirmed Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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 1930937] Proposed package removed from archive
The version of screen-resolution-extra in the proposed pocket of Focal that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Confirmed Status in screen-resolution-extra source package in Groovy: Fix Committed Status in screen-resolution-extra source package in Hirsute: Confirmed Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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 1930937] Proposed package removed from archive
The version of screen-resolution-extra in the proposed pocket of Focal that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Confirmed Status in screen-resolution-extra source package in Groovy: Fix Committed Status in screen-resolution-extra source package in Hirsute: Confirmed Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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 1930937] Proposed package removed from archive
The version of screen-resolution-extra in the proposed pocket of Focal that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Confirmed Status in screen-resolution-extra source package in Groovy: Fix Committed Status in screen-resolution-extra source package in Hirsute: Confirmed Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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 1943342] Re: Several seconds for icons to appear and dissappear from the dock
I'm going to do what you've written and I'll post if the problem is still taking place or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1943342 Title: Several seconds for icons to appear and dissappear from the dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: The icons take several seconds to appear and disappear from the dock. The dock has been showing this behavior from time to time without apparently reason since day zero. show-mounts is set to false. Description:Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1943342/+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 1938747] Re: [SRU] can't adjust output volume through volume-slider after changing output-device
This bug was fixed in the package gnome-control-center - 1:3.36.5-0ubuntu3 --- gnome-control-center (1:3.36.5-0ubuntu3) focal; urgency=medium * d/p/git-Fix-volume-adjustment-failure-on-volume-slider.patch Can't adjust the output volume via volume-slider after changing the current output-device. (LP: #1938747) -- Hui Wang Tue, 03 Aug 2021 16:53:47 +0800 ** Changed in: gnome-control-center (Ubuntu Focal) 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/1938747 Title: [SRU] can't adjust output volume through volume-slider after changing output-device Status in HWE Next: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Status in gnome-control-center source package in Hirsute: Fix Released Status in gnome-control-center source package in Impish: Fix Released Bug description: [Impact] On the machine with the legacy HDA audio driver, suppose the current output device is Speaker, users plug a HDMI monitor and select the HDMI audio as the current output device in the g-c-c, after that the output volume can't be adjusted through the volume-slider in the g-c-c. The UI of the volume-slider could be changed, but the output volume doesn't change. [Fix] Backport 1 upstream commit 0f18a662be6ee0d225249d1ad003dfef69294449. The root cause of this issue is the stream is not got when changing the output-device, the patch adds the getting stream in the update_sink callback, this could fix this bug. [Test] run the patches g-c-c, plug a hdmi monitor, select the HDMI audio from g-c-c, then change the output volume via volume-slider, play music, the sound could be changed with the adjustment with the volume-slider. [Where problems will occur] This patch brings the change to the output and input volume adjustment in the cc-sound-panel, this could make the output/input volume changing not work anymore, for example, the internal speaker or internal mic work well, after plugging a headset, the output device changes to headphone, the intput device changes to Mic, then the volume adjustment doesn't work on headphone and Mic anymore. But this possibility is very low since I tested the patch on different Lenovo and Dell machines, no regression found so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938747/+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 1943558] Re: Regression: Gnome shell has red tint after installation of Nvidia proprietary drivers
The bug doesn't seem to happen for most Nvidia users so it's not yet high priority. Regardless, the conversation should stay in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4071 ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4071 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4071 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4071 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Tags added: nvidia -- 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/1943558 Title: Regression: Gnome shell has red tint after installation of Nvidia proprietary drivers Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Upstream report of this issue: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4071 A colleague tested the latest daily of Ubuntu 21.10 and had a red tint after installing the proprietary nvidia drivers. Did not happen with gnome-shell versions < 40. Changing display refresh rate made the red tint go away. This report should serve as a reminder to fix this bug before it hits the masses after release. If you need more specific info I'll request it from my colleague, he did not want to bother reporting the bug himself. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1943558/+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 1943569] Re: Sometimes distorted sound in or after Firefox
Does the bug occur if you stick to the original daemon.conf? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1943569 Title: Sometimes distorted sound in or after Firefox Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sometimes when I open Firefox and play a video or start Plex Media Player or start to play a game I get a distorted audio/sound. I modified the Pulse Audio daemon.conf by this tutorial https://medium.com/@gamunu/enable-high-quality-audio-on- linux-6f16f3fe7e1f to improve the sound in Linux. The deamon.conf should be attached. When I get this issue I have to open a terminal and enter »pulseaudio -k«. After this it's normal again. Here's a complete hwinfo: https://gist.github.com/Johnnii360/1cbdbb0f27180013652a01f21c2f4792 My sound card is a Creative SoundBlaster X-Fi Titanium Fatal1ty (EMU20k2). Kernel version: 5.4.0-84-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 14 12:25:30 2021 InstallationDate: Installed on 2019-11-10 (674 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.40 dmi.board.name: Z390 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-05-31T09:26:29.202354 mtime.conffile..etc.pulse.daemon.conf: 2020-12-26T09:12:04.962975 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1943569/+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 1943417] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze + Screen freeze -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943417 Title: Screen freeze Status in Ubuntu: Incomplete Bug description: ubuntu freezes frequently. can't even able to shutdown the system so i have to press the power button ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 13 11:36:03 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics [103c:85f1] InstallationDate: Installed on 2021-08-24 (19 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 30c9:0035 Luxvisions Innotech Limited HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 2, Class=Application Specific Interface, Driver=, 480M MachineType: HP HP Laptop 15s-du1xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=b978107e-eaec-49de-9940-8be83bba3111 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2021 dmi.bios.release: 15.43 dmi.bios.vendor: Insyde dmi.bios.version: F.43 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85F1 dmi.board.vendor: HP dmi.board.version: 37.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.28 dmi.modalias: dmi:bvnInsyde:bvrF.43:bd03/31/2021:br15.43:efr37.28:svnHP:pnHPLaptop15s-du1xxx:pvrType1ProductConfigId:sku25U57PA#ACJ:rvnHP:rn85F1:rvr37.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-du1xxx dmi.product.sku: 25U57PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1943417/+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 1943328] Re: display 1920x1080 not showing in setting
Thanks for the bug report. It appears the system can't get an EDID over the VGA port and so is defaulting to low resolution: [ 6595.926] (II) modeset(0): EDID for output VGA-1 [ 6595.926] (II) modeset(0): Printing probed modes for output VGA-1 [ 6595.927] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) I would recommend using a digital monitor connection (HDMI) instead. If you can't do that then try plugging in the VGA cable again, firmly. Also try a different VGA cable, but HDMI would be better. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - display 1920x1080 not showing in setting + [i915] display 1920x1080 not showing in setting ** Package changed: linux (Ubuntu) => linux-hwe-5.11 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943328 Title: [i915] display 1920x1080 not showing in setting Status in linux-hwe-5.11 package in Ubuntu: New Bug description: display 1920x1080 not showing in setting. i cant change my display. everything looks bigger and ugly ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 11 19:27:58 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Generation Core Processor Family Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2021-09-10 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=bb5421d7-dc24-45ad-8107-199e6e049a18 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd07/10/2018:br4.6:svnMSI:pnMS-7817:pvr1.0:skuTobefilledbyO.E.M.:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 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/linux-hwe-5.11/+bug/1943328/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
That seems like we should be able to extract a verification from the errors.ubuntu.com results. Is it possible to query crashes with a specific dependency version? Seeing no crash reports with libx11 2:1.6.9-2ubuntu1.3 would suggest this is fixed. On the other hand, https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/comments/110 suggests that this may *not* be fixed in focal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG ==
[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
Re comment #110, Cinnamon might just be missing the obvious: > [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called We added XInitThreads to mutter in 3.36.2-2 and it is upstreamed in 3.36.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafp
[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
If you want evidence that the libx11 1.7.0 fix works then the error reports linked from bug 1886059 are convincing enough to me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bug
[Desktop-packages] [Bug 1942733] Update Released
The verification of the Stable Release Update for udisks2 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1942733 Title: Disk Capacity shows "Unknown" when installing OS on eMMC Status in OEM Priority Project: New Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Focal: Fix Released Bug description: [Impact] * This fix "Disk Capacity" in gnome-control-center shows "Unknown" if installing Focal on eMMC [Test Plan] * Install Focal on eMMC desktop or laptop. * Open "Settings" application and select "About" * Check the volume of "Disk Capacity" [Where problems could occur] * This changes eMMC's media removable property to false. * All the changes is in Hirsute, so only effect on Focal. [Other Info] * Upstream bug: https://github.com/storaged-project/udisks/pull/834 * Due to MediaRemoveable is false, gnome-control-center will skip this device and "Unknown" will show in "Disk Capacity" To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942733/+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 1942733] Re: Disk Capacity shows "Unknown" when installing OS on eMMC
This bug was fixed in the package udisks2 - 2.8.4-1ubuntu2 --- udisks2 (2.8.4-1ubuntu2) focal; urgency=medium * debian/patches/0001-udev-Distinguish-mmcblk-class-device-types.patch debian/patches/0002-udev-Propagate-mmcblk-disk-attributes-to-mmcblk_boot.patch debian/patches/0003-udiskslinuxdrive-Tweak-the-removable-ejectable-hints.patch debian/patches/0004-udiskslinuxblock-Tweak-the-hints-for-mmcblk-class-de.patch - backport 4 commits from upstream to fix mmcblk is not removeable. https://github.com/storaged-project/udisks/issues/358 (lp: #1942733) -- Andy Chi Mon, 06 Sep 2021 11:01:13 +0800 ** Changed in: udisks2 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Bug watch added: github.com/storaged-project/udisks/issues #358 https://github.com/storaged-project/udisks/issues/358 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1942733 Title: Disk Capacity shows "Unknown" when installing OS on eMMC Status in OEM Priority Project: New Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Focal: Fix Released Bug description: [Impact] * This fix "Disk Capacity" in gnome-control-center shows "Unknown" if installing Focal on eMMC [Test Plan] * Install Focal on eMMC desktop or laptop. * Open "Settings" application and select "About" * Check the volume of "Disk Capacity" [Where problems could occur] * This changes eMMC's media removable property to false. * All the changes is in Hirsute, so only effect on Focal. [Other Info] * Upstream bug: https://github.com/storaged-project/udisks/pull/834 * Due to MediaRemoveable is false, gnome-control-center will skip this device and "Unknown" will show in "Disk Capacity" To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942733/+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
