Re: [Desktop-packages] [Bug 2022897] [NEW] package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to install/upgrade: podproces nowy pakiet chromium-browser skrypt pre-installation zwrócił ko
Hi Luke Skywalker, Judging by the error message, it looks like your snapd is out of date. Can you please open a terminal and share the output of "snap info snapd"? You can also try "snap refresh snapd" to update it. May the force be with you. -- 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/2022897 Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to install/upgrade: podproces nowy pakiet chromium-browser skrypt pre- installation zwrócił kod błędu 1 Status in chromium-browser package in Ubuntu: New Bug description: during : sudo apt upgrade i receive: Errors occured during proceeding: /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 5 09:26:42 2023 Dependencies: ErrorMessage: podproces nowy pakiet chromium-browser skrypt pre-installation zwrócił kod błędu 1 InstallationDate: Installed on 2023-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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: chromium-browser Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to install/upgrade: podproces nowy pakiet chromium-browser skrypt pre-installation zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2022897/+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 2022897] Re: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to install/upgrade: podproces nowy pakiet chromium-browser skrypt pre-installation zwrócił kod błęd
No problem at all, happy journey to Linux! ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- 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/2022897 Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to install/upgrade: podproces nowy pakiet chromium-browser skrypt pre- installation zwrócił kod błędu 1 Status in chromium-browser package in Ubuntu: Invalid Bug description: during : sudo apt upgrade i receive: Errors occured during proceeding: /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 5 09:26:42 2023 Dependencies: ErrorMessage: podproces nowy pakiet chromium-browser skrypt pre-installation zwrócił kod błędu 1 InstallationDate: Installed on 2023-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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: chromium-browser Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to install/upgrade: podproces nowy pakiet chromium-browser skrypt pre-installation zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2022897/+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 2022073] Re: Font/Character Rendering Issue
Hi Chris, thanks for the bug report. The attached file is not actually a PNG (it is identified as "Paint.NET image data") and I cannot open it, could you please upload a new one in a common format? Could you share address of the affected web site and see if you get something either in the journal, i.e., journalctl -f or in the Chromium log, chromium --enable-logging=stderr ? -- 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/2022073 Title: Font/Character Rendering Issue Status in chromium-browser package in Ubuntu: New Bug description: I've been building some single purpose kiosks using Ubuntu server on RaspberyPis (models 3 and 4). It's a minimal build that uses matchbox- window-manager and chromium in kiosk mode. Prior to 22.04 we had no issues (see 'correct font' link). Building new Pi images from a base 22.04 install I'm encountering these font issues. My process is pretty simple. We use the RaspberryPi Imager to create the base install, then update && upgrade. After that we have some scripts to install our packages and some configurations files to auto login and run our xinit script at the end of .bashrc to open the webpage. Everything is working fine except for this issue with the font. From what I can tell the specific font in the css of the webpage is not installed, but sans-serif is the fallback in the css code and that appears to be used, but it is just rendering wierd. Looking for similar issues online I have tried to refresh the font cache but not much else comes up. I've managed to install chrome (proper) from the debian stable repository and have no issues. This is not an ideal workaround due to other issues that will surely arise. I am attaching an image with 3 screen clips (2 buggy font renders and 1 correct from an older build that doesn't have this issue). ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: User Name 5.15.0-1029.31-raspi 5.15.98 Uname: Linux 5.15.0-1029-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Jun 1 09:41:58 2023 ImageMediaBuild: 20230217.1 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Snap: chromium 113.0.5672.126 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 5Error 2023-05-22T16:39:36-04:00 2023-06-01T09:18:39-04:00 Auto-refresh snaps "chromium", "snapd" 7Done2023-06-01T09:19:28-04:00 2023-06-01T09:20:47-04:00 Auto-refresh snap "chromium" SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2022073/+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
Re: [Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
> When will I see this fix in apt for Luna? See https://wiki.ubuntu.com/PhasedUpdates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact -- Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Test Case - 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. Other Info -- I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+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 2023365] [NEW] Window movement is delayed in screen share in Wayland
Public bug reported: In Wayland, - Open Chromium or Firefox - Go to https://mozilla.github.io/webrtc-landing/gum_test.html - Start full screen capture - Drag some windows around Expected: The movement of each window is reproduced in the screen cast smoothly and immediately. Observed: It takes a couple of seconds until each moved window's position is verified in the screen cast. The issue does not appear in Xorg. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 Date: Fri Jun 9 09:11:35 2023 InstallationDate: Installed on 2022-05-16 (388 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-01-17 (142 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland ** Attachment added: "Screencast from 2023-06-09 09-04-13.webm" https://bugs.launchpad.net/bugs/2023365/+attachment/5678751/+files/Screencast%20from%202023-06-09%2009-04-13.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023365 Title: Window movement is delayed in screen share in Wayland Status in mutter package in Ubuntu: New Bug description: In Wayland, - Open Chromium or Firefox - Go to https://mozilla.github.io/webrtc-landing/gum_test.html - Start full screen capture - Drag some windows around Expected: The movement of each window is reproduced in the screen cast smoothly and immediately. Observed: It takes a couple of seconds until each moved window's position is verified in the screen cast. The issue does not appear in Xorg. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 Date: Fri Jun 9 09:11:35 2023 InstallationDate: Installed on 2022-05-16 (388 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-01-17 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023365/+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 1991022] Re: [SRU] Service activation via Systemd socket
Hi, what exactly does restarting the session mean? I could verify whether that would work. Otherwise the behavior I observed is consistent with https://source.puri.sm/kop316/mmsd/-/issues/3. ** Bug watch added: source.puri.sm/kop316/mmsd/-/issues #3 https://source.puri.sm/kop316/mmsd/-/issues/3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Incomplete Status in speech-dispatcher source package in Kinetic: Incomplete Status in speech-dispatcher source package in Lunar: Incomplete Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Then, systemctl start --user speech-dispatcher.socket snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+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
Re: [Desktop-packages] [Bug 2023365] Re: Window movement is delayed in screen share in Wayland
I tried it again and could no longer reproduce it, so maybe it was. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023365 Title: Window movement is delayed in screen share in Wayland Status in mutter package in Ubuntu: Incomplete Bug description: In Wayland, - Open Chromium or Firefox - Go to https://mozilla.github.io/webrtc-landing/gum_test.html - Start full screen capture - Drag some windows around Expected: The movement of each window is reproduced in the screen cast smoothly and immediately. Observed: It takes a couple of seconds until each moved window's position is verified in the screen cast. The issue does not appear in Xorg. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 Date: Fri Jun 9 09:11:35 2023 InstallationDate: Installed on 2022-05-16 (388 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-01-17 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023365/+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 1991022] Re: [SRU] Service activation via Systemd socket
Yes, I can confirm that restarting the user session is enough. ** Description changed: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech- dispatcher. Note: Either the installed socket needs to be started manually to - function correctly or the system needs to be rebooted. + function correctly or the session must be restarted or the system needs + to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Then, - systemctl start --user speech-dispatcher.socket + systemctl start --user speech-dispatcher.socket #Or restart session or machine snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Incomplete Status in speech-dispatcher source package in Kinetic: Incomplete Status in speech-dispatcher source package in Lunar: Incomplete Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the t
[Desktop-packages] [Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
*** This bug is a duplicate of bug 1732482 *** https://bugs.launchpad.net/bugs/1732482 The problem is https://forum.snapcraft.io/t/how-to-expose-desktop-files- created-by-snaps-to-the-de. Probably duplicate of the there mentioned LP:1732482. I can confirm it is not a problem from Chromium PPA. ** No longer affects: gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 1732482 [snap] doesn't properly save desktop files for "create shortcuts" action -- 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/2007652 Title: [snap] PWA don't launch as applications, just another chromium window Status in chromium-browser package in Ubuntu: Confirmed Bug description: I have recently converted from deb to snap package of chromium and progressive web applications (PWAs) launch just as another window of chromium and are not recognized as separate application by the window manager (for example when switching using Super+Tab) or dock (grouped under chromium windows). This is either a regression of the snap package vs deb or ubuntu 20.04 vs ubuntu 18.04 (I am not able to differentiate between these two since both happened together). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+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 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
*** This bug is a duplicate of bug 1732482 *** https://bugs.launchpad.net/bugs/1732482 Thanks for the response, zwm. The desktop file is necessary for Gnome Shell to categorize the PWA as a different application — in its own tab group — instead of just another Chromium window. This bug is therefore a particular consequence of Chromium, as a snapped application, not being able create its own desktop files in the canonical paths. Do you agree with the reasoning? -- 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/2007652 Title: [snap] PWA don't launch as applications, just another chromium window Status in chromium-browser package in Ubuntu: Confirmed Bug description: I have recently converted from deb to snap package of chromium and progressive web applications (PWAs) launch just as another window of chromium and are not recognized as separate application by the window manager (for example when switching using Super+Tab) or dock (grouped under chromium windows). This is either a regression of the snap package vs deb or ubuntu 20.04 vs ubuntu 18.04 (I am not able to differentiate between these two since both happened together). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+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 2016972] Re: Chromium snap does not support Intel Raptor Lake (13th gen)
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/2016972 Title: Chromium snap does not support Intel Raptor Lake (13th gen) Status in chromium-browser package in Ubuntu: Fix Released Bug description: The Chromium snap does not support Intel Raptor Lake (13th gen). RPL support was added in Mesa version 22.2.0 and our snaps contain: • /snap/gnome-3-38-2004: Mesa version 21.2.6 • /snap/gnome-42-2204: Mesa version 22.2.5 So the way forward is to get the chromium snap to use gnome-42-2204 (right now Chromium uses 3-38-2004). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2016972/+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 1969141] Re: [snap] seccomp denials for syscall=312, 314, 330 on amd64
** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Low ** Tags added: log-noise -- 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/1969141 Title: [snap] seccomp denials for syscall=312,314,330 on amd64 Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: # Steps to reproduce 1) Install Chromium's snap snap install chromium 2) Monitor logs journalctl -o cat -f --grep chromium 3) Start Chromium journalctl will be filled with errors due to some syscalls not permitted by the seccomp policy, like those: Apr 14 11:18:14 sdeziel-lemur audit[1734639]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=1734639 comm="chrome" exe="/snap/chromium/1961/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=314 compat=0 ip=0x77ccfac2276d code=0x5 Apr 14 11:18:14 sdeziel-lemur audit[1734751]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=1734751 comm="chrome" exe="/snap/chromium/1961/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=312 compat=0 ip=0x7a9d5be7f76d code=0x5 Apr 14 11:18:14 sdeziel-lemur audit[1734790]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=1734790 comm="chrome" exe="/snap/chromium/1961/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=330 compat=0 ip=0x735f8ecd303b code=0x5 # Additional information $ uname -a Linux sdeziel-lemur 5.13.0-39-generic #44~20.04.1-Ubuntu SMP Thu Mar 24 16:43:35 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 100.0.4896.88 1961 latest/stable canonical✓ - $ snap connections chromium Interface PlugSlot Notes audio-playbackchromium:audio-playback :audio-playback - audio-record chromium:audio-record :audio-record- bluez chromium:bluez :bluez - browser-support chromium:browser-sandbox :browser-support - camerachromium:camera :camera manual content[gnome-3-38-2004] chromium:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gtk-3-themes] chromium:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes- content[sound-themes] chromium:sound-themes gtk-common-themes:sound-themes - cups-control chromium:cups-control :cups-control- desktop chromium:desktop:desktop - desktop-legacychromium:desktop-legacy :desktop-legacy - gsettings chromium:gsettings :gsettings - home chromium:home :home - joystick chromium:joystick :joystick - mount-observe chromium:mount-observe - - mpris - chromium:mpris - network chromium:network:network - network-bind chromium:network-bind :network-bind- network-manager chromium:network-manager- - openglchromium:opengl :opengl - password-manager-service chromium:password-manager-service - - personal-fileschromium:chromium-config :personal-files - pulseaudiochromium:pulseaudio - - raw-usb chromium:raw-usb- - removable-media chromium:removable-media :removable-media - screen-inhibit-controlchromium:screen-inhibit-control :screen-inhibit-control - system-files chromium:etc-chromium-browser-policies :system-files
[Desktop-packages] [Bug 1993562] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor
** Tags added: log-noise snap -- 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/1993562 Title: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor Status in chromium-browser package in Ubuntu: Fix Released Bug description: When starting chromium's snap, those messages are logged: $ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F snap.chromium.chromium audit: type=1400 audit(1666201583.608:610): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:611): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_name" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:612): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:613): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_version" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Chromium behaves OK but generates log pollution. Additional info: $ snap list chromium snapd Name Version RevTracking Publisher Notes chromium 106.0.5249.119 2136 latest/stable canonical✓ - snapd 2.57.4 17336 latest/stable canonical✓ snapd $ uname -rm 5.15.0-52-generic x86_64 $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993562/+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 1862262] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/sys_vendor and product_name
** Tags added: log-noise -- 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/1862262 Title: [snap] apparmor denials on /sys/devices/virtual/dmi/id/sys_vendor and product_name Status in chromium-browser package in Ubuntu: Fix Released Bug description: When starting chromium's snap, those messages are logged: Feb 6 12:34:17 foo kernel: [106190.836260] audit: type=1400 audit(1581010457.097:1372): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" pid=20044 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Feb 6 12:34:17 foo kernel: [106190.836401] audit: type=1400 audit(1581010457.097:1373): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/product_name" pid=20044 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Feb 6 12:34:17 foo chromium_chromium.desktop[20044]: [20191:20191:0206/123417.177438:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. Chromium seemingly behaves OK but possibly with reduced sandboxing? Additional info: $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: stable refresh-date: yesterday at 17:45 EST channels: stable:80.0.3987.87 2020-02-05 (1016) 160MB - candidate: 80.0.3987.87 2020-02-05 (1016) 160MB - beta: 80.0.3987.85 2020-02-04 (1014) 160MB - edge: 81.0.4040.5 2020-02-06 (1018) 161MB - installed: 80.0.3987.87(1016) 160MB - $ uname -a Linux simon-lemur 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862262/+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 1852362] Re: ColorManager/Avahi apparmor denials when selecting printer
** Tags added: log-noise -- 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/1852362 Title: ColorManager/Avahi apparmor denials when selecting printer Status in chromium-browser package in Ubuntu: New Bug description: Using 19.10 with the current snap, when clicking on printing and selecting a printer the journal gets apparmor denials about avahi and colormanager pid=915 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.Avahi.Server" member="ServiceBrowserNew" mask="send" name="org.freedesktop.Avahi" pid=24201 label="snap.chromium.chromium" peer_pid=935 peer_label="unconfined" pid=915 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/ColorManager" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.17" pid=24201 label="snap.chromium.chromium" peer_pid=1018 peer_label="unconfined" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1852362/+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 2017011] Re: [snap] unable to read /proc/pressure/{cpu, io, memory}
** Tags added: log-noise
--
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/2017011
Title:
[snap] unable to read /proc/pressure/{cpu,io,memory}
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
During normal operation, chromium wants to read
/proc/pressure/{cpu,io,memory} but is denied by the Apparmor policy:
$ journalctl -b0 -k --grep 'chromium.chromium' | grep -F
'name="/proc/pressure/'
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:817): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:818): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:819): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Note that simply starting the browser doesn't prompt it try and read
those files, you need to do something more involving like watching
Youtube for example.
Additional information:
$ snap list chromium core20
Name VersionRev Tracking Publisher Notes
chromium 112.0.5615.49 2424 latest/stable canonical✓ -
core2020230308 1852 latest/stable canonical✓ base
$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
$ uname -a
Linux sdeziel-lemur 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017011/+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 2006646] Re: hwacc branch builds that use minigbm will switch to software compositor on amd.
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/2006646 Title: hwacc branch builds that use minigbm will switch to software compositor on amd. Status in chromium-browser package in Ubuntu: Fix Released Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+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 2006966] Re: Missing flag causing lack of hardware encoding in hwacc build.
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/2006966 Title: Missing flag causing lack of hardware encoding in hwacc build. Status in chromium-browser package in Ubuntu: Fix Released Bug description: This is about the hwacc branch of snap-from-source package. The chromium 110 version of the build guide came with the instruction to add an additional flag when launching chromium: VaapiVideoDecodeLinuxGL This flag is not present in chromium.launcher of the beta branch of hwacc, causing hw acceleration to fail. This was caught by checkbox kivu run. I will make a merge request adding this flag. $ snap info chromium | grep installed installed: 110.0.5481.77-hwacc(2320) 174MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006966/+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 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: Fix Released Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+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 2000175] Re: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise
** Tags added: log-noise ** Changed in: chromium-browser (Ubuntu) Assignee: Bram Stolk (b-stolk) => (unassigned) -- 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/2000175 Title: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise Status in chromium-browser package in Ubuntu: Confirmed Bug description: # Issue description After installing chromium with hwacc (snap refresh chromium --channel latest/candidate/hwacc) I notice a lot of those new messages in dmesg: Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3297): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3298): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature_next.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Those 2 files do not exist in the host's filesystem: $ ls /etc/igfx_user_feature.txt /etc/igfx_user_feature_next.txt ls: cannot access '/etc/igfx_user_feature.txt': No such file or directory ls: cannot access '/etc/igfx_user_feature_next.txt': No such file or directory # Additional information $ uname -a Linux sdeziel-lemur 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ snap list chromium core20 snapd Name Version RevTrackingPublisher Notes chromium 107.0.5304.121-hwacc 2224 latest/candidate/… canonical✓ - core2020221123 1738 latest/stable canonical✓ base snapd 2.57.617883 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000175/+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 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/1987137 Title: Migrating chromium-browser to core22 has libwayland-client0 issues Status in chromium-browser package in Ubuntu: Fix Released Bug description: Following on an earlier bug report that related to simple core22 migration for chromium-browser, here is a blocker that I don't know how to deal with. After checking out the core22 branch from git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22 (which already contains the early, easy migration commits), doing a build eventually generates (snippet here): 2022-08-19 20:15:05.809 :: In file included from ../../third_party/wayland/src/src/wayland-client.h:40: 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct wl_proxy *) wl_display, 2022-08-19 20:15:05.809 ::^ 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct wl_proxy *) wl_display, 2022-08-19 20:15:05.810 ::^ 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct wl_proxy *) wl_registry, 2022-08-19 20:15:05.810 :: ^ 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct wl_proxy *) wl_compositor, and lots more of the same; it seems pretty clear that the relevant wayland library is simply not new enough, and I don't know what to add/modify to add core22 support to the mix, so I am open to suggestions. I do notice the file parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json, which contains package version manifests for various distros, but not Ubuntu 22.04, so I'm *guessing* that might need enhancement. But that's just a guess. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+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 1971043] Re: GetVSyncParametersIfAvailable() failed
This originates from Brave. If someone can reproduce in Chromium please leave a comment saying so. Also it would be helpful for importance triaging to know how this affects the usability of the browser. ** Summary changed: - There are 2 errors. + GetVSyncParametersIfAvailable() failed ** Tags added: brave -- 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/1971043 Title: GetVSyncParametersIfAvailable() failed Status in chromium-browser package in Ubuntu: Confirmed Bug description: [19708:19708:0430/182408.372175:ERROR:object_proxy.cc(623)] Failed to call method: org.gnome.ScreenSaver.GetActive: object_path= /: org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/” [19754:19754:0430/182417.304932:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [19754:19754:0430/182420.489586:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [19754:19754:0430/182420.497097:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 30 18:22:41 2022 DistUpgraded: 2022-04-22 10:11:58,416 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd CoffeeLake-S GT2 [UHD Graphics 630] [1458:d000] InstallationDate: Installed on 2021-10-01 (211 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2357:0108 TP-Link TL-WN822N Version 4 RTL8192EU Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B365M GAMING HD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=bf34d45c-f034-4c70-b408-388da5fb2f59 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-04-22 (8 days ago) dmi.bios.date: 09/05/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: B365M GAMING HD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd09/05/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnB365MGAMINGHD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MGAMINGHD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B365M GAMING HD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+22.04.20211217-0ubuntu2 version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1971043/+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 1967827] Re: Screen Keyboard does not open when entering an input field
** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Critical -- 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/1967827 Title: Screen Keyboard does not open when entering an input field Status in chromium-browser package in Ubuntu: Confirmed Bug description: The screen keyboard does not display when using the touchscreen to input into a text input field on Chromium (e.g. Search Bar and Address Bar) or Chrome. This makes these browsers unusable on a tablet without an external keyboard. In addition there is no way to manually bring up the screen keyboard e.g. by placing a button on the address bar or panel. The Firefox browser, files and settings all invoke the touchscreen keyboard when pressing into a text input field and work as expected. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Chromium: Version 100.0.4896.60 ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 06:51:40 2022 InstallationDate: Installed on 2022-04-02 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Snap: chromium 100.0.4896.60 (latest/stable) Snap.Changes: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967827/+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 1967488] Re: Chromium stable snap don't work on Wayland (NVIDIA 510.60.02 driver)
** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Critical -- 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/1967488 Title: Chromium stable snap don't work on Wayland (NVIDIA 510.60.02 driver) Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+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 1967175] Re: Righ click on links menu doesn't render 99.0.4844.84
Is this still reproducible? ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High -- 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/1967175 Title: Righ click on links menu doesn't render 99.0.4844.84 Status in chromium-browser package in Ubuntu: New Bug description: snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 3 days ago, at 10:51 EEST channels: latest/stable:99.0.4844.84 2022-03-26 (1945) 141MB - latest/candidate: 99.0.4844.84 2022-03-26 (1945) 141MB - latest/beta: 100.0.4896.46 2022-03-18 (1943) 137MB - latest/edge: 101.0.4951.7 2022-03-28 (1947) 139MB - installed: 99.0.4844.84 (1945) 141MB - lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 Right clicking web links with text or link buttons is expected to open a menu. However the right click menu doesn't render. Instead right clicking opens a black background (without any text/shape). Right clicking link with plain image works (https://askubuntu.com/) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967175/+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 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
*** This bug is a duplicate of bug 1732482 *** https://bugs.launchpad.net/bugs/1732482 I'm posting what I've learned so far but there is still much to figure. > In the comment #5 you mention window classes as a way to do this feat. The desktop file seems like a possible way to launch Chromium with a specific window class which makes it a separate application. Is this a correct deduction? I messed up when transcribing the output for comment #5. I'm editing it to fix it. Bottom line is: The classes are the same in Bionic/deb as well (as the attached image shows), nonetheless the PWA does fall into a different tab group. Still in Bionic/deb, if I change StartupWMClass (regardless of matching --app-id) in the desktop file though, then the unwanted behavior (PWA grouped under Chromium) is observed if the application is opened from inside Chromium, whereas trying the launcher itself fails to open the PWA and only opens normal Chromium. So it just knows and needs to be launched with the registered app-id, and Gnome Shell will expect that as its class. Back to the snap world, same observations apply, except that snap cannot write to the a canonical XDG_DATA_DIR ($HOME/.local/share/applications) and thus Gnome Shell is oblivious. But if I try cp ~/snap/chromium/current/*/*.desktop ~/.local/share/applications then I **can open the PWA from the dock and it behaves as a separate application indeed**, but not if opened from inside Chromium, and their classes do diverge in the success case: ---> $ wmctrl -lx #Opened from dock item, different classes 0x01a00020 0 xterm.XTerm canonical xterm 0x01c3 0 chromium.Chromium canonical Neuer Tab - Chromium 0x0283 0 crx_mdpkiolbdkhdjpekfbkbmhigcaggjagi.Chromium-browser canonical Google Chat - Chat $ wmctrl -lx #Opened from inside Chromium, same classes 0x01a00020 0 xterm.XTerm canonical xterm 0x01c3 0 chromium.Chromium canonical Neuer Tab - Chromium 0x01c00015 0 crx_mdpkiolbdkhdjpekfbkbmhigcaggjagi.Chromium canonical Google Chat - Chat <--- Also, as noted elsewhere, the path to the executable registered in the desktop file points unfortunately to the unsandboxed binary, namely /snap/chromium/2497/usr/lib/chromium-browser/chrome. ** Attachment added: "PWA from Chromium deb in Bionic" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+attachment/5682104/+files/qemu-bionic.png -- 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/2007652 Title: [snap] PWA don't launch as applications, just another chromium window Status in chromium-browser package in Ubuntu: Confirmed Bug description: I have recently converted from deb to snap package of chromium and progressive web applications (PWAs) launch just as another window of chromium and are not recognized as separate application by the window manager (for example when switching using Super+Tab) or dock (grouped under chromium windows). This is either a regression of the snap package vs deb or ubuntu 20.04 vs ubuntu 18.04 (I am not able to differentiate between these two since both happened together). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+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 1967175] Re: Righ click on links menu doesn't render 99.0.4844.84
Thanks for giving it a shot again, your contribution is much appreciated. ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released ** Summary changed: - Righ click on links menu doesn't render 99.0.4844.84 + Right click on links menu doesn't render 99.0.4844.84 -- 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/1967175 Title: Right click on links menu doesn't render 99.0.4844.84 Status in chromium-browser package in Ubuntu: Fix Released Bug description: snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 3 days ago, at 10:51 EEST channels: latest/stable:99.0.4844.84 2022-03-26 (1945) 141MB - latest/candidate: 99.0.4844.84 2022-03-26 (1945) 141MB - latest/beta: 100.0.4896.46 2022-03-18 (1943) 137MB - latest/edge: 101.0.4951.7 2022-03-28 (1947) 139MB - installed: 99.0.4844.84 (1945) 141MB - lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 Right clicking web links with text or link buttons is expected to open a menu. However the right click menu doesn't render. Instead right clicking opens a black background (without any text/shape). Right clicking link with plain image works (https://askubuntu.com/) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967175/+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 1991022] Re: [SRU] Service activation via Systemd socket
I installed 0.11.1-1ubuntu3 from jammy-proposed and the snap[5] in a Jammy virtual machine, logged out, logged in, opened Pavucontrol, ran snap run --shell geheim XDG_RUNTIME_DIR=/run/user/1000 spd-say hi and verified that the volume indicator in Pavucontrol moved right after issuing the command. [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Status in speech-dispatcher source package in Kinetic: Fix Committed Status in speech-dispatcher source package in Lunar: Fix Committed Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the session must be restarted or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Restart the user session so the new systemd unit gets activated. Then, snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+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 1991022] Re: [SRU] Service activation via Systemd socket
Verified in Lobster (0.11.4-2ubuntu0.1) and Kinetic (0.11.3-1ubuntu1.1) that the test case produces sound. ** Tags removed: verification-needed verification-needed-kinetic verification-needed-lunar ** Tags added: verification-done verification-done-kinetic verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Status in speech-dispatcher source package in Kinetic: Fix Committed Status in speech-dispatcher source package in Lunar: Fix Committed Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the session must be restarted or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Restart the user session so the new systemd unit gets activated. Then, snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Removing chromium-browser as affected package because this wasn't actually verified on Chromium. If it is verified on Chromium, please revert that. ** No longer affects: chromium-browser (Ubuntu) -- 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/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+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 2025537] Re: chrome Check failed
*** This bug is a duplicate of bug 2017980 *** https://bugs.launchpad.net/bugs/2017980 ** This bug has been marked a duplicate of bug 2017980 Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) -- 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/2025537 Title: chrome Check failed Status in chromium-browser package in Ubuntu: Incomplete Bug description: local_slava@worksystem:~$ google-chrome [19394:19394:0701/201749.072306:FATAL:credentials.cc(127)] Check failed: . : Отказано в доступе (13) Trace/breakpoint trap (core dumped) How fix this? After update ubuntu... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025537/+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 2025526] Re: Printer is not available in chromium snap
Thanks for the bug report, Heiko. We do not have cups-control in Chromium. What is the output of 'snap connections chromium'? Is the cups one connected? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser 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/~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 2025526] Re: Printer is not available in chromium snap
It could be a problem in Chromium or Cups then. If you start Chromium from the command line with chromium --enable-logging=stderr |& tee chromium.log and work from there, do you see anything relevant in the output? If yes, please attach the generated log file to this bug report. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New ** Description changed: - 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 + 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" + 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 + flatpaks. ** Also affects: cups (Ubuntu) Importance: Undecided Status: New -- 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: New Status in cups package in Ubuntu: New 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/~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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
This problem should now be solved for Chromium (>=114.0.5735.198). Please confirm or deny it if you are a Chromium user previously affected by this bug. ** Description changed: Possible, proposed solutions Option 1: Please install from these channels and report back with success or failure. snap refresh --channel candidate/core22 firefox - snap refresh --edge chromium Option 2: - chromium --ozone-platform=wayland - MOZ_ENABLE_WAYLAND=1 firefox + chromium --ozone-platform=wayland + MOZ_ENABLE_WAYLAND=1 firefox If nothing works, it is possible around the issue by disabling hardware acceleration. Original bug report --- Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Good! Marking it as fixed then, thank you again for reporting back. ** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Released -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Possible, proposed solutions Option 1: Please install from these channels and report back with success or failure. snap refresh --channel candidate/core22 firefox Option 2: chromium --ozone-platform=wayland MOZ_ENABLE_WAYLAND=1 firefox If nothing works, it is possible around the issue by disabling hardware acceleration. Original bug report --- Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200
[Desktop-packages] [Bug 2025916] Re: command-chain ... not found
I think you had removed the gnome-42-2204 and this caused the interface not to connect. > sudo apt install snap --reinstall > sudo apt install snap --reinstall chromium You conflated snap[1] and snapd[2] in those instances. If your intention was to reinstall Chromium (and not snapd), then you could have used either of apt install --reinstall chromium snap remove chromium && snap install chromium [1] https://packages.ubuntu.com/mantic/snap [2] https://packages.ubuntu.com/mantic/snapd ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/2025916 Title: command-chain ... not found Status in chromium-browser package in Ubuntu: Incomplete Bug description: (I'm not familiar with snap, was migrated to it by *buntu for chromium-browser) Received the usual, well-know notification of having to snap refresh, some time given ... Closed chromium and issue the usual 'sudo snap refresh'. It went through, without any error indication. Restarting chromium failed, on the command line with $ chromium-browser Content snap command-chain for /snap/chromium/2529/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Using Firefox, after some Google I found and tried $ sudo apt install snap --reinstall ... The following NEW packages will be installed: snap And, no, I did not uninstall it. This is my work laptop, and I do only the basic and necessary system administration on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025916/+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 1563184] Re: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"
Is this still a problem? If yes, does the --disable-gpu flag help? -- 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/1563184 Title: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process" Status in chromium-browser package in Ubuntu: Confirmed Status in chromium-browser package in Arch Linux: Confirmed Bug description: crashes on startup with [2457:2457:0322/182419:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process Segmentation fault System ODROID XU3 armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
You mention snap update in the title. What specific snap are you referring to, Chromium, Cups or Snapd? The output of "snap changes" could be useful. If you roll it back with "snap revert ", does it work again? > Launching chrome from menu shortcut that is managed by the snap works > and it using this location /snap/bin/chromium > > Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome > Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Indeed, you should let the snap manage the shortcut, as the one you used in 20.04 invokes the binary directly, out of the snap sandbox. Do you get issues with that in place? Please attach the output of snap connections chromium snap connections cups ** Also affects: cups (Ubuntu) Importance: Undecided Status: New ** Changed in: cups (Ubuntu) Status: New => Incomplete ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
Thanks for the confirmation, but I don't yet know the context of the issue. Did you update from Bionic to Focal or did you simply notice the issue after the last Chromium update? Is there any problem when running 'chromium' from a terminal or is it a issue specific to the launcher? Please try to be as specific as possible, context is also very welcome. -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
Thank you very much for elaborating, that is much clearer. A couple of questions: 1. When you do not use /snap/chromium/current/usr/lib/chromium- browser/chrome, but rather chromium or /snap/bin/chromium, do you ever get those GLIBC errors? If not, what is the exact error you get? You mention permission denied, can you give me that full error message? Also, if you think the message is not clear enough, please try --enable- logging=stderr. 2. I have uploaded the older version to the stable/core20 channel, with which you can replace the current one: snap refresh --channel stable/core20 chromium Does that fix any of the issues you observed? As a matter of fact, I can reproduce the error when using the full unconfined path (/snap/chromium/current/usr/lib/chromium- browser/chrome), but that is discouraged and not supported. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Confirmed ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Confirmed Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
3. Please specify whether the errors are only observed for headless Chromium or if it is also observed for normal Chromium. ** Tags added: focal printing -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Confirmed Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
To be clear, the reason why this has hit you is that Chromium in the stable channel switched from Core20 in 114.0.5735.106 to Core22 in 114.0.5735.198 (this is a downstream, in other words Ubuntu maintainer's, decision, not Chromium's maintainers'). Core20 is a base from Ubuntu 20.04, while core22, from 22.04. As such, it makes sense that you had no library problems in Focal with the unconfined command (/snap/chromium/.../chrome) when Core20 was used — as the base and your system libraries were the same, they were compatible environments. Once Core22 is used to build, Chromium is linked against its libraries, and if you run the unconfined command in 20.04 now, it will find the host's GLIBC 2.31 instead of the base's 2.35; That aligns with the error messages. And that's why we discourage and cannot support unconfined runs. We are not tempted to switch back to Core20 — unless issues with the supported run (/snap/bin/chromium, snap run chromium or simply chromium) are found — because Core22 is the newer base, and actually solves bugs with hardware acceleration. I created the stable/core20 channel with the previous snap so you, the affected users, could confirm the switch was the cause and have time to adapt. But very importantly: This does not mean that we are going to actively maintain that new channel, so please don't rely on it for long term. -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Confirmed Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
Marcus, from what I gather, and correct me if I'm wrong, you were able to fix all your problems in your headless environment with Chromium edge. Not with Chromium stable? And hats off to you for responding to the proposed questions and investigating the issue. That was a great help and much appreciated! -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Confirmed Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Invalid -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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
Re: [Desktop-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
Am 07/07/2023 um 17:59 schrieb Michaelus: > ... by the Apache user, and, because APT forces the SNAP Chromium > package, rather than the standard Debian package, and because the Apache > user's (www-data) home directory is /var/www and not /home/www-data, one > cannot invoke Chromium via Apache at /snap/bin/chromium because of the > SNAP home directory requirement That is LP:1620771. > It is my opinion that IF Ubuntu 20.04 LTS (supported until April 2025) > is built with SNAP Core20, building a single Chromium SNAP on Core22 > going forward will continue to break Ubuntu 20.04 systems That invocation is not supported, so one could argue that it breaks unsupported setups. I say that although I appreciate that as per LP:1620771 that might currently have been the only way for you. > ... well, the fact that /snap/chromium/**current**/usr/lib/chromium- > browser/chrome (current) is a symlink to whatever build # is the > "current" suggests Chromium can/and-without-problems-should-be-able-to- > be called from that path (as it has been, until someone decided to make > the latest Chromium build against Core22) That's unfortunate because, in general, it cannot. Please feel free file a bug against snapd if you believe that should change, this one is mixed up with printing so it wouldn't be proper to target it to snapd as of now. > That, and the fact that there's no option to revert to a previous > Chromium build, is why this is "broken" There is, as for all snaps, with "snap revert", but that is indeed not at all a solution. > With respect, not "everyone and everything" is running on the "latest > and greatest" Sure, and I'm glad no one here holds that opinion. -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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
Re: [Desktop-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
I also appreciate your situation and I'm sorry this has been giving you a hard time. I'm happy to help with what I can. > 1. Is there any way we can influence where chromium looks for glibc to > find the base 2.35? (Is this something that would be resolved if I > could get /snap/bin/chromium working?) Not really. Yes, this would be resolved if you managed to get /snap/bin/chromium working. > 2. I still cannot get `chromium` or `/snap/bin/chromium` to work on any > of the versions, stable / edge / stable/core20. It reports the rather > unhelpful `cannot open path of the current working directory: Permission > denied` That could be some things, e.g. LP:1973321, LP:1620771. > Migrating to 22.04 is pretty much off the table for our situation as > 20.04 is still under lts and we have a _lot_ of other dependencies to > deal with. I'm also ok with opening a new ticket if you are set on > keeping this one closed. 20.04 is definitely supported and your experience should be as good as in 22.04; I'm sorry that is not the case. Please, if your problem isn't already covered in the ones I mentioned, do open a new ticket, this one is a bit mixed up. -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
-- Michaelus > you're saying invoking chromium via a fully qualified, real-path, with a SNAP-created symbolic link to a actual build directory, is a "unsupported setup" ? Yes, running a snap via /snap/chromium/current/usr/lib/chromium- browser/chrome is unsupported. (I don't know how you conclude that is a "symbolic link to a build directory" though.) -- Marcus I'm glad you solved all the issues that this update gave rise to and shared your solution with chromedriver. For what it's worth, yes, were you to find a problem with it, you would file a bug for chromium-browser. Thank you too for your superb cooperation and responsiveness. -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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
Re: [Desktop-packages] [Bug 2025916] Re: command-chain ... not found
That is currently a Snap shortcoming, there is no dependency enforcement like in Apt. So in general you'd really have to ask. :/ -- 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/2025916 Title: command-chain ... not found Status in chromium-browser package in Ubuntu: Incomplete Bug description: (I'm not familiar with snap, was migrated to it by *buntu for chromium-browser) Received the usual, well-know notification of having to snap refresh, some time given ... Closed chromium and issue the usual 'sudo snap refresh'. It went through, without any error indication. Restarting chromium failed, on the command line with $ chromium-browser Content snap command-chain for /snap/chromium/2529/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Using Firefox, after some Google I found and tried $ sudo apt install snap --reinstall ... The following NEW packages will be installed: snap And, no, I did not uninstall it. This is my work laptop, and I do only the basic and necessary system administration on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025916/+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
Re: [Desktop-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
> (I still maintain that if Ubuntu 20.04 LTS is supported until April > 2025, and its base SNAP is core20, it is not appropriate (if, only > because of my biased opinion) to build snaps on core22, which, you > admit, is the base snap core for Ubuntu 22.04) I think there is a misunderstanding here. Snaps for core22 can run in any series, be it 18.04, 20.04, 22.04 etc., otherwise it would really mean that for each series XX we would have to use the corresponding coreXX. They can only run in any series because they are not run directly as a binary that sees the host libraries, but rather uses snap confinment. So if your base is 20.04, a snap based on core22 works nonetheless, because it's seeing the libraries provided by core22 instead of your host system. That is _exactly_ what is sidestepped once you run it with the /snap/chromium/current/usr/lib/chromium-browser/chrome instead of the normal /snap/bin/chromium, namely the snap runs unconfined an thus uses the system libraries, which may be (and in the present case is) different than what it was linked it during its build, justifying the errors you see. > Do you have any sense of "how long" the stable/core20 channel will be > available? > > I am grateful for the stable/core20 build as of now, but need to plan to > either migrate to Ubuntu 22.04 (or later) or off Ubuntu altogether By default it's 30 days after launch, I'm happy to keep it alive for longer though if it will help, just note it is frozen, it will not be maintained, so new CVEs in Chromium or any of its dependent libraries won't be addressed and so on. -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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
Re: [Desktop-packages] [Bug 2025916] Re: command-chain ... not found
> I never installed gnome; and surely not with snap. That snap is just poorly named, it doesn't have only Gnome stuff, but also other snaps' dependencies, including e.g. Chromium. There is nothing surprising in the fact that it was refreshed though and as such gives no insight into the original problem. -- 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/2025916 Title: command-chain ... not found Status in chromium-browser package in Ubuntu: Incomplete Bug description: (I'm not familiar with snap, was migrated to it by *buntu for chromium-browser) Received the usual, well-know notification of having to snap refresh, some time given ... Closed chromium and issue the usual 'sudo snap refresh'. It went through, without any error indication. Restarting chromium failed, on the command line with $ chromium-browser Content snap command-chain for /snap/chromium/2529/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Using Firefox, after some Google I found and tried $ sudo apt install snap --reinstall ... The following NEW packages will be installed: snap And, no, I did not uninstall it. This is my work laptop, and I do only the basic and necessary system administration on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025916/+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 2027552] Re: package chromium-browser failed to install
Looks like the usual connection problem during installation. Please attach snap info chromium apt list --installed | grep chromium ls /var/lib/snapd/desktop/applications/chromium* ls /usr/share/applications -- 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/2027552 Title: package chromium-browser failed to install Status in chromium-browser package in Ubuntu: New Bug description: the package failed to launch. Afterwards I tried removing chromium via cli I got the response that the package is not installed (yet I can see the launch icon in the application menu). ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.15.0-76.83~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 12 09:55:47 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-18 (23 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) 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: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2027552/+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 2025916] Re: command-chain ... not found
** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Confirmed -- 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/2025916 Title: command-chain ... not found Status in chromium-browser package in Ubuntu: Confirmed Bug description: (I'm not familiar with snap, was migrated to it by *buntu for chromium-browser) Received the usual, well-know notification of having to snap refresh, some time given ... Closed chromium and issue the usual 'sudo snap refresh'. It went through, without any error indication. Restarting chromium failed, on the command line with $ chromium-browser Content snap command-chain for /snap/chromium/2529/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Using Firefox, after some Google I found and tried $ sudo apt install snap --reinstall ... The following NEW packages will be installed: snap And, no, I did not uninstall it. This is my work laptop, and I do only the basic and necessary system administration on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025916/+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 2025916] Re: command-chain ... not found
If it still shows up in "snap changes" (which at this point is
unfortunately unlikely), please get the ID for the refresh and share the
output of `snap change {ID}`.
--
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/2025916
Title:
command-chain ... not found
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
(I'm not familiar with snap, was migrated to it by *buntu for
chromium-browser)
Received the usual, well-know notification of having to snap refresh, some
time given ...
Closed chromium and issue the usual 'sudo snap refresh'. It went through,
without any error indication. Restarting chromium failed, on the command line
with
$ chromium-browser
Content snap command-chain for
/snap/chromium/2529/gnome-platform/command-chain/desktop-launch not found:
ensure slot is connected
Using Firefox, after some Google I found and tried
$ sudo apt install snap --reinstall
...
The following NEW packages will be installed:
snap
And, no, I did not uninstall it. This is my work laptop, and I do only
the basic and necessary system administration on it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025916/+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 2028547] Re: chromium snap: apparmor messages
Thanks for the report, Andreas. Other than the error messages, is there any observable misbehavior? I suppose one of them would be not respecting the Gnutls global configuration. You are using latest/edge/hwacc, correct? -- 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/2028547 Title: chromium snap: apparmor messages Status in chromium-browser package in Ubuntu: New Bug description: chromium 116.0.5845.32-hwacc 2551 latest/edge/… canonical** I'm getting a few apparmor DENIED messages with this snap on my lunar system: a) about /var/lib [68468.147326] audit: type=1400 audit(1690201352.140:586): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.chromium" name="/var/lib/" pid=38424 comm="5" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 b) about /etc/gnutls/config (which is a valid gnutls configuration file, just not shipped with the package, but users can create it, see [1]). I listed several messages because it's a different command in each [68468.312147] audit: type=1400 audit(1690201352.304:589): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/gnutls/config" pid=38507 comm="gio-querymodule" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [68468.312863] audit: type=1400 audit(1690201352.304:590): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/gnutls/config" pid=38506 comm="gdk-pixbuf-quer" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [68468.487025] audit: type=1400 audit(1690201352.480:591): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/gnutls/config" pid=38397 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [68476.836329] audit: type=1400 audit(1690201360.828:608): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/gnutls/config" pid=38801 comm="exe" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 c) /etc/vulkan/implicit_layer.d [68469.077529] audit: type=1400 audit(1690201353.068:595): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=38625 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 1. https://ubuntu.com/server/docs/gnutls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028547/+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 2028653] Re: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher)
** Changed in: chromium-browser (Ubuntu) Status: New => Triaged ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Critical -- 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/2028653 Title: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher) Status in chromium-browser package in Ubuntu: Fix Committed Bug description: There is error in line 143. Probably left over from git merge: === >>> hwacc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028653/+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 2028653] Re: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher)
Ouch... Thank you for the report. I committed the fix and while the new snap isn't finished building, I rolled back the edge snap to the previous version. ** 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/2028653 Title: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher) Status in chromium-browser package in Ubuntu: Fix Committed Bug description: There is error in line 143. Probably left over from git merge: === >>> hwacc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028653/+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
Re: [Desktop-packages] [Bug 2028711] [NEW] Feature Request: out-of-date browser notification
Hi Clinton, thanks for your suggestion. Chromium is a snap in Ubuntu, and as such, it automatically updates when the process is not running (and forcefully so after 15 days), so I do not understand the value of adding that. Upstream might consider it though, you can try a report in https://crbug.com/. -- 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/2028711 Title: Feature Request: out-of-date browser notification Status in chromium-browser package in Ubuntu: New Bug description: On the top right side of the Chromium tab bar, could you display the following red text watermark, if the browser is out-of-date: “This version is NOT secure. Update to stay secure.” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028711/+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 2028711] Re: Feature Request: out-of-date browser notification
** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- 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/2028711 Title: Feature Request: out-of-date browser notification Status in chromium-browser package in Ubuntu: Won't Fix Bug description: On the top right side of the Chromium tab bar, could you display the following red text watermark, if the browser is out-of-date: “This version is NOT secure. Update to stay secure.” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028711/+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
Re: [Desktop-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
As far as I know, Xvfb and --headless result in quite different environments, as the first will run in normal graphical mode and the latter won't. I see no reason why this would affect your extension packing, however I have no experience with extensions in Chromium. Could the graphical environment be playing a role here? Did you try the natural ---> xvfb-run /snap/bin/chromium --class="ChrUnsnapped" --pack-extension=MyExt --pack-extension-key=MyExt.pem <--- instead? The snap won't have access to the system's /tmp, but I think you can work around that, at least for the sake of testing. -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2028653] Re: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher)
For the record, currently only x64 has 117, as Launchpad builders are getting stuck. ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/2028653 Title: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher) Status in chromium-browser package in Ubuntu: Fix Released Bug description: There is error in line 143. Probably left over from git merge: === >>> hwacc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028653/+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
Re: [Desktop-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
Thanks for sharing your resuilts, David! -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript
** Changed in: chromium-browser (Ubuntu) Status: Won't Fix => Triaged ** Changed in: firefox (Ubuntu) Status: Won't Fix => Triaged ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- 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/2032992 Title: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Triaged Bug description: Steps to reproduce: 1) Install chromium snap snap install chromium 2) Install openjdk-21 documentation sudo apt install openjdk-21-doc 3) Browse API documentation chromium /usr/share/doc/openjdk-21-doc/api/index.html The search bar is inactive and dev console contains: jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND $ls -l /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js lrwxrwxrwx 1 root root 43 Mar 17 13:31 /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js -> ../../../../javascript/jquery/jquery.min.js cat /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js prints the file contents Downloaded version of chrome opens documentation with active search bar and no javascript errors /tmp/chrome/chrome /usr/share/doc/openjdk-21-doc/api/index.html Expected results: Chromium snap should be able to follow symlink into /usr/share/javascript and correctly load OpenJDK API documentation. Note: this probably should be a specific exclusion for Debian-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2032992/+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 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript
I proposed https://github.com/snapcore/snapd/pull/13130. ** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress ** Changed in: firefox (Ubuntu) Status: Triaged => In Progress -- 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/2032992 Title: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: In Progress Bug description: Steps to reproduce: 1) Install chromium snap snap install chromium 2) Install openjdk-21 documentation sudo apt install openjdk-21-doc 3) Browse API documentation chromium /usr/share/doc/openjdk-21-doc/api/index.html The search bar is inactive and dev console contains: jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND $ls -l /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js lrwxrwxrwx 1 root root 43 Mar 17 13:31 /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js -> ../../../../javascript/jquery/jquery.min.js cat /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js prints the file contents Downloaded version of chrome opens documentation with active search bar and no javascript errors /tmp/chrome/chrome /usr/share/doc/openjdk-21-doc/api/index.html Expected results: Chromium snap should be able to follow symlink into /usr/share/javascript and correctly load OpenJDK API documentation. Note: this probably should be a specific exclusion for Debian-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2032992/+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 2033433] Re: Xorg 100% CPU and frozen desktop after closing chromium
Duly reproduced. I don't have SSH set up here and couldn't get out with Ctrl+Alt+Backspace either, had to resort to Sysrq. The journal shows a nouveau fault at the time of the crash. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+attachment/5696501/+files/journal ** Tags added: xorg ** Tags added: nouveau -- 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/2033433 Title: Xorg 100% CPU and frozen desktop after closing chromium Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromi
[Desktop-packages] [Bug 2033433] Re: Xorg 100% CPU and frozen desktop after closing chromium
If you hit that again can you please also retrieve the log? -- 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/2033433 Title: Xorg 100% CPU and frozen desktop after closing chromium Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+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
Re: [Desktop-packages] [Bug 2033433] Re: Xorg 100% CPU and frozen desktop after closing chromium
The journal and >log 2>&1 snap run --strace='-o strace' chromium --enable- logging=stderr would be very thorough if that runs fine. Thanks for testing and have a good crash! -- 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/2033433 Title: Xorg 100% CPU and frozen desktop after closing chromium Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https:
[Desktop-packages] [Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
** This bug is no longer a duplicate of bug 1732482 [snap] doesn't properly save desktop files for "create shortcuts" action -- 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/2007652 Title: [snap] PWA don't launch as applications, just another chromium window Status in chromium-browser package in Ubuntu: Confirmed Bug description: I have recently converted from deb to snap package of chromium and progressive web applications (PWAs) launch just as another window of chromium and are not recognized as separate application by the window manager (for example when switching using Super+Tab) or dock (grouped under chromium windows). This is either a regression of the snap package vs deb or ubuntu 20.04 vs ubuntu 18.04 (I am not able to differentiate between these two since both happened together). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+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
Re: [Desktop-packages] [Bug 2033017] Re: Chromium fails to get data from google end point verification helper app
Yes.
>logfile 2>&1 snap run chromium --enable-logging
If that doesn't prove sufficient you can also add --v=1.
Having journalctl -f running at the same time will allow you to see
Apparmor denials.
--
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/2033017
Title:
Chromium fails to get data from google end point verification helper
app
Status in chromium-browser package in Ubuntu:
New
Bug description:
I am trying out Google end-point verification. This is a system that
allows the admins of a Google Workplace env to set information
security requirements on the browsers/systems that connect. When using
snapped Chromium, it fails to fetch data from the host system.
The details:
Prelude
1. I use the latest Chromium from the snap-store (Version 116.0.5845.110
(Official Build) snap (64-bit))
2. I install the Google end-point verification extension:
https://chrome.google.com/webstore/detail/endpoint-verification/callobklhcbilhphinckomhgkigmfocg
3. I install the helper app:
https://support.google.com/a/users/answer/9018161?hl=en using apt.
What goes wrong
4. The helper app has a shell script that fetches the details of the host.
That works fine. Note that it detects the encrypted disk.
kristofer@kristofer-ThinkPad-X1-Nano-Gen-1:~$
/opt/google/endpoint-verification/bin/device_state.sh
serial_number: "PW00QL5N"
disk_encrypted: ENABLED
os_version: "22.04"
screen_lock_secured: ENABLED
hostname: "kristofer-ThinkPad-X1-Nano-Gen-1"
model: "20UN002KMH"
os_firewall: "no"
mac_addresses: "00:d2:b1:d3:c4:42"
mac_addresses: "00:16:3e:00:00:00"
mac_addresses: "00:16:3e:4f:fa:02"
mac_addresses: "a6:8d:49:a8:08:fb"
mac_addresses: "04:56:e5:dc:20:fd"
kristofer@kristofer-ThinkPad-X1-Nano-Gen-1:~$
5. The chromium extension attempts to get this data, but fails. Here are the
logs from the extension. Note that it has diskEncrypted set to false.
[230825 08:58:34.05] [ChromeDeviceInfoProvider] [WARNING] No policy set to
fetch device certificate.
[230825 08:58:34.05] [ChromeDeviceInfoProvider] [WARNING] Error getting
Device ID. Failed to retrieve the device id.
[230825 08:58:34.06] [ChromeDeviceInfoProvider] [DEBUG] Response:
{"osVersion":"22","diskEncrypted":false,"screenLockSecured":true,"deviceSerialNumber":"","deviceModel":"20UN002KMH","deviceHostName":"kristofer-ThinkPad-X1-Nano-Gen-1","deviceMacAddresses":[]}.
[230825 08:58:34.06] [NativeDeviceInfoProvider] [WARNING] Error while
fetching non-configurable device info. Specified native messaging host not
found.
The same extension, on the same machine, running on Chrome is able to detect
the data from (4):
[230825 09:00:49.97] [ChromeDeviceInfoProvider] [WARNING] No policy set to
fetch device certificate.
[230825 09:00:49.98] [ChromeDeviceInfoProvider] [DEBUG] Response:
{"osVersion":"22.04","diskEncrypted":true,"screenLockSecured":true,"deviceSerialNumber":"","deviceModel":"20UN002KMH","deviceHostName":"kristofer-ThinkPad-X1-Nano-Gen-1","deviceMacAddresses":["00:16:3e:4f:fa:02","00:16:3e:00:00:00","04:56:e5:dc:20:fd","a6:8d:49:a8:08:fb","00:d2:b1:d3:c4:42"],"deviceId":"QW2aBSoOVzwVDPNxJdhd1K5NtFs","osFirewall":false}.
I suspect, but I don't know, that the snap confinement prevents it
from fetching the data. Should you have any questions or need help to
get more detailed logs, please reach out to me.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033017/+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 1843392] Re: [snap] smart card reader no longer works
*** This bug is a duplicate of bug 1967632 *** https://bugs.launchpad.net/bugs/1967632 Hi, Pascal. The snap with the new pcscd interface is awaiting approval from the Snapcraft team. Once that is done I'll post here so that someone can attempt to verify the fix. > I think I incidentally removed the 'duplicate' Don't worry, it remains logged in the full activity log page (link at the end of comment section), so I just added it back, thanks for the heads up. ** This bug has been marked a duplicate of bug 1967632 [snap] apparmor denied when trying to load pkcs11 module for smart card authentication -- 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/1843392 Title: [snap] smart card reader no longer works Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Bug description: chromium uses the Netscape Cryptographic Module to access smartcards for authentication purposes. This stopped working when switching to the snap version. Chromium would normally access the setup in ~/.pki/nssdb/pkcs11.txt That file would refer to a library used to access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc- pkcs11.so The problem can be bypassed by manually launching chromium via: /snap/chromium/current/usr/lib/chromium-browser/chrome To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1843392/+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
Re: [Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
Daniel, thanks a lot for guiding the debugging on this, and Andreas for carrying the debugging out. I thought incorrectly that this was already stated: The leak does not happen with VAAPI disabled ---> chromium --disable-features=VaapiVideoDecoder,VaapiVideoEncoder,VaapiVideoDecodeLinuxGL <--- (As such it does not occur in stable/candidate channels, that do not have VAAPI merged in.) We don't have much of a delta about hwacc with upstream right now, it's mostly patches for Ozone (which doesn't get used in Xorg, correct me if I'm wrong) and then the chromium.launcher that simply turns on some flags. Patches: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/build/chromium-patches/optimization?h=dev Flags: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/launcher/chromium.launcher?h=dev#n128 -- 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/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Opinion Bug description: chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType:
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
** Tags added: kivu -- 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/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+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.launchpa
[Desktop-packages] [Bug 2009739] Re: hwacc build crashes on direct scanout.
** Tags removed: hwacc ** Tags added: kivu -- 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/2009739 Title: hwacc build crashes on direct scanout. Status in chromium-browser package in Ubuntu: New Bug description: This pertains to the HWACC branches of the chromium snap. When launched full-screen on an Intel iGPU, the hardware overlay use will result in a core dump. This could be related to direct-scanout and overlay planes? To reproduce: $ chromium --start-fullscreen OS: Ubuntu 22.10 Chromium: 111.0.5563.19-hwacc GPU: Alderlake iGPU stolk@workpc:/snap/chromium/current/bin$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/beta/hwacc refresh-date: yesterday at 08:52 PST channels: latest/stable:110.0.5481.177 2023-03-06 (2367) 156MB - latest/candidate: 111.0.5563.64 2023-03-08 (2381) 155MB - latest/beta: 111.0.5563.64 2023-03-07 (2380) 155MB - latest/edge: 112.0.5615.12 2023-03-03 (2375) 156MB - installed: 111.0.5563.19-hwacc(2376) 174MB - stolk@workpc:/snap/chromium/current/bin$ chromium --start-fullscreen [73039:73039:0308/101357.917887:WARNING:chrome_main_delegate.cc(618)] This is Chrome version 111.0.5563.19 (not a warning) [73039:73039:0308/101358.450380:WARNING:wayland_object.cc(152)] Binding to gtk_shell1 version 4 but version 5 is available. [73039:73039:0308/101358.450401:WARNING:wayland_object.cc(152)] Binding to zwp_pointer_gestures_v1 version 1 but version 3 is available. [73039:73039:0308/101358.450416:WARNING:wayland_object.cc(152)] Binding to zwp_linux_dmabuf_v1 version 3 but version 4 is available. Gtk-Message: 10:13:58.455: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [73039:73039:0308/101358.611145:WARNING:account_consistency_mode_manager.cc(70)] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured. [73039:73039:0308/101358.625559:WARNING:wayland_surface.cc(151)] Server doesn't support zcr_alpha_compositing_v1. [73039:73039:0308/101358.625573:WARNING:wayland_surface.cc(166)] Server doesn't support overlay_prioritizer. [73039:73039:0308/101358.625579:WARNING:wayland_surface.cc(180)] Server doesn't support surface_augmenter. [73039:73039:0308/101358.625583:WARNING:wayland_surface.cc(195)] Server doesn't support wp_content_type_v1 [73039:73039:0308/101358.625586:WARNING:wayland_surface.cc(214)] Server doesn't support zcr_color_management_surface. [73039:73039:0308/101358.625774:WARNING:cursor_loader.cc(123)] Failed to load a platform cursor of type kNull [73039:73039:0308/101358.626013:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73209:73209:0308/101358.654205:ERROR:gpu_init.cc(525)] Passthrough is not supported, GL is egl, ANGLE is [73209:73209:0308/101358.657517:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process. [73039:73039:0308/101358.692393:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable. [73039:73039:0308/101358.706280:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706292:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706371:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706375:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73209:73209:0308/101358.722161:ERROR:gbm_pixmap_wayland.cc(75)] Cannot create bo with format= RGBA_ and usage=SCANOUT [73209:73209:0308/101358.722276:ERROR:gbm_pixmap_wayland.cc(75)] Cannot create bo with format= RGBA_ and usage=GPU_READ [73209:73209:0308/101358.722320:ERROR:shared_image_factory.cc(661)] CreateSharedImage: could not create backing. [73209:73209:0308/101358.722375:ERROR:shared_image_factory.cc(516)] DestroySharedImage: Could not find shared image mailbox [73209:73209:0308/101358.722458:ERROR:raster_decoder.cc(1117)] RasterDecoderImpl: Context lost during MakeCurrent. [73209:73209:0308/101358.722500:ERROR:gpu_service_impl.cc(980)] Exiting GPU
[Desktop-packages] [Bug 2011281]
In bug description: 1> when I went to use my saved passwords in chromium today, I found that they were absent. In your last comment: 2> chromium continues to be able to *use* my saved passwords. But I don't know where they're actually saved Which one is correct/up to date? Likewise for 3> I found that there was a ~/snap/chromium/common/chromium/Default/Login Data.old containing all of my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data containing a single password entry and 4> But I don't know where they're actually saved It looks impossible that Chromium is accessing passwords from 'Login Data.old'; there is no longer any reference to that, anywhere, so I think quote 3 might not be up to date. Depending on the situation you could try --password-store=basic, but given the already buggy circumstances, better have those configuration files backed up. Without a reproducible case and access to those data files, which of course you must not share as it contains passwords, this is hard to debug. -- 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/2011281 Title: chromium snap upgrade "lost" my passwords Status in chromium-browser package in Ubuntu: New Bug description: On upgrade to chromium snap revision 2333 (now since upgraded to 2367), I received a window with a notice about password migration: "Password storage via the Gnome keyring has been fixed, but for it to work, you have to rename your old ~/snap/chromium/common/chromium/Default/Login Data file so that a new, working one can replace it." I don't remember if I did this or not. However, when I went to use my saved passwords in chromium today, I found that they were absent. Tracking down the data in the chromium profile, I found that there was a ~/snap/chromium/common/chromium/Default/Login Data.old containing all of my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data containing a single password entry for a site that I happened to have created a new login for in the past few days. That's not a very user-friendly experience on upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+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
Re: [Desktop-packages] [Bug 2011281]
> Currently, I have a ~/snap/chromium/common/chromium/Default/Login Data which
> was last modified September 5. So perhaps passwords are still being written
> here.
Does this file have the expected number of entries, with sites you
recognize as having your saved passwords that you cannot nonetheless
display? I attach one such file as an example. Namely we are looking for
--->
INSERT INTO logins
VALUES('http://example.com','','','username','userPassword',X'763130ea422b31c5606d2e8435833cf73bb492',
...
<---
Also please confirm that version > last_compatible_version in that file.
When you enter a site for which you have a password saved, does the key
button appear in the address bar, as in the attached picture?
> So for you, chrome://settings/passwords shows your passwords under 'Saved
> Passwords' without having to specify --password-store=basic?
Yes. And --password-store=basic should be neither needed nor correct if
password-manager-service is connected, as it is for working without
keyring, but it was worth trying just in case something had gone funky
in that aspect.
And one more thing worth trying is to export your passwords, that is a
button under the vertical dots button in that page. Then look in the
generated CSV and see if the passwords are readable there.
--
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/2011281
Title:
chromium snap upgrade "lost" my passwords
Status in chromium-browser package in Ubuntu:
New
Bug description:
On upgrade to chromium snap revision 2333 (now since upgraded to
2367), I received a window with a notice about password migration:
"Password storage via the Gnome keyring has been fixed, but for it to
work, you have to rename your old
~/snap/chromium/common/chromium/Default/Login Data file so that a new,
working one can replace it."
I don't remember if I did this or not. However, when I went to use my
saved passwords in chromium today, I found that they were absent.
Tracking down the data in the chromium profile, I found that there was
a ~/snap/chromium/common/chromium/Default/Login Data.old containing
all of my passwords, and a
~/snap/chromium/common/chromium/Default/Login Data containing a single
password entry for a site that I happened to have created a new login
for in the past few days.
That's not a very user-friendly experience on upgrade.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+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
Re: [Desktop-packages] [Bug 2011281]
Forgot the attachments, here they are. ** Attachment added: "passwd.png" https://bugs.launchpad.net/bugs/2011281/+attachment/5699821/+files/passwd.png ** Attachment added: "login-data.dump" https://bugs.launchpad.net/bugs/2011281/+attachment/5699822/+files/login-data.dump -- 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/2011281 Title: chromium snap upgrade "lost" my passwords Status in chromium-browser package in Ubuntu: New Bug description: On upgrade to chromium snap revision 2333 (now since upgraded to 2367), I received a window with a notice about password migration: "Password storage via the Gnome keyring has been fixed, but for it to work, you have to rename your old ~/snap/chromium/common/chromium/Default/Login Data file so that a new, working one can replace it." I don't remember if I did this or not. However, when I went to use my saved passwords in chromium today, I found that they were absent. Tracking down the data in the chromium profile, I found that there was a ~/snap/chromium/common/chromium/Default/Login Data.old containing all of my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data containing a single password entry for a site that I happened to have created a new login for in the past few days. That's not a very user-friendly experience on upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+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
Re: [Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Santiago, Spotify is proprietary, there is nothing for us to do. You have to request them to update their base from core20 to core22. According to 'snap info spotify', their contact link is https://community.spotify.com/t5/Desktop-Linux/bd-p/desktop_linux. ** No longer affects: snapd (Ubuntu) ** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in ubuntu-spotify-app: New Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Possible, proposed solutions Option 1: Please install from these channels and report back with success or failure. snap refresh --channel candidate/core22 firefox Option 2: chromium --ozone-platform=wayland MOZ_ENABLE_WAYLAND=1 firefox If nothing works, it is possible around the issue by disabling hardware acceleration. Original bug report --- Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/sh
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Marking Firefox as fix released as well since now Firefox is on core22 and that was confirmed in earlier comments to solve the problem. Please reset if observed otherwise. -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in ubuntu-spotify-app: New Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Possible, proposed solutions Option 1: Please install from these channels and report back with success or failure. snap refresh --channel candidate/core22 firefox Option 2: chromium --ozone-platform=wayland MOZ_ENABLE_WAYLAND=1 firefox If nothing works, it is possible around the issue by disabling hardware acceleration. Original bug report --- Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Relea
[Desktop-packages] [Bug 2035220] Re: cve-2023-4863
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Critical
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
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/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
In Progress
Status in libwebp package in Ubuntu:
New
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
New
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+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 2035220] Re: cve-2023-4863
For your information, Chromium is now in 116.0.5845.187 in x86, and
should be in ARM too tomorrow.
--
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/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
In Progress
Status in firefox package in Ubuntu:
New
Status in firefox-esr package in Ubuntu:
New
Status in libwebp package in Ubuntu:
New
Status in thunderbird package in Ubuntu:
New
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
New
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+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 2035220] Re: cve-2023-4863
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Released
--
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/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
Fix Released
Status in firefox package in Ubuntu:
Fix Released
Status in firefox-esr package in Ubuntu:
New
Status in libwebp package in Ubuntu:
New
Status in thunderbird package in Ubuntu:
Fix Released
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
Confirmed
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: Unknown Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: When opening a SketchUp model (example) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
Thanks, it seems you already pinned down the issue, I'll investigate how to get the newer Mesa in (I think that's provided by a gnome-* snap) and all the following is just for completeness. Can you attach the following information? ---> snap info chromium firefox snap connections chromium snap connections firefox <--- > In order to test if the system MESA has the fix while the Chromium snaps does not, I unpacked it and ran the Chromium binary against system libraries. In general, for testing purposes you can run the unconfined binary directly by calling /snap/chromium/current/usr/lib/chromium- browser/chrome or /snap/firefox/current/usr/lib/firefox/firefox. You can also verify if an issue is related to hardware acceleration by passing --disable-gpu. ** Also affects: firefox via https://gitlab.freedesktop.org/mesa/mesa/-/issues/9695 Importance: Unknown Status: Unknown ** Project changed: firefox => mesa -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: Unknown Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: When opening a SketchUp model (example) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
Asked about the possibility of a rebuild at https://github.com/ubuntu/gnome-sdk/issues/167. ** Bug watch added: github.com/ubuntu/gnome-sdk/issues #167 https://github.com/ubuntu/gnome-sdk/issues/167 -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: Unknown Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+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 2035603] [NEW] Duplicity 1.2.2-1 fails to build from source
Public bug reported: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz ** Affects: duplicity (Ubuntu) Importance: Undecided Assignee: Nathan Teodosio (nteodosio) Status: Triaged ** Tags: ftbfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/2035603 Title: Duplicity 1.2.2-1 fails to build from source Status in duplicity package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+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 2035603] Re: Duplicity 1.2.2-1 fails to build from source
** Patch added: "duplicity.diff" https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+attachment/5700826/+files/duplicity.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/2035603 Title: Duplicity 1.2.2-1 fails to build from source Status in duplicity package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+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 2035603] Re: Duplicity 1.2.2-1 fails to build from source
For consistency I followed the maintainer's patch style. ** Patch added: "duplicity.diff" https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+attachment/5700853/+files/duplicity.diff ** Patch removed: "duplicity.diff" https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+attachment/5700826/+files/duplicity.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/2035603 Title: Duplicity 1.2.2-1 fails to build from source Status in duplicity package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+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 2035603] Re: Duplicity 1.2.2-1 fails to build from source
** Description changed: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz + + For the record this builds fine with the latest upstream release + setup.py so I'm not poking them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/2035603 Title: Duplicity 1.2.2-1 fails to build from source Status in duplicity package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz For the record this builds fine with the latest upstream release setup.py so I'm not poking them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+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 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
With the help of 3v1n0 it's confirmed that this is Mutter interpretation of a sandboxed application. Whether this is a bug is then a matter of opinion and actually complicated[1]. You may need to convince Gnome maintainers about it or use another desktop environment. [1] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/84 ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Opinion ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [snap] PWA don't launch as applications, just another chromium window Status in chromium-browser package in Ubuntu: Invalid Status in mutter package in Ubuntu: Opinion Bug description: I have recently converted from deb to snap package of chromium and progressive web applications (PWAs) launch just as another window of chromium and are not recognized as separate application by the window manager (for example when switching using Super+Tab) or dock (grouped under chromium windows). This is either a regression of the snap package vs deb or ubuntu 20.04 vs ubuntu 18.04 (I am not able to differentiate between these two since both happened together). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+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 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Description changed: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. - - -  - tracking:candidate - installed: 62.0.3202.94 (123) 246MB - -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: In Progress Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
The Gnome snap has been built with a newer Mesa. Could you try snap refresh --candidate gnome-42-2204 and then start the browser? Does the issue go away? -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: New Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
** Changed in: chromium-browser (Ubuntu) Status: New => Fix Committed ** Changed in: firefox (Ubuntu) Status: New => Fix Committed -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: New Status in chromium-browser package in Ubuntu: Fix Committed Status in firefox package in Ubuntu: Fix Committed Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
Sorry, I hadn't seen you already had done those tests in the linked bug report. > the chromium snap needs the updated MESA library It uses the one gnome-42-2204 exposes. If migrating to candidate didn't help, then the problem should be something else. -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: New Status in chromium-browser package in Ubuntu: Fix Committed Status in firefox package in Ubuntu: Fix Committed Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => New ** Changed in: firefox (Ubuntu) Status: Fix Committed => New -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: New Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+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 2036426] Re: gnome calculator crash on IMF server error
The problem looks to be var bodyinput = yield session.send_async (message, 1, new GLib.Cancellable()); That is not the signature of the function and it doesn't return the body input. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/2036426 Title: gnome calculator crash on IMF server error Status in gnome-calculator package in Ubuntu: New Bug description: Description: Ubuntu 23.04 Release: 23.04 gnome-calculator: Installed: 1:44.0-1ubuntu1 Candidate: 1:44.0-1ubuntu1 Version table: *** 1:44.0-1ubuntu1 500 500 http://mirror.sg.gs/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status when i tried to open the app, it crashed immediately with this in the log: ** (gnome-calculator:75655): WARNING **: 19:43:34.821: currency- provider.vala:161: Couldn't download IMF currency rate file: HTTP/2 Error: INTERNAL_ERROR (gnome-calculator:75655): libsoup-WARNING **: 19:43:34.821: (../libsoup/soup-session.c:334):soup_session_dispose: runtime check failed: (soup_connection_manager_get_num_conns (priv->conn_manager) == 0) (gnome-calculator:75655): libsoup-WARNING **: 19:43:34.821: (../libsoup/soup-connection-manager.c:84):soup_host_free: runtime check failed: (host->conns == NULL) Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/2036426/+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 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
** Changed in: chromium-browser (Ubuntu) Status: In Progress => 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
This is supposedly fixed in edge and beta channels (x86 and ARMv8): snap refresh --edge chromium #Or snap refresh --beta chromium #And then connect the required plugs: snap connect chromium:dot-local-share-applications snap connect chromium:dot-local-share-icons Your report of whether this works or not would be very welcome. -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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 2036647] Journal log
Yesterday I got crashes whenever I tried to maximize it or resize it. I started Ubuntu on Wayland from SDDM though. After I started it from GDM I no longer reproduce the problem, although I rebooted in between so... I didn't get a crash file in /var/crash. I attach the journal from yesterday, filtered for gnome-terminal. You can see 3 segfaults, and I think that is indeed the number of times I tried the terminal before giving up on it. ** Attachment added: "journal-b-1-grep-gnome-terminal-C3.txt" https://bugs.launchpad.net/bugs/2036647/+attachment/5702600/+files/journal-b-1-grep-gnome-terminal-C3.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2036647 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Gnome terminal just crashed, was moving pointer across window. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-terminal 3.49.92-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 22:39:00 2023 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2023-09-18 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918) ProcCmdline: /usr/libexec/gnome-terminal-server SegvAnalysis: Segfault happened at: 0x7f58c3c30180 : movzbl (%rsi),%ecx PC (0x7f58c3c30180) ok source "(%rsi)" (0x5646400b2000) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_utf8_pointer_to_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 ??? () at /lib/x86_64-linux-gnu/libvte-2.91.so.0 ??? () at /lib/x86_64-linux-gnu/libvte-2.91.so.0 ??? () at /lib/x86_64-linux-gnu/libvte-2.91.so.0 ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2036647/+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 2013216] [NEW] Single click on title bar does not transfer focus to target window
Public bug reported: Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar rls-ll-incoming ** Attachment added: "screencast:increase-sound-volume-to-hear-mouse-clicks" https://bugs.launchpad.net/bugs/2013216/+attachment/5658718/+files/simplescreenrecorder-2023-03-29_11.45.22.mkv -- 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/2013216 Title: Single click on title bar does not transfer focus to target window Status in gnome-shell package in Ubuntu: New Bug description: Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop- amd64.iso). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013216/+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 2013216] Re: Single click on title bar does not transfer focus to target window
** Description changed: Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. + + Reproduction recipe: + + 1. Open gnome-terminal. + 2. Run xedit. + 3. Focus gnome-terminal. + 4. Click Xedit's title bar. + + Expected: Xedit has focus. + Observed: gnome-terminal retains focus. + . + 5. Focus Xedit. + 6. Click gnome-terminal's title bar. + + Expected and observed: Xedit relinquishes focus and gnome-terminal gets + focus. I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) -- 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/2013216 Title: Single click on title bar does not transfer focus to target window Status in gnome-shell package in Ubuntu: New Bug description: Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Reproduction recipe: 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop- amd64.iso). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013216/+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 2013233] [NEW] Custom shortcuts with super key are hit-or-miss
Public bug reported:
Some custom shortcuts with super key will not work. The failing ones I
found:
Super + {1..9}
--
These will say
> Super+{Number} is already being used for Activate favorite app 9. If
you replace it, Activate favorite app 9 will be disabled.
That is not what happens though; rather the old binding is not
relinquished.
Super + o
-
Assigning this gives no such notice as above, however it is assigned
disable orientation lock.
I followed the answer in
https://askubuntu.com/questions/1179858/disable-orientation-lock-
shortcut-super-o-in-ubuntu-18-04-gnome, namely
gsettings set org.gnome.settings-daemon.plugins.media-keys
rotate-video-lock-static []
log out/log in
and now the shortcut works.
Conclusion
--
gnome-control-center should either say it's not possible to map such
combinations or honor the override.
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
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/2013233
Title:
Custom shortcuts with super key are hit-or-miss
Status in gnome-control-center package in Ubuntu:
New
Bug description:
Some custom shortcuts with super key will not work. The failing ones I
found:
Super + {1..9}
--
These will say
> Super+{Number} is already being used for Activate favorite app 9. If
you replace it, Activate favorite app 9 will be disabled.
That is not what happens though; rather the old binding is not
relinquished.
Super + o
-
Assigning this gives no such notice as above, however it is assigned
disable orientation lock.
I followed the answer in
https://askubuntu.com/questions/1179858/disable-orientation-lock-
shortcut-super-o-in-ubuntu-18-04-gnome, namely
gsettings set org.gnome.settings-daemon.plugins.media-keys
rotate-video-lock-static []
log out/log in
and now the shortcut works.
Conclusion
--
gnome-control-center should either say it's not possible to map such
combinations or honor the override.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2013233/+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
