[Desktop-packages] [Bug 1978521] brltty crashed with SIGSEGV in runSpeechDriverThread()
StacktraceTop: asyncDiscardEvent (event=0x0) at ../../Programs/async_event.c:147 runSpeechDriverThread (argument=0x5642f4c2b890) at ../../Programs/spk_thread.c:842 runThread (argument=0x5642f4c2bb80) at ../../Programs/thread.c:46 start_thread (arg=) at ./nptl/pthread_create.c:442 clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1978521 Title: brltty crashed with SIGSEGV in runSpeechDriverThread() Status in brltty package in Ubuntu: New Bug description: this problem occurs recurring on every boot ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: brltty 6.4-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.21.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Tue Jun 14 06:24:44 2022 ExecutablePath: /usr/bin/brltty InstallationDate: Installed on 2022-05-14 (30 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512) ProcCmdline: /bin/brltty --no-daemon SegvAnalysis: Segfault happened at: 0x5642f400ee48 :mov 0x20(%rbp),%rdi PC (0x5642f400ee48) ok source "0x20(%rbp)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: brltty StacktraceTop: runSpeechDriverThread () ?? () start_thread (arg=) at ./nptl/pthread_create.c:442 clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Title: brltty crashed with SIGSEGV in runSpeechDriverThread() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1978521/+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 1978521] [NEW] brltty crashed with SIGSEGV in runSpeechDriverThread()
Public bug reported: this problem occurs recurring on every boot ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: brltty 6.4-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.21.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Tue Jun 14 06:24:44 2022 ExecutablePath: /usr/bin/brltty InstallationDate: Installed on 2022-05-14 (30 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512) ProcCmdline: /bin/brltty --no-daemon SegvAnalysis: Segfault happened at: 0x5642f400ee48 : mov 0x20(%rbp),%rdi PC (0x5642f400ee48) ok source "0x20(%rbp)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: brltty StacktraceTop: runSpeechDriverThread () ?? () start_thread (arg=) at ./nptl/pthread_create.c:442 clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Title: brltty crashed with SIGSEGV in runSpeechDriverThread() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: ** Affects: brltty (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1978521 Title: brltty crashed with SIGSEGV in runSpeechDriverThread() Status in brltty package in Ubuntu: New Bug description: this problem occurs recurring on every boot ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: brltty 6.4-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.21.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Tue Jun 14 06:24:44 2022 ExecutablePath: /usr/bin/brltty InstallationDate: Installed on 2022-05-14 (30 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512) ProcCmdline: /bin/brltty --no-daemon SegvAnalysis: Segfault happened at: 0x5642f400ee48 :mov 0x20(%rbp),%rdi PC (0x5642f400ee48) ok source "0x20(%rbp)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: brltty StacktraceTop: runSpeechDriverThread () ?? () start_thread (arg=) at ./nptl/pthread_create.c:442 clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Title: brltty crashed with SIGSEGV in runSpeechDriverThread() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1978521/+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 1978467] Re: Buggy highlighting for active open window app's icon.
*** This bug is a duplicate of bug 1965123 *** https://bugs.launchpad.net/bugs/1965123 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 1965123, 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. ** This bug has been marked a duplicate of bug 1965123 Active launchers area pixels (corners) missing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1978467 Title: Buggy highlighting for active open window app's icon. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: The white highlighting on the open window app's icon is buggy, here is a video showing the bug while discord is the highlighted program: https://www.veed.io/view/2188d755-510a-4ccd-bf8c-b359f8cacc8c (This doesn't only apply to discord, it applies to all the icons) And this doesn't happen all the time, it happens randomly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 16:48:38 2022 InstallationDate: Installed on 2022-06-13 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1978467/+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 1975872] Re: [ASUS GL552VW] Loss of signal (black screen) on external monitor
Sorry my mistake. The minimum value of "max bpc" for your HDMI-2 is 8, as mentioned in the attachment in comment #4. Please use that in a Xorg session and tell us if that solves the problem at 1920x1080: xrandr --output HDMI-2 --set "max bpc" 8 Although you can't change the setting in a Wayland session, you can change it in Xorg and then log out and into a Wayland session and the kernel should remember the same setting. A proper solution is coming in: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2412 -- 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/1975872 Title: [ASUS GL552VW] Loss of signal (black screen) on external monitor Status in mutter package in Ubuntu: Incomplete Bug description: External screen flickers on and off (image is present and then signal is lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh installation. Details: - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make that HDMI work with NVIDIA GTX 960M in my laptop). - Nothing was installed after installing the OS - i connected to the Internet while installing the system and marked the option to download the updates. - I had that issue on Windows 10 - I fixed it by installing a latest Intel GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers installed by Windows - they were the latest Intel drivers. - Internal screen works fine. - If I mirror external and internal monitor, external isn't flickering, but internal monitor's resolution is lower that external's one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 26 22:34:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d] InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. GL552VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1975872/+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 1978488] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1978488/+attachment/5597116/+files/ProcEnviron.txt ** Changed in: ubuntu-mate Status: New => Confirmed ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1978488 Title: LibreOffice Writer lags freezes high CPU 22.04 LTS Status in Ubuntu MATE: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Upgraded to 22.04 LTS (20.04 no issues). Using Nvidia 4xx series driver. 48GB RAM, dual 1080ti gpu, i7 cpu. LibreOffice Writer constantly lags, losing function, freezes (does not crash) with any type of writer document (odt or xslx). New single page or existing multi-page documents, doesn't matter, same issue after a minute or two. Hates text selection, mouse-wheel scrolling is a tell- tale sign. New Writer windows opened during lag are black. CPU usage in htop is very high for soffice.bin, ~60 - 80%. Must pkill the soffice.bin and use file recover but lag freeze up will occur again soon after opening. I experience the issue with all three installation methods: snap, distro command-line install, or using the LibreOffice ppa "fresh". I've tried changing OpenCL settings, disabling all extensions, disable smooth scrolling, disabling java, have purged install/reinstall and limiting to single window. I have the Marco ppa installed (ppa:ubuntu- mate-dev/marco). Doesn't seem to matter or what mate-tweak option is selected. LO using Yaru or other theme; doesn't matter same effect. Terminal does not show me any helpful errors when Writer is called directly from command line, at least I can easily identify. Guessing this is upstream of MATE and a libreoffice thing; a few similar issues around the web but no good workaround. I can update my exact specs and kernel later as required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-03-27 (1174 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Package: nvidia-graphics-drivers-510 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Tags: third-party-packages jammy Uname: Linux 5.15.0-37-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2022-06-03 (10 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1978488/+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 1978488] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1978488/+attachment/5597115/+files/ProcCpuinfoMinimal.txt -- 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/1978488 Title: LibreOffice Writer lags freezes high CPU 22.04 LTS Status in Ubuntu MATE: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Upgraded to 22.04 LTS (20.04 no issues). Using Nvidia 4xx series driver. 48GB RAM, dual 1080ti gpu, i7 cpu. LibreOffice Writer constantly lags, losing function, freezes (does not crash) with any type of writer document (odt or xslx). New single page or existing multi-page documents, doesn't matter, same issue after a minute or two. Hates text selection, mouse-wheel scrolling is a tell- tale sign. New Writer windows opened during lag are black. CPU usage in htop is very high for soffice.bin, ~60 - 80%. Must pkill the soffice.bin and use file recover but lag freeze up will occur again soon after opening. I experience the issue with all three installation methods: snap, distro command-line install, or using the LibreOffice ppa "fresh". I've tried changing OpenCL settings, disabling all extensions, disable smooth scrolling, disabling java, have purged install/reinstall and limiting to single window. I have the Marco ppa installed (ppa:ubuntu- mate-dev/marco). Doesn't seem to matter or what mate-tweak option is selected. LO using Yaru or other theme; doesn't matter same effect. Terminal does not show me any helpful errors when Writer is called directly from command line, at least I can easily identify. Guessing this is upstream of MATE and a libreoffice thing; a few similar issues around the web but no good workaround. I can update my exact specs and kernel later as required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-03-27 (1174 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Package: nvidia-graphics-drivers-510 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Tags: third-party-packages jammy Uname: Linux 5.15.0-37-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2022-06-03 (10 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1978488/+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 1978488] Re: LibreOffice Writer lags freezes high CPU 22.04 LTS
apport information ** Tags added: apport-collected third-party-packages ** Description changed: Upgraded to 22.04 LTS (20.04 no issues). Using Nvidia 4xx series driver. 48GB RAM, dual 1080ti gpu, i7 cpu. LibreOffice Writer constantly lags, losing function, freezes (does not crash) with any type of writer document (odt or xslx). New single page or existing multi-page documents, doesn't matter, same issue after a minute or two. Hates text selection, mouse-wheel scrolling is a tell- tale sign. New Writer windows opened during lag are black. CPU usage in htop is very high for soffice.bin, ~60 - 80%. Must pkill the soffice.bin and use file recover but lag freeze up will occur again soon after opening. I experience the issue with all three installation methods: snap, distro command-line install, or using the LibreOffice ppa "fresh". I've tried changing OpenCL settings, disabling all extensions, disable smooth scrolling, disabling java, have purged install/reinstall and limiting to single window. I have the Marco ppa installed (ppa:ubuntu- mate-dev/marco). Doesn't seem to matter or what mate-tweak option is selected. LO using Yaru or other theme; doesn't matter same effect. Terminal does not show me any helpful errors when Writer is called directly from command line, at least I can easily identify. Guessing this is upstream of MATE and a libreoffice thing; a few similar issues around the web but no good workaround. I can update my exact specs and kernel later as required. Thanks! + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: MATE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2019-03-27 (1174 days ago) + InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) + Package: nvidia-graphics-drivers-510 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 + Tags: third-party-packages jammy + Uname: Linux 5.15.0-37-generic x86_64 + UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. + UpgradeStatus: Upgraded to jammy on 2022-06-03 (10 days ago) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1978488/+attachment/5597114/+files/Dependencies.txt -- 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/1978488 Title: LibreOffice Writer lags freezes high CPU 22.04 LTS Status in Ubuntu MATE: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Upgraded to 22.04 LTS (20.04 no issues). Using Nvidia 4xx series driver. 48GB RAM, dual 1080ti gpu, i7 cpu. LibreOffice Writer constantly lags, losing function, freezes (does not crash) with any type of writer document (odt or xslx). New single page or existing multi-page documents, doesn't matter, same issue after a minute or two. Hates text selection, mouse-wheel scrolling is a tell- tale sign. New Writer windows opened during lag are black. CPU usage in htop is very high for soffice.bin, ~60 - 80%. Must pkill the soffice.bin and use file recover but lag freeze up will occur again soon after opening. I experience the issue with all three installation methods: snap, distro command-line install, or using the LibreOffice ppa "fresh". I've tried changing OpenCL settings, disabling all extensions, disable smooth scrolling, disabling java, have purged install/reinstall and limiting to single window. I have the Marco ppa installed (ppa:ubuntu- mate-dev/marco). Doesn't seem to matter or what mate-tweak option is selected. LO using Yaru or other theme; doesn't matter same effect. Terminal does not show me any helpful errors when Writer is called directly from command line, at least I can easily identify. Guessing this is upstream of MATE and a libreoffice thing; a few similar issues around the web but no good workaround. I can update my exact specs and kernel later as required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-03-27 (1174 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Package: nvidia-graphics-drivers-510 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1978341] Re: Merge for xdg-desktop-portal 1.14.4 from Debian unstable
** Changed in: xdg-desktop-portal (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1978341
Title:
Merge for xdg-desktop-portal 1.14.4 from Debian unstable
Status in xdg-desktop-portal package in Ubuntu:
Fix Released
Bug description:
This is a merge request for 1.14.4.
==> debian/changelog <==
xdg-desktop-portal (1.14.4-1ubuntu1) UNRELEASED; urgency=medium
* Merge from Debian. Remaining changes:
- debian/patches/{01..11}webextensions-portal.patch
* Single patch file was split into multiple files to avoid dpkg-source
complaining that it patched files multiple times.
-- Nathan Pratta Teodosio Fri, 10 Jun 2022
14:08:05 -0300
==> END <==
Build tested with Pbuilder.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978341/+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 1978486] Re: Right clicks on file icons select a different file
I use xorg. I have attached a movie of this behavior. ** Attachment added: "Screencast from 06-13-2022 04:40:04 PM.webm" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978486/+attachment/5597095/+files/Screencast%20from%2006-13-2022%2004%3A40%3A04%20PM.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1978486 Title: Right clicks on file icons select a different file Status in nautilus package in Ubuntu: Incomplete Bug description: Upgraded to 20.04 from 18.04. Right clicking on files in icon view will always select a different file. This does not happen in list (or detail) mode. Switching between the two modes several times will sometimes make the functionality work for a while in icon mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 11:47:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (2894 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2022-06-07 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-07-06T11:04:37.239623 usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978486/+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 1978486] Re: Right clicks on file icons select a different file
Thank you for your bug report, could you do a video showing the issue? Do you use xorg or wayland? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1978486 Title: Right clicks on file icons select a different file Status in nautilus package in Ubuntu: Incomplete Bug description: Upgraded to 20.04 from 18.04. Right clicking on files in icon view will always select a different file. This does not happen in list (or detail) mode. Switching between the two modes several times will sometimes make the functionality work for a while in icon mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 11:47:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (2894 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2022-06-07 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-07-06T11:04:37.239623 usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978486/+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 1978491] Re: print colors as gray not saved
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1978491 Title: print colors as gray not saved Status in gnome-control-center package in Ubuntu: New Bug description: Hi, i noticed that my printer printed in grayscale and the setting in gnome-control-center is always yes. i can change the setting in "additional settings" below the printer list with opens a filemanager like view with all printers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Jun 13 18:59:40 2022 InstallationDate: Installed on 2022-05-22 (22 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1978491/+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 1008213] Re: Missing depends on whoopsie.
** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Summary changed: - Missing depends on whoopsie. + whoopsie used in dbus config without depends -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1008213 Title: whoopsie used in dbus config without depends Status in network-manager package in Ubuntu: Confirmed Bug description: By depends I mean one of Suggests/Recommends/Depends. Currently, with no other changes, I'd say you need Depends. Thus I think you should change part of your package to accommodate for systems that don't have whoopsie installed. /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf:91: This leads to... arcadia:~# cat /var/log/upstart/dbus.log Unknown username "whoopsie" in message bus configuration file It's not an error and it doesn't break anything, but it should be easy for you to change things a little. One option is to create this user, though I'd coordinate that with the whoopsie developer. A perhaps better solution is to split this configuration out so that is will only be included if/when whoopsie is installed or the whoopsie user is available. Thank you. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-23.31-lowlatency-pae 3.2.14 Uname: Linux 3.2.0-23-lowlatency-pae i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Sun Jun 3 15:05:40 2012 IpRoute: default via 192.168.172.100 dev eth2 metric 100 169.254.0.0/16 dev eth2 scope link metric 1000 192.168.172.0/24 dev eth2 proto kernel scope link src 192.168.172.26 IwConfig: Error: [Errno 2] No such file or directory NetDevice.eth2: Error: [Errno 2] No such file or directory X: INTERFACE_MAC=f4:6d:04:2c:0a:e1 NetDevice.lo: Error: [Errno 2] No such file or directory X: INTERFACE_MAC=00:00:00:00:00:00 NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=false RfKill: Error: [Errno 2] No such file or directory SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-01-03 (152 days ago) WpaSupplicantLog: nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto eth8 759a3094-00a2-4699-bcb0-99d4662887a6 802-3-ethernet0never no no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth2 802-3-ethernetunmanaged /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0asleep disabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1008213/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
The kernel you are trying might have a different configuration leading to have apparmor not enforced the same way perhaps? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Confirmed Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
This may be an Ubuntu kernel problem. I have upgraded my kernel from 5.15.0.37.39 to 5.15.1-051501.202111061036 without changing anything else, and the mentioned problem with Evince has gone away. But this problem resurfaces after changing back to the previous kernel 5.15.0.37.39 from grub during boot. So, some changes from kernel 5.15.0.37.39 to 5.15.1-051501.202111061036 solve this problem. Can anybody confirm this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Confirmed Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
Works for me, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Confirmed Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+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 1978385] Re: systemctl enable gdm3 failes lts 22
** Package changed: ubuntu => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1978385 Title: systemctl enable gdm3 failes lts 22 Status in gdm3 package in Ubuntu: New Bug description: systemctl disable lightdm - works systemctl enable gdm3 - fails up on latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1978385/+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 1978385] [NEW] systemctl enable gdm3 failes lts 22
You have been subscribed to a public bug: systemctl disable lightdm - works systemctl enable gdm3 - fails up on latest update ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- systemctl enable gdm3 failes lts 22 https://bugs.launchpad.net/bugs/1978385 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1008213] Re: Missing depends on whoopsie.
This bug still persists. Ubuntu MATE 20.04.4, network-manager 1.22.10-1ubuntu2.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1008213 Title: Missing depends on whoopsie. Status in network-manager package in Ubuntu: Confirmed Bug description: By depends I mean one of Suggests/Recommends/Depends. Currently, with no other changes, I'd say you need Depends. Thus I think you should change part of your package to accommodate for systems that don't have whoopsie installed. /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf:91: This leads to... arcadia:~# cat /var/log/upstart/dbus.log Unknown username "whoopsie" in message bus configuration file It's not an error and it doesn't break anything, but it should be easy for you to change things a little. One option is to create this user, though I'd coordinate that with the whoopsie developer. A perhaps better solution is to split this configuration out so that is will only be included if/when whoopsie is installed or the whoopsie user is available. Thank you. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-23.31-lowlatency-pae 3.2.14 Uname: Linux 3.2.0-23-lowlatency-pae i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Sun Jun 3 15:05:40 2012 IpRoute: default via 192.168.172.100 dev eth2 metric 100 169.254.0.0/16 dev eth2 scope link metric 1000 192.168.172.0/24 dev eth2 proto kernel scope link src 192.168.172.26 IwConfig: Error: [Errno 2] No such file or directory NetDevice.eth2: Error: [Errno 2] No such file or directory X: INTERFACE_MAC=f4:6d:04:2c:0a:e1 NetDevice.lo: Error: [Errno 2] No such file or directory X: INTERFACE_MAC=00:00:00:00:00:00 NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=false RfKill: Error: [Errno 2] No such file or directory SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-01-03 (152 days ago) WpaSupplicantLog: nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto eth8 759a3094-00a2-4699-bcb0-99d4662887a6 802-3-ethernet0never no no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth2 802-3-ethernetunmanaged /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0asleep disabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1008213/+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 1978491] [NEW] print colors as gray not saved
Public bug reported: Hi, i noticed that my printer printed in grayscale and the setting in gnome- control-center is always yes. i can change the setting in "additional settings" below the printer list with opens a filemanager like view with all printers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Jun 13 18:59:40 2022 InstallationDate: Installed on 2022-05-22 (22 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "location of setting" https://bugs.launchpad.net/bugs/1978491/+attachment/5597078/+files/gnome-control-center.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1978491 Title: print colors as gray not saved Status in gnome-control-center package in Ubuntu: New Bug description: Hi, i noticed that my printer printed in grayscale and the setting in gnome-control-center is always yes. i can change the setting in "additional settings" below the printer list with opens a filemanager like view with all printers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Jun 13 18:59:40 2022 InstallationDate: Installed on 2022-05-22 (22 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1978491/+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 1978488] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1978488 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1978488 Title: LibreOffice Writer lags freezes high CPU 22.04 LTS Status in Ubuntu MATE: New Status in libreoffice package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Upgraded to 22.04 LTS (20.04 no issues). Using Nvidia 4xx series driver. 48GB RAM, dual 1080ti gpu, i7 cpu. LibreOffice Writer constantly lags, losing function, freezes (does not crash) with any type of writer document (odt or xslx). New single page or existing multi-page documents, doesn't matter, same issue after a minute or two. Hates text selection, mouse-wheel scrolling is a tell- tale sign. New Writer windows opened during lag are black. CPU usage in htop is very high for soffice.bin, ~60 - 80%. Must pkill the soffice.bin and use file recover but lag freeze up will occur again soon after opening. I experience the issue with all three installation methods: snap, distro command-line install, or using the LibreOffice ppa "fresh". I've tried changing OpenCL settings, disabling all extensions, disable smooth scrolling, disabling java, have purged install/reinstall and limiting to single window. I have the Marco ppa installed (ppa:ubuntu- mate-dev/marco). Doesn't seem to matter or what mate-tweak option is selected. LO using Yaru or other theme; doesn't matter same effect. Terminal does not show me any helpful errors when Writer is called directly from command line, at least I can easily identify. Guessing this is upstream of MATE and a libreoffice thing; a few similar issues around the web but no good workaround. I can update my exact specs and kernel later as required. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1978488/+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 1978488] Re: LibreOffice Writer lags freezes high CPU 22.04 LTS
Please run apport-collect 1978488 ** Also affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags removed: 22.04 libreoffice writer ** Tags added: jammy ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New -- 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/1978488 Title: LibreOffice Writer lags freezes high CPU 22.04 LTS Status in Ubuntu MATE: New Status in libreoffice package in Ubuntu: New Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Upgraded to 22.04 LTS (20.04 no issues). Using Nvidia 4xx series driver. 48GB RAM, dual 1080ti gpu, i7 cpu. LibreOffice Writer constantly lags, losing function, freezes (does not crash) with any type of writer document (odt or xslx). New single page or existing multi-page documents, doesn't matter, same issue after a minute or two. Hates text selection, mouse-wheel scrolling is a tell- tale sign. New Writer windows opened during lag are black. CPU usage in htop is very high for soffice.bin, ~60 - 80%. Must pkill the soffice.bin and use file recover but lag freeze up will occur again soon after opening. I experience the issue with all three installation methods: snap, distro command-line install, or using the LibreOffice ppa "fresh". I've tried changing OpenCL settings, disabling all extensions, disable smooth scrolling, disabling java, have purged install/reinstall and limiting to single window. I have the Marco ppa installed (ppa:ubuntu- mate-dev/marco). Doesn't seem to matter or what mate-tweak option is selected. LO using Yaru or other theme; doesn't matter same effect. Terminal does not show me any helpful errors when Writer is called directly from command line, at least I can easily identify. Guessing this is upstream of MATE and a libreoffice thing; a few similar issues around the web but no good workaround. I can update my exact specs and kernel later as required. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1978488/+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 1978486] [NEW] Right clicks on file icons select a different file
Public bug reported: Upgraded to 20.04 from 18.04. Right clicking on files in icon view will always select a different file. This does not happen in list (or detail) mode. Switching between the two modes several times will sometimes make the functionality work for a while in icon mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 11:47:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (2894 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2022-06-07 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-07-06T11:04:37.239623 usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1978486 Title: Right clicks on file icons select a different file Status in nautilus package in Ubuntu: New Bug description: Upgraded to 20.04 from 18.04. Right clicking on files in icon view will always select a different file. This does not happen in list (or detail) mode. Switching between the two modes several times will sometimes make the functionality work for a while in icon mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 11:47:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (2894 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2022-06-07 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-07-06T11:04:37.239623 usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978486/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
To summarize for other people with the problem: `sudo aa-complain /usr/bin/evince` fixes this for me. (I had to install the apparmor-utils package to run that) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Confirmed Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+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 1978429] Re: Crashes when smart info is open while the drive is pulled
Thanks! ** Changed in: gnome-disk-utility (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1978429 Title: Crashes in udisks_drive_ata_get_smart_enabled when smart info is open while the drive is pulled Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: 1. Open smart data for a given drive (not the boot drive, *points at step 2*) 2. detach drive from system (sata drives support hot swap) 3. wait a few seconds 4. disk utility has crashed if smart info is not open it will not crash and the drive drops out of the drive list the smart data window should either close or remain open and stop updating if the drive is removed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 42.0-1ubuntu1 Uname: Linux 5.17.13-051713-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Jun 12 22:42:11 2022 InstallationDate: Installed on 2021-11-26 (198 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211126) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1978429/+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 1978485] Re: /usr/bin/gnome-disks:11:udisks_drive_ata_get_smart_enabled:update_updated_label:on_timeout:g_timeout_dispatch:g_main_dispatch
*** This bug is a duplicate of bug 1978429 *** https://bugs.launchpad.net/bugs/1978429 ** This bug has been marked a duplicate of bug 1978429 Crashes when smart info is open while the drive is pulled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1978485 Title: /usr/bin/gnome- disks:11:udisks_drive_ata_get_smart_enabled:update_updated_label:on_timeout:g_timeout_dispatch:g_main_dispatch Status in gnome-disk-utility package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-disk-utility. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/f0a06990b03ac728dd70db5feea2bb202ff21015 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1978485/+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 1978429] Re: Crashes when smart info is open while the drive is pulled
Corresponding report https://errors.ubuntu.com/problem/f0a06990b03ac728dd70db5feea2bb202ff21015 ** Summary changed: - Crashes when smart info is open while the drive is pulled + Crashes in udisks_drive_ata_get_smart_enabled when smart info is open while the drive is pulled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1978429 Title: Crashes in udisks_drive_ata_get_smart_enabled when smart info is open while the drive is pulled Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: 1. Open smart data for a given drive (not the boot drive, *points at step 2*) 2. detach drive from system (sata drives support hot swap) 3. wait a few seconds 4. disk utility has crashed if smart info is not open it will not crash and the drive drops out of the drive list the smart data window should either close or remain open and stop updating if the drive is removed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 42.0-1ubuntu1 Uname: Linux 5.17.13-051713-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Jun 12 22:42:11 2022 InstallationDate: Installed on 2021-11-26 (198 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211126) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1978429/+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 1978485] [NEW] /usr/bin/gnome-disks:11:udisks_drive_ata_get_smart_enabled:update_updated_label:on_timeout:g_timeout_dispatch:g_main_dispatch
*** This bug is a duplicate of bug 1978429 *** https://bugs.launchpad.net/bugs/1978429 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-disk-utility. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/f0a06990b03ac728dd70db5feea2bb202ff21015 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: 5.1 artful bionic cosmic disco impish jammy saucy trusty utopic vivid wily xenial yakkety zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1978485 Title: /usr/bin/gnome- disks:11:udisks_drive_ata_get_smart_enabled:update_updated_label:on_timeout:g_timeout_dispatch:g_main_dispatch Status in gnome-disk-utility package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-disk-utility. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/f0a06990b03ac728dd70db5feea2bb202ff21015 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1978485/+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 1978476] Re: Incorrect UNTIL recurrence with midnight start
Thank you for the bug report, upstreamed fixed it for 3.44.3+ so it will be fixed in Ubuntu when that version lands ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Low ** Changed in: evolution-data-server (Ubuntu) Status: New => Triaged ** Changed in: evolution-data-server (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1978476 Title: Incorrect UNTIL recurrence with midnight start Status in evolution-data-server package in Ubuntu: Fix Committed Bug description: EDS generates instances for recurring events starting at midnight with an UNTIL date incorrectly. Specifically, using e_cal_client_generate_instances() or e_cal_recur_generate_instances_sync() generates an instance one day after the UNTIL date. This bug was introduced with the migration to libical-glib and libecal-2.0, so this affects bot focal and jammy. It was fixed with commit 3969303e (master) and 7fb64814 (gnome-42) which will be part of the 3.45.1+ and 3.44.3+ releases respectively. Upstream bug report: https://gitlab.gnome.org/GNOME/evolution-data- server/-/issues/393 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1978476/+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 1944667] Re: High CPU usage in Xorg with NVIDIA reverse prime external monitor
I have a very simple solution that solved it for me. I have an Acer Nitro with NVIDIA GeForce GTX 1650. After installing Ubuntu 22.04, every time I attached an external monitor the Xorg CPU usage was 25% - 33% even when nothing is running. This happens with driver 470 and 510. To fix it - run the NVidia X-server settings app. Under Prime Profiles, select NVIDIA (Performance Mode). Reboot. Now Xorg CPU usage is 0.3%. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1944667 Title: High CPU usage in Xorg with NVIDIA reverse prime external monitor Status in nvidia-graphics-drivers-470 package in Ubuntu: Expired Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: With my Legion Slim 7 in hybrid graphics mode (using amdgpu to drive the laptop display) and an external monitor connected via the nvidia card on a USB-C/HDMI connection, Xorg consistently uses around 40% CPU even with no apps running. If I put the laptop in discrete graphics mode so the nvidia card drives both the laptop display and the external monitor Xorg uses close to 0% CPU, which is what I would expect it to be in hybrid mode. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-core 2:1.20.13-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Thu Sep 23 11:48:15 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.13.0-16-generic, x86_64: installed nvidia, 470.63.01, 5.14.5-051405-generic, x86_64: installed nvidia, 470.63.01, 5.15.0-051500rc2-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3801] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:380c] InstallationDate: Installed on 2021-09-15 (8 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet splash amdgpu.backlight=0 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: HACN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 15ACH6 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6: dmi.product.family: Legion S7 15ACH6 dmi.product.name: 82K8 dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6 dmi.product.version: Legion S7 15ACH6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed
Sorry to inform that Nvidia 340.108 patched by ppa:kelebek333/nvidia-legacy does NOT compile on new kernel 5.18. Here is terminal output during compilation: Building module: cleaning build area... [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; make -k module KERNDIR=/lib/modules/5.18-051800-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/5.18-051800-generic/build LD=/usr/bin/ld.bfd; make -C uvm module KERNEL_UNAME=5.18-051800-generic KBUILD_EXTMOD=/var/lib/dkms/nvidia-340/340.108/build/uvm...(bad exit status: 2) ERROR (dkms apport): kernel package linux-headers-5.18-051800-generic is not supported Error! Bad return status for module build on kernel: 5.18-051800-generic (x86_64) Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information. You may find a make.log file attached to find more details.. Just to inform you that updated patches for Nvidia 340.108 and kernel 5.18 are available here: minimyth2/script/nvidia/nvidia-340.108/files at master · warpme/minimyth2 (github.com) The site https://nvidia.if-not-true-then-false.com/patcher/NVIDIA-340xx/ also updated the patches. Thanks in advance to a willing developer who will endeavor to compile a new working driver... ** Attachment added: "Nvidia 340.108 patched by ppa:kelebek333/nvidia-legacy does NOT compile on new kernel 5.18" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+attachment/5597062/+files/make.log ** Summary changed: - Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed + Nvidia 340.108 fails to install with kernels 5.1x - new patches needeed -- 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/1916640 Title: Nvidia 340.108 fails to install with kernels 5.1x - new patches needeed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: As usual I have opened this (no more) new bug report... As ALWAYS happened in the past, EVERY TWO MONTHS new patches are needed for old Nvidia 340.108 drivers, that is, with each release of a new kernel... Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.11 is not yet available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Anyway thanks for your great contribution to community and hope you publish new patched drivers without having to always report the same bug... Good day to all the developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+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 1978476] [NEW] Incorrect UNTIL recurrence with midnight start
Public bug reported: EDS generates instances for recurring events starting at midnight with an UNTIL date incorrectly. Specifically, using e_cal_client_generate_instances() or e_cal_recur_generate_instances_sync() generates an instance one day after the UNTIL date. This bug was introduced with the migration to libical-glib and libecal-2.0, so this affects bot focal and jammy. It was fixed with commit 3969303e (master) and 7fb64814 (gnome-42) which will be part of the 3.45.1+ and 3.44.3+ releases respectively. Upstream bug report: https://gitlab.gnome.org/GNOME/evolution-data- server/-/issues/393 ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1978476 Title: Incorrect UNTIL recurrence with midnight start Status in evolution-data-server package in Ubuntu: New Bug description: EDS generates instances for recurring events starting at midnight with an UNTIL date incorrectly. Specifically, using e_cal_client_generate_instances() or e_cal_recur_generate_instances_sync() generates an instance one day after the UNTIL date. This bug was introduced with the migration to libical-glib and libecal-2.0, so this affects bot focal and jammy. It was fixed with commit 3969303e (master) and 7fb64814 (gnome-42) which will be part of the 3.45.1+ and 3.44.3+ releases respectively. Upstream bug report: https://gitlab.gnome.org/GNOME/evolution-data- server/-/issues/393 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1978476/+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 1975638] Re: Broken background portal autostart in 1.14.3
** Description changed: - Impact With 1.14.3 the background portal creates a broken autostart file (it sends an incorrectly quoted app ID to implementations). This means apps like EasyEffects or Pika Backup cannot rely on the background portal to create a working autostart file. Please update to xdg-desktop-portal 1.14.4 https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.14.4 which fixes this issue. - Test Case 1. Install ASHPD Demo https://flathub.org/apps/details/com.belmoussaoui.ashpd.demo from Flathub 2. Within the app make a background portal request with auto start enabled (you must accept the prompt from GNOME Shell) 3. Note the contents of ~/.config/autostart/com.belmoussaoui.ashpd.demo.desktop is a desktop file, however the exec key’s value has an app id with quotes, making it invalid. 4. After logging out and in or restarting, the app will not already be running, even though it previously asked the portal API for it to be auto started. The same steps can be repeated with EasyEffects from Flathub instead of ASHPD Demo, note the EasyEffects switch is named "Start Service at Login" within EasyEffects' preferences menu. When the bug is fixed, the created desktop file for auto start is valid and the app will start after login. - Regression potential + The update is a new minor version including the fix for that bug and + translation updates (which are going to be imported by launchpad but not + part of the deb on Ubuntu) + The codepath change is specific to flatpak commandline parsing so check that flatpaks still start correctly -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1975638 Title: Broken background portal autostart in 1.14.3 Status in xdg-desktop-portal package in Ubuntu: Fix Committed Bug description: - Impact With 1.14.3 the background portal creates a broken autostart file (it sends an incorrectly quoted app ID to implementations). This means apps like EasyEffects or Pika Backup cannot rely on the background portal to create a working autostart file. Please update to xdg- desktop-portal 1.14.4 https://github.com/flatpak/xdg-desktop- portal/releases/tag/1.14.4 which fixes this issue. - Test Case 1. Install ASHPD Demo https://flathub.org/apps/details/com.belmoussaoui.ashpd.demo from Flathub 2. Within the app make a background portal request with auto start enabled (you must accept the prompt from GNOME Shell) 3. Note the contents of ~/.config/autostart/com.belmoussaoui.ashpd.demo.desktop is a desktop file, however the exec key’s value has an app id with quotes, making it invalid. 4. After logging out and in or restarting, the app will not already be running, even though it previously asked the portal API for it to be auto started. The same steps can be repeated with EasyEffects from Flathub instead of ASHPD Demo, note the EasyEffects switch is named "Start Service at Login" within EasyEffects' preferences menu. When the bug is fixed, the created desktop file for auto start is valid and the app will start after login. - Regression potential The update is a new minor version including the fix for that bug and translation updates (which are going to be imported by launchpad but not part of the deb on Ubuntu) The codepath change is specific to flatpak commandline parsing so check that flatpaks still start correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1975638/+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 1975638] Re: Broken background portal autostart in 1.14.3
** Description changed: + - Impact + With 1.14.3 the background portal creates a broken autostart file (it sends an incorrectly quoted app ID to implementations). This means apps like EasyEffects or Pika Backup cannot rely on the background portal to create a working autostart file. Please update to xdg-desktop-portal 1.14.4 https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.14.4 which fixes this issue. + + - Test Case + + 1. Install ASHPD Demo + https://flathub.org/apps/details/com.belmoussaoui.ashpd.demo from + Flathub + + 2. Within the app make a background portal request with auto start + enabled (you must accept the prompt from GNOME Shell) + + 3. Note the contents of + ~/.config/autostart/com.belmoussaoui.ashpd.demo.desktop is a desktop + file, however the exec key’s value has an app id with quotes, making it + invalid. + + 4. After logging out and in or restarting, the app will not already be + running, even though it previously asked the portal API for it to be + auto started. + + The same steps can be repeated with EasyEffects from Flathub instead of + ASHPD Demo, note the EasyEffects switch is named "Start Service at + Login" within EasyEffects' preferences menu. + + When the bug is fixed, the created desktop file for auto start is valid + and the app will start after login. + + - Regression potential + + The codepath change is specific to flatpak commandline parsing so check + that flatpaks still start correctly -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1975638 Title: Broken background portal autostart in 1.14.3 Status in xdg-desktop-portal package in Ubuntu: Fix Committed Bug description: - Impact With 1.14.3 the background portal creates a broken autostart file (it sends an incorrectly quoted app ID to implementations). This means apps like EasyEffects or Pika Backup cannot rely on the background portal to create a working autostart file. Please update to xdg- desktop-portal 1.14.4 https://github.com/flatpak/xdg-desktop- portal/releases/tag/1.14.4 which fixes this issue. - Test Case 1. Install ASHPD Demo https://flathub.org/apps/details/com.belmoussaoui.ashpd.demo from Flathub 2. Within the app make a background portal request with auto start enabled (you must accept the prompt from GNOME Shell) 3. Note the contents of ~/.config/autostart/com.belmoussaoui.ashpd.demo.desktop is a desktop file, however the exec key’s value has an app id with quotes, making it invalid. 4. After logging out and in or restarting, the app will not already be running, even though it previously asked the portal API for it to be auto started. The same steps can be repeated with EasyEffects from Flathub instead of ASHPD Demo, note the EasyEffects switch is named "Start Service at Login" within EasyEffects' preferences menu. When the bug is fixed, the created desktop file for auto start is valid and the app will start after login. - Regression potential The codepath change is specific to flatpak commandline parsing so check that flatpaks still start correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1975638/+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 1975638] Re: Broken background portal autostart in 1.14.3
Thanks, the new version is merged in https://bugs.launchpad.net/ubuntu/+source/xdg-desktop- portal/1.14.4-1ubuntu1 and we will also SRU that update to the LTS ** Changed in: xdg-desktop-portal (Ubuntu) Importance: Undecided => Low ** Changed in: xdg-desktop-portal (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1975638 Title: Broken background portal autostart in 1.14.3 Status in xdg-desktop-portal package in Ubuntu: Fix Committed Bug description: With 1.14.3 the background portal creates a broken autostart file (it sends an incorrectly quoted app ID to implementations). This means apps like EasyEffects or Pika Backup cannot rely on the background portal to create a working autostart file. Please update to xdg- desktop-portal 1.14.4 https://github.com/flatpak/xdg-desktop- portal/releases/tag/1.14.4 which fixes this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1975638/+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 1978467] [NEW] Buggy highlighting for active open window app's icon.
Public bug reported: The white highlighting on the open window app's icon is buggy, here is a video showing the bug while discord is the highlighted program: https://www.veed.io/view/2188d755-510a-4ccd-bf8c-b359f8cacc8c (This doesn't only apply to discord, it applies to all the icons) And this doesn't happen all the time, it happens randomly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 16:48:38 2022 InstallationDate: Installed on 2022-06-13 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: - The white highlighting on the open window app's icon is buggy, here is a - video showing the bug while discord is the highlighted program: - https://www.veed.io/view/2188d755-510a-4ccd-bf8c-b359f8cacc8c + The white highlighting on the open window app's icon is buggy, here is a video showing the bug while discord is the highlighted program: https://www.veed.io/view/2188d755-510a-4ccd-bf8c-b359f8cacc8c + (This doesn't only apply to discord, it applies to all the icons) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 16:48:38 2022 InstallationDate: Installed on 2022-06-13 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: The white highlighting on the open window app's icon is buggy, here is a video showing the bug while discord is the highlighted program: https://www.veed.io/view/2188d755-510a-4ccd-bf8c-b359f8cacc8c (This doesn't only apply to discord, it applies to all the icons) + And this doesn't happen all the time, it happens randomly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 16:48:38 2022 InstallationDate: Installed on 2022-06-13 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1978467 Title: Buggy highlighting for active open window app's icon. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: The white highlighting on the open window app's icon is buggy, here is a video showing the bug while discord is the highlighted program: https://www.veed.io/view/2188d755-510a-4ccd-bf8c-b359f8cacc8c (This doesn't only apply to discord, it applies to all the icons) And this doesn't happen all the time, it happens randomly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 16:48:38 2022 InstallationDate: Installed on 2022-06-13 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1978467/+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 1975872] Re: [ASUS GL552VW] Loss of signal (black screen) on external monitor
Sorry, I forgot to add that I did all of those actions in Xorg session. Xrandr wouldn't let me change output settings If I was in Wayland session. Unfortunately, changing max bpc to 6 under Xorg session didn't give an effect - screen is still flickering, although not so violently. I tried to change it to lower numbers, such as 3, but no luck either. -- 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/1975872 Title: [ASUS GL552VW] Loss of signal (black screen) on external monitor Status in mutter package in Ubuntu: Incomplete Bug description: External screen flickers on and off (image is present and then signal is lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh installation. Details: - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make that HDMI work with NVIDIA GTX 960M in my laptop). - Nothing was installed after installing the OS - i connected to the Internet while installing the system and marked the option to download the updates. - I had that issue on Windows 10 - I fixed it by installing a latest Intel GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers installed by Windows - they were the latest Intel drivers. - Internal screen works fine. - If I mirror external and internal monitor, external isn't flickering, but internal monitor's resolution is lower that external's one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 26 22:34:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d] InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. GL552VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1975872/+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 1978429] Re: Crashes when smart info is open while the drive is pulled
https://errors.ubuntu.com/oops/e159c992-eb0c-11ec-abf9-fa163ef35206 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1978429 Title: Crashes when smart info is open while the drive is pulled Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: 1. Open smart data for a given drive (not the boot drive, *points at step 2*) 2. detach drive from system (sata drives support hot swap) 3. wait a few seconds 4. disk utility has crashed if smart info is not open it will not crash and the drive drops out of the drive list the smart data window should either close or remain open and stop updating if the drive is removed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 42.0-1ubuntu1 Uname: Linux 5.17.13-051713-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Jun 12 22:42:11 2022 InstallationDate: Installed on 2021-11-26 (198 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211126) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1978429/+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 1973269] Re: Upgrading LibreOffice 7 on Ubuntu 20.04 reset app and settings
After last upgrade settings was reset again and I Just solved in this way: mv ~/snap/libreoffice/256/.config/libreoffice/4/user/ ~/snap/libreoffice/256/.config/libreoffice/4/user.orig cp -av ~/snap/libreoffice/254/.config/libreoffice/4/user/ ~/snap/libreoffice/256/.config/libreoffice/4/ Cheers -- 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/1973269 Title: Upgrading LibreOffice 7 on Ubuntu 20.04 reset app and settings Status in libreoffice package in Ubuntu: New Bug description: Hi everyone, I have a problem with LibreOffice 7.3, every time I upgrade the snap app it will reset my LibreOffice settings, recent files and extensions! Does anyone has the same problem? Some details: snap 2.55.3 snapd 2.55.3 series 16 ubuntu 20.04 kernel 5.14.0-1036-oem Description: Ubuntu 20.04.4 LTS Release: 20.04 libreoffice 7.3.3.2 254 latest/stable canonical✓ - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1973269/+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 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly
If it's still unreliable then try 6 instead of 8, but 8 should look better. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => In Progress -- 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/1929209 Title: [i915] external monitor goes black for several seconds at a time, randomly Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: At times it is completely debilitating; at other times it does not happen for hours. The physical connections are clean and solid. I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:56:04 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (847 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+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 1978341] Re: Merge for xdg-desktop-portal 1.14.4 from Debian unstable
I uploaded xdg-desktop-portal 1.14.4-1ubuntu1 to kinetic, but I forgot
to include a reference to this bug in the changelog entry, so I'm
manually updating the status.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1978341
Title:
Merge for xdg-desktop-portal 1.14.4 from Debian unstable
Status in xdg-desktop-portal package in Ubuntu:
Fix Committed
Bug description:
This is a merge request for 1.14.4.
==> debian/changelog <==
xdg-desktop-portal (1.14.4-1ubuntu1) UNRELEASED; urgency=medium
* Merge from Debian. Remaining changes:
- debian/patches/{01..11}webextensions-portal.patch
* Single patch file was split into multiple files to avoid dpkg-source
complaining that it patched files multiple times.
-- Nathan Pratta Teodosio Fri, 10 Jun 2022
14:08:05 -0300
==> END <==
Build tested with Pbuilder.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978341/+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 1978341] Re: Merge for xdg-desktop-portal 1.14.4 from Debian unstable
I can confirm dpkg-source does complain about files being patches
multiple times by a single patch, and it makes it a fatal error. That
doesn't sound right to me, but this is not the place to discuss it. If I
apply the patch with quilt before building the source package, the error
goes away.
** Changed in: xdg-desktop-portal (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: xdg-desktop-portal (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1978341
Title:
Merge for xdg-desktop-portal 1.14.4 from Debian unstable
Status in xdg-desktop-portal package in Ubuntu:
Fix Committed
Bug description:
This is a merge request for 1.14.4.
==> debian/changelog <==
xdg-desktop-portal (1.14.4-1ubuntu1) UNRELEASED; urgency=medium
* Merge from Debian. Remaining changes:
- debian/patches/{01..11}webextensions-portal.patch
* Single patch file was split into multiple files to avoid dpkg-source
complaining that it patched files multiple times.
-- Nathan Pratta Teodosio Fri, 10 Jun 2022
14:08:05 -0300
==> END <==
Build tested with Pbuilder.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978341/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
-6ubuntu2 is the version that will get to Jammy (22.04), 9ubuntu1 is the version currently in the devel series (future Kinetic, 22.10). In general it is preferable to use the version compiled for your current series, even though using the one in -devel might make sense in a testing context, as was the case here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa built with in openssl3 fails to connect to TLS 1.1 or lower server * Test case try to connect to a TLS <= 1.1 access point * Regression potential the patch lowers the security level in some situation for compatibility, it shouldn't prevent connecting to newer hardware, still try to connect to different type of wifi with different security levels --- those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1978007] Re: Please merge network-manager-applet 1.28.0-1 from Debian unstable
Thanks! ** Changed in: network-manager-applet (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1978007 Title: Please merge network-manager-applet 1.28.0-1 from Debian unstable Status in network-manager-applet package in Ubuntu: Fix Committed Bug description: This is a proposed merge for network-manager-applet 1.28.0-1. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium * Merge with Debian. Remaining changes: - d/control, d/rules: + Run dh_translations. - d/control: + Replace gnome-icon-theme by humanity-icon-theme in Recommends. Both provide gnome-lockscreen's icon, but the latter is installed by default in Ubuntu. - d/patches: + Force-online-state-with-unmanaged-devices.patch + Have-the-appindicator-enabled-by-default.patch + lp341684_device_sensitive_disconnect_notify.patch + lp460144_correctly_update_notification.patch + Make-policykit-restricted-actions-insensitive.patch + Support-hiding-rather-than-desensitizing-disallowed-items.patch * Drop patches applied upstream: - git_owe_activation.patch - gitlab_new_meson.patch * Drop , since the packages are now also available in s390x. -- Nathan Pratta Teodosio Fri, 10 Jun 2022 13:54:36 -0300 ==>END<== I tested it with Pbuilder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978007/+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 1969574] Re: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace
** Information type changed from Public to Public Security -- 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/1969574 Title: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Released Bug description: I have 3 apps open in 1 workspace, When i press window key and i want to select app 2 or 3 with mouse, app 1 shows up! I can only go to app 2 with [window + tab] or [alt + tab] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:05:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-25 (145 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-16 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969574/+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 1978341] Re: Merge for xdg-desktop-portal 1.14.4 from Debian unstable
The webextensions-portal patch was generated from the upstream PR by
appending ".patch" to the URL (https://github.com/flatpak/xdg-desktop-
portal/pull/705.patch). Since the PR contains multiple commits, the
patch retains the split by commits, which explains why files are patched
multiple times. This shouldn't be a problem for dpkg-source though, the
warning shouldn't prevent building the package, and maintenance will be
easier if we keep the patch closer to the upstream PR.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1978341
Title:
Merge for xdg-desktop-portal 1.14.4 from Debian unstable
Status in xdg-desktop-portal package in Ubuntu:
Confirmed
Bug description:
This is a merge request for 1.14.4.
==> debian/changelog <==
xdg-desktop-portal (1.14.4-1ubuntu1) UNRELEASED; urgency=medium
* Merge from Debian. Remaining changes:
- debian/patches/{01..11}webextensions-portal.patch
* Single patch file was split into multiple files to avoid dpkg-source
complaining that it patched files multiple times.
-- Nathan Pratta Teodosio Fri, 10 Jun 2022
14:08:05 -0300
==> END <==
Build tested with Pbuilder.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978341/+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 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock
Fixes need to always land in the _next_ Ubuntu release first: 22.10 (kinetic) That fix is awaiting sponsorship here: http://reqorts.qa.ubuntu.com/reports/sponsoring/ When a sponsor starts working on it you will see the packages appear (even pre-release) at: https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1967121 Title: Dock auto-hides when a right click context menu is opened while a window is under the dock Status in Dash to dock: Fix Released Status in ubuntu-dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Triaged Bug description: [Impact] If the dock is set to auto-hide and a window is under the dock, then the dock hides prematurely when a menu is opened from one of its icons. This only seems to happen with GNOME 42. [Test Plan] 1. Set the dock to auto hide. 2. Move a window under the dock's position so that it wants to auto-hide. 3. Open the dock and right click on one of the icons to open a menu. Expected: Dock stays open while the menu is open. Observed: Dock closes while the menu is open. [Where problems could occur] This fix may affect any scenarios relating to the dock auto-hiding. [Other Info] Upstream fixes: ubuntu-dock: https://github.com/micheleg/dash-to-dock/pull/1739 dash-to-dock: https://github.com/micheleg/dash-to-dock/pull/1751 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Just add MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment and then reboot. If that doesn't fix your problem then please open a new bug. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+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 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock
The fix looks awesome. Thanks Daniel. Out of curiosity, I was wondering about why this issue is still in triagged on the jammy-updates milestone. Does it require approval from an external peer now that the 22.04 is out? I am asking this as I am trying to learn about release cycles of packages in the Ubuntu ecosystem. Also is there some sort of CI where we can see the built package from launchpad? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1967121 Title: Dock auto-hides when a right click context menu is opened while a window is under the dock Status in Dash to dock: Fix Released Status in ubuntu-dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Triaged Bug description: [Impact] If the dock is set to auto-hide and a window is under the dock, then the dock hides prematurely when a menu is opened from one of its icons. This only seems to happen with GNOME 42. [Test Plan] 1. Set the dock to auto hide. 2. Move a window under the dock's position so that it wants to auto-hide. 3. Open the dock and right click on one of the icons to open a menu. Expected: Dock stays open while the menu is open. Observed: Dock closes while the menu is open. [Where problems could occur] This fix may affect any scenarios relating to the dock auto-hiding. [Other Info] Upstream fixes: ubuntu-dock: https://github.com/micheleg/dash-to-dock/pull/1739 dash-to-dock: https://github.com/micheleg/dash-to-dock/pull/1751 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+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 1925468] Re: stack-buffer-overflow of import.c in function _import_bin
was solved in 0.99.beta20-1
** Changed in: libcaca (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1925468
Title:
stack-buffer-overflow of import.c in function _import_bin
Status in libcaca:
Fix Released
Status in libcaca package in Ubuntu:
Fix Released
Bug description:
Hello ubuntu security team
issues：https://github.com/cacalabs/libcaca/issues/56
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or
$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g
-fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link
-fsanitize-coverage=bb"
$ make
3.Create the poc_bin.cc && build
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
void crash(const uint8_t *Data, size_t Size) {
if(Size<8) return ;
size_t len=0;
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
caca_create_frame(cv,0);
caca_set_frame(cv,0);
caca_import_canvas_from_memory(cv,Data,Size,"bin");
caca_free_canvas(cv);
cv=NULL;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x0a,0x20,0x0a,0x0a,0x20,0x20,0x20,0x20,0x20,0x20,0x47,0x47,0x47};
len = sizeof(buffer)/sizeof(unsigned char);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
crash((const uint8_t*)buffer,len);
return 0;
}
4.compile poc_bin.cc
clang++ -g poc_bin.cc -O2 -fno-omit-frame-pointer -fsanitize=address
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_bin
5.Run poc_bin
asan info:
=
==3817476==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7ffe7cd3774d at pc 0x7f8c6314acfd bp 0x7ffe7cd376c0 sp 0x7ffe7cd376b8
READ of size 1 at 0x7ffe7cd3774d thread T0
#0 0x7f8c6314acfc in _import_bin
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33
#1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
#2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
#3 0x7f8c62ba00b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_bin+0x41c38d)
Address 0x7ffe7cd3774d is located in stack of thread T0 at offset 45 in frame
#0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
This frame has 1 object(s):
[32, 45) 'buffer' (line 31) <== Memory access at offset 45 overflows this
variable
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33 in _import_bin
Shadow bytes around the buggy address:
0x10004f99ee90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eeb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99eed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x10004f99eee0: 00 00 00 00 f1 f1 f1 f1 00[05]f3 f3 00 00 00 00
0x10004f99eef0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10004f99ef30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user:f7
Container overflow: fc
Array cookie:ac
Intra object redzone:bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone:cb
Shadow gap: cc
==3817476==ABORTING
Thanks
To manage notifications about this bug go to:
[Desktop-packages] [Bug 1925467] Re: stack-buffer-overflow of text.c in function _import_ansi
was solved in 0.99.beta20-1
** Changed in: libcaca (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1925467
Title:
stack-buffer-overflow of text.c in function _import_ansi
Status in libcaca:
Fix Released
Status in libcaca package in Ubuntu:
Fix Released
Bug description:
Hello ubuntu security team
issues: https://github.com/cacalabs/libcaca/issues/55
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1
libcaca version e4968ba
Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library
$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or
$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g
-fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link
-fsanitize-coverage=bb"
$ make
3.Create the poc_ansi.cc && build
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
void crash(const uint8_t *Data, size_t Size) {
if(Size<8) return ;
size_t len=0;
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
caca_create_frame(cv,0);
caca_set_frame(cv,0);
caca_import_canvas_from_memory(cv,Data,Size,"ansi");
caca_free_canvas(cv);
cv=NULL;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x20,0x4a,0x0c,0x0a,0x20,0x0a,0x20,0x0c,0xc,0xc};
len = sizeof(buffer)/sizeof(unsigned char);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
crash((const uint8_t*)buffer,len);
return 0;
}
4.compile poc_ansi.cc
clang++ -g poc_ansi.cc -O2 -fno-omit-frame-pointer -fsanitize=address
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_ansi
5.Run poc_ansi
asan info:
=
==3763372==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7ffda0164bea at pc 0x7f098d82c310 bp 0x7ffda01647b0 sp 0x7ffda01647a8
READ of size 1 at 0x7ffda0164bea thread T0
#0 0x7f098d82c30f in _import_ansi
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38
#1 0x4c6c72 in crash(unsigned char const*, unsigned long)
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
#2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
#3 0x7f098d2780b2 in __libc_start_main
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_mbay+0x41c38d)
Address 0x7ffda0164bea is located in stack of thread T0 at offset 42 in frame
#0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
This frame has 1 object(s):
[32, 42) 'buffer' (line 31) <== Memory access at offset 42 overflows this
variable
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38 in _import_ansi
Shadow bytes around the buggy address:
0x100034024920: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
0x100034024930: f8 f8 f8 f8 f8 f8 f8 f8 f8 f2 f2 f2 f2 f2 f2 f2
0x100034024940: f2 f2 f8 f2 f2 f2 f8 f3 f3 f3 f3 f3 00 00 00 00
0x100034024950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100034024960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x100034024970: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00[02]f3 f3
0x100034024980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100034024990: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000340249c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user:f7
Container overflow: fc
Array cookie:ac
Intra object redzone:bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone:cb
Shadow gap: cc
==3763372==ABORTING
Thanks
To manage notifications about this bug go to:
[Desktop-packages] [Bug 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04
Having the revision in the path doesn't seem optimal indeed and it should probably rather use the 'current' variant -- 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/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
** Attachment added: "gnome" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5596972/+files/gnome -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+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 1971089] Re: Network Manager bug constant reconnecting and CPU usage
reassigning to miredo then since it seems to be an issue due to this component ** Package changed: network-manager (Ubuntu) => miredo (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971089 Title: Network Manager bug constant reconnecting and CPU usage Status in miredo package in Ubuntu: Confirmed Bug description: Anyconnectin result cpu heavy usage. constant reconnections wifi/ethernet..no matter ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun May 1 17:00:00 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-06-03 (1793 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.148 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to jammy on 2022-04-25 (6 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/miredo/+bug/1971089/+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 1978400] Re: GNOME Network Displays does not work with error Authorization supplicant timed out
Thank you for your bug report. wpa 2.10, which is the version included in the current Ubuntu serie, has been released in january where the patch you reference is from 2020, so yes it is included. Could you perhaps report the issue on gnome-n-d gitlab? ** Changed in: wpa (Ubuntu) Importance: Undecided => Low ** Changed in: wpa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1978400 Title: GNOME Network Displays does not work with error Authorization supplicant timed out Status in wpa package in Ubuntu: Incomplete Bug description: I have a problem with connecting to a Miracast device via GNOME Network Displays package (https://gitlab.gnome.org/GNOME/gnome-network-displays) on Ubuntu. It sees the device normally (I see the device name in "Available Video Sinks" list), but when I'm trying to connect, after some time I've got the connection failed with the error: ``` p2p-dev-wlp0s20f3: Authorization supplicant timed out ``` Other systems (Android, Windows, MacOS) connects to it successfully. In the https://gitlab.gnome.org/GNOME/gnome-network-displays it's described that wpa_supplicant requires the patch: https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benja...@sipsolutions.net/ Maybe just adding this one-line patch could resolve this issue? Or it is already applied? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jun 12 09:56:19 2022 InstallationDate: Installed on 2022-04-14 (58 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: wpa UpgradeStatus: Upgraded to jammy on 2022-04-14 (58 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1978400/+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 1864215] Re: Please add webp loader to gdk-pixbuf
No it's not fixed, the upstream gdk-pixbuf task got closed because they don't want to accept new loaders in source so it needs to be fixed in another component. We should probably push to integrate it as a new package at some point but there hasn't been high demand for it so far and it's not frequent to find webp images yet which means it's still a low priority item. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1864215 Title: Please add webp loader to gdk-pixbuf Status in gdk-pixbuf: Fix Released Status in gdk-pixbuf package in Ubuntu: Confirmed Status in gdk-pixbuf package in Baltix: Triaged Status in Debian: New Bug description: Attempting to load a webp image -- for instance, https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp or https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file format" error. Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in libwebp, but isn't this really a gdk-pixbuf issue? If it really does belong to libwebp, my apologies, please dup this bug to 1407644 (I'm confident it doesn't belong to eog since I don't use that program; I have other programs that use libgdk-pixbuf). You can probably use eog to test this, or run /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i webp (I assume the loader would mention webp if there was a loader for it). I have these packages installed in addition to libgdk-pixbuf2.0-0: libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes the format: $ file /tmp/FKK78W.jpg.webp /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 1200x533, Scaling: [none]x[none], YUV color, decoders should clamp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 Date: Fri Feb 21 08:48:36 2020 InstallationDate: Installed on 2019-10-10 (133 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1864215/+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 1972034] Re: On browser download/save dialog, filename in name box is highlighted as if it is active, but typing doesn't edit name unless you click into the box
gnome-text-editor != gedit, could you try the first one? they use different versions of GTK and it would help figuring out if the issue is with the newer GTK -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1972034 Title: On browser download/save dialog, filename in name box is highlighted as if it is active, but typing doesn't edit name unless you click into the box Status in nautilus package in Ubuntu: Incomplete Bug description: This has bugged me for many years now, and figure as long as the kinks are being worked out on this bug: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1971516 I should bring it up: When you download a file from a browser, the save dialog pops up, and the filename in the name box at the top is highlighted (just the name, not the extension), which is the universal symbol for "I'm highlighted, start typing and you'll overwrite me!" However, typing does nothing unless you click the box, at which point the cursor is in the middle of the name, and you have re-highlight if you want to rename the file. This is still confusing to me after many years. Expected behaviour: Either: Filename is highlighted and you can start typing to replace the name (but not the extension) Or: Filname is NOT highlighted by default, indicating you are not ready to edit. Since Ubuntu 20.04... possibly longer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1972034/+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 1974054] Re: Without a reason gnome-shell CPU usage gets high
That's bug 1965563... But yes you can just run: gsettings set org.gnome.shell disabled-extensions "['ubuntu- appindicat...@ubuntu.com']" or a list of extensions like: gsettings set org.gnome.shell disabled-extensions "['ubuntu- appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']" where the names are from /usr/share/gnome-shell/extensions/ -- 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/1974054 Title: Without a reason gnome-shell CPU usage gets high Status in gnome-shell package in Ubuntu: Incomplete Bug description: Without a reason, CPU usage for gnome-shell jumps from 4% to 22%. All I did this normal workflow, locking/unlocking multiple times over few hours and couple of suspends. The screenshot is showing 37% because of the screenshot tool, but idling at 22%. And if I re-logged or reboot, it idles at 4% normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 17:24:38 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-02-03 (103 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1978429] Re: Crashes when smart info is open while the drive is pulled
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Incomplete ** Changed in: gnome-disk-utility (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1978429 Title: Crashes when smart info is open while the drive is pulled Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: 1. Open smart data for a given drive (not the boot drive, *points at step 2*) 2. detach drive from system (sata drives support hot swap) 3. wait a few seconds 4. disk utility has crashed if smart info is not open it will not crash and the drive drops out of the drive list the smart data window should either close or remain open and stop updating if the drive is removed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 42.0-1ubuntu1 Uname: Linux 5.17.13-051713-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Jun 12 22:42:11 2022 InstallationDate: Installed on 2021-11-26 (198 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211126) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1978429/+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 1974054] Re: Without a reason gnome-shell CPU usage gets high
Is there a way to run the extensions app on Wayland or must switch to Xorg? $ gnome-extensions-app Gdk-Message: 09:49:57.059: Error flushing display: Protocol error $ extension-manager Gdk-Message: 09:50:09.674: Error 71 (Protocol error) dispatching to Wayland display. -- 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/1974054 Title: Without a reason gnome-shell CPU usage gets high Status in gnome-shell package in Ubuntu: Incomplete Bug description: Without a reason, CPU usage for gnome-shell jumps from 4% to 22%. All I did this normal workflow, locking/unlocking multiple times over few hours and couple of suspends. The screenshot is showing 37% because of the screenshot tool, but idling at 22%. And if I re-logged or reboot, it idles at 4% normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 17:24:38 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-02-03 (103 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1974054] Re: Without a reason gnome-shell CPU usage gets high
Thanks. The last messages in that log from ubuntu-appindicators may be related as it has caused bugs like this before. Please: 1. sudo apt install gnome-shell-extension-prefs 2. Open the Extensions app 3. Disable Ubuntu AppIndicators 4. Log in again If that doesn't solve it then maybe also try disabling the other extensions in the same way. -- 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/1974054 Title: Without a reason gnome-shell CPU usage gets high Status in gnome-shell package in Ubuntu: Incomplete Bug description: Without a reason, CPU usage for gnome-shell jumps from 4% to 22%. All I did this normal workflow, locking/unlocking multiple times over few hours and couple of suspends. The screenshot is showing 37% because of the screenshot tool, but idling at 22%. And if I re-logged or reboot, it idles at 4% normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 17:24:38 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-02-03 (103 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1974054] Re: Without a reason gnome-shell CPU usage gets high
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+attachment/5596959/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1974054 Title: Without a reason gnome-shell CPU usage gets high Status in gnome-shell package in Ubuntu: Incomplete Bug description: Without a reason, CPU usage for gnome-shell jumps from 4% to 22%. All I did this normal workflow, locking/unlocking multiple times over few hours and couple of suspends. The screenshot is showing 37% because of the screenshot tool, but idling at 22%. And if I re-logged or reboot, it idles at 4% normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 17:24:38 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-02-03 (103 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1975872] Re: [ASUS GL552VW] Loss of signal (black screen) on external monitor
** Tags added: bandwidth -- 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/1975872 Title: [ASUS GL552VW] Loss of signal (black screen) on external monitor Status in mutter package in Ubuntu: Incomplete Bug description: External screen flickers on and off (image is present and then signal is lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh installation. Details: - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make that HDMI work with NVIDIA GTX 960M in my laptop). - Nothing was installed after installing the OS - i connected to the Internet while installing the system and marked the option to download the updates. - I had that issue on Windows 10 - I fixed it by installing a latest Intel GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers installed by Windows - they were the latest Intel drivers. - Internal screen works fine. - If I mirror external and internal monitor, external isn't flickering, but internal monitor's resolution is lower that external's one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 26 22:34:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d] InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. GL552VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1975872/+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 1978401] Re: display turns suddenly off and then on again
A monitor going blank and then coming back almost always means that a stable signal (enough bandwidth) can't be maintained. You should start by trying to replace the DisplayPort cable, or at least re-plugging the one you have. If that doesn't solve it then to at least prove the theory please try using 1920x1080 for a little while. ** Tags added: bandwidth nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-510 (Ubuntu) ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Incomplete -- 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/1978401 Title: display turns suddenly off and then on again Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Bug description: Hi, Randomly the display turns off and then on again. Happens sometimes many times and others times not at all, randomly. Related to https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-495/+bug/1956252 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 12 09:45:00 2022 DistUpgraded: 2022-04-21 07:46:27,025 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] [10de:1e07] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU102 [GeForce RTX 2080 Ti Rev. A] [1458:37a9] InstallationDate: Installed on 2022-04-03 (69 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=7d72a26f-7e2e-4ed2-851b-4bedb4181f16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (52 days ago) dmi.bios.date: 01/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12l dmi.board.asset.tag: Default string dmi.board.name: Z390 AORUS PRO-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12l:bd01/19/2021:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSPRO-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z390 AORUS PRO dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1978401/+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 1978451] [NEW] The PPP daemon has died: A modem hung up the phone (exit code = 16) → LCP: timeout sending Config-Requests
Public bug reported: /etc/wvdial.conf: ===8<-- [Dialer Defaults] StupidMode = 1 Modem Type = Analog Modem Baud = 9600 New PPPD = yes Modem = /dev/ttyUSB0 ISDN = 0 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 +FCLASS=0 [Dialer Orange] Init3 = AT+CGDCONT=1,"IP","mworld.be",,0,0 Phone = *99# Mcc = 206 Mnc = 10 Username = '' Password = '' Carrier Check = off -->8=== execution: ===8<-- $ eject /dev/sr0 $ wvdial Orange --> WvDial: Internet dialer version 1.61 --> Initializing modem. --> Sending: ATZ OK --> Sending: ATQ0 V1 E1 S0=0 +FCLASS=0 ATQ0 V1 E1 S0=0 +FCLASS=0 OK --> Sending: AT+CGDCONT=1,"IP","mworld.be",,0,0 AT+CGDCONT=1,"IP","mworld.be",,0,0 OK --> Modem initialized. --> Sending: ATDT*99# --> Waiting for carrier. ATDT*99# CONNECT 360 --> Carrier detected. Waiting for prompt. --> Don't know what to do! Starting pppd and hoping for the best. --> Starting pppd at… --> Pid of pppd: 84797 --> Using interface ppp0 --> Disconnecting at… --> The PPP daemon has died: A modem hung up the phone (exit code = 16) --> man pppd explains pppd error codes in more detail. --> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information. --> Auto Reconnect will be attempted in 5 seconds -->8=== From the error codes list in “man pppd”: 16 The link was terminated by the modem hanging up. /var/log/messages: ===8<-- $timestamp $host pppd[84797]: pppd 2.4.9 started by $user, uid 0 $timestamp $host pppd[84797]: Using interface ppp0 $timestamp $host pppd[84797]: Connect: ppp0 <--> /dev/ttyUSB0 $timestamp $host pppd[84797]: LCP: timeout sending Config-Requests $timestamp $host pppd[84797]: Connection terminated. $timestamp $host pppd[84797]: Modem hangup $timestamp $host pppd[84797]: Exit. -->8=== The modem is a Huawei E220. I added “debug” to /etc/ppp/options but this failed to increase verbosity in /var/log/messages. When another machine connects to the same wireless broadband provider, CHAP is automatically negotiated and successfully used, FWIW. ** Affects: wvdial (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wvdial in Ubuntu. https://bugs.launchpad.net/bugs/1978451 Title: The PPP daemon has died: A modem hung up the phone (exit code = 16) → LCP: timeout sending Config-Requests Status in wvdial package in Ubuntu: New Bug description: /etc/wvdial.conf: ===8<-- [Dialer Defaults] StupidMode = 1 Modem Type = Analog Modem Baud = 9600 New PPPD = yes Modem = /dev/ttyUSB0 ISDN = 0 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 +FCLASS=0 [Dialer Orange] Init3 = AT+CGDCONT=1,"IP","mworld.be",,0,0 Phone = *99# Mcc = 206 Mnc = 10 Username = '' Password = '' Carrier Check = off -->8=== execution: ===8<-- $ eject /dev/sr0 $ wvdial Orange --> WvDial: Internet dialer version 1.61 --> Initializing modem. --> Sending: ATZ OK --> Sending: ATQ0 V1 E1 S0=0 +FCLASS=0 ATQ0 V1 E1 S0=0 +FCLASS=0 OK --> Sending: AT+CGDCONT=1,"IP","mworld.be",,0,0 AT+CGDCONT=1,"IP","mworld.be",,0,0 OK --> Modem initialized. --> Sending: ATDT*99# --> Waiting for carrier. ATDT*99# CONNECT 360 --> Carrier detected. Waiting for prompt. --> Don't know what to do! Starting pppd and hoping for the best. --> Starting pppd at… --> Pid of pppd: 84797 --> Using interface ppp0 --> Disconnecting at… --> The PPP daemon has died: A modem hung up the phone (exit code = 16) --> man pppd explains pppd error codes in more detail. --> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information. --> Auto Reconnect will be attempted in 5 seconds -->8=== From the error codes list in “man pppd”: 16 The link was terminated by the modem hanging up. /var/log/messages: ===8<-- $timestamp $host pppd[84797]: pppd 2.4.9 started by $user, uid 0 $timestamp $host pppd[84797]: Using interface ppp0 $timestamp $host pppd[84797]: Connect: ppp0 <--> /dev/ttyUSB0 $timestamp $host pppd[84797]: LCP: timeout sending Config-Requests $timestamp $host pppd[84797]: Connection terminated. $timestamp $host pppd[84797]: Modem hangup $timestamp $host pppd[84797]: Exit. -->8=== The modem is a Huawei E220. I added “debug” to /etc/ppp/options but this failed to increase verbosity in /var/log/messages. When another machine connects to the same wireless broadband provider, CHAP is automatically negotiated and successfully used, FWIW. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1978366] Re: unlocking screen hangs for 20-40sec before working
Thanks for the bug report. Please start by removing all custom extensions: cd ~/.local/share/gnome-shell rm -rf extensions and then log in again. Does the problem still occur? ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1978366 Title: unlocking screen hangs for 20-40sec before working Status in Ubuntu: Incomplete Bug description: Ever since installing (not upgrading) Ubuntu-22.04, I've noticed that quite often (but not always) unlocking the screensaver freezes the entire system. By that I mean I will tap my keyboard, the blank screen will lighten up and show the password field, I start typing, get the "***" characters, and then it freezes: typing doesn't continue, mouse stops moving. If I wait, 30-40 (ish) seconds later it will catch up and start responding again and I can continue. Quite often the freeze doesn't occur until I have entered my password and hit ENTER - but it does freeze earlier too. I have figured out that if this happens, I can speed up the process by hitting Ctrl-Alt-F3 to go to a tty, then immediately Alt-F2 to go back to gnome - and that flushes out the problem. Definitely shaves many seconds off waiting around for the fault to clear by itself. I was also talking to a collegue who installed Ubuntu-22.04 this week - he's noticed the same issue. Also a Dell laptop - but different model. I would guess Wayland related - but don't have any evidence for that, so I put this as gnome-shell Thanks! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:02:34 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-13 (89 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1978366/+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 1978331] Re: DING shows several errors when no monitor is attached
The first MR is in version 45 and the second is in version 46. So fix released to kinetic in both cases. ** Tags added: fixed-in-46 fixed-upstream ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Assignee: (unassigned) => Sergio Costas (rastersoft-gmail) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1978331 Title: DING shows several errors when no monitor is attached Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Bug description: Recent version of gnome shell or extension has been emitting large numbers of identical, or quote similar, entries in the system journal, when the monitor is turned off or physically disconnected. The error is: DING: (gjs:10210): Gdk-CRITICAL **: 09:58:45.854: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1978331/+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 1978349] Re: Monitors sometimes permanently blanked after resume
In case there's more than just that amdgpu kernel crash happening please also run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - Monitors sometimes permanently blanked after resume + [amdgpu] Monitors sometimes permanently blanked after resume -- 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/1978349 Title: [amdgpu] Monitors sometimes permanently blanked after resume Status in linux package in Ubuntu: Incomplete Bug description: Sometimes monitors don't wake up after resume. Happened couple times with Ubuntu 22.04 so far. Journalctl lists only one instance of this, might have failed to save the logs on other times. kernel BUG at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:10039! 1. (assumedly) occurs when resuming from ram 2. suspend chosen from ui 3. resume by clicking key on keyboard 4.-11. not tested yet with mainline builds, since uncertain about how to reproduce reliably. 12. openssh-server only installed after today's instance, so don't have much debug data beyond what was saved in logs before sysrq-sub. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 23:02:04 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: 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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 4966 F pulseaudio /dev/snd/controlC1: iheino 4966 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A
[Desktop-packages] [Bug 1978330] Re: Extension does odd things when other extension is disabled
Fix released to kinetic already: https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/46-1 ** Tags added: fixed-in-46 fixed-upstream ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1978330 Title: Extension does odd things when other extension is disabled Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Bug description: When an extension that was enabled before DING is disabled, the desktop with the icons stops behaving like a desktop, and instead they behave like a transparent window that can be over other windows, be moved by pressing the "Windows" key, and so on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1978330/+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 1975872] Re: [ASUS GL552VW] Loss of signal (black screen) on external monitor
Please also follow the instructions in comment #10, remembering to log into 'Ubuntu on Xorg' first. I'm hoping that will allow you to maintain a stable 1920x1080 60Hz signal. -- 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/1975872 Title: [ASUS GL552VW] Loss of signal (black screen) on external monitor Status in mutter package in Ubuntu: Incomplete Bug description: External screen flickers on and off (image is present and then signal is lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh installation. Details: - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make that HDMI work with NVIDIA GTX 960M in my laptop). - Nothing was installed after installing the OS - i connected to the Internet while installing the system and marked the option to download the updates. - I had that issue on Windows 10 - I fixed it by installing a latest Intel GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers installed by Windows - they were the latest Intel drivers. - Internal screen works fine. - If I mirror external and internal monitor, external isn't flickering, but internal monitor's resolution is lower that external's one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 26 22:34:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d] InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. GL552VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1975872/+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 1975872] Re: [ASUS GL552VW] Loss of signal (black screen) on external monitor
Or even try: xrandr --output HDMI-2 --set "max bpc" 6 -- 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/1975872 Title: [ASUS GL552VW] Loss of signal (black screen) on external monitor Status in mutter package in Ubuntu: Incomplete Bug description: External screen flickers on and off (image is present and then signal is lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh installation. Details: - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make that HDMI work with NVIDIA GTX 960M in my laptop). - Nothing was installed after installing the OS - i connected to the Internet while installing the system and marked the option to download the updates. - I had that issue on Windows 10 - I fixed it by installing a latest Intel GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers installed by Windows - they were the latest Intel drivers. - Internal screen works fine. - If I mirror external and internal monitor, external isn't flickering, but internal monitor's resolution is lower that external's one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 26 22:34:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d] InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. GL552VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1975872/+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 580437] Re: wvdial returns with Huawei E160E error NO CARRIER
Your config does not contain: Carrier Check = off You probably need to add that line. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wvdial in Ubuntu. https://bugs.launchpad.net/bugs/580437 Title: wvdial returns with Huawei E160E error NO CARRIER Status in wvdial package in Ubuntu: Confirmed Bug description: Binary package hint: wvdial This error is not limited to wvdial, network-manager cannot either connect with similar errors. Wvdial however seems to give better logging information, so I'll attach log with hopefully relevant information. I have access to a Windows machine where the device works, so it is possible to connect with it. I have a Huawei E160E from Finnish provider Saunalahti. All the AT commands seems to go through, but when trying to connect wvdial returns NO CARRIER, and tries to connect again, never succeeding. I have tried using both /dev/ttyUSB0 and /dev/ttyUSB1 both giving the same errors. The wvdial.conf has been received from http://linux.fi/index.php/Wvdial#Saunalahti in to which I've added some debugging AT commands. [Dialer defaults] Modem = /dev/ttyUSB0 Init1 = ATZ Init2 = ATI Init3 = AT+GMR Init4 = AT+CSQ Init5 = AT^SYSINFO Init6 = AT+COPS? Init7 = AT+CGREG? Init8 = AT+CGDCONT=1,"IP","internet.saunalahti" Phone = *99***1# Stupid Mode = 1 Username = " " Password = " " ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: wvdial 1.60.3 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Fri May 14 13:15:24 2010 ProcEnviron: SHELL=/bin/zsh PATH=(custom, user) LANG=en_US.utf8 SourcePackage: wvdial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wvdial/+bug/580437/+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 1974054] Re: Without a reason gnome-shell CPU usage gets high
Next time the high CPU of gnome-shell occurs, please run: journalctl -b0 > journal.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1974054 Title: Without a reason gnome-shell CPU usage gets high Status in gnome-shell package in Ubuntu: Incomplete Bug description: Without a reason, CPU usage for gnome-shell jumps from 4% to 22%. All I did this normal workflow, locking/unlocking multiple times over few hours and couple of suspends. The screenshot is showing 37% because of the screenshot tool, but idling at 22%. And if I re-logged or reboot, it idles at 4% normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 17:24:38 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-02-03 (103 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
Yes crashes in libgbm.so.1.0.0 are likely to be this bug. But we should create new bugs for each crash to confirm what they really are. Please run: ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash or if that doesn't work then try: apport-cli /var/crash/_usr_bin_gnome-shell.1000.crash -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+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 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
This bug is fixed already in 42.1. If you still have problems then
please open a new bug by running:
ubuntu-bug gnome-shell
and we can work from there.
--
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/1967274
Title:
Screen sometimes can't update [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in mutter source package in Jammy:
Fix Released
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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
