[Bug 2069156] Re: weechat segfaults on /quit
This might be https://github.com/weechat/weechat/issues/2046, caused by a bug in Python 3.12. I have both Perl and Python plugins loaded, and my Valgrind log shows that the memory that the Perl plugin is trying to free during unload was freed by _PyObject_Free earlier. ** Bug watch added: github.com/weechat/weechat/issues #2046 https://github.com/weechat/weechat/issues/2046 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069156 Title: weechat segfaults on /quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weechat/+bug/2069156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064656] Re: gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` multiple times every s
> Everyone from Russian translators team can fix this issue by simply changing translation to '24h' at https://translations.launchpad.net/ It would also be a good idea to fix the upstream translations as well, at https://l10n.gnome.org/. (I've done so for the Lithuanian translation.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064656 Title: gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` multiple times every second for users using the lt_LT , ru_RU, Indonesian (id) and maybe other locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/2064656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069156] [NEW] weechat segfaults on /quit
Public bug reported: I've used weechat twice after upgrading to Ubuntu 24.04 LTS. Both times I got a segfault when I tried to /quit it. coredumpctl gdb weechat gives me this stack trace: Core was generated by `/usr/bin/weechat'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7efcd85d71e0 in ?? () (gdb) bt #0 0x7efcd85d71e0 in ?? () #1 #2 0x7efcda037cdb in __freelocale (dataset=0x62e3d4d94c50) at ./locale/freelocale.c:43 #3 __freelocale (dataset=0x62e3d4d94c50) at ./locale/freelocale.c:31 #4 0x7efcd8865a5e in perl_destruct () from /lib/x86_64-linux-gnu/libperl.so.5.38 #5 0x7efcd8ebaea7 in weechat_perl_unload (script=0x62e3d4deaea0) at /usr/src/weechat-4.1.1-1build7/src/plugins/perl/weechat-perl.c:731 #6 0x7efcd8ebb015 in weechat_perl_unload_all () at /usr/src/weechat-4.1.1-1build7/src/plugins/perl/weechat-perl.c:786 #7 0x7efcd8ee81b1 in plugin_script_end (weechat_plugin=0x62e3d4cba130, plugin_data=0x7efcd8ef6140 ) at /usr/src/weechat-4.1.1-1build7/src/plugins/plugin-script.c:1789 #8 0x7efcd8ebbe2f in weechat_plugin_end (plugin=0x62e3d4cba130) at /usr/src/weechat-4.1.1-1build7/src/plugins/perl/weechat-perl.c:1347 #9 0x62e3d3160317 in plugin_unload (plugin=0x62e3d4cba130) at /usr/src/weechat-4.1.1-1build7/src/plugins/plugin.c:1253 #10 0x62e3d316034c in plugin_unload_all () at /usr/src/weechat-4.1.1-1build7/src/plugins/plugin.c:1305 #11 0x62e3d3160492 in plugin_end () at /usr/src/weechat-4.1.1-1build7/src/plugins/plugin.c:1425 #12 0x62e3d30c834d in weechat_end (gui_end_cb=) at /usr/src/weechat-4.1.1-1build7/src/core/weechat.c:708 #13 main (argc=, argv=) at /usr/src/weechat-4.1.1-1build7/src/gui/curses/normal/main.c:45 I do have a couple of Perl plugins in ~/.weechat/perl/autoload/ (ctrl_w.pl and xclip.pl, downloaded from wherever one gets Weechat plugins). I can reproduce this easily by starting weechat and doing an immediate /quit. Here's a valgrind log of such a run: ==357063== Memcheck, a memory error detector ==357063== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==357063== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info ==357063== Command: /usr/bin/weechat ==357063== Parent PID: 355771 ==357063== ==357063== Warning: client switching stacks? SP change: 0x1ffe8020e0 --> 0x1ffefff3d0 ==357063== to suppress, use: --max-stackframe=8377072 or greater ==357087== ==357087== HEAP SUMMARY: ==357087== in use at exit: 52,351,034 bytes in 78,890 blocks ==357087== total heap usage: 244,339 allocs, 165,449 frees, 98,363,505 bytes allocated ==357087== ==357088== ==357088== HEAP SUMMARY: ==357088== in use at exit: 52,359,916 bytes in 79,061 blocks ==357088== total heap usage: 250,910 allocs, 171,849 frees, 98,650,952 bytes allocated ==357088== ==357063== Invalid read of size 8 ==357063==at 0x4EE4ACD: __freelocale (freelocale.c:43) ==357063==by 0x4EE4ACD: freelocale (freelocale.c:31) ==357063==by 0x7639A5D: perl_destruct (in /usr/lib/x86_64-linux-gnu/libperl.so.5.38.2) ==357063==by 0x7572EA6: weechat_perl_unload (in /usr/lib/x86_64-linux-gnu/weechat/plugins/perl.so) ==357063==by 0x7573014: weechat_perl_unload_all (in /usr/lib/x86_64-linux-gnu/weechat/plugins/perl.so) ==357063==by 0x75A01B0: plugin_script_end (in /usr/lib/x86_64-linux-gnu/weechat/plugins/perl.so) ==357063==by 0x7573E2E: weechat_plugin_end (in /usr/lib/x86_64-linux-gnu/weechat/plugins/perl.so) ==357063==by 0x1AF316: ??? (in /usr/bin/weechat) ==357063==by 0x1AF34B: ??? (in /usr/bin/weechat) ==357063==by 0x1AF491: ??? (in /usr/bin/weechat) ==357063==by 0x11734C: ??? (in /usr/bin/weechat) ==357063==by 0x4ED71C9: (below main) (libc_start_call_main.h:58) ==357063== Address 0x8a522f0 is 272 bytes inside a block of size 638 free'd ==357063==at 0x484988F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==357063==by 0x7FF8E27: _PyObject_Free (obmalloc.c:1853) ==357063==by 0x7FF8E27: _PyObject_Free (obmalloc.c:1843) ==357063==by 0x800B3D0: type_dealloc (typeobject.c:5065) ==357063==by 0x8137EC7: Py_DECREF (object.h:705) ==357063==by 0x8137EC7: delete_garbage (gcmodule.c:1034) ==357063==by 0x8137EC7: gc_collect_main (gcmodule.c:1303) ==357063==by 0x8138875: _PyGC_CollectNoFail (gcmodule.c:2135) ==357063==by 0x810A170: interpreter_clear (pystate.c:895) ==357063==by 0x8101627: finalize_interp_clear (pylifecycle.c:1743) ==357063==by 0x8105FFE: Py_EndInterpreter (pylifecycle.c:2202) ==357063==by 0x7DE7DEC: ??? ==357063==by 0x7DE7ED4: ??? ==357063==by 0x7E037D0: ??? ==357063==by 0x7DE8D8E: ??? ==357063== Block was alloc'd at ==357063==at 0x4846828: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==357063==by 0x7FF9CDF: _PyObject_Malloc (obmalloc.c:1569) ==357063==by 0x8010997: _PyType_FromMetaclass_impl
[Bug 2064656] Re: gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` multiple times every s
Yeah, that makes sense. (Of course constant spamming is more likely to result in a translation fix ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064656 Title: gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` multiple times every second for users using the lt_LT locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/2064656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047778] Re: Software Updater unable to cancel Ubuntu Pro upgrade
Could someone please clarify exact what changes were made? Is the fix only for the terminal version, or does it also include the GUI component? In which versions is the change released? When I check for updates on my 22.04.04 LTS, there is still a message regarding Ubuntu Pro security updates. ** Attachment added: "ubuntu_pro_update_message.png" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2047778/+attachment/5785538/+files/ubuntu_pro_update_message.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047778 Title: Software Updater unable to cancel Ubuntu Pro upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2047778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
"useradd -D" has started to fail with passwd 1:4.13+dfsg1-4ubuntu3.1: # useradd -D Usage: useradd [options] LOGIN useradd -D useradd -D [options] Options: --badname do not check for bad names -b, --base-dir BASE_DIR base directory for the home directory of the new account ... # echo $? 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067250] Re: /usr/bin/w -s segfaults
Ah, it's an old bug: https://gitlab.com/procps-ng/procps/-/issues/301 ** Bug watch added: gitlab.com/procps-ng/procps/-/issues #301 https://gitlab.com/procps-ng/procps/-/issues/301 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067250 Title: /usr/bin/w -s segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2067250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067250] [NEW] /usr/bin/w -s segfaults
Public bug reported: procps 2:4.0.4-4ubuntu3 Just running "w -s" segfaults: # w -s 07:55:26 up 8 min, 3 users, load average: 0.00, 0.03, 0.02 USER TTY FROM IDLE WHAT Segmentation fault (core dumped) I see if I can get a backtrace. ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Affects: procps (Debian) Importance: Unknown Status: Unknown ** Package changed: shadow (Ubuntu) => procps (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067250 Title: /usr/bin/w -s segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2067250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067250] Re: /usr/bin/w -s segfaults
Program received signal SIGSEGV, Segmentation fault. print_host ( host=host@entry=0x4c , len=16, len@entry=256, fromlen=fromlen@entry=16) at src/w.c:112 112 if (*host == '\0') break; (gdb) bt #0 print_host ( host=host@entry=0x4c , len=16, len@entry=256, fromlen=fromlen@entry=16) at src/w.c:112 #1 0x7161 in print_from (session=session@entry=0x0, u=u@entry=0x0, ip_addresses=ip_addresses@entry=0, fromlen=fromlen@entry=16) at src/w.c:264 #2 0x80e0 in showinfo (session=0x55560580 "3", name=name@entry=0x55560770 "root", u=u@entry=0x0, formtype=formtype@entry=0, maxcmd=maxcmd@entry=35, from=from@entry=1, userlen=8, fromlen=16, ip_addresses=0, pids=0) at src/w.c:622 #3 0x6a8f in main (argc=, argv=) at src/w.c:831 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067250 Title: /usr/bin/w -s segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2067250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061285] Re: Snapshot cannot detect laptop camera
Probably a duplicate of bug 2061687, given the empty pw-dump output. Does systemctl --user restart wireplumber.service fix it for the remainder of the login session? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061285 Title: Snapshot cannot detect laptop camera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-snapshot/+bug/2061285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064656] [NEW] gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` multiple times every
Public bug reported: After upgrading to Ubuntu 24.04 LTS I ran journalctl -f and noticed that gnome-shell was spamming errors at the rate of 12 lines every second: geg. 02 18:29:19 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:19 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:c6:25:2f:1a:a1:27:08:00 SRC=192.168.1.180 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=30487 PROTO=2 geg. 02 18:29:21 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:21 blynas gnome-shell[3980]: Using untranslated default instead. My locale is lt_LT.UTF-8, which is relevant. This is caused by a mistaken translation of the quote characters in "'24h'" which is used as the default value for a particular gsettings key. Specifically, this translation: https://translations.launchpad.net/ubuntu/noble/+source/gsettings- desktop-schemas/+pots/gsettings-desktop-schemas/lt/232/+translate. Since I'm a member of the Lithuanian translators team, I've fixed the translation error in translations.launchpad.net, but my gnome-shell will continue to spam multiple errors every second until an updated language- pack-gnome-lt-base is released. (I've also submitted a fixed translation upstream to l10n.gnome.org.) Workaround: run dconf-editor, find /org/gnome/desktop/interface/clock- format, uncheck Use default value, click Apply. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 2 18:25:59 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1786 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-05-02 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble 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/2064656 Title: gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` multiple times every second for users using the lt_LT locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
Hi Dave, I'm not sure if this is of any help but I did install your image linked here and it worked perfectly. This is on a rpi 4 8GB where I previously had issues with the installer crashing while installing to sd card, no matter which of your workarounds I've tried. So... yea your image fixed my issue and I was able to successfully install 24.04! I have a few spare SD cards laying around, let me know if I can help debug anything. Thanks man! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 1969285] Re: Wayland session unavailable after upgrade from 21.10
** Package changed: ubuntu => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969285 Title: Wayland session unavailable after upgrade from 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969285] [NEW] Wayland session unavailable after upgrade from 21.10
Public bug reported: After upgrading from 21.10 to beta 22.04 the Wayland session is no longer available. By default, I do not even get the option to select the session type but if I lock the screen, the login screen changes from the X11 UI to the Gnome UI and the bottom right button appears. When clicking on the session selector button the screen blanks out and then returns to a X11 session login screen (X11 session works as expected). I thought this was related to the https://bugs.launchpad.net/bugs/1960898 because I had the dash-to-dock extension in 21.10 but after attempting the gsettings fix, it still did not work. I also removed the extension but Wayland still does not work. I installed lightdm and switched to it for a successful Wayland session for now. Hardware: https://linux-hardware.org/?probe=800aefa57e ** Affects: 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/1969285 Title: Wayland session unavailable after upgrade from 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1969285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958283] Re: linux-firmware missing renoir_ta
I downloaded and installed 1.187.26 via browser. I can also confirm that it fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958283 Title: linux-firmware missing renoir_ta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958283/+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 1958283] Re: linux-firmware missing renoir_ta
@Aaron, I am not able to find the first bad version because apt tells me that the specified version for firmware-linux was not found. See the attached log. ** Attachment added: "find-first-bad-version.txt" https://bugs.launchpad.net/ubuntu/focal/+source/linux-firmware/+bug/1958283/+attachment/427/+files/find-first-bad-version.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958283 Title: linux-firmware missing renoir_ta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] Re: Internal monitor of AMD based laptop not working after update
As mentioned in https://bugs.launchpad.net/ubuntu/focal/+source/linux- firmware/+bug/1958283: I am able to fix the problem temporarily with a downgrade: sudo apt install linux-firmware=1.187 After a reboot, I no longer have any graphics errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958283] Re: linux-firmware missing renoir_ta
I am able to fix the problem temporarily with a downgrade: sudo apt install linux-firmware=1.187 After a reboot, I no longer have any graphics errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958283 Title: linux-firmware missing renoir_ta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/412/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/411/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/410/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/409/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/408/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/407/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/406/+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/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/405/+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/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/404/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/403/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/402/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/401/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/400/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/399/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/398/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/397/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/396/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] Re: Internal monitor of AMD based laptop not working after update
apport information ** Tags added: apport-collected jolnir third-party-packages ** Description changed: After applying the latest updates for focal yesterday and rebooting, the internal display of my laptop is no longer usable. Only a noisy, snowy image can be seen on the display. An externally connected display still works. I can reproduce this behavior on 2 laptops: TUXEDO Pulse 14 - Gen1 AMD Ryzen 7 4800H ThinkPad T14s AMD Gen 1 AMD Ryzen 5 Pro 4650U + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: marius 1618 F pulseaudio + /dev/snd/controlC0: marius 1618 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: Pantheon + Dependencies: + + DistroRelease: elementary OS 6.1 + MachineType: TUXEDO TUXEDO Pulse 14 Gen1 + Package: linux-firmware 1.187 [origin: Ubuntu] + PackageArchitecture: all + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=/dev/mapper/data-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-27-generic N/A + linux-backports-modules-5.13.0-27-generic N/A + linux-firmware 1.187 + Tags: third-party-packages jolnir + Uname: Linux 5.13.0-27-generic x86_64 + UnreportableReason: Das ist kein offizielles elementary-Paket. Bitte entfernen Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: sudo + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 05/11/2021 + dmi.bios.release: 5.16 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: N.1.07.A03 + dmi.board.asset.tag: Standard + dmi.board.name: PULSE1401 + dmi.board.vendor: NB02 + dmi.board.version: Standard + dmi.chassis.asset.tag: Standard + dmi.chassis.type: 10 + dmi.chassis.vendor: TUXEDO + dmi.chassis.version: Standard + dmi.ec.firmware.release: 1.7 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnTUXEDO:pnTUXEDOPulse14Gen1:pvrStandard:rvnNB02:rnPULSE1401:rvrStandard:cvnTUXEDO:ct10:cvrStandard:skuPULSE1401: + dmi.product.family: TUXEDO Computers + dmi.product.name: TUXEDO Pulse 14 Gen1 + dmi.product.sku: PULSE1401 + dmi.product.version: Standard + dmi.sys.vendor: TUXEDO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1958343/+attachment/395/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958283] Re: linux-firmware missing renoir_ta
I can also confirm this issue. I added a "screenshot" in https://bugs.launchpad.net/ubuntu/+bug/1958343. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958283 Title: linux-firmware missing renoir_ta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] Re: Internal monitor of AMD based laptop not working after update
** Package changed: ubuntu => linux-firmware (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] Re: Internal monitor of AMD based laptop not working after update
I extracted the last updated packages with cat /var/log/dpkg.log | grep "\ upgrade\ " ** Attachment added: "dpkg.log" https://bugs.launchpad.net/ubuntu/+bug/1958343/+attachment/394/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] [NEW] Internal monitor of AMD based laptop not working after update
Public bug reported: After applying the latest updates for focal yesterday and rebooting, the internal display of my laptop is no longer usable. Only a noisy, snowy image can be seen on the display. An externally connected display still works. I can reproduce this behavior on 2 laptops: TUXEDO Pulse 14 - Gen1 AMD Ryzen 7 4800H ThinkPad T14s AMD Gen 1 AMD Ryzen 5 Pro 4650U ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "PXL_20220118_153746678.jpg" https://bugs.launchpad.net/bugs/1958343/+attachment/365/+files/PXL_20220118_153746678.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958343/+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 1913388] Re: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
fyi, fixed patch for clucene to keep the ABI constant on s390x is attached to https://sourceforge.net/p/clucene/bugs/233/. The patch requires that clucene uses a separate type clucene_float_t in its API, with multiple yet trivial changes all across the code base. None of the packages that depend on clucene required modifications to cope with that API change; sword, bibletime, dovecot, and libreoffice just build in a current hirose with a modified clucene. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913388] Re: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
Indeed, my patch is just broken. I have not received any upstream feedback about the patch or the proposed alternatives -- unfortunately, clucene's community appears rather inactive, with 0 emails on the developer list in the last three months. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+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 1910738] [NEW] package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not p
Public bug reported: No problematic behaviour except for push-up notification showing this bug. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-modules-5.8.0-36-generic (not installed) ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euler 1632 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 10:26:39 2021 DpkgTerminalLog: Preparing to unpack .../0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb ... Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted DuplicateSignature: package:linux-modules-5.8.0-36-generic:(not installed) Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-12-22 (748 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: PC Specialist LTD N2x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: linux-image-5.8.0-34-generic linux-base RelatedPackageVersions: grub-pc 2.04-1ubuntu35.1 SourcePackage: linux Title: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to groovy on 2020-10-23 (76 days ago) dmi.bios.date: 06/02/2018 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N2x0WU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.07.13:bd06/02/2018:br7.13:efr7.13:svnPCSpecialistLTD:pnN2x0WU:pvrNotApplicable:rvnCLEVO:rnN2x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N2x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910738 Title: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux- modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876157] Re: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020
I tried the patch from #15 but it still hangs for me, albeit after 3min and not after a few seconds like without the patch. I tried version 5.31b and it works fine. Core i5-4570, 16 GiB RAM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876157 Title: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1876157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876157] Re: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020
I tried the patch from #15 but it still hangs for me. I have 16 GiB RAM installed. Anything else I can try? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876157 Title: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1876157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904899] Re: pixel color access delivers wrong data on s390x (e.g., tests/color_test.py)
version 0.6.4 has been released, including the fix -- https://docs.wand- py.org/en/0.6.4/changes.html#version-0-6-4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904899 Title: pixel color access delivers wrong data on s390x (e.g., tests/color_test.py) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wand/+bug/1904899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904899] [NEW] pixel color access delivers wrong data on s390x (e.g., tests/color_test.py)
Public bug reported: When using an Imagemagick compiled with HDRI=1 (e.g., ,libmagickwand-6.q16hdri-6) many color-related test cases in wand fail. The root cause is that python-wand assumes that ImageMagick's QuantumType would be float for 16-bit HDRI. However, in that config QuantumType is derive from float_t, which on s390x today is defined as double. The upstream issue https://github.com/emcconville/wand/issues/504 has already been resolved. The fix will be included in the upcoming release 0.6.4. Please consider upgrading to the new release, once available. Upstream fix in PR https://github.com/emcconville/wand/pull/505 The issue can be reproduced by running the testsuite (pytest / pytest-3). ** Affects: wand (Ubuntu) Importance: Undecided Status: New ** Description changed: When using an Imagemagick compiled with HDRI=1 (e.g., ,libmagickwand-6.q16hdri-6) many color-related test cases in wand fail. The root cause is that python-wand assumes that ImageMagick's QuantumType would be float for 16-bit HDRI. However, in that config QuantumType is derive from float_t, which on s390x today is defined as double. The upstream issue https://github.com/emcconville/wand/issues/504 has already been resolved. The fix will be included in the upcoming release 0.6.4. Please consider upgrading to the new release, once available. + + The issue can be reproduced by running the testsuite (pytest / + pytest-3). ** Description changed: When using an Imagemagick compiled with HDRI=1 (e.g., ,libmagickwand-6.q16hdri-6) many color-related test cases in wand fail. The root cause is that python-wand assumes that ImageMagick's QuantumType would be float for 16-bit HDRI. However, in that config QuantumType is derive from float_t, which on s390x today is defined as double. The upstream issue https://github.com/emcconville/wand/issues/504 has already been resolved. The fix will be included in the upcoming release 0.6.4. Please consider upgrading to the new release, once available. + Upstream fix in PR https://github.com/emcconville/wand/pull/505 The issue can be reproduced by running the testsuite (pytest / pytest-3). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904899 Title: pixel color access delivers wrong data on s390x (e.g., tests/color_test.py) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wand/+bug/1904899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904724] Re: package linux-modules-extra-5.8.0-29-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.8.0-29-generic/kernel/kernel/torture.ko.dpkg-new': Operation no
Was solved with sudo apt --fix-broken install sudo apt upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904724 Title: package linux-modules-extra-5.8.0-29-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.8.0-29-generic/kernel/kernel/torture.ko.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904724] [NEW] package linux-modules-extra-5.8.0-29-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.8.0-29-generic/kernel/kernel/torture.ko.dpkg-new': Operation
Public bug reported: New kernel installation 5.8.0-29 was corrupted. Problem with sudo apt upgrade: You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies. linux-image-generic : Depends: linux-modules-extra-5.8.0-29-generic but it is not installed ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-modules-extra-5.8.0-29-generic (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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euler 1581 F pulseaudio CasperMD5CheckResult: skip Date: Wed Nov 18 11:50:28 2020 ErrorMessage: unable to open '/lib/modules/5.8.0-29-generic/kernel/kernel/torture.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-12-22 (697 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: PC Specialist LTD N2x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: linux-image-5.8.0-28-generic linux-base RelatedPackageVersions: grub-pc 2.04-1ubuntu35 SourcePackage: linux Title: package linux-modules-extra-5.8.0-29-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.8.0-29-generic/kernel/kernel/torture.ko.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to groovy on 2020-10-23 (25 days ago) dmi.bios.date: 06/02/2018 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N2x0WU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.07.13:bd06/02/2018:br7.13:efr7.13:svnPCSpecialistLTD:pnN2x0WU:pvrNotApplicable:rvnCLEVO:rnN2x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N2x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904724 Title: package linux-modules-extra-5.8.0-29-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.8.0-29-generic/kernel/kernel/torture.ko.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904724/+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
