[Desktop-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Still no fix or workaround? Having a fresh ubuntu 20.04 installed. nvidia 470.86 xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 5.11.0-43-generic HP zbook, G5. External monitor, Xorg high cpu load, external monitor random slow. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1956005] Re: Firefox Snap won't open links to WhatsApp API
** Attachment added: "open-in-firefox-option.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/+attachment/5550318/+files/open-in-firefox-option.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in firefox package in Ubuntu: New Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/+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 1956005] Re: Firefox Snap won't open links to WhatsApp API
Seems like the "Open in Firefox" option is missing for these links (see next attachment): -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in firefox package in Ubuntu: New Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/+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 1956005] Re: Firefox Snap won't open links to WhatsApp API
** Attachment added: "Pop up opened when clicking link to WhatsApp API" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/+attachment/5550316/+files/firefox-snap-whatsapp-links.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in firefox package in Ubuntu: New Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/+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 1956005] [NEW] Firefox Snap won't open links to WhatsApp API
Public bug reported: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Snap won't open Whatsapp API links + Firefox Snap won't open links to WhatsApp API ** Description changed: The .deb version of Firefox handles links to WhatsApp API - (https://api.whatsapp.com/send/?phone=) without any problem. + (https://api.whatsapp.com/send/?phone=) without any problem: these + links open the WhatsApp web client. - Snap version of Firefox opens the pop up "Choose an application to open - whatsapp lnks" that only shows System Handler (which fails if selected). - Choosing Firefox is not possible (/bin and similar folders are out of - range of the snap). + Snap version of Firefox doesn't know how to handle these links. It opens + the pop up "Choose an application to open whatsapp lnks" that only shows + the option System Handler (which fails opening them if selected). + + Choosing Firefox is not possible as /bin and similar folders are out of + range for the snap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in firefox package in Ubuntu: New Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/+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 1955998] [NEW] laptop doesn't wake after susopend/closed lid
Public bug reported: I installed Ubuntu 21.10 on my laptop (Lenovo Yoga Slim 14 ARE 05 - AMD Ryzen 4700 - 1§ GB RAM - 512 GB SSD). Every time I close the lid or let the laptop go to suspend the system doesn't resume. Clicking the mouse or pushing the keys doesn't resume the OS. The only way to resume is to hold the power button until the machine turns off and then reboot. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 29 18:36:27 2021 InstallationDate: Installed on 2021-12-29 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1955998 Title: laptop doesn't wake after susopend/closed lid Status in lightdm package in Ubuntu: New Bug description: I installed Ubuntu 21.10 on my laptop (Lenovo Yoga Slim 14 ARE 05 - AMD Ryzen 4700 - 1§ GB RAM - 512 GB SSD). Every time I close the lid or let the laptop go to suspend the system doesn't resume. Clicking the mouse or pushing the keys doesn't resume the OS. The only way to resume is to hold the power button until the machine turns off and then reboot. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 29 18:36:27 2021 InstallationDate: Installed on 2021-12-29 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1955998/+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 1955996] [NEW] gnome-shell uses excessive memory
Public bug reported: I leave my computer running for days at a time. I noticed that gnome- shell was using something like 8-gigs of memory. I just kill the process on a regular basis. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 29 10:20:23 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-22 (706 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-19 (70 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1955996 Title: gnome-shell uses excessive memory Status in gnome-shell package in Ubuntu: New Bug description: I leave my computer running for days at a time. I noticed that gnome- shell was using something like 8-gigs of memory. I just kill the process on a regular basis. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 29 10:20:23 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-22 (706 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-19 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955996/+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 1946525] Re: Removable media are not mounted automatically
** Description changed: 1) Ubuntu Desktop amd 64 20211008.1 daily build - 2) udisks 2.9.4-1 + 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: - Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet - Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M - |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1946525 Title: Removable media are not mounted automatically Status in udisks2 package in Ubuntu: Confirmed Bug description: 1) Ubuntu Desktop amd 64 20211008.1 daily build 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+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 1955982] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build: After upgrading to new kernel and back to old one I see the message about error bu
Public bug reported: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build: After upgrading to new kernel and back to old one I see the message about error but I do not notice any sympthoms. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-43-generic Date: Tue Dec 28 17:10:06 2021 InstallationDate: Installed on 2021-09-24 (95 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1955982 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build: After upgrading to new kernel and back to old one I see the message about error but I do not notice any sympthoms. Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build: After upgrading to new kernel and back to old one I see the message about error but I do not notice any sympthoms. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-43-generic Date: Tue Dec 28 17:10:06 2021 InstallationDate: Installed on 2021-09-24 (95 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1955982/+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 1955981] [NEW] pieces of text not printed at all
Public bug reported: When I try to print the pdf from https://ukestuff.files.wordpress.com/2021/12/beginners-guide-to-playing-chord-melodies.pdf some pages are not printed correctly, some pieces of text are completely missing from the page - some are just blank, some look like deleted (the text that follows is shifted left). I can reproduce this with evince and atril. The pdf prints fine from okular and firefox. This is happening with pages 13 and onward of this file, even when trying to print them one by one. E.g. in the attached photo, left is page 14 printed from evince, right is printed from okular. Note the missing letters TAB, missing note numbers, missing pause character on line 3 and deleted song name before the words 'was a 1957 hit'. atril 1.24.0 (Using poppler/cairo (0.86.1) and SyncTeX 1.21) evince 3.36.10 okular 1.9.3 Firefox 95.0.1 The printer is Brother HL1110. ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Attachment added: "photo" https://bugs.launchpad.net/bugs/1955981/+attachment/5550256/+files/JPEG%20image%203.jpeg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1955981 Title: pieces of text not printed at all Status in evince package in Ubuntu: New Bug description: When I try to print the pdf from https://ukestuff.files.wordpress.com/2021/12/beginners-guide-to-playing-chord-melodies.pdf some pages are not printed correctly, some pieces of text are completely missing from the page - some are just blank, some look like deleted (the text that follows is shifted left). I can reproduce this with evince and atril. The pdf prints fine from okular and firefox. This is happening with pages 13 and onward of this file, even when trying to print them one by one. E.g. in the attached photo, left is page 14 printed from evince, right is printed from okular. Note the missing letters TAB, missing note numbers, missing pause character on line 3 and deleted song name before the words 'was a 1957 hit'. atril 1.24.0 (Using poppler/cairo (0.86.1) and SyncTeX 1.21) evince 3.36.10 okular 1.9.3 Firefox 95.0.1 The printer is Brother HL1110. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1955981/+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 1853977] Re: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty
+1 I think this is the root bug/problem though --> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-340/+bug/1916640 This PPA solved it for me https://launchpad.net/~kelebek333/+archive/ubuntu/nvidia-legacy/+packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1853977 Title: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Hello, When installing `nvidia-340` there is an error is the postinst script: philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340 Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to upgrade. Need to get 0 B/51.9 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 309892 files and directories currently installed.) Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ... Stopping nvidia-persistenced nvidia-persistenced: no process found Done. (snip) Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-340-340.107 DKMS files... Building for 4.15.0-70-generic Building for architecture x86_64 Building initial module for 4.15.0-70-generic Done. The comment at https://askubuntu.com/questions/969352/uninstalling- and-then-reinstalling-nvidia-384-kills-colord tells us that /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853977/+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
