[Desktop-packages] [Bug 1944404] [NEW] [HDA-Intel - HDA NVidia, playback] No sound at all
Public bug reported: Hi...my problem is that I am using the nVidia GTX card connected by HDMI cable to a widescreen Samsung monitor that doesn't have speakers. Ubuntu assumes I can use that to play audio. In reality I'm using stereo speakers connected to the "center" output from the rear of the computer. This works fine in windows, but not in Ubuntu 20.04. I've tried several fixes to similar looking issues on line, but still I don't get sound. The only option I have under settings is for the HDMI/DisplayPort 2 - GM107 High Definition audio controller [GE Force 940 MX]. I've tried an old solution by adding hdajackretask and I've tried adjusting volume levels using alsamixer, but those solutions didn't help. Anyone have any other ideas? Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: larry 11338 F pulseaudio /dev/snd/controlC2: larry 11338 F pulseaudio /dev/snd/controlC1: larry 11338 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 23:05:52 2021 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GM107 High Definition Audio Controller [GeForce 940MX] - HDA NVidia Symptom_Type: No sound at all Title: [HDA-Intel - HDA NVidia, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2019 dmi.bios.release: 64.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/31/2019:br64.14:svnDellInc.:pnXPS8700:pvr:sku0x05B7:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: 0x05B7 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1944404 Title: [HDA-Intel - HDA NVidia, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi...my problem is that I am using the nVidia GTX card connected by HDMI cable to a widescreen Samsung monitor that doesn't have speakers. Ubuntu assumes I can use that to play audio. In reality I'm using stereo speakers connected to the "center" output from the rear of the computer. This works fine in windows, but not in Ubuntu 20.04. I've tried several fixes to similar looking issues on line, but still I don't get sound. The only option I have under settings is for the HDMI/DisplayPort 2 - GM107 High Definition audio controller [GE Force 940 MX]. I've tried an old solution by adding hdajackretask and I've tried adjusting volume levels using alsamixer, but those solutions didn't help. Anyone have any other ideas? Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: larry 11338 F pulseaudio /dev/snd/controlC2: larry 11338 F pulseaudio /dev/snd/controlC1: larry 11338 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 23:05:52 2021 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GM107 High Definition Audio Controller [GeForce 940MX] - HDA NVidia Symptom_Type: No sound at all Title: [HDA-Intel - HDA NVidia, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2019 dmi.bios.release: 64.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1929999] Re: [SRU] libreoffice 6.4.7.2.M3 for Focal
** Description changed: [Impact] * LibreOffice 6.4.7.2.M3 is a bug-fix release of the 6.4 line: It receives important bug-fixes on top of the 6.4 branch which is EOL since November 30, 2020. Currently maintained by Andras Timar for France's MIMO (https://blog.documentfoundation.org/blog/2013/06/17/the-document-foundation-welcomes-frances-mimo-in-the-advisory-board/) * Version 6.4.7 is currently released in focal. https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-6-4 (that's a total of ?? bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. - https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/12419370/+listing-archive-extra + https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/12712294/+listing-archive-extra - * [amd64] ... - * [arm64] ... - * [armhf] ... - * [ppc64el] ... - * [s390x] ... + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/amd64/libr/libreoffice/20210921_030416_a2220@/log.gz + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/arm64/libr/libreoffice/20210921_010758_2afcd@/log.gz + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/armhf/libr/libreoffice/20210920_223713_b4dfd@/log.gz + * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/ppc64el/libr/libreoffice/20210920_232648_4df4d@/log.gz + * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/s390x/libr/libreoffice/20210921_020008_6c843@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ?? bug fixes always carries the potential for introducing regressions, even though it is a bug-fix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- 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/192 Title: [SRU] libreoffice 6.4.7.2.M3 for Focal Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Focal: New Bug description: [Impact] * LibreOffice 6.4.7.2.M3 is a bug-fix release of the 6.4 line: It receives important bug-fixes on top of the 6.4 branch which is EOL since November 30, 2020. Currently maintained by Andras Timar for France's MIMO (https://blog.documentfoundation.org/blog/2013/06/17/the-document-foundation-welcomes-frances-mimo-in-the-advisory-board/) * Version 6.4.7 is currently released in focal. https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-6-4 (that's a total of ?? bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/12712294/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/amd64/libr/libreoffice/20210921_030416_a2220@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/arm64/libr/libreoffice/20210921_010758_2afcd@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/armhf/libr/libreoffice/20210920_223713_b4dfd@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/ppc64el/libr/libreoffice/20210920_232648_4df4d@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/s390x/libr/libreoffice/20210921_020008_6c843@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ?? bug fixes always carries the potential for introducing regressions, even though it is a bug-fix- only release, meaning that no new features were added,
[Desktop-packages] [Bug 1409536] Re: After testing settings cannot return to Mouse & Touchpad settings
[Expired for One Hundred Papercuts because there has been no activity for 60 days.] ** Changed in: hundredpapercuts Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1409536 Title: After testing settings cannot return to Mouse & Touchpad settings Status in One Hundred Papercuts: Expired Status in unity-control-center package in Ubuntu: Expired Bug description: If I go into the "Mouse & Touchpad" section in "System Settings" and I click the button in the top-right hand corner called "Test Your Settings". Once I am in the "Test Your Settings" section I cannot return to the "Mouse & Touchpad" section by selecting it at the top- left hand corner next to the "System Settings" button, I can click it a hundred times but nothing happens. Instead I have to click the "System Settings" button and return to the main screen to go back into the "Mouse & Touchpad" section. And this is a small bug, but it is still rather annoying that I have to use min 2 clicks instead of 1, to return to the "Mouse & Touchpad" section. OS information: Description: Ubuntu 14.10 Release: 14.10 Package information: unity-control-center: Installed: 14.10.0+14.10.20140922-0ubuntu2 Candidate: 14.10.0+14.10.20140922-0ubuntu2 Version table: *** 14.10.0+14.10.20140922-0ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1409536/+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 1908082] Re: Ubuntu Firefox is 15% slower than Flatpak Firefox for speedometer benchmark
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1908082 Title: Ubuntu Firefox is 15% slower than Flatpak Firefox for speedometer benchmark Status in firefox package in Ubuntu: Expired Bug description: Steps to reproduce: I installed Firefox Flatpak (https://flathub.org/apps/details/org.mozilla.firefox) and Chrome. I executed closed all apps and processes and one by one I executed Speedometer test (https://browserbench.org/Speedometer2.0/) in each browser 3 times. I took the max score for reach browser out of the 3 executions of the test. Actual results: Results 100.3 - Firefox Flatpak 85.42 - FIrefox DEB (pre-installd from the store) 100.3 - Google Chrome The preinstalled DEB package Firefox was slower than both Firefox Flatpak and Chrome Expected results: I expected Firefox DEB and Firefox Flatpak to have the same results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1908082/+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 1409536] Re: After testing settings cannot return to Mouse & Touchpad settings
[Expired for unity-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1409536 Title: After testing settings cannot return to Mouse & Touchpad settings Status in One Hundred Papercuts: Expired Status in unity-control-center package in Ubuntu: Expired Bug description: If I go into the "Mouse & Touchpad" section in "System Settings" and I click the button in the top-right hand corner called "Test Your Settings". Once I am in the "Test Your Settings" section I cannot return to the "Mouse & Touchpad" section by selecting it at the top- left hand corner next to the "System Settings" button, I can click it a hundred times but nothing happens. Instead I have to click the "System Settings" button and return to the main screen to go back into the "Mouse & Touchpad" section. And this is a small bug, but it is still rather annoying that I have to use min 2 clicks instead of 1, to return to the "Mouse & Touchpad" section. OS information: Description: Ubuntu 14.10 Release: 14.10 Package information: unity-control-center: Installed: 14.10.0+14.10.20140922-0ubuntu2 Candidate: 14.10.0+14.10.20140922-0ubuntu2 Version table: *** 14.10.0+14.10.20140922-0ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1409536/+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 1940133] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strdup() from g_error_copy()
*** This bug is a duplicate of bug 1944388 *** https://bugs.launchpad.net/bugs/1944388 Bug 1944388 has a better backtrace of this problem so we should use that. ** This bug has been marked a duplicate of bug 1944388 gnome-shell crashed with SIGSEGV in g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach() -- 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/1940133 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strdup() from g_error_copy() Status in gnome-shell package in Ubuntu: New Bug description: hang ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 16 19:09:25 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-08-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210816) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_error_copy () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-8.so.0 g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1940133/+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 1944388] Re: gnome-shell crashed with SIGSEGV in g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1944388 Title: gnome-shell crashed with SIGSEGV in g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: gnome-shell crashed with SIGSEGV in g_strdup() ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu6 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 02:58:40 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_error_copy () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-8.so.0 g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-8.so.0 Title: gnome-shell crashed with SIGSEGV in g_strdup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1944388/+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 1944388] Re: gnome-shell crashed with SIGSEGV in g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach()
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1851 https://gitlab.gnome.org/GNOME/mutter/-/issues/1851 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1851 Importance: Unknown Status: Unknown ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1944388 Title: gnome-shell crashed with SIGSEGV in g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: gnome-shell crashed with SIGSEGV in g_strdup() ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu6 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 02:58:40 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_error_copy () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-8.so.0 g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-8.so.0 Title: gnome-shell crashed with SIGSEGV in g_strdup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1944388/+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 1944388] Re: gnome-shell crashed with SIGSEGV in g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl()
** Summary changed: - gnome-shell crashed with SIGSEGV in g_strdup() + gnome-shell crashed with SIGSEGV in g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() ** Summary changed: - gnome-shell crashed with SIGSEGV in g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() + gnome-shell crashed with SIGSEGV in g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach() ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1944388/+attachment/5526539/+files/CoreDump.gz ** Information type changed from Private to Public -- 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/1944388 Title: gnome-shell crashed with SIGSEGV in g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: gnome-shell crashed with SIGSEGV in g_strdup() ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu6 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 02:58:40 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_error_copy () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-8.so.0 g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-8.so.0 Title: gnome-shell crashed with SIGSEGV in g_strdup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1944388/+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 1944122] Re: GUI crash
*** This bug is a duplicate of bug 1939417 *** https://bugs.launchpad.net/bugs/1939417 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1939417, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - Xorg crash + GUI crash ** This bug has been marked a duplicate of bug 1939417 Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault -- 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/1944122 Title: GUI crash Status in xorg package in Ubuntu: New Bug description: in the middle of working the GUI crashed (mouse movements yes, no klicks possible) came back, crashed again, login screen appeared. Clearly an issue with AMD-GPU as dmesg states. This report was only possible via ssh from a different machine. Distributor ID: Ubuntu Description: Ubuntu 21.04 Release: 21.04 Codename: hirsute Linux peter 5.14.0-051400drmtip20210904-generic #202109040225 SMP Sat Sep 4 02:34:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Sep 20 14:26:27 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20210418, 5.11.0-34-generic, x86_64: installed vhba, 20210418, 5.11.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (278 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 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.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4: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. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 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 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 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 xserver.bootTime: Mon Sep 20 14:25:30 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.1 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1944122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1880405] Re: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
** Changed in: mutter (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1880405 Title: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Hirsute: Fix Released Status in mutter package in Debian: Fix Released Bug description: [ Impact ] Shell becomes slow and unresponsive flooding journal with JS errors [ Test case ] 1. Resize the terminal to use half the screen (using CMD+LEFT) 2. switch it to fullscreen (F11) and back (F11) 3. Repeat this some number of times ensure we don't end up in a loop with 100% CPU usage. 4. Ensure that it's still possible to get window focus and the UI is responsive. [ Regression potential ] Events are ignored for windows which are still visible. --- O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+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 1944398] [NEW] [Bluetooth Headset, playback] auto_switch=2 doesn't work with Discord
Public bug reported: I am having a problem connecting a bluetooth headset as HSP/HFP (headset_head_unit). It seems that the only way to use my headset as an HSP/HFP device is to set module-bluetooth-policy auto_switch=2, as A2DP is the hard-coded default. It's hard to find information because of the overwhelming number of issues people have had getting HSP/HFP to work in the first place. auto_switch=2 does switch the protocol to HSP/HFP, but in such a way that Discord does not recognize that the device is connected any longer. If I manually switch my headset to HSP/HFP before joining a voicechat channel, everything works as expected, but I can find no way to default my headset to HSP/HFP. Steps to reproduce: Open Discord, having previously set input/output to Bluetooth device Connect Bluetooth headset Join Voice Chat Expected result: Bluetooth unit sets profile to HSP/HFP Discord outputs and inputs via the headset Actual result: Bluetooth unit sets profile to "off" No output or input through Discord ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-84.94-lowlatency 5.4.133 Uname: Linux 5.4.0-84-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: hukt 2399 F pulseaudio /dev/snd/controlC0: hukt 2399 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Sep 20 21:36:10 2021 InstallationDate: Installed on 2020-04-27 (511 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: M98 Symptom_Type: None of the above Title: [M98, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0910 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LE PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0910:bd03/18/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLEPLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1944398 Title: [Bluetooth Headset, playback] auto_switch=2 doesn't work with Discord Status in alsa-driver package in Ubuntu: New Bug description: I am having a problem connecting a bluetooth headset as HSP/HFP (headset_head_unit). It seems that the only way to use my headset as an HSP/HFP device is to set module-bluetooth-policy auto_switch=2, as A2DP is the hard-coded default. It's hard to find information because of the overwhelming number of issues people have had getting HSP/HFP to work in the first place. auto_switch=2 does switch the protocol to HSP/HFP, but in such a way that Discord does not recognize that the device is connected any longer. If I manually switch my headset to HSP/HFP before joining a voicechat channel, everything works as expected, but I can find no way to default my headset to HSP/HFP. Steps to reproduce: Open Discord, having previously set input/output to Bluetooth device Connect Bluetooth headset Join Voice Chat Expected result: Bluetooth unit sets profile to HSP/HFP Discord outputs and inputs via the headset Actual result: Bluetooth unit sets profile to "off" No output or input through Discord ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-84.94-lowlatency 5.4.133 Uname: Linux 5.4.0-84-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: hukt 2399 F pulseaudio /dev/snd/controlC0: hukt 2399 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Sep 20 21:36:10 2021 InstallationDate: Installed on 2020-04-27 (511 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: M98 Symptom_Type: None of the above Title: [M98, playback]
[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Changed in: fedora Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Released Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Won't Fix Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable allows anyone to disable the remote calls in x and/or b, and then upgrade to Focal without breaking rpcbind or needing to remove the env var. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+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 304393]
I filed bug 1854147 against libtirpc with the denylist additions suggested in comment 0. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Released Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Won't Fix Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable allows anyone to disable the remote calls in x and/or b, and then upgrade to Focal without breaking rpcbind or needing to remove the env var. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+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 304393]
We are tracking this upstream. It is unclear whether bindresvport will remain as a public API in glibc. So far, it has not been subject to the Sun RPC transition in glibc, although libtirpc implements the symbol as well. It may therefore be possible to turn the glibc symbol in to a compat symbol, effectively removing it from the glibc API. In this case, it is unlikely that upstream will implement a denylist, similar to what is available in libtirpc today. Applications built on Red Hat Enterprise Linux 8 can already use the libtirpc denylist functionality for bindresvport by linking against libtirpc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Released Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Won't Fix Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable allows anyone to disable the remote calls in x and/or b, and then upgrade to Focal without breaking rpcbind or needing to remove the env var. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1944223] Re: Wayland Session can't be run on supported NVIDIA setups
This bug was fixed in the package gnome-session - 40.1.1-1ubuntu1
---
gnome-session (40.1.1-1ubuntu1) impish; urgency=medium
* Merge with debian, containing latest stable release:
We already included most of the patches.
* debian/patches: Install again gnome-wayland so that can be used from X11 gdm
(LP: #1944223)
* d/p/ubuntu-sessions.patch: Add ubuntu-wayland session to support gdm on X11
(LP: #1944223, required for LP: #1942911)
* d/p/ubuntu-sessions.patch: Skip ubuntu-xorg.desktop.in from translations.
The .in.in file is already translated.
* gnome-session.install: Include gnome-wayland session
* ubuntu-session.install: Include ubuntu-wayland session
* debian/rules: Update pot file name to be generated
* Remaining changes with debian:
- debian/control.in:
+ Recommend session-migration
+ Move xwayland dependency to gnome-session and make gnome-session
Arch: any
+ Split gnome-startup-applications to a separate binary package so
that it can be uninstalled without breaking the system
+ Add unity-session
- debian/rules: Ensure pot file is generated to translate session files
- Split ubuntu-session out of gnome-session.
- debian/data: Add old-style systemd user session used by Unity
- debian/gnome-session-bin.postinst, debian/gnome-session-bin.prerm:
Moved registering gnome-session binary as a session manager to
gnome-session-bin package
- don't install gnome-mimeapps.list (installed by desktop-file-utils in
Ubuntu):
debian/gnome-session-common.dirs, gnome-session-common.install,
gnome-session-common.maintscript, gnome-session-common.postinst
- debian/patches/ubuntu/support_autostart_delay.patch:
+ Bugzilla patch to support adding a delay to autostart apps, using
a "X-GNOME-Autostart-Delay" key in the desktop file
- debian/patches/ubuntu/ubuntu_sessions.patch:
+ Add ubuntu sessions
- debian/patches/ubuntu/remove_session_saving_from_gui.patch:
+ Add GNOME_SESSION_SAVE environment variable for people wanting to
use the save session still, knowing that it can break your system
if used unwisely
- debian/patches/ubuntu/add_sessionmigration.patch:
+ launch session-migration if present at the start of the session.
This sync tool runns different session migration scripts that can be
provided in various desktop packages.
- debian/patches/ubuntu/dbus_request_shutdown.patch:
+ Add "RequestShutdown" and "RequestReboot" DBus methods to allow
other applications to shutdown or reboot the machine via the session
manager.
- debian/patches/ubuntu/ignore_gsettings_region.patch:
+ Ignore the "region" gsettings value - users' setting of LC_*
variables saved in ~/.pam_environment.
- debian/patches/revert_remove_gnome_session_properties.patch:
+ Don't merge translations into gnome-session-properties.desktop
- debian/ubuntu-settings-migrate-to-defaults.18.10.1.py:
+ Migrate users using old default ubuntu-settings to current ones
- debian/xdg_dirs_desktop_session.sh: Install a new script into
/etc/profile.d to prepend a $DESKTOP_SESSION related directory to
$XDG_{CONFIG,DATA}_DIRS.
gnome-session (40.1.1-1) unstable; urgency=medium
* New upstream release
- GNOME session will now only block sleep for suspend inhibitors and will
block shutdown if a logout inhibitor is active.
Previously a suspend inhibitor would prevent both sleep & logout.
Apps may need to be updated and grab both a logout & suspend inhibitor.
* Drop patches applied in new release
gnome-session (3.38.0-4) unstable; urgency=medium
* Team upload
[ Marco Trevisan (Treviño) ]
* debian/control: Bump dependency on meson 0.53 as per upstream
* d/p/util-Disable-capturing-of-subpatterns.patch:
Cherry-pick upstream patch fixing a stack overflow when environment
variables have very long values, in particular when using fish and
LS_COLORS
[ Didier Roche ]
* debian/55gnome-session_gnomerc:
Protect against multiple additions of the same path.
Do not append the same path to XDG_DATA_DIRS, resulting to duplication
on consecutive logout/logins due to an older session lingering and the
environment being reused. One consequence is that Electron applications
crash (LP: #1764355)
[ Simon McVittie ]
* d/patches: Turn upstream bug reference into a URL
* d/patches: Actively remove undesired variables from activation
environment.
This works around bugs in cinnamon-session and mate-session-manager,
which do not yet have an equivalent of gnome-session's variable_blacklist
and so will upload login-session-specific variables like XDG_SESSION_ID
into `dbus-daemon --session` and, indirectly, `systemd --user`.
(Closes: #973474)
-- Marco Trevisan (Treviño) Mon, 20 Sep 2021
20:34:00 +0200
**
[Desktop-packages] [Bug 1943768] Re: gsd defaults to wrong keymap for Sinhala (Sri Lanka) locale
This bug was fixed in the package gnome-settings-daemon - 40.0.1-1ubuntu3 --- gnome-settings-daemon (40.0.1-1ubuntu3) impish; urgency=medium * d/p/ubuntu/keyboard-Use-ibus-sources-from-locale.patch: add si_LK to the list of locales for which we prefer m17n. LP: #1943768. -- Steve Langasek Wed, 15 Sep 2021 15:58:15 -0700 ** Changed in: gnome-settings-daemon (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1943768 Title: gsd defaults to wrong keymap for Sinhala (Sri Lanka) locale Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in localechooser package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Triaged Bug description: Per https://lists.ubuntu.com/archives/ubuntu- devel/2021-September/041616.html, Sri Lanka has a national keyboard standard, wijesekera, which is implemented by ibus-m17n but which is not being used by default. We should add si_LK to the list of locales for which we use m17n. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1943768/+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 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C
Recently, I noticed that, from time to time, efivars values are automatically restored to default thus making necessary to redo all the steps in the aforementioned solution. Does anyone know if it is possible to change this behavior? Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1203592 Title: Keyboard backlight does not work in Samsung Series 9 NP900X4C Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: In Ubuntu 13.04, the keyboard backlight does not work in Samsung Series 9 NP900X4C. Adding the FN key mappings as described in https://help.ubuntu.com/community/SamsungSeries9 does show information in the notification area when pressing the keyboard backlight's + and - buttons, but: 1) The notification always identifies the backlight as "full max" 2) It has no effect on the backlight - it's always off When I first installed Ubuntu on this machine (12.10), even though the fn keys never worked I did have intermitent backlight functionality - the light sensor would sometimes work and I'd see light in the keyboard. I dual boot in Windows 8 and backlighting works there, so this is not a hardware issue. More discussion can be found here: http://askubuntu.com/questions/233312/how-to-make-keyboard-backlight- fn-buttons-work-in-samsung-series-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1203592/+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 1822156] Re: Cannot parse m3u8 playlist
Just noticed that VLC opens and plays the "radio.m3u8" stream just fine. (It is the "YLE Puhe" radio channel from Finland) $ sudo apt install vlc $ vlc Download/radio.m3u8 Ref: https://www.radio-browser.info/#/search?page=1=YLE -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem-pl-parser in Ubuntu. https://bugs.launchpad.net/bugs/1822156 Title: Cannot parse m3u8 playlist Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Hello, I have a m3u8 (utf8 format) playlist, but many players do not understand that file. Neither does totem-pl-parser. Ref: https://developer.gnome.org/totem-pl-parser/stable/ radio.m3u8 attached. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libtotem-plparser-dev 3.26.3-1ubuntu1 Uname: Linux 5.0.1-050001-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 16:06:11 2019 InstallationDate: Installed on 2019-03-06 (21 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: totem-pl-parser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1822156/+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 1822156] Re: Cannot parse m3u8 playlist
Hello, Yes, it is long time since I filed this report. I am now using Ubuntu 21.10 (daily version). I tried to play the file in Totem, but it does not understand the format (or Gstreamer is missing a plugin for it). I have installed the ubuntu-restricted-extras package. I attached a video of my test. Please tell me if you need additional tests or information. ** Attachment added: "Screencast from 20-09-2021 20:25:22.webm" https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1822156/+attachment/5526556/+files/Screencast%20from%2020-09-2021%2020%3A25%3A22.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem-pl-parser in Ubuntu. https://bugs.launchpad.net/bugs/1822156 Title: Cannot parse m3u8 playlist Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Hello, I have a m3u8 (utf8 format) playlist, but many players do not understand that file. Neither does totem-pl-parser. Ref: https://developer.gnome.org/totem-pl-parser/stable/ radio.m3u8 attached. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libtotem-plparser-dev 3.26.3-1ubuntu1 Uname: Linux 5.0.1-050001-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 16:06:11 2019 InstallationDate: Installed on 2019-03-06 (21 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: totem-pl-parser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1822156/+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 1927149] Re: Irrelevant translatable strings
On 2021-09-20 04:14, Matthias Klumpp wrote: > I still think this is a dumb fix, especially since you loose the > feature to actually mark strings from being untranslatable by > dropping the appstream dependency. And I still don't understand that part of your reasoning. If appstreams's version of metainfo.its is not present when the POT file is generated, it falls back to gettext's version which does not extract strings at all. And that's what we want to achieve in Ubuntu, at least as long as GNOME keeps appstream's metainfo.its away when generating the upstream POT file. Did you see this issue: https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/149 > A proper workaround would be to leave that in, possibly backport the > ITS patch for appstream to update the file, and then mark the release > entries you don't want to have translated with `translate="no"` in > the XML. That's a possible way to deal with it in the future once the GNOME Software maintainer (and all other GNOME project maintainers...) have reached an agreement with the Damned Lies admins on the matter. Please note that several `translatable="no"` have already been added: https://gitlab.gnome.org/GNOME/gnome-software/-/commit/7dc44712 (seems to be effective only for GNOME 41) But the strings for 40+ are still translatable, so even if the problem is reduced compared to when I first filed this bug report, it's still present. If the Damned Lies admins would change their mind, we still have the problem with the very latest info. Let's study the release of gnome-software 40.4 as an example. The NEWS file and the appdata.xml file were updated in the same commit (surprise, surprise) on August 13: https://gitlab.gnome.org/GNOME/gnome-software/-/commit/70c23e4a The actual release HAPPENED ON THE SAME DAY!! So even if those strings had been passed to the GNOME translators via Damned Lies, the strings for 40.4 would still have been shipped untranslated. You can't just snap your fingers to have strings translated. Translators need time. As you already know, I think it was an unfortunate mistake to consider the strings translatable by default. If some project owners wanted them to be translatable, it would have been much better to give those projects a possibility to opt in for translation. The maintainers of projects which opted in could be assumed to be aware of the required translation workflow for this to make sense. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1927149 Title: Irrelevant translatable strings Status in AppStream: Unknown Status in GNOME Software: Unknown Status in snap-store-desktop: New Status in gnome-software package in Ubuntu: Fix Released Bug description: When building gnome-software on Ubuntu, dh_translations generates a translation template (.pot file) to be imported to Rosetta. That template includes 700+ log messages from data/appdata/org.gnome.Software.appdata.xml.in. The messages are not shown to users, and it makes no sense to have those strings translated. It's worth mentioning that the strings are excluded in upstream's translation template. The issue was first reported at the ubuntu-translators mailing list: https://lists.ubuntu.com/archives/ubuntu-translators/2021-May/007757.html I stripped the redundant strings from the template and uploaded it to hirsute manually as a temporary measure. The reason why this happens seems to be that the appstream package is included in Build-Depends. appstream installs the file /usr/share/gettext/its/metainfo.its with rules which make all the log entries be extracted. But the gettext package installs /usr/share/gettext-0.21/its/metainfo.its with more sensible rules which do not make the log entries be extracted. If the former is not present, xgettext falls back to the latter. So a solution to this issue is to drop appstream from Build-Depends. gnome-software seems to build fine without that package (tested in PPA). To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1927149/+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 1944223] Re: Wayland Session can't be run on supported NVIDIA setups
Upstream fix https://gitlab.gnome.org/GNOME/gnome- session/-/merge_requests/71 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1944223 Title: Wayland Session can't be run on supported NVIDIA setups Status in gnome-session package in Ubuntu: In Progress Bug description: When running in NVIDIA setups with drivers major than 470 and modesetting enabled, it should be possible to (optionally) run an ubuntu Wayland session. However this is currently not possible because ubuntu-wayland.desktop session is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1944223/+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 1944223] [NEW] Wayland Session can't be run on supported NVIDIA setups
Public bug reported: When running in NVIDIA setups with drivers major than 470 and modesetting enabled, it should be possible to (optionally) run an ubuntu Wayland session. However this is currently not possible because ubuntu-wayland.desktop session is missing. ** Affects: gnome-session (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Tags: nvidia rls-ii-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1944223 Title: Wayland Session can't be run on supported NVIDIA setups Status in gnome-session package in Ubuntu: In Progress Bug description: When running in NVIDIA setups with drivers major than 470 and modesetting enabled, it should be possible to (optionally) run an ubuntu Wayland session. However this is currently not possible because ubuntu-wayland.desktop session is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1944223/+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 1944102] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for libjpeg-turbo8 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1944102/+attachment/5526360/+files/CoreDump.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1944102 Title: unity-settings-daemon crashed with SIGSEGV in XQueryExtension() Status in unity-settings-daemon package in Ubuntu: Invalid Bug description: Just logged in, i opened Terminal ... ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: unity-settings-daemon 15.04.1+21.10.20210715-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Mon Sep 20 06:33:42 2021 ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon InstallationDate: Installed on 2016-02-08 (2050 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160208) ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon ProcEnviron: LANG=da_DK.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: unity-settings-daemon StacktraceTop: XQueryExtension () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libXext.so.6 XSyncQueryExtension () from /lib/x86_64-linux-gnu/libXext.so.6 gsd_idle_monitor_init_dbus () from /lib/x86_64-linux-gnu/libunity-settings-daemon.so.1 main () Title: unity-settings-daemon crashed with SIGSEGV in XQueryExtension() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare staff sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1944102/+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 1944102] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1944102/+attachment/5526506/+files/ThreadStacktrace.txt ** Changed in: unity-settings-daemon (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1944102 Title: unity-settings-daemon crashed with SIGSEGV in XQueryExtension() Status in unity-settings-daemon package in Ubuntu: Invalid Bug description: Just logged in, i opened Terminal ... ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: unity-settings-daemon 15.04.1+21.10.20210715-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Mon Sep 20 06:33:42 2021 ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon InstallationDate: Installed on 2016-02-08 (2050 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160208) ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon ProcEnviron: LANG=da_DK.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: unity-settings-daemon StacktraceTop: XQueryExtension () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libXext.so.6 XSyncQueryExtension () from /lib/x86_64-linux-gnu/libXext.so.6 gsd_idle_monitor_init_dbus () from /lib/x86_64-linux-gnu/libunity-settings-daemon.so.1 main () Title: unity-settings-daemon crashed with SIGSEGV in XQueryExtension() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare staff sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1944102/+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 1944102] unity-settings-daemon crashed with SIGSEGV in XQueryExtension()
Stacktrace:
#0 0x7f6db2885ce3 in XQueryKeymap (dpy=0x563ec4a8f810,
keys=0x7f6db299a0ec "SYNC") at ../../src/QuKeybd.c:44
rep = {type = 0 '\000', pad1 = 0 '\000', sequenceNumber = 0, length =
0, map = '\000' }
req =
#1 0x in ?? ()
No symbol table info available.
StacktraceSource:
#0 0x7f6db2885ce3 in XQueryKeymap (dpy=0x563ec4a8f810,
keys=0x7f6db299a0ec "SYNC") at ../../src/QuKeybd.c:44
[Error: QuKeybd.c was not found in source tree]
#1 0x in ?? ()
StacktraceTop:
XQueryKeymap (dpy=0x563ec4a8f810, keys=0x7f6db299a0ec "SYNC") at
../../src/QuKeybd.c:44
?? ()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1944102
Title:
unity-settings-daemon crashed with SIGSEGV in XQueryExtension()
Status in unity-settings-daemon package in Ubuntu:
Invalid
Bug description:
Just logged in, i opened Terminal ...
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: unity-settings-daemon 15.04.1+21.10.20210715-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Sep 20 06:33:42 2021
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2016-02-08 (2050 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160208)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
ProcEnviron:
LANG=da_DK.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
Signal: 11
SourcePackage: unity-settings-daemon
StacktraceTop:
XQueryExtension () from /lib/x86_64-linux-gnu/libX11.so.6
?? () from /lib/x86_64-linux-gnu/libXext.so.6
XSyncQueryExtension () from /lib/x86_64-linux-gnu/libXext.so.6
gsd_idle_monitor_init_dbus () from
/lib/x86_64-linux-gnu/libunity-settings-daemon.so.1
main ()
Title: unity-settings-daemon crashed with SIGSEGV in XQueryExtension()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare staff sudo
wireshark
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1944102/+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 1942437] Re: [UIFe] Impish wallpapers
This bug was fixed in the package ubuntu-wallpapers - 21.10.1-0ubuntu1 --- ubuntu-wallpapers (21.10.1-0ubuntu1) impish; urgency=medium * Add Impish's wallpapers, both default and the first two winners of the community contest (LP: #1942437) * Update the AUTHORS file, adding missing entries for all community wallpapers since artful * Update the README.md instructions to include the AUTHORS file -- Olivier Tilloy Thu, 16 Sep 2021 18:32:49 +0200 ** Changed in: ubuntu-wallpapers (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1942437 Title: [UIFe] Impish wallpapers Status in ubuntu-wallpapers package in Ubuntu: Fix Released Bug description: The Impish Indri wallpapers, including two original images that won the wallpaper competition¹, and the official ones produced by the Canonical design team. As we got those past UI freeze (which happened on September 9), this requires a UI freeze exception². Gunnar (~gunnarhj), who is an administrator of both the documentation and translation teams, acknowledged the update in comment #8. ¹ https://ubuntu.com/blog/winners-of-the-21-10-wallpaper-competition ² https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze_Exceptions Original description: We need to include the winners of the 21.10 wallpaper competition in the release image. I don't know how to attack files here so I'll just provide links to the winning images in Discourse: First: https://discourse.ubuntu.com/t/wallpaper-competition-for- impish-indri-ubuntu-21-10/22852/171?u=rhys- davies&_ga=2.144156597.1440561583.1630580808-2071368223.1629705927 Second: https://discourse.ubuntu.com/t/wallpaper-competition-for- impish-indri-ubuntu-21-10/22852/60?u=rhys- davies&_ga=2.144156597.1440561583.1630580808-2071368223.1629705927 Also, I mentioned in the competition that if the Desktop team decided that they could fit more submissions into the release image without it becoming too big, that the next 8 submissions might make it in too. So if you decide you can fit more in please let me or Monica know and take them from the links in this blog post which lists them in the winning order: https://ubuntu.com/blog/winners-of-the-21-10-wallpaper- competition Let me know if there's anything else I can do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1942437/+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 1822156] Re: Cannot parse m3u8 playlist
> I verified your sample file works with totem-pl-parser 3.26.5-5ubuntu1 Hi, How exactly did you verify the sample m3u8 file ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem-pl-parser in Ubuntu. https://bugs.launchpad.net/bugs/1822156 Title: Cannot parse m3u8 playlist Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Hello, I have a m3u8 (utf8 format) playlist, but many players do not understand that file. Neither does totem-pl-parser. Ref: https://developer.gnome.org/totem-pl-parser/stable/ radio.m3u8 attached. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libtotem-plparser-dev 3.26.3-1ubuntu1 Uname: Linux 5.0.1-050001-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 16:06:11 2019 InstallationDate: Installed on 2019-03-06 (21 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: totem-pl-parser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1822156/+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 1942307] Re: ubiquity uses performance mode for nvidia driver
This bug was fixed in the package nvidia-prime - 0.8.17 --- nvidia-prime (0.8.17) impish; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. -- Alberto Milone Fri, 17 Sep 2021 16:45:11 +0200 ** Changed in: nvidia-prime (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: In Progress Status in nvidia-prime package in Ubuntu: Fix Released Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+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 1942789] Re: On-demand and RTD3 need to be separated
This bug was fixed in the package nvidia-prime - 0.8.17
---
nvidia-prime (0.8.17) impish; urgency=medium
[ Jeremy Szu ]
* Set on-demand mode as default nvidia mode (LP: #1942307)
[ Alberto Milone ]
* prime-select:
- Detect chassis type and enable RTD3 only
on laptops (LP: #1942788).
- on-demand mode doesn't need to depend on
RTD3 (LP: #1942789).
- Use bootvga detection when last_gfx_boot
is not available.
-- Alberto Milone Fri, 17 Sep 2021
16:45:11 +0200
** Changed in: nvidia-prime (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1942789
Title:
On-demand and RTD3 need to be separated
Status in OEM Priority Project:
Confirmed
Status in nvidia-prime package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
In Progress
Bug description:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.com/tseliot/ubuntu-drivers-common/issues/55.
Some parts need to be adjusted, e.g.
```
# If we are dealing with NVIDIA PRIME, and runtimepm
# is supported, enable it
if (os.path.isfile('/run/nvidia_runtimepm_supported') and
os.path.isfile('/usr/bin/prime-select')):
print('Trying to select the on-demand PRIME profile')
try:
subprocess.call(['prime-select', 'on-demand'])
except:
pass
# Create the override file for gpu-manager
with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
f.write('# File created by ubuntu-drivers\n')
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+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 1944060] Re: Black Screen after Session Unlock from Suspend
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1944060 Title: Black Screen after Session Unlock from Suspend Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Release: Ubuntu 20.04.3 LTS Installation Style: Minimal (selected during GUI install) (Untested against full installation style) Patient System Hardware Information: Lenovo ThinkPad P50 (Xenon) - Intel HD Graphics + NVIDIA Quadro M2000M (NVIDIA Prime enabled w/proprietary drivers) (GPU is not suspected to be the issue) Expected Behavior: 1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) Resume user desktop session. Actual Behavior: 1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) GNOME lock screen freezes - spinner stops moving but mouse cursor and keyboard are responsive (can switch TTYs). After GNOME lock screen freeze, if you switch out of TTY2 (default for GUI), and back into it, a black screen is shown. If you attempt to login via TTY1, you are switched to the black screen session in TTY2. Solution / Workaround: This behavior can be avoided by installing the "gnome-scrensaver" package. Something in this package is required by GNOME in order to successfully resume this system from suspend, even though no screen saver settings were configured after installing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1944060/+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 1944060] [NEW] Black Screen after Session Unlock from Suspend
You have been subscribed to a public bug: Ubuntu Release: Ubuntu 20.04.3 LTS Installation Style: Minimal (selected during GUI install) (Untested against full installation style) Patient System Hardware Information: Lenovo ThinkPad P50 (Xenon) - Intel HD Graphics + NVIDIA Quadro M2000M (NVIDIA Prime enabled w/proprietary drivers) (GPU is not suspected to be the issue) Expected Behavior: 1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) Resume user desktop session. Actual Behavior: 1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) GNOME lock screen freezes - spinner stops moving but mouse cursor and keyboard are responsive (can switch TTYs). After GNOME lock screen freeze, if you switch out of TTY2 (default for GUI), and back into it, a black screen is shown. If you attempt to login via TTY1, you are switched to the black screen session in TTY2. Solution / Workaround: This behavior can be avoided by installing the "gnome-scrensaver" package. Something in this package is required by GNOME in order to successfully resume this system from suspend, even though no screen saver settings were configured after installing it. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment unmetdeps -- Black Screen after Session Unlock from Suspend https://bugs.launchpad.net/bugs/1944060 You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta 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 1944216] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Public bug reported: Fails to boot upgrade Ubuntu 5.11.0-34, revert back to 5.8.0-63 on menu entry script in Grub and all works fine. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-34-generic Date: Sun Sep 19 23:55:28 2021 InstallationDate: Installed on 2021-02-28 (203 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1944216 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Fails to boot upgrade Ubuntu 5.11.0-34, revert back to 5.8.0-63 on menu entry script in Grub and all works fine. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-34-generic Date: Sun Sep 19 23:55:28 2021 InstallationDate: Installed on 2021-02-28 (203 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1944216/+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 1943984] Re: No archive files for static compilation are included in the -dev package
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757 ** Bug watch added: Debian Bug tracker #994757 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 1943859] Re: The development package does not include static libraries
Debian bug report: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994752 ** Bug watch added: Debian Bug tracker #994752 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994752 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1943859 Title: The development package does not include static libraries Status in pango1.0 package in Ubuntu: New Bug description: The development package for pango (libpango1.0-dev) does not include static libraries so it is not possible to link these libraries statically. See attached patch with the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1943859/+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 1943984] Re: No archive files for static compilation are included in the -dev package
Thank for your bug report, the package is in sync with Debian so could you report the issue there? ** Changed in: graphite2 (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::
Hi everyone! Bug seems to be still there with gnome-shell version 3.36.9 we have ubuntu 20.04 with gdm3, after login, desktop was freezing and syslog filled up to 25G Sep 20 10:04:37 pc18 gnome-shell[487166]: == Stack trace for context 0x5602852a68b0 == Sep 20 10:04:37 pc18 gnome-shell[487166]: message repeated 10 times: [ == Stack trace for context 0x5602852a68b0 ==] Sep 20 10:04:37 pc18 gnome-shell[487166]: The offending callback was AsyncReadyCallback(). Sep 20 10:04:37 pc18 gnome-shell[487166]: message repeated 32 times: [ == Stack trace for context 0x5602852a68b0 ==] Sep 20 10:04:37 pc18 gnome-shell[487166]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Sep 20 10:04:37 pc18 gnome-shell[487166]: The offending callback was SourceFunc(). bug seems to be still open on gnome side: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868 -- 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/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Issue is explained in detail here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 16 18:56:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-01 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+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 1944122] [NEW] Xorg crash
Public bug reported: in the middle of working the GUI crashed (mouse movements yes, no klicks possible) came back, crashed again, login screen appeared. Clearly an issue with AMD-GPU as dmesg states. This report was only possible via ssh from a different machine. Distributor ID: Ubuntu Description:Ubuntu 21.04 Release:21.04 Codename: hirsute Linux peter 5.14.0-051400drmtip20210904-generic #202109040225 SMP Sat Sep 4 02:34:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Sep 20 14:26:27 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20210418, 5.11.0-34-generic, x86_64: installed vhba, 20210418, 5.11.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (278 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 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.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4: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. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 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 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 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 xserver.bootTime: Mon Sep 20 14:25:30 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.1 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash hirsute third-party-packages ubuntu ** Attachment added: "dmesg_20sep2021crasing_APU.txt" https://bugs.launchpad.net/bugs/1944122/+attachment/5526448/+files/dmesg_20sep2021crasing_APU.txt -- 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/1944122 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: in the middle of working the GUI crashed (mouse movements yes, no klicks possible) came back, crashed again, login screen appeared. Clearly an issue with AMD-GPU as dmesg states. This report was only possible via ssh from a different machine. Distributor ID: Ubuntu Description: Ubuntu 21.04 Release: 21.04 Codename: hirsute Linux peter 5.14.0-051400drmtip20210904-generic #202109040225 SMP Sat Sep 4 02:34:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
[Desktop-packages] [Bug 1944119] [NEW] Moving home folder results in programs no longer running, resetting home to original location fixes problem
Public bug reported: Using usermod -d to move home folder; after, any program not installed via apt command (including snaps, appimages, and other binaries installed through dpkg) will start and immediately crash. returning home folder to it's original location resolves the problem. other users of the system are not affected, assuming their home folders are not moved. when moved, the original home folder is left in place, accessible and unmodified. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gvfs 1.47.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 06:34:23 2021 InstallationDate: Installed on 2021-09-15 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs Symptom: storage Title: Documents cannot be opened in desktop UI on storage device UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1944119 Title: Moving home folder results in programs no longer running, resetting home to original location fixes problem Status in gvfs package in Ubuntu: New Bug description: Using usermod -d to move home folder; after, any program not installed via apt command (including snaps, appimages, and other binaries installed through dpkg) will start and immediately crash. returning home folder to it's original location resolves the problem. other users of the system are not affected, assuming their home folders are not moved. when moved, the original home folder is left in place, accessible and unmodified. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gvfs 1.47.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 06:34:23 2021 InstallationDate: Installed on 2021-09-15 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs Symptom: storage Title: Documents cannot be opened in desktop UI on storage device UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1944119/+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 1942437] Re: [UIFe] Impish wallpapers
Uploaded: https://launchpad.net/ubuntu/+source/ubuntu- wallpapers/21.10.1-0ubuntu1 ** Changed in: ubuntu-wallpapers (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1942437 Title: [UIFe] Impish wallpapers Status in ubuntu-wallpapers package in Ubuntu: Fix Committed Bug description: The Impish Indri wallpapers, including two original images that won the wallpaper competition¹, and the official ones produced by the Canonical design team. As we got those past UI freeze (which happened on September 9), this requires a UI freeze exception². Gunnar (~gunnarhj), who is an administrator of both the documentation and translation teams, acknowledged the update in comment #8. ¹ https://ubuntu.com/blog/winners-of-the-21-10-wallpaper-competition ² https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze_Exceptions Original description: We need to include the winners of the 21.10 wallpaper competition in the release image. I don't know how to attack files here so I'll just provide links to the winning images in Discourse: First: https://discourse.ubuntu.com/t/wallpaper-competition-for- impish-indri-ubuntu-21-10/22852/171?u=rhys- davies&_ga=2.144156597.1440561583.1630580808-2071368223.1629705927 Second: https://discourse.ubuntu.com/t/wallpaper-competition-for- impish-indri-ubuntu-21-10/22852/60?u=rhys- davies&_ga=2.144156597.1440561583.1630580808-2071368223.1629705927 Also, I mentioned in the competition that if the Desktop team decided that they could fit more submissions into the release image without it becoming too big, that the next 8 submissions might make it in too. So if you decide you can fit more in please let me or Monica know and take them from the links in this blog post which lists them in the winning order: https://ubuntu.com/blog/winners-of-the-21-10-wallpaper- competition Let me know if there's anything else I can do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1942437/+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 1942437] Re: [UIFe] Impish wallpapers
go for it! ** Changed in: ubuntu-wallpapers (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1942437 Title: [UIFe] Impish wallpapers Status in ubuntu-wallpapers package in Ubuntu: Triaged Bug description: The Impish Indri wallpapers, including two original images that won the wallpaper competition¹, and the official ones produced by the Canonical design team. As we got those past UI freeze (which happened on September 9), this requires a UI freeze exception². Gunnar (~gunnarhj), who is an administrator of both the documentation and translation teams, acknowledged the update in comment #8. ¹ https://ubuntu.com/blog/winners-of-the-21-10-wallpaper-competition ² https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze_Exceptions Original description: We need to include the winners of the 21.10 wallpaper competition in the release image. I don't know how to attack files here so I'll just provide links to the winning images in Discourse: First: https://discourse.ubuntu.com/t/wallpaper-competition-for- impish-indri-ubuntu-21-10/22852/171?u=rhys- davies&_ga=2.144156597.1440561583.1630580808-2071368223.1629705927 Second: https://discourse.ubuntu.com/t/wallpaper-competition-for- impish-indri-ubuntu-21-10/22852/60?u=rhys- davies&_ga=2.144156597.1440561583.1630580808-2071368223.1629705927 Also, I mentioned in the competition that if the Desktop team decided that they could fit more submissions into the release image without it becoming too big, that the next 8 submissions might make it in too. So if you decide you can fit more in please let me or Monica know and take them from the links in this blog post which lists them in the winning order: https://ubuntu.com/blog/winners-of-the-21-10-wallpaper- competition Let me know if there's anything else I can do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1942437/+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 1944113] Re: Many UI elements (list box, drop down) don't work at all in kf5 environment
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1944113 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in libreoffice package in Ubuntu: New Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1944113/+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 1944084] Re: file roller crashed by file.zip 20 GB
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1944084 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1944084 Title: file roller crashed by file.zip 20 GB Status in file-roller package in Ubuntu: New Bug description: First, my English is very bad! Sorry! File roller crashed by files at 20 GB. First I have tried "b1freearchiver": no problems, but not translated in german, than I tried "Ark": perfect, no problems and translated in german, and, surprise, nautilus works with Ark! Could you solve the problem in Gnome: Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1944084/+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 1944113] [NEW] Many UI elements (list box, drop down) don't work at all in kf5 environment
Public bug reported: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: kf5 -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in libreoffice package in Ubuntu: New Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1944113/+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
