[Desktop-packages] [Bug 1912911] Re: When printing with my Brother hl-2170w printer I keep getting an invalid page range error on a blank page, after the desired pages are printed
I also observed this issue on my laptop with 20.04. I created a patched version in this PPA[1] and it seems the issue is resolved with the patch mentioned in comment #5. If anyone can confirm the patched version does help, I'll submit the patch for SRU. [1] https://launchpad.net/~robertliu/+archive/ubuntu/lp-1912911 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1912911 Title: When printing with my Brother hl-2170w printer I keep getting an invalid page range error on a blank page, after the desired pages are printed Status in cups package in Ubuntu: Confirmed Bug description: When I run uname -a, this is basically what I get: "5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux" apt-cache policy cups gives me the following: cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages === 4 and 5 are being answered together... Before the upgrade, I was able to print one or more pages, and not see the extra error page. This is the desired behavior. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 23 13:15:24 2021 InstallationDate: Installed on 2020-12-21 (33 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for SCRIBE: dnssd://Brother%20HL-2170W%20series._pdl-datastream._tcp.local/ MachineType: Dell Inc. Inspiron 7773 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/SCRIBE.ppd'] failed with exit code 2: grep: /etc/cups/ppd/SCRIBE.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=9899e123-f378-4328-a399-78cd6361f58e ro quiet splash resume=UUID=46e80ad1-16de-4fdf-b1f7-96f4f58b1c57 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2017 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0R58C3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd09/14/2017:br1.2:svnDellInc.:pnInspiron7773:pvr:rvnDellInc.:rn0R58C3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7773 dmi.product.sku: 0809 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1912911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043755] Re: Screen show garbage when shrinking window from maximized window in Xorg
Recorded video ** Attachment added: "Ubuntu 22.04 Flash.mp4" https://bugs.launchpad.net/bugs/2043755/+attachment/5720302/+files/Ubuntu%2022.04%20Flash.mp4 ** Tags added: oem-priority originate-from-2043633 somerville -- 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/2043755 Title: Screen show garbage when shrinking window from maximized window in Xorg Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: The Windows is flickering when shrinking from maximized window in Xorg session. The issue won't happen if I disable animation in g-c-c > Accesibility > Enable Animations. Description:Ubuntu 22.04.3 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2043755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043755] [NEW] Screen show garbage when shrinking window from maximized window in Xorg
Public bug reported: The Windows is flickering when shrinking from maximized window in Xorg session. The issue won't happen if I disable animation in g-c-c > Accesibility > Enable Animations. Description:Ubuntu 22.04.3 LTS Release:22.04 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2043633 somerville ** Attachment added: "oemlogs-ubuntu-20231117111542+0800.apport.gz" https://bugs.launchpad.net/bugs/2043755/+attachment/5720301/+files/oemlogs-ubuntu-20231117111542+0800.apport.gz ** Description changed: - The Windows is flickering when shrinking from maximized window in Xorg - session. + The Windows is flickering when shrinking from maximized window in Xorg session. + The issue won't happen if I disable animation in g-c-c > Accesibility > Enable Animations. Description:Ubuntu 22.04.3 LTS Release:22.04 -- 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/2043755 Title: Screen show garbage when shrinking window from maximized window in Xorg Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: The Windows is flickering when shrinking from maximized window in Xorg session. The issue won't happen if I disable animation in g-c-c > Accesibility > Enable Animations. Description:Ubuntu 22.04.3 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2043755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
This is also happening for me. It takes multiple tries to launch some of my snap applications like Discord, Zoom, and Slack from my Application Menu. I don't have this problem for IntelliJ Ultimate. It seemed like a lot of the applications that are having this issue rely on core22, but I don't know if that's actually related. Here are my snaps (I've been trying to add and remove slack and zoom to try and fix them): NameVersion RevTracking Publisher Notes bare1.0 5 latest/stable canonical✓ base core16-2.60.416202 latest/stable canonical✓ core core18 20230901 2796 latest/stable canonical✓ base core22 20230801 864latest/stable canonical✓ base discord 0.0.35 163latest/stable snapcrafters✪ - gnome-42-2204 0+git.ff35a85141latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable canonical✓ - gtk2-common-themes 0.1 13 latest/stable canonical✓ - intellij-idea-ultimate 2023.2.5 462latest/stable jetbrains✓ classic snapd 2.60.4 20290 latest/stable canonical✓ snapd If I try opening them directly from the terminal it works every time. But if I open them using dolphin (with terminal open) I sometimes get the following error: /user.slice/user-1000.slice/user@1000.service/app.slice/app- discord_discord-f458540dedf040da87633a4e587169ac.scope is not a snap cgroup This seems to be consistent with the frequency of if I try and launch if from the Application Menu, so I'm assuming this is a similar error. Here is my system information: Operating System: Ubuntu 22.04 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 Kernel Version: 6.2.16-060216-generic (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: Radeon RX 7900 XTX Manufacturer: ASUS Hopefully this information is useful in trying to find a fix! -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue Status in GNOME Shell: New Status in KDE Base: New Status in gnome-desktop package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Status in kio package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Opinion Bug description: Hi, Lunar up to date, Intel+Nvidia GPUs, Ubuntu Wayland or X11 session, hybrid or discrete graphics. If I click on a snap dash icon, nothing happens. Tested with Thunderbird, Firefox, Shortwave... (VS Code seems ok, maybe due to classic confinment?) I can launch without issue Chrome (deb), Synaptic, GNOME apps, etc. Recent updates included gnome-shell and libadwaita. --- I get this type of log for all problematic snaps: /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome- shortwave_shortwave-11885.scope is not a snap cgroup --- Context: $ snap --version snap2.58.3+23.04ubuntu1 snapd 2.58.3+23.04ubuntu1 series 16 ubuntu 23.04 kernel 6.1.0-16-generic $ snap list Nom Version Révision Suivi Éditeur Notes bare 1.0 5 latest/stable canonical✓base code ee2b180d122 latest/stable vscode✓ classic core 16-2.58.2 14784 latest/stable canonical✓core core18202303082714 latest/stable canonical✓base core20202302071828 latest/stable canonical✓base core2220230210522 latest/stable canonical✓base firefox 111.0-2 2432 latest/candidate mozilla✓ - gimp 2.10.30 393 latest/stable snapcrafters - gnome-3-28-1804 3.28.0-19-g98f9e67.98f9e67 161 latest/stable canonical✓- gnome-3-38-2004 0+git.6f39565 119 latest/stable canonical✓- gnome-42-2204 0+git.09673a5 65 latest/stable canonical✓- gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓- gtk-theme-pocillo 0.14.4.1
[Desktop-packages] [Bug 2021523] Re: totem displays "Unable to play the file" dialog for a video it can play
Same obs. but with meta/x-gst-fourcc-mett. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2021523 Title: totem displays "Unable to play the file" dialog for a video it can play Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: I have an MP4 video file from a GoPro camera, and when I try to play it with totem, it displays a "Unable to play the file" dialog complaining about missing gstreamer elements (see attachment); totem prints the following on stderr: ** Message: 11:46:33.328: Missing plugin: gstreamer|1.0|totem|meta/x-gst-fourcc-fdsc decoder|decoder-meta/x-gst-fourcc-fdsc (meta/x-gst-fourcc-fdsc decoder) ** Message: 11:46:33.329: Missing plugin: gstreamer|1.0|totem|meta/x-gst-fourcc-gpmd decoder|decoder-meta/x-gst-fourcc-gpmd (meta/x-gst-fourcc-gpmd decoder) ** Message: 11:46:33.329: Missing plugin: gstreamer|1.0|totem|GStreamer element vaapipostproc|element-vaapipostproc (GStreamer element vaapipostproc) (totem:574404): GStreamer-CRITICAL **: 11:46:33.330: Trying to dispose element queue0, but it is in READY instead of the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. This problem may also be caused by a refcounting bug in the application or some element. If I click "cancel" to dismiss the dialog, then totem plays the video just fine. mediainfo shows the following for the video file in question: General Count: 332 Count of stream of this kind : 1 Kind of stream : General Kind of stream : General Stream identifier: 0 Count of video streams : 1 OtherCount : 3 Video_Format_List: AVC Video_Format_WithHint_List : AVC Codecs Video : AVC Video_Language_List : English Other_Format_List: QuickTime TC / / Other_Format_WithHint_List : QuickTime TC / / Other_Codec_List : QuickTime TC / / Other_Language_List : English / / Complete name: /home/roland/Pictures/GoPro-Hero8/2023/05/09/GH010165.MP4 Folder name : /home/roland/Pictures/GoPro-Hero8/2023/05/09 File name extension : GH010165.MP4 File name: GH010165 File extension : MP4 Format : MPEG-4 Format : MPEG-4 Format/Extensions usually used : braw mov mp4 m4v m4a m4b m4p m4r 3ga 3gpa 3gpp 3gp 3gpp2 3g2 k3g jpm jpx mqv ismv isma ismt f4a f4b f4v Commercial name : MPEG-4 Format profile : Base Media / Version 1 Internet media type : video/mp4 Codec ID : mp41 Codec ID : mp41 (mp41) Codec ID/Url : http://www.apple.com/quicktime/download/standalone.html CodecID_Compatible : mp41 File size: 2198334022 File size: 2.05 GiB File size: 2 GiB File size: 2.0 GiB File size: 2.05 GiB File size: 2.047 GiB Duration : 2624622 Duration : 43 min 44 s Duration : 43 min 44 s 622 ms Duration : 43 min 44 s Duration : 00:43:44.622 Duration : 00:02:54;27 Duration : 00:43:44.622 (00:02:54;27) Overall bit rate mode: VBR Overall bit rate mode: Variable Overall bit rate : 6700650 Overall bit rate : 6 701 kb/s Frame rate : 29.970 Frame rate : 29.970 FPS Frame count : 5243 Stream size : 10434366 Stream size : 9.95 MiB (0%)
[Desktop-packages] [Bug 1729433]
Jeff, Koen, Olivier and Jan: can you please test version 7.6.2 or above? With bug 125543 fixed, I wonder if the issue is also fixed for you. Thank you. -- 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/1729433 Title: LibreOffice doesn't remember window size when running under Wayland Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice package in Fedora: Confirmed Bug description: 1. Open any LibreOffice document, e.g., a Writer or Calc document. 2. Make the window a reasonable, non-maximized size. 3. Maximize the window. 4. Close LibreOffice. 5. Open the document again; it will open maximized. 6. Un-maximize the window. 7. Observe how the window has a ridiculously small size, not its previously unmaximized size. LibreOffice or gnome-shell bug? Not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-core 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:21:29 2017 InstallationDate: Installed on 2017-05-19 (166 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
Hello Mate, I see that the debdiff you provided applies to Noble, but this bug is also marked as affecting Mantic. Could you provide an updated debdiff for the Mantic version? Thanks! -- 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/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Mantic: New Status in mesa source package in Noble: Fix Released Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] Update Released
The verification of the Stable Release Update for qpdf has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to 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 Released Status in qpdf source package in Lunar: Fix Released Status in qpdf source package in Mantic: Fix Released Status in qpdf package in Debian: Fix Released 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
[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
This bug was fixed in the package qpdf - 11.3.0-1ubuntu1 --- qpdf (11.3.0-1ubuntu1) lunar; urgency=medium * Fix data loss bug introduced in 11.0.0 and fixed in 11.6.3. The bug causes the qpdf tokenizer to discard the character after a one-digit or two-digit quoted octal string. Most writers don't create these, and they are rare outside of content streams. By default, qpdf doesn't parse content streams. The most common place for this to occur would be in a document's /ID string, but in the worst case, this bug could cause silent damage to some strings in a PDF file's metadata, such as bookmark names or form field values. (LP: #2039804) -- Jay Berkenbilt Thu, 19 Oct 2023 07:09:54 -0400 ** Changed in: qpdf (Ubuntu Lunar) Status: Fix Committed => Fix Released -- 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 Released Status in qpdf source package in Lunar: Fix Released Status in qpdf source package in Mantic: Fix Released Status in qpdf package in Debian: Fix Released 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 ]
[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
This bug was fixed in the package qpdf - 11.5.0-1ubuntu1 --- qpdf (11.5.0-1ubuntu1) mantic; urgency=medium * Fix data loss bug introduced in 11.0.0 and fixed in 11.6.3. The bug causes the qpdf tokenizer to discard the character after a one-digit or two-digit quoted octal string. Most writers don't create these, and they are rare outside of content streams. By default, qpdf doesn't parse content streams. The most common place for this to occur would be in a document's /ID string, but in the worst case, this bug could cause silent damage to some strings in a PDF file's metadata, such as bookmark names or form field values. (LP: #2039804) -- Jay Berkenbilt Thu, 19 Oct 2023 07:20:25 -0400 ** Changed in: qpdf (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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 Released Status in qpdf source package in Lunar: Fix Released Status in qpdf source package in Mantic: Fix Released Status in qpdf package in Debian: Fix Released 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 ]
[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
Happy to (in addition to comment #19) confirm that qpdf + libqpdf29 from noble-release and mantic/lunar-proposed fix the issue. noble: --- $ lsb_release -cs No LSB modules are available. noble $ wget -q https://github.com/qpdf/qpdf/files/12885974/018.pdf $ sudo apt update && sudo apt install -y qpdf $ dpkg -s qpdf | grep Version: Version: 11.6.3-1 $ qpdf --check 018.pdf checking 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 mantic: --- $ lsb_release -cs No LSB modules are available. mantic $ wget -q https://github.com/qpdf/qpdf/files/12885974/018.pdf $ sudo apt update && sudo apt install -y qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.5.0-1 Version: 11.5.0-1 $ qpdf --check 018.pdf WARNING: 018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: 018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: 018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: 018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: 018.pdf: file is damaged WARNING: 018.pdf (offset 110267): xref not found WARNING: 018.pdf: Attempting to reconstruct cross-reference table qpdf: 018.pdf: unable to find trailer dictionary while recovering damaged file $ sudo add-apt-repository -yp proposed $ sudo apt install -y -t mantic-proposed qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.5.0-1ubuntu1 Version: 11.5.0-1ubuntu1 $ qpdf --check 018.pdf checking 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 lunar: --- $ lsb_release -cs lunar $ wget -q https://github.com/qpdf/qpdf/files/12885974/018.pdf $ sudo apt update && sudo apt install -y qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.3.0-1 Version: 11.3.0-1 $ qpdf --check 018.pdf WARNING: 018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: 018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: 018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: 018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: 018.pdf: file is damaged WARNING: 018.pdf (offset 110267): xref not found WARNING: 018.pdf: Attempting to reconstruct cross-reference table qpdf: 018.pdf: unable to find trailer dictionary while recovering damaged file $ sudo add-apt-repository -yp proposed $ sudo apt install -y -t lunar-proposed qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.3.0-1ubuntu1 Version: 11.3.0-1ubuntu1 $ qpdf --check 018.pdf checking 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 -- 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 Released Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Fix Released 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
[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
Marking Noble as Fix Released (11.6.3-1). $ git log --oneline -1 pkg/ubuntu/noble | cat 03517080d29d 11.6.3-1 (patches unapplied) $ git show pkg/ubuntu/noble -- libqpdf/QPDFTokenizer.cc ** Changed in: qpdf (Ubuntu) Status: Fix Committed => Fix Released -- 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 Released Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Fix Released 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
[Desktop-packages] [Bug 1904547] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_get_panel_orientation_managed() from reset_current_config() from on_screen_changed() from on_screen_
** Changed in: gnome-control-center Status: New => 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/1904547 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_get_panel_orientation_managed() from reset_current_config() from on_screen_changed() from on_screen_changed() from g_closure_invoke() Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center package in Debian: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.38.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/22eb073fed09f6a2f9f5ff9bd4b2677ea9b8336f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1904547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 Mantic) 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 Released 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 2038907] Re: Ubuntu patch incorrect disable the thunderbolt and security panels
Noble also has 1:45.0-1ubuntu3, with the same fix. This all started before noble was released, hence the version collision, but I'm pretty sure that throughout the devel cycle, noble will get a gnome-control- center version bump, so no harm in releasing mantic with this version now. -- 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 Released 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 2038907] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to 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 Released 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 2043609] Re: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK.
I could reproduce it. The old installer makes use of the time zone location to "guess" the desired locale, but that is apparently not the case with the flutter based installer (at least not for the English variants). There is a similar issue reported at GitHub: https://github.com/canonical/ubuntu-desktop-installer/issues/2386 ** Bug watch added: github.com/canonical/ubuntu-desktop-installer/issues #2386 https://github.com/canonical/ubuntu-desktop-installer/issues/2386 ** Summary changed: - 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. + 24.04 install with a British timezone location sets en_US.UTF-8 locale ** Package changed: gnome-control-center (Ubuntu) => ubuntu-desktop- installer ** Changed in: ubuntu-desktop-installer Importance: Undecided => High ** Changed in: ubuntu-desktop-installer Status: Incomplete => Confirmed -- 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/2043609 Title: 24.04 install with a British timezone location sets en_US.UTF-8 locale Status in ubuntu-desktop-installer: Confirmed Bug description: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:45.0-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 18:17:48 2023 InstallationDate: Installed on 2023-11-15 (0 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231115.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043716] [NEW] Desktop freezing and slowing down when multiple apps running
Public bug reported: This machine is being used a lot to cast to Chromecast using Chromium. Some days Chromium is regularly freezing every 10 minutes or so. It is necessary to restart the computer to get casting again. Regularly, the freeze causes the "force close" or "wait" pop up to appear. If I am quick to react, I can quit Chromium and a reboot gets things going again. But if I am too slow, sometimes the whole desktop freezes including the mouse and I need to Alt-SysRq+B. If I am casting and during a boring bit I want to check my emails, then running Thunderbird causes the whole system to slow down, and the casting to reduce resolution and only update the screen every 10 seconds or so. Please let me know if there is anything I can do to help diagnose the problem. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10.1-lowlatency 6.5.3 Uname: Linux 6.5.0-10-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 16 17:52:42 2023 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-11-06 (10 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2043716 Title: Desktop freezing and slowing down when multiple apps running Status in gnome-shell package in Ubuntu: New Bug description: This machine is being used a lot to cast to Chromecast using Chromium. Some days Chromium is regularly freezing every 10 minutes or so. It is necessary to restart the computer to get casting again. Regularly, the freeze causes the "force close" or "wait" pop up to appear. If I am quick to react, I can quit Chromium and a reboot gets things going again. But if I am too slow, sometimes the whole desktop freezes including the mouse and I need to Alt-SysRq+B. If I am casting and during a boring bit I want to check my emails, then running Thunderbird causes the whole system to slow down, and the casting to reduce resolution and only update the screen every 10 seconds or so. Please let me know if there is anything I can do to help diagnose the problem. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10.1-lowlatency 6.5.3 Uname: Linux 6.5.0-10-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 16 17:52:42 2023 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-11-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
** Changed in: mesa (Ubuntu Noble) Status: Confirmed => 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/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Mantic: New Status in mesa source package in Noble: Fix Released Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
It also works properly on mine now -- 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/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Committed Status in libreoffice source package in Jammy: Fix Released Status in snapd source package in Jammy: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
Setting network-manager back to confirmed as I think the case is made that this is an issue, despite upstream having reservations about whether network-manager is quite the right place for this particular setting. Also setting netplan.io in jammy to fix released as 0.105 was back-ported there quite a while ago now and the current (22.04.3) image should support setting this at first-boot. Setting kinetic to won't fix (as it's EOL). ** Changed in: network-manager (Ubuntu Kinetic) Status: Incomplete => Won't Fix ** Changed in: network-manager (Ubuntu Jammy) Status: Incomplete => Confirmed ** Changed in: network-manager (Ubuntu) Status: Incomplete => Confirmed ** Changed in: netplan.io (Ubuntu Jammy) Status: Triaged => Fix Released ** Changed in: netplan Assignee: Lukas Märdian (slyon) => (unassigned) ** Also affects: network-manager (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Noble) Importance: Low Status: Confirmed ** Also affects: netplan.io (Ubuntu Noble) Importance: Medium Status: Fix Released ** Also affects: network-manager (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu Lunar) Status: New => Fix Released ** Changed in: netplan.io (Ubuntu Mantic) Status: New => Fix Released ** Changed in: network-manager (Ubuntu Lunar) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu Lunar) Status: New => Confirmed ** Changed in: network-manager (Ubuntu Mantic) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu Mantic) Status: New => Confirmed -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Confirmed Status in netplan.io source package in Jammy: Fix Released Status in network-manager source package in Jammy: Confirmed Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Won't Fix Status in netplan.io source package in Lunar: Fix Released Status in network-manager source package in Lunar: Confirmed Status in netplan.io source package in Mantic: Fix Released Status in network-manager source package in Mantic: Confirmed Status in netplan.io source package in Noble: Fix Released Status in network-manager source package in Noble: Confirmed Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
This would appear to be fixed on my jammy system. Any objections to marking this fix released? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Committed Status in libreoffice source package in Jammy: Fix Released Status in snapd source package in Jammy: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1432599]
When an interface is configured outside of NetworkManager's knowledge (like libvirt's or docker's bridge), then NetworkManager generates an in-memory connection profile and pretends(!) that this is active. This is to show that something is going on with the device, and NetworkManager is supposed to touch that device. Whether this pretend mode is of any use is a good question. It's obviously confusing. I actually do make use of this behaviour to have a dispatcher script that does something for such external devices, so it's not entirely useless. Also, it causes the output of `nmcli device` to show that *something* is going on there. Although, maybe that's more confusing than helpful. In any case, NetworkManager needs a way to express that something is happening with this devices, and this is the way it does that. It doesn't mean that NetworkManager actually touches the device. Comment 26 does not say what actual problem NetworkManager causes by this (aside the confusion to the user). Comment 26 also explains that `nm-online` gives wrong results. I think nm-online has one real use-case: to implement `NetworkManager-wait-online.service` (with the `--startup` option). Without the `--startup` option, I don't think it's of any use at all. It can only return "online" or "offline". It maps the NetworkManager's states "local", "site", and "global" to "online". I think that is is sensible, if you connect to a libvirt bridge some network is configured and nm-online considers that as "online". However I don't think that describing the online state in two words is meaningful and calling `nm-online` is not useful. For a while NetworkManager had a udev rule to automatically unmanage docker bridges. But that was dropped, because docker bridges are nothing special. It's a common thing that something aside NetworkManager configures an interface and NetworkManager must not interfere. So, what actual problems are causes by this? --- > 1) You should never need to create (actually *shouldn't* create) an ifcfg-* > file for a libvirt-created bridge. If proper operation requires this, then > there is definitely a bug. Right. NM doesn't. > 2) NetworkManager should never mess around with bridge devices created by other entities (e.g. libvirt, but really anyone else), and no special plugin should be required to make that happen. If we (libvirt) wanted NM to manage the bridge, we would create it via NM. Right. NM shouldn't. Does it? -- 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/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Fedora: Won't Fix Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1432599]
In previous versions of GNOME (such as the version in RHEL 7.6), an active NetworkManager connection profile for virbr0 caused a wired Ethernet connection to appear in the top bar in GNOME Shell. It seems this is actually now suppressed, and GNOME Control Center does not expose the virbr0 device on the network panel (or allow it to be configured there). For users who are looking to check if a NetworkManager connection profile is active excluding libvirt's, disabling NetworkManager's control of the bridge devices still seems to me like an appropriate method to adjust the behavior of nm-online. I'm not sure I agree with the comment about *never* using ifcfg: the configuration I provided above is equivalent to setting "unmanaged-devices=interface-name:virbr0" in /etc/NetworkManager/NetworkManager.conf. It is read by NetworkManager's ifcfg-rh settings plugin, versus NetworkManager's keyfile settings plugin. It's also worth mentioning that libvirt allows hook scripts to be run when a virtual network switch is started/stopped, which can substitute for NetworkManager dispatcher scripts for these devices: https://libvirt.org/hooks.html -- 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/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Fedora: Won't Fix Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1432599]
This has remained reproducible in every release from Fedora 23 through Fedora 30 -- the problem never went away (and the underlying reason/behavior never changed). Please re-open against Fedora 30. This occurs in Fedora Workstation when it is installed to disk. The behavior can be very easily seen by booting the Fedora Workstation live image, without any wired or wireless network connections. (However the missing 'libvirt-daemon-config-network' package needs to be installed from local storage after boot, except on Fedora 23 and Fedora 26 where this is already present.) [liveuser@localhost ~]$ nmcli connection NAMEUUID TYPEDEVICE virbr0 f20e2384-0dca-4a6b-b4cb-3dd1582c1ce1 bridge virbr0 [liveuser@localhost ~]$ nm-online Connecting... 30s [online] This is (falsely) indicating that "the network is connected", as described in nm-online(1). Configuring NetworkManager to not manage virbr0 still works around this: [liveuser@localhost ~]$ cat > ifcfg-virbr0 << EOF > DEVICE=virbr0 > NM_CONTROLLED=no > EOF [liveuser@localhost ~]$ sudo cp ifcfg-virbr0 /etc/sysconfig/network-scripts/ [liveuser@localhost ~]$ rm ifcfg-virbr0 [liveuser@localhost ~]$ sudo nmcli connection reload [liveuser@localhost ~]$ nmcli connection [liveuser@localhost ~]$ nm-online Connecting...0s [offline] But this should be an automatic setting, not a manual one. We already know that the explicit configuration of this interface is handled by libvirt (see /etc/libvirt/qemu/networks/default.xml), and NetworkManager should not be managing it and potentially changing its state. However this more generally applies to any virtual network switch created with libvirt though, whether or not it is named virbr0. Which package should contain the hooks to do this? Should NetworkManager be able to identify a libvirt network switch, or should libvirt configure NetworkManager (perhaps using a separate settings plugin) to not manage its devices? -- 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/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Fedora: Won't Fix Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1432599]
(NB: I'm a libvirt developer, so I'm writing this comment from that POV) 1) You should never need to create (actually *shouldn't* create) an ifcfg-* file for a libvirt-created bridge. If proper operation requires this, then there is definitely a bug. 2) NetworkManager should never mess around with bridge devices created by other entities (e.g. libvirt, but really anyone else), and no special plugin should be required to make that happen. If we (libvirt) wanted NM to manage the bridge, we would create it via NM. People normally don't see the issue you describe, because almost everybody has a permanently online internet connection these days, but I can see why it would be problematic. Since this behavior has been present in NM for such a long time, I would say that the proper place for the bug to be filed would be upstream rather than in Fedora. I don't know if the NM developers pay more attention to their mailing list, or to their issue tracker on gitlab.freedesktop.org. -- 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/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Fedora: Won't Fix Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2032852] Re: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common
Hi! Excuse my poor English! Same problem than mike cooper (18.04 to 20.04). I did what mike cooper wrote and his suggestion works very good (I don't reboot)! Thanks Mike! -- 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/2032852 Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice- common Status in libreoffice package in Ubuntu: Confirmed Status in libreoffice source package in Focal: In Progress Bug description: package install error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 24 02:36:52 2023 ErrorMessage: conflicting packages - not installing libreoffice-common InstallationDate: Installed on 2023-08-22 (1 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: libreoffice Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2032852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007702] Re: Deb version numbering is misleading
I have uploaded this and unsubscribed ubuntu-sponsors. Please feel free to resubscribe if you have anything else that needs to be sponsored. ** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Committed -- 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/2007702 Title: Deb version numbering is misleading Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... This might make one think[1][2] that it will install a critically outdated Chromium while it does not, because it installs the snap. [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 [2] https://askubuntu.com/q/1420925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Hi Paride, after more than 24 hours running transmission-daemon from Andreas' PPA linked in #18, memory usage is only 300mb. More torrents than when my initial comment (#14) was posted, so I'd say it's fixed. Thanks to everyone who put the effort in to sort this out. -- 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 Status in transmission source package in Jammy: New Status in transmission source package in Lunar: New Status in transmission package in Debian: New 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 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
@xnox: > I thought 390 is so obsolete, that everyone has migrated to newer ones if their card supports it. Sadly I can't. I have 2 Thinkpads with this GPU (Core i7 T420, Core i7 W520) and it is built in -- it can't be replaced. If upstream has dropped it then there is little that can be done but a warning when I upgraded to Mantic would have been good! I got nothing, I just lost PRIME offload. Secondly, I feel it would be the Ubuntu spirit to automatically _remove_ the no-longer-supported driver and configure Nouveau instead. So far I have spent hours on this and cannot get it working. It is very frustrating indeed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-455 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp