[Desktop-packages] [Bug 1887793] Re: [snap] chromium unable to launch
Here is another report for maybe the same issue : https://askubuntu.com/a/1259814 -- 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/1887793 Title: [snap] chromium unable to launch Status in chromium-browser package in Ubuntu: New Bug description: Updated the chromium snap yesterday, latest/stable (1229). Today from a fresh boot, it won't launch. ``` mattias@cerebus:~$ chromium Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module" Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module" Trace/breakpoint trap (core dumped) ``` Using snap revert it goes back to latest/stable (1213), and works perfectly. Refreshing back to 1229 reproduces the issue. OS: Ubuntu 20.04 LTS x86_64 Kernel: 5.4.0-40-generic Uptime: 1 hour, 43 mins Packages: 2233 (dpkg), 86 (snap) Shell: bash 5.0.16 Resolution: 2560x1440, 2560x1440 DE: GNOME WM: Mutter WM Theme: Adwaita Theme: Yaru [GTK2/3] Icons: Yaru [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-4770K (8) @ 3.900GHz GPU: NVIDIA GeForce GTX 970 Memory: 8251MiB / 15945MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1887793] Re: [snap] chromium unable to launch
>From memory I gathered this set of command from this bug report: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365 Maybe it's related ? -- 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/1887793 Title: [snap] chromium unable to launch Status in chromium-browser package in Ubuntu: Incomplete Bug description: Updated the chromium snap yesterday, latest/stable (1229). Today from a fresh boot, it won't launch. ``` mattias@cerebus:~$ chromium Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module" Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module" Trace/breakpoint trap (core dumped) ``` Using snap revert it goes back to latest/stable (1213), and works perfectly. Refreshing back to 1229 reproduces the issue. OS: Ubuntu 20.04 LTS x86_64 Kernel: 5.4.0-40-generic Uptime: 1 hour, 43 mins Packages: 2233 (dpkg), 86 (snap) Shell: bash 5.0.16 Resolution: 2560x1440, 2560x1440 DE: GNOME WM: Mutter WM Theme: Adwaita Theme: Yaru [GTK2/3] Icons: Yaru [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-4770K (8) @ 3.900GHz GPU: NVIDIA GeForce GTX 970 Memory: 8251MiB / 15945MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1887793] Re: [snap] chromium unable to launch
>From memory I gathered this set of command from this #1864365 Maybe it's related ? -- 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/1887793 Title: [snap] chromium unable to launch Status in chromium-browser package in Ubuntu: Incomplete Bug description: Updated the chromium snap yesterday, latest/stable (1229). Today from a fresh boot, it won't launch. ``` mattias@cerebus:~$ chromium Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module" Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module" Trace/breakpoint trap (core dumped) ``` Using snap revert it goes back to latest/stable (1213), and works perfectly. Refreshing back to 1229 reproduces the issue. OS: Ubuntu 20.04 LTS x86_64 Kernel: 5.4.0-40-generic Uptime: 1 hour, 43 mins Packages: 2233 (dpkg), 86 (snap) Shell: bash 5.0.16 Resolution: 2560x1440, 2560x1440 DE: GNOME WM: Mutter WM Theme: Adwaita Theme: Yaru [GTK2/3] Icons: Yaru [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-4770K (8) @ 3.900GHz GPU: NVIDIA GeForce GTX 970 Memory: 8251MiB / 15945MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1887793] Re: [snap] chromium unable to launch
@mlw I my last test the fix survived a reboot though it did not few months ago. -- 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/1887793 Title: [snap] chromium unable to launch Status in chromium-browser package in Ubuntu: Incomplete Bug description: Updated the chromium snap yesterday, latest/stable (1229). Today from a fresh boot, it won't launch. ``` mattias@cerebus:~$ chromium Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module" Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module" Trace/breakpoint trap (core dumped) ``` Using snap revert it goes back to latest/stable (1213), and works perfectly. Refreshing back to 1229 reproduces the issue. OS: Ubuntu 20.04 LTS x86_64 Kernel: 5.4.0-40-generic Uptime: 1 hour, 43 mins Packages: 2233 (dpkg), 86 (snap) Shell: bash 5.0.16 Resolution: 2560x1440, 2560x1440 DE: GNOME WM: Mutter WM Theme: Adwaita Theme: Yaru [GTK2/3] Icons: Yaru [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-4770K (8) @ 3.900GHz GPU: NVIDIA GeForce GTX 970 Memory: 8251MiB / 15945MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1887793] Re: [snap] chromium unable to launch
@mlw I my last test the fix survived a reboot though I did not few months ago. -- 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/1887793 Title: [snap] chromium unable to launch Status in chromium-browser package in Ubuntu: Incomplete Bug description: Updated the chromium snap yesterday, latest/stable (1229). Today from a fresh boot, it won't launch. ``` mattias@cerebus:~$ chromium Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module" Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module" Trace/breakpoint trap (core dumped) ``` Using snap revert it goes back to latest/stable (1213), and works perfectly. Refreshing back to 1229 reproduces the issue. OS: Ubuntu 20.04 LTS x86_64 Kernel: 5.4.0-40-generic Uptime: 1 hour, 43 mins Packages: 2233 (dpkg), 86 (snap) Shell: bash 5.0.16 Resolution: 2560x1440, 2560x1440 DE: GNOME WM: Mutter WM Theme: Adwaita Theme: Yaru [GTK2/3] Icons: Yaru [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-4770K (8) @ 3.900GHz GPU: NVIDIA GeForce GTX 970 Memory: 8251MiB / 15945MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1874727] Re: fullscreen uses only 1/4 of screen on secondary monitor with HiDPI scaling
The report I submitted was a dup of https://bugs.chromium.org/p/chromium/issues/detail?id=1055057 I've identified the patch proposed in 1055057 landed in Chrom* 83.0.4102.0, after testing with 83.0.4103.56 the issue is gone! Thanks! -- 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/1874727 Title: fullscreen uses only 1/4 of screen on secondary monitor with HiDPI scaling Status in chromium-browser package in Ubuntu: Confirmed Bug description: lsb_release -rd -> Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy chromium -> chromium: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: hardware: 2x monitors: 4K scaling: 200% Is: In chromium the fullscreen-mode uses only 1/4 of the screen on the 2nd monitor. Should be: In chromium the fullscreen-mode uses 1/1 of the screen on the 2nd monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874727/+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 1874727] Re: fullscreen uses only 1/4 of screen on secondary monitor with HiDPI scaling
Bug reported here : https://bugs.chromium.org/p/chromium/issues/detail?id=1082763 -- 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/1874727 Title: fullscreen uses only 1/4 of screen on secondary monitor with HiDPI scaling Status in chromium-browser package in Ubuntu: Confirmed Bug description: lsb_release -rd -> Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy chromium -> chromium: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: hardware: 2x monitors: 4K scaling: 200% Is: In chromium the fullscreen-mode uses only 1/4 of the screen on the 2nd monitor. Should be: In chromium the fullscreen-mode uses 1/1 of the screen on the 2nd monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874727/+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 1874727] Re: [snap] fullscreen uses only 1/4 of screen on secondary monitor with HiDPI scaling
Yes it seems related to HiDPI, in fact this issue appears either with a second monitor or not. I'm using a laptop with an HiDPI display. I have the same issue with Google Chrome. I'm now able to run apport-collect, but it seems to be taking a long time. -- 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/1874727 Title: [snap] fullscreen uses only 1/4 of screen on secondary monitor with HiDPI scaling Status in chromium-browser package in Ubuntu: Confirmed Bug description: lsb_release -rd -> Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy chromium -> chromium: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: hardware: 2x monitors: 4K scaling: 200% Is: In chromium the fullscreen-mode uses only 1/4 of the screen on the 2nd monitor. Should be: In chromium the fullscreen-mode uses 1/1 of the screen on the 2nd monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874727/+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 1874727] Re: [snap] fullscreen uses only 1/4 of screen on 2. monitor
I'm also affected by this problem. I found some workarounds: - while staying in "1/4 fullscreen", defocus chromium by selecting an other window, click on the "1/4 fullscreen" -> 1/4 become full - switching to another Gnome workspace and back to the one with the fullscreen chromium -> 1/4 become full (I can't run `apport-collect 1874727` : "You are not the reporter or subscriber of this problem report, or the report is a duplicate or already closed.") -- 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/1874727 Title: [snap] fullscreen uses only 1/4 of screen on 2. monitor Status in chromium-browser package in Ubuntu: Incomplete Bug description: lsb_release -rd -> Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy chromium -> chromium: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: hardware: 2x monitors: 4K scaling: 200% Is: In chromium the fullscreen-mode uses only 1/4 of the screen on the 2nd monitor. Should be: In chromium the fullscreen-mode uses 1/1 of the screen on the 2nd monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874727/+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
