[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063831 Title: Clicking on bottom half of applications switches to background application To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967488 Title: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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->monitor)" in meta_win
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 Ubuntu Bugs, which is subscribed to 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() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1970917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874415 Title: [snap] chromedriver doesn't work without --headless under Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1930371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958503] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Nothing very interesting here, the /boot partition on this server is very small (240M) and the upgrade ran out of space while generating an initramfs image. I was able to recover by removing the oldest linux-image package. I was surprised that do-release-upgrade didn't check whether there will be enough free space in /boot beforehand. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18 Uname: Linux 4.15.0-166-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 20 09:41:08 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /home/mgedmin/bin/python, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-01-20 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958503 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532508 Title: Screen contents revealed briefly on resume, before even unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940808] Re: cannot install libssl-dev due to phased updates?
https://launchpad.net/ubuntu/+archivemirrors shows four mirrors in Lithuania, all "up to date". Two of them actually are. One (Vilnius University) has a focal- updates/Packages.gz from 2021-05-04 with libssl-dev version 1.1.1f-1ubuntu2.3, one (LitNET) has a focal-updates/Packages.gz from 2021-07-29 with libssl-dev version 1.1.1f-1ubuntu2.4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940808 Title: cannot install libssl-dev due to phased updates? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1940808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940808] Re: cannot install libssl-dev due to phased updates
On a closer look it may just be a mirror inconsistency. There's no Phased-Update-Percentage field in /var/lib/apt/lists/lt.archive.ubuntu.com_ubuntu_dists_focal- updates_main_binary-amd64_Packages for the libssl-dev entry, and the only available version is 1.1.1f-1ubuntu2.4. ** Changed in: apt (Ubuntu) Status: New => Invalid ** Summary changed: - cannot install libssl-dev due to phased updates + cannot install libssl-dev due to phased updates? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940808 Title: cannot install libssl-dev due to phased updates? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1940808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940808] [NEW] cannot install libssl-dev due to phased updates
Public bug reported: I have two Vagrant boxes: one with Ubuntu 18.04 LTS, one with Ubuntu 20.04 LTS. Both currently refuse to install libssl-dev for me: vagrant@ubuntu2004:~$ sudo apt install libssl-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libssl-dev : Depends: libssl1.1 (= 1.1.1f-1ubuntu2.4) but 1.1.1f-1ubuntu2.5 is to be installed E: Unable to correct problems, you have held broken packages. vagrant@ubuntu2004:~$ apt policy libssl-dev libssl-dev: Installed: (none) Candidate: 1.1.1f-1ubuntu2.4 Version table: 1.1.1f-1ubuntu2.4 500 500 http://lt.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1.1.1f-1ubuntu2.3 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1.1.1f-1ubuntu2 500 500 http://lt.archive.ubuntu.com/ubuntu focal/main amd64 Packages vagrant@ubuntu2004:~$ apt policy libssl1.1 libssl1.1: Installed: 1.1.1f-1ubuntu2.5 Candidate: 1.1.1f-1ubuntu2.5 Version table: *** 1.1.1f-1ubuntu2.5 100 100 /var/lib/dpkg/status 1.1.1f-1ubuntu2.4 500 500 http://lt.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1.1.1f-1ubuntu2.3 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1.1.1f-1ubuntu2 500 500 http://lt.archive.ubuntu.com/ubuntu focal/main amd64 Packages (The 18.04 box is in a similar situation.) packages.ubuntu.com says that libssl1.1 1.1.1f-1ubuntu2.5 is the current version available in focal-updates. I'm pretty sure my VM here doesn't see it because of apt's phased updates (but I only know this because I'm following the blogs on Planet Ubuntu; the error message give no clue!). I have no idea how to resolve this in a generic way (it's an Ansible playbook that fails for me). As a manual fix, I suppose I could downgrade libssl1.1 to 1.1.1f-1ubuntu2.4, but I don't want to hardcode specific version numbers -- I expect 1.1.1f-1ubuntu2.5 will be available universally some time soon? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.6 ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 Uname: Linux 5.4.0-80-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 23 07:08:34 2021 InstallationDate: Installed on 2021-08-11 (11 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940808 Title: cannot install libssl-dev due to phased updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1940808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931077] Re: emergency shell ignores all keyboard input
Ideally, I'd wish it not to stop sshd when /boot/efi becomes unavailable. Or at least bring back the services it stopped when the emergency shell is canceled. More practically, and more on topic to the original reason for this bug report, I'd like it if stopping the emergency shell would print a message on the console, so the instructions to press Enter or Ctrl-D do not appear to still be relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931077 Title: emergency shell ignores all keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931077] Re: emergency shell ignores all keyboard input
Looking at the journal, I think the sequence of events is: - SSD fails last Friday - I log in today over ssh, start messing around - I notice that collectd is not running (since Friday), try to `sudo systemctl start collectd` - systemd tries to bring up collectd's dependency local-fs.target, which need /dev/sda1, which is the failed drive - I figure _that_ out and start editing /etc/fstab to switch the /boot/efi device to the backup on /dev/sdb1 - in the background systemd gives up on local-fs.target and starts emergency.target, which shuts down all the services (including sshd, but not killing my ssh session) and brings up an emergency shell - I finish editing /etc/fstab and do a `sudo mount /boot/efi; sudo systemctl daemon-reload; sudo systemctl start collectd` - systemd notices that local-fs.target is all fine actually and stops the emergency shell - systemd doesn't start all the services that it shut down minutes ago - I exit my ssh session by mistake and now we have the situation where the emergency shell is stopped but its startup message remains, confusing users. (And also no systemd services are running, except for collectd, which is not very useful for getting the system back online.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931077 Title: emergency shell ignores all keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931077] [NEW] emergency shell ignores all keyboard input
Public bug reported: An SSD that held my /boot/efi partition failed, took down local-fs.target, which brought up emergency.target. I ended up with no ssh access, and a message on the local console telling me to press Enter to get a root shell, or press Ctrl-D to continue booting normally. The system did not react to either Enter or Ctrl-D. I could switch between virtual consoles (but nothing was running on them, e.g. no getty), toggle Caps Lock, or reboot with Ctrl+Alt+Del. An emergency console that doesn't accept keyboard input is not a useful emergency console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.47 ProcVersionSignature: Ubuntu 4.15.0-144.148-generic 4.15.18 Uname: Linux 4.15.0-144-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Mon Jun 7 11:18:39 2021 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-144-generic root=/dev/mapper/hostname-root ro SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2019-08-12 (664 days ago) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd08/14/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931077 Title: emergency shell ignores all keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700079] Re: openvpn broken after unattended security upgrade
Bug still there in 18.04.5 LTS. Had an unattended security upgrade of openvpn on May 5, which shut down the old ovpn-server: | May 05 06:14:19 fridge ovpn-server[3384]: event_wait : Interrupted system call (code=4) | May 05 06:14:19 fridge ovpn-server[3384]: /sbin/ip route del 10.8.0.0/24 | May 05 06:14:19 fridge ovpn-server[3384]: openvpn_execve: unable to fork: Resource temporarily unavailable (errno=11) | May 05 06:14:19 fridge ovpn-server[3384]: Exiting due to fatal error and started a new one | May 05 06:14:19 fridge ovpn-server[13115]: OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 27 2021 ... | May 05 06:14:19 fridge ovpn-server[13116]: /sbin/ip link set dev tun1 up mtu 1500 | May 05 06:14:19 fridge ovpn-server[13116]: /sbin/ip addr add dev tun1 local 10.8.0.1 peer 10.8.0.2 | May 05 06:14:19 fridge ovpn-server[13116]: /sbin/ip route add 10.8.0.0/24 via 10.8.0.2 | May 05 06:14:19 fridge ovpn-server[13116]: ERROR: Linux route add command failed: external program exited with error status: 2 and then clients could connect to the VPN server but did not get any network connectivity through it. I'm wondering if there's a race between the old ovpn-server running /sbin/ip route del vs the new opvpn-server running /sbin/ip route add? Also curiously systemctl status openvpn@server a few days later showed | ā openvpn@server.service - OpenVPN connection to server |Loaded: loaded (/lib/systemd/system/openvpn@.service; indirect; vendor preset: enabled) |Active: active (running) since Fri 2021-04-16 07:36:38 EEST; 3 weeks 0 days ago | Docs: man:openvpn(8) |https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage |https://community.openvpn.net/openvpn/wiki/HOWTO | Main PID: 13116 (openvpn) |Status: "Initialization Sequence Completed" | Tasks: 0 (limit: 4915) |CGroup: /system.slice/system-openvpn.slice/openvpn@server.service |ā£ 13116 /usr/sbin/openvpn --writepid /run/openvpn/server.pid --daemon ovpn-server --cd /etc/openvpn --config /etc/openvpn/server.conf | | May 04 19:36:22 fridge ovpn-server[3384]: laurynas2/78.58.248.51:52905 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key | May 04 19:36:22 fridge ovpn-server[3384]: laurynas2/78.58.248.51:52905 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key | May 04 19:36:22 fridge ovpn-server[3384]: laurynas2/78.58.248.51:52905 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 2048 bit RSA | May 04 20:22:09 fridge ovpn-server[3384]: laurynas2/78.58.248.51:52905 [laurynas2] Inactivity timeout (--ping-restart), restarting | May 04 20:22:09 fridge ovpn-server[3384]: laurynas2/78.58.248.51:52905 SIGUSR1[soft,ping-restart] received, client-instance restarting | May 05 00:43:45 fridge ovpn-server[3384]: TLS Error: cannot locate HMAC in incoming packet from [AF_INET]185.200.118.51:33488 | May 05 06:14:19 fridge ovpn-server[3384]: event_wait : Interrupted system call (code=4) | May 05 06:14:19 fridge ovpn-server[3384]: /sbin/ip route del 10.8.0.0/24 | May 05 06:14:19 fridge ovpn-server[3384]: openvpn_execve: unable to fork: Resource temporarily unavailable (errno=11) | May 05 06:14:19 fridge ovpn-server[3384]: Exiting due to fatal error i.e. the PID was of the new instance, but all the log entries were from the old instance. A service openvpn@server restart fixed everything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700079 Title: openvpn broken after unattended security upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1700079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925813] Re: fwupdmgr removed GRUB from my UEFI boot list
Forwarded upstream to https://github.com/fwupd/fwupd/issues/3186 ** Bug watch added: github.com/fwupd/fwupd/issues #3186 https://github.com/fwupd/fwupd/issues/3186 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925813 Title: fwupdmgr removed GRUB from my UEFI boot list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1925813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925840] Re: update-notifier says "(null)" on first boot after a release upgrade
/usr/share/ecryptfs-utils/ecryptfs-record-passphrase appears to be a text file: _Name: Record your encryption passphrase Priority: High OnlyAdminUsers: False DisplayIf: test -e $HOME/.ecryptfs/wrapped-passphrase -a ! -e $HOME/.ecryptfs/.wrapped-passphrase.recorded Terminal: True GettextDomain: ecryptfs-utils Command: "sh -c 'ecryptfs-unwrap-passphrase $HOME/.ecryptfs/wrapped-passphrase 2>/dev/null && echo [Enter] && head -n1 && touch $HOME/.ecryptfs/.wrapped-passphrase.recorded '" _Description: To encrypt your home directory or "Private" folder, a strong passphrase has been automatically generated. Usually your directory is unlocked with your user password, but if you ever need to manually recover this directory, you will need this passphrase. Please print or write it down and store it in a safe location. If you click "Run this action now", enter your login password at the "Passphrase" prompt and you can display your randomly generated passphrase. Otherwise, you will need to run "ecryptfs-unwrap-passphrase" from the command line to retrieve and record your generated passphrase. AFAIU update-manager is supposed to show the text from it, but instead it shows the (null). I don't know exactly how ecryptfs communicates with update-notifier. Running strings on the pam_ecryptfs PAM module shows /var/lib/update-notifier/user.d/ecryptfs-record-passphrase /var/lib/update-notifier/dpkg-run-stamp the first of those is a symlink to /usr/share/ecryptfs-utils/ecryptfs- record-passphrase, the second is a regular empty file. I think pam_ecryptfs creates the symlink and touches the stamp file to wake up a sleeping update-notifier? Or maybe something more complicated, since I was trying to reproduce the bug with sudo touch /var/lib/update-notifier/dpkg-run-stamp and it did not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925840 Title: update-notifier says "(null)" on first boot after a release upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1925840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925840] [NEW] update-notifier says "(null)" on first boot after a release upgrade
Public bug reported: Upgraded my Ubuntu 20.10 to 21.04 with sudo do-release-upgrade -d, rebooted, and got this window in my face a couple of minutes after booting (see attached image). It is shown by update-notifier and says (null), then gives me an option to [Perform this action]. lsof -p $(pidof update-notifier) shows ... update-no 4269 mg 16r REG 259,5 1025 14027136 /usr/share/ecryptfs-utils/ecryptfs-record-passphrase so it is probably trying to tell me to record my ecryptfs recovery passphrase? (For the record, my ~/Private is correctly unlocked and mounted.) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: update-notifier 3.192.40 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 19:47:59 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (680 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: update-notifier UpgradeStatus: Upgraded to hirsute on 2021-04-23 (0 days ago) ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Attachment added: "update-notifier.png" https://bugs.launchpad.net/bugs/1925840/+attachment/5491507/+files/Ekrano%20nuotrauka%20i%C5%A1%202021-04-23%2019-44-27.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925840 Title: update-notifier says "(null)" on first boot after a release upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1925840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900121] Re: firmware upgrades remove the ubuntu boot loader from EFI boot vars
I did a fundamental mistake and changed two things at a time: 1. deleted the duplicate Linux-Firmware-Updater boot entry with efibootmgr -B -b 0002 2. decided to apply the two firmware upgrades separately I ran fwupdmgr upgrade twice, selected the Intel ME upgrade first, rejected the System Firmware upgrade, rebooted, saw the upgrade being applied, after which the laptop booted into Ubuntu. I ran fwupdmgr upgrade again, let it upgrade the system firmware, rebooted, and it worked fine. I wonder if my mistake was trying to upgrade both? I wonder if it was the system firmware deleting Boot0001 both initially (when that was pointing to grub) and in comment #13 (when that was pointing to Linux-Firmware-Updater) when it saw a bunch of capsules it didn't like? efibootmgr currently looks like this: | BootCurrent: 0003 | Timeout: 0 seconds | BootOrder: 0003,001A,,0018,0019,001B,001C,001D,001E,001F,0020,0021,0027,0001 | Boot* Windows Boot Manager | Boot0001* Linux-Firmware-Updater | Boot0003* ubuntu and it looked mostly the same before and after each reboot, with just a BootNext: 0001 showing up after each fwupmgr upgrade call. Nothing is removing Boot0001 when the firmware upgrades are successful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900121 Title: firmware upgrades remove the ubuntu boot loader from EFI boot vars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900121] Re: firmware upgrades remove the ubuntu boot loader from EFI boot vars
I'm now reliably in this situation: efibootmgr shows | BootCurrent: 0003 | Timeout: 0 seconds | BootOrder: 0003,001A,,0018,0019,001B,001C,001D,001E,001F,0020,0021,0002,0027 | Boot* Windows Boot Manager | Boot0002* Linux-Firmware-Updater | Boot0003* ubuntu ... I run fwupdmgr upgrade, then check efibootmgr before the reboot and see | BootNext: 0001 | BootCurrent: 0003 | Timeout: 0 seconds | BootOrder: 0003,001A,,0018,0019,001B,001C,001D,001E,001F,0020,0021,0002,0027,0001 | Boot* Windows Boot Manager | Boot0001* Linux-Firmware-Updater | Boot0002* Linux-Firmware-Updater | Boot0003* ubuntu then I reboot and see the grub menu instead of the firmware upgrade, and when I boot I see | BootCurrent: 0003 | Timeout: 0 seconds | BootOrder: 0003,001A,,0018,0019,001B,001C,001D,001E,001F,0020,0021,0002,0027 | Boot* Windows Boot Manager | Boot0002* Linux-Firmware-Updater | Boot0003* ubuntu If I try to manually boot the Linux Firmware Installer boot entry, I get a bunch of errors: https://twitter.com/mgedmin/status/1385605275948830720/photo/1 (The reason why I had two Linux-Firmware-Updater entries is bug 1925813. I got ubuntu on Boot0003 after I manually ran grub-install while Boot0001 and Boot0002 were both Linux-Firmware-Updater.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900121 Title: firmware upgrades remove the ubuntu boot loader from EFI boot vars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900121] Re: firmware upgrades remove the ubuntu boot loader from EFI boot vars
This happened again, while trying to upgrade the Lenovo ThinkPad X390 system firmware from version 1.70 to 1.71. I missed the initial details again, unfortunately -- didn't see what the computer was doing while rebooting, came back to see it booted into Windows with the 'ubuntu' boot menu entry missing from EFI vars, and the firmware update not applied. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900121 Title: firmware upgrades remove the ubuntu boot loader from EFI boot vars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925813] [NEW] fwupdmgr removed GRUB from my UEFI boot list
Public bug reported:
== Introduction ==
This is going to sound very similar to bug 1900121, but I believe it's a
different bug.
Today I tried to upgrade the system firmware and the Intel ME firmware
on my ThinkPad X390 with `fwupdmgr upgrade` (after attempting to upgrade
with snap-store failed with no indication of what was wrong, but that's
not related to this bug).
When `fwupdmgr` asked me to reboot, I confirmed, and then I was called
away from my laptop for a few minutes. I didn't see what happened
during boot, but when I came back, I found my laptop booted into
Windows. (This is a bug -- bug 1900121 probably -- but not the bug I'm
reporting now). Since I was already there, I let Windows install its
updates, which could be important. A few Windows reboots later I went
into the UEFI setup to restore Ubuntu in the boot priority list, but I
didn't find it there.
Then I booted a GRUB shell from a USB drive (by pressing F12 to get the
boot menu), used `configfile (hd1,gpt1)/efi/ubuntu/grub.cfg` to boot my
primary OS, and restored the `ubuntu` boot entry by running `sudo grub-
install /dev/nvme0n1`.
Then I checked with `sudo fwupdmgr upgrade` whether the firmware
upgrades had been applied or not. They had not, so I let fwupdmgr
install them. Then I did not let fwupdmgr reboot but decided to check
the boot priority list in `efibootmgr -v`.
== The bug ==
fwupdmgr removed the `ubuntu` entry and replaced it with a second copy
of the `Linux-Firmware-Updater` boot entry.
I suspect it's because the BootCurrent was pointing to the USB flash
drive that I used for recovery, rather than the regular ubuntu entry.
== Details ==
efibootmgr -v when I rescue-booted:
| BootCurrent: 001E
| Timeout: 0 seconds
| BootOrder:
001A,,0018,0019,001B,001C,001D,001E,001F,0020,0021,0002,0027
| Boot* Windows Boot Manager
HD(1,GPT,efd54dec-f70c-4b32-9480-c2dd0043ea0d,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...e.^?...
| Boot0002* Linux-Firmware-Updater
HD(1,GPT,efd54dec-f70c-4b32-9480-c2dd0043ea0d,0x800,0x82000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.d.x.6.4...e.f.i...
| Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
| Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
| Boot0012 Diagnostic Splash Screen
FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
| Boot0013 Lenovo Diagnostics
FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
| Boot0014 Regulatory Information
FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
| Boot0015 Startup Interrupt Menu
FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
| Boot0016 Rescue and Recovery
FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
| Boot0017 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
| Boot0018* USB CD
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
| Boot0019* USB FDD
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
| Boot001A* NVMe0
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
| Boot001B* NVMe1
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a401)
| Boot001C* ATA HDD0
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f602)
| Boot001D* ATA HDD1
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
| Boot001E* USB HDD
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
| Boot001F* PXE BOOT
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
| Boot0020 Other CD
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35406)
| Boot0021 Other HDD
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f606)
| Boot0022* IDER BOOT CDROM PciRoot(0x0)/Pci(0x14,0x0)/USB(11,1)
| Boot0023* IDER BOOT Floppy PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0)
| Boot0024* ATA HDD
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
| Boot0025* ATAPI CD
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
| Boot0026 ThinkShield secure wipe
FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
| Boot0027* LENOVO CLOUD
VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi)
| Boot0001* ubuntu
HD(1,MBR,0x224ca4b1,0x1ad80,0x7359280)/File(\EFI\ubuntu\shimx64.efi)
efibootmgr -v after I ran grub-install /dev/nvme0n1
| BootCurrent: 001E
| Timeout: 0 seconds
| BootOrder:
0001,001A,,0018,0019,001B,001C,001D,001E,001F,0020,0021,0002,0027
| Boot* Windows Boot Manager
[Bug 1925182] Re: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!)
Thank you for the reproducer! I was about to comment suggesting a race condition, since I have clamav- freshclam installed on several machines but only one of them reported a failure. Then I looked closer and realized that my monitoring is incomplete. I have clamav-freshclam installed on two bionic and two focal servers. It failed to restart on both bionic servers (but only one of them was monitoring the presence of the freshclam process). Both focal servers are fine. (This failure doesn't break the unattended upgrade -- dpkg thinks everything is fine. If I didn't have other monitoring set up, I would not have noticed that I'm not getting AV database updates, and the problem would self-correct after the next reboot.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925182 Title: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1925182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707611 Title: Sound does not automatically switch to HDMI when connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925182] [NEW] ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!)
Public bug reported: An unattended upgrade upgraded clamav last night, after which clamav- freshclam failed to start: # systemctl status clamav-freshclam ā clamav-freshclam.service - ClamAV virus database updater Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2021-04-20 06:59:59 EEST; 6h ago Docs: man:freshclam(1) man:freshclam.conf(5) https://www.clamav.net/documents Main PID: 18433 (code=exited, status=2) Apr 20 06:59:59 fridge systemd[1]: Started ClamAV virus database updater. Apr 20 06:59:59 fridge freshclam[18433]: WARNING: Ignoring deprecated option SafeBrowsing at /etc/clamav/freshclam.conf:22 Apr 20 06:59:59 fridge freshclam[18433]: ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log). Apr 20 06:59:59 fridge freshclam[18433]: ERROR: initialize: libfreshclam init failed. Apr 20 06:59:59 fridge freshclam[18433]: ERROR: Initialization error! Apr 20 06:59:59 fridge freshclam[18433]: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!). Apr 20 06:59:59 fridge systemd[1]: clamav-freshclam.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Apr 20 06:59:59 fridge systemd[1]: clamav-freshclam.service: Failed with result 'exit-code'. The permissions of /var/log/clamav/freshclam.log are 0640 clamav:adm; the parent directory is mode 0755 clamav:clamav. Restarting the clamav-freshclam service makes the error go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: clamav-freshclam 0.103.2+dfsg-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Tue Apr 20 13:39:47 2021 ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: clamav UpgradeStatus: Upgraded to bionic on 2019-09-11 (586 days ago) ** Affects: clamav (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925182 Title: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1925182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923445] [NEW] netplan generator segfaults, leaves server with no working DNS
Public bug reported: A server I have stopped being able to resolve DNS queries. According to resolvectl status, no DNS servers have been configured. /etc/netplan/01-netcfg.yaml has networking configuration that looks correct to me, and if I do 'netplan try', I get working a network. Somehow systemd's configuration diverged from netplan's. Before I did the 'netplan try', I looked at /run/systemd/network/. There was one file in it, /run/systemd/network/, with just [Match] [Link] WakeOnLan=magic in it. The timestamp on that file is Apr 7, 06:28, which is almost 24 hours since the last reboot. journalctl shows this at around that timestamp: Apr 07 06:27:56 momsen systemd[1]: Starting Daily apt upgrade and clean activities... Apr 07 06:27:56 momsen postfix/smtpd[38430]: disconnect from unknown[121.66.35.37] ehlo=1 auth=0/1 quit=1 commands=2/3 Apr 07 06:28:01 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:01 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:01 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:01 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:01 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:01 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:01 momsen systemd[1]: Reloading. Apr 07 06:28:01 momsen kernel: traps: netplan[38842] general protection fault ip:55c8cfed3cf0 sp:7fff25300030 error:0 in generate[55c8cfed+8000] Apr 07 06:28:01 momsen systemd[38840]: /usr/lib/systemd/system-generators/netplan terminated by signal SEGV. Apr 07 06:28:01 momsen systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket ā /run/dbus/system_bus_socket; please update the unit file accordingly. Apr 07 06:28:01 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:01 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:02 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:02 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:02 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:02 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:02 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:02 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:02 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:02 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:02 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:02 momsen dbus-daemon[548]: [system] Reloaded configuration Apr 07 06:28:02 momsen systemd[1]: Reexecuting. Apr 07 06:28:02 momsen systemd[1]: systemd 245.4-4ubuntu3.6 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) Apr 07 06:28:02 momsen systemd[1]: Detected architecture x86-64. Apr 07 06:28:02 momsen kernel: traps: netplan[39030] general protection fault ip:563995b5acf0 sp:7ffc8299c2f0 error:0 in generate[563995b57000+8000] Apr 07 06:28:02 momsen systemd[39028]: /usr/lib/systemd/system-generators/netplan terminated by signal SEGV. ... Apr 07 06:28:03 momsen kernel: traps: netplan[39132] general protection fault ip:55f15ae8ecf0 sp:7fff9cbcb100 error:0 in generate[55f15ae8b000+8000] Apr 07 06:28:03 momsen systemd[39130]: /usr/lib/systemd/system-generators/netplan terminated by signal SEGV. ... Apr 07 06:28:07 momsen systemd-udevd[429]: /run/systemd/network/10-netplan-enp35s0.link: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add OriginalName=* in the [Match] section. Apr 07 06:28:08 momsen systemd[1]: Reloading. Apr 07 06:28:08 momsen kernel: traps: netplan[40203] general protection fault ip:55bbc1fe6cf0 sp:7ffedcbfea00 error:0 in generate[55bbc1fe3000+8000] Apr 07 06:28:08 momsen systemd[40201]: /usr/lib/systemd/system-generators/netplan terminated by signal SEGV. ... Apr 07 06:28:22 momsen systemd[1]: apt-daily-upgrade.service: Succeeded. Apr 07 06:28:22 momsen systemd[1]: Finished Daily apt upgrade and clean activities. /var/crash is empty, so I'm afraid I don't have any information about the netplan generator segfault. I tried running systemctl daemon-reload to see if I could provoke a crash again, and either that command doesn't run all the generators, or the netplan generator failed to crash. Or maybe something was broken during the nightly unattended upgrade on Apr 7 causing the crash -- e.g. I find it somewhat suspicious that /var/log/apt/history.log shows netplan.io and libnetplan0 being upgraded in separate transactions? Start-Date: 2021-04-07 06:27:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libnetplan0:amd64
[Bug 1919343] [NEW] Have ignore squashfs by default
Public bug reported: I've noticed today that collectd tracks disk usage of every version of every snap, since those are squashfs mounts. There are rather a lot of those: $ ls -ld /var/lib/collectd/rrd/$(hostname -f)/df-snap*|wc -l 262 I suggest adding FSType squashfs to the block in the default /etc/collectd/collectd.conf. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: collectd 5.9.2.g-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 16 17:37:45 2021 InstallationDate: Installed on 2016-09-10 (1648 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: collectd UpgradeStatus: Upgraded to focal on 2020-04-26 (324 days ago) ** Affects: collectd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919343 Title: Have ignore squashfs by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1919343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842432] Re: service postgrey reload fails
Still a problem in 20.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842432 Title: service postgrey reload fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgrey/+bug/1842432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900121] Re: firmware upgrades remove the ubuntu boot loader from EFI boot vars
> After charging battery to 12% and updating by "fwupdmgr upgrade", computer restart -> show "Check power failure,please insert the power source or charge the power" -> power on normally. The error message give the impression that you had the power cable disconnected and battery at 12% while trying to update the firmware? When I tried this, the power cable was plugged in. (Possibly the error message is just misleading. I regret not paying close attention when I did that the first time, so I didn't notice any error messages that might have been displayed, as long as they didn't require a keypress to dismiss.) > Have you ever entered BIOS (or Setup) and pressed "F9". It will excute "Load default"(or "Setup default"). No, I haven't. > By the way, althrough you charge battery to 12%, the bios upgrades still failed due to low power. When the battery is above 50% ,bios will update successfully. Oh, that is interesting information and it explains one mystery at least! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900121 Title: firmware upgrades remove the ubuntu boot loader from EFI boot vars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900121] Re: firmware upgrades remove the ubuntu boot loader from EFI boot vars
If it helps, I have in my notes the full output of `efibootmgr -v` from Oct 16 with the 'ubuntu' entry missing, and then the full output after I ran grub-install to recover. I do not have a full output of `efibootmgr -v` from earlier, but I do have just the `ubuntu` entry from February, after a little misadventure with creating UEFI-bootable USB drives messed up my EFI boot vars and I successfully recovered by running `grub-install`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900121 Title: firmware upgrades remove the ubuntu boot loader from EFI boot vars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900121] Re: firmware upgrades remove the ubuntu boot loader from EFI boot vars
1. My notes say "LENOVO System firmware 0.1.67 -> 0.1.70, also described
as Lenovo ThinkPad T490s/ThinkPad X390 (W-BIOS) System Firmware 1.70".
I have recorded in my notes that after I attempted the update from snap-
store (at 7% battery), I ran fwupdmgr get-upgrades in a terminal and saw
ā Update State:success
ā Update Error:failed to update_prepare using upower: Cannot
install update when battery is not at least 10% unless forced
and then I checked the battery level again (the laptop was plugged in at
the time), saw it had risen to 12%, so I ran
fwupdmgr upgrade
and restarted when prompted. (And then saw the firmware upgrade
process, and rebooted again, and got Windows, with no Ubuntu in the UEFI
boot menu, after which I proceeded to disable secure boot and boot from
my USB key).
2. `fwupdmgr get-history` today shows
āāSystem Firmware:
ā ā Device ID: ca8e899e46f1da1776d16410bc92f2cf0d963433
ā ā Previous version:0.1.67
ā ā Update State:success
ā ā Update Error:failed to update to 117474352: battery level is too
low
ā ā Last modified: 2020-10-17 06:17
ā ā GUID:6300ba52-d9ea-4ca0-88f9-f89ef73cc07b
ā ā Device Flags:ā¢ Internal device
ā āā¢ Updatable
ā āā¢ Requires AC power
ā āā¢ Supported on remote server
ā āā¢ Needs a reboot after installation
ā āā¢ Reported to remote server
ā āā¢ Cryptographic hash verification is available
ā āā¢ Device is usable for the duration of the update
ā ā
ā āāThinkPad T490s/X390 (W-BIOS for Machine types: 20NX, 20NY, 20Q0, 20Q1)
System Update:
ā New version: 0.1.70
ā Remote ID: lvfs
ā Summary: Lenovo ThinkPad T490s/ThinkPad X390/ThinkPad System
Firmware
ā License: Proprietary
ā Size: 25,1Ā MB
ā Created: 2020-08-31
ā Urgency: High
ā Vendor:Lenovo Ltd.
ā Description: Lenovo ThinkPad T490s/ThinkPad X390 (W-BIOS) System
Firmware 1.70
ā
ā The computer will be restarted automatically after updating BIOS
completely. Do NOT turn off your computer or remove the AC adaptor while update
is in progress.
ā
ā This stable release fixes the following issues:
ā
āā¢ Fixed an issue where BIOS might generate 1802 error with L850 WWAN.
āā¢ Fixed an issue where system may occur post hang issue with TBT dock.
āā¢ Fixed an issue where MEFW LVFS file can't be updated.
3. That was my USB drive with a custom grub.cfg that lets me pick one of
several Ubuntu ISO images. https://mg.pov.lt/blog/booting-iso-from-
usb-2020.html has more information, but really, all I did was disable
secure boot, select the USB drive in the UEFI boot menu, get me a GRUB
menu, cancel it, get the GRUB command line and do a bunch of ls
(hd1,gpt1) to figure out where everything is, then chain-boot
with
grub> configfile (hd1,gpt5)/boot/grub/grub.cfg
to get the actual grub config from the root partition of the installed
Ubuntu system. After which I looked at `efibootmgr -v`, saw that it
didn't have an entry for ubuntu, and then I ran `sudo grub-install
/dev/nvme0n1`, then ran `efibootmgr -v` and saw that the ubuntu entry is
back.
It was the next day when snap-store offered the system firmware upgrade
to version 1.70 again that I noticed /sys/class/dmi/id/bios_version
still showing 1.67.
I haven't recorded in my notes how I upgraded again (snap-store or
fwupdmgr in a terminal), but I have written down that this time I
checked efibootmgr -v before rebooting, and that I saw both ubuntu and
Linux-Firmware-Updater entries, with BootNext pointing to Linux-
Firmware-Updater. That particular upgrade was uneventful: it rebooted
back into Ubuntu, and /sys/class/dmi/id/bios_version showed the new
firmware version ("N2JET92W (1.70 )").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900121
Title:
firmware upgrades remove the ubuntu boot loader from EFI boot vars
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900121/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008380] Re: mutt -f =FOO and mutt -f +FOO are broken
It's 2020 and I'm still trying to fix this. Upstream moved to GitHub so: - https://github.com/scop/bash-completion/pull/463 - https://github.com/scop/bash-completion/pull/465 fix mutt -f +foo and mutt -f =foo for me on Ubuntu 20.10. On Ubuntu 18.04 LTS, though, mutt -f =foo remains broken, and I don't understand why. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008380 Title: mutt -f =FOO and mutt -f +FOO are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1008380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901847] Re: snapd fails to shut down, gets killed after 1m30s during reboot
Today this happened again. I installed a bunch of updates with update- manager, was prompted to reboot, checked with 'snap refresh --list' to see if there were any snap updates pending (there weren't), and let update-manager do the reboot. snapd took 1m30s to shut down. lapkr. 11 09:08:29 blynas systemd[1]: Stopped D-Bus System Message Bus. lapkr. 11 09:08:31 blynas dbus-daemon[992]: [system] Activating systemd to hand-off: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.2851' (uid=0 pid=3021119 comm="/usr/bin/gdbus call --system --dest org.freedeskto" label="unconfined") lapkr. 11 09:08:38 blynas AptDaemon.Worker[2993491]: INFO: Finished transaction /org/debian/apt/transaction/dff292185c0a4a19af71998f9f7e813c lapkr. 11 09:08:38 blynas org.debian.apt[2993491]: /usr/lib/python3/dist-packages/aptdaemon/progress.py:490: Warning: Source ID 49 was not found when attempting to remove it lapkr. 11 09:08:38 blynas org.debian.apt[2993491]: GLib.source_remove(id) lapkr. 11 09:08:38 blynas org.debian.apt[2993491]: /usr/lib/python3/dist-packages/aptdaemon/progress.py:490: Warning: Source ID 50 was not found when attempting to remove it lapkr. 11 09:08:38 blynas org.debian.apt[2993491]: GLib.source_remove(id) lapkr. 11 09:08:38 blynas org.debian.apt[2993491]: /usr/lib/python3/dist-packages/aptdaemon/progress.py:490: Warning: Source ID 51 was not found when attempting to remove it lapkr. 11 09:08:38 blynas org.debian.apt[2993491]: GLib.source_remove(id) lapkr. 11 09:08:38 blynas org.debian.apt[2993491]: 09:08:38 AptDaemon.Worker [INFO]: Finished transaction /org/debian/apt/transaction/dff292185c0a4a19af71998f9f7e813c lapkr. 11 09:08:53 blynas snapd[1016]: daemon.go:586: WARNING: cannot gracefully shut down in-flight snapd API activity within: 25s lapkr. 11 09:08:56 blynas dbus-daemon[992]: [system] Failed to activate service 'org.freedesktop.PackageKit': timed out (service_start_timeout=25000ms) lapkr. 11 09:08:56 blynas dbus-daemon[992]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) lapkr. 11 09:09:58 blynas systemd[1]: snapd.service: State 'stop-sigterm' timed out. Killing. lapkr. 11 09:09:58 blynas systemd[1]: snapd.service: Killing process 1016 (snapd) with signal SIGKILL. lapkr. 11 09:09:58 blynas systemd[1]: snapd.service: Main process exited, code=killed, status=9/KILL lapkr. 11 09:09:58 blynas systemd[1]: snapd.service: Failed with result 'timeout'. lapkr. 11 09:09:58 blynas systemd[1]: Stopped Snap Daemon. lapkr. 11 09:09:58 blynas systemd[1]: snapd.service: Triggering OnFailure= dependencies. lapkr. 11 09:09:58 blynas systemd[1]: Requested transaction contradicts existing jobs: Transaction for snapd.failure.service/start is destructive (swapfile.swap has 'stop' job queued, but 'start' is included in transaction). lapkr. 11 09:09:58 blynas systemd[1]: snapd.service: Failed to enqueue OnFailure= job, ignoring: Transaction for snapd.failure.service/start is destructive (swapfile.swap has 'stop' job queued, but 'start' is included in transaction). lapkr. 11 09:09:58 blynas systemd[1]: Stopped target Basic System. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901847 Title: snapd fails to shut down, gets killed after 1m30s during reboot To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903354] [NEW] /usr/share/weechat/python/queue.py shadows stdlib module, cannot be imported
Public bug reported: There was a bug in a weechat script in my ~/.weechat/python/autoload, which triggered apport's exception hook. The apport hook failed with Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 72, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 32, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 12, in import os, glob, subprocess, os.path, time, pwd, sys, requests_unixsocket File "/usr/lib/python3/dist-packages/requests_unixsocket/__init__.py", line 1, in import requests File "/usr/lib/python3/dist-packages/requests/__init__.py", line 43, in import urllib3 File "/usr/lib/python3/dist-packages/urllib3/__init__.py", line 7, in from .connectionpool import HTTPConnectionPool, HTTPSConnectionPool, connection_from_url File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 28, in from six.moves import queue File "", line 1039, in _handle_fromlist File "/usr/lib/python3/dist-packages/six.py", line 92, in __get__ result = self._resolve() File "/usr/lib/python3/dist-packages/six.py", line 115, in _resolve return _import_module(self.mod) File "/usr/lib/python3/dist-packages/six.py", line 82, in _import_module __import__(name) File "/usr/share/weechat/python/queue.py", line 277 if args == "": ^ TabError: inconsistent use of tabs and spaces in indentation which highligts two problems: - the 'queue' weechat script is in sys.path and shadows a standard library module - it is using mixed tabs and spaces for indentation, which is forbidden in Python 3 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: weechat-scripts (not installed) ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 22:18:39 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (512 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: weechat-scripts UpgradeStatus: Upgraded to groovy on 2020-10-23 (14 days ago) ** Affects: weechat-scripts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903354 Title: /usr/share/weechat/python/queue.py shadows stdlib module, cannot be imported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weechat-scripts/+bug/1903354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903336] Re: plocate -r says invalid option -- 'r'
This is fixed in upstream version 1.0.5, with this commit: https://git.sesse.net/?p=plocate;a=commitdiff;h=f7dddf5cd31d26be12c4c4d718d257fe012fe368 Looking at https://sources.debian.org/src/plocate/1.0.7-1/debian/changelog/ I think there may be some other changes worth SRUing: - make /etc/cron.daily/plocate cleanly if the package has been removed (in 1.0.5-3) - Remove locate alternative when package is removed (in prerm) (in 1.0.6-1). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903336 Title: plocate -r says invalid option -- 'r' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plocate/+bug/1903336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903336] [NEW] plocate -r says invalid option -- 'r'
Public bug reported: $ plocate --help ... -r, --regexp interpret patterns as basic regexps (slow) ... $ plocate -r xyzzy plocate: invalid option -- 'r' Note that `plocate --regexp xyzzy` works fine. This is fixed in some upstream version (I tested by pulling in a docker image of debian/sid, which has plocate 1.0.7). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: plocate 1.0.4-4 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 19:52:49 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (512 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: plocate UpgradeStatus: Upgraded to groovy on 2020-10-23 (14 days ago) ** Affects: plocate (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903336 Title: plocate -r says invalid option -- 'r' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plocate/+bug/1903336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899356 Title: [snap] file chooser has no icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901847] Re: snapd fails to shut down, gets killed after 1m30s during reboot
It would be nice if snapd would log something about what it's doing to the journal. I did run a `snap refresh --list` before rebooting and I saw that a chromium update was being delayed since chromium was running. I closed chromium a few seconds before initiating the reboot. Perhaps snapd thought it was a good opportunity to start the upgrade? After the reboot I did a manual `sudo snap refresh` to be sure chromium would be upgraded before I launched it, and I saw the progress bar go from 0 to 100%, rather slowly. I wasn't paying much attention, but I think it said it was downloading the new version of chromium. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901847 Title: snapd fails to shut down, gets killed after 1m30s during reboot To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901847] [NEW] snapd fails to shut down, gets killed after 1m30s during reboot
Public bug reported: I installed some updated and was prompted to reboot. The shutdown part of the reboot took a long time (over 1 minute 30 seconds), and I saw that systemd was waiting for snapd to shut down cleanly before killing it with SIGKILL 90 seconds later. journalctl -b -1 -e shows this: spal. 28 11:03:02 blynas systemd[1]: NetworkManager.service: Succeeded. spal. 28 11:03:02 blynas systemd[1]: Stopped Network Manager. spal. 28 11:03:02 blynas systemd[1]: Stopping D-Bus System Message Bus... spal. 28 11:03:02 blynas systemd[1]: dbus.service: Succeeded. spal. 28 11:03:02 blynas systemd[1]: dbus.service: Unit process 989 (dbus-daemon) remains running after unit stopped. spal. 28 11:03:02 blynas systemd[1]: dbus.service: Unit process 322309 (python3) remains running after unit stopped. spal. 28 11:03:02 blynas systemd[1]: Stopped D-Bus System Message Bus. spal. 28 11:03:02 blynas thermald[1025]: terminating on user request .. spal. 28 11:03:03 blynas systemd[1]: thermald.service: Succeeded. spal. 28 11:03:03 blynas systemd[1]: Stopped Thermal Daemon Service. spal. 28 11:03:03 blynas clamd[1036]: Wed Oct 28 11:03:03 2020 -> --- Stopped at Wed Oct 28 11:03:03 2020 spal. 28 11:03:03 blynas clamd[1036]: Wed Oct 28 11:03:03 2020 -> Socket file removed. spal. 28 11:03:03 blynas systemd[1]: clamav-daemon.service: Succeeded. spal. 28 11:03:03 blynas systemd[1]: Stopped Clam AntiVirus userspace daemon. spal. 28 11:03:26 blynas snapd[1013]: daemon.go:586: WARNING: cannot gracefully shut down in-flight snapd API activity within: 25s spal. 28 11:04:31 blynas systemd[1]: snapd.service: State 'stop-sigterm' timed out. Killing. spal. 28 11:04:31 blynas systemd[1]: snapd.service: Killing process 1013 (snapd) with signal SIGKILL. spal. 28 11:04:31 blynas systemd[1]: snapd.service: Main process exited, code=killed, status=9/KILL spal. 28 11:04:31 blynas systemd[1]: snapd.service: Failed with result 'timeout'. spal. 28 11:04:31 blynas systemd[1]: Stopped Snap Daemon. spal. 28 11:04:31 blynas systemd[1]: snapd.service: Triggering OnFailure= dependencies. spal. 28 11:04:31 blynas systemd[1]: Requested transaction contradicts existing jobs: Transaction for snapd.failure.service/start is destructive (systemd-remount-fs.service has 'stop' job queued, but 'start' is included in transaction). spal. 28 11:04:31 blynas systemd[1]: snapd.service: Failed to enqueue OnFailure= job, ignoring: Transaction for snapd.failure.service/start is destructive (systemd-remount-fs.service has 'stop' job queued, but 'start' is included in transaction). spal. 28 11:04:31 blynas systemd[1]: Stopped target Basic System. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: snapd 2.47.1+20.10.1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 12:29:28 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (503 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: snapd UpgradeStatus: Upgraded to groovy on 2020-10-23 (5 days ago) modified.conffile..etc.sudoers.d.99-snapd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/99-snapd.conf'] ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901847 Title: snapd fails to shut down, gets killed after 1m30s during reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1901847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900107] Re: fwupd is eating 100% CPU for 30 minutes
No crash file in /var/crash, unfortunately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900107 Title: fwupd is eating 100% CPU for 30 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900223] Re: snap refresh --list shows an available update but snap refresh doesn't install it
I wish snap wouldn't lie to me by saying "all snaps are up to date" when it means "there's an outdated snap but I cannot update it because the application is running". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900223 Title: snap refresh --list shows an available update but snap refresh doesn't install it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1900223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900223] Re: snap refresh --list shows an available update but snap refresh doesn't install it
Yes, but I assumed that in order to stop snap-store it was enough to close its window. Your question made me doubt that, and I see that pgrep snap-store finds it running. This probably explains everything, except for one question: how is a regular user expected to update snap-store? Running pkill snap-store in a terminal seems like suboptimal UX. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900223 Title: snap refresh --list shows an available update but snap refresh doesn't install it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1900223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900223] [NEW] snap refresh --list shows an available update but snap refresh doesn't install it
Public bug reported: snap-store tells me there's an update available for snap-store. I tried to tell it to update itself, but it says it can't because the application is currently running. Fair enough, that's not the bug I'm reporting here, just some background information. snap refresh --list shows NameVersion Rev Publisher Notes snap-store 3.36.0-82-g80486d0 481 canonicalā - so I run `sudo snap refresh` to install the update (after closing snap-store), and it tells me Visi snap paketai yra atnaujinti. (that's "all snaps are up to date"; I can't figure out how to make snap speak English -- it ignores LC_ALL=C/LANGUAGE=en) snap info snap-store shows name:snap-store summary: Snap Store is a graphical desktop application for discovering, installing and managing snaps on Linux. publisher: Canonicalā store-url: https://snapcraft.io/snap-store contact: https://bugs.launchpad.net/snap-store/ license: unset description: | Snap Store showcases featured and popular applications with useful descriptions, ratings, reviews and screenshots. Applications can be found either through browsing categories or by searching. Snap Store can also be used to switch channels, view and alter snap permissions and view and submit reviews and ratings. Snap Store is based on GNOME Software, optimized for the Snap experience. commands: - snap-store - snap-store.ubuntu-software - snap-store.ubuntu-software-local-file snap-id: gjf3IPXoRiipCu9K0kVu52f0H56fIksg tracking: latest/stable/ubuntu-20.04 refresh-date: 2020-06-22 channels: latest/stable:3.31.1+git187.84b64e0b 2020-04-22 (415) 45MB - latest/candidate: 3.31.1+git189.991d1d1d 2020-08-09 (472) 45MB - latest/beta: 3.36.0-82-g80486d0 2020-09-11 (481) 53MB - latest/edge: 20200414.ac9047f 2020-04-14 (375) 50MB - installed: 3.36.0-80-g208fd61(467) 52MB - and I don't understand what is going on here with the phantom update that is both available and not. (also, I don't see latest/stable/ubuntu-20.04 among the channels, which also feels strange) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: snapd 2.46.1+20.04 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 09:35:47 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (492 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: snapd UpgradeStatus: Upgraded to focal on 2020-04-24 (175 days ago) modified.conffile..etc.sudoers.d.99-snapd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/99-snapd.conf'] ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900223 Title: snap refresh --list shows an available update but snap refresh doesn't install it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1900223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900121] Re: firmware upgrades remove the ubuntu boot loader from EFI boot vars
A strange thing happened today: snap-software told me there are important system upgrades available, and one of those was the same firmware upgrade for the x390 (1.67 -> 1.70) that I was sure I'd already installed yesterday. fwupdmgr get-updates and /sys/class/dmi/id/bios_version confirmed that no, my firmware was still at version 1.67, despite me seeing the upgrade process with my own eyes yesterday. So I installed the update again, took a snapshot of efibootmgr -v for my notes, saw that it had all the right entries (BootNext: 0002 aka Linux- Firmware-Updater, BootCurrent: 0001 aka ubuntu), rebooted, saw the firmware upgrade process again (two capsules, nice large translated installing text in the middle of the screen with a |/- spinner above it overlapping the huge LENOVO logo, then a red progress bar, then another reboot, then a black screen with a "self-healing bios backup" and an increasing percentage text, then another reboot. I went into the boot order menu (F12) and saw that ubuntu was still there. I booted and /sys/class/dmi/id/bios_version is showing 1.70 this time. I have no explanation, only theories. Maybe I did something yesterday (boot into the Linux Firmware Upgrade target with no upgrade queued?) that made the laptop think the firmware got corrupted and it restored the older version from a backup? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900121 Title: firmware upgrades remove the ubuntu boot loader from EFI boot vars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900107] Re: fwupd is eating 100% CPU for 30 minutes
Definitely no custom stuff in /usr/local. This was a fresh install of 20.04 in a loaner laptop while mine was getting its keyboard repaired. I'll have to boot it up and check /var/crash on Monday. I killed the misbehaving process with `kill` at the gdb prompt, IIRC. I don't know what signal it sends and whether it causes a core dump. I suspect it doesn't... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900107 Title: fwupd is eating 100% CPU for 30 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900121] [NEW] firmware upgrades remove the ubuntu boot loader from EFI boot vars
Public bug reported: snap-store offered me a system firmware upgrade for my Lenovo ThinkPad X390. I installed it with fwmgr upgrade [*], which prompted me to reboot, which I did, and I saw the firmware upgrade go through, and then it rebooted again -- into Windows. The UEFI boot menu I get on F12 offers me Windows, the NVME drive (which boots Windows), PXE boot, and a Linux Firmware Installer. If I try that one, I get an error about 0 firmware updates being available and the system hangs until I hold the power button. I've booted from a rescue USB, checked efibootmgr -v, saw no Ubuntu entry there, re-ran grub-install /dev/nvme0n1, and now the system boots normally. [*] I tried to install the update from snap-store directly, but my battery was at 7% so that failed with a notification stating the reason. I waited until the battery was charged up to 15%, then tried again, but this time the update failed without giving me a reason. Then I did the update from a terminal with fwupdmgr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fwupd 1.3.11-1~focal1 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 13:13:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (491 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: fwupd UpgradeStatus: Upgraded to focal on 2020-04-24 (174 days ago) mtime.conffile..etc.fwupd.remotes.d.lvfs-testing.conf: 2020-10-08T10:00:47.263185 mtime.conffile..etc.fwupd.remotes.d.lvfs.conf: 2020-10-08T10:00:47.311185 ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900121 Title: firmware upgrades remove the ubuntu boot loader from EFI boot vars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900107] [NEW] fwupd is eating 100% CPU for 30 minutes
Public bug reported: The fan of my laptop started going full-throttle and I ran htop to see why. I see a /usr/libexec/fwupd/fwupd eating 100% CPU for 29:55 minutes. According to ps -o pid,lstart,etime,cmd the process was started yesterday at 22:44. The laptop was suspended yesterday at 23:15 and woken up this morning at 09:03. The time now is 11:26, so it doesn't seem to be directly related to the suspend. perf top attributes all the time to libptrhead-2.31.so, in __pthread_rwlock_wrlock. pstack is unable to extract a stack trace: 86826: /usr/libexec/fwupd/fwupd (No symbols found) crawl: Input/output error Error tracing through process 86826 0x7f1c6e8cbe4a: The journal has some interesting messages from fwupd this morning, but I hope apport will attach them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fwupd 1.3.11-1~focal1 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 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 16 11:22:23 2020 ExecutablePath: /usr/libexec/fwupd/fwupd InstallationDate: Installed on 2020-10-08 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900107 Title: fwupd is eating 100% CPU for 30 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900107] Re: fwupd is eating 100% CPU for 30 minutes
So, apport didn't attach the journal, therefore spal. 16 09:09:34 bigas systemd[1]: Finished Refresh fwupd metadata and update motd. ... spal. 16 10:55:37 bigas fwupd[86826]: 07:55:37:0051 GLib-GObject invalid uninstantiatable type 'GParamInt64' in cast to 'FwupdDevice' spal. 16 10:55:37 bigas fwupd[86826]: 07:55:37:0052 Fwupd fwupd_device_get_id: assertion 'FWUPD_IS_DEVICE (device)' failed spal. 16 10:55:37 bigas fwupd[86826]: 07:55:37:0052 GLib-GObject ../../../gobject/gsignal.c:3482: invalid object type 'GParamInt64' for value type 'FuDevice' spal. 16 10:55:37 bigas fwupd[86826]: 07:55:37:0059 GLib-GObject invalid unclassed pointer in cast to 'FuDeviceList' spal. 16 10:55:37 bigas fwupd[86826]: 07:55:37:0059 GLib-GObject invalid unclassed pointer in cast to 'FwupdDevice' spal. 16 10:55:37 bigas fwupd[86826]: 07:55:37:0059 Fwupd fwupd_device_get_id: assertion 'FWUPD_IS_DEVICE (device)' failed spal. 16 10:55:37 bigas fwupd[86826]: 07:55:37:0059 GLib-GObject instance with invalid (NULL) class pointer spal. 16 10:55:37 bigas fwupd[86826]: 07:55:37:0059 GLib-GObject g_signal_emit_valist: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed and nothing since then, except for the 100% CPU loop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900107 Title: fwupd is eating 100% CPU for 30 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900107] Re: fwupd is eating 100% CPU for 30 minutes
gdb is useless without debug symbols: __pthread_rwlock_wrlock_full (abstime=0x0, clockid=0, rwlock=0x55af956f1a60) at pthread_rwlock_common.c:720 720 pthread_rwlock_common.c: No such file or directory. (gdb) bt #0 __pthread_rwlock_wrlock_full (abstime=0x0, clockid=0, rwlock=0x55af956f1a60) at pthread_rwlock_common.c:720 #1 __GI___pthread_rwlock_wrlock (rwlock=0x55af956f1a60) at pthread_rwlock_wrlock.c:27 #2 0x7f1c6eae8b35 in g_rw_lock_writer_lock () from target:/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x55af9397e5db in ?? () #4 0x7f1c6ea9ca28 in ?? () from target:/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1c6ea9be8e in g_main_context_dispatch () from target:/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f1c6ea9c240 in ?? () from target:/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f1c6ea9c533 in g_main_loop_run () from target:/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x55af93979e3d in main () -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900107 Title: fwupd is eating 100% CPU for 30 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1900107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900095 Title: "Restart Firefox" button quits but doesn't restart after Firefox upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1900095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899356
Title:
chromium's file chooser has no icons
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899356/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897919] [NEW] package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Public bug reported: This looks like a network error: Download snap "snapd" (9279) from channel "stable" (received an unexpected http response code (503) when trying to download https://api.snapcraft.io/api/v1/snaps/download/PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4_9279.snap) that happened during do-release-upgrade from 18.04 to 20.04, but the consequence is that the entire upgrade is now considered to be failed and I have to pick up the pieces manually. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lxd 3.0.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 30 17:25:44 2020 Ec2AMI: ami-0001c5ea Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps-ovhssd2018-1 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: lxd Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-09-30 (0 days ago) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ec2-images focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897919 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1897919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895647] [NEW] containerd-shim deadlocks, then crashes
Public bug reported:
I'm using docker-compose to wrangle a bunch of containers, and quite
often one of my containers hangs.
When I inspect the process with strace, I see it's blocked on write(2,
"...").
/proc/$container_pid/fd/2 is a pipe, the other end of which is managed
by a containerd-shim process.
strace -p $containerd_shim_pid shows it blocked in futex(0xad3848,
FUTEX_WAIT_PRIVATE, 0, NULL).
After enough time passes (around 5 or 10 minutes?) I see that
containerd-shim crash with a SIGABRT. This time I had strace still
attached:
strace: Process 861273 attached
futex(0xad3848, FUTEX_WAIT_PRIVATE, 0, NULL) = ? ERESTARTSYS (To be restarted
if SA_RESTART is set)
--- SIGABRT {si_signo=SIGABRT, si_code=SI_USER, si_pid=867057, si_uid=0} ---
nanosleep({tv_sec=0, tv_nsec=100}, NULL) = 0
nanosleep({tv_sec=0, tv_nsec=100}, NULL) = 0
write(2, "SIGABRT: abort", 14) = 14
write(2, "\n", 1) = 1
write(2, "PC=", 3) = 3
write(2, "0x45c791", 8) = 8
write(2, " m=", 3) = 3
write(2, "0", 1)= 1
write(2, " sigcode=", 9)= 9
write(2, "0", 1)= 1
write(2, "\n", 1) = 1
write(2, "\n", 1) = 1
write(2, "goroutine ", 10) = 10
write(2, "0", 1)= 1
write(2, " [", 2) = 2
write(2, "idle", 4) = 4
write(2, "]:\n", 3) = 3
write(2, "runtime.futex", 13) = 13
...
write(2, "rflags ", 7) = 7
write(2, "0x286", 5)= 5
write(2, "\n", 1) = 1
write(2, "cs ", 7) = 7
write(2, "0x33", 4) = 4
write(2, "\n", 1) = 1
write(2, "fs ", 7) = 7
write(2, "0x0", 3) = 3
write(2, "\n", 1) = 1
write(2, "gs ", 7) = 7
write(2, "0x0", 3) = 3
write(2, "\n", 1) = 1
exit_group(2) = ?
+++ exited with 2 +++
(Full strace log attached, unless I forget)
It would be nice if I could read that Go traceback somewhere instead of
looking at truncated strace writes, but I don't know where.
journalctl -u containerd shows only this:
rugs. 15 12:10:32 blynas containerd[1133]:
time="2020-09-15T12:10:32.805932666+03:00" level=info msg="shim containerd-shim
started"
address=/containerd-shim/a65286bda8fa7242d30c2a351a60d90c344ee6d8af60a7487b1efe75014914c3.sock
debug=false pid=861273
rugs. 15 12:10:33 blynas containerd[1133]:
time="2020-09-15T12:10:33.489963805+03:00" level=info msg="shim containerd-shim
started"
address=/containerd-shim/863c8b7d5dc91b24ae633dbf6efc21b2d9f4973ee6dd4bdf2cb86868f9de.sock
debug=false pid=861500
rugs. 15 12:10:34 blynas containerd[1133]:
time="2020-09-15T12:10:34.197921760+03:00" level=info msg="shim containerd-shim
started"
address=/containerd-shim/08c9c71a81352069f02b14389fb0a636484071e76a443665cb3eefa781a86f3a.sock
debug=false pid=861671
rugs. 15 12:11:03 blynas containerd[1133]:
time="2020-09-15T12:11:03.521908472+03:00" level=info msg="shim containerd-shim
started"
address=/containerd-shim/32b7b8e90d39f2cc59125f5072f7b6012a2e784dc79101694fa749bdfedee8bc.sock
debug=false pid=862495
rugs. 15 12:20:09 blynas containerd[1133]:
time="2020-09-15T12:20:09.424130178+03:00" level=info msg="shim reaped"
id=b76c63912cae0a668aa1f0b9baa2bd74a6c5bbb6a32c1bcae351028cfb101f78
rugs. 15 12:20:09 blynas containerd[1133]:
time="2020-09-15T12:20:09.424177796+03:00" level=warning msg="cleaning up after
shim dead" id=b76c63912cae0a668aa1f0b9baa2bd74a6c5bbb6a32c1bcae351028cfb101f78
namespace=moby
rugs. 15 12:20:12 blynas containerd[1133]:
time="2020-09-15T12:20:12.765586972+03:00" level=info msg="shim reaped"
id=4ea9c0c055e7df514cb4cdb7b6aae7db2ecfea299b712907a229e464827ef219
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: containerd 1.3.3-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 15 12:20:56 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (460 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: containerd
UpgradeStatus: Upgraded to focal on 2020-04-24 (143 days ago)
** Affects: containerd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal wayland-session
** Attachment added: "strace output during the hang and subsequent SIGABRT"
https://bugs.launchpad.net/bugs/1895647/+attachment/5410954/+files/containerd-shim-strace.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: color emoji not rendered; many bw emoji rendered as boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: [snap] color emoji not rendered; many bw emoji rendered as boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: [snap] color emoji not rendered; many bw emoji rendered as boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: [snap] color emoji not rendered; many bw emoji rendered as boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: [snap] color emoji not rendered; many bw emoji rendered as boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: [snap] color emoji not rendered; many bw emoji rendered as boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: [snap] color emoji not rendered; many bw emoji rendered as boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: [snap] color emoji not rendered; many bw emoji rendered as boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: [snap] color emoji not rendered; many bw emoji rendered as boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: [snap] color emoji not rendered; many bw emoji rendered as boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874415 Title: chromedriver doesn't work with the snap package, without --headless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875076] Re: mpv fails on wayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784
*** This bug is a duplicate of bug 1868520 *** https://bugs.launchpad.net/bugs/1868520 Apparently the root cause is mesa bug 1868520. ** This bug has been marked a duplicate of bug 1868520 Clients fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875076 Title: mpv fails on wayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1875076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875076] Re: mpv fails on wayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784
*** This bug is a duplicate of bug 1868520 *** https://bugs.launchpad.net/bugs/1868520 The workaround mentioned in the mpv upstream issue works for me: export MESA_LOADER_DRIVER_OVERRIDE=i965 mpv ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875076 Title: mpv fails on wayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1875076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875076] Re: mpv fails on wayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784
This looks like a matching upstream bug: https://github.com/mpv- player/mpv/issues/7516 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875076 Title: mpv fails on wayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1875076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875076] Re: mpv fails on wayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784
Forgot to mention: this laptop has Intel video (Mesa IntelĀ® UHD Graphics 620 (WHL GT2)). This looks like a matching Debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=955273 ** Bug watch added: github.com/mpv-player/mpv/issues #7516 https://github.com/mpv-player/mpv/issues/7516 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875076 Title: mpv fails on wayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1875076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875076] [NEW] mpv fails on wayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784
Public bug reported: I upgraded my Ubuntu 19.10 laptop to 20.04 LTS and now mpv is unable to play any video. I've tried it with files that played fine on 19.10. All I get is $ mpv http://intranet-host.example.com/somevideo.avi (+) Video --vid=1 (mpeg4 624x480 23.976fps) (+) Audio --aid=1 (mp3 2ch 44100Hz) [vo/gpu/wayland] GNOME's wayland compositor is known to have many serious issues with mpv. Switch to GNOME's xorg session for the best experience. AO: [pulse] 44100Hz stereo 2ch float VO: [gpu] 624x480 yuv420p [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 AV: 00:00:00 / 00:21:58 (0%) A-V: 0.000 Cache: 4.6s/1MB [vo/gpu/wayland] Error occurred on the display fd, closing Exiting... (Quit) I'm using an Ubuntu on Wayland session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mpv 0.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 22:02:41 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (317 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: mpv UpgradeStatus: Upgraded to focal on 2020-04-24 (1 days ago) ** Affects: mpv (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Bug watch added: Debian Bug tracker #955273 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955273 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875076 Title: mpv fails on wayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1875076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874415
Title:
chromedriver doesn't work with the snap package, without --headless
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874415/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874415 Title: chromedriver doesn't work with the snap package, without --headless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778946
Title:
No dns resolution after closing a vpn/pptp connection
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1778946/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793427 Title: network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub- resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-fortisslvpn/+bug/1793427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793427 Title: network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub- resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-fortisslvpn/+bug/1793427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867921] Re: cannot create user data directory: /home/mg/snap/ripgrep/8: Not a directory
Just to clarify, does this mean root can't use snaps too, or is /root handled specially? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867921 Title: cannot create user data directory: /home/mg/snap/ripgrep/8: Not a directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1867921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867921] [NEW] cannot create user data directory: /home/mg/snap/ripgrep/8: Not a directory
Public bug reported: A while ago I installed ripgrep on a server with sudo apt install snapd sudo snap install ripgrep --classic sudo snap alias ripgrep.rg rg and it didn't work for me: $ rg --help cannot create user data directory: /home/mg/snap/ripgrep/4: Too many levels of symbolic links but I was busy and didn't file a bug. Today it still doesn't work, but the error message is different: $ rg --help cannot create user data directory: /home/mg/snap/ripgrep/8: Not a directory Possibly relevant information (especially given the symlink reference in the original error message): my home directory according to /etc/passwd is /home/mg, which is actually a symlink to ../home-ssd/mg. /home is an ext4 partition on a MD RAID-1 device on spinning rust, /home-ssd is an ext4 partition on an LVM volume (mirrored as raid-1) on a pair of SSDs. /home-ssd is too small to contain all the home directories, hence the selective symlinking. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snap (not installed) ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 Date: Wed Mar 18 14:42:48 2020 SourcePackage: snap UpgradeStatus: Upgraded to bionic on 2019-09-11 (188 days ago) ** Affects: snap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867921 Title: cannot create user data directory: /home/mg/snap/ripgrep/8: Not a directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1867921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
