[Desktop-packages] [Bug 2040273] Re: [SRU] Enable support for Caracal Cloud Archive
This bug was fixed in the package software-properties - 0.99.40 --- software-properties (0.99.40) noble; urgency=medium * cloudarchive: Enable support for the Caracal Ubuntu Cloud Archive on 22.04 (LP: #2040273). -- Corey Bryant Tue, 24 Oct 2023 08:20:52 -0400 ** Changed in: software-properties (Ubuntu Noble) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2040273 Title: [SRU] Enable support for Caracal Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Triaged Status in software-properties source package in Noble: Fix Released Bug description: Please add support for: cloud-archive:caracal cloud-archive:caracal-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the caracal cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:caracal sudo add-apt-repository cloud-archive:caracal-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2040273/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]
** Changed in: gnome-shell Status: Unknown => New -- 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/2040453 Title: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”] Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: New Bug description: Hello, Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer possible to restart gnome-shell without crashing the session. The only way not to crash it is to close all applications before restarting gnome-shell. I have verified this too. This has already been reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 a tentative patch for mutter proposed: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598 Please consider reviewing/testing this patch and pushing an update so people can restart gnome-shell session without crashing it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2040453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]
yeah, I haven't necessarily reported every crash I've experienced in launchpad as I've been restarting gnome-shell quite a bit when updating my extensions to gnome45 and couldn't be sure whether the crash was caused by the extension or gnome-shell itself. This crash on the other hand stayed when I upgraded on bare metal and was also reported by a number of people contributing to gnome-extensions which is why I felt it was worth investigating. I have seen extensions commenting on this in their ReadMe and I'm yet to find someone who isn't experiencing a crash when restarting gnome-shell on X11. -- 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/2040453 Title: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Hello, Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer possible to restart gnome-shell without crashing the session. The only way not to crash it is to close all applications before restarting gnome-shell. I have verified this too. This has already been reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 a tentative patch for mutter proposed: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598 Please consider reviewing/testing this patch and pushing an update so people can restart gnome-shell session without crashing it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2040453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040453] Re: Gnome 45 crash on restart in X11 session
OK let's link this to https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/7050 https://errors.ubuntu.com/oops/0b660737-7287-11ee-9b14-fa163ec44ecd sounds similar to bug 2039340, which is similar to a bunch of crashes in getenv that are probably all the same bug. ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Summary changed: - Gnome 45 crash on restart in X11 session + Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”] -- 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/2040453 Title: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Hello, Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer possible to restart gnome-shell without crashing the session. The only way not to crash it is to close all applications before restarting gnome-shell. I have verified this too. This has already been reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 a tentative patch for mutter proposed: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598 Please consider reviewing/testing this patch and pushing an update so people can restart gnome-shell session without crashing it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2040453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040453] Re: Gnome 45 crash on restart in X11 session
thanks for following up. I have attached my journal.txt and you will find the same error in at as in the gnome-shell gitlab bug `Window manager error: Another compositing manager is already running on screen 0 on display “:0”`. Also, the same behaviour occurs as if I close all windows before restarting, it doesn't crash which is what made me think that they are related. I also only started noticing this when I started to test 23.10 in gnome-boxes prior to the release (I frequently do gnome-shell restarts as I contribute to extensions) and noticed this behaviour right away as I never had the issue with 23.04. As soon as I upgraded my machine, the restarts started to crash (which makes testing extensions quite tedious). note that I cleared up the journal before running this test. I also cleared up my crash logs to see but it's not generating any report. There are a number of gnome-shell crashes linked to my woopside-id, including the following: https://errors.ubuntu.com/oops/0b660737-7287-11ee-9b14-fa163ec44ecd https://errors.ubuntu.com/oops/14ef2be8-195c-11ee-b183-fa163e55efd0 https://errors.ubuntu.com/oops/1a4daae8-0925-11ee-bcf5-fa163ef35206 I am not sure the above reports are directly connected to this issue but based on the fact that many people seem to be having the same issue since gnome45 is out, this doesn't look like an isolated issue. See this discussion on github for instance: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/7050 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7050 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 ** Attachment added: "journalctl output" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040453/+attachment/5713272/+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/2040453 Title: Gnome 45 crash on restart in X11 session Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer possible to restart gnome-shell without crashing the session. The only way not to crash it is to close all applications before restarting gnome-shell. I have verified this too. This has already been reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 a tentative patch for mutter proposed: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598 Please consider reviewing/testing this patch and pushing an update so people can restart gnome-shell session without crashing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040453] Re: Gnome 45 crash on restart in X11 session
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7050 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 -- 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/2040453 Title: Gnome 45 crash on restart in X11 session Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer possible to restart gnome-shell without crashing the session. The only way not to crash it is to close all applications before restarting gnome-shell. I have verified this too. This has already been reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 a tentative patch for mutter proposed: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598 Please consider reviewing/testing this patch and pushing an update so people can restart gnome-shell session without crashing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040615] Re: Xorg freeze
It looks like there are recurring problems coming from the Nvidia kernel driver here, but let's start with this: 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. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. 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. 3. If step 2 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. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2040615 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: the screen regularly freezes sometime when using some application and also sometime when doing nothing i have tried reisub command but it has no effect ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-87.97~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-87-generic x86_64 .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 Open Kernel Module for x86_64 535.104.12 Release Build (dvs-builder@U16-I3-A14-4-4) Wed Sep 20 09:32:00 UTC 2023 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2) ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 23:55:09 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Today GraphicsCard: Intel Corporation Device [8086:9ba4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:170d] NVIDIA Corporation Device [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:170d] InstallationDate: Installed on 2023-10-25 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 322e:202c Sonix Technology Co., Ltd. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 30fa:0400 USB OPTICAL MOUSE Bus 001 Device 004: ID 13d3:3563 IMC Networks Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LHB_FX506LHB ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-87-generic root=UUID=3ee592ff-12a3-43bf-8dba-b143740cba7e ro quiet splash acpi=force vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX506LHB.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX506LHB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX506LHB.311:bd02/09/2022:br5.17:efr3.5:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LHB_FX506LHB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LHB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX506LHB_FX506LHB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri
[Desktop-packages] [Bug 2040615] Re: Xorg freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2040615 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: the screen regularly freezes sometime when using some application and also sometime when doing nothing i have tried reisub command but it has no effect ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-87.97~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-87-generic x86_64 .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 Open Kernel Module for x86_64 535.104.12 Release Build (dvs-builder@U16-I3-A14-4-4) Wed Sep 20 09:32:00 UTC 2023 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2) ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 23:55:09 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Today GraphicsCard: Intel Corporation Device [8086:9ba4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:170d] NVIDIA Corporation Device [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:170d] InstallationDate: Installed on 2023-10-25 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 322e:202c Sonix Technology Co., Ltd. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 30fa:0400 USB OPTICAL MOUSE Bus 001 Device 004: ID 13d3:3563 IMC Networks Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LHB_FX506LHB ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-87-generic root=UUID=3ee592ff-12a3-43bf-8dba-b143740cba7e ro quiet splash acpi=force vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX506LHB.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX506LHB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX506LHB.311:bd02/09/2022:br5.17:efr3.5:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LHB_FX506LHB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LHB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX506LHB_FX506LHB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 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~20.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2040615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040615] [NEW] Xorg freeze
You have been subscribed to a public bug: the screen regularly freezes sometime when using some application and also sometime when doing nothing i have tried reisub command but it has no effect ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-87.97~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-87-generic x86_64 .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 Open Kernel Module for x86_64 535.104.12 Release Build (dvs-builder@U16-I3-A14-4-4) Wed Sep 20 09:32:00 UTC 2023 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2) ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 23:55:09 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Today GraphicsCard: Intel Corporation Device [8086:9ba4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:170d] NVIDIA Corporation Device [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:170d] InstallationDate: Installed on 2023-10-25 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 322e:202c Sonix Technology Co., Ltd. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 30fa:0400 USB OPTICAL MOUSE Bus 001 Device 004: ID 13d3:3563 IMC Networks Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LHB_FX506LHB ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-87-generic root=UUID=3ee592ff-12a3-43bf-8dba-b143740cba7e ro quiet splash acpi=force vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX506LHB.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX506LHB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX506LHB.311:bd02/09/2022:br5.17:efr3.5:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LHB_FX506LHB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LHB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX506LHB_FX506LHB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 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~20.04.8 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/2040615 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 2039374] Re: xbrlapi causes long delay in GUI login
> if there is an active IPv6 regular (non-loopback) interface with an IPv6 address and network connection, then connection attempts to ::1 seem to hang and timeout Probably it uses the default route to send packets to ::1, which is deemed not to receive any response. > I haven't seen any other daemons with issues from this. Maybe they are using IPv4 for loopback? Probably ** Description changed: - Ubuntu 22.04.3 LTS + Ubuntu 22.04.3 LTS xbrlapi 6.4-4ubuntu3 After logging in to the GUI, there is a delay of over 2 minutes before the desktop environment loads (screen will be black with a mouse cursor) This is caused by /etc/X11/Xsession.d/90xbrlapi The script runs xbrlapi, which hangs for 2 minutes or so, presumably because it is trying to connect to a BrlAPI server that doesn't exist on my machine. I guess this packages was installed by orca, because I did not directly install it myself and I don't need it. Did not happen before 22.04 Others have this issue: https://askubuntu.com/questions/1448501/ubuntu-22-04-1-lts-very-long-x-session-login-due-to-90xbrlapi -- 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/2039374 Title: xbrlapi causes long delay in GUI login Status in brltty package in Ubuntu: New Bug description: Ubuntu 22.04.3 LTS xbrlapi 6.4-4ubuntu3 After logging in to the GUI, there is a delay of over 2 minutes before the desktop environment loads (screen will be black with a mouse cursor) This is caused by /etc/X11/Xsession.d/90xbrlapi The script runs xbrlapi, which hangs for 2 minutes or so, presumably because it is trying to connect to a BrlAPI server that doesn't exist on my machine. I guess this packages was installed by orca, because I did not directly install it myself and I don't need it. Did not happen before 22.04 Others have this issue: https://askubuntu.com/questions/1448501/ubuntu-22-04-1-lts-very-long-x-session-login-due-to-90xbrlapi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/2039374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036597] Re: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos))
Dropping an update here, [same as I did on Stack Exchange](https://askubuntu.com/a/1490412/1105829): I bumped into the same issue, and I was lucky enough to remember that the only change I made to my system today was to install [okular](https://github.com/KDE/okular). The fix above works fine, as long as I don't open okular. If I do, and then reboot, I am back to square one. Note that another user is suggesting that [adding hidden files to the folders prevents this from happening](https://askubuntu.com/questions/1488100/okular-breaking-home- directories-links). I cannot find any mention of this bug in the KDE bug tracker, so maybe I'll try to add a new one in the coming days. I hope this helps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/2036597 Title: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos)) Status in xdg-user-dirs package in Ubuntu: Incomplete Bug description: Can't enter these folders. This is on an almost fresh install of Mantic. martin@ThinkPad-P14s-Gen-3:~$ cd Music bash: cd: Music: Too many levels of symbolic links martin@ThinkPad-P14s-Gen-3:~$ ls -l total 2988 drwxrwxr-x 3 martin martin4096 Sep 18 12:44 bin drwxr-xr-x 2 martin martin4096 Sep 19 13:48 Desktop drwxr-xr-x 19 martin martin4096 Sep 18 12:42 Documents drwxr-xr-x 4 martin martin4096 Sep 19 13:48 Downloads drwx-- 5 martin martin4096 Sep 18 16:24 Dropbox lrwxrwxrwx 1 martin martin 18 Sep 19 13:56 Music -> /home/martin/Music lrwxrwxrwx 1 martin martin 21 Sep 19 13:56 Pictures -> /home/martin/Pictures lrwxrwxrwx 1 martin martin 19 Sep 19 13:56 Public -> /home/martin/Public drwxrwxr-x 3 martin martin4096 Sep 18 16:25 R -rw--- 1 martin martin 3029503 Sep 19 14:08 references.bib drwx-- 13 martin martin4096 Sep 19 13:56 snap lrwxrwxrwx 1 martin martin 22 Sep 19 13:56 Templates -> /home/martin/Templates lrwxrwxrwx 1 martin martin 19 Sep 19 13:56 Videos -> /home/martin/Videos ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 14:19:32 2023 InstallationDate: Installed on 2023-09-18 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/2036597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 87ubuntu2 --- gnome-shell-extension-ubuntu-dock (87ubuntu2) mantic; urgency=medium [ Marco Trevisan (Treviño) ] * locationsWorker: Exit with the main script exit code (LP: #2038783) [ Stuart Hayhurst ] * appIcons: Use Mtk.Rectangle instead of Meta.Rectangle (LP: #2034664) -- Marco Trevisan (Treviño) Mon, 09 Oct 2023 03:04:54 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Fix Committed => Fix Released -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
This bug was fixed in the package ubuntu-release-upgrader - 1:23.10.11 --- ubuntu-release-upgrader (1:23.10.11) mantic; urgency=medium * do-release-upgrade: pass XDG_CURRENT_DESKTOP env var (LP: #2034986) * tests: use di.stable() instead of di.devel() * Run pre-build.sh: updating po files, mirrors, and demotions. -- Nick Rosbrook Thu, 12 Oct 2023 10:46:33 -0400 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038783] Re: Exit code of locations mount script is not respecting error
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 87ubuntu2 --- gnome-shell-extension-ubuntu-dock (87ubuntu2) mantic; urgency=medium [ Marco Trevisan (Treviño) ] * locationsWorker: Exit with the main script exit code (LP: #2038783) [ Stuart Hayhurst ] * appIcons: Use Mtk.Rectangle instead of Meta.Rectangle (LP: #2034664) -- Marco Trevisan (Treviño) Mon, 09 Oct 2023 03:04:54 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Fix Committed => Fix Released -- 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/2038783 Title: Exit code of locations mount script is not respecting error Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js /foo/bar/baz echo $? An error should be shown and the return code should be 15 Doing instead gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js $HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2038783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038907] Re: Ubuntu patch incorrect disable the thunderbolt and security panels
This bug was fixed in the package gnome-control-center - 1:45.0-1ubuntu3 --- gnome-control-center (1:45.0-1ubuntu3) mantic; urgency=medium * d/p/u/Disable-non-working-camera-microphones-panels.patch: - fix the patch to not disable the entire privacy->devices section and restore access to the thunderbolt and security panels (lp: #2038907) -- Sebastien Bacher Tue, 10 Oct 2023 11:50:37 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038907 Title: Ubuntu patch incorrect disable the thunderbolt and security panels Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Mantic: Fix Committed Bug description: * Impact After an upstream reorganisation the patch to disable the microcophone/camera panels incorrectly disable also the rest of the device section, including thunderbolt and security which should be displayed * Testcase $ gnome-control-center privacy The right page should have a devices section listing thunderbolt (if the corresponding hardware is available) and security * Regression potential The change is a simple tweak to the .ui of the privacy panel, any bug would show in that panel. Also the thunderbolt and security panel haven't got recent testing due to this issue so they could be buggy (but it wouldn't be a regression over having the functionality not available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024680] Re: Dell XPS 9730 no sound, I have tried the 22.04 lts same issue
It's fixed in ubuntu 23.10, thanks to kernel 6.5 I guess. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2024680 Title: Dell XPS 9730 no sound, I have tried the 22.04 lts same issue Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've tried various fixes without success, I did manage to get the NVIDA HDMI in the sound options but I've never had the inbuilt Intel Media Hardware working for sound. 22.04 LTS had the same issue and I've upgraded to the new version 23.04 which looks good. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2245 F wireplumber /dev/snd/seq:daniel 2241 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 22 17:30:27 2023 InstallationDate: Installed on 2023-06-16 (5 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 067X4F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd03/23/2023:br1.2:efr1.1:svnDellInc.:pnXPS179730:pvr:rvnDellInc.:rn067X4F:rvrA00:cvnDellInc.:ct10:cvr:sku0BDB: dmi.product.family: XPS dmi.product.name: XPS 17 9730 dmi.product.sku: 0BDB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2024680/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use
Ubuntu 23.10 still has this problem. Without actually using the app I saw an RSS of 600MB on my AMD64 desktop, measured using `sudo smem -tk`. After a reboot (still without opening the app manually) I see a steady 300MB RSS. It's the heaviest app in use on my desktop after Firefox. While keeping Flatpaks and Snaps up-to-date is great, perhaps it could exit after having done that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1616332 Title: gnome-software using hundreds of MB of memory when not in use Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Triaged Bug description: It seems gnome-software is running in the background all the time. Not a big deal if it was lightweight, but it seems to use hundreds of MB (from smem output): PID User Command Swap USS PSS RSS 2291 jan /usr/bin/gnome-software --g 285436 112576 117982 134036 A total of over 400MB in RAM and swap combined. After killing and restarting, it takes "only" a bit over 100MB. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 24 09:45:53 2016 InstallationDate: Installed on 2012-11-10 (1382 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-software UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1616332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
All, thanks for pushing this through. To be clear, I agree with all the points that it would have been better if we could have included the extra tests, but I'm glad you agree with my analysis about the cost vs. benefit. I will find some time to test in the next few days. I can do the manual test from the test plan and also do a local build with the additional test cases by just cherry-picking the commit into a temporary branch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Fix Committed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who
[Desktop-packages] [Bug 2040657] [NEW] bluez does not detect Logitech Pebble M350, no option to connect
Public bug reported: I lost the proprietary USB dongle and decided I wanted to try bluetooth with this particular mouse. I am able to connect with bluetooth on Windows 11, but the device doesn't even show up in `bluetoothctl scan on`. This is seen on Jammy with bluez 5.64-0ubuntu1 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2040657 Title: bluez does not detect Logitech Pebble M350, no option to connect Status in bluez package in Ubuntu: New Bug description: I lost the proprietary USB dongle and decided I wanted to try bluetooth with this particular mouse. I am able to connect with bluetooth on Windows 11, but the device doesn't even show up in `bluetoothctl scan on`. This is seen on Jammy with bluez 5.64-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
** Changed in: gnome-shell
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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/gnome-shell/+bug/2038998/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
I understand that qpdf in Noble will auto-sync when Noble opens. ** Changed in: qpdf (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Fix Committed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has a rigorous test suite and an extremely good quality record. It processes
[Desktop-packages] [Bug 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
I have twice installed Linux Mint on an 2011 iMac. It is 21.5 inch with AMD Radeon HD 6750M 512 MB graphics and 2.5 GHz Intel Core i5. Every time I install Linux Mint, it boots correctly a couple times but then simply displays a totally blank screen when booted up. Once this happens, the system will not boot correctly again. Ubuntu works fine, why is Linux Mint broken? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train
[Desktop-packages] [Bug 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
I have twice installed Linux Mint on an 2011 iMac. It is 21.5 inch with AMD Radeon HD 6750M 512 MB graphics and 2.5 GHz Intel Core i5. Every time I install Linux Mint, it boots correctly a couple times but then simply displays a totally blank screen when booted up. Once this happens, the system will not boot correctly again. Ubuntu works fine, why is Linux Mint broken? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train
[Desktop-packages] [Bug 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
I have twice installed Linux Mint on an 2011 iMac. It is 21.5 inch with AMD Radeon HD 6750M 512 MB graphics and 2.5 GHz Intel Core i5. Every time I install Linux Mint, it boots correctly a couple times but then simply displays a totally blank screen when booted up. Once this happens, the system will not boot correctly again. Ubuntu works fine, why is Linux Mint broken? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train
[Desktop-packages] [Bug 2038557] Re: Update gtk4 to 4.12.3
Uploaded now to noble and mantic series ** Changed in: gtk4 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2038557 Title: Update gtk4 to 4.12.3 Status in gtk4 package in Ubuntu: Fix Committed Bug description: There is a new point release in the stable GTK 4.12 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.12.3/NEWS The version currently in Ubuntu 23.10 is 4.12.2 Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- Many of the default Ubuntu 23.10 desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are not affected by this SRU. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2038557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
New info: I realised this is something related to my integrated graphic
in my laptop (AMD Radeon graphic integrated). So, if I launch Firefox,
Steam etc. with my dedicated graphic (AMD Radeon RX 5600m), works
perfectly, no issues.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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/gnome-shell/+bug/2038998/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039964] Re: Internal hard disk partition cannot be mounted manually
Please delete this bug report.
I fixed the issue by running chkdsk on the Windows side. It found errors
that were fixed and the NTFS partition can now be mounted and read by
Ubuntu. I still don't understand why Ubuntu 23.04 could mount and read
the partition with the errors present but the issue is now fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039964
Title:
Internal hard disk partition cannot be mounted manually
Status in udisks2 package in Ubuntu:
New
Bug description:
I upgraded to 23.10. Since then I cannot access the NTFS partition on
this dual boot (with Windows 10) PC. Also an external USB drive
formatted in NTFS cannot be mounted. Everything works fine on 23.04.
The error message received is idential in both cases:
Error mounting /dev/sda4 at /media/john/: wrong fs type, bad option,
bad superblock on /dev/sda4, missing codepage or helper program or
other error
To repeat - everying works fine on 23.04. There is no problem with the
NTFS partition or USB drive on Windows or 23.04.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: udisks2 2.10.1-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.snapd.rules
70-snap.snapd-desktop-integration.rules 70-snap.snap-store.rules
70-snap.firefox.rules 70-snap.firmware-updater.rules
Date: Fri Oct 20 11:26:01 2023
InstallationDate: Installed on 2023-09-30 (20 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
Lsusb:
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=617f5749-671f-4ec7-8fbb-5d6d8b33bdfd ro quiet splash vt.handoff=7
SourcePackage: udisks2
Symptom: storage
Title: Internal hard disk partition cannot be mounted manually
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-DS2 DVI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/12/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2DVI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2039964/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040292] Re: network-manager SRU flags system for restart required but also restarted the service
** Tags removed: block-proposed-mantic -- 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/2040292 Title: network-manager SRU flags system for restart required but also restarted the service Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Mantic: New Bug description: [ Impact ] * During an upgrade (or installation) of the network-manager package, its debian/network-manager.postinst maintainer script restarts NetworkManager.service and also requests users to reboot their system. * It requests a reboot, by calling into /usr/share/update-notifier/notify-reboot-required and listing "network-manager" in /var/run/reboot-required.pkgs * Restarting the systemd service AND asking for a reboot isn't needed. Just the service restart is enough and we shouldn't ask for a reboot as that is bad UX [ Test Plan ] * Reboot your system (or clear /var/run/reboot-required.pkgs) echo "" | sudo tee /var/run/reboot-required.pkgs * Install network-manager from mantic-proposed apt install [--reinstall] -t mantic-proposed network-manager * Observe that the NetworkManager.service was restarted by this operation: "active (running) [...] 2 min ago" systemctl status Networkmanager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; preset: enabled) Active: active (running) since Wed 2023-10-25 15:21:27 CEST; 2min ago Docs: man:NetworkManager(8) Main PID: 3880250 (NetworkManager) Tasks: 4 (limit: 28344) Memory: 6.1M CPU: 425ms CGroup: /system.slice/NetworkManager.service └─3880250 /usr/sbin/NetworkManager --no-daemon * Observe that network-manager was NOT written to /var/run/reboot-required.pkgs cat /var/run/reboot-required.pkgs * Observe that no GUI popped up asking you for a reboot because of NetworkManager [ Where problems could occur ] * This change is touching a maintainer script (.postinst) * Failures or syntax errors could leave the network-manager package unconfigured * It could break installation of the network-manager package [ Other Info ] * This SRU should probably just be staged, using `block-proposed-mantic` and bundled with the next upload. === original description === After applying the network-manager SRU in mantic, I get a notification that a system restart is required to fully apply updates. This immediately raised a question, because I KNOW my network connection was restarted when the SRU was installed (I have a VPN that did not auto-reconnect). And I checked the state of the process - it was definitely restarted and is running from the binary currently on disk. The network-manager postinst has the following code: # request a reboot (NM tears down interfaces on restart # which is not the way we want to go) [ -x /usr/share/update-notifier/notify-reboot-required ] && \ /usr/share/update-notifier/notify-reboot-required But the service restart is also happening. debian/rules currently has: override_dh_installsystemd: dh_installsystemd -pnetwork-manager --no-start NetworkManager-dispatcher.service NetworkManager-wait-online.service nm-priv-helper.service dh_installsystemd -pnetwork-manager --no-also NetworkManager.service No other systemd overrides. Nothing inhibits the restart of the service. It needs to be one or the other. And if we're doing SRUs of network- manager, then this is bad UX for users applying their daily updates and should be fixed in SRU. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:19:38 2023 InstallationDate: Installed on 2019-12-23 (1401 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-10-16 (8 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2040292/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2026301] Re: LibreOffice Impress always crash and not responding while save PPTX files
Sorry, I can't test it again because I upgrade my Ubuntu to 23.10, which is included LibreOffice 7.6 in repos -- 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/2026301 Title: LibreOffice Impress always crash and not responding while save PPTX files Status in libreoffice package in Ubuntu: New Bug description: I have a template from SlidesGo and I edit it in LibreOffice Impress. But, I find if I save my file (with PPTX format) it always not responding and I repeat to click "Wait" to save my PPTX file correctly ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libreoffice-impress 4:7.5.4-0ubuntu0.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 7 00:12:22 2023 InstallationDate: Installed on 2023-07-04 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2026301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040296] Re: On the top pannel which contains date and time the calendar popup when I click on the upcoming months date that is november 1, 2023 last two weeks are displayed ou
** Package changed: ubuntu => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/2040296 Title: On the top pannel which contains date and time the calendar popup when I click on the upcoming months date that is november 1, 2023 last two weeks are displayed outside the box which contains the weeks. I am reporting this bug on oct 24, 2023 Status in gnome-shell package in Ubuntu: New Bug description: On the top pannel which contains date and time the calendar popup when I click on the upcoming months date that is november 1, 2023 last two weeks are displayed outside the box which contains the weeks. I am reporting this bug on oct 24, 2023. This is happening if i click the button of 1st november 2023 without clicking after button, if click any other day and click the next month november date which follows after october it is ok, but if my first click is next month nov1, nov2, nov3, nov4, this problem is occuring. kindly fix this error community. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040296] [NEW] On the top pannel which contains date and time the calendar popup when I click on the upcoming months date that is november 1, 2023 last two weeks are displayed
You have been subscribed to a public bug: On the top pannel which contains date and time the calendar popup when I click on the upcoming months date that is november 1, 2023 last two weeks are displayed outside the box which contains the weeks. I am reporting this bug on oct 24, 2023. This is happening if i click the button of 1st november 2023 without clicking after button, if click any other day and click the next month november date which follows after october it is ok, but if my first click is next month nov1, nov2, nov3, nov4, this problem is occuring. kindly fix this error community. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- On the top pannel which contains date and time the calendar popup when I click on the upcoming months date that is november 1, 2023 last two weeks are displayed outside the box which contains the weeks. I am reporting this bug on oct 24, 2023 https://bugs.launchpad.net/bugs/2040296 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040292] Re: network-manager SRU flags system for restart required but also restarted the service
** Tags added: block-proposed-mantic -- 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/2040292 Title: network-manager SRU flags system for restart required but also restarted the service Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Mantic: New Bug description: [ Impact ] * During an upgrade (or installation) of the network-manager package, its debian/network-manager.postinst maintainer script restarts NetworkManager.service and also requests users to reboot their system. * It requests a reboot, by calling into /usr/share/update-notifier/notify-reboot-required and listing "network-manager" in /var/run/reboot-required.pkgs * Restarting the systemd service AND asking for a reboot isn't needed. Just the service restart is enough and we shouldn't ask for a reboot as that is bad UX [ Test Plan ] * Reboot your system (or clear /var/run/reboot-required.pkgs) echo "" | sudo tee /var/run/reboot-required.pkgs * Install network-manager from mantic-proposed apt install [--reinstall] -t mantic-proposed network-manager * Observe that the NetworkManager.service was restarted by this operation: "active (running) [...] 2 min ago" systemctl status Networkmanager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; preset: enabled) Active: active (running) since Wed 2023-10-25 15:21:27 CEST; 2min ago Docs: man:NetworkManager(8) Main PID: 3880250 (NetworkManager) Tasks: 4 (limit: 28344) Memory: 6.1M CPU: 425ms CGroup: /system.slice/NetworkManager.service └─3880250 /usr/sbin/NetworkManager --no-daemon * Observe that network-manager was NOT written to /var/run/reboot-required.pkgs cat /var/run/reboot-required.pkgs * Observe that no GUI popped up asking you for a reboot because of NetworkManager [ Where problems could occur ] * This change is touching a maintainer script (.postinst) * Failures or syntax errors could leave the network-manager package unconfigured * It could break installation of the network-manager package [ Other Info ] * This SRU should probably just be staged, using `block-proposed-mantic` and bundled with the next upload. === original description === After applying the network-manager SRU in mantic, I get a notification that a system restart is required to fully apply updates. This immediately raised a question, because I KNOW my network connection was restarted when the SRU was installed (I have a VPN that did not auto-reconnect). And I checked the state of the process - it was definitely restarted and is running from the binary currently on disk. The network-manager postinst has the following code: # request a reboot (NM tears down interfaces on restart # which is not the way we want to go) [ -x /usr/share/update-notifier/notify-reboot-required ] && \ /usr/share/update-notifier/notify-reboot-required But the service restart is also happening. debian/rules currently has: override_dh_installsystemd: dh_installsystemd -pnetwork-manager --no-start NetworkManager-dispatcher.service NetworkManager-wait-online.service nm-priv-helper.service dh_installsystemd -pnetwork-manager --no-also NetworkManager.service No other systemd overrides. Nothing inhibits the restart of the service. It needs to be one or the other. And if we're doing SRUs of network- manager, then this is bad UX for users applying their daily updates and should be fixed in SRU. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:19:38 2023 InstallationDate: Installed on 2019-12-23 (1401 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-10-16 (8 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2040292/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2038557] Re: Update gtk4 to 4.12.3
** Description changed: There is a new point release in the stable GTK 4.12 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.12.3/NEWS The version currently in Ubuntu 23.10 is 4.12.2 Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok + Test Case 3 + --- + Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. + What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. Many of the default Ubuntu 23.10 desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Description changed: There is a new point release in the stable GTK 4.12 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.12.3/NEWS The version currently in Ubuntu 23.10 is 4.12.2 Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- - Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. + Many of the default Ubuntu 23.10 desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. - The Ubuntu flavors use a different portal backend, most commonly xdg- - desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. - - Many of the default Ubuntu 23.10 desktop apps use GTK4. A serious enough - regression could severely break the Ubuntu Desktop. + Ubuntu includes xdg-desktop-portal-gnome by default which is used for + many snap actions like providing a file chooser. This is critical + functionality for our snaps. The Ubuntu flavors use a different portal + backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are + not affected by this SRU. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2038557 Title: Update gtk4 to 4.12.3 Status in gtk4 package in Ubuntu: In Progress Bug description: There is a new point release in the stable GTK 4.12 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.12.3/NEWS The version currently in Ubuntu 23.10 is 4.12.2 Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- Many of the default Ubuntu 23.10 desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly
[Desktop-packages] [Bug 2040292] Re: network-manager SRU flags system for restart required but also restarted the service
** Description changed: + [ Impact ] + + * During an upgrade (or installation) of the network-manager package, its debian/network-manager.postinst maintainer script restarts NetworkManager.service and also requests users to reboot their system. + * It requests a reboot, by calling into /usr/share/update-notifier/notify-reboot-required and listing "network-manager" in /var/run/reboot-required.pkgs + * Restarting the systemd service AND asking for a reboot isn't needed. Just the service restart is enough and we shouldn't ask for a reboot as that is bad UX + + [ Test Plan ] + + * Reboot your system (or clear /var/run/reboot-required.pkgs) +echo "" | sudo tee /var/run/reboot-required.pkgs + * Install network-manager from mantic-proposed +apt install [--reinstall] -t mantic-proposed network-manager + * Observe that the NetworkManager.service was restarted by this operation: "active (running) [...] 2 min ago" +systemctl status Networkmanager.service + ● NetworkManager.service - Network Manager + Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; preset: enabled) + Active: active (running) since Wed 2023-10-25 15:21:27 CEST; 2min ago +Docs: man:NetworkManager(8) +Main PID: 3880250 (NetworkManager) + Tasks: 4 (limit: 28344) + Memory: 6.1M + CPU: 425ms + CGroup: /system.slice/NetworkManager.service + └─3880250 /usr/sbin/NetworkManager --no-daemon + * Observe that network-manager was NOT written to /var/run/reboot-required.pkgs +cat /var/run/reboot-required.pkgs + * Observe that no GUI popped up asking you for a reboot because of NetworkManager + + [ Where problems could occur ] + + * This change is touching a maintainer script (.postinst) + * Failures or syntax errors could leave the network-manager package unconfigured + * It could break installation of the network-manager package + + [ Other Info ] + + * This SRU should probably just be staged, using `block-proposed-mantic` and bundled with the next upload. + + === original description === + After applying the network-manager SRU in mantic, I get a notification that a system restart is required to fully apply updates. This immediately raised a question, because I KNOW my network connection was restarted when the SRU was installed (I have a VPN that did not auto-reconnect). And I checked the state of the process - it was definitely restarted and is running from the binary currently on disk. The network-manager postinst has the following code: - # request a reboot (NM tears down interfaces on restart - # which is not the way we want to go) - [ -x /usr/share/update-notifier/notify-reboot-required ] && \ - /usr/share/update-notifier/notify-reboot-required + # request a reboot (NM tears down interfaces on restart + # which is not the way we want to go) + [ -x /usr/share/update-notifier/notify-reboot-required ] && \ + /usr/share/update-notifier/notify-reboot-required But the service restart is also happening. debian/rules currently has: override_dh_installsystemd: - dh_installsystemd -pnetwork-manager --no-start NetworkManager-dispatcher.service NetworkManager-wait-online.service nm-priv-helper.service - dh_installsystemd -pnetwork-manager --no-also NetworkManager.service + dh_installsystemd -pnetwork-manager --no-start NetworkManager-dispatcher.service NetworkManager-wait-online.service nm-priv-helper.service + dh_installsystemd -pnetwork-manager --no-also NetworkManager.service No other systemd overrides. Nothing inhibits the restart of the service. It needs to be one or the other. And if we're doing SRUs of network- manager, then this is bad UX for users applying their daily updates and should be fixed in SRU. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:19:38 2023 InstallationDate: Installed on 2019-12-23 (1401 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-10-16 (8 days ago) nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.44.2 connected started full enabled enabled enabled missing enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.44.2 connected started full enabled enabled enabled missing enabled -- You
[Desktop-packages] [Bug 2040292] Re: network-manager SRU flags system for restart required but also restarted the service
** Also affects: network-manager (Ubuntu Mantic) Importance: Undecided Status: New -- 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/2040292 Title: network-manager SRU flags system for restart required but also restarted the service Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Mantic: New Bug description: After applying the network-manager SRU in mantic, I get a notification that a system restart is required to fully apply updates. This immediately raised a question, because I KNOW my network connection was restarted when the SRU was installed (I have a VPN that did not auto-reconnect). And I checked the state of the process - it was definitely restarted and is running from the binary currently on disk. The network-manager postinst has the following code: # request a reboot (NM tears down interfaces on restart # which is not the way we want to go) [ -x /usr/share/update-notifier/notify-reboot-required ] && \ /usr/share/update-notifier/notify-reboot-required But the service restart is also happening. debian/rules currently has: override_dh_installsystemd: dh_installsystemd -pnetwork-manager --no-start NetworkManager-dispatcher.service NetworkManager-wait-online.service nm-priv-helper.service dh_installsystemd -pnetwork-manager --no-also NetworkManager.service No other systemd overrides. Nothing inhibits the restart of the service. It needs to be one or the other. And if we're doing SRUs of network- manager, then this is bad UX for users applying their daily updates and should be fixed in SRU. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:19:38 2023 InstallationDate: Installed on 2019-12-23 (1401 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-10-16 (8 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2040292/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040292] Re: network-manager SRU flags system for restart required but also restarted the service
** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: Confirmed => Triaged -- 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/2040292 Title: network-manager SRU flags system for restart required but also restarted the service Status in network-manager package in Ubuntu: Triaged Bug description: After applying the network-manager SRU in mantic, I get a notification that a system restart is required to fully apply updates. This immediately raised a question, because I KNOW my network connection was restarted when the SRU was installed (I have a VPN that did not auto-reconnect). And I checked the state of the process - it was definitely restarted and is running from the binary currently on disk. The network-manager postinst has the following code: # request a reboot (NM tears down interfaces on restart # which is not the way we want to go) [ -x /usr/share/update-notifier/notify-reboot-required ] && \ /usr/share/update-notifier/notify-reboot-required But the service restart is also happening. debian/rules currently has: override_dh_installsystemd: dh_installsystemd -pnetwork-manager --no-start NetworkManager-dispatcher.service NetworkManager-wait-online.service nm-priv-helper.service dh_installsystemd -pnetwork-manager --no-also NetworkManager.service No other systemd overrides. Nothing inhibits the restart of the service. It needs to be one or the other. And if we're doing SRUs of network- manager, then this is bad UX for users applying their daily updates and should be fixed in SRU. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:19:38 2023 InstallationDate: Installed on 2019-12-23 (1401 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-10-16 (8 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2040292/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040450] Re: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libxkbcommon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/2040450 Title: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken Status in libxkbcommon package in Ubuntu: Confirmed Bug description: When using keyboard layout Latvian (apostrophe), when writing accented characters like "š", second character is outputed accented, too. When writing, for example, 'so, šō is outputted (should be šo) When testing keyboard during Ubuntu 23.10 installation and choosing Latvian (apostrophe) layout, the behaviour was correct. affects ubuntu/mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/2040450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1187077] Re: package libgl1-mesa-dri failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd6
Problem in Ubuntu 22.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1187077 Title: package libgl1-mesa-dri failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 Status in mesa package in Ubuntu: Expired Bug description: Happened after installing fglrx-updates. ProblemType: Package DistroRelease: Ubuntu 13.04 Package: libgl1-mesa-dri 9.1.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 3 18:35:36 2013 DistUpgraded: 2013-06-01 18:31:15,548 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.012, 3.8.0-23-generic, x86_64: installed DpkgTerminalLog: Preparing to replace libgl1-mesa-dri:amd64 9.1.1-0ubuntu3 (using .../libgl1-mesa-dri_9.1.1-0ubuntu3_amd64.deb) ... Unpacking replacement libgl1-mesa-dri:amd64 ... dpkg: error processing /var/cache/apt/archives/libgl1-mesa-dri_9.1.1-0ubuntu3_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 DuplicateSignature: Unpacking replacement libgl1-mesa-dri:amd64 ... dpkg: error processing /var/cache/apt/archives/libgl1-mesa-dri_9.1.1-0ubuntu3_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:056e] Advanced Micro Devices [AMD] nee ATI Thames XT [Radeon HD 7670M] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:056e] InstallationDate: Installed on 2012-09-07 (268 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) JockeyStatus: kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) kmod:fglrx_updates - ATI Fire GL (Proprietary, Enabled, Not in use) MachineType: Dell Inc. Vostro 3560 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-23-generic root=UUID=ee915b12-aec5-4d5c-868e-82e41c81b4da ro quiet splash vt.handoff=7 SourcePackage: mesa Title: package libgl1-mesa-dri 9.1.1-0ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 UpgradeStatus: Upgraded to raring on 2013-06-01 (2 days ago) dmi.bios.date: 05/17/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0C05GV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/17/2012:svnDellInc.:pnVostro3560:pvrA07:rvnDellInc.:rn0C05GV:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Vostro 3560 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1187077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
The attachment "debdiff that replaces mem-leaky ubuntu openssl3 patch with the gentoo openssl3 patch" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040488] [NEW] loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed
Public bug reported: I tried to do this with `apport-cli /var/crash/_usr_libexec_udisks2_udisksd.0.crash`, but 's'ending doesn't do anything obvious. I run this from a cloud image over ssh, I really don't have any GUI. So filing this manually. Trying to load the lvm2 module crashes udisks immediately: busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager EnableModule sb lvm2 true udisksd[5709]: cannot register existing type 'UDisksDaemon' udisksd[5709]: g_once_init_leave: assertion 'result != 0' failed udisksd[5709]: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed systemd[1]: Started systemd-coredump@2-5767-0.service - Process Core Dump (PID 5767/UID 0). Module libudev.so.1 from deb systemd-253.5-1ubuntu6.amd64 Module libsystemd.so.0 from deb systemd-253.5-1ubuntu6.amd64 Stack trace of thread 5709: #0 0x56079be701ad udisks_module_manager_load_modules (udisksd + 0x601ad) #1 0x56079be5fdf5 n/a (udisksd + 0x4fdf5) #2 0x7f7d5f122a11 n/a (libglib-2.0.so.0 + 0x5aa11) #3 0x7f7d5f17e46f n/a (libglib-2.0.so.0 + 0xb646f) #4 0x7f7d5f12346f g_main_loop_run (libglib-2.0.so.0 + 0x5b46f) #5 0x56079be323d2 main (udisksd + 0x223d2) #6 0x7f7d5ee280d0 __libc_start_call_main (libc.so.6 + 0x280d0) #7 0x7f7d5ee28189 __libc_start_main_impl (libc.so.6 + 0x28189) #8 0x56079be324f5 _start (udisksd + 0x224f5) ProblemType: Crash Architecture: amd64 Date: Wed Oct 25 12:13:14 2023 DistroRelease: Ubuntu 23.10 ExecutablePath: /usr/libexec/udisks2/udisksd Package: udisks2 2.10.1-1ubuntu1 ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Affects: udisks2 (Ubuntu Mantic) Importance: Undecided Status: New ** Tags: mantic regression-release ** Also affects: udisks2 (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2040488 Title: loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed Status in udisks2 package in Ubuntu: New Status in udisks2 source package in Mantic: New Bug description: I tried to do this with `apport-cli /var/crash/_usr_libexec_udisks2_udisksd.0.crash`, but 's'ending doesn't do anything obvious. I run this from a cloud image over ssh, I really don't have any GUI. So filing this manually. Trying to load the lvm2 module crashes udisks immediately: busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager EnableModule sb lvm2 true udisksd[5709]: cannot register existing type 'UDisksDaemon' udisksd[5709]: g_once_init_leave: assertion 'result != 0' failed udisksd[5709]: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed systemd[1]: Started systemd-coredump@2-5767-0.service - Process Core Dump (PID 5767/UID 0). Module libudev.so.1 from deb systemd-253.5-1ubuntu6.amd64 Module libsystemd.so.0 from deb systemd-253.5-1ubuntu6.amd64 Stack trace of thread 5709: #0 0x56079be701ad udisks_module_manager_load_modules (udisksd + 0x601ad) #1 0x56079be5fdf5 n/a (udisksd + 0x4fdf5) #2 0x7f7d5f122a11 n/a (libglib-2.0.so.0 + 0x5aa11) #3 0x7f7d5f17e46f n/a (libglib-2.0.so.0 + 0xb646f) #4 0x7f7d5f12346f g_main_loop_run (libglib-2.0.so.0 + 0x5b46f) #5 0x56079be323d2 main (udisksd + 0x223d2) #6 0x7f7d5ee280d0 __libc_start_call_main (libc.so.6 + 0x280d0) #7 0x7f7d5ee28189 __libc_start_main_impl (libc.so.6 + 0x28189) #8 0x56079be324f5 _start (udisksd + 0x224f5) ProblemType: Crash Architecture: amd64 Date: Wed Oct 25 12:13:14 2023 DistroRelease: Ubuntu 23.10
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
The development release isn't open yet. We will need to sync across from Debian when it opens. I am subscribed to this bug. Feel free to ping me here if it's not been done in a few weeks. ** Changed in: qpdf (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Triaged Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
Thank you for the discussion. On balance I think what you've said makes sense and it's not worth going further, but I think it's important to have the trade-offs and choices documented here and that's done now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Triaged Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has a
[Desktop-packages] [Bug 2039804] Please test proposed package
Hello Jay, or anyone else affected, Accepted qpdf into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qpdf/11.3.0-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Confirmed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
Hello Jay, or anyone else affected, Accepted qpdf into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qpdf/11.5.0-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: qpdf (Ubuntu Mantic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: qpdf (Ubuntu Lunar) Status: New => Fix Committed ** Tags added: verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Confirmed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream:
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
** Summary changed: - SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 + Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Confirmed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has
[Desktop-packages] [Bug 2040450] Re: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken
** Package changed: ubuntu => libxkbcommon (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/2040450 Title: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken Status in libxkbcommon package in Ubuntu: New Bug description: When using keyboard layout Latvian (apostrophe), when writing accented characters like "š", second character is outputed accented, too. When writing, for example, 'so, šō is outputted (should be šo) When testing keyboard during Ubuntu 23.10 installation and choosing Latvian (apostrophe) layout, the behaviour was correct. affects ubuntu/mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/2040450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040478] [NEW] Issue when screen locking or suspending
Public bug reported: There are several issues with the suspend/screen lock options in Ubuntu. First of all, the extensions are automatically deactivated when locking or suspending. Second, the suspend option never works as expected, when leaving the device for a while after suspending the fans increase to 100% and the device gets really hot. Afterwards, the only option is the reboot the device since it's "stuck" in a recovery mode. Current release: Ubuntu 23.10 (happened as well on 22.04, 23.04) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-screensaver 3.6.1-13ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 12:27:02 2023 GnomeSessionIdleInhibited: Yes GnomeSessionInhibitors: 1: AppId = user, Flags = 12, Reason = Inhibit by undefined GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'gnome' InstallationDate: Installed on 2022-02-16 (616 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to mantic on 2023-10-25 (0 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/2040478 Title: Issue when screen locking or suspending Status in gnome-screensaver package in Ubuntu: New Bug description: There are several issues with the suspend/screen lock options in Ubuntu. First of all, the extensions are automatically deactivated when locking or suspending. Second, the suspend option never works as expected, when leaving the device for a while after suspending the fans increase to 100% and the device gets really hot. Afterwards, the only option is the reboot the device since it's "stuck" in a recovery mode. Current release: Ubuntu 23.10 (happened as well on 22.04, 23.04) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-screensaver 3.6.1-13ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 12:27:02 2023 GnomeSessionIdleInhibited: Yes GnomeSessionInhibitors: 1: AppId = user, Flags = 12, Reason = Inhibit by undefined GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'gnome' InstallationDate: Installed on 2022-02-16 (616 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to mantic on 2023-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/2040478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
For some reason some binaries are no longer making it into the snap. :| I'm investigating... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
I backported Andrey Kudinov's suggested change (replacing Ubuntu's openssl3-compat.patch with gentoo's version) and built a transmission package in a PPA for jammy (Andrey's PPA only has packages for kinetic and lunar). I've been testing the patched transmission-gtk for the last 24 hours and the memory leak is gone. I'm attaching a debdiff. ** Patch added: "debdiff that replaces mem-leaky ubuntu openssl3 patch with the gentoo openssl3 patch" https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+attachment/5713173/+files/fix-mem-leak.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted
I can confirm this fixes the issue for me, too, using network-manager 1.44.2-1ubuntu1.2 from mantic-proposed. $ sudo apt install -t mantic-proposed network-manager [...] $ LC_ALL=C apt list -i network-manager Listing... Done network-manager/mantic-proposed,now 1.44.2-1ubuntu1.2 amd64 [installed] $ nmcli con add type dummy connection.interface-name dummy0 $ sudo cat /etc/netplan/90-NM-4189c63a-ecee-4a39-90f3-fffad2b96d0b.yaml network: version: 2 dummy-devices: NM-4189c63a-ecee-4a39-90f3-fffad2b96d0b: renderer: NetworkManager networkmanager: uuid: "4189c63a-ecee-4a39-90f3-fffad2b96d0b" name: "dummy-dummy0" passthrough: connection.interface-name: "dummy0" dummy._: "" ipv4.method: "disabled" ipv6.addr-gen-mode: "default" ipv6.method: "disabled" ipv6.ip6-privacy: "-1" proxy._: "" $ nmcli d show dummy0 GENERAL.DEVICE: dummy0 GENERAL.TYPE: dummy GENERAL.HWADDR: 32:89:DC:E0:74:2F GENERAL.MTU:1500 GENERAL.STATE: 100 (verbunden) GENERAL.CONNECTION: dummy-dummy0 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/10 IP4.GATEWAY:-- IP6.GATEWAY:-- $ nmcli con del dummy-dummy0 $ LC_ALL=C nmcli d show dummy0 Error: Device 'dummy0' not found. $ sudo LC_ALL=C cat /etc/netplan/90-NM-4189c63a-ecee-4a39-90f3-fffad2b96d0b.yaml cat: /etc/netplan/90-NM-4189c63a-ecee-4a39-90f3-fffad2b96d0b.yaml: No such file or directory $ journalctl -u NetworkManager -e # I cannot spot any errors in here ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- 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/2040153 Title: Network Manager will not remove Netplan YAMLs when connections are deleted Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: In Progress Status in netplan.io source package in Mantic: Invalid Status in network-manager source package in Mantic: Fix Committed Bug description: [ Impact ] Desktop users, or any users with YAML files in /usr/lib/netplan, can't delete Network Manager connections persistently. That means that, when the connection is deliberately deleted by the user, it will re-appear when the system is rebooted or netplan apply is executed. This is happening because the systemd service unit is setting the property "ProtectSystem" to true. Because of that, /usr is being presented to the Network Manager daemon as read-only. When connections are deleted, libnetplan will try to open its YAML files with writing permissions and will fail for files from /usr/lib/netplan. Even if the user hasn't added any files there manually, the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by the package ubuntu-settings. This issue is fixed by allow-listing /usr/lib/netplan with ReadWritePaths=/usr/lib/netplan in systemd so the Network Manager's daemon will be able to write to that directory. This upload also improves the autopkgtests related to Netplan. Network Manager will be started by systemd, which ensures we are testing in the same environment conditions used by a desktop installation. It also adds a few more instances of connections deletions so we can test a bit more that YAML files are being removed. It also adds all the dependencies required by the test script (which sadly was causing the nm_netplan.py tests to be skipped). [ Test Plan ] Launch a new Mantic VM: $ lxc launch ubuntu:mantic --vm Install network-manager and ubuntu-settings: # apt install network-manager ubuntu-settings Run Netplan # netplan apply Create a dummy connection via nmcli: # nmcli con add type dummy connection.interface-name dummy0 Check a new YAML will be created in /etc/netplan Delete the connection with nmcli # nmcli con del dummy-dummy0 Check the YAML WAS NOT removed from /etc/netplan You will see the error below in the NetworkManager's journal netplan_delete_connection: Cannot write output state: Read-only file system Add the PPA containing the fix and run the same test described above # add-apt-repository ppa:danilogondolfo/network-manager # apt update # apt upgrade Check that the YAML will be created when the connection is added and deleted and the connection is removed. [ Where problems could occur ] As the only change is a relaxation of the restrictions applied by systemd on the environment where Network Manager runs, we are not expecting any regression. As for the changes in the autopkgtest related to Netplan, they are passing on all
[Desktop-packages] [Bug 2040450] [NEW] Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken
You have been subscribed to a public bug: When using keyboard layout Latvian (apostrophe), when writing accented characters like "š", second character is outputed accented, too. When writing, for example, 'so, šō is outputted (should be šo) When testing keyboard during Ubuntu 23.10 installation and choosing Latvian (apostrophe) layout, the behaviour was correct. affects ubuntu/mantic ** Affects: libxkbcommon (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken https://bugs.launchpad.net/bugs/2040450 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxkbcommon 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 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted
The autopkgtest failures on arm64 are not related to these changes and it's happening for a while now. So they are not regressions. I'm running network-manager from proposed on my main machine and the problem is resolved. -- 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/2040153 Title: Network Manager will not remove Netplan YAMLs when connections are deleted Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: In Progress Status in netplan.io source package in Mantic: Invalid Status in network-manager source package in Mantic: Fix Committed Bug description: [ Impact ] Desktop users, or any users with YAML files in /usr/lib/netplan, can't delete Network Manager connections persistently. That means that, when the connection is deliberately deleted by the user, it will re-appear when the system is rebooted or netplan apply is executed. This is happening because the systemd service unit is setting the property "ProtectSystem" to true. Because of that, /usr is being presented to the Network Manager daemon as read-only. When connections are deleted, libnetplan will try to open its YAML files with writing permissions and will fail for files from /usr/lib/netplan. Even if the user hasn't added any files there manually, the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by the package ubuntu-settings. This issue is fixed by allow-listing /usr/lib/netplan with ReadWritePaths=/usr/lib/netplan in systemd so the Network Manager's daemon will be able to write to that directory. This upload also improves the autopkgtests related to Netplan. Network Manager will be started by systemd, which ensures we are testing in the same environment conditions used by a desktop installation. It also adds a few more instances of connections deletions so we can test a bit more that YAML files are being removed. It also adds all the dependencies required by the test script (which sadly was causing the nm_netplan.py tests to be skipped). [ Test Plan ] Launch a new Mantic VM: $ lxc launch ubuntu:mantic --vm Install network-manager and ubuntu-settings: # apt install network-manager ubuntu-settings Run Netplan # netplan apply Create a dummy connection via nmcli: # nmcli con add type dummy connection.interface-name dummy0 Check a new YAML will be created in /etc/netplan Delete the connection with nmcli # nmcli con del dummy-dummy0 Check the YAML WAS NOT removed from /etc/netplan You will see the error below in the NetworkManager's journal netplan_delete_connection: Cannot write output state: Read-only file system Add the PPA containing the fix and run the same test described above # add-apt-repository ppa:danilogondolfo/network-manager # apt update # apt upgrade Check that the YAML will be created when the connection is added and deleted and the connection is removed. [ Where problems could occur ] As the only change is a relaxation of the restrictions applied by systemd on the environment where Network Manager runs, we are not expecting any regression. As for the changes in the autopkgtest related to Netplan, they are passing on all architectures. Autopkgtests amd64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/amd64/n/network-manager/20231023_175203_b2798@/log.gz ppc64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/ppc64el/n/network-manager/20231023_182332_f0497@/log.gz s390x - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/s390x/n/network-manager/20231023_190810_ced8d@/log.gz arm64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/arm64/n/network-manager/20231024_084542_ac017@/log.gz armhf - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/armhf/n/network-manager/20231024_083545_ac017@/log.gz [ Other Info ] --- Original description --- When a connection is deleted using any NM facility, libnetplan is failing to delete the YAML file. Because of that, the connection will be recreated when "netplan generate" runs again. This is probably being caused by a combination of two things. First, the NM's systemd unit has this setting "ProtectSystem=true", which will mount /usr as read-only for NM. Second, we migrated the default "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1]. When libnetplan tries to open this file for writing, the open system fails with EROFS: --- 22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system) 22517 write(2,
[Desktop-packages] [Bug 2040474] [NEW] GPU reset fails and system freezes
Public bug reported: There is no specific scenario when the system crashes. In most cases the system crashes completely, but occasionally the system recovers. The system was freshly installed and updated with latest packages. Description:Ubuntu 23.10 Release:23.10 Kernel: 6.5.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 7 01:35:40 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/2040474/+attachment/5713166/+files/syslog.txt ** Description changed: There is no specific scenario when the system crashes. In most cases the system crashes completely, but occasionally the system recovers. The system was freshly installed and updated with latest packages. Description: Ubuntu 23.10 Release: 23.10 + + Kernel: 6.5.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 7 + 01:35:40 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2040474 Title: GPU reset fails and system freezes Status in mesa package in Ubuntu: New Bug description: There is no specific scenario when the system crashes. In most cases the system crashes completely, but occasionally the system recovers. The system was freshly installed and updated with latest packages. Description: Ubuntu 23.10 Release: 23.10 Kernel: 6.5.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 7 01:35:40 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2040474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040472] [NEW] Backport packages from mantic to server-backports PPA for focal and jammy
Public bug reported: Backport the following packages to the server-backports PPA for noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice', 'spice- protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager'] ** Affects: dpdk (Ubuntu) Importance: Undecided Status: New ** Affects: edk2 (Ubuntu) Importance: Undecided Status: New ** Affects: libslirp (Ubuntu) Importance: Undecided Status: New ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Affects: libvirt-python (Ubuntu) Importance: Undecided Status: New ** Affects: meson (Ubuntu) Importance: Undecided Status: New ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Affects: rdma-core (Ubuntu) Importance: Undecided Status: New ** Affects: seabios (Ubuntu) Importance: Undecided Status: New ** Affects: spice (Ubuntu) Importance: Undecided Status: New ** Affects: spice-protocol (Ubuntu) Importance: Undecided Status: New ** Affects: spice-vdagent (Ubuntu) Importance: Undecided Status: New ** Affects: virglrenderer (Ubuntu) Importance: Undecided Status: New ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New ** Affects: dpdk (Ubuntu Focal) Importance: Undecided Status: New ** Affects: edk2 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: libslirp (Ubuntu Focal) Importance: Undecided Status: New ** Affects: libvirt (Ubuntu Focal) Importance: Undecided Status: New ** Affects: libvirt-python (Ubuntu Focal) Importance: Undecided Status: New ** Affects: meson (Ubuntu Focal) Importance: Undecided Status: New ** Affects: openvswitch (Ubuntu Focal) Importance: Undecided Status: New ** Affects: qemu (Ubuntu Focal) Importance: Undecided Status: New ** Affects: rdma-core (Ubuntu Focal) Importance: Undecided Status: New ** Affects: seabios (Ubuntu Focal) Importance: Undecided Status: New ** Affects: spice (Ubuntu Focal) Importance: Undecided Status: New ** Affects: spice-protocol (Ubuntu Focal) Importance: Undecided Status: New ** Affects: spice-vdagent (Ubuntu Focal) Importance: Undecided Status: New ** Affects: virglrenderer (Ubuntu Focal) Importance: Undecided Status: New ** Affects: virt-manager (Ubuntu Focal) Importance: Undecided Status: New ** Affects: dpdk (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: edk2 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: libslirp (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: libvirt (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: libvirt-python (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: meson (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: openvswitch (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: qemu (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: rdma-core (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: seabios (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: spice (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: spice-protocol (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: spice-vdagent (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: virglrenderer (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: virt-manager (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: needs-ppa-backport ** Changed in: dpdk (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: edk2 (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: libslirp (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: libvirt (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: libvirt-python (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: meson (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: openvswitch (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: qemu (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: rdma-core (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: seabios (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: spice (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: spice-protocol (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: spice-vdagent (Ubuntu) Milestone: None => ubuntu-23.11 **
[Desktop-packages] [Bug 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
** Changed in: qpdf (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Confirmed Status in qpdf source package in Lunar: New Status in qpdf source package in Mantic: New Status in qpdf package in Debian: Confirmed Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change and has to be reprocessed in the new state. qpdf has a rigorous test suite and an extremely good quality record. It processes millions of documents daily by many commercial entities. My current employer runs millions of pages a day through qpdf. [ Other
[Desktop-packages] [Bug 2040453] Re: Gnome 45 crash on restart in X11 session
I don't see any evidence that upstream bug is related to this yet... 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. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. 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. 3. If step 2 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. 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. ** Project changed: gnome-shell => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Status: Unknown => New ** Changed in: ubuntu Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7050 => None ** No longer affects: ubuntu ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: mantic -- 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/2040453 Title: Gnome 45 crash on restart in X11 session Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer possible to restart gnome-shell without crashing the session. The only way not to crash it is to close all applications before restarting gnome-shell. I have verified this too. This has already been reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 a tentative patch for mutter proposed: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598 Please consider reviewing/testing this patch and pushing an update so people can restart gnome-shell session without crashing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040453] Re: Gnome 45 crash on restart in X11 session
** Project changed: mutter => gnome-shell -- 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/2040453 Title: Gnome 45 crash on restart in X11 session Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: New Bug description: Hello, Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer possible to restart gnome-shell without crashing the session. The only way not to crash it is to close all applications before restarting gnome-shell. I have verified this too. This has already been reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 a tentative patch for mutter proposed: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598 Please consider reviewing/testing this patch and pushing an update so people can restart gnome-shell session without crashing it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2040453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040453] [NEW] Gnome 45 crash on restart in X11 session
Public bug reported: Hello, Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer possible to restart gnome-shell without crashing the session. The only way not to crash it is to close all applications before restarting gnome-shell. I have verified this too. This has already been reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 a tentative patch for mutter proposed: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598 Please consider reviewing/testing this patch and pushing an update so people can restart gnome-shell session without crashing it. ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Attachment added: "proposed patch" https://bugs.launchpad.net/bugs/2040453/+attachment/5713163/+files/patch.txt ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7050 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2040453 Title: Gnome 45 crash on restart in X11 session Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: New Bug description: Hello, Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer possible to restart gnome-shell without crashing the session. The only way not to crash it is to close all applications before restarting gnome-shell. I have verified this too. This has already been reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 a tentative patch for mutter proposed: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598 Please consider reviewing/testing this patch and pushing an update so people can restart gnome-shell session without crashing it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2040453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
