[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap
Changing the printerdriver from driverless to a selected Cups driver for the printermodell solved the issue on my end. It seems that snaps that are not using Cups-control are having trouble with connecting to printers using the driverless approach. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap
Here is the output as it is now after switching from driverless printing to a cups driver for my printer. lpstat -v Gerät für HP_Officejet_Pro_8610_2414BB: implicitclass://HP_Officejet_Pro_8610_2414BB/ Gerät für HP_Officejet_Pro_8610_2414BB@HPFC3FDB2414BB.local: implicitclass://HP_Officejet_Pro_8610_2414BB%40HPFC3FDB2414BB.local/ lpstat -p Drucker HP_Officejet_Pro_8610_2414BB ist im Leerlauf. Aktiviert seit Mo 03 Jul 2023 15:10:43 CEST Drucker HP_Officejet_Pro_8610_2414BB@HPFC3FDB2414BB.local ist im Leerlauf. Aktiviert seit Di 04 Jul 2023 16:40:45 CEST cups.lpstat -v device for HP_Officejet_Pro_8610_2414BB: proxy://%2Frun%2Fcups%2Fcups.sock/HP_Officejet_Pro_8610_2414BB device for HP_Officejet_Pro_8610_2414BB@HPFC3FDB2414BB.local: proxy://%2Frun%2Fcups%2Fcups.sock/HP_Officejet_Pro_8610_2414BB@HPFC3FDB2414BB.local cups.lpstat -p printer HP_Officejet_Pro_8610_2414BB is idle. enabled since Mon Jul 3 15:15:20 2023 printer HP_Officejet_Pro_8610_2414BB@HPFC3FDB2414BB.local is idle. enabled since Tue Jul 4 16:40:45 2023 snap list | grep cups cups2.4.6-1 962 latest/stable openprinting** - snap connections cups SchnittstellePlug Slot Notizen avahi-controlcups:avahi-control:avahi-control - cups chromium:cups cups:cups - cups-control - cups:cups-server - cups-control cups:cups-control :cups-control - home cups:home :home - network cups:network :network - network-bind cups:network-bind :network-bind - network-manager-observe cups:network-manager-observe :network-manager-observe - raw-usb cups:raw-usb :raw-usb - system-files cups:etc-cups :system-files - -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap
I fixed the problem myself by setting the printer up with a cupsdriver. Since my printer is connected to my LAN as a networkprinter it is using the default "driverless" setup that works out of the box after i install Kubuntu. It works for native apps and flatpaks as well. Applications installed as snap seem to be unable to detect the printer. This happens on three different systems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931765] Re: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)
At first i did not know that the problem was caused by the ppa. However i think that the MESA drivers should always be upgraded to the latest stable version. Ubuntu should handle the MESA packages like firefox. Ubuntu is the only officialy supported linuxdistribution supported by Steam for gaming and runs on outdated gpudrivers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1931765 Title: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston) Status in libva package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: SUMMARY VAAPI is broken on KDE Plasma Wayland and Weston Session STEPS TO REPRODUCE 1. Open a terminal 2. Type in vainfo OBSERVED RESULT Error Message: heiko@Tuxedobook:~$ vainfo wl_drm@6: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.10.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit EXPECTED RESULT Should show VAAPI information without errors like on X11 session This bug was reproduced multiple times on two systems one with an intel igpu and one with a dedicated AMD GPU. Both systems are using the MESA drivers from this ppa: https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa This bug was discovered because KODI Mediacenter was crashing on startup on wayland while it is working flawless on X11/X.org. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.22.0 ADDITIONAL INFORMATION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1931765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931765] Re: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)
Yes it works with the MESA packages from the ubunturepos. The problem occurs after adding the kisak mesa fresh ppa and upgrading to the latest stable MESA release. It only happens when Wayland is used. I always use this otherwise great ppa to keep my MESA drivers up to date. Sadly the packages in the ubuntu are often to old if you use your system for gaming. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1931765 Title: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston) Status in libva package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: SUMMARY VAAPI is broken on KDE Plasma Wayland and Weston Session STEPS TO REPRODUCE 1. Open a terminal 2. Type in vainfo OBSERVED RESULT Error Message: heiko@Tuxedobook:~$ vainfo wl_drm@6: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.10.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit EXPECTED RESULT Should show VAAPI information without errors like on X11 session This bug was reproduced multiple times on two systems one with an intel igpu and one with a dedicated AMD GPU. Both systems are using the MESA drivers from this ppa: https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa This bug was discovered because KODI Mediacenter was crashing on startup on wayland while it is working flawless on X11/X.org. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.22.0 ADDITIONAL INFORMATION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1931765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931765] Re: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)
Are there any news related to the bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1931765 Title: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston) Status in libva package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: SUMMARY VAAPI is broken on KDE Plasma Wayland and Weston Session STEPS TO REPRODUCE 1. Open a terminal 2. Type in vainfo OBSERVED RESULT Error Message: heiko@Tuxedobook:~$ vainfo wl_drm@6: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.10.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit EXPECTED RESULT Should show VAAPI information without errors like on X11 session This bug was reproduced multiple times on two systems one with an intel igpu and one with a dedicated AMD GPU. Both systems are using the MESA drivers from this ppa: https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa This bug was discovered because KODI Mediacenter was crashing on startup on wayland while it is working flawless on X11/X.org. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.22.0 ADDITIONAL INFORMATION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1931765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp