[Bug 1868654] Re: reuseport_bpf in net from ubuntu_kernel_selftests failed on X-4.15 PowerPC
** Also affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-signed-hwe (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux-signed-hwe (Ubuntu) Status: New => Invalid ** Changed in: linux-signed-hwe (Ubuntu Xenial) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868654 Title: reuseport_bpf in net from ubuntu_kernel_selftests failed on X-4.15 PowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1868654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915275] Re: mysql-8.0 regressed on riscv64 due to new glibc
Submitted to Debian (for an upload there into experimental and into Hirsute) => https://salsa.debian.org/mariadb-team/mysql/-/merge_requests/46 Test PPA: => https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4487/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915275 Title: mysql-8.0 regressed on riscv64 due to new glibc To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1915275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916541] Re: smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade
Thanks, I'll upload the backported fix to Hirsute soon. ** Changed in: postfix (Ubuntu) Status: Confirmed => In Progress ** Changed in: postfix (Ubuntu) Status: In Progress => Confirmed ** Changed in: postfix (Ubuntu) Status: Confirmed => Invalid ** Changed in: glibc (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916541 Title: smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1916541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918678] Re: reuseport_bpf_numa in ubuntu_kernel_selftests.net ADT test failure with bionic/linux-hwe
** Description changed: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux-hwe/20210311_063109_0b20b@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux-hwe/20210311_062431_3dadb@/log.gz + + reuseport_bpf_numa has been failing with xenial/linux-hwe for amd64 and + ppc64el. This failure is not a regression, I'm opening a new bug report + as it doesn't seem to be related to bug 1867570 or bug 1909286. ** Summary changed: - reuseport_bpf_numa in ubuntu_kernel_selftests.net ADT test failure with bionic/linux-hwe + reuseport_bpf_numa in ubuntu_kernel_selftests.net ADT test failure with xenial/linux-hwe ** Also affects: linux-hwe (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu Xenial) Status: New => Confirmed ** No longer affects: linux-hwe (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918678 Title: reuseport_bpf_numa in ubuntu_kernel_selftests.net ADT test failure with xenial/linux-hwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1918678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911187] Re: scheduled reboot reboots immediately if dbus or logind is not available
# VERIFICATION FOCAL Installed systemd from -proposed : # dpkg -l | grep systemd ii libnss-resolve:amd64 245.4-4ubuntu3.5 amd64nss module to resolve names via systemd-resolved ii libnss-systemd:amd64 245.4-4ubuntu3.5 amd64nss module providing dynamic user and group name resolution ii libpam-systemd:amd64 245.4-4ubuntu3.5 amd64system and service manager - PAM module ii libsystemd-dev:amd64 245.4-4ubuntu3.5 amd64systemd utility library - development files ii libsystemd0:amd64 245.4-4ubuntu3.5 amd64systemd utility library ii networkd-dispatcher2.0.1-1 all Dispatcher service for systemd-networkd connection status changes ii systemd245.4-4ubuntu3.5 amd64system and service manager ii systemd-container 245.4-4ubuntu3.5 amd64systemd container/nspawn tools ii systemd-journal-remote 245.4-4ubuntu3.5 amd64tools for sending and receiving remote journal logs ii systemd-sysv 245.4-4ubuntu3.5 amd64system and service manager - SysV links ii systemd-tests 245.4-4ubuntu3.5 amd64tests for systemd ii systemd-timesyncd 245.4-4ubuntu3.5 amd64minimalistic service to synchronize local time with NTP servers Following test plan from description # systemctl stop dbus.service # systemctl stop dbus.socket # shutdown +1 -r "REBOOT!" Failed to set wall message, ignoring: Connection timed out Failed to call ScheduleShutdown in logind, no action will be taken: Connection timed out Machine does not reboot as expected. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911187 Title: scheduled reboot reboots immediately if dbus or logind is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918668] Re: vm changes cause NULL pointer derefs
Running update-grub/grub-probe seems to trigger it every time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918668 Title: vm changes cause NULL pointer derefs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918681] [NEW] CVE-2021-28117: Discover: Missing URI scheme validation
*** This bug is a security vulnerability *** Public security bug reported: https://kde.org/info/security/advisory-20210310-1.txt https://security-tracker.debian.org/tracker/CVE-2021-28117 KDE Project Security Advisory = Title: Discover: Missing URI scheme validation Risk Rating: Low CVE: CVE-2021-28117 Versions:Discover >= 5.15.0 <= 5.21.3 Author: Aleix Pol Gonzalez Date:10 March 2021 Overview Discover fetches the description and related texts of some applications/plugins from store.kde.org. That text is displayed to the user, after turning into a clickable link any part of the text that looks like a link. This is done for any kind of link, be it smb:// nfs:// etc. when in fact it only makes sense for http/https links. Impact == Opening links that the user has clicked on is not very problematic but can be used to chain to other attack vectors. Given the intended functionality of the feature is just for http/https links it makes sense to do that verification. Workaround == Only click on http/https links in Discover. Solution Install Plasma 5.21.3, 5.18.7 or apply these patches Plasma 5.21: https://commits.kde.org/plasma/discover/94478827aab63d2e2321f0ca9ec5553718798e60 Plasma 5.18: https://commits.kde.org/plasma/discover/fcd3b30552bf03a384b1a16f9bb8db029c111356 Credits === Thanks to Fabian Bräunlein for reporting the issue. ** Affects: plasma-discover (Ubuntu) Importance: Undecided Status: New ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-28117 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918681 Title: CVE-2021-28117: Discover: Missing URI scheme validation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1918681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844582] Re: "Invalid argument" when trying to scan
Apologies for the slow response. Please find attached the requested log file. ** Attachment added: "The requested file, 'log.xz'." https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+attachment/5475860/+files/log.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844582 Title: "Invalid argument" when trying to scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
This ticket is now discussed and worked on in a broader scope and is therefore dependent on: → https://salsa.debian.org/debian/kdump-tools/-/merge_requests/5 → https://bugs.debian.org/983486 ** Bug watch added: Debian Bug tracker #983486 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983486 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911187] Re: scheduled reboot reboots immediately if dbus or logind is not available
# VERIFICATION BIONIC Installed systemd from -proposed : # dpkg -l | grep systemd ii libnss-resolve:amd64 237-3ubuntu10.45 amd64nss module to resolve names via systemd-resolved ii libnss-systemd:amd64 237-3ubuntu10.45 amd64nss module providing dynamic user and group name resolution ii libpam-systemd:amd64 237-3ubuntu10.45 amd64system and service manager - PAM module ii libsystemd-dev:amd64 237-3ubuntu10.45 amd64systemd utility library - development files ii libsystemd0:amd64 237-3ubuntu10.45 amd64systemd utility library ii networkd-dispatcher1.7-0ubuntu3.3 all Dispatcher service for systemd-networkd connection status changes ii python3-systemd234-1build1 amd64Python 3 bindings for systemd ii systemd237-3ubuntu10.45 amd64system and service manager ii systemd-container 237-3ubuntu10.45 amd64systemd container/nspawn tools ii systemd-journal-remote 237-3ubuntu10.45 amd64tools for sending and receiving remote journal logs ii systemd-sysv 237-3ubuntu10.45 amd64system and service manager - SysV links ii systemd-tests 237-3ubuntu10.45 amd64tests for systemd Following test plan from description # systemctl stop dbus.service # systemctl stop dbus.socket # shutdown +1 -r "REBOOT!" Failed to set wall message, ignoring: Refusing activation, D-Bus is shutting down. Failed to call ScheduleShutdown in logind, no action will be taken: Refusing activation, D-Bus is shutting down. Machine does not reboot as expected. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911187 Title: scheduled reboot reboots immediately if dbus or logind is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914866] Re: USB3 UAS to SATA SSD not recognized
Currently I am using a new USB3 to SATA cable. This is working like a charm. The cables I was using before: https://www.amazon.de/gp/product/B018G1RLYC/ref=ppx_yo_dt_b_asin_title_o06_s00?ie=UTF8=1 https://www.amazon.de/gp/product/B01ESQZG6Y/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8=1 https://www.amazon.de/gp/product/B01E3QSG3Y/ref=ppx_yo_dt_b_asin_title_o09_s00?ie=UTF8=1 https://www.amazon.de/gp/product/B081W2CQ66/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1 https://www.aliexpress.com/item/4001003811312.html?spm=a2g0s.9042311.0.0.27424c4dDSypjT The cable I am using now: https://www.amazon.de/gp/product/B086W944YT/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8=1 It can be, that I just had a really bad luck with all these cables above except the one I am using. right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914866 Title: USB3 UAS to SATA SSD not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918678] [NEW] reuseport_bpf_numa in ubuntu_kernel_selftests.net ADT test failure with bionic/linux-hwe
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux-hwe/20210311_063109_0b20b@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux-hwe/20210311_062431_3dadb@/log.gz ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-hwe (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Description changed: Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux-hwe/20210311_063109_0b20b@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/linux-hwe/20210225_211517_72358@/log.gz - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux-hwe/20210311_103058_d5621@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux-hwe/20210311_062431_3dadb@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux-hwe/20210311_053849_a6264@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux-hwe/20210311_063109_0b20b@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux-hwe/20210311_062431_3dadb@/log.gz ** Summary changed: - linux-hwe 4.15.0-137.141~16.04.1 ADT test failure with linux-hwe 4.15.0-137.141~16.04.1 + reuseport_bpf_numa in ubuntu_kernel_selftests.net ADT test failure with linux-hwe ** Summary changed: - reuseport_bpf_numa in ubuntu_kernel_selftests.net ADT test failure with linux-hwe + reuseport_bpf_numa in ubuntu_kernel_selftests.net ADT test failure with bionic/linux-hwe ** Also affects: linux-hwe (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux-hwe (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918678 Title: reuseport_bpf_numa in ubuntu_kernel_selftests.net ADT test failure with bionic/linux-hwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1918678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915275] Re: mysql-8.0 regressed on riscv64 due to new glibc
Submitted upstream as https://bugs.mysql.com/bug.php?id=102926 ** Bug watch added: MySQL Bug System #102926 http://bugs.mysql.com/bug.php?id=102926 ** Also affects: mysql-server via http://bugs.mysql.com/bug.php?id=102926 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/1915275 Title: mysql-8.0 regressed on riscv64 due to new glibc To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1915275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918466] Re: Garbage window on external 4k display
Can you please attach output of `grep . /sys/class/drm/*/enabled`, thanks! ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
This is weird. I just tried reproducing this issue on both 20.04.2.0 release images and on the latest hirsute (21.04) dailies (Ubuntu Desktop) and failed. Steps I used to reproduce it: 1. Booted up the image on a VM 2. Ubiquity starts, on the left-hand side list I selected 'Norsk bokmål' and then the equivalent of 'Install Ubuntu'. 3. Moved through all the stages, installing the system on disk 4. On the username and password screen, I typed '[' on my keyboard and got 'å' on the input field instead - meaning the correct keyboard layout was used. Am I doing something wrong? Can anyone tell me if I'm missing a step? Or is it no longer reproducible on both focal and hirsute *again*? Cheers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891003] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable
** Summary changed: - mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable on B-AWS-5.3 + mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891003 Title: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1891003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918613] Re: [FFe] GDM background configurable with gsettings
Having the schema in GDM was our initial proposal but you told us that it would be better to do it the way we just proposed and do it in an independent schema as long as it is not yet accepted upsteam. In both cases there will be a migration *if* something similar is ever implemented in gnome-shell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918613 Title: [FFe] GDM background configurable with gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii
** Description changed: + [Impact] + + * unattended-upgrades --help crashes in apt.systemd.daily script when + locale is not in UTF-8. + [Test Case] + + In the fixed case no crash is observed. rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076 Creating bb-lp-1806076 Starting bb-lp-1806076 rbalint@yogi:~$ lxc shell bb-lp-1806076 mesg: ttyname failed: No such device root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: language-pack-ru The following NEW packages will be installed: language-pack-ru language-pack-ru-base 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. Need to get 2310 kB of archives. After this operation, 11.8 MB of additional disk space will be used. Selecting previously unselected package language-pack-ru-base. (Reading database ... 28536 files and directories currently installed.) Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru-base (1:18.04+20180712) ... Selecting previously unselected package language-pack-ru. Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru-base (1:18.04+20180712) ... Generating locales (this might take a while)... ru_RU.UTF-8... done ru_UA.UTF-8... done Generation complete. - root@bb-lp-1806076:~# env LANG=ru_RU unattended-upgrade --help | cat + + root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale + LANG=ru_RU + root@bb-lp-1806076:~# + /usr/lib/apt/apt.systemd.daily update Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 1983, in - (options, args) = parser.parse_args() # type: ignore - File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args - stop = self._process_args(largs, rargs, values) - File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args - self._process_long_opt(rargs, values) - File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt - option.process(opt, value, values, self) - File "/usr/lib/python3.6/optparse.py", line 785, in process - self.action, self.dest, opt, value, values, parser) - File "/usr/lib/python3.6/optparse.py", line 807, in take_action - parser.print_help() - File "/usr/lib/python3.6/optparse.py", line 1647, in print_help - file.write(self.format_help()) + File "/usr/bin/unattended-upgrade", line 2171, in + (options, args) = parser.parse_args() # type: ignore + File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args + stop = self._process_args(largs, rargs, values) + File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args + self._process_long_opt(rargs, values) + File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt + option.process(opt, value, values, self) + File "/usr/lib/python3.6/optparse.py", line 785, in process + self.action, self.dest, opt, value, values, parser) + File "/usr/lib/python3.6/optparse.py", line 807, in take_action + parser.print_help() + File "/usr/lib/python3.6/optparse.py", line 1647, in print_help + file.write(self.format_help()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 126-133: ordinal not in range(128) - root@bb-lp-1806076:~# env LANG=ru_RU.UTF-8 unattended-upgrade --help | cat - Usage: unattended-upgrade [options] + root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale + LANG=ru_RU.UTF-8 + root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update + root@bb-lp-1806076:~# - Options: - -h, --helpshow this help message and exit - -d, --debug print debug messages - --apt-debug make apt/libapt print verbose debug messages - -v, --verbose print info messages - --dry-run Simulation, download but do not install - --download-only Only download, do not even try to install. - --minimal-upgrade-steps - Upgrade in minimal steps (and allow interrupting with - SIGTERM + [Where problems could occur] + + * Nowhere, really. The fix is setting LC_ALL=C.UFT-8 for u-u --help and + it is processed by grep then. + [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.6, the problem page at https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error
[Bug 1918670] Re: usb audio is not able to use after boot from 5.10.0-1017-oem
** Changed in: linux-oem-5.10 (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918670 Title: usb audio is not able to use after boot from 5.10.0-1017-oem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1918670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916541] Re: smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade
** Changed in: glibc (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916541 Title: smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1916541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii
** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806076 Title: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1806076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES
Hello Rafael, or anyone else affected, Accepted isc-dhcp into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/isc- dhcp/4.3.5-3ubuntu7.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: isc-dhcp (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894172 Title: isc-dhcp-server using wrong env variable for INTERFACES To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832021] Re: Checksum drop of metadata traffic on isolated networks with DPDK
** Changed in: cloud-archive Importance: Undecided => Medium ** Changed in: cloud-archive/queens Importance: Undecided => Medium ** Changed in: cloud-archive/rocky Importance: Undecided => Medium ** Changed in: cloud-archive/stein Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832021 Title: Checksum drop of metadata traffic on isolated networks with DPDK To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1832021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915177] Re: xtables-addons fails to build after ip_route_me_harder() signature change
One more data point $ dkms status xtables-addons, 3.9, 5.8.0-44-generic, x86_64: installed xtables-addons, 3.9, 5.8.0-45-generic, x86_64: installed minor data point: geoip appears to be working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915177 Title: xtables-addons fails to build after ip_route_me_harder() signature change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1915177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894172] Please test proposed package
Hello Rafael, or anyone else affected, Accepted isc-dhcp into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/isc- dhcp/4.4.1-2.1ubuntu5.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894172 Title: isc-dhcp-server using wrong env variable for INTERFACES To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892369] Re: Impossible to skip integrity test for ubuntu-server 20.04.1 iso
OK, I understand..the request then is for cancelling the integrity test *once it has started*. Can you open a new bug, with a very clear/direct title about this? Something like "Add a way to cancel integrity test on Ubuntu server ISO once it has started", so we can track this feature request over there. Thanks in advance, Guilherme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892369 Title: Impossible to skip integrity test for ubuntu-server 20.04.1 iso To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES
Hello Rafael, or anyone else affected, Accepted isc-dhcp into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/isc- dhcp/4.4.1-2.1ubuntu10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: isc-dhcp (Ubuntu Groovy) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: isc-dhcp (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894172 Title: isc-dhcp-server using wrong env variable for INTERFACES To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832021] Re: Checksum drop of metadata traffic on isolated networks with DPDK
** Changed in: cloud-archive/queens Assignee: (unassigned) => Erlon R. Cruz (sombrafam) ** Changed in: cloud-archive/rocky Assignee: (unassigned) => Erlon R. Cruz (sombrafam) ** Changed in: cloud-archive/stein Assignee: (unassigned) => Erlon R. Cruz (sombrafam) ** Changed in: charm-neutron-openvswitch Assignee: (unassigned) => Erlon R. Cruz (sombrafam) ** Changed in: cloud-archive Assignee: (unassigned) => Erlon R. Cruz (sombrafam) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832021 Title: Checksum drop of metadata traffic on isolated networks with DPDK To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1832021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
** Changed in: ubiquity (Ubuntu Focal) Milestone: ubuntu-20.04.2 => ubuntu-20.04.3 ** Changed in: ubiquity (Ubuntu Hirsute) Milestone: None => ubuntu-21.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894843] Please test proposed package
Hello ITD27M01, or anyone else affected, Accepted neutron into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:16.3.0-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894843 Title: [dvr_snat] Router update deletes rfp interface from qrouter even when VM port is present on this host To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1894843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896734] Re: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack
Hello Dmitrii, or anyone else affected, Accepted neutron into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:16.3.0-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: neutron (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896734 Title: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1896734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915786] Please test proposed package
Hello Chris, or anyone else affected, Accepted neutron into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:16.3.0-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915786 Title: [SRU] Ussuri stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916761] Re: [dvr] bound port permanent arp entries never deleted
Hello Edward, or anyone else affected, Accepted neutron into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:16.3.0-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: neutron (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916761 Title: [dvr] bound port permanent arp entries never deleted To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1916761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918659] Re: switch wireguard over to a full supported backport for v5.4 kernels
Both of the scaffolding patches (aa350dbe3a1ee5e062228f8f5ebd2ffb6e58709c b41352a93c163afafd29f56bb18fd3c0fef1120c) are present in linux stable v5.4.91 which have been applied to focal/master-next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918659 Title: switch wireguard over to a full supported backport for v5.4 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918613] Re: [FFe] GDM background configurable with gsettings
Not sure if the gsettings schema change should be part of gdm though, as if this will ever be upstreamed that's where it will belong. Indeed, it will makes the FFe a bit more complex and cause more changes though, but we'd get there anyways when (if) we'll have to migrate to gnome keys. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918613 Title: [FFe] GDM background configurable with gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918670] Re: usb audio is not able to use after boot from 5.10.0-1017-oem
** Package changed: linux-meta-oem-5.10 (Ubuntu) => linux-oem-5.10 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918670 Title: usb audio is not able to use after boot from 5.10.0-1017-oem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1918670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918667] Re: collectd disk plugin doesnt work on 5.x kernel (hwe)
it seems that it was already fixed in 5.7.2-2ubuntu1.2 ** Changed in: collectd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918667 Title: collectd disk plugin doesnt work on 5.x kernel (hwe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1918667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918670] [NEW] usb audio is not able to use after boot from 5.10.0-1017-oem
Public bug reported: I got below error, when plug usb-c headset to my system. and usb audio is not able to use, however, the usb audio works on 5.10.0-1014-oem on my system: Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: BUG: kernel NULL pointer dereference, address: 0012 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: #PF: supervisor read access in kernel mode Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: #PF: error_code(0x) - not-present page Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: PGD 0 P4D 0 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: Oops: [#1] SMP NOPTI Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: CPU: 2 PID: 364 Comm: systemd-udevd Not tainted 5.10.0-1017-oem #18-Ubuntu Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: Hardware name: Dell Inc. Latitude 9510/, BIOS 1.4.2 12/22/2020 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: RIP: 0010:usb_audio_probe+0x2e3/0x5c0 [snd_usb_audio] Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: Code: 48 83 7d b8 00 48 8b 7d c8 74 17 48 8b 45 b8 80 78 14 00 74 0d 48 8b 75 b0 e8 59 81 01 00 48 8b 7d c8 48 8b 45 b8 48 8b 75 b0 <0f> b7 40 12 66 89 87 9c 00 00 00 48 63 07 48 89 3c c5 60 5a fd c0 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: RSP: :ad254067fa40 EFLAGS: 00010246 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: RAX: RBX: c0fd5c60 RCX: 8dff8a7372c8 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: RDX: 8dff8a737ec8 RSI: 8dff82e2f400 RDI: 8dff870c88b8 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: RBP: ad254067faa0 R08: 006d R09: 0022 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: R10: 000b R11: a032b784ff8d R12: Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: R13: c0fd5c60 R14: R15: c0fd5d60 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: FS: 7f017910d8c0() GS:8e010568() knlGS: Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: CS: 0010 DS: ES: CR0: 80050033 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: CR2: 0012 CR3: 00010749e006 CR4: 003706e0 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: Call Trace: ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "kernel log" https://bugs.launchpad.net/bugs/1918670/+attachment/5475854/+files/journalctl-1.log ** Description changed: - I got below error, when plug usb-c headset to my system. I got error - below and usb audio is not able to use, and the usb audio works on - 5.10.0-1014-oem on my system: + I got below error, when plug usb-c headset to my system. and usb audio + is not able to use, however, the usb audio works on 5.10.0-1014-oem on + my system: Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: BUG: kernel NULL pointer dereference, address: 0012 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: #PF: supervisor read access in kernel mode Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: #PF: error_code(0x) - not-present page - Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: PGD 0 P4D 0 + Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: PGD 0 P4D 0 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: Oops: [#1] SMP NOPTI Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: CPU: 2 PID: 364 Comm: systemd-udevd Not tainted 5.10.0-1017-oem #18-Ubuntu Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: Hardware name: Dell Inc. Latitude 9510/, BIOS 1.4.2 12/22/2020 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: RIP: 0010:usb_audio_probe+0x2e3/0x5c0 [snd_usb_audio] Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: Code: 48 83 7d b8 00 48 8b 7d c8 74 17 48 8b 45 b8 80 78 14 00 74 0d 48 8b 75 b0 e8 59 81 01 00 48 8b 7d c8 48 8b 45 b8 48 8b 75 b0 <0f> b7 40 12 66 89 87 9c 00 00 00 48 63 07 48 89 3c c5 60 5a fd c0 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: RSP: :ad254067fa40 EFLAGS: 00010246 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: RAX: RBX: c0fd5c60 RCX: 8dff8a7372c8 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: RDX: 8dff8a737ec8 RSI: 8dff82e2f400 RDI: 8dff870c88b8 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: RBP: ad254067faa0 R08: 006d R09: 0022 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: R10: 000b R11: a032b784ff8d R12: Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: R13: c0fd5c60 R14: R15: c0fd5d60 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: FS: 7f017910d8c0() GS:8e010568() knlGS: Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: CS: 0010 DS: ES: CR0: 80050033 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: CR2: 0012 CR3: 00010749e006 CR4: 003706e0 Mar 11 20:20:46 kchsieh-Latitude-9510 kernel: Call Trace: -- You received this bug notification because you
[Bug 1912307] Re: [MIR] abseil
Building mozc without abseil isn't as simple as expected and is an upstream change as well and not only the debian patch. Updating the MIR status seems that seems the way forward - Debian is changing the soname with every snapshot, as discussed it's not ideal but it's manageable and ensure there is no incompatible change even if there is no .symbols - the build issue has been resolved - the assembler warning is not present when building the current git version, since it's just a gcc warning in the tests could be get the MIR accepted on that basis? we could bisect to find when it got resolved and try to cherrypick a change but if there is no hurry it would probably be best to spend that time on other work instead Changing back to New and unassigned so it's in the review queue again ** Changed in: abseil (Ubuntu) Status: Incomplete => New ** Changed in: abseil (Ubuntu) Assignee: Sebastien Bacher (seb128) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912307 Title: [MIR] abseil To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/abseil/+bug/1912307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1918599] Re: "File system loop detected" with btrfs over NFS
On Thu 2021-03-11 (12:31), Ubuntu Foundations Team Bug Bot wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It seems that your bug report is not filed about a > specific source package though, rather it is just filed against Ubuntu > in general. It is important that bug reports be filed about source > packages so that people interested in the package can find the bugs > about it. I am not sure whether the bug is in btrfs, nfs-server or the GNU utilities or in a combination of them. -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de Allmandring 30aTel:++49-711-68565868 70569 Stuttgart (Germany) WWW:http://www.tik.uni-stuttgart.de/ REF:<161546591847.28828.17838281687088999024.mal...@soybean.canonical.com> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918599 Title: "File system loop detected" with btrfs over NFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1918599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918667] Re: collectd disk plugin doesnt work on 5.x kernel (hwe)
this commit could be backported and would fix this issue: https://github.com/Stackdriver/collectd/pull/182/commits/f7b16999c0bf5d61dec559b92a7afba214b06bee -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918667 Title: collectd disk plugin doesnt work on 5.x kernel (hwe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1918667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop
** Description changed: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. - Normally, when I click Cancel or Connect, the modal window disappears - and returns me to the desktop. + After I have clicked on one of the networks, normally, when I click + Cancel or Connect, the modal window disappears and returns me to the + desktop. With the current gnome-shell, this modal window persists and I cannot - access the desktop - this is both in Wayland and in X. + access the desktop - this is both in Wayland and in X. Connect doesn't + seem to work - it's like the buttons are no longer accepting clicks. The + ESC key also doesn't do anything. (If I don't click on a network, the + ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918667] [NEW] collectd disk plugin doesnt work on 5.x kernel (hwe)
Public bug reported: after updating a ubuntu 18.04 machine to HWE 5.x kernel the disk plugin doesnt work anymore. its seems to be related to https://github.com/collectd/collectd/issues/2951 the issue was fixed in 5.8.1 ** Affects: collectd (Ubuntu) Importance: Undecided Status: Invalid ** Description changed: - after updating to a ubuntu 18.04 machine to HWE 5.x kernel the disk - plugin doesnt work. + after updating a ubuntu 18.04 machine to HWE 5.x kernel the disk plugin + doesnt work anymore. its seems to be related to https://github.com/collectd/collectd/issues/2951 the issue was fixed in 5.8.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918667 Title: collectd disk plugin doesnt work on 5.x kernel (hwe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1918667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918668] Re: vm changes cause NULL pointer derefs
One other example: [ 41.499636] BUG: kernel NULL pointer dereference, address: 0518 [ 41.506015] #PF: supervisor read access in kernel mode [ 41.508850] #PF: error_code(0x) - not-present page [ 41.510728] PGD 0 P4D 0 [ 41.511714] Oops: [#1] SMP PTI [ 41.513040] CPU: 1 PID: 198 Comm: kworker/u8:4 Tainted: GW 5.8.0-45-generic #51 [ 41.516172] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-1 04/01/2014 [ 41.519019] Workqueue: writeback wb_workfn (flush-252:0) [ 41.520954] RIP: 0010:__mod_memcg_state.part.0+0xc/0x90 [ 41.522845] Code: f0 56 30 93 e8 15 9f 2e 00 5b 41 5c 41 5d 5d c3 4c 8b 25 ff 52 99 01 e9 76 ff ff ff 0f 0b 0f 1f 44 00 00 48 63 d2 55 48 63 f6 <48> 8b 87 18 05 00 00 65 48 8b 0c f0 48 01 ca 48 c1 e6 03 49 89 d0 [ 41.536800] RSP: 0018:abad803ff7d8 EFLAGS: 00010097 [ 41.540726] RAX: ffe2 RBX: 0011 RCX: 00032192 [ 41.543210] RDX: RSI: 0011 RDI: [ 41.545567] RBP: abad803ff810 R08: R09: 96e43801ec00 [ 41.547992] R10: R11: 1000 R12: 96e43801ec00 [ 41.550528] R13: R14: R15: 96e43ffb2000 [ 41.552904] FS: () GS:96e43dc8() knlGS: [ 41.557020] CS: 0010 DS: ES: CR0: 80050033 [ 41.559173] CR2: 0518 CR3: 35f4c000 CR4: 06e0 [ 41.561005] Call Trace: [ 41.561769] ? __mod_lruvec_state+0x47/0xf0 [ 41.562897] clear_page_dirty_for_io+0x187/0x200 [ 41.564111] mpage_submit_page+0x24/0x90 [ 41.565181] mpage_map_and_submit_buffers+0xe3/0x190 [ 41.566477] mpage_map_and_submit_extent+0x5a/0x200 [ 41.567732] ext4_writepages+0x671/0x860 [ 41.568882] ? update_load_avg+0x82/0x630 [ 41.570181] do_writepages+0x38/0xc0 [ 41.571320] ? write_inode+0x5c/0x100 [ 41.572625] __writeback_single_inode+0x40/0x230 [ 41.574046] writeback_sb_inodes+0x22a/0x4e0 [ 41.575380] __writeback_inodes_wb+0x56/0xf0 [ 41.576798] wb_writeback+0x201/0x2e0 [ 41.578252] wb_check_old_data_flush+0xb7/0xc0 [ 41.580364] wb_do_writeback+0xbe/0x180 [ 41.581989] ? set_worker_desc+0xa6/0xb0 [ 41.583553] wb_workfn+0x74/0x290 [ 41.589094] ? __switch_to+0x7f/0x380 [ 41.590524] ? __switch_to_asm+0x42/0x70 [ 41.591753] ? __switch_to_asm+0x36/0x70 [ 41.593102] process_one_work+0x1e8/0x3b0 [ 41.594571] worker_thread+0x50/0x370 [ 41.595935] kthread+0x12f/0x150 [ 41.597224] ? process_one_work+0x3b0/0x3b0 [ 41.598772] ? __kthread_bind_mask+0x70/0x70 [ 41.600473] ret_from_fork+0x22/0x30 [ 41.601997] Modules linked in: isofs binfmt_misc nls_iso8859_1 input_leds joydev serio_raw sch_fq_codel drm ip_tables x_tables autofs4 ahci xhci_pci xhci_pci_renesas psmouse virtio_net libahci net_failover virtio_blk failover [ 41.609197] CR2: 0518 [ 41.610567] ---[ end trace 63fecb49c24b6bde ]--- [ 41.612023] RIP: 0010:__mod_memcg_state.part.0+0xc/0x90 [ 41.613631] Code: f0 56 30 93 e8 15 9f 2e 00 5b 41 5c 41 5d 5d c3 4c 8b 25 ff 52 99 01 e9 76 ff ff ff 0f 0b 0f 1f 44 00 00 48 63 d2 55 48 63 f6 <48> 8b 87 18 05 00 00 65 48 8b 0c f0 48 01 ca 48 c1 e6 03 49 89 d0 [ 41.623236] RSP: 0018:abad803ff7d8 EFLAGS: 00010097 [ 41.625530] RAX: ffe2 RBX: 0011 RCX: 00032192 [ 41.629038] RDX: RSI: 0011 RDI: [ 41.632316] RBP: abad803ff810 R08: R09: 96e43801ec00 [ 41.635007] R10: R11: 1000 R12: 96e43801ec00 [ 41.637663] R13: R14: R15: 96e43ffb2000 [ 41.640305] FS: () GS:96e43dc8() knlGS: [ 41.643404] CS: 0010 DS: ES: CR0: 80050033 [ 41.645522] CR2: 0518 CR3: 35f4c000 CR4: 06e0 [ 41.647610] [ cut here ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918668 Title: vm changes cause NULL pointer derefs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918669] [NEW] No weather information any more ("no data available")
Public bug reported:
On several machines running Xubuntu 20.10, I do not get weather information any
more.
The applet says there is currently no data available.
I checked different locations, too. Nothing.
my ~/.xsession-errors has the lines
8<
(wrapper-2.0:2497): weather-WARNING **: 14:07:40.109: Herunterladen der
astronomischen Daten fehlgeschlagen mit HTTP-Status-Code 2, Ursache:
Fehler beim Auflösen von »api.met.no«: Temporärer Fehler bei der
Namensauflösung
(wrapper-2.0:2497): weather-WARNING **: 14:07:40.110: Herunterladen der
Wetterdaten fehlgeschlagen mit HTTP-Status-Code 2, Ursache: Fehler beim
Auflösen von »api.met.no«: Temporärer Fehler bei der Namensauflösung
available 0weather-Message: 14:07:51.966:
https://api.met.no/weatherapi/sunrise/2.0/?lat=50.776351=6.083862=2021-03-06=+01:00=5
wird abgerufen
weather-Message: 14:07:51.966:
https://api.met.no/weatherapi/locationforecast/1.9/?lat=50.776351=6.083862=177
wird abgerufen
(wrapper-2.0:2497): weather-WARNING **: 14:07:51.967: Herunterladen der
astronomischen Daten fehlgeschlagen mit HTTP-Status-Code 2, Ursache:
Fehler beim Auflösen von »api.met.no«: Temporärer Fehler bei der
Namensauflösung
(wrapper-2.0:2497): weather-WARNING **: 14:07:51.969: Herunterladen der
Wetterdaten fehlgeschlagen mit HTTP-Status-Code 2, Ursache: Fehler beim
Auflösen von »api.met.no«: Temporärer Fehler bei der Namensauflösung
(process:2474): GLib-GIO-CRITICAL **: 14:08:02.526:
g_application_get_is_remote: assertion 'application->priv->is_registered' failed
weather-Message: 14:08:02.891:
https://api.met.no/weatherapi/sunrise/2.0/?lat=50.776351=6.083862=2021-03-06=+01:00=5
wird abgerufen
weather-Message: 14:08:02.891:
https://api.met.no/weatherapi/locationforecast/1.9/?lat=50.776351=6.083862=177
wird abgerufen
(wrapper-2.0:2497): weather-WARNING **: 14:08:11.804: Herunterladen der
Wetterdaten fehlgeschlagen mit HTTP-Status-Code 404, Ursache: Not Found
git-annex: Nothing listed in /home/andreas/.config/git-annex/autostart
8<
Ich checked with one machine running Debian testing, which already has
version xfce4-weather-plugin_0.11.0-1_amd64.deb of the package, which
works fine with the regular location.
At XFCE's pages on the weather plugin, there is a bug report, 4 months
old, regarding a deprecated API for version 0.10.1-1,
https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin/-/issues/32 ,
that is closed. Is this perhaps the reason for my problem?
Sadly, I could not simply install the Debian package to check, because
the required, higher versions of some gdk-pixbuf packages are not
available in Xubuntu, so I gave up on that for now.
Regards,
Andreas
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xfce4-weather-plugin 0.10.1-1
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Thu Mar 11 13:38:00 2021
SourcePackage: xfce4-weather-plugin
UpgradeStatus: Upgraded to groovy on 2020-10-31 (131 days ago)
** Affects: xfce4-weather-plugin (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918669
Title:
No weather information any more ("no data available")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1918669/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918668] [NEW] vm changes cause NULL pointer derefs
Public bug reported: After booting with groovy:linux master-next branch as of 2021-03-10, NULL pointer dereferences are seen. One of them is like the one below: [ 10.012503] BUG: kernel NULL pointer dereference, address: 0518 [ 10.030761] #PF: supervisor read access in kernel mode [ 10.042518] #PF: error_code(0x) - not-present page [ 10.050165] PGD 0 P4D 0 [ 10.077050] Oops: [#1] SMP PTI [ 10.081927] CPU: 0 PID: 516 Comm: kexec-load Tainted: GW 5.8.0-45-generic #51 [ 10.092486] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-1 04/01/2014 [ 10.103510] RIP: 0010:__mod_memcg_state.part.0+0xc/0x90 [ 10.115100] Code: f0 56 d0 ba e8 f5 9e 2e 00 5b 41 5c 41 5d 5d c3 4c 8b 25 ff 52 99 01 e9 76 ff ff ff 0f 0b 0f 1f 44 00 00 48 63 d2 55 48 63 f6 <48> 8b 87 18 05 00 00 65 48 8b 0c f0 48 01 ca 48 c1 e6 03 49 89 d0 [ 10.145025] RSP: 0018:ab9780557ab0 EFLAGS: 00010096 [ 10.146841] RAX: ffe2 RBX: 0002 RCX: 00032183 [ 10.149891] RDX: RSI: 0002 RDI: [ 10.153006] RBP: ab9780557ae8 R08: R09: 0004 [ 10.165999] R10: f30fc1cb2a88 R11: R12: 88ec39f32400 [ 10.168142] R13: R14: 0001 R15: 88ec3ffb2000 [ 10.170299] FS: () GS:88ec3dc0() knlGS: [ 10.172783] CS: 0010 DS: ES: CR0: 80050033 [ 10.175285] CR2: 0518 CR3: 78a7c000 CR4: 06f0 [ 10.178009] Call Trace: [ 10.179133] ? __mod_lruvec_state+0x47/0xf0 [ 10.180897] __activate_page.part.0+0x125/0x290 [ 10.182665] __activate_page+0x3a/0x40 [ 10.184496] pagevec_lru_move_fn+0x9d/0xe0 [ 10.186124] ? __activate_page.part.0+0x290/0x290 [ 10.188030] lru_add_drain_cpu+0xeb/0x1b0 [ 10.190041] lru_add_drain+0x28/0x40 [ 10.194029] exit_mmap+0x82/0x1b0 [ 10.195400] ? get_file_caps.constprop.0+0xa2/0x150 [ 10.197578] ? _cond_resched+0x1a/0x50 [ 10.199834] ? mutex_lock+0x13/0x40 [ 10.201931] mmput+0x5f/0x140 [ 10.203772] exec_mmap+0x198/0x220 [ 10.205484] begin_new_exec+0x9e/0x2d0 [ 10.207132] load_elf_binary+0x7b2/0xe20 [ 10.209471] ? ima_bprm_check+0x89/0xb0 [ 10.211378] search_binary_handler+0xe1/0x270 [ 10.213590] exec_binprm+0x51/0x1a0 [ 10.215013] __do_execve_file+0x361/0x5b0 [ 10.216671] do_execve+0x27/0x30 [ 10.218596] __x64_sys_execve+0x2c/0x40 [ 10.220646] do_syscall_64+0x49/0xc0 [ 10.222729] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.226379] RIP: 0033:0x7f8881dafb7b [ 10.228548] Code: Unable to access opcode bytes at RIP 0x7f8881dafb51. [ 10.230985] RSP: 002b:7fffa1572278 EFLAGS: 0246 ORIG_RAX: 003b [ 10.233907] RAX: ffda RBX: RCX: 7f8881dafb7b [ 10.236543] RDX: 5576aad6e7a8 RSI: 5576aad6e788 RDI: 5576aad6e7d8 [ 10.240265] RBP: 5576aad6e788 R08: 5576aad6e7d8 R09: feff5475a9d4ff72 [ 10.243031] R10: 7f8881d76610 R11: 0246 R12: 5576aa32447e [ 10.245755] R13: 5576aad6e7a8 R14: 5576aad6e7a8 R15: 5576aad6e7d8 [ 10.248772] Modules linked in: isofs binfmt_misc nls_iso8859_1 joydev input_leds serio_raw sch_fq_codel drm ip_tables x_tables autofs4 ahci psmouse libahci virtio_blk xhci_pci xhci_pci_renesas virtio_net net_failover failover [ 10.258738] CR2: 0518 [ 10.260139] ---[ end trace f7c347003caf39b8 ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Groovy) Importance: Critical Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918668 Title: vm changes cause NULL pointer derefs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832021] Re: Checksum drop of metadata traffic on isolated networks with DPDK
** Also affects: cloud-archive/queens Importance: Undecided Status: New ** Also affects: cloud-archive/stein Importance: Undecided Status: New ** Changed in: cloud-archive/stein Status: New => Fix Released ** Also affects: cloud-archive/rocky Importance: Undecided Status: New ** Also affects: neutron (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/1832021 Title: Checksum drop of metadata traffic on isolated networks with DPDK To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1832021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896734] Re: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack
Hello Dmitrii, or anyone else affected, Accepted neutron into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:17.1.0-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: neutron (Ubuntu Groovy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896734 Title: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1896734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915275] Re: mysql-8.0 regressed on riscv64 due to new glibc
And that awkward number if directly consumed is just "-1"
$ cat test-sysconf.cpp
#include
#include
int main() {
std::cout << "_SC_LEVEL1_DCACHE_LINESIZE = " <<
sysconf(_SC_LEVEL1_DCACHE_LINESIZE) << "\n";
return 0;
}
$ rm test-sysconf; g++ -Wall -o test-sysconf test-sysconf.cpp && ./test-
sysconf
riscv64 @ Hirsute
_SC_LEVEL1_DCACHE_LINESIZE = -1
riscv64 @ Focal
_SC_LEVEL1_DCACHE_LINESIZE = 0
So it changed the "I can't get this" result from 0 to -1 and that is what broke
us.
This does not talk about the proper fail RC :-/
https://www.gnu.org/software/libc/manual/html_node/Constants-for-Sysconf.html
Man page mentions it:
RETURN VALUE
The return value of sysconf() is one of the following:
* On error, -1 is returned and errno is set to indicate the
cause of the error (for example, EINVAL, indicating that name is
invalid).
* If name corresponds to an option, a positive value is returned
if the option is supported, and -1 is returned if the option is not
supported.
So I guess we need to teach mysql to handle that well.
** Changed in: mysql-8.0 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915275
Title:
mysql-8.0 regressed on riscv64 due to new glibc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1915275/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916761] Re: [dvr] bound port permanent arp entries never deleted
Hello Edward, or anyone else affected, Accepted neutron into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:17.1.0-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: neutron (Ubuntu Groovy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916761 Title: [dvr] bound port permanent arp entries never deleted To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1916761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915785] Please test proposed package
Hello Chris, or anyone else affected, Accepted neutron into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:17.1.0-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915785 Title: [SRU] Victoria stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918666] [NEW] Cannot close the modal "Connect to Wifi" window to return to desktop
Public bug reported: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 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/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894843] Please test proposed package
Hello ITD27M01, or anyone else affected, Accepted neutron into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:17.1.0-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894843 Title: [dvr_snat] Router update deletes rfp interface from qrouter even when VM port is present on this host To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1894843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915275] Re: mysql-8.0 regressed on riscv64 due to new glibc
I have separated the problem from all the mysql code. This file here works on x86 and on older riscv64. But if ran on current hirsute riscv64 it breaks as mysql-server-8.0 does. I further simplified it and attach it hereby for debugging. It seems that the detection of the cache-line-size is failing and from there things go south. riscv64 @ Hirsute CL 18446744073709551615 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted (core dumped) riscv64 @ Focal CL 0 static 32@0x3fff86f2c0 x86 @ Hirsute CL 64 static 32@0x7fff300363a0 So it seems what is broken is "sysconf(_SC_LEVEL1_DCACHE_LINESIZE);" On some platforms that returns good values (e.g. x86) and on others it used to return "0". Mysql had code to cover the "0" case, but the new libc@riscv64 we get a crazy high value and that breaks all that we see. ** Attachment added: "test-riscv64-alloc.cpp" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1915275/+attachment/5475843/+files/test-riscv64-alloc.cpp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915275 Title: mysql-8.0 regressed on riscv64 due to new glibc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1915275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299604] Re: evolution keeps asking for password
It's been fine since https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1299604/comments/70, and now it's back again. The previous solution doesn't work anymore. Running Evolution Mail 3.36.4-0ubuntu1 on Kubuntu 20.04.2. I've tried removing and adding again the account, to no avail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299604 Title: evolution keeps asking for password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1299604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918599] Re: "File system loop detected" with btrfs over NFS
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1918599/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918599 Title: "File system loop detected" with btrfs over NFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1918599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918623] Re: upgrade 16.04 to 18,04 on ppc64 failed
** Tags added: xenial2bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918623 Title: upgrade 16.04 to 18,04 on ppc64 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1918623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918618] Re: check_running_kernel (part of nagios-plugins-contrib) fails as a 20.04 LTS Kernel is now LZ4 compressed
The attachment "This is the patch that fixes this issue" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918618 Title: check_running_kernel (part of nagios-plugins-contrib) fails as a 20.04 LTS Kernel is now LZ4 compressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins-contrib/+bug/1918618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918658] [NEW] Display glitches when showing context menu
Public bug reported: I am using Android Studio to develop Applications. When i have lots of windows opened and i try to open a context menu or write code, it shows a frame of some applications that are below the current window. In the video it is more clear. I don't know if this is a problem related to Ubuntu or Android Studio but it is very noisy. In this case it is clear that the frame shown belongs to the Arduino window that is open under it. Sometimes i can see frames of my wallpaper (when i don't have any window under it) or others. This problem doesn't happen with other programs (for now). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 13:07:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.8.0-43-generic, x86_64: installed nvidia, 460.39, 5.8.0-44-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-44-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2021-01-17 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=34f5f1d0-f244-447f-8b6b-1ec5c14fe8f6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd06/05/2020:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "A video of this glitch" https://bugs.launchpad.net/bugs/1918658/+attachment/5475814/+files/2021-03-11_13-05-40.mov -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918658 Title: Display glitches when showing context menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1918658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918659] [NEW] switch wireguard over to a full supported backport for v5.4 kernels
Public bug reported: Upstream produces a proper independent backport of wireguard for v5.4 based kernels. Due to the nature of the compat version in the DKMS packages some features are not implemented there leading to worse performance. This proper backport is now in use in the majority of distros which use the v5.4 base, and as such support for v5.4 is likely to end soon in the compat tree. Switch to using that backport. tl;dr $ git clone https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal $ cd focal $ git cherry-pick aa350dbe3a1ee5e062228f8f5ebd2ffb6e58709c b41352a93c163afafd29f56bb18fd3c0fef1120c $ curl 'https://git.zx2c4.com/wireguard-linux/patch/?id2=gregkh/stable-5.4.y=backport-5.4.y' | git am -s The whole series should apply cleanly. Afterwards, simply enable CONFIG_WIREGUARD=y and you're good to go. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Andy Whitcroft (apw) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Description changed: Upstream produces a proper independent backport of wireguard for v5.4 based kernels. Due to the nature of the compat version in the DKMS packages some features are not implemented there leading to worse performance. This proper backport is now in use in the majority of distros which use the v5.4 base, and as such support for v5.4 is likely to end soon in the compat tree. Switch to using that backport. + + tl;dr + + $ git clone https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal + $ cd focal + $ git cherry-pick aa350dbe3a1ee5e062228f8f5ebd2ffb6e58709c b41352a93c163afafd29f56bb18fd3c0fef1120c + $ curl 'https://git.zx2c4.com/wireguard-linux/patch/?id2=gregkh/stable-5.4.y=backport-5.4.y' | git am -s + + The whole series should apply cleanly. Afterwards, simply enable + CONFIG_WIREGUARD=y and you're good to go. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918659 Title: switch wireguard over to a full supported backport for v5.4 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908502] Re: [MIR] libdeflate
desktop subscribed now ** Changed in: libdeflate (Ubuntu Hirsute) Status: Incomplete => New ** Changed in: libdeflate (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908502 Title: [MIR] libdeflate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1908502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839477] Re: Firewall group stuck in PENDING_UPDATE
I see these errors in all Ussuri deployments so lets get this fixed. If you need information I can provide it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839477 Title: Firewall group stuck in PENDING_UPDATE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron-fwaas/+bug/1839477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907109] Re: xtables-addons 3.0-0.1ubuntu4/3.8-2ubuntu0.1 fails to build with linux 5.4.0-57.63
Hello Ahmed, By the logs I'm assuming you are running 20.04 (Focal Fossa). For this series there is an update to xtables-addons-dkms currently in -proposed (this fix is being tracked via bug 1915177). To get this update you can either enable the -proposed pocket or wait for a few more days until the fix is available in -updates. Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907109 Title: xtables-addons 3.0-0.1ubuntu4/3.8-2ubuntu0.1 fails to build with linux 5.4.0-57.63 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1907109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
** Changed in: glibc (Ubuntu Xenial) Status: New => Invalid ** Changed in: glibc (Ubuntu Bionic) Status: New => Invalid ** Changed in: glibc (Ubuntu Focal) Status: New => Invalid ** Changed in: glibc (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
Also: setting all the other tasks to Invalid as there's noting wrong with them; the issue (and the fix) belong to systemd. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Changed in: fam (Ubuntu) Status: Incomplete => Invalid ** Changed in: freeradius (Ubuntu) Status: Incomplete => Invalid ** Changed in: ipfm (Ubuntu) Status: Incomplete => Invalid ** Changed in: n2n (Ubuntu) Status: Incomplete => Invalid ** Changed in: pfm (Ubuntu) Status: Incomplete => Invalid ** Changed in: shadowsocks (Ubuntu) Status: Incomplete => Invalid ** Changed in: sysfsutils (Ubuntu) Status: Incomplete => Invalid ** Changed in: virtualbox (Ubuntu) Status: Incomplete => Invalid ** Changed in: xl2tpd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1915887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
Fixed in Debian with the introduction of a new quilt patch: https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 Counting this as Fix Committed. ** Changed in: systemd (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1915887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915275] Re: mysql-8.0 regressed on riscv64 due to new glibc
Ok I found in the stdc++ implementation of "new" that sz indeed is passed to malloc. void *ptr = std::malloc(sz)) Thereby it indeed means "bytes" and that means ~18 exabyte which is slightly more than most systems can offer :-) The question now becomes, where is this value created/derived from and can we reproduce this maybe even outside of the complexity of mysql. To me it starts to seem more like an issue in the lib, but to know that for sure we will need to track down where this value really comes from. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915275 Title: mysql-8.0 regressed on riscv64 due to new glibc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1915275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1912690] Re: Bluetooth transaction timeout on startup
The error came from time to time - say every 10th start. I have not noticed it for long, but maybe it is still there. I will update you once it appears again. Am Do., 11. März 2021 um 04:25 Uhr schrieb Dongshan Yin < 1912...@bugs.launchpad.net>: > is the issue resolved now? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1912690 > > Title: > Bluetooth transaction timeout on startup > > Status in Ubuntu: > Confirmed > > Bug description: > When starting up , the system hangs after showing the following three > lines and stops the boot process: > Bluetooth: hci0: command 0xfc09 tx timeout > Bluetooth: hci0: Failed to send firmware data (-110) > Bluetooth: hci0: sending frame failed (-19) > > I have Ubuntu 20.04 and the latest packages. > > Thanks, > detlef > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1912690/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912690 Title: Bluetooth transaction timeout on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1912690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916541] Re: smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade
Comment #5 of the upstream bug report [1] says this is Fixed for 2.34. Also backported to 2.33. The backport commit for 2.33 is [2]. [1] https://sourceware.org/bugzilla/show_bug.cgi?id=27389#c5 [2] https://sourceware.org/git/?p=glibc.git;a=commit;h=3e880d733753183696d1a81c34caef3a9add2b0c ** Tags added: rls-hh-incoming ** Changed in: glibc (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916541 Title: smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1916541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all
Yes I do, I played video with video player, played youtube video, and I still can not hear any sound from my speaker, I don't know what's the problem Pada tanggal Kam, 11 Mar 2021 pukul 17.25 Po-Hsu Lin < 1651...@bugs.launchpad.net> menulis: > Thanks for checking, so your computer should have the fix already. > > Do you still having this audio (no sound at all) issue? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1651500 > > Title: > [ASUS X441SA] [8086:2284] No sound at all > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > 1. Release of ubuntu > Description: Ubuntu 16.04.1 LTS > Release: 16.04 > > 2. version of the package > AlsaMixer v1.1.0 > > > 3. I expect to hear sound from speaker > > 4. I can not any sound from speaker > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 > Uname: Linux 4.4.0-53-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.4 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: hamda 1627 F pulseaudio > CurrentDesktop: Unity > Date: Tue Dec 20 22:51:08 2016 > InstallationDate: Installed on 2016-12-15 (5 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: hamda 1627 F pulseaudio > Symptom_Jack: Speaker, Internal > Symptom_Type: No sound at all > Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/08/2016 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: X441SA.301 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: X441SA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: ATN12345678901234567 > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.name: X441SA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651500/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651500 Title: [ASUS X441SA] [8086:2284] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892205] Re: tcgbios.c:1519:33: error: taking address of packed member of ‘struct ’ may result in an unaligned pointer value [-Werror=address-of-packed-member]
[Copypaste from LP: #1892475] Hello Marietto, If I understand correctly you are having problems compiling igvtg-xen from the upstream source code. In this case this bug tracker is not the right place where to report this issue, as we use it to track bugs in Ubuntu, and not issues or incompatibilities with third-party projects. This unless the problem you hit is a problem with the (Ubuntu packaged) GCC, but I don't think this is the case; more likely there's an incompatibility between igvtg-xen and the version of gcc/glibc in Focal, which is however working as expected. You can find pointers to get help for this sort of problem here: https://ubuntu.com/support/community-support If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is specifically a bug in Ubuntu, and then change the bug status back to New. Thanks! ** Changed in: xen (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892205 Title: tcgbios.c:1519:33: error: taking address of packed member of ‘struct ’ may result in an unaligned pointer value [-Werror=address-of-packed- member] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1892205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915275] Re: mysql-8.0 regressed on riscv64 due to new glibc
In my comparison on Focal (older libc / stdc++) all calls to "operator new[]" and "operator new" had sz=0 like: Breakpoint 5, operator new (sz=0) at ../../../../src/libstdc++-v3/libsupc++/new_op.cc:47 The first operator new that didn't have sz=0 in this good case was a totally different backtrace at: Breakpoint 5, operator new (sz=sz@entry=72) at ../../../../src/libstdc++-v3/libsupc++/new_op.cc:47 47 in ../../../../src/libstdc++-v3/libsupc++/new_op.cc (gdb) bt #0 operator new (sz=sz@entry=72) at ../../../../src/libstdc++-v3/libsupc++/new_op.cc:47 #1 0x002add4f7104 in gtid_server_init () at ./sql/mysqld.cc:2372 #2 0x002add502c20 in init_server_components () at ./sql/mysqld.cc:5872 #3 0x002add509054 in mysqld_main (argc=, argv=) at ./sql/mysqld.cc:7097 #4 0x003fbc0d3204 in __libc_start_main (main=0x2add4c4084 , argc=, argv=0x3fffe67528, init=, fini=, rtld_fini=, stack_end=) at libc-start.c:308 #5 0x002add4f18cc in _start () at ./include/my_sys.h:864 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915275 Title: mysql-8.0 regressed on riscv64 due to new glibc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1915275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915275] Re: mysql-8.0 regressed on riscv64 due to new glibc
>From the backtrace at frist we see: At the start of mysql it calls init_server_components -> delegates_init. That then initializes a new object alignas(Trans_delegate) static char place_trans_mem[sizeof(Trans_delegate)]; ... transaction_delegate = new (place_trans_mem) Trans_delegate; That then triggers the allocation of a lock::Shared_spin_lock::Shared_spin_lock Which itself uses the default constructor: Shared_spin_lock() = default; That then goes into memory::Aligned_atomic::Aligned_atomic There (at least to my naive view) it seems to go terribly wrong with it's size assumptions because if sz is the size in bytes then #6 0x003ff76389b8 in operator new (sz=18446744073709551615) clearly is too much. ... #6 0x003ff76389b8 in operator new (sz=18446744073709551615) at ../../../../src/libstdc++-v3/libsupc++/new_op.cc:54 handler = p = #7 0x003ff76389d6 in operator new[] (sz=) at ../../../../src/libstdc++-v3/libsupc++/new_opv.cc:32 No locals. #8 0x002aac352ed8 in memory::Aligned_atomic::Aligned_atomic ( this=0x2aae2463d0 ) at ./sql/memory/aligned_atomic.h:282 No locals. #9 memory::Aligned_atomic::Aligned_atomic (value=0, this=0x2aae2463d0 ) at ./sql/memory/aligned_atomic.h:287 ... ** Attachment added: "Backtrace of the issue in Hirsute rsicv64" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1915275/+attachment/5475790/+files/riscv64-libc2.33-hirsute-crash.backtrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915275 Title: mysql-8.0 regressed on riscv64 due to new glibc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1915275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916034] Re: Please merge flash-kernel 3.104 from Debian unstable
** Changed in: flash-kernel (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916034 Title: Please merge flash-kernel 3.104 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1916034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916541] Re: smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade
** Also affects: glibc via https://sourceware.org/bugzilla/show_bug.cgi?id=27389 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/1916541 Title: smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1916541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916898] Re: Please merge u-boot 2021.01+dfsg-2 from Debian unstable
** Changed in: u-boot (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916898 Title: Please merge u-boot 2021.01+dfsg-2 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1916898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918134] Re: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key
We will also need to ensure master kernels have updated dkms-build and dkms-build--nvidia-N as we will sync those into the new linux- restricted-modules packages and break them. ** Changed in: linux-restricted-modules (Ubuntu) Status: New => In Progress ** Changed in: linux-restricted-modules (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-restricted-modules (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918134 Title: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918613] Re: [FFe] GDM background configurable with gsettings
** Description changed: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. + + [Upstream Issue] + https://gitlab.gnome.org/GNOME/gdm/-/issues/684 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918613 Title: [FFe] GDM background configurable with gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918643] [NEW] package libjpeg-progs 8c-2ubuntu7 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-turbo-progs 1.1.90+svn733-0ubuntu4.1
Public bug reported: This warning appears when I call some apps, Terminal included (yes, I'm working in a desktop environment) ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libjpeg-progs 8c-2ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 AptOrdering: libjpeg9:amd64: Install libjpeg-progs:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Mar 11 06:50:08 2021 ErrorMessage: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-turbo-progs 1.1.90+svn733-0ubuntu4.1 InstallationDate: Installed on 2021-03-09 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu7 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-turbo-progs 1.1.90+svn733-0ubuntu4.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libjpeg8-empty (Ubuntu) Importance: Undecided Status: New ** 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/1918643 Title: package libjpeg-progs 8c-2ubuntu7 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg- turbo-progs 1.1.90+svn733-0ubuntu4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1918643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892475] Re: /usr/bin/ld: utils.o:(.data.rel.local+0x0): multiple definition of `xprintf'; xs_tdb_dump.o:(.bss+0x0): first defined here collect2: error: ld returned 1 exit status
Hello Marietto, If I understand correctly you are having problems compiling igvtg-xen from the upstream source code. In this case this bug tracker is not the right place where to report this issue, as we use it to track bugs in Ubuntu, and not issues or incompatibilities with third-party projects. This unless the problem you hit is a problem with the (Ubuntu packaged) GCC, but I don't think this is the case; more likely there's an incompatibility between igvtg-xen and the version of gcc/glibc in Focal, which is however working as expected. You can find pointers to get help for this sort of problem here: https://ubuntu.com/support/community-support If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is specifically a bug in Ubuntu, and then change the bug status back to New. Thanks! ** Changed in: xen (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892475 Title: /usr/bin/ld: utils.o:(.data.rel.local+0x0): multiple definition of `xprintf'; xs_tdb_dump.o:(.bss+0x0): first defined here collect2: error: ld returned 1 exit status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1892475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912783] Re: west-chamber-dkms fails to build after ip_route_me_harder() signature change
I can confirm that west-chamber=20100405+svn2007.r124-8ubuntu0.1 can be installed and compiled with the latest 4.15 and 5.4 kernels in bionic: $ dkms status west-chamber, 20100405+svn2007.r124, 4.15.0-137-generic, x86_64: installed west-chamber, 20100405+svn2007.r124, 5.4.0-67-generic, x86_64: installed xtables-addons, 3.0, 4.15.0-137-generic, x86_64: installed xtables-addons, 3.0, 5.4.0-67-generic, x86_64: installed The autopkgtests were also successful: bionic/linux amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/amd64/w/west- chamber/20210311_104034_5e19d@/log.gz bionic/linux-hwe-5.4 amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/amd64/w/west- chamber/20210311_104313_48486@/log.gz ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912783 Title: west-chamber-dkms fails to build after ip_route_me_harder() signature change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/west-chamber/+bug/1912783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918497] Re: connect to one shared folder error package
Thank you for your bug report. * which packages did you upgrade? * how do you try to connect? * what error do you get exactly? (could take a screenshot showing it) ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918497 Title: connect to one shared folder error package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1918497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918641] [NEW] migration to ubuntu20.04 failed
Public bug reported: problem with python2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 11:37:17 2021 InstallationDate: Installed on 2017-01-06 (1524 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-03-11 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade 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/1918641 Title: migration to ubuntu20.04 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1918641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915275] Re: mysql-8.0 regressed on riscv64 due to new glibc
I was following: - https://dev.mysql.com/doc/refman/8.0/en/using-gdb-on-mysqld.html I - https://dev.mysql.com/doc/refman/8.0/en/crashing.html Which mostly comes down to: $ apt source mysql-server-8.0 $ apt install gdb mysql-server-core-8.0-dbgsym libc6-dbg libstdc++6-dbgsym $ sudo gdb /usr/sbin/mysqld (gdb) run --skip-stack-trace --gdb --core-file --general-log --general-log-file --verbose --innodb-read-only --help --debug To be clear - in a normal working environment that would not even start the server for real - it would initialize a bit and then report on the used and possible config options. For comparison in a similar environment I'll also use 8.0.23-0ubuntu0.20.04.1 in Focal. Hoping that this might help to differentiate the noise from data. But since things work there I'll need to find which function to break on ... I'll attach an initial backtrace here ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915275 Title: mysql-8.0 regressed on riscv64 due to new glibc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1915275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900775] Fix included in openstack/cinder 16.3.0
This issue was fixed in the openstack/cinder 16.3.0 release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900775 Title: Cinder fails to create image-based volume if mirroring is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-rbd-mirror/+bug/1900775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918623] [NEW] upgrade 16.04 to 18,04 on ppc64 failed
Public bug reported: update fails ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.32 ProcVersionSignature: Ubuntu 4.4.0-203.235-powerpc64-smp 4.4.249 Uname: Linux 4.4.0-203-powerpc64-smp ppc64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: powerpc CrashDB: ubuntu Date: Thu Mar 11 11:19:09 2021 InstallationDate: Installed on 2017-08-15 (1303 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release powerpc (20160719) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2021-03-11 (0 days ago) VarLogDistupgradeAptlog: Log time: 2021-03-11 11:18:15.424787 Log time: 2021-03-11 11:18:20.487800 Log time: 2021-03-11 11:18:59.486217 Log time: 2021-03-11 11:19:15.487118 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug dist-upgrade powerpc xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918623 Title: upgrade 16.04 to 18,04 on ppc64 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1918623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all
Thanks for checking, so your computer should have the fix already. Do you still having this audio (no sound at all) issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651500 Title: [ASUS X441SA] [8086:2284] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913189] Re: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1
Thanks everyone for getting it fixed! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913189 Title: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1913189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907422] Re: [MIR] needrestart + dependencies
Regarding needrestart per-se: Dan, I pushed a new version of needrestart to hirsute including a sanity-test autopkgtest - could you take a look if that is good enough? One note: currently the test is failing on armhf (but not blocking, as this was the first time it ran). The reason for that is that apparently kernel checking does not work on armhf right now. Basically what is happening is that needrestart is skipping kernel checks, which is something the test does not expect. I was thinking of making the test skip the kernel checks if they cannot be performed, but then again I think this might be an actual regression in the current needrestart version. Which makes me think if maybe we should leave it as is and simply report it upstream - because I don't see this mentioned as a 'known issue'. I see Debian had a bug for armhf kernel detection not working in 2015 [1], but this seemed to be fixed in 2016 with needrestart 1.8. So I'd expect armhf having full functionality. Anyway, right now needrestart has migrated to release. I'll send a bug report to Debian about armhf and forward the autopkgtest, if you're fine with how it looks right now. Do you think if I can promote all the things to main now? Thanks! [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800720 ** Bug watch added: Debian Bug tracker #800720 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800720 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907422 Title: [MIR] needrestart + dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libintl-perl/+bug/1907422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)
** Tags removed: 5.8 hwe-5.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912316 Title: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1912316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909022] Re: Ardour crashes when using the Calf Limiter LV2 plugin and tying to raise the Oversampling parameter to 4
Little tip to the workaround from Erich Eickmeyer I found out the the same... Ardour crashes when parameter "Oversampling" has the value "4" Because of this i was unable to open my Ardour and Mixbus files anymore. To save the work with enabling/disabling all plugins open the affected .ardour file in a text-editor and search for "Calf Limiter". under "active" change the value "1" to "0" and save and close. Now you can open the file in Ardour/Mixbus again and change the parameter "Oversampling" from 4 to to a value between 1 and 3. After this you can enable the Calf Limiter plugin again. You will do this on our own risk! you should make a backup before manipulating the .ardour file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909022 Title: Ardour crashes when using the Calf Limiter LV2 plugin and tying to raise the Oversampling parameter to 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calf/+bug/1909022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915177] Re: xtables-addons fails to build after ip_route_me_harder() signature change
Thanks MikeR for your tests! I can also confirm that xtables-addons 3.9-1ubuntu0.2~20.04.1 can be installed and compiled with both 5.4 and 5.8 kernels in Focal: $ dkms status xtables-addons, 3.9, 5.4.0-66-generic, x86_64: installed xtables-addons, 3.9, 5.8.0-45-generic, x86_64: installed The autopkgtest with the latest kernels in -proposed were also successful: * focal/linux amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/x/xtables-addons/20210311_100438_52f1a@/log.gz * focal/linux-hwe-5.8 amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/x/xtables-addons/20210311_100607_a6229@/log.gz Thank you! ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915177 Title: xtables-addons fails to build after ip_route_me_harder() signature change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1915177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918619] Re: Kind of slowly refresh
Actually there is more, as it's shown on this other video. The same problem happens when “there is a display event”…? Like when my mouse go over an element, even if I can't click on it. ** Attachment added: "VID_20210311_105952.mp4" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1918619/+attachment/5475721/+files/VID_20210311_105952.mp4 ** Description changed: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. + + EDIT: I remember having this problem a year ago perhaps, and it + disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Lenovo HD Graphics 620 [17aa:39e9] + Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918619 Title: Kind of slowly refresh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1918619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909734] Re: TPM PCR checking will fail if the all characters are 0
** Tags added: originate-from-1918600 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909734 Title: TPM PCR checking will fail if the all characters are 0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1909734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)
Hi Kelsey, I think the failure for starmie-kernel deserves a new bug (as it's not failing with code 2048). Thus I opened bug 1918620 Let's track this there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912316 Title: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1912316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918583] Re: Switch to libgpiod and disable CONFIG_GPIO_SYSFS
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918583 Title: Switch to libgpiod and disable CONFIG_GPIO_SYSFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918619] [NEW] Kind of slowly refresh
Public bug reported: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "sample of the problem" https://bugs.launchpad.net/bugs/1918619/+attachment/5475701/+files/VID_20210311_104202.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918619 Title: Kind of slowly refresh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1918619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904583] Re: SRU: Backport the latest developments on drivers detection and hybrid graphics
Also, once the FTBFS is resolved, this is still blocked on LP: #1915003. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904583 Title: SRU: Backport the latest developments on drivers detection and hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1904583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915003] Re: SRU: Always update the initramfs when changing power profile
Can we get this verified? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916558] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916558 Title: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1916558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
