[Desktop-packages] [Bug 2055040] Re: Software rendering under Wayland mode
I have retried the debug command from #4 and noticed no errors anymore. -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: Fix Released Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2055040] Re: Software rendering under Wayland mode
Today I got the update notification to the latest snap release 22.0.6261.39. So I have tried that one with a fresh profile and my old one and fortunately both are working now. So I guess the issue has been fixed, thanks a lot! -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2055040] Re: Software rendering under Wayland mode
1. Confirmed. 2. I am not able to respond to this question since I have started to use the experimental snap for a while now. The intention was to get the smartcards over OpenSC to work as stated here: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/comments/57 3. Done, please have a look at the attachment. ** Attachment added: "chr.log" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+attachment/5749490/+files/chr.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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2055040] Re: Software rendering under Wayland mode
The output is: > tracking: latest/edge Exactly, I had the impression that some interactive websites with animations ran particularly slow and the CPU fan began to become very noisy. htop revealed the CPU's load of nearly 100% due to the chromium processes. This was the reason that I have tried to retrieve the same websites on the Firefox browser (always with the official snap and Wayland as a compositing manager) where I hadn't any difficulty at all. So I have checked the chrome://gpu's output and noticed the cause. -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: Incomplete Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2055040] [NEW] Software rendering under Wayland mode
Public bug reported: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. ** Affects: chromium-browser (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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 1846554] Re: 'Files' icon should not be listed twice in the Cinnamon start menu
I guess this is no longer an issue in more recent Ubuntu releases. ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1846554 Title: 'Files' icon should not be listed twice in the Cinnamon start menu Status in cinnamon package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: The Nautilus 'Files' icon gets always listed twice in the Cinnamon start menu (reproduced on Ubuntu 16.04 LTS and unchanged on 18.04 LTS). This small fix to /usr/share/applications/nautilus.desktop seems to work: Change > NotShowIn=Unity;GNOME; into > NotShowIn=Unity;GNOME;X-Cinnamon; (no idea if this is the best solution) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 [modified: usr/share/applications/nautilus.desktop] ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Oct 3 20:57:27 2019 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'240' b'org.gnome.nautilus.window-state' b'geometry' b"'1268x778+396+123'" SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-09-14 (19 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1846554/+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 1846554] Re: 'Files' icon should not be listed twice in the Cinnamon start menu
I guess this is no longer an issue in more recent Ubuntu releases. ** Changed in: cinnamon (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1846554 Title: 'Files' icon should not be listed twice in the Cinnamon start menu Status in cinnamon package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: The Nautilus 'Files' icon gets always listed twice in the Cinnamon start menu (reproduced on Ubuntu 16.04 LTS and unchanged on 18.04 LTS). This small fix to /usr/share/applications/nautilus.desktop seems to work: Change > NotShowIn=Unity;GNOME; into > NotShowIn=Unity;GNOME;X-Cinnamon; (no idea if this is the best solution) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 [modified: usr/share/applications/nautilus.desktop] ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Oct 3 20:57:27 2019 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'240' b'org.gnome.nautilus.window-state' b'geometry' b"'1268x778+396+123'" SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-09-14 (19 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1846554/+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 2033590] Re: random crashes of gnome-characters
Exactly the same issue here. To copy and paste a few special characters you need to run the application over and over again. This is very cumbersome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2033590 Title: random crashes of gnome-characters Status in gnome-characters package in Ubuntu: Confirmed Bug description: Usually just a one-line record in syslog: Aug 30 19:10:45 COLOSSUS org.gnome.Characters[11012]: ***MEMORY- ERROR***: org.gnome.Characters[11012]: GSlice: assertion failed: sinfo->n_allocated > 0 Aug 30 19:12:38 COLOSSUS org.gnome.Characters[11134]: ***MEMORY- ERROR***: org.gnome.Characters[11134]: GSlice: assertion failed: sinfo->n_allocated > 0 Aug 30 19:17:29 COLOSSUS kernel: [ 2840.611031] pool- org.gnome.[11513]: segfault at 1c8 ip 7fd1854d1ae3 sp 7fd1794ca9d8 error 6 in libglib-2.0.so.0.7200.4[7fd18547a000+8f000] Aug 30 22:44:26 COLOSSUS kernel: [15257.581416] gnome- character[18769]: segfault at 18 ip 7fb24db9eae3 sp 7ffc99c29ca8 error 6 in libglib-2.0.so.0.7200.4[7fb24db47000+8f000] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-characters 41.0-4 ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 Uname: Linux 5.15.0-82-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Aug 30 22:52:57 2023 InstallationDate: Installed on 2020-05-03 (1215 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-characters UpgradeStatus: Upgraded to jammy on 2022-07-15 (412 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/2033590/+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 1877754] [NEW] GTKFileChooser: deselect highlighted directory
Public bug reported: Open a random file save form (gedit, LibreOffice doesn't matter). Sometimes the first entry in the file list gets highlighted automatically which may be a folder (especially when it is not the first time you save a file). So the user may click on another entry to change the selection, but clicking on the background *does not cause* a deselection to take place. In my opinion that would be an expected usage pattern as it is the case on common other platforms. Why is that important? Sometimes the user just needs to choose the current working directory and not a particular folder/file (he doesn't want to have the file stored in a subfolder). The only valid (and nasty) workaround is to go one hierarchy upwards and then double-click the directory folder. The folder gets opened and the user finally finds him /her-self with no entry highlighted. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: gtkfilechooser ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Description changed: Open a random file save form (gedit, LibreOffice doesn't matter). Sometimes the first entry in the file list gets highlighted - automatically (when it is not the first time you save a file). So the - user may click on another entry to change the selection, but clicking on - the background *does not cause* a deselection to take place. In my - opinion that would be an expected usage pattern as it is the case on - common other platforms. + automatically which may be a folder (especially when it is not the first + time you save a file). So the user may click on another entry to change + the selection, but clicking on the background *does not cause* a + deselection to take place. In my opinion that would be an expected usage + pattern as it is the case on common other platforms. Why is that important? Sometimes the user just needs to choose the - working directory and not a particular file. The only valid (and nasty) + current working directory and not a particular folder/file (he doesn't + want to have the file stored in a subfolder). The only valid (and nasty) workaround is to go one hierarchy upwards and then double-click the directory folder. The folder gets opened and the user finally finds him /her-self with no entry highlighted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877754 Title: GTKFileChooser: deselect highlighted directory Status in Ubuntu: New Bug description: Open a random file save form (gedit, LibreOffice doesn't matter). Sometimes the first entry in the file list gets highlighted automatically which may be a folder (especially when it is not the first time you save a file). So the user may click on another entry to change the selection, but clicking on the background *does not cause* a deselection to take place. In my opinion that would be an expected usage pattern as it is the case on common other platforms. Why is that important? Sometimes the user just needs to choose the current working directory and not a particular folder/file (he doesn't want to have the file stored in a subfolder). The only valid (and nasty) workaround is to go one hierarchy upwards and then double-click the directory folder. The folder gets opened and the user finally finds him/her-self with no entry highlighted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877754/+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 1820509] Re: Avoid use-after-free in _XimProtoSetIMValues()
Any news on this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1820509 Title: Avoid use-after-free in _XimProtoSetIMValues() Status in libx11 package in Ubuntu: New Bug description: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1820509/+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 1846554] [NEW] 'Files' icon should not be listed twice in the Cinnamon start menu
Public bug reported: The Nautilus 'Files' icon gets always listed twice in the Cinnamon start menu (reproduced on Ubuntu 16.04 LTS and unchanged on 18.04 LTS). This small fix to /usr/share/applications/nautilus.desktop seems to work: Change > NotShowIn=Unity;GNOME; into > NotShowIn=Unity;GNOME;X-Cinnamon; (no idea if this is the best solution) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 [modified: usr/share/applications/nautilus.desktop] ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Oct 3 20:57:27 2019 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'240' b'org.gnome.nautilus.window-state' b'geometry' b"'1268x778+396+123'" SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-09-14 (19 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1846554 Title: 'Files' icon should not be listed twice in the Cinnamon start menu Status in nautilus package in Ubuntu: New Bug description: The Nautilus 'Files' icon gets always listed twice in the Cinnamon start menu (reproduced on Ubuntu 16.04 LTS and unchanged on 18.04 LTS). This small fix to /usr/share/applications/nautilus.desktop seems to work: Change > NotShowIn=Unity;GNOME; into > NotShowIn=Unity;GNOME;X-Cinnamon; (no idea if this is the best solution) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 [modified: usr/share/applications/nautilus.desktop] ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Oct 3 20:57:27 2019 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'240' b'org.gnome.nautilus.window-state' b'geometry' b"'1268x778+396+123'" SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-09-14 (19 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1846554/+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 1820509] Re: Avoid use-after-free in _XimProtoSetIMValues()
Unfortunately I just stumbled over this commit by accident since I checked the commit log of libX11. So for a reproduction we would need to contact the original reporter Sami Farin (https://bugs.freedesktop.org/show_bug.cgi?id=93186) but I do not find any valid email address from him. ** Bug watch added: freedesktop.org Bugzilla #93186 https://bugs.freedesktop.org/show_bug.cgi?id=93186 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1820509 Title: Avoid use-after-free in _XimProtoSetIMValues() Status in libx11 package in Ubuntu: New Bug description: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1820509/+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 1820509] [NEW] Avoid use-after-free in _XimProtoSetIMValues()
Public bug reported: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1820509 Title: Avoid use-after-free in _XimProtoSetIMValues() Status in libx11 package in Ubuntu: New Bug description: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1820509/+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
