[Desktop-packages] [Bug 2063831] Re: Clicking on bottom half of applications switches to background application
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3451 https://gitlab.gnome.org/GNOME/mutter/-/issues/3451 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3451 Importance: Unknown Status: Unknown -- 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/2063831 Title: Clicking on bottom half of applications switches to background application Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Basicly having more that 1 GUI application running in full screen and clicking bottom half of the currently opened GUI application will make the other application come to the foreground Eg: Google Chrome & Eclipse IDE are both in fullscreen, - Clicking On Eclipse IDE bottom half of the app window will get chrome to display infront of Eclipse, Eg2: Terminal and DBeaver are both in fullscreen, - Clicking On DBeaver bottom half of the app window will get Termial to display infront of DBeaver, ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:07:41 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-P GT2 [Iris Xe Graphics] [1462:1331] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Ti Mobile] [1462:135d] InstallationDate: Installed on 2024-04-25 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Micro-Star International Co., Ltd. Katana GF66 12UD ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=7c59c657-2812-4b59-8441-927f4302e8fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1584IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-1584 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1584IMS.10C:bd05/05/2022:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF6612UD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1584:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku1584.1: dmi.product.family: GF dmi.product.name: Katana GF66 12UD dmi.product.sku: 1584.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 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/mutter/+bug/2063831/+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 2063304] Re: chromium 124.0.6367.60 fails to draw its window
*** This bug is a duplicate of bug 2063049 ***
https://bugs.launchpad.net/bugs/2063049
(Confirming that I have ozone-platform-hint set to Auto instead of
Default in chrome://flags.)
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Re: chromium 124.0.6367.60 fails to draw its window
The syscall=330, the mknod denial, the /etc/vulkan/ denials are also
produced by the working chromium snap.
The /etc/igfx_user_feature.txt denial only shows up with the broken
chromium 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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Re: chromium 124.0.6367.60 fails to draw its window
(sorry, copy/paste fail) > dmesg has a bunch of repeated bal. 24 09:40:04 blynas kernel: audit: type=1400 audit(1713940804.105:20243): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/igfx_user_feature.txt" pid=7070 comm="FSBroker7944" requested_mask="r" denied_mask=" r" fsuid=1000 ouid=0 bal. 24 09:40:04 blynas kernel: audit: type=1400 audit(1713940804.105:20244): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/igfx_user_feature_next.txt" pid=7070 comm="FSBroker7944" requested_mask="r" denied_m ask="r" fsuid=1000 ouid=0 bal. 24 09:40:12 blynas kernel: audit: type=1400 audit(1713940812.841:20245): apparmor="DENIED" operation="mknod" class="file" profile="snap.firefox.firefox" name="/home/mg/.local/share/fonts/.uuid.TMP-tJGwe8" pid=191609 comm=57656220436F6E74656E74 req uested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 and on startup bal. 24 09:20:31 blynas systemd[3777]: Started snap.chromium.chromium-0ad4ed29-f99c-4296-9b4f-349b888ce2f6.scope. bal. 24 09:20:32 blynas kernel: audit: type=1326 audit(1713939632.053:20170): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=189920 comm="chrome" exe="/snap/chromium/2828/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=330 compat=0 ip=0x77eb42b8ff6b code=0x5 bal. 24 09:20:32 blynas kernel: audit: type=1326 audit(1713939632.053:20171): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=189921 comm="chrome" exe="/snap/chromium/2828/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=330 compat=0 ip=0x7980e32def6b code=0x5 bal. 24 09:20:32 blynas chrome[189858]: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.165:20172): apparmor="DENIED" operation="mknod" class="file" profile="snap.chromium.chromium" name="/home/mg/.local/share/fonts/.uuid.TMP-u02YgN" pid=189858 comm="ThreadPoolForeg" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 bal. 24 09:20:32 blynas gnome-keyring-daemon[3862]: asked to register item /org/freedesktop/secrets/collection/login/16, but it's already registered bal. 24 09:20:32 blynas gnome-keyring-d[3862]: asked to register item /org/freedesktop/secrets/collection/login/16, but it's already registered bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20173): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20174): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20175): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20176): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20177): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20178): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20179): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas chromium_chromium.desktop[189858]: [189858:189858:0424/092032.211248:ERROR:chrome_browser_cloud_management_controller.cc(161)] Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build. bal. 24 09:20:33 blynas chromium_chromium.desktop[189858]: [189858:189858:0424/092033.495512:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not part of the idle
[Desktop-packages] [Bug 2063304] Snap.Info.gtk-common-themes.txt
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769956/+files/Snap.Info.gtk-common-themes.txt
** Tags added: 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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Re: chromium 124.0.6367.60 fails to draw its window
dmesg has a bunch of repeated
`snap revert chromium` reverted to 123.0.6312.122, which works fine.
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Info.gnome-42-2204.txt
apport information
** Attachment added: "Snap.Info.gnome-42-2204.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769955/+files/Snap.Info.gnome-42-2204.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Info.core20.txt
apport information
** Attachment added: "Snap.Info.core20.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769953/+files/Snap.Info.core20.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Info.cups.txt
apport information
** Attachment added: "Snap.Info.cups.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769954/+files/Snap.Info.cups.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Info.core.txt
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769952/+files/Snap.Info.core.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.ChromiumPrefs.txt
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769949/+files/Snap.ChromiumPrefs.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Info.chromium.txt
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769951/+files/Snap.Info.chromium.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769947/+files/ProcCpuinfoMinimal.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Connections.txt
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769950/+files/Snap.Connections.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769948/+files/ProcEnviron.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] HookError_chromium_browser.txt
apport information
** Attachment added: "HookError_chromium_browser.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769946/+files/HookError_chromium_browser.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769945/+files/Dependencies.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] [NEW] chromium 124.0.6367.60 fails to draw its window
Public bug reported:
Since the last snap update to 124.0.6367.60, I cannot use chromium. It
launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at it,
the less sure I was (no Nvidia here, no issues with older snap versions, no KMS
errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-collected mantic snap wayland-session
** Tags added: apport-collected mantic wayland-session
** Description changed:
Since the last snap update to 124.0.6367.60, I cannot use chromium. It
launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
- At first I thought I was experiencing bug 1967488, but the more I looked
- at it, the less sure I was (no Nvidia here, no issues with older snap
- versions, no KMS errors in journalctl), so I'm filing a new one.
+ At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu5
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DiskUsage:
+ Filesystem Type Size Used Avail Use% Mounted on
+ /dev/nvme0n1p5 ext4 732G 483G 212G 70% /
+ tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
+ /dev/nvme0n1p5 ext4 732G 483G 212G 70% /
+ DistroRelease: Ubuntu 23.10
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2019-06-12 (1777 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: chromium-browser 1:85.0.4183.83-0ubuntu3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
+ Snap.Changes:
+ ID Status Spawn Ready Summary
+ 824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
+ Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
+ Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
+ Tags: mantic wayland-session
+ Uname: Linux 6.5.0-28-generic x86_64
+ UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
+ UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use%
[Desktop-packages] [Bug 1967488] Re: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU
I have the same problem but with Intel video. Chromium 124.0.6367.60 shows up camouflaged as my desktop wallpaper after the last snap update. -- 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: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU Status in chromium-browser package in Ubuntu: Triaged 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/transparent 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 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly
Debian reverted the change to isolate these low quality fonts from the rest of the system in https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=883973, and now this bug is back in Ubuntu 23.10. ** Bug watch added: Debian Bug tracker #883973 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883973 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/412195 Title: ttf-tahoma-replacement makes some web-sites look ugly Status in fontconfig package in Ubuntu: Invalid Status in wine1.2 package in Ubuntu: Fix Released Bug description: Binary package hint: wine1.2 This font package is good for wine 1.2; however, it also makes sites look ugly in Firefox and other browsers. I had to manually remove the fonts from /usr/share/fonts/ to rectfiy this, because removing the package through apt would have made me remove wine 1.2 and I didn't want that. ProblemType: Bug Architecture: i386 Date: Wed Aug 12 00:23:40 2009 DistroRelease: Ubuntu 9.10 Package: ttf-tahoma-replacement 1.1.27-0ubuntu1 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-5.24-generic SourcePackage: wine1.2 Uname: Linux 2.6.31-5-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/412195/+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
Upstream bug: https://gitlab.gnome.org/GNOME/gnome- calculator/-/issues/359 Upstream says the actual bug is in libsoup: https://gitlab.gnome.org/GNOME/libsoup/-/issues/361. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calculator/-/issues #359 https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/359 ** Also affects: gnome-calculator via https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/359 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/libsoup/-/issues #361 https://gitlab.gnome.org/GNOME/libsoup/-/issues/361 -- 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: Unknown Status in gnome-calculator package in Ubuntu: Confirmed 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/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 1973084] Re: transmission-daemon high RAM usage
I backported Andrey Kudinov's suggested change (replacing Ubuntu's openssl3-compat.patch with gentoo's version) and built a transmission package in a PPA for jammy (Andrey's PPA only has packages for kinetic and lunar). I've been testing the patched transmission-gtk for the last 24 hours and the memory leak is gone. I'm attaching a debdiff. ** Patch added: "debdiff that replaces mem-leaky ubuntu openssl3 patch with the gentoo openssl3 patch" https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+attachment/5713173/+files/fix-mem-leak.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 1775434] Re: Wrong ExecStop in systemd service unit
This appears to have been fixed in transmission 4.0 packages in 23.10 (mantic) and Debian sid. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1775434 Title: Wrong ExecStop in systemd service unit Status in transmission package in Ubuntu: Confirmed Bug description: ExecStop in /lib/systemd/system/transmission-daemon.service is: ExecStop=/bin/kill -s STOP $MAINPID when it should be: ExecStop=/bin/kill -s TERM $MAINPID since SIGSTOP will just suspend the daemon until it received a SIGCONT. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: transmission-daemon (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 13:47:25 2018 InstallationDate: Installed on 2018-04-28 (39 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: transmission UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1775434/+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 2037179] Re: transmission-daemon memory leak
*** This bug is a duplicate of bug 1973084 *** https://bugs.launchpad.net/bugs/1973084 ** This bug has been marked a duplicate of bug 1973084 transmission-daemon high RAM usage -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/2037179 Title: transmission-daemon memory leak Status in transmission package in Ubuntu: Confirmed Bug description: Since deploying transmission-daemon on Ubuntu 22.04 I've noticed a regular memory leak I'm not sure where or when, but it does appear the bug has been fixed upstream: https://github.com/transmission/transmission/issues/3077 Required Information: 1) # lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) # apt-cache policy transmission-daemon transmission-daemon: Installed: 3.00-2ubuntu2 Candidate: 3.00-2ubuntu2 Version table: *** 3.00-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status 3/4) Application behavior is normal, and working as expected, with the exception of the memory leak. I've been using scheduled restarts to get around it. See pmap output below, it shows the process currently using nearly 2GB of memory while running no torrents & being alive for 1 days, 16 hours. # pmap $(pgrep -u debian-transmission) | sort -hk 2 170: /usr/bin/transmission-daemon -f --log-error 55e93cf7 4K rw--- transmission-daemon 55e93cf71000 4K rw--- [ anon ] 7fe36bfff000 4K - [ anon ] 7fe3c5bf9000 4K - [ anon ] 7fe3c63fa000 4K - [ anon ] 7fe3c6c1 4K - legacy.so 7fe3c6c15000 4K rw--- legacy.so 7fe3c6c16000 4K - [ anon ] 7fe3c7417000 4K - [ anon ] 7fe3c7c18000 4K - [ anon ] 7fe3c8428000 4K r libffi.so.8.1.0 7fe3c8429000 4K - libffi.so.8.1.0 7fe3c842a000 4K r libffi.so.8.1.0 7fe3c842b000 4K rw--- libffi.so.8.1.0 7fe3c843e000 4K r libresolv.so.2 7fe3c843f000 4K rw--- libresolv.so.2 7fe3c8446000 4K r libkeyutils.so.1.9 7fe3c8447000 4K r libkeyutils.so.1.9 7fe3c8448000 4K rw--- libkeyutils.so.1.9 7fe3c845e000 4K - libtasn1.so.6.6.2 7fe3c845f000 4K r libtasn1.so.6.6.2 7fe3c846 4K rw--- libtasn1.so.6.6.2 7fe3c85c 4K r libgpg-error.so.0.32.1 7fe3c85c1000 4K rw--- libgpg-error.so.0.32.1 7fe3c85c4000 4K r libbrotlicommon.so.1.0.9 7fe3c85c5000 4K r-x-- libbrotlicommon.so.1.0.9 7fe3c85e5000 4K r libbrotlicommon.so.1.0.9 7fe3c85e6000 4K rw--- libbrotlicommon.so.1.0.9 7fe3c860 4K r libsasl2.so.2.0.25 7fe3c8601000 4K rw--- libsasl2.so.2.0.25 7fe3c860d000 4K - libkrb5support.so.0.1 7fe3c860e000 4K r libkrb5support.so.0.1 7fe3c860f000 4K rw--- libkrb5support.so.0.1 7fe3c8612000 4K r-x-- libcom_err.so.2.1 7fe3c8613000 4K r libcom_err.so.2.1 7fe3c8614000 4K r libcom_err.so.2.1 7fe3c8615000 4K rw--- libcom_err.so.2.1 7fe3c8641000 4K - libk5crypto.so.3.1 7fe3c8642000 4K r libk5crypto.so.3.1 7fe3c8643000 4K rw--- libk5crypto.so.3.1 7fe3c8644000 4K rw--- [ anon ] 7fe3c870 4K - libkrb5.so.3.3 7fe3c8792000 4K r libgmp.so.10.4.1 7fe3c8793000 4K rw--- libgmp.so.10.4.1 7fe3c87d9000 4K rw--- libnettle.so.8.4 7fe3c881f000 4K - libhogweed.so.6.4 7fe3c882 4K r libhogweed.so.6.4 7fe3c8821000 4K rw--- libhogweed.so.6.4 7fe3c8bb6000 4K rw--- libunistring.so.2.2.0 7fe3c8cec000 4K - libgcrypt.so.20.3.4 7fe3c8cf6000 4K rw--- [ anon ] 7fe3c8d0 4K r libcap.so.2.44 7fe3c8d01000 4K rw--- libcap.so.2.44 7fe3c8d1f000 4K - liblz4.so.1.9.3 7fe3c8d2 4K r liblz4.so.1.9.3 7fe3c8d21000 4K rw--- liblz4.so.1.9.3 7fe3c8d4b000 4K r liblzma.so.5.2.5 7fe3c8d4c000 4K rw--- liblzma.so.5.2.5 7fe3c8d4d000 4K r libbrotlidec.so.1.0.9 7fe3c8d59000 4K r libbrotlidec.so.1.0.9 7fe3c8d5a000 4K rw--- libbrotlidec.so.1.0.9 7fe3c8e2a000 4K r libzstd.so.1.4.8 7fe3c8e2b000 4K rw--- libzstd.so.1.4.8 7fe3c8e3a000 4K - liblber-2.5.so.0.1.11 7fe3c8e3b000 4K r liblber-2.5.so.0.1.11 7fe3c8e3c000 4K rw--- liblber-2.5.so.0.1.11 7fe3c8e96000 4K - libldap-2.5.so.0.1.11 7fe3c8e99000 4K rw--- libldap-2.5.so.0.1.11 7fe3c8eeb000 4K -
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
The memory leak makes transmission unusable, so this bug should qualify for a SRU. All we need is for someone to prepare a debdiff and request sponsorship for the upload, as described in https://wiki.ubuntu.com/StableReleaseUpdates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 2037179] Re: transmission-daemon memory leak
I'm also seeing memory leaks in transmission-gtk after upgrading to 22.04 LTS. In 48 hours it eats up all the RAM and Swap and gets killed by systemd-oomd. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/2037179 Title: transmission-daemon memory leak Status in transmission package in Ubuntu: Confirmed Bug description: Since deploying transmission-daemon on Ubuntu 22.04 I've noticed a regular memory leak I'm not sure where or when, but it does appear the bug has been fixed upstream: https://github.com/transmission/transmission/issues/3077 Required Information: 1) # lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) # apt-cache policy transmission-daemon transmission-daemon: Installed: 3.00-2ubuntu2 Candidate: 3.00-2ubuntu2 Version table: *** 3.00-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status 3/4) Application behavior is normal, and working as expected, with the exception of the memory leak. I've been using scheduled restarts to get around it. See pmap output below, it shows the process currently using nearly 2GB of memory while running no torrents & being alive for 1 days, 16 hours. # pmap $(pgrep -u debian-transmission) | sort -hk 2 170: /usr/bin/transmission-daemon -f --log-error 55e93cf7 4K rw--- transmission-daemon 55e93cf71000 4K rw--- [ anon ] 7fe36bfff000 4K - [ anon ] 7fe3c5bf9000 4K - [ anon ] 7fe3c63fa000 4K - [ anon ] 7fe3c6c1 4K - legacy.so 7fe3c6c15000 4K rw--- legacy.so 7fe3c6c16000 4K - [ anon ] 7fe3c7417000 4K - [ anon ] 7fe3c7c18000 4K - [ anon ] 7fe3c8428000 4K r libffi.so.8.1.0 7fe3c8429000 4K - libffi.so.8.1.0 7fe3c842a000 4K r libffi.so.8.1.0 7fe3c842b000 4K rw--- libffi.so.8.1.0 7fe3c843e000 4K r libresolv.so.2 7fe3c843f000 4K rw--- libresolv.so.2 7fe3c8446000 4K r libkeyutils.so.1.9 7fe3c8447000 4K r libkeyutils.so.1.9 7fe3c8448000 4K rw--- libkeyutils.so.1.9 7fe3c845e000 4K - libtasn1.so.6.6.2 7fe3c845f000 4K r libtasn1.so.6.6.2 7fe3c846 4K rw--- libtasn1.so.6.6.2 7fe3c85c 4K r libgpg-error.so.0.32.1 7fe3c85c1000 4K rw--- libgpg-error.so.0.32.1 7fe3c85c4000 4K r libbrotlicommon.so.1.0.9 7fe3c85c5000 4K r-x-- libbrotlicommon.so.1.0.9 7fe3c85e5000 4K r libbrotlicommon.so.1.0.9 7fe3c85e6000 4K rw--- libbrotlicommon.so.1.0.9 7fe3c860 4K r libsasl2.so.2.0.25 7fe3c8601000 4K rw--- libsasl2.so.2.0.25 7fe3c860d000 4K - libkrb5support.so.0.1 7fe3c860e000 4K r libkrb5support.so.0.1 7fe3c860f000 4K rw--- libkrb5support.so.0.1 7fe3c8612000 4K r-x-- libcom_err.so.2.1 7fe3c8613000 4K r libcom_err.so.2.1 7fe3c8614000 4K r libcom_err.so.2.1 7fe3c8615000 4K rw--- libcom_err.so.2.1 7fe3c8641000 4K - libk5crypto.so.3.1 7fe3c8642000 4K r libk5crypto.so.3.1 7fe3c8643000 4K rw--- libk5crypto.so.3.1 7fe3c8644000 4K rw--- [ anon ] 7fe3c870 4K - libkrb5.so.3.3 7fe3c8792000 4K r libgmp.so.10.4.1 7fe3c8793000 4K rw--- libgmp.so.10.4.1 7fe3c87d9000 4K rw--- libnettle.so.8.4 7fe3c881f000 4K - libhogweed.so.6.4 7fe3c882 4K r libhogweed.so.6.4 7fe3c8821000 4K rw--- libhogweed.so.6.4 7fe3c8bb6000 4K rw--- libunistring.so.2.2.0 7fe3c8cec000 4K - libgcrypt.so.20.3.4 7fe3c8cf6000 4K rw--- [ anon ] 7fe3c8d0 4K r libcap.so.2.44 7fe3c8d01000 4K rw--- libcap.so.2.44 7fe3c8d1f000 4K - liblz4.so.1.9.3 7fe3c8d2 4K r liblz4.so.1.9.3 7fe3c8d21000 4K rw--- liblz4.so.1.9.3 7fe3c8d4b000 4K r liblzma.so.5.2.5 7fe3c8d4c000 4K rw--- liblzma.so.5.2.5 7fe3c8d4d000 4K r libbrotlidec.so.1.0.9 7fe3c8d59000 4K r libbrotlidec.so.1.0.9 7fe3c8d5a000 4K rw--- libbrotlidec.so.1.0.9 7fe3c8e2a000 4K r libzstd.so.1.4.8 7fe3c8e2b000 4K rw--- libzstd.so.1.4.8 7fe3c8e3a000 4K - liblber-2.5.so.0.1.11 7fe3c8e3b000 4K r liblber-2.5.so.0.1.11 7fe3c8e3c000 4K rw--- liblber-2.5.so.0.1.11 7fe3c8e96000 4K - libldap-2.5.so.0.1.11 7fe3c8e99000 4K rw--- libldap-2.5.so.0.1.11 7fe3c8eeb000 4K - libgssapi_krb5.so.2.2
[Desktop-packages] [Bug 2013652] Re: small thumbnails are generated if you have the screenshots folder open in nautilus
Looking through upstream bug tracker I wonder if this might be caused by https://gitlab.gnome.org/GNOME/nautilus/-/issues/2487#note_1553836? -- 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/2013652 Title: small thumbnails are generated if you have the screenshots folder open in nautilus Status in nautilus package in Ubuntu: New Bug description: If you have ~/Pictures/Screenshots open in Nautilus and you take new screenshots, some of them will get tiny thumbnails instead of regular size thumbnails. See attached picture of the end result: some images have full size thumbnails, some have tiny ones. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 17:02:09 2023 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'extra-large'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'starred']" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1300, 971)' InstallationDate: Installed on 2019-06-12 (1387 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (161 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2013652/+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 2013652] [NEW] small thumbnails are generated if you have the screenshots folder open in nautilus
Public bug reported: If you have ~/Pictures/Screenshots open in Nautilus and you take new screenshots, some of them will get tiny thumbnails instead of regular size thumbnails. See attached picture of the end result: some images have full size thumbnails, some have tiny ones. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 17:02:09 2023 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'extra-large'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'starred']" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1300, 971)' InstallationDate: Installed on 2019-06-12 (1387 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (161 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session ** Attachment added: "screenshot of nautilus with varying thumbnail sizes" https://bugs.launchpad.net/bugs/2013652/+attachment/5659588/+files/Ekrano%20nuotrauka%20i%C5%A1%202023-03-31%2017-01-58.png ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2487 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2487 -- 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/2013652 Title: small thumbnails are generated if you have the screenshots folder open in nautilus Status in nautilus package in Ubuntu: New Bug description: If you have ~/Pictures/Screenshots open in Nautilus and you take new screenshots, some of them will get tiny thumbnails instead of regular size thumbnails. See attached picture of the end result: some images have full size thumbnails, some have tiny ones. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 17:02:09 2023 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'extra-large'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'starred']" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1300, 971)' InstallationDate: Installed on 2019-06-12 (1387 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (161 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2013652/+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 2007998] [NEW] Arrow before folders when you enable expandability in the list view, to be visible only if subfolders or files are present in the parent folder
Public bug reported: OS: Ubuntu 22.04.2 LTS Release: 22.04 In Ubuntu 22.04 Nautilus > Preferences you have "Expandable Folders in List View" If you activate the "Tree" option, the arrow in front of the folders will be present even for empty folders. The arrow should only be present before folders when the parent directory is not empty, but it is always present, which causes a lot of confusion. What's the trick to expanding an empty folder? I use Nemo as File Manager on another laptop and the arrow before the folder is only present if that folder is not empty. Which also makes sense! A few days ago I posted this issue (including screenshots) on AskUbuntu and other users confirmed that it's a BUG, as it is reproduced to them too: https://askubuntu.com/questions/1454724/arrow-before-folders-when-you- enable-expandability-in-the-list-view-to-be-visib ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/2007998 Title: Arrow before folders when you enable expandability in the list view, to be visible only if subfolders or files are present in the parent folder Status in nautilus package in Ubuntu: New Bug description: OS: Ubuntu 22.04.2 LTS Release: 22.04 In Ubuntu 22.04 Nautilus > Preferences you have "Expandable Folders in List View" If you activate the "Tree" option, the arrow in front of the folders will be present even for empty folders. The arrow should only be present before folders when the parent directory is not empty, but it is always present, which causes a lot of confusion. What's the trick to expanding an empty folder? I use Nemo as File Manager on another laptop and the arrow before the folder is only present if that folder is not empty. Which also makes sense! A few days ago I posted this issue (including screenshots) on AskUbuntu and other users confirmed that it's a BUG, as it is reproduced to them too: https://askubuntu.com/questions/1454724/arrow-before-folders-when-you- enable-expandability-in-the-list-view-to-be-visib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2007998/+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 1874415] Re: [snap] chromedriver doesn't work without --headless under Wayland
I'm now using Xephyr to confine my ChromeDriver-based Selenium tests Xephyr :2 -screen 1300x720 export DISPLAY=:2 unset WAYLAND_DISPLAY This works fine for me on Ubuntu 22.10 in a Wayland session (and it also worked on 22.04 LTS). As a bonus, the Chromium window doesn't steal focus any more when my Selenium tests close and open new browser windows! But since things worked fine for me on 22.04 even before I implemented the Xephyr sandboxing, I'm not sure if this will be helpful to you or not. -- 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/1874415 Title: [snap] chromedriver doesn't work without --headless under Wayland Status in chromium-browser package in Ubuntu: Fix Released Bug description: Since I upgraded my Ubuntu 19.04 laptop to Ubuntu 19.10 I've been unable to run Robot Framework tests using SeleniumLibrary with Chrome. I keep getting errors from chromedriver: Parent suite setup failed: WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally. (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /snap/chromium/current/command-chromium.wrapper is no longer running, so ChromeDriver is assuming that Chrome has crashed.) Things work somewhat better when I ask chromium to run in headless mode, although I still get weird failures partway through the test suite (I think on the first test that uses Select Window): TimeoutException: Message: timeout: Timed out receiving message from renderer: 300.000. It would be easier to debug this if I could _see_ what the browser is doing, which brings us back to the original problem: non-headless chromium doesn't work in 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874415/+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 1993904] Re: key binding to launch gnome-control-center doesn't work
This was fixed upstream in version 42.beta: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/371a1260630035724e20972ae5bda7098e2928a7 Ubuntu explicitly reverts that in debian/patches/ubuntu/Revert-media- keys-fix-gnome-settings-desktop-file.patch with the rationale > Ubuntu isn't getting the rename until gnome-control-center 42 Well, 22.10 now has gnome-control-center 43 with the .desktop file rename, so this patch ought to be dropped. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1993904 Title: key binding to launch gnome-control-center doesn't work Status in gnome-settings-daemon package in Ubuntu: New Bug description: There's a default keybinding of XF86Tools to launch gnome-control- center. On my ThinkPad X390's keyboard it is Fn-F9. This keybinding no longer works in Ubuntu 22.10. Instead I see this error in my journal: spal. 22 20:27:34 blynas gsd-media-keys[3793]: Could not find application 'gnome-control-center.desktop' or '(null)' AFACT gnome-control-center 43 renamed the .desktop file to /usr/share/applications/org.gnome.Settings.desktop ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-settings-daemon 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 20:29:29 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1227 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1993904/+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 1993904] [NEW] key binding to launch gnome-control-center doesn't work
Public bug reported: There's a default keybinding of XF86Tools to launch gnome-control- center. On my ThinkPad X390's keyboard it is Fn-F9. This keybinding no longer works in Ubuntu 22.10. Instead I see this error in my journal: spal. 22 20:27:34 blynas gsd-media-keys[3793]: Could not find application 'gnome-control-center.desktop' or '(null)' AFACT gnome-control-center 43 renamed the .desktop file to /usr/share/applications/org.gnome.Settings.desktop ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-settings-daemon 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 20:29:29 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1227 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1993904 Title: key binding to launch gnome-control-center doesn't work Status in gnome-settings-daemon package in Ubuntu: New Bug description: There's a default keybinding of XF86Tools to launch gnome-control- center. On my ThinkPad X390's keyboard it is Fn-F9. This keybinding no longer works in Ubuntu 22.10. Instead I see this error in my journal: spal. 22 20:27:34 blynas gsd-media-keys[3793]: Could not find application 'gnome-control-center.desktop' or '(null)' AFACT gnome-control-center 43 renamed the .desktop file to /usr/share/applications/org.gnome.Settings.desktop ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-settings-daemon 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 20:29:29 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1227 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1993904/+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 1993797] Re: refreshing the view with F5 forgets the sort order
I suspect upstream commit https://gitlab.gnome.org/GNOME/nautilus/-/commit/c72e6def48e47454d4b620f58c93753a8a1b6a3f fixes this, which would explain why I couldn't reproduce using gnome- nightly. (There are several sorting-related upstream commits after the 43.0 tag.) -- 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/1993797 Title: refreshing the view with F5 forgets the sort order Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: 1. Open Nautilus 2. Switch to list view 3. Sort by size or mtime by clicking on the relevant heading 4. Press F5 to refresh the view Expectation: - Nautilus remembers the sort order Actual behavior: - the list is now sorted by name (in ascending order) Additional information: - This is a regression since Ubuntu 22.04 LTS - I was unable to reproduce the problem using the org.gnome.NautilusDevel flatpak from gnome-nightly ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 21 12:58:21 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1226 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993797/+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 1993797] [NEW] refreshing the view with F5 forgets the sort order
Public bug reported: Steps to reproduce: 1. Open Nautilus 2. Switch to list view 3. Sort by size or mtime by clicking on the relevant heading 4. Press F5 to refresh the view Expectation: - Nautilus remembers the sort order Actual behavior: - the list is now sorted by name (in ascending order) Additional information: - This is a regression since Ubuntu 22.04 LTS - I was unable to reproduce the problem using the org.gnome.NautilusDevel flatpak from gnome-nightly ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 21 12:58:21 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1226 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1993797 Title: refreshing the view with F5 forgets the sort order Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: 1. Open Nautilus 2. Switch to list view 3. Sort by size or mtime by clicking on the relevant heading 4. Press F5 to refresh the view Expectation: - Nautilus remembers the sort order Actual behavior: - the list is now sorted by name (in ascending order) Additional information: - This is a regression since Ubuntu 22.04 LTS - I was unable to reproduce the problem using the org.gnome.NautilusDevel flatpak from gnome-nightly ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 21 12:58:21 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1226 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993797/+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 1978069] [NEW] pressing ctrl+shift+p makes chromium become non-responsive
Public bug reported: 1. Open Chromium 2. Press Ctrl+Shift+P What happens: a print dialog pops up (presumably from xdg-desktop- portal-gnome), and both the dialog and the main Chromium window become non-responsive. After a few seconds GNOME Shell pops up a "this app is unresponsive" dialog with options to wait or kill it. Waiting doesn't seem to help (although it may be that my patience is too short). What should happen: a responsive print dialog that I can dismiss because I pressed Ctrl+Shift+P by accident. So far this has happened twice to me in Ubuntu 22.04 LTS. Wayland Ubuntu session, in case it matters. ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 10:34:36 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1092 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Snap: chromium 102.0.5005.61 (latest/stable) Snap.Changes: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to jammy on 2022-04-29 (40 days ago) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy snap wayland-session -- 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/1978069 Title: pressing ctrl+shift+p makes chromium become non-responsive Status in chromium-browser package in Ubuntu: New Bug description: 1. Open Chromium 2. Press Ctrl+Shift+P What happens: a print dialog pops up (presumably from xdg-desktop- portal-gnome), and both the dialog and the main Chromium window become non-responsive. After a few seconds GNOME Shell pops up a "this app is unresponsive" dialog with options to wait or kill it. Waiting doesn't seem to help (although it may be that my patience is too short). What should happen: a responsive print dialog that I can dismiss because I pressed Ctrl+Shift+P by accident. So far this has happened twice to me in Ubuntu 22.04 LTS. Wayland Ubuntu session, in case it matters. ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 10:34:36 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1092 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Snap: chromium 102.0.5005.61 (latest/stable) Snap.Changes: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to jammy on 2022-04-29 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1978069/+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 1970917] Re: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->mo
Happened to me today, when I unplugged the USB C cable connecting my ThinkPad to the dock with an external monitor plugged in, and then closed the laptop lid to put it to sleep. journalctl shows ``` geg. 27 15:53:39 blynas gnome-shell[3815]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed geg. 27 15:53:39 blynas gnome-shell[3815]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed geg. 27 15:53:39 blynas gnome-shell[3815]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed geg. 27 15:53:39 blynas gnome-shell[3815]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed geg. 27 15:53:40 blynas systemd-logind[906]: Lid closed. geg. 27 15:53:41 blynas gnome-shell[3815]: ** geg. 27 15:53:41 blynas gnome-shell[3815]: mutter:ERROR:../src/core/window.c:3728:meta_window_update_for_monitors_changed: assertion failed: (!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)) geg. 27 15:53:41 blynas gnome-shell[3815]: Bail out! mutter:ERROR:../src/core/window.c:3728:meta_window_update_for_monitors_changed: assertion failed: (!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)) geg. 27 15:53:41 blynas gnome-shell[3815]: GNOME Shell crashed with signal 6 geg. 27 15:53:41 blynas gnome-shell[3815]: == Stack trace for context 0x563285c4a4b0 == ``` Ubuntu 22.04 LTS, Intel video (in case that matters). -- 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/1970917 Title: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)" in meta_window_update_for_monitors_changed() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: gnome-shell crashes with SIGABRT due to assertion failure: "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)" in meta_window_update_for_monitors_changed(). However a bug in errors.ubuntu.com is hiding it. Sometimes it is visible on https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058 (when the last crash report was from jammy) and sometimes not (impish). To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1970917/+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 1874415] Re: [snap] chromedriver doesn't work without --headless under Wayland
I can no longer observe this on Ubuntu 22.04 LTS (Wayland session) with chromium snap 101.0.4951.64 (1993). (An xeyes test confirms that the selenium-driven chromium is using Xwayland.) -- 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/1874415 Title: [snap] chromedriver doesn't work without --headless under Wayland Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since I upgraded my Ubuntu 19.04 laptop to Ubuntu 19.10 I've been unable to run Robot Framework tests using SeleniumLibrary with Chrome. I keep getting errors from chromedriver: Parent suite setup failed: WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally. (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /snap/chromium/current/command-chromium.wrapper is no longer running, so ChromeDriver is assuming that Chrome has crashed.) Things work somewhat better when I ask chromium to run in headless mode, although I still get weird failures partway through the test suite (I think on the first test that uses Select Window): TimeoutException: Message: timeout: Timed out receiving message from renderer: 300.000. It would be easier to debug this if I could _see_ what the browser is doing, which brings us back to the original problem: non-headless chromium doesn't work in 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874415/+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 1969285] Re: Wayland session unavailable after upgrade from 21.10
** Package changed: ubuntu => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1969285 Title: Wayland session unavailable after upgrade from 21.10 Status in gdm3 package in Ubuntu: New Bug description: After upgrading from 21.10 to beta 22.04 the Wayland session is no longer available. By default, I do not even get the option to select the session type but if I lock the screen, the login screen changes from the X11 UI to the Gnome UI and the bottom right button appears. When clicking on the session selector button the screen blanks out and then returns to a X11 session login screen (X11 session works as expected). I thought this was related to the https://bugs.launchpad.net/bugs/1960898 because I had the dash-to-dock extension in 21.10 but after attempting the gsettings fix, it still did not work. I also removed the extension but Wayland still does not work. I installed lightdm and switched to it for a successful Wayland session for now. Hardware: https://linux-hardware.org/?probe=800aefa57e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969285/+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 1930371] Re: top bar displayed on top of a fullscreen window that gets moved from one monitor to another
This bug also affects 21.10, FWIW. -- 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/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Bug description: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1930371/+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 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
I've seen this three times now on Ubuntu 21.10 (GNOME 40). I don't recall ever seeing it on Ubuntu 20.10. -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+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 1930371] Re: top bar displayed on top of a fullscreen window that gets moved from one monitor to another
Filed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4351 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4351 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4351 -- 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/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another Status in gnome-shell package in Ubuntu: New Bug description: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930371/+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 1930371] [NEW] top bar displayed on top of a fullscreen window that gets moved from one monitor to another
Public bug reported: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another Status in gnome-shell package in Ubuntu: New Bug description: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930371/+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 1707611] Re: Sound does not automatically switch to HDMI when connected
My laptop with Ubuntu 20.10 automatically switches to the HDMI output when I plug in my monitor (via a USB C cable connected to a dock station connected to the monitor via a HDMI cable). And then, a second later, it switches to the USB dock's audio output (which has nothing plugged in), but that's a different bug. Incidentally, module-switch-on-connect in PulseAudio 14 (and also Ubuntu 20.10's 13.99.2) has a blacklist of sink names that should not be switched to. The default value of this blacklist is a regexp matching "hdmi". The blacklist doesn't appear to work (which is also a different bug). If it does start to work at some point, you may have to edit /etc/pulse/default.pa and change load-module module-switch-on-connect to say load-module module-switch-on-connect blacklist="" if you want HDMI outputs to be switched to. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1707611 Title: Sound does not automatically switch to HDMI when connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: When connecting a HDMI cable or other audio device, the user must manually click on the "sound volume" in the top-right and switch to the newly connected device. Example: you connect a HDMI cable to the television, but then you must manually choose the HDMI sound option; it does not get selected automatically. Often times e.g. when the HDMI cable is disconnected, the user must then manually click on the "speakers" or "line out" setting - EVEN IF IT'S ALREADY SELECTED, it must be clicked on again for the sound to work through the computer's speakers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707611/+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 1913388] Re: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
fyi, fixed patch for clucene to keep the ABI constant on s390x is attached to https://sourceforge.net/p/clucene/bugs/233/. The patch requires that clucene uses a separate type clucene_float_t in its API, with multiple yet trivial changes all across the code base. None of the packages that depend on clucene required modifications to cope with that API change; sword, bibletime, dovecot, and libreoffice just build in a current hirose with a modified clucene. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: Triaged Status in clucene-core package in Ubuntu: Triaged Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+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 1913388] Re: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
Indeed, my patch is just broken. I have not received any upstream feedback about the patch or the proposed alternatives -- unfortunately, clucene's community appears rather inactive, with 0 emails on the developer list in the last three months. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: Triaged Status in clucene-core package in Ubuntu: Triaged Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+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 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I don't know if you need more confirmations, but upgrading to mutter + libmitter from groovy-proposed fixed my chromium problem too. (The only weird bit was how I was unconsensually logged out during the upgrade, but that could've been plymouth or some other package.) -- 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: In Progress Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: In Progress Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) 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/mutter/+bug/1897224/+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 1899356] Re: [snap] file chooser has no icons
I do not currently have access to the machine, due to COVID lockdowns.
I haven't changed the theme, so it _should_ be the default for Ubuntu
sessions, i.e. Yaru.
(My current machine doesn't exhibit the problem. Firefox also didn't
have the problem on the machine where I took this screenshot.)
--
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/1899356
Title:
[snap] file chooser has no icons
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This is a freshly installed Ubuntu 20.04 LTS system. I apt installed
chromium-browser, which pulled in the snap. I'm in an Ubuntu on
Wayland session.
The file chooser (accessible e.g. by Ctrl+O) in Chromium is missing
all of the icons (see screenshot).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 11 18:06:45 2020
InstallationDate: Installed on 2020-10-08 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium']
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 85.0.4183.121
(a81aa729a8e1fd413943a339393c82e7b8055ddc-refs/branch-heads/4183@{#1864})
Snap.ChromiumVersion: Chromium 85.0.4183.121 snap
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/1899356/+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 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in Chromium (and non-snap browsers too)
Feels fixed to me too!
--
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/1858636
Title:
snapd generates incomplete fontconfig caches, result in emoji
rendering issue in Chromium (and non-snap browsers too)
Status in chromium-browser package in Ubuntu:
Invalid
Status in snapd package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I've just upgraded to groovy and hit this bug. For now I'm using socat as a workaround: socat abstract-listen:/tmp/.X11-unix/X0,reuseaddr,fork unix:/tmp/.X11-unix/X0 This works, but is rather slow (and probably also opens a security hole on multiuser machines). -- 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: Confirmed Status in mutter package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Bug description: I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) 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/mutter/+bug/1897224/+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 1900095] [NEW] "Restart Firefox" button quits but doesn't restart after Firefox upgrades
Public bug reported: When I upgrade Firefox via apt upgrade (or, more often, Update Manager) and open a new tab, Firefox shows a page telling me that it's been upgraded and I need to restart it before I can continue browsing. There's a "Restart Firefox" button. I press it, Firefox quits, and then fails to restart. I have to start Firefox myself. This is similar to bug 80773, but that one was fixed back in 2012, so I think this is a new one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 81.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mg 3603 F pulseaudio /dev/snd/controlC0: mg 3603 F pulseaudio BuildID: 20201012085804 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 09:13:04 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-10-08 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=81.0/20200917005511 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET88W (1.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES2142P dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1QET88W(1.63):bd04/22/2020:svnLENOVO:pn20HES2142P:pvrThinkPadT470:rvnLENOVO:rn20HES2142P:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES2142P dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- 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/1900095 Title: "Restart Firefox" button quits but doesn't restart after Firefox upgrades Status in firefox package in Ubuntu: New Bug description: When I upgrade Firefox via apt upgrade (or, more often, Update Manager) and open a new tab, Firefox shows a page telling me that it's been upgraded and I need to restart it before I can continue browsing. There's a "Restart Firefox" button. I press it, Firefox quits, and then fails to restart. I have to start Firefox myself. This is similar to bug 80773, but that one was fixed back in 2012, so I think this is a new one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 81.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mg 3603 F pulseaudio /dev/snd/controlC0: mg 3603 F pulseaudio BuildID: 20201012085804 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 09:13:04 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False
[Desktop-packages] [Bug 1899356] [NEW] chromium's file chooser has no icons
Public bug reported:
This is a freshly installed Ubuntu 20.04 LTS system. I apt installed
chromium-browser, which pulled in the snap. I'm in an Ubuntu on Wayland
session.
The file chooser (accessible e.g. by Ctrl+O) in Chromium is missing all
of the icons (see screenshot).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 11 18:06:45 2020
InstallationDate: Installed on 2020-10-08 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium']
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 85.0.4183.121
(a81aa729a8e1fd413943a339393c82e7b8055ddc-refs/branch-heads/4183@{#1864})
Snap.ChromiumVersion: Chromium 85.0.4183.121 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal wayland-session
** Attachment added: "screenshot of chromium's file chooser"
https://bugs.launchpad.net/bugs/1899356/+attachment/5420916/+files/Screenshot%20from%202020-10-11%2018-08-27.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/1899356
Title:
chromium's file chooser has no icons
Status in chromium-browser package in Ubuntu:
New
Bug description:
This is a freshly installed Ubuntu 20.04 LTS system. I apt installed
chromium-browser, which pulled in the snap. I'm in an Ubuntu on
Wayland session.
The file chooser (accessible e.g. by Ctrl+O) in Chromium is missing
all of the icons (see screenshot).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 11 18:06:45 2020
InstallationDate: Installed on 2020-10-08 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium']
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 85.0.4183.121
(a81aa729a8e1fd413943a339393c82e7b8055ddc-refs/branch-heads/4183@{#1864})
Snap.ChromiumVersion: Chromium 85.0.4183.121 snap
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/1899356/+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 1894373] Re: [UX430UA, Realtek ALC295, Black Headphone Out, Left] Playback problem
Same problem on Ubuntu 20.04 with Linux 5.4.0-48-generic x86_64. Using Linux 5.4.0-42-generic x86_64 fixes the problem though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1894373 Title: [UX430UA, Realtek ALC295, Black Headphone Out, Left] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: Everything works well, except the Headphone jack. The Headphones are detected, they are not mutted in alsamixer and pavucontrol detects them and detects sound is going to the headphones. However there is no sound. With speakers everything is allright ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-45.49~18.04.2-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 4502 F pulseaudio /dev/snd/pcmC0D0p: daniel 4502 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Sep 5 14:22:55 2020 InstallationDate: Installed on 2018-02-19 (928 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio Interno - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [UX430UA, Realtek ALC295, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to bionic on 2018-09-21 (714 days ago) dmi.bios.date: 12/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UA.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UA.201:bd12/16/2016:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-09-05T13:28:26.876229 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1894373/+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 1868293] Re: gnome-shell crashed in meta_workspace_index: Workspace does not exist to index!
I'm from an upgraded ubuntu 20.04 notebook that freezes less than 1 minute after login. The only time it unfrozen a bit it thrown the popup with this error. Well, at least there was the link to this bug as duplicate or something. The solution they suggested here https://forums.developer.nvidia.com/t/ubuntu-20-04-screen-freezes-after-5-minutes-of-uptime-with-nvidia-drivers/122297 didn't work. So I think it's something in gnome--ubuntu20.04 -- 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/1868293 Title: gnome-shell crashed in meta_workspace_index: Workspace does not exist to index! Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/5340b1db97f4c8202e6c7a695097f4f6c22a0695 --- gnome-shell crashed when I tried to move fireforx from one workspace to another. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 18:49:14 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-03-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: meta_bug () at /lib/x86_64-linux-gnu/libmutter-6.so.0 meta_workspace_index () at /lib/x86_64-linux-gnu/libmutter-6.so.0 () at /lib/x86_64-linux-gnu/libffi.so.7 () at /lib/x86_64-linux-gnu/libffi.so.7 () at /lib/libgjs.so.0 Title: gnome-shell crashed with SIGABRT in meta_bug() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868293/+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 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
I once had trouble getting full native resolution on an external 2560x1080 monitor. It turned out to be a problem with the DisplayPort -> HDMI monitor cable I had (not enough bandwidth without using a custom reduced frequency mode via xrandr/way harded custom EDID hacks for wayland), and switching to a better cable (DP -> DP, rated for 4K video) allowed me full use of the monitor. Have you ruled out hardware/cable problems by, e.g. booting to a different OS, or trying a different cable? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Incomplete Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+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 1858636] Re: color emoji not rendered; many bw emoji rendered as boxes
I ended up adding
if [ -n "$PS1" ]; then
# only for interactive sessions please
if [ -f /var/cache/fontconfig/0bd3dc0958fa22058ebb13e2872b-le64.cache-7
]; then
echo "color emoji will be broken in Chromium again (LP: #1858636) unless
you"
echo "sudo rm
/var/cache/fontconfig/0bd3dc0958fa22058ebb13e2872b-le64.cache-7"
fi
fi
to my ~/.bashrc to warn me when this problem is coming back. So far the
appearance of this broken font cache file correlates 100% with some snap
(any snap! refreshing _lxd_ which has nothing to do with GUI apps or
fonts causes this!) getting refreshed, according to the timestamp
reported by snap changes.
--
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/1858636
Title:
color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev
[Desktop-packages] [Bug 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
Maybe not.
ls -ld /snap/*/current/usr/share/fonts/truetype/noto shows that only one
snap has that directory (gnome-3-34-1804), and instead of containing all
the fonts but NotoColorEmoji.ttf it's the exact opposite: it contains
one font only, and that is NotoColorEmoji.ttf.
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
[Desktop-packages] [Bug 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
Curiously, fc-cat /var/cache/fontconfig
/0bd3dc0958fa22058ebb13e2872b-le64.cache-7.bork does not complain
about the cache file being invalid. It shows information about a bunch
of Noto fonts BUT! not the ColorEmoji one!
diff -u <(fc-cat /var/cache/fontconfig/*.bork|cut -d'"' -f2|sort) <(ls
/usr/share/fonts/truetype/noto/|sort)
shows that NotoColorEmoji.ttf is the only font missing from the font
cache file.
Now it's time for baseless speculation: could it be that snap refresh
somehow runs fc-cache inside a container where /var/cache/fontconfig is
bind-mounted from the host OS, but /usr/share/fonts/truetype/ comes from
some base snap image?
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
[Desktop-packages] [Bug 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
FWIW 0bd3dc0958fa22058ebb13e2872b is MD5 of
"/usr/share/fonts/truetype/noto". fontconfig keeps one cache file per
font directory.
The timestamp of the broken fontconfig cache file is May 15, 10:37. I
wonder what my computer was doing at the time.
'last reboot' indicates that I rebooted on May 12, and then today, May
20. I'm pretty sure I launched Chromium right after booting and never
quit it until the next reboot.
journalctl shows me what my computer was doing on May 15 at 10:36:
geg. 15 10:36:59 blynas lxd.daemon[365715]: => Stop reason is: snap refresh
geg. 15 10:36:59 blynas lxd.daemon[365715]: => Stopping LXD
geg. 15 10:36:59 blynas lxd.daemon[1225]: => LXD exited cleanly
so it is snap refresh, not reboot, that creates the broken fontconfig
cache file! It's just that when I snap refresh something that is not
chromium, I don't restart chromium!
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79
[Desktop-packages] [Bug 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
This time I successfully resurrected color emoji by manually removing
the file that fc-cache used to complain about. Or, rather, I moved it
aside, for study:
sudo mv /var/cache/fontconfig/0bd3dc0958fa22058ebb13e2872b-
le64.cache-7{,.bork}
Then I restarted Chromium and emoji are now colorful again.
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
[Desktop-packages] [Bug 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
FWIW rebooting also makes the problem reappear. snap info shows that I
last refreshed chromium 13 days ago, but I rebooted today to install a
kernel update, and color emoji disappeared.
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
Another experiment: while emoji are broken, I can do sudo fc-cache -s
-v, and it doesn't find any invalid cache files, and when I restart
chromium, I don't get color emoji.
But then I do sudo apt install --reinstall fonts-noto-color-emoji, and I
see a /var/log/fontconfig.log with an up-to-date timestamp, and it says,
again,
/var/cache/fontconfig: invalid cache file:
0bd3dc0958fa22058ebb13e2872b-le64.cache-7
and I restart chromium again, and now I have working color emoji.
(Until the next snap refresh at least).
I don't understand anything.
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version:
[Desktop-packages] [Bug 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
Yesterday I saw a notification about chromium being auto-refreshed,
restarted it, and today I noticed that color emoji are gone again.
I suspect the two facts are 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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
I tired to figure out what exactly happens when I reinstall fonts-noto-
color-emoji. According to dpkg's output, fontconfig's triggers run.
fontconfig's postinst runs
# Force regeneration of all fontconfig cache files.
mkdir -p /var/cache/fontconfig
fc-cache -s -v 1>/var/log/fontconfig.log 2>&1 || printf "fc-cache
failed.\nSee /var/log/fontconfig.log for more information.\n"
when triggered. I looked at /var/log/fontconfig.log, and I see a lot of
"skipped" messages for various directories (because "existing cache is
valid" or "looped directory detected"), and then I see
/var/cache/fontconfig: cleaning cache directory
/var/cache/fontconfig: invalid cache file:
0bd3dc0958fa22058ebb13e2872b-le64.cache-7
fc-cache: succeeded
Now I'm wondering how a fontconfig cache file becomes invalid, and how
do other applications cope.
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan
[Desktop-packages] [Bug 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
Unfortunately the workaround is temporary. I rebooted and the emoji are
gone again.
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X390
[Desktop-packages] [Bug 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
The workaround worked for me too. I used the simplified version
sudo apt install --reinstall fonts-noto-color-emoji
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
[Desktop-packages] [Bug 1874415] Re: chromedriver doesn't work with the snap package, without --headless
This is interesting information! I have the chromium and chromium-chromedriver packages installed via apt. I wonder if that is why my example (headless) can work without overriding executable_path? chromium-chromedriver ships a /usr/bin/chromedriver that's a shell script that exec's /snap/bin/chromium.chromedriver. > Does this work for you? No. I get seleniumwhy.py:10: DeprecationWarning: executable_path has been deprecated, please pass in a Service object driver = webdriver.Chrome(options=options, executable_path=driver_path) Traceback (most recent call last): File "seleniumwhy.py", line 10, in driver = webdriver.Chrome(options=options, executable_path=driver_path) File "/usr/lib/python3/dist-packages/selenium/webdriver/chrome/webdriver.py", line 95, in __init__ RemoteWebDriver.__init__( File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 152, in __init__ self.start_session(capabilities, browser_profile) File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 249, in start_session response = self.execute(Command.NEW_SESSION, parameters) File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 318, in execute self.error_handler.check_response(response) File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/errorhandler.py", line 242, in check_response raise exception_class(message, screen, stacktrace) selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally. (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /snap/chromium/current/command-chromium.wrapper is no longer running, so ChromeDriver is assuming that Chrome has crashed.) Meanwhile --headless emits the same DeprecationWarning, but works. I'm also on Ubuntu 20.04 today (was on 19.10 when I filed the bug). Possibly relevant: I use the Ubuntu on Wayland session. -- 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/1874415 Title: chromedriver doesn't work with the snap package, without --headless Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since I upgraded my Ubuntu 19.04 laptop to Ubuntu 19.10 I've been unable to run Robot Framework tests using SeleniumLibrary with Chrome. I keep getting errors from chromedriver: Parent suite setup failed: WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally. (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /snap/chromium/current/command-chromium.wrapper is no longer running, so ChromeDriver is assuming that Chrome has crashed.) Things work somewhat better when I ask chromium to run in headless mode, although I still get weird failures partway through the test suite (I think on the first test that uses Select Window): TimeoutException: Message: timeout: Timed out receiving message from renderer: 300.000. It would be easier to debug this if I could _see_ what the browser is doing, which brings us back to the original problem: non-headless chromium doesn't work in 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874415/+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 1874415] Re: chromedriver doesn't work with the snap package, without --headless
Here's my minimal example:
#!/usr/bin/env python3
import time
import sys
from selenium import webdriver
options = webdriver.chrome.options.Options()
if '--headless' in sys.argv:
options.add_argument("headless")
driver = webdriver.Chrome(options=options)
driver.get("https://ubuntu.com;)
time.sleep(1)
print(driver.current_url)
driver.quit()
I can run python3 ex.py --headless, and it works (prints https://ubuntu.com
after 10 seconds).
I can run it without --headless and I get
selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome
failed to start: exited abnormally.
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location
/snap/chromium/current/command-chromium.wrapper is no longer running, so
ChromeDriver is assuming that Chrome has crashed.)
--
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/1874415
Title:
chromedriver doesn't work with the snap package, without --headless
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Since I upgraded my Ubuntu 19.04 laptop to Ubuntu 19.10 I've been
unable to run Robot Framework tests using SeleniumLibrary with Chrome.
I keep getting errors from chromedriver:
Parent suite setup failed:
WebDriverException: Message: unknown error: Chrome failed to start: exited
abnormally.
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location
/snap/chromium/current/command-chromium.wrapper is no longer running, so
ChromeDriver is assuming that Chrome has crashed.)
Things work somewhat better when I ask chromium to run in headless mode,
although I still get weird failures partway through the test suite (I think on
the first test that uses Select Window): TimeoutException: Message: timeout:
Timed out receiving message from renderer: 300.000.
It would be easier to debug this if I could _see_ what the browser is
doing, which brings us back to the original problem: non-headless
chromium doesn't work in 19.10.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874415/+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 1874415] [NEW] chromedriver doesn't work with the snap package, without --headless
Public bug reported: Since I upgraded my Ubuntu 19.04 laptop to Ubuntu 19.10 I've been unable to run Robot Framework tests using SeleniumLibrary with Chrome. I keep getting errors from chromedriver: Parent suite setup failed: WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally. (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /snap/chromium/current/command-chromium.wrapper is no longer running, so ChromeDriver is assuming that Chrome has crashed.) Things work somewhat better when I ask chromium to run in headless mode, although I still get weird failures partway through the test suite (I think on the first test that uses Select Window): TimeoutException: Message: timeout: Timed out receiving message from renderer: 300.000. It would be easier to debug this if I could _see_ what the browser is doing, which brings us back to the original problem: non-headless chromium doesn't work in 19.10. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: 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/1874415 Title: chromedriver doesn't work with the snap package, without --headless Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since I upgraded my Ubuntu 19.04 laptop to Ubuntu 19.10 I've been unable to run Robot Framework tests using SeleniumLibrary with Chrome. I keep getting errors from chromedriver: Parent suite setup failed: WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally. (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /snap/chromium/current/command-chromium.wrapper is no longer running, so ChromeDriver is assuming that Chrome has crashed.) Things work somewhat better when I ask chromium to run in headless mode, although I still get weird failures partway through the test suite (I think on the first test that uses Select Window): TimeoutException: Message: timeout: Timed out receiving message from renderer: 300.000. It would be easier to debug this if I could _see_ what the browser is doing, which brings us back to the original problem: non-headless chromium doesn't work in 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874415/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection
The workaround I now use is to modify the cp -a command in /etc/ppp/ip-
up.d/usepeerdns to look like this:
cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE" || {
rm -f "$REALRESOLVCONF.pppd-backup.$PPP_IFACE" "$REALRESOLVCONF.tmp"
exit 1
}
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ppp in Ubuntu.
https://bugs.launchpad.net/bugs/1778946
Title:
No dns resolution after closing a vpn/pptp connection
Status in ppp package in Ubuntu:
Fix Released
Status in ppp package in Debian:
New
Bug description:
step to reproduce
set a VPN connection configured to connect a Microsoft vpn server
(pptp)
internet acces is ok
enable the vpn connection using the applet on the top right corner of
the desktop
internet still ok
ping works
disable the vpn connection
ping doesn't works with a host but works if i specify an ip address
ping: xx.net: Nom ou service inconnu
As a workaround, i disable the ethernet link and re-enable it
name resolution is now ok
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 27 18:09:30 2018
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2014-06-03 (1484 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IpRoute:
default via 192.168.0.254 dev eth0 proto dhcp metric 20100
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
RfKill:
SourcePackage: network-manager
UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
CONNECTION CON-UUID CON-PATH
eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2
Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd
/org/freedesktop/NetworkManager/ActiveConnection/6
lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 --
----
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING
WIFI-HW WIFI WWAN-HW WWAN
running 1.10.6 connected (site only) started limited enabled
enabled enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1778946/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection
Unfortunately the fix doesn't work and Ubuntu 19.10 with ppp 2.4.7-2+4.1ubuntu4.1 is still affected. I've added a bunch of logger -t usepeerdns -- doing stuff commands to /etc/ppp/ip-up.d/usepeerdns and /etc/ppp/ip- down.d/usepeerdns. Here's what I see when /etc/resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf (which is the standard Ubuntu configuration) and /run/systemd/resolve/stub-resolv.conf is owned by systemd-resolve:systemd-resolve: $ journalctl -b SYSLOG_IDENTIFIER=usepeerdns -f kov. 18 22:16:44 blynas usepeerdns[29590]: running /etc/ppp/ip-up.d/usepeerdns ppp0 0 10.46.37.85 192.0.2.1 7c4ea6b5-3f8b-4874-a81a-c4712fa17787 kov. 18 22:16:44 blynas usepeerdns[29592]: the real resolv.conf is /run/systemd/resolve/stub-resolv.conf kov. 18 22:16:44 blynas usepeerdns[29595]: created /run/systemd/resolve/stub-resolv.conf.tmp kov. 18 22:16:44 blynas usepeerdns[29597]: -rw-r--r-- 1 systemd-resolve systemd-resolve 719 Mar 18 22:16 /run/systemd/resolve/stub-resolv.conf -rw-r--r-- 1 root root749 Mar 18 22:16 /run/systemd/resolve/stub-resolv.conf.tmp This indicates that the script aborted early due to the `#!/bin/sh -e` shebang line, as I had more logging statements. The failing command must've been the cp -a. Disconnecting produces kov. 18 22:16:49 blynas usepeerdns[29785]: running /etc/ppp/ip-down.d/usepeerdns ppp0 0 10.46.37.85 192.0.2.1 7c4ea6b5-3f8b-4874-a81a-c4712fa17787 kov. 18 22:16:49 blynas usepeerdns[29791]: -rw-r--r-- 1 systemd-resolve systemd-resolve 719 Mar 18 22:16 /run/systemd/resolve/stub-resolv.conf -rw--- 1 root root719 Mar 18 22:16 /run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0 kov. 18 22:16:49 blynas usepeerdns[29797]: moved /run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0 to /run/systemd/resolve/stub-resolv.conf kov. 18 22:16:49 blynas usepeerdns[29803]: -rw--- 1 root root 719 Mar 18 22:16 /run/systemd/resolve/stub-resolv.conf kov. 18 22:16:49 blynas usepeerdns[29805]: all is well! Now if I apply a manual fix of the form sudo chmod a+r /etc/resolv.conf and then connect to the VPN again, I'll see that the script runs successfully to the end kov. 18 22:18:17 blynas usepeerdns[30617]: running /etc/ppp/ip-up.d/usepeerdns ppp0 0 10.46.37.85 192.0.2.1 7c4ea6b5-3f8b-4874-a81a-c4712fa17787 kov. 18 22:18:17 blynas usepeerdns[30619]: the real resolv.conf is /run/systemd/resolve/stub-resolv.conf kov. 18 22:18:17 blynas usepeerdns[30622]: created /run/systemd/resolve/stub-resolv.conf.tmp kov. 18 22:18:17 blynas usepeerdns[30627]: -rw-r--r-- 1 root root 719 Mar 18 22:16 /run/systemd/resolve/stub-resolv.conf -rw-r--r-- 1 root root 749 Mar 18 22:18 /run/systemd/resolve/stub-resolv.conf.tmp kov. 18 22:18:17 blynas usepeerdns[30636]: backed up /run/systemd/resolve/stub-resolv.conf to /run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0 kov. 18 22:18:17 blynas usepeerdns[30638]: -rw-r--r-- 1 root root 719 Mar 18 22:16 /run/systemd/resolve/stub-resolv.conf -rw-r--r-- 1 root root 719 Mar 18 22:16 /run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0 -rw-r--r-- 1 root root 749 Mar 18 22:18 /run/systemd/resolve/stub-resolv.conf.tmp kov. 18 22:18:17 blynas usepeerdns[30640]: moved /run/systemd/resolve/stub-resolv.conf.tmp to /run/systemd/resolve/stub-resolv.conf kov. 18 22:18:17 blynas usepeerdns[30643]: -rw-r--r-- 1 systemd-resolve systemd-resolve 719 Mar 18 22:18 /run/systemd/resolve/stub-resolv.conf -rw-r--r-- 1 root root719 Mar 18 22:16 /run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0 kov. 18 22:18:17 blynas usepeerdns[30644]: all is well! and when I disconnect, the bug is no longer showing up: kov. 18 22:18:38 blynas usepeerdns[30885]: running /etc/ppp/ip-down.d/usepeerdns ppp0 0 10.46.37.85 192.0.2.1 7c4ea6b5-3f8b-4874-a81a-c4712fa17787 kov. 18 22:18:38 blynas usepeerdns[30900]: -rw-r--r-- 1 systemd-resolve systemd-resolve 719 Mar 18 22:18 /run/systemd/resolve/stub-resolv.conf -rw-r--r-- 1 root root719 Mar 18 22:16 /run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0 kov. 18 22:18:38 blynas usepeerdns[30905]: moved /run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0 to /run/systemd/resolve/stub-resolv.conf kov. 18 22:18:38 blynas usepeerdns[30907]: -rw-r--r-- 1 root root 719 Mar 18 22:16 /run/systemd/resolve/stub-resolv.conf kov. 18 22:18:38 blynas usepeerdns[30908]: all is well! The only difference is the ownership of
[Desktop-packages] [Bug 1793427] Re: network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-resolv.conf
*** This bug is a duplicate of bug 1778946 *** https://bugs.launchpad.net/bugs/1778946 ** This bug has been marked a duplicate of bug 1778946 No dns resolution after closing a vpn/pptp connection -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1793427 Title: network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub- resolv.conf Status in network-manager-fortisslvpn package in Ubuntu: Confirmed Status in network-manager-l2tp package in Ubuntu: Confirmed Status in network-manager-pptp package in Ubuntu: Confirmed Bug description: (I'm not able to use ubuntu-bug as it fails with a 503 error trying to connect to the crash server) I'm using Ubuntu 18.04.1 on 64bit Intel with: network-manager1.10.6-2ubuntu1 network-manager-fortisslvpn1.2.8-1build1 network-manager-fortisslvpn-gnome 1.2.8-1build1 network-manager-gnome 1.8.10-2ubuntu1 systemd237-3ubuntu10.3 When I connect then disconnect from my VPN using the network-manager- fortisslvpn VPN interface, it will break the permissions on /run/systemd/resolv/stub-resolv.conf such that I can't use DNS anymore until I fix the permissions. On my system I see: $ ls -al /etc/resolv.conf lrwxrwxrwx 1 root root 39 Oct 22 2017 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf When there's no VPN connection, I see: $ ls -al /run/systemd/resolve/ total 8 drwxr-xr-x 3 systemd-resolve systemd-resolve 100 Sep 19 23:05 ./ drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../ drwx-- 2 systemd-resolve systemd-resolve 60 Sep 19 23:05 netif/ -rw-r--r-- 1 systemd-resolve systemd-resolve 714 Sep 19 23:05 resolv.conf -rw-r--r-- 1 systemd-resolve systemd-resolve 783 Sep 19 19:31 stub-resolv.conf Now I start the fortisslvpn VPN: $ ls -al /run/systemd/resolve/ total 16 drwxr-xr-x 3 systemd-resolve systemd-resolve 140 Sep 19 23:06 ./ drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../ drwx-- 2 systemd-resolve systemd-resolve 80 Sep 19 23:06 netif/ -rw-r--r-- 1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf -rw-r--r-- 1 systemd-resolve systemd-resolve 783 Sep 19 23:06 stub-resolv.conf -rw--- 1 rootroot783 Sep 19 19:31 stub-resolv.conf.pppd-backup.ppp0 -rw-r--r-- 1 rootroot805 Sep 19 23:06 stub-resolv.conf.tmp Note how the stub-resolv.conf.pppd-backup-ppp0 has 0600 file permissions. Now I stop the fortisslvpn VPN: $ ls -al /run/systemd/resolve/ total 12 drwxr-xr-x 3 systemd-resolve systemd-resolve 120 Sep 19 23:06 ./ drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../ drwx-- 2 systemd-resolve systemd-resolve 60 Sep 19 23:06 netif/ -rw-r--r-- 1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf -rw--- 1 rootroot783 Sep 19 19:31 stub-resolv.conf -rw-r--r-- 1 rootroot805 Sep 19 23:06 stub-resolv.conf.tmp Now the stub-resolv.conf file hs 0600 permissions and my DNS is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-fortisslvpn/+bug/1793427/+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 1793427] Re: network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-resolv.conf
*** This bug is a duplicate of bug 1778946 *** https://bugs.launchpad.net/bugs/1778946 I've the same problem with a L2TP VPN. This still happens on Ubuntu 19.10. ** Also affects: network-manager-l2tp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1793427 Title: network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub- resolv.conf Status in network-manager-fortisslvpn package in Ubuntu: Confirmed Status in network-manager-l2tp package in Ubuntu: Confirmed Status in network-manager-pptp package in Ubuntu: Confirmed Bug description: (I'm not able to use ubuntu-bug as it fails with a 503 error trying to connect to the crash server) I'm using Ubuntu 18.04.1 on 64bit Intel with: network-manager1.10.6-2ubuntu1 network-manager-fortisslvpn1.2.8-1build1 network-manager-fortisslvpn-gnome 1.2.8-1build1 network-manager-gnome 1.8.10-2ubuntu1 systemd237-3ubuntu10.3 When I connect then disconnect from my VPN using the network-manager- fortisslvpn VPN interface, it will break the permissions on /run/systemd/resolv/stub-resolv.conf such that I can't use DNS anymore until I fix the permissions. On my system I see: $ ls -al /etc/resolv.conf lrwxrwxrwx 1 root root 39 Oct 22 2017 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf When there's no VPN connection, I see: $ ls -al /run/systemd/resolve/ total 8 drwxr-xr-x 3 systemd-resolve systemd-resolve 100 Sep 19 23:05 ./ drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../ drwx-- 2 systemd-resolve systemd-resolve 60 Sep 19 23:05 netif/ -rw-r--r-- 1 systemd-resolve systemd-resolve 714 Sep 19 23:05 resolv.conf -rw-r--r-- 1 systemd-resolve systemd-resolve 783 Sep 19 19:31 stub-resolv.conf Now I start the fortisslvpn VPN: $ ls -al /run/systemd/resolve/ total 16 drwxr-xr-x 3 systemd-resolve systemd-resolve 140 Sep 19 23:06 ./ drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../ drwx-- 2 systemd-resolve systemd-resolve 80 Sep 19 23:06 netif/ -rw-r--r-- 1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf -rw-r--r-- 1 systemd-resolve systemd-resolve 783 Sep 19 23:06 stub-resolv.conf -rw--- 1 rootroot783 Sep 19 19:31 stub-resolv.conf.pppd-backup.ppp0 -rw-r--r-- 1 rootroot805 Sep 19 23:06 stub-resolv.conf.tmp Note how the stub-resolv.conf.pppd-backup-ppp0 has 0600 file permissions. Now I stop the fortisslvpn VPN: $ ls -al /run/systemd/resolve/ total 12 drwxr-xr-x 3 systemd-resolve systemd-resolve 120 Sep 19 23:06 ./ drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../ drwx-- 2 systemd-resolve systemd-resolve 60 Sep 19 23:06 netif/ -rw-r--r-- 1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf -rw--- 1 rootroot783 Sep 19 19:31 stub-resolv.conf -rw-r--r-- 1 rootroot805 Sep 19 23:06 stub-resolv.conf.tmp Now the stub-resolv.conf file hs 0600 permissions and my DNS is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-fortisslvpn/+bug/1793427/+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 1858636] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318199/+files/ProcInterrupts.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318196/+files/ProcCpuinfo.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318197/+files/ProcCpuinfoMinimal.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318195/+files/Lsusb.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] Snap.Info.chromium.txt
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318203/+files/Snap.Info.chromium.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318192/+files/CurrentDmesg.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318207/+files/UdevDb.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318198/+files/ProcEnviron.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] Snap.Info.core.txt
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318204/+files/Snap.Info.core.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318193/+files/Dependencies.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] Snap.Info.core18.txt
apport information
** Attachment added: "Snap.Info.core18.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318205/+files/Snap.Info.core18.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] Snap.Connections.txt
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318202/+files/Snap.Connections.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] Snap.Info.gtk-common-themes.txt
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318206/+files/Snap.Info.gtk-common-themes.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] Snap.ChromiumPrefs.txt
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318201/+files/Snap.ChromiumPrefs.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318194/+files/Lspci.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318200/+files/ProcModules.txt
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
New
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1858636] [NEW] [snap] color emoji not rendered; many bw emoji rendered as boxes
Public bug reported:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-
snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't have
it when I first upgraded to Ubuntu 19.10 and to the snapified Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-not-
color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0CTO1WW
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-collected eoan snap wayland-session
** Tags added: apport-collected eoan snap wayland-session
** Description changed:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
[Desktop-packages] [Bug 1855997] Re: firefox www.google.com crashes when a firefox instance is already running and MOZ_ENABLE_WAYLAND is set to 1
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1598995 (same steps to reproduce, and I see the same "runtime check failed: (impl->staging_cairo_surface != cairo_surface)" errors in my journal that correspond to Firefox crashes) ** Bug watch added: Mozilla Bugzilla #1598995 https://bugzilla.mozilla.org/show_bug.cgi?id=1598995 -- 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/1855997 Title: firefox www.google.com crashes when a firefox instance is already running and MOZ_ENABLE_WAYLAND is set to 1 Status in firefox package in Ubuntu: New Bug description: Steps to reproduce: - make sure Firefox is not running - export MOZ_ENABLE_WAYLAND=1 - firefox then in a new terminal - export MOZ_ENABLE_WAYLAND=1 - firefox www.google.com Expectation: - a new tab opens in the Firefox window, loading google Actual result: - firefox crashes This is a recent regression: it used to work fine in 70.0.1+build1-0ubuntu0.19.10.1, broke when I upgraded to 71.0+build5-0ubuntu0.19.10.1. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 71.0+build5-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191205203726 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 09:26:41 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (181 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205203726 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-10-18 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/+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 1855997] [NEW] firefox www.google.com crashes when a firefox instance is already running and MOZ_ENABLE_WAYLAND is set to 1
Public bug reported: Steps to reproduce: - make sure Firefox is not running - export MOZ_ENABLE_WAYLAND=1 - firefox then in a new terminal - export MOZ_ENABLE_WAYLAND=1 - firefox www.google.com Expectation: - a new tab opens in the Firefox window, loading google Actual result: - firefox crashes This is a recent regression: it used to work fine in 70.0.1+build1-0ubuntu0.19.10.1, broke when I upgraded to 71.0+build5-0ubuntu0.19.10.1. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 71.0+build5-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191205203726 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 09:26:41 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (181 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205203726 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-10-18 (53 days ago) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1855997 Title: firefox www.google.com crashes when a firefox instance is already running and MOZ_ENABLE_WAYLAND is set to 1 Status in firefox package in Ubuntu: New Bug description: Steps to reproduce: - make sure Firefox is not running - export MOZ_ENABLE_WAYLAND=1 - firefox then in a new terminal - export MOZ_ENABLE_WAYLAND=1 - firefox www.google.com Expectation: - a new tab opens in the Firefox window, loading google Actual result: - firefox crashes This is a recent regression: it used to work fine in 70.0.1+build1-0ubuntu0.19.10.1, broke when I upgraded to 71.0+build5-0ubuntu0.19.10.1. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 71.0+build5-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191205203726 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 09:26:41 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (181 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205203726 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-10-18 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/+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 1855996] [NEW] TypeError: expected string or bytes-like object in apport hook
Public bug reported: I see this on my machine when I try to report a Firefox bug: $ ubuntu-bug firefox ERROR: hook /usr/share/apport/package-hooks/source_firefox.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 205, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_firefox.py", line 1386, in add_info if (profile.current or profile.default) and profile.addon_compat_check_disabled: File "/usr/share/apport/package-hooks/source_firefox.py", line 1227, in addon_compat_check_disabled is_nightly = re.sub(r'^[^\.]+\.[0-9]+([a-z0-9]*).*', r'\1', self.last_version) == 'a1' File "/usr/lib/python3.7/re.py", line 192, in sub return _compile(pattern, flags).sub(repl, string, count) TypeError: expected string or bytes-like object ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 71.0+build5-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191205203726 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 09:26:03 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (181 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205203726 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-10-18 (53 days ago) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1855996 Title: TypeError: expected string or bytes-like object in apport hook Status in firefox package in Ubuntu: New Bug description: I see this on my machine when I try to report a Firefox bug: $ ubuntu-bug firefox ERROR: hook /usr/share/apport/package-hooks/source_firefox.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 205, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_firefox.py", line 1386, in add_info if (profile.current or profile.default) and profile.addon_compat_check_disabled: File "/usr/share/apport/package-hooks/source_firefox.py", line 1227, in addon_compat_check_disabled is_nightly = re.sub(r'^[^\.]+\.[0-9]+([a-z0-9]*).*', r'\1', self.last_version) == 'a1' File "/usr/lib/python3.7/re.py", line 192, in sub return _compile(pattern, flags).sub(repl, string, count) TypeError: expected string or bytes-like object ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 71.0+build5-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191205203726 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 09:26:03 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (181 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205203726 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-10-18 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855996/+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 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault in _filterKeybinding:windowManager.js:1825 from invoke_handler() from process_even
Unfortunately I was unable to reproduce the bug. -- 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/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault in _filterKeybinding:windowManager.js:1825 from invoke_handler() from process_event() from process_special_modifier_key() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1851528/+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 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
Upstream bug report: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1870 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1870 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1870 -- 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/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault Status in gnome-shell package in Ubuntu: New Bug description: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851528/+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 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
The JS traceback points to this line: https://gitlab.gnome.org/GNOME/gnome-shell/blob/3913fa5044b2cd1d5abadc9b4254d06215491458/js/ui/windowManager.js#L1771 (GitLab commit doesn't match gnome-shell from Ubuntu 19.10, sorry! I didn't have the time to go hunt for the exact commit that corresponds to the package, instead I extracted the source file with gresource extract /usr/lib/gnome-shell/libgnome-shell.so /org/gnome/shell/ui/windowManager.js, looked up the line, then found the same code in the same function in the current gitlab tree.) The column points to the `binding.get_name()` call. -- 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/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault Status in gnome-shell package in Ubuntu: New Bug description: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851528/+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 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
apport-retrace --gdb --sandbox system --cache ~/.cache/apport-retrace
/var/crash/_usr_bin_gnome-shell.1000.crash
...
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Toks failas ar aplankas
neegzistuoja.
[Current thread is 1 (Thread 0x7f5c91796cc0 (LWP 3417))]
(gdb) bt
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x56068ef0852a in dump_gjs_stack_on_signal_handler ()
#2
#3 0x5606b18aca40 in ?? ()
#4 0x7f5c971a9f11 in invoke_handler (binding=0x56069dc351c0,
event=0x5606b4c878c0, window=0x56069dc351c0, handler=,
display=0x5606900e0020) at ../src/core/keybindings.c:1921
#5 process_event (display=display@entry=0x5606900e0020,
window=window@entry=0x56069e5ad220, event=event@entry=0x5606b4c878c0)
at ../src/core/keybindings.c:2005
#6 0x7f5c971ab83e in process_special_modifier_key
(display=display@entry=0x5606900e0020, event=event@entry=0x5606b4c878c0,
window=window@entry=0x56069e5ad220,
modifier_press_only=modifier_press_only@entry=0x5606900e01a8,
resolved_key_combo=resolved_key_combo@entry=0x5606900e0198,
trigger_callback=0x7f5c971a5100 )
at ../src/core/keybindings.c:2051
#7 0x7f5c971ac976 in process_overlay_key (window=0x56069e5ad220,
event=0x5606b4c878c0, display=0x5606900e0020)
at ../src/core/keybindings.c:2151
#8 process_key_event (event=0x5606b4c878c0, window=0x56069e5ad220,
display=0x5606900e0020) at ../src/core/keybindings.c:2228
#9 meta_keybindings_process_event (display=display@entry=0x5606900e0020,
window=window@entry=0x56069e5ad220,
event=event@entry=0x5606b4c878c0) at ../src/core/keybindings.c:2326
#10 0x7f5c971a801c in meta_display_handle_event (event=0x5606b4c878c0,
display=0x5606900e0020) at ../src/core/events.c:358
#11 event_callback (event=0x5606b4c878c0, data=0x5606900e0020) at
../src/core/events.c:479
#12 0x7f5c97368235 in _clutter_event_process_filters ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#13 0x7f5c9737e585 in emit_keyboard_event ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#14 0x7f5c9721c0e0 in meta_input_device_native_process_kbd_a11y_event
(event=0x5606b4c878c0, device=0x56068fd782b0,
emit_event_func=0x7f5c9737e570 ) at
../src/backends/native/meta-input-device-native.c:1195
#15 0x7f5c9737fa36 in _clutter_process_event ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#16 0x7f5c97399d08 in _clutter_stage_queue_event ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#17 0x7f5c9721901c in meta_event_dispatch (g_source=,
callback=, user_data=)
at ../src/backends/native/meta-device-manager-native.c:686
#18 0x7f5c97cf984d in g_main_context_dispatch () from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#19 0x7f5c97cf9ad0 in g_main_context_iterate.isra () from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#20 0x7f5c97cf9dc3 in g_main_loop_run () from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#21 0x7f5c971aefe0 in meta_run () at ../src/core/main.c:676
#22 0x56068ef07d85 in main ()
(gdb) frame 4
#4 0x7f5c971a9f11 in invoke_handler (binding=0x56069dc351c0,
event=0x5606b4c878c0, window=0x56069dc351c0, handler=,
display=0x5606900e0020) at ../src/core/keybindings.c:1921
1921../src/core/keybindings.c: Toks failas ar aplankas neegzistuoja.
(gdb) print *binding->handler
$1 = {name = 0x5606b49e5e80 "", func = 0x5606b18aca40, default_func =
0x7f5c5b333f10, data = 0, flags = 0, user_data = 0x5606b10c4e30,
user_data_free_func = 0x7f5c97487c60}
(gdb) print *binding
$2 = {name = 0x5606b49d15d0 "\220T\241\234\006V", combo = {keysym = 50, keycode
= 0, modifiers = META_VIRTUAL_SUPER_MASK},
resolved_combo = {keycodes = 0x5606a0c44d70, len = 1, mask = 64}, flags = 0,
handler = 0x5606b37830b0}
#gnome-shell reactions on IRC:
18:34 looks suspicious
18:35 its as if the looked up binding was freed already and now just
contains garbage
--
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/1851528
Title:
JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0
and segfault
Status in gnome-shell package in Ubuntu:
New
Bug description:
I was trying to bring my Firefox window to front by pressing Super+2
(it's my second pinned launcher), and gnome-shell crashed.
journalctl shows this:
lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed
UTF-8 character sequence at offset 0
[Desktop-packages] [Bug 1851528] [NEW] JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
Public bug reported: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault Status in gnome-shell package in Ubuntu: New Bug description: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851528/+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 1849105] Re: [snap] cannot pause video with bluetooth headset buttons any more (MPRIS denied by apparmor)
I can confirm that the fix works with chromium snap 78.0.3904.70 (rev
909).
--
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/1849105
Title:
[snap] cannot pause video with bluetooth headset buttons any more
(MPRIS denied by apparmor)
Status in chromium-browser package in Ubuntu:
Fix Released
Bug description:
On Ubuntu 19.04 I could press the button on my Bluetooth headset and
the YouTube video playing in my Chromium would pause/resume. This no
longer works in 19.10. What happens instead is I get an OSD popup
with a NO ENTRY symbol (circle with a diagonal backslash) from gnome-
shell.
I suspect the additional sandboxing of the snap package is the
culprit.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 76.0.3809.100-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
Date: Mon Oct 21 15:04:13 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 208G 62G 78% /
tmpfs tmpfs 7,7G 122M 7,6G 2% /dev/shm
/dev/nvme0n1p5 ext4 284G 208G 62G 78% /
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (130 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion: Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago)
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0CTO1WW
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849105/+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 1849105] Re: [snap] cannot pause video with bluetooth headset buttons any more (MPRIS denied by apparmor)
I've been googling, and it appears that Chromium should enable the mpris
interface in the snapcraft YAML for this to work:
https://snapcraft.io/docs/mpris-interface
Except if Chromium actually uses what looks like a dynamic part
("instance" + pid) in the dbus interface name, can it be made to work
without patching Chromium's source?
--
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/1849105
Title:
[snap] cannot pause video with bluetooth headset buttons any more
(MPRIS denied by apparmor)
Status in chromium-browser package in Ubuntu:
New
Bug description:
On Ubuntu 19.04 I could press the button on my Bluetooth headset and
the YouTube video playing in my Chromium would pause/resume. This no
longer works in 19.10. What happens instead is I get an OSD popup
with a NO ENTRY symbol (circle with a diagonal backslash) from gnome-
shell.
I suspect the additional sandboxing of the snap package is the
culprit.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 76.0.3809.100-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
Date: Mon Oct 21 15:04:13 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 208G 62G 78% /
tmpfs tmpfs 7,7G 122M 7,6G 2% /dev/shm
/dev/nvme0n1p5 ext4 284G 208G 62G 78% /
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (130 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion: Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago)
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0CTO1WW
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849105/+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 1849105] Re: cannot pause video with bluetooth headset buttons any more
I'm seeing this in journalctl -b -g chromium:
spal. 19 15:00:35 blynas dbus-daemon[4473]: apparmor="DENIED"
operation="dbus_bind" bus="session"
name="org.mpris.MediaPlayer2.chromium.instance5306" mask="bind" pid=5306
label="snap.chromium.chromium"
spal. 19 15:00:35 blynas chromium_chromium.desktop[4596]:
[5306:5650:1019/150035.747129:ERROR:bus.cc(555)] Failed to get the ownership of
org.mpris.MediaPlayer2.chromium.instance5306: Connection ":1.116" is not
allowed to own the service "org.mpris.MediaPlayer2.chromium.instance5306" due
to AppArmor policy
There's also
spal. 19 14:45:47 blynas kernel: audit: type=1107 audit(1571485547.156:75):
pid=1458 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/"
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects"
mask="send" name="org.bluez" pid=5306 label="snap.chromium.chromium"
peer_pid=1496 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103
hostname=? addr=? terminal=?'
but I think it the bluetooth headset button works via MPRIS, rather than
directly through bluez.
** Summary changed:
- cannot pause video with bluetooth headset buttons any more
+ [snap] cannot pause video with bluetooth headset buttons any more (MPRIS
denied by apparmor)
--
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/1849105
Title:
[snap] cannot pause video with bluetooth headset buttons any more
(MPRIS denied by apparmor)
Status in chromium-browser package in Ubuntu:
New
Bug description:
On Ubuntu 19.04 I could press the button on my Bluetooth headset and
the YouTube video playing in my Chromium would pause/resume. This no
longer works in 19.10. What happens instead is I get an OSD popup
with a NO ENTRY symbol (circle with a diagonal backslash) from gnome-
shell.
I suspect the additional sandboxing of the snap package is the
culprit.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 76.0.3809.100-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
Date: Mon Oct 21 15:04:13 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 208G 62G 78% /
tmpfs tmpfs 7,7G 122M 7,6G 2% /dev/shm
/dev/nvme0n1p5 ext4 284G 208G 62G 78% /
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (130 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion: Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago)
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0CTO1WW
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849105/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :
