[Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
arm64.nopauth regulator_ignore_unused modprobe.blacklist=qcom_q6v5_pas are required to boot from usb, but then there is a problem with USB, resulting in an endless loop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061158] [NEW] package libc-dev-bin 2.31-0ubuntu9.14 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Public bug reported: During running `sudo do-release-upgrade` many packages fail to install with `.dpkg-query: no packages found matching ...`, including libc. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libc-dev-bin 2.31-0ubuntu9.14 ProcVersionSignature: Ubuntu 5.15.0-102.112~20.04.1-generic 5.15.148 Uname: Linux 5.15.0-102-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 12 08:34:50 2024 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2021-06-18 (1028 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.8 apt 2.0.5 SourcePackage: glibc Title: package libc-dev-bin 2.31-0ubuntu9.14 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2024-04-12 (0 days ago) ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061158 Title: package libc-dev-bin 2.31-0ubuntu9.14 failed to install/upgrade: dpkg- deb --control subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2061158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880495] Re: Upgrade from 1.95 to 2.35 failure because column maasserver_domain.ttl does not exist
** Also affects: maas/3.3 Importance: Undecided Status: New ** Also affects: maas/3.4 Importance: Undecided Status: New ** Changed in: maas/3.3 Status: New => Won't Fix ** Changed in: maas/3.4 Status: New => Won't Fix ** Changed in: maas/3.3 Importance: Undecided => Medium ** Changed in: maas/3.4 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/1880495 Title: Upgrade from 1.95 to 2.35 failure because column maasserver_domain.ttl does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1880495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969510] Re: MAAS deletes image architectures if you delete all images of that architecture
** Also affects: maas/3.4 Importance: Undecided Status: New ** Changed in: maas/3.4 Status: New => Won't Fix ** Changed in: maas/3.4 Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969510 Title: MAAS deletes image architectures if you delete all images of that architecture To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1969510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838247] Re: apt remove maas-region-controller causes broken DB state
** Changed in: maas Milestone: 3.5.0 => 3.5.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838247 Title: apt remove maas-region-controller causes broken DB state To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1838247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969510] Re: MAAS deletes image architectures if you delete all images of that architecture
** Changed in: maas Milestone: 3.4.x => 3.5.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969510 Title: MAAS deletes image architectures if you delete all images of that architecture To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1969510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880495] Re: Upgrade from 1.95 to 2.35 failure because column maasserver_domain.ttl does not exist
** Changed in: maas Milestone: 3.4.x => 3.5.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880495 Title: Upgrade from 1.95 to 2.35 failure because column maasserver_domain.ttl does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1880495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887558] Re: Multipath JBOD storage devices are not shown via /dev/mapper but each path as a single device.
** Changed in: maas Milestone: 3.5.0 => 3.5.0-beta1 ** Changed in: maas 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/1887558 Title: Multipath JBOD storage devices are not shown via /dev/mapper but each path as a single device. To manage notifications about this bug go to: https://bugs.launchpad.net/bcache-tools/+bug/1887558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865515] Re: Chainbooting from grub over the network to local shim breaks chain of trust
** Changed in: maas Milestone: 3.5.0 => 3.5.0-beta1 ** Changed in: maas 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/1865515 Title: Chainbooting from grub over the network to local shim breaks chain of trust To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003745] Re: Cannot deploy older Ubuntu releases
** Changed in: maas 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/2003745 Title: Cannot deploy older Ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2003745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003745] Re: Cannot deploy older Ubuntu releases
** Changed in: maas Milestone: 3.5.0 => 3.5.0-beta1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003745 Title: Cannot deploy older Ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2003745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055805] [NEW] tochpad do not working with kernel 6.8
Public bug reported: After the standard update procedure and installation of a new version of the kernel, the touchpad on the MacBook Pro 13 - 2014 stopped working. Even the mouse cursor does not appear on the screen. If you select the old kernel version 6.6 in the bootloader options, then everything works correctly Ubuntu 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 11:11:43 2024 InstallationDate: Installed on 2023-11-06 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.6.0-14-generic root=UUID=2075733d-58de-4836-9c71-04dd00378200 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 430.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr430.0.0.0.0:bd12/17/2020:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: tochpad do not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975467] [NEW] package passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] failed to install/upgrade: unable to make backup link of './usr/bin/passwd' before installing new
Public bug reported: While updating Ubuntu 20.04.4 TLS I'm getting an error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 23 11:45:21 2022 DuplicateSignature: package:passwd:1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] Unpacking passwd (1:4.8.1-1ubuntu5.20.04.2) over (1:4.8.1-1ubuntu5.20.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-43VTuR/5-passwd_1%3a4.8.1-1ubuntu5.20.04.2_amd64.deb (--unpack): unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted ErrorMessage: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted InstallationDate: Installed on 2021-05-24 (363 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: shadow Title: package passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] failed to install/upgrade: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975467 Title: package passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] failed to install/upgrade: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1975467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965536] Re: Network icon disappeared in Unity
Had the same problem but it seems to be fixed after installing 'indicator-applet' and 'indicator-application' packages. I think they were removed during upgrade for some reason. I'm not sure both of them are required and believe 'indicator-applet' could fix this alone, but I'm just happy network icon is back and too lazy to double check which package fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965536 Title: Network icon disappeared in Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1965536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
I just installed the -proposed package and still no dice. Could someone post (here or elsewhere) a instructions for getting this working from scratch as of today? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
I was able to configure switching languages input by Alt + Shift combination in Ubuntu 22.04 by instruction here - https://askubuntu.com/a/1407561/1548713 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
@linrunner: Thanks for the explanation that tlp will mostly work without acpi-call-dkms and completely without it in the future! Also your warning hint from the TLP doc might help some people here: "Warning: On Ubuntu 21.10 and 20.04.4 the acpi-call-dkms packages in the official repositories are incompatible with the provided kernel 5.13 and may cause TLP battery care malfunction, system freezes and reboots. Solution: use acpi-call-dkms version 1.2.2 from the TLP PPA or download from Ubuntu 22.04 and install manually." – https://linrunner.de/tlp/installation/ubuntu.html#thinkpads-only @raph: Still this package is not fixed for Ubuntu 20.04 and could render more laptops unbootable. The bug status „Fix released“ is not true for 20.04. Could someone maybe adjust the bug status? Could you provide some insight what's holding you back to get the fix into Ubuntu 20.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953261 Title: kernel >= 5.13 BUG: kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
Thanks! Unfortunally not possible to switch to legacy boot like this. Also I think I've read somewhere that efivars can only be accessed from a uefi boot session. No I have not set something like "efi_no_storage_paranoia". It was a standard ubuntu 20.04 installation with tlp installed from the official package sources. Same on my two brothers laptops. From the dpkg.log of my brother: `2022-01-20 09:55:50 install linux-image-5.13.0-27-generic:amd64 5.13.0-27.29~20.04.1` This was when the error message started to appear. On my laptop the day before I was locked out, I did a copy of the /sys/firmware/efi/efivars folder. Would that help you? The only thing is, that when copying these files using nautilus, the dump-* files could not be copied. They became empty files, although they were about 10-20kB. The other files are 19.4kB. Do you know a way to find out the total available size of the NVRAM? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953261 Title: kernel >= 5.13 BUG: kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
Thanks for your reply raph! Yes I tried pressing F1 repeatedly after pressing the power button. I also tried using an external USB keyboard. Also tried F12 for boot menu. But the error seems to block startup before it checks if F1/F12 are pressed. As described earlier, the first two/three times or so the error appeared it was actually possible to enter bios setup with F1. Sadly I didn't find the cause of the error soon enough. So now the NVRAM seems to be so full, it can't even enter BIOS or listen to keys pressed :( I brought my laptop to a local repair store. They couldn't fix it themselves but will send it to a store in berlin specialized on motherboard repairs an firmware flashing. If I understood correctly, clearing NVRAM completely could also make the laptop unbootable. I hope they can somehow clear and reinstall the original firmware image using a special hardware interface. I will report any progress. If you have any other ideas, I can do tests with the other broken laptop of my brother. Thanks a lot for your interest! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953261 Title: kernel >= 5.13 BUG: kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
I could imagine that this error potentially also affects other Thinkpad models. Of course if they have a larger NVRAM it will take longer for the dump files to fill it up. Maybe even weeks if only a few dump files are generated with each restart. At least some newer models like the X1 Yoga seem to have a firmware option to clear the storage if full: See Hardware Maintenance Manual page 45 https://download.lenovo.com/pccbbs/mobiles_pdf/tp_x1_carbon- yoga_hmm_en.pdf#page=45=auto,-195,488 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953261 Title: kernel >= 5.13 BUG: kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
Sadly no. When turning the laptop on, there is the info screen with bios version etc. visible for two seconds. Then the Error Message appears: „Error: The non-volatile variable storage is about full. Press F1 to enter Setup.“ At first it was possible to enter BIOS setup and then exit the setup to continue boot. But after two restarts pressing F1 just doesn't work anymore. The error screen just stays. The only thing I can do is power down and startup again to re-arrive at the error screen. I removed CMOS-Battery for halve an hour. The only thing that changed is that the error page now additionally shows the line „0271: Real Time Clock Error – Check Date and Time settings.“ above the line with the non-volatile error. Still no way to enter BIOS setup or boot from USB. As mentioned above this happened to two different Thinkpad x131e in different cities from me and my brother. My second brother could be warned in time to apply the fix from nix-community while booting was still possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953261 Title: kernel >= 5.13 BUG: kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic
Good morning! Yesterday my Kernel was updated to 5.13.0-28-generic via the regular update cycle: I can connfirm that my problem is fixed too, Thanks to you all! Am 31.01.22 um 21:42 schrieb Dan: > Hey everyone! kernel version 5.13.0-28-generic is out and it seems to > fix this issue! Myself and another user were already able to confirm > that. Good luck everyone! > -- Kontakt: Ing. Anton Lettenbichler Prof.-Böhm-Straße 6 4870 Vöcklamarkt Fon: +43(0)699 1105 76 69 E-mail: anton.lettenbich...@geosono.com Web: www.geosono.com Firma: geosono - Anton Lettenbichler e.U. Sitz des Unternehmens: Vöcklamarkt FirmenbuchNr: FN 311210 m Firmenbuchgericht: Landesgericht Wels UID/VAT-ID: ATU64165423 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958724 Title: System Shutdown and resume hangs since Kernel linux- image-5.13.0-23-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
Me and my brothers each own a Thinkpad x131e and were running Ubuntu 20.04 with tlp very smoothly. Until with the recent kernel update 5.13 three weeks ago each of us encountered the error `Error: The Non-Volatile Variable Storage is About Full` on boot. At first the error could be ignored by entering BIOS setup and save settings. But after a few restarts it was stuck when the error message appears, not even being able to enter BIOS setup or to boot. Unlike newer Thinkpads (e.g. X1) this model does not provide a firmware option to clear the NVRAM storage if it is full. Two of us could not resolve the issue before this to happen – so our ThinkPads are now BRICKED!!! At least one of us could rescue his Laptop so far by deleting the dump-* files in /etc/firmware/efi/efivars and not restarting the laptop, only using standby. We then found the fix by https://gist.github.com/roadkell/9e98db6656e28fbbf1bf51082040f67f and manually installing the acpi-call module 1.2.2 from the nix-community made the error on boot go away. So big thanks to them! I know this bug is not the fault of the Ubuntu team, but nevertheless it's quite unacceptable that an update destroys our hardware. This got me in the middle of my exams and a project I had to finish. I know some people would say this laptop model is quite old, buy a new one. But I choose Ubuntu because of sustainability – because it doesn't force you to buy new hardware every two years. Me and my brothers had our ThinkPad x131e's perfectly up to speed with modern SSD and RAM doing audio editing and blender animations. And now it's just not booting anymore because NVRAM memory chip is full. So I suggest getting the acpi-call package version 1.2.2 into every release of Ubuntu as soon as possible so no more hardware gets destroyed! I hope I will find someone who can somehow physically reset the chip on the motherboards that are now unbootable. Removing the CMOS-Battery did not clear the NVRAM. Any thoughts on this? Any help appreciated! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953261 Title: kernel >= 5.13 BUG: kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893753] Re: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17
> Maybe you can help me to extend that example to show the issue? As mentioned in the original bug report for this [1], the easiest way to reproduce the issue is to add an empty `init_worker_by_lua_block` block to the `http` section of the nginx config. [1] https://github.com/openresty/lua-nginx-module/issues/1714 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893753 Title: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1893753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959070] [NEW] NO standby or shutdown possible (5.13.0.27)
Public bug reported: I am using Xubuntu (actual LTS-version) with AMD-Ryzen with Kernel: 5.13.0.27 there is no regular powerdwn or Standby possible: The system does not switch off with: "tl@tl-as:~$ shutdown now -h" too; If I boot with the last version in the boot options (5.11.0.46) I can use Standby, Powerdown again normally Additional infos: Description:Ubuntu 20.04.3 LTS Release:20.04 -Systemstarts- Wed Jan 26 07:44: 5.13.0-27-generi Wed Jan 26 08:01: 5.11.0-46-generi Wed Jan 26 06:55: 5.13.0-27-generi Wed Jan 26 04:39: 5.13.0-27-generi Tue Jan 25 20:33: 5.13.0-27-generi Tue Jan 25 12:40: 5.13.0-27-generi Tue Jan 25 06:53: 5.13.0-27-generi Tue Jan 25 06:51: 5.13.0-27-generi Tue Jan 25 06:46: 5.13.0-27-generi Tue Jan 25 04:31: 5.13.0-27-generi Mon Jan 24 22:15: 5.13.0-27-generi Mon Jan 24 11:42: 5.13.0-27-generi Mon Jan 24 08:38: 5.13.0-27-generi Sun Jan 23 06:27: 5.11.0-46-generi Wed Jan 19 09:16: 5.11.0-46-generi Tue Jan 18 19:19: 5.11.0-46-generi ** Affects: linux (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/1959070 Title: NO standby or shutdown possible (5.13.0.27) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806291] Re: [needs-packaging] Boot-Repair pre-installed in ISOs
Do not see how to vote for this issue. +1 for including the tool. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806291 Title: [needs-packaging] Boot-Repair pre-installed in ISOs To manage notifications about this bug go to: https://bugs.launchpad.net/boot-repair/+bug/806291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953722] [NEW] package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
Public bug reported: -( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.8.0-59-generic:amd64: Remove linux-hwe-5.8-headers-5.8.0-59:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 10:42:13 2021 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2020-07-09 (517 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: Error: command ['readlink', '-f', "ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. , Error: [Errno 2] Нет такого файла или каталога: 'Error: command [\'readlink\', \'-f\', "ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n', unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953722 Title: package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953721] [NEW] package linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
Public bug reported: _( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.8.0-59-generic:amd64: Remove linux-hwe-5.8-headers-5.8.0-59:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 10:42:13 2021 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2020-07-09 (517 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: Error: command ['readlink', '-f', "ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. , Error: [Errno 2] Нет такого файла или каталога: 'Error: command [\'readlink\', \'-f\', "ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n', unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953721 Title: package linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933771] Re: Bluetooth headset random disconnects AX200
Confirming, did not see any disconnects for past two weeks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933771 Title: Bluetooth headset random disconnects AX200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893753] Re: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17
Hey Christian, thanks for the update and for sharing the new packages via PPA. I have installed them on a few Focal machines that have lua module enabled in nginx, and can confirm that the nginx process no longer crashes on startup, and that lua module works fine for my use cases (tracking metrics). I posted an update to https://github.com/openresty/lua-nginx- module/issues/1714 where this issue was initially reported, perhaps other folks will be able to test the new packages too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893753 Title: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1893753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945343] [NEW] Headerbar is broken due to libhandy bug
Public bug reported: When removable media is mounted gnome-photos headerbar became too big. This is due to a bug in libhandy. upsteam bug: https://gitlab.gnome.org/GNOME/gnome-photos/-/issues/172 fix commit: https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/761 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-photos 40.0-2 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 28 18:49:34 2021 InstallationDate: Installed on 2021-04-13 (168 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: gnome-photos UpgradeStatus: Upgraded to impish on 2021-09-27 (1 days ago) ** Affects: gnome-photos (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "gnome-photos.png" https://bugs.launchpad.net/bugs/1945343/+attachment/5528729/+files/gnome-photos.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945343 Title: Headerbar is broken due to libhandy bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-photos/+bug/1945343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926084] Re: [hirsute] Bluetooth speakers reconnect randomly
Issue occurs in impish as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926084 Title: [hirsute] Bluetooth speakers reconnect randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942883] [NEW] dont work laptop screen on intel uhd 620
Public bug reported: dont work laptop screen on intel uhd 620 driver big screen on connected by hdmi work correct ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Sep 7 14:30:54 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8538] InstallationDate: Installed on 2021-08-18 (19 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ProBook 450 G6 ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=08563b86-ae87-4e89-a3a7-9da18c4c8ca9 ro xdg.force_integrated=1 modprobe.blacklist=nouveau SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2020 dmi.bios.release: 14.1 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.14.01 dmi.board.name: 8538 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2D.00 dmi.chassis.asset.tag: 5CD944621W dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 81.45 dmi.modalias: dmi:bvnHP:bvrR71Ver.01.14.01:bd10/19/2020:br14.1:efr81.45:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2D.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G6 dmi.product.sku: 5PQ05EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107+git2109030500.d201a4~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.3~git2109070600.27f2c9~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 21.3~git2109070600.27f2c9~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942883 Title: dont work laptop screen on intel uhd 620 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1942883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42097] Re: Installer crashed after "Who are you?" step (Kubuntu 6.06 live)
anton_wes...@t-online.de continuing: by discover I have removed the package of installer and habe reinstalled; no change: again installer crashed and again with cause of MD5 checksum error, ans again at libnvidia...418... Regards anton_wes...@t-online.de -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/42097 Title: Installer crashed after "Who are you?" step (Kubuntu 6.06 live) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/42097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42097] Re: Installer crashed after "Who are you?" step (Kubuntu 6.06 live)
anton_wes...@t-online.de continuing: unfortunately the Collected data and the Apport I can only send to you, not to myself, am not able to get a copy on a file. yet, with a magnified lens, I could read tha the cause is a MD5 checksum error caused by libnvidia...418... in muon I saw: a) such a package is not installed; b) ...418... are transient packaged; by muon I installed all packegas for nvidia with number 390. but again installer crashed. in the Collected data and the Apport I saw, that nevertheless ...418... caused MD5 checksum error. the new packeges I installed had nor been used. Regards anton_wes...@t-online.de -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/42097 Title: Installer crashed after "Who are you?" step (Kubuntu 6.06 live) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/42097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42097] Re: Installer crashed after "Who are you?" step (Kubuntu 6.06 live)
I am runnung kubuntu 20.04.LTS from a USB stick, which I have bought. Before of about two days I hav successfully installed on a HDD. Always same HDD: Partitioning made "manually", but always similar. The window "Ubuntu Apport" shows the cause: "CasperMD5CheckMismatch" (the file I have sent to you). and at the same time in my terminal "Konsole" was this displayed: root@kubuntu:~# ubuntu-bug ubiquity QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) Why in the last days (automatically ?) the MD5 checksum is gone defective? the collected data file, which I have sent to you, contains some information which and whar is false. I now have not the information, what I should re-install. Regards anton_wes...@t-online.de -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/42097 Title: Installer crashed after "Who are you?" step (Kubuntu 6.06 live) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/42097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Media keys back to normal, mouse is ok too, but Fn+F4 and Fn+F10 are not working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
With v7 it seems that Fn+F4 and Fn+F10 still do nothing, however other media keys got Mute Mic mapping as well as their primary function. For example if I press Vol+ I hear that volume increased but also GNOME shows that microphone become muted. This happens for mute, vol+, vol- and playback control keys. This seems also bugs window manager since after pressing media key input from keyboard become unavailable until I switch to another window. As for mouse it works as expected now. ** Attachment added: "dmesg with v7" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+attachment/5507012/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
I believe you are talking about v7 kernel. I've tried it and for this version dmesg was sielent on Fn+F4 and Fn+F10 pressing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932336] Re: Numerous ACPI BIOS Error (bug) errors during boot
Thank you for clarification. Yes, system looks stable. The only thing that bothers is that these messages are visible for a moment during power off/suspend. Please close this ticket -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932336 Title: Numerous ACPI BIOS Error (bug) errors during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Hi Chris, difference between full log and one I attached to previous comment is that in the full one contained line "usage 0 hid: 0x0c index 0x00 code 0x00 type 0x0" repeated endlessly. I rebooted system once log file was filled with that line up to ~150 mb. If anything else should be in that log then it didn't appear in about minute after pressing keys. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Here what I was able to extract with the latest kernel: Fn+F4 [ 44.615947] lenovo_raw_event data 0x1:0x0:0x0 [ 44.615950] report id/type/app: 1/0/786433 maxfield: 1 [ 44.615952] field 0 physical: 0x00 logical 0x00 app 0x0c0001 flags 0x00, max usage 573 [ 44.615953] usage 0 hid: 0x0c index 0x00 code 0x00 type 0x0 Fn+F10 [ 51.971153] lenovo_raw_event data 0x1:0x0:0x0 [ 51.971183] report id/type/app: 1/0/786433 maxfield: 1 [ 51.971185] field 0 physical: 0x00 logical 0x00 app 0x0c0001 flags 0x00, max usage 573 [ 51.971188] usage 0 hid: 0x0c index 0x00 code 0x00 type 0x0 After pressing fn+Fx keys keyboard and mouse stopped to work and last line in logs above was printed forever. ** Attachment added: "dmesg with v6" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+attachment/5505510/+files/fnF10dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932336] [NEW] Numerous ACPI BIOS Error (bug) errors during boot
Public bug reported: I've noticed that on every boot numerous errors appears: [2.547015] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.IEC.ECRD], AE_NOT_FOUND (20201113/psargs-330) [2.547028] No Local Variables are initialized for Method [_TMP] [2.547030] No Arguments are initialized for method [_TMP] [2.547033] ACPI Error: Aborting method \_SB.PCI0.LPCB.I_EC.SEN2._TMP due to previous error (AE_NOT_FOUND) (20201113/psparse-529) [2.547381] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.IEC.ECRD], AE_NOT_FOUND (20201113/psargs-330) [2.547388] No Local Variables are initialized for Method [_TMP] [2.547389] No Arguments are initialized for method [_TMP] [2.547391] ACPI Error: Aborting method \_SB.PCI0.LPCB.I_EC.SEN2._TMP due to previous error (AE_NOT_FOUND) (20201113/psparse-529) [2.547398] thermal thermal_zone2: failed to read out thermal zone (-5) [2.547459] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.IEC.ECRD], AE_NOT_FOUND (20201113/psargs-330) [2.547465] No Local Variables are initialized for Method [_TMP] [2.547466] No Arguments are initialized for method [_TMP] [2.547468] ACPI Error: Aborting method \_SB.PCI0.LPCB.I_EC.SEN3._TMP due to previous error (AE_NOT_FOUND) (20201113/psparse-529) [2.547583] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.IEC.ECRD], AE_NOT_FOUND (20201113/psargs-330) [2.547589] No Local Variables are initialized for Method [_TMP] [2.547590] No Arguments are initialized for method [_TMP] [2.547592] ACPI Error: Aborting method \_SB.PCI0.LPCB.I_EC.SEN3._TMP due to previous error (AE_NOT_FOUND) (20201113/psparse-529) [2.547598] thermal thermal_zone3: failed to read out thermal zone (-5) [2.547642] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.IEC.ECRD], AE_NOT_FOUND (20201113/psargs-330) [2.547647] No Local Variables are initialized for Method [_TMP] [2.547648] No Arguments are initialized for method [_TMP] [2.547650] ACPI Error: Aborting method \_SB.PCI0.LPCB.I_EC.SEN4._TMP due to previous error (AE_NOT_FOUND) (20201113/psparse-529) [2.547901] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.IEC.ECRD], AE_NOT_FOUND (20201113/psargs-330) [2.547906] No Local Variables are initialized for Method [_TMP] [2.547907] No Arguments are initialized for method [_TMP] [2.547909] ACPI Error: Aborting method \_SB.PCI0.LPCB.I_EC.SEN4._TMP due to previous error (AE_NOT_FOUND) (20201113/psparse-529) [2.547915] thermal thermal_zone4: failed to read out thermal zone (-5) [2.547980] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.IEC.ECRD], AE_NOT_FOUND (20201113/psargs-330) [2.547985] No Local Variables are initialized for Method [_TMP] [2.547987] No Arguments are initialized for method [_TMP] [2.547988] ACPI Error: Aborting method \_SB.PCI0.LPCB.I_EC.SEN5._TMP due to previous error (AE_NOT_FOUND) (20201113/psparse-529) [2.548230] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.IEC.ECRD], AE_NOT_FOUND (20201113/psargs-330) [2.548235] No Local Variables are initialized for Method [_TMP] [2.548237] No Arguments are initialized for method [_TMP] [2.548238] ACPI Error: Aborting method \_SB.PCI0.LPCB.I_EC.SEN5._TMP due to previous error (AE_NOT_FOUND) (20201113/psparse-529) Seems that it's not affecting how PC works, just could be seen for a moment during poweroff/reboot. I'm not sure what could cause these errors so I don't know what else I can provide. This happens on the Lenovo AiO PC, full specs are listed here https://psref.lenovo.com/Detail/IdeaCentre/IdeaCentre_AIO_5_27IMB05?M=F0FA0066UA ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Jun 17 18:27:43 2021 InstallationDate: Installed on 2021-04-13 (65 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RebootRequiredPkgs: gnome-shell RelatedPackageVersions:
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Here is what dmesg shows now: Fn+F4 [ 90.603608] lenovo_raw_event data 0x1:0x0:0x0 [ 90.603611] report id/type/app: 3223070016/1/0 maxfield: 786433 [ 90.603612] field 0 hid usage hid: 0x0c index 0x00 Fn+F10 [ 95.779641] lenovo_raw_event data 0x1:0x0:0x0 [ 95.779652] report id/type/app: 3223070016/1/0 maxfield: 786433 [ 95.779670] field 0 hid usage hid: 0x0c index 0x00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
No worries, thats might happen for everyone. Some good news, now there is some reaction on both keys in dmesg: [ 28.599434] (efault) data 0x0:0x00x0 Message is the same for Fn+F4 and Fn+F10. Mouse still work in weird way with mouse wheel not working. There is also a quirk that restart entry in gnome-shell reacts only on right click, left-clicking makes menu disappear. ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+attachment/5504727/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
v4 folder seems empty for me. Am I overlooking something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Sure, here it is. ** Attachment added: "dmesg with v3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+attachment/5504017/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Keyboard worked with new kernel, however Fn+F4 still doesn't functional. I've also noticed that mouse middle button stopped to work (both scrolling and clicking) on this version. dmesg doesn't show anything on pressing Fn+F4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
With v2 both keyboard and mouse from Lenovo Essentials set stopped to work. Fortunately I had a replacement so I still was able to check what happens. Seems that they stopped to be recognized as input devices, at least there were no messages like following in dmesg input: Primax Lenovo Essential Wireless Keyboard and Mouse Combo as /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/0003:17EF:60A9.0001/input/input3 hid-generic 0003:17EF:60A9.0001: input,hidraw0: USB HID v1.11 Keyboard [Primax Lenovo Essential Wireless Keyboard and Mouse Combo] on usb-:00:14.0-5/input0 input: Primax Lenovo Essential Wireless Keyboard and Mouse Combo as /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.1/0003:17EF:60A9.0002/input/input4 hid-generic 0003:17EF:60A9.0002: input,hidraw1: USB HID v1.11 Mouse [Primax Lenovo Essential Wireless Keyboard and Mouse Combo] on usb-:00:14.0-5/input1 input: Primax Lenovo Essential Wireless Keyboard and Mouse Combo as /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.2/0003:17EF:60A9.0003/input/input5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
I've checked provided kernel and seems nothing has changed. Keys still does't work and dmesg is sielent when I'm pressing mic mute. For Fn+F10 it seems that the closest behavior would be to take selective screenshot. But if there is no such event defined that it might be mapped as a generic Fn button so it still could be used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Hi Chris, Here is what I've got running these command in parallel mute: # cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 # cat /sys/kernel/debug/hid/0003\:17EF\:60A9.0003/events report (size 3) (numbered) = 01 00 00 Fn+F10: # cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 # cat /sys/kernel/debug/hid/0003\:17EF\:60A9.0003/events report (size 3) (numbered) = 01 00 00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Hi Chris, Here is output of the cat /sys/kernel/debug/hid/0003\:17EF\:60A9.0003/events report (size 3) (numbered) = 01 00 00 # for Fn+F4 report (size 3) (numbered) = 01 00 00 # for Fn+F10 I've added rdesc as attachment as it quite long. ** Attachment added: "cat /sys/kernel/debug/hid/0003\:17EF\:60A9.0003/rdesc" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+attachment/5502431/+files/rdesc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913634] Re: Touchpad not working with 20.04 on ThinkBook 13s IML
Still reproducing on Ubuntu 20.04.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913634 Title: Touchpad not working with 20.04 on ThinkBook 13s IML To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1913634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904213] Re: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
Confirming, that workaround from #4 also fixes that issue in Ubuntu 20.04.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1904213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] [NEW] Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Public bug reported: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926084] [NEW] Bluetooth speakers reconnect randomly
Public bug reported: Bluetooth speakers reconnect randomly. The onlt workaround that seems to work is to remove speakers from paired devies, restart buetooth service and connect them once again. Once these stepss are performed connection become stable until reboot or hibernation. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Apr 25 17:22:11 2021 InstallationDate: Installed on 2021-04-13 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 44:AF:28:F7:A9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:2239397 acl:225 sco:0 events:318945 errors:0 TX bytes:207283666 acl:315238 sco:0 commands:3564 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926084 Title: Bluetooth speakers reconnect randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925766] [NEW] extensions disabled after upgrade
Public bug reported: I updated yesterday (I think), and after a reboot today all extensions were disabled. I went to the gnome-shell extensions website, ticked to enable my extension and it toggled on. The extensions did not seem to work. I reloaded the page and they are off again. I clicked enabled, still nothing. Reload page and all are off. I check logs in journalctl and could see nothing relevant. Eventually a bit of searching suggests enabling via gnome-shell-tweaks, so I open that up and they're all unticked, and disabled (can't be ticked). I realised there's a global "enable extensions" tickbox which has been unticked. Enabling this fixes everything. I have had to do this in the past, several months back as I had forgotten until now. Something is disabling this on upgrade and it is not obvious from the extensions web-page that they have been disabled. Ideally they should not be disabled at all, but if they are at least there should be some more obvious feedback after upgrade and on the extensions website ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 10:24:59 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-22 (640 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-15 (342 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925766 Title: extensions disabled after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1925766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925731] [NEW] distrib upgrade from 20.10 to 21.04 crashes while do-release-upgrade -d
Public bug reported: crash during dist upgrade from 20.10 to 21.04 command running withh root privilege ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.15 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Fri Apr 23 07:30:39 2021 InstallationDate: Installed on 2020-10-28 (176 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to groovy on 2021-04-23 (0 days ago) VarLogDistupgradeAptlog: Log time: 2021-04-23 07:30:21.622543 Log time: 2021-04-23 07:30:24.470036 Log time: 2021-04-23 07:30:39.695409 Log time: 2021-04-23 07:30:41.437953 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925731 Title: distrib upgrade from 20.10 to 21.04 crashes while do-release-upgrade -d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1925731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922999] [NEW] package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit st
Public bug reported: i dont know ProblemType: Package DistroRelease: Ubuntu 20.10 Package: grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 8 12:46:53 2021 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 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.10 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (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/1922999 Title: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1922999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904213] Re: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
I have the same issue with that laptop using Fedora 33: https://bugzilla.redhat.com/show_bug.cgi?id=1934754 Found temporary solution here: https://github.com/thesofproject/linux/issues/2795 ** Bug watch added: github.com/thesofproject/linux/issues #2795 https://github.com/thesofproject/linux/issues/2795 ** Also affects: sound-2.6 via https://github.com/thesofproject/linux/issues/2795 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1934754 https://bugzilla.redhat.com/show_bug.cgi?id=1934754 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1904213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Hi Robie, Thank's a lot – everything updated fine now! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
(I'm running Ubuntu 20.04.2 LTS) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Now that the new version was released to the "updates" channel I tried a regular Update using the default Ubuntu update-manager GUI. I don't have tinyjsd or jsunit installed so I expected everything to go smoothly. Instead the update-manager proposes a partial system update to install the thunderbird version and REMOVE the enigmail package (see screenshot). I suspect, this would not migrate my enigmail keys. If I understood it right there should be a new version for the enigmail package as well, which handles the migration of the encryption keys to the new internal PGP implementation. Is the update for the enigmail package still stuck somewhere? @racb posted earlier that the two packages should be updated together: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/comments/33 ** Attachment added: "update-manager proposes to remove Enigmail" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+attachment/5466601/+files/update-manager.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916722] [NEW] Pulseaudio fails to start after reboot if home partition is encrypted
Public bug reported: It seems that with Ubuntu 20.10, Pulseaudio now tries to start as main user too early, before user logs in and the home partition is decrypted. Probably pulseaudio should not start as main user before login of this user. Starting pulseaudio manually after login works. grep 'pulseaudio' /var/log/syslog Feb 24 10:52:31 aziber systemd[1451]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. Feb 24 10:52:31 aziber dbus-daemon[972]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=123 pid=1497 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Feb 24 10:52:38 aziber systemd[3631]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. Feb 24 10:52:38 aziber pulseaudio[3690]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 1. Feb 24 10:52:38 aziber pulseaudio[3899]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 2. Feb 24 10:52:39 aziber pulseaudio[4128]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 3. Feb 24 10:52:39 aziber pulseaudio[4311]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 4. Feb 24 10:52:39 aziber pulseaudio[4493]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Start request repeated too quickly. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.socket: Failed with result 'service-start-limit-hit'. Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: Connection failure: Connection refused Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: pa_context_connect() failed: Connection refused Feb 24 10:52:42 aziber gnome-session[5663]: gnome-session-binary[5663]: WARNING: App 'pulseaudio.desktop' exited with code 1 Feb 24 10:52:42 aziber gnome-session-binary[5663]: WARNING: App 'pulseaudio.desktop' exited with code 1 Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed to add PIDs to scope's control group: No such process Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed with result 'resources'. Feb 24 10:52:45 aziber systemd[1432]: pulseaudio.service: Succeeded. Feb 24 10:52:55 aziber systemd[1432]: pulseaudio.socket: Succeeded. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 24 10:57:51 2021 InstallationDate: Installed on 2019-11-29 (452 days ago) InstallationMedia: Ubuntu 19.04 "Dis
[Bug 1916464] [NEW] Regression: auto-update notification and GUI doesn't allow installing updates without restart
Public bug reported: Linux is great and famous for being able to install most updates without Restart. However, recently Ubuntu started showing only "Update & Restart" button in GUI, even when no kernel packages are offered to be updated. There should be only "Update" button without restarting when no kernel updates are pending. Why do people now get Windows-like experience of always restarting? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 22 11:56:42 2021 InstallationDate: Installed on 2019-11-29 (450 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: Upgraded to groovy on 2020-10-25 (119 days ago) ** Affects: gnome-software (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/1916464 Title: Regression: auto-update notification and GUI doesn't allow installing updates without restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1916464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916460] [NEW] Regression: upgrading of 3rd-party deb packages no longer works in GUI
Public bug reported: If you download an unofficial deb package and open it with gnome- software from the browser, it will let you to install it. However, if you already have an older version of the same package installed, it will offer to Remove only. Previously, it would offer to upgrade. This makes upgrading of 3rd-party software cumbersome. Tested with packages from here: https://angryip.org/download/#linux ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 22 11:28:14 2021 InstallationDate: Installed on 2019-11-29 (450 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: Upgraded to groovy on 2020-10-25 (119 days ago) ** Affects: gnome-software (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/1916460 Title: Regression: upgrading of 3rd-party deb packages no longer works in GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1916460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893753] Re: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17
Thomas, I believe lua-resty-core is required by lua-nginx-module 0.10.16 or later. The patches I proposed for hirsuite and focal in my previous comment upgrade the module to 0.10.15 which is the latest version that does *not* require lua-resty-core, but is fresh enough to work with the packaged version of NGINX (unlike the currently shipped 0.10.11). While we wait for a longer term plan with respect to lua-resty-core, is there any reason not to upgrade to 0.10.15 to fix what seems completely broken now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893753 Title: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1893753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913634] Re: Touchpad not working with 20.04 on ThinkBook 13s IML
** Attachment added: "devices.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1913634/+attachment/5457861/+files/devices.log ** Description changed: After installing current 20.04 on ThinkBook 13s IML I have found that its touchpad is not recognized on boot and not working at all. + + $ dmesg |grep i2c + [0.817823] i2c /dev entries driver + [1.038337] i2c i2c-0: 1/1 memory slots populated (from DMI) + [1.044114] i2c_hid i2c-CUST0001:00: supply vdd not found, using dummy regulator + [1.044161] i2c_hid i2c-CUST0001:00: supply vddl not found, using dummy regulator + [1.199246] i2c_hid i2c-CUST0001:00: failed to retrieve report from device. + [1.199281] input: CUST0001:00 06CB:CD98 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input5 + [1.199393] input: CUST0001:00 06CB:CD98 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input6 + [1.199449] hid-generic 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [CUST0001:00 06CB:CD98] on i2c-CUST0001:00 + [ 12.714228] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost arbitration + [ 13.742776] i2c_designware i2c_designware.0: controller timed out + [ 13.742785] i2c_hid i2c-CUST0001:00: failed to retrieve report from device. + [ 13.742844] input: CUST0001:00 06CB:CD98 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input10 + [ 13.742950] input: CUST0001:00 06CB:CD98 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input11 + [ 13.743015] hid-multitouch 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [CUST0001:00 06CB:CD98] on i2c-CUST0001:00 + [ 14.766780] i2c_designware i2c_designware.0: controller timed out + [ 14.766793] i2c_hid i2c-CUST0001:00: failed to set a report to device. + [ 15.791022] i2c_designware i2c_designware.0: controller timed out + [ 15.791060] i2c_hid i2c-CUST0001:00: failed to set a report to device. + [ 16.815119] i2c_designware i2c_designware.0: controller timed out + [ 17.838959] i2c_designware i2c_designware.0: controller timed out + [ 17.838978] i2c_hid i2c-CUST0001:00: failed to set a report to device. + [ 18.863103] i2c_designware i2c_designware.0: controller timed out + [ 19.887102] i2c_designware i2c_designware.0: controller timed out + [ 20.98] i2c_designware i2c_designware.0: controller timed out + [ 21.938779] i2c_designware i2c_designware.0: controller timed out + [ 22.958772] i2c_designware i2c_designware.0: controller timed out + [ 23.982770] i2c_designware i2c_designware.0: controller timed out + [ 25.006802] i2c_designware i2c_designware.0: controller timed out + [ 26.03] i2c_designware i2c_designware.0: controller timed out + [ 27.055015] i2c_designware i2c_designware.0: controller timed out + [ 28.078885] i2c_designware i2c_designware.0: controller timed out + [ 29.103159] i2c_designware i2c_designware.0: controller timed out + [ 30.127106] i2c_designware i2c_designware.0: controller timed out + [ 31.151129] i2c_designware i2c_designware.0: controller timed out + [ 32.175108] i2c_designware i2c_designware.0: controller timed out + [ 32.175146] i2c_hid i2c-CUST0001:00: failed to set a report to device. + [ 33.199020] i2c_designware i2c_designware.0: controller timed out + [ 34.222805] i2c_designware i2c_designware.0: controller timed out + [ 35.246821] i2c_designware i2c_designware.0: controller timed out + [ 36.274763] i2c_designware i2c_designware.0: controller timed out + [ 37.294764] i2c_designware i2c_designware.0: controller timed out + [ 38.318808] i2c_designware i2c_designware.0: controller timed out + [ 39.342999] i2c_designware i2c_designware.0: controller timed out + [ 40.366798] i2c_designware i2c_designware.0: controller timed out + [ 41.391007] i2c_designware i2c_designware.0: controller timed out + [ 42.415123] i2c_designware i2c_designware.0: controller timed out + [ 43.437697] i2c_designware i2c_designware.0: controller timed out + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 28 22:35:50 2021 InstallationDate: Installed on 2020-10-29 (91 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913634 Title:
[Bug 1913634] [NEW] Touchpad not working with 20.04 on ThinkBook 13s IML
Public bug reported: After installing current 20.04 on ThinkBook 13s IML I have found that its touchpad is not recognized on boot and not working at all. $ dmesg |grep i2c [0.817823] i2c /dev entries driver [1.038337] i2c i2c-0: 1/1 memory slots populated (from DMI) [1.044114] i2c_hid i2c-CUST0001:00: supply vdd not found, using dummy regulator [1.044161] i2c_hid i2c-CUST0001:00: supply vddl not found, using dummy regulator [1.199246] i2c_hid i2c-CUST0001:00: failed to retrieve report from device. [1.199281] input: CUST0001:00 06CB:CD98 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input5 [1.199393] input: CUST0001:00 06CB:CD98 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input6 [1.199449] hid-generic 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [CUST0001:00 06CB:CD98] on i2c-CUST0001:00 [ 12.714228] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost arbitration [ 13.742776] i2c_designware i2c_designware.0: controller timed out [ 13.742785] i2c_hid i2c-CUST0001:00: failed to retrieve report from device. [ 13.742844] input: CUST0001:00 06CB:CD98 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input10 [ 13.742950] input: CUST0001:00 06CB:CD98 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0001:00/0018:06CB:CD98.0001/input/input11 [ 13.743015] hid-multitouch 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [CUST0001:00 06CB:CD98] on i2c-CUST0001:00 [ 14.766780] i2c_designware i2c_designware.0: controller timed out [ 14.766793] i2c_hid i2c-CUST0001:00: failed to set a report to device. [ 15.791022] i2c_designware i2c_designware.0: controller timed out [ 15.791060] i2c_hid i2c-CUST0001:00: failed to set a report to device. [ 16.815119] i2c_designware i2c_designware.0: controller timed out [ 17.838959] i2c_designware i2c_designware.0: controller timed out [ 17.838978] i2c_hid i2c-CUST0001:00: failed to set a report to device. [ 18.863103] i2c_designware i2c_designware.0: controller timed out [ 19.887102] i2c_designware i2c_designware.0: controller timed out [ 20.98] i2c_designware i2c_designware.0: controller timed out [ 21.938779] i2c_designware i2c_designware.0: controller timed out [ 22.958772] i2c_designware i2c_designware.0: controller timed out [ 23.982770] i2c_designware i2c_designware.0: controller timed out [ 25.006802] i2c_designware i2c_designware.0: controller timed out [ 26.03] i2c_designware i2c_designware.0: controller timed out [ 27.055015] i2c_designware i2c_designware.0: controller timed out [ 28.078885] i2c_designware i2c_designware.0: controller timed out [ 29.103159] i2c_designware i2c_designware.0: controller timed out [ 30.127106] i2c_designware i2c_designware.0: controller timed out [ 31.151129] i2c_designware i2c_designware.0: controller timed out [ 32.175108] i2c_designware i2c_designware.0: controller timed out [ 32.175146] i2c_hid i2c-CUST0001:00: failed to set a report to device. [ 33.199020] i2c_designware i2c_designware.0: controller timed out [ 34.222805] i2c_designware i2c_designware.0: controller timed out [ 35.246821] i2c_designware i2c_designware.0: controller timed out [ 36.274763] i2c_designware i2c_designware.0: controller timed out [ 37.294764] i2c_designware i2c_designware.0: controller timed out [ 38.318808] i2c_designware i2c_designware.0: controller timed out [ 39.342999] i2c_designware i2c_designware.0: controller timed out [ 40.366798] i2c_designware i2c_designware.0: controller timed out [ 41.391007] i2c_designware i2c_designware.0: controller timed out [ 42.415123] i2c_designware i2c_designware.0: controller timed out [ 43.437697] i2c_designware i2c_designware.0: controller timed out ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 28 22:35:50 2021 InstallationDate: Installed on 2020-10-29 (91 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913634 Title: Touchpad not working with 20.04 on ThinkBook 13s IML To manage notifications about this bug go to:
Re: [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
The workaround is to unload the thermal kernel module that overreacts to short-lived temperature changes due to CPU load while charging. sudo rmmod int3403_thermal On Wed, Dec 2, 2020, 01:21 Magdalena S <1873...@bugs.launchpad.net> wrote: > I also have the same issue with the Lenovo Yoga C940 regarding the > regular thermal shutdowns on Manjaro 20.2. They occur mainly during > charging and in particular during video conferences (Zoom, etc.), which > is really annoying. I have also tried different linux kernels (5.4 - > 5.10) but the shutdowns remained. This way, the lenovo yoga notebook is > simply not serviceable under Linux. > > If there is any solution for that I would be really thankful. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1873083 > > Title: > Lenovo Yoga C940 frequently does thermal shutdown > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Until the new images are available: Just update apt of the live system before installing and the installation should work. For those who don't know how to: Start Live-System/ISO-Image with internet connected Choose "Try Ubuntu" Open "Terminal" Type: sudo apt-get update sudo apt-get install apt Then start installation of Ubuntu with your favourite options - even with third party drivers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893753] Re: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17
** Merge proposal linked: https://code.launchpad.net/~knyar/ubuntu/+source/nginx/+git/nginx/+merge/393789 ** Merge proposal linked: https://code.launchpad.net/~knyar/ubuntu/+source/nginx/+git/nginx/+merge/393790 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893753 Title: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1893753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893753] Re: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17
Because of this issue libnginx-mod-http-lua is completely broken in several versions of Ubuntu. Upgrading lua-nginx-module to 0.10.15 fixes the issue, and I have suggested two patches that would make libnginx-mod-http-lua usable again: - hirsuite: https://code.launchpad.net/~knyar/ubuntu/+source/nginx/+git/nginx/+merge/393789 - focal: https://code.launchpad.net/~knyar/ubuntu/+source/nginx/+git/nginx/+merge/393790 Note that the latest version of lua-nginx-module is 0.10.19, however upgrading to it is more tricky than upgrading to 0.10.15. Beginning at version 0.10.16, lua-nginx-module requires the lua-resty-core library (https://github.com/openresty/lua-resty-core) to be available, and I have not been able to find it packaged in Ubuntu. There are several options on how to package that lua library (either as a separate Ubuntu package, or together with libnginx-mod-http-lua), which is probably something that Ubuntu nginx maintainers should decide. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893753 Title: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1893753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904216] Re: /usr/bin/direvent Segmentation fault (core dumped)
** Description changed: Ubuntu 20.04 (with all updates on 13.11.2020) ● direvent.service - monitors events in the file system directories - Loaded: loaded (/lib/systemd/system/direvent.service; enabled; vendor preset: enabled) - Active: failed (Result: core-dump) since Fri 2020-11-13 15:57:19 CET; 2s ago -Docs: man:direvent(1p) - Process: 741652 ExecStart=/usr/bin/direvent --foreground (code=dumped, signal=SEGV) -Main PID: 741652 (code=dumped, signal=SEGV) + Loaded: loaded (/lib/systemd/system/direvent.service; enabled; vendor preset: enabled) + Active: failed (Result: core-dump) since Fri 2020-11-13 15:57:19 CET; 2s ago + Docs: man:direvent(1p) + Process: 741652 ExecStart=/usr/bin/direvent --foreground (code=dumped, signal=SEGV) + Main PID: 741652 (code=dumped, signal=SEGV) direvent.service: Main process exited, code=dumped, status=11/SEGV direvent.service: Failed with result 'core-dump'. - - - == ApportVersion = - 2.20.11-0ubuntu27.11 - - == Architecture = - amd64 - - == CasperMD5CheckResult = - pass - - == Date = - Fri Nov 13 16:00:26 2020 - - == Dependencies = - dpkg 1.19.7ubuntu3 - gcc-10-base 10.2.0-5ubuntu1~20.04 - init-system-helpers 1.57 - libacl1 2.2.53-6 - libbz2-1.0 1.0.8-2 - libc6 2.31-0ubuntu9.1 - libcrypt1 1:4.4.10-10ubuntu4 - libgcc-s1 10.2.0-5ubuntu1~20.04 - libidn2-0 2.2.0-2 - liblzma5 5.2.4-1ubuntu1 - libpcre2-8-0 10.34-7 - libselinux1 3.0-1build2 - libunistring2 0.9.10-2 - libzstd1 1.4.4+dfsg-3 - perl-base 5.30.0-9ubuntu0.2 - tar 1.30+dfsg-7 - zlib1g 1:1.2.11.dfsg-2ubuntu1.2 - - == DistroRelease = - Ubuntu 20.04 - - == InstallationDate = - Installed on 2020-06-02 (163 days ago) - - == InstallationMedia = - Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) - - == Package = - direvent 5.2-1 - - == PackageArchitecture = - amd64 - - == ProblemType = - Bug - - == ProcCpuinfoMinimal = - processor : 3 - vendor_id : AuthenticAMD - cpu family : 23 - model : 49 - model name : AMD EPYC 7402P 24-Core Processor - stepping: 0 - microcode : 0x8301038 - cpu MHz : 2794.750 - cache size : 512 KB - physical id : 6 - siblings: 1 - core id : 0 - cpu cores : 1 - apicid : 6 - initial apicid : 6 - fpu : yes - fpu_exception : yes - cpuid level : 16 - wp : yes - flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl tsc_reliable nonstop_tsc cpuid extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ssbd ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xsaves clzero arat overflow_recov succor - bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass - bogomips: 5589.50 - TLB size: 3072 4K pages - clflush size: 64 - cache_alignment : 64 - address sizes : 43 bits physical, 48 bits virtual - power management: - - == ProcEnviron = - TERM=linux - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash - - == ProcVersionSignature = - Ubuntu 5.4.0-52.57-generic 5.4.65 - - == SourcePackage = - direvent - - == Tags = - focal uec-images - - == Uname = - Linux 5.4.0-52-generic x86_64 - - == UpgradeStatus = - No upgrade log present (probably fresh install) - - ProblemType: Bug - DistroRelease: Ubuntu 20.04 - Package: direvent 5.2-1 - ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 - Uname: Linux 5.4.0-52-generic x86_64 - ApportVersion: 2.20.11-0ubuntu27.11 - Architecture: amd64 - CasperMD5CheckResult: pass - Date: Fri Nov 13 16:00:26 2020 - InstallationDate: Installed on 2020-06-02 (163 days ago) - InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) - ProcEnviron: - TERM=linux - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: direvent - UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904216 Title: /usr/bin/direvent Segmentation fault
[Bug 1904216] [NEW] /usr/bin/direvent Segmentation fault (core dumped)
Public bug reported: Ubuntu 20.04 (with all updates on 13.11.2020) ● direvent.service - monitors events in the file system directories Loaded: loaded (/lib/systemd/system/direvent.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Fri 2020-11-13 15:57:19 CET; 2s ago Docs: man:direvent(1p) Process: 741652 ExecStart=/usr/bin/direvent --foreground (code=dumped, signal=SEGV) Main PID: 741652 (code=dumped, signal=SEGV) direvent.service: Main process exited, code=dumped, status=11/SEGV direvent.service: Failed with result 'core-dump'. == ApportVersion = 2.20.11-0ubuntu27.11 == Architecture = amd64 == CasperMD5CheckResult = pass == Date = Fri Nov 13 16:00:26 2020 == Dependencies = dpkg 1.19.7ubuntu3 gcc-10-base 10.2.0-5ubuntu1~20.04 init-system-helpers 1.57 libacl1 2.2.53-6 libbz2-1.0 1.0.8-2 libc6 2.31-0ubuntu9.1 libcrypt1 1:4.4.10-10ubuntu4 libgcc-s1 10.2.0-5ubuntu1~20.04 libidn2-0 2.2.0-2 liblzma5 5.2.4-1ubuntu1 libpcre2-8-0 10.34-7 libselinux1 3.0-1build2 libunistring2 0.9.10-2 libzstd1 1.4.4+dfsg-3 perl-base 5.30.0-9ubuntu0.2 tar 1.30+dfsg-7 zlib1g 1:1.2.11.dfsg-2ubuntu1.2 == DistroRelease = Ubuntu 20.04 == InstallationDate = Installed on 2020-06-02 (163 days ago) == InstallationMedia = Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) == Package = direvent 5.2-1 == PackageArchitecture = amd64 == ProblemType = Bug == ProcCpuinfoMinimal = processor : 3 vendor_id : AuthenticAMD cpu family : 23 model : 49 model name : AMD EPYC 7402P 24-Core Processor stepping: 0 microcode : 0x8301038 cpu MHz : 2794.750 cache size : 512 KB physical id : 6 siblings: 1 core id : 0 cpu cores : 1 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 16 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl tsc_reliable nonstop_tsc cpuid extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ssbd ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xsaves clzero arat overflow_recov succor bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass bogomips: 5589.50 TLB size: 3072 4K pages clflush size: 64 cache_alignment : 64 address sizes : 43 bits physical, 48 bits virtual power management: == ProcEnviron = TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash == ProcVersionSignature = Ubuntu 5.4.0-52.57-generic 5.4.65 == SourcePackage = direvent == Tags = focal uec-images == Uname = Linux 5.4.0-52-generic x86_64 == UpgradeStatus = No upgrade log present (probably fresh install) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: direvent 5.2-1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Nov 13 16:00:26 2020 InstallationDate: Installed on 2020-06-02 (163 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: direvent UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: direvent (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug direvent focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904216 Title: /usr/bin/direvent Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/direvent/+bug/1904216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864871] Re: Failed to init Intel sound card in 20.04
Update on the initial report: currently with 5.4.0-53 sound card is initialized without any workarounds. But only output dynamics works, reported microphone issue here: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1904213 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864871 Title: Failed to init Intel sound card in 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904213] [NEW] Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
Public bug reported: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1904213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
ubuntu 20.04, kernel Linux 5.4.0-52-generic samsung galaxy buds, cant switch to hsp/hfp thinkpad x1 carbon. laptop has intel BT 8087:0a2b, /lib/firmware/intel/ibt-12-16.sfi is used. tried to get "new" from here https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/intel but it has same fw file as i have on my system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885191] Re: [Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
Another workaround is to use the legacy server install image for 20.04: http://cdimage.ubuntu.com/ubuntu-legacy-server/releases/20.04.1/release/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885191 Title: [Focal] Installation Fails with "Invalid dep_id" when using Intel VROC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1885191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894860] Re: Boot fails with newer kernel
Kernel update to 5.4.0-48 fixed issue for me. What about you, Eugen? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894860 Title: Boot fails with newer kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 I have the same issue. My Bose 700 connect and have sound output for A2DP, but nothing when trying to select HSP/HFP. Laptop: HP Spectre X360 2019 OS: Ubuntu 20.04.01 LTS Kernel: 5.4.0-47-generic Headset: Bose 700 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883174] Re: Some desktop icons disappear
I can confirm the problem. Upgrade was from 18.04 to 20.04 and 4th monitor added to new grophic card. Icons disappearing is happening daily. Not all icons disappear. Suspend and wake up retruns icons to its original place. Usually it happens when I save a Libre Writer document and close the Writer. Let me know if I can help further and how. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892627] [NEW] When I launch the Ubuntu installation the error message /dev/sda failed to execute pops up and the installation is only a command line.
Public bug reported: how do i finish the installation with the command line? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 15:05:35 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892627 Title: When I launch the Ubuntu installation the error message /dev/sda failed to execute pops up and the installation is only a command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1892627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841039] Re: Multiple keys have same keycode on HP ProBook 450 G6
I also have same problem on my HP ProBook 450 G6. Using sudo showkey -k gave me these results: - pressing Fn+F3: keycode 190 press keycode 190 release - pressing Fn+F4: keycode 190 press keycode 190 release - pressing Fn+F8: keycode 190 press keycode 190 release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841039 Title: Multiple keys have same keycode on HP ProBook 450 G6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1841039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947664] Re: Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1)
I've also encountered problem recently. I'm installing headers 4.15.0-112.113. Progress is stuck on unpacking stage at 4%. I've tried clearing cache but this didn't seem to help. dpkg is disk sleep in htop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947664 Title: Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1) To manage notifications about this bug go to: https://bugs.launchpad.net/dpkg/+bug/947664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885265] Re: NFSd4 crashes system in unhash_delegation_locked
This exact kernel panic happened to us again on newer linux version 5.4.0-39-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885265 Title: NFSd4 crashes system in unhash_delegation_locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1885265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888857] Re: deadlock in pthread_cond_signal under high contention
With the packages you gave me I was not able to reproduce the problem. Thank you very much! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/157 Title: deadlock in pthread_cond_signal under high contention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888857] Re: deadlock in pthread_cond_signal under high contention
Thank you for the prompt reply! I've installed the packages and left the test application running for the weekend. I'll write you back on Monday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/157 Title: deadlock in pthread_cond_signal under high contention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888857] [NEW] deadlock in pthread_cond_signal under high contention
Public bug reported: Hello! I'm working on a large C++-based cross-platform project. I noticed that on arm64-based systems some of my processes sporadically became paralyzed by the deadlock hitting all the threads posting to the single boost::asio::io_service. I investigated the deadlock condition further and reduced the problem to the simple test application available at https://github.com/bezkrovatki/deadlock_in_pthread_cond_signal There you may find there the test source code, the detailed description, the deadlock call stacks for all threads and theirs compact view as a call graph. In a short, in the test I have threads of two types: (1) producers - Np threads calling pthread_cond_signal after unlocking a mutex at a rate of Rp calls per second; (2) consumers - Nc threads calling pthread_cond_wait at a rate of Rc calls per second. Np, Rp and Rc can be specified with command line parameters, Nc is equal to the number of CPU cores of the particular system running the test. Once started on arm64-based multi-core device the test eventually gets all its threads blocked if the Np, Rp and Rc are enough to keep contention high around pthread_cond_singal calls. The deadlock can be workarounded by * reducing probability of concurring pthread_cond_singal calls by tuning Np, Rp and Rc; * moving pthread_cond_singal call under the lock Moreover, the deadlock can be broken by ptrace: attaching with debugger, generating dump with Google Breakpad and etc. makes the process revive. One time I was able to wake up the process from the deadlock with SIGSTOP/SIGCONT, however, the healing effect was very limited and the process returned into the deadlock state in a few seconds. I would like to note that a problem with symptoms that look similar was reported and fixed in kernel several years ago (see https://groups.google.com/forum/#!topic/mechanical-sympathy/QbmpZxp6C64 and https://github.com/torvalds/linux/commit/76835b0ebf8a7fe85beb03c75121419a7dec52f0). However, I believe this time the problem is on the NPTL implementation side because: * 100% of the observed deadlocks both in our product and the tests appear to have the same structure: single producer blocked in __condvar_quiesce_and_switch_g1, all other producers blocked in __condvar_acquire_lock, all consumers blocked in __pthread_cond_wait_common; * mutex misbehavior was never observed either in test or in my project; * wakeups by ptrace/signal simply mean waiting on a futex got interrupted and on the next iteration (if any) at least one of these call paths made progress after observing changed global state, which can be a side effect of the race in the userland as well as in the kernel; * while the mutex object is more contended than pthread_cond_signal related internal data of the condvar if I put the pthread_cond_signal call under the lock, I cannot reproduce the problem. I looked at the nptl source code (https://elixir.bootlin.com/glibc/glibc-2.27/source/nptl/pthread_cond_common.c#L280) a bit. I'm not burdened with a deep knowledge of the implemented algorithm and its dark corners. For me the observed deadlock looks quite probable from the source code. 1) All producers (signalling threads) except one are blocked in __condvar_acquire_lock@pthread_cond_common.c:280, they are waiting for the single signalling thread which was lucky to succeed in acquiring the internal data lock. 2) According to the comments lavishly sown around the code, that "lucky" signalling thread waits for the some of consumers (waiting threads) to leave G1 group to be able to close the group and make the group switch in __condvar_quiesce_and_switch_g1@pthread_cond_common.c:412 3) And all consumers (waiting threads) wait, of course, they wait for the producers to send a signal, see __pthread_cond_wait_common@pthread_cond_wait.c:502 4) And if you watch the code around __pthread_cond_wait_common@pthread_cond_wait.c:502 carefully you can see that when the waiting for signals on the futex gets interrupted, the code wakes our "lucky" thread blocked in __condvar_quiesce_and_switch_g1@pthread_cond_common.c:412 at first (by calling __condvar_dec_grefs@pthread_cond_wait.c:149 ) and only then re-evaluates the condition and returns to the waiting on the futex if necessary. This fact can explain how ptrace/signal allows to break the deadlock. -- I posted the bug report here because the glibc's wiki strongly recommends to start from the distribution bug tracker. All arm64-based devices I tested were running Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libc6 2.27-3ubuntu1 Uname: Linux 4.9.187-52 aarch64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: arm64 Date: Fri Jul 24 14:05:57 2020 Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: glibc
[Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
@Bob Lawrence (pilotbob42) So i'm back with a better workaround. First I enabled the intel driver like I specified in my first point.(this removes the tearing) Then I used your workaround, but this was causing the other inputs to error at startup so I on some forum that adding a command at startup applications is a better solution. So i added:"xrandr --output HDMI-3 --mode 1920x1080 --scale 0.x0." as a new command in Startup Applications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
@Bob Lawrence (pilotbob42) I don't have .xprofile but i created it my home folder like you suggested and added the text, mine was HDMI3. Unfortunately it doesn't seem to do anything. I also observed that changing the DPI solves the issue on most distros I tried. But i don't like any other DPI than 100%. Also in regard to the workaround posted by me changing to DRI 2, mostly solves the issue on gnome on POP OS, still a few mouse trails but it is bearable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885265] Re: NFSd4 crashes system in unhash_delegation_locked
** Description changed: After running quite busy NFS4 server with ZFS as backend filesystem for some time we get system crash with weekly regularity. Clients are mounted with delegation propagation enabled and client mount options are as follows: type nfs4 (rw,nosuid,nodev,noexec,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,acregmin=600,acregmax=600,acdirmin=600,acdirmax=600,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=y.y.y.y,local_lock=none,addr=x.x.x.x) Server side configuration is PIPEFS_MOUNTPOINT=/run/rpc_pipefs RPCNFSDARGS="--grace-time 10 32" RPCMOUNTDARGS="--manage-gids --num-threads=8" STATDARGS="" RPCSVCGSSDARGS="" SVCGSSDARGS="" - - The error happens in executing unhash_delegation_locked function called from laundromat_main. Error on the console before reboot is below: + The error happens in executing unhash_delegation_locked function called + from laundromat_main. Error on the console before reboot is below: [2768169.862683] BUG: unable to handle page fault for address: c09451a9 [2768169.863924] #PF: supervisor write access in kernel mode [2768169.864790] #PF: error_code(0x0003) - permissions violation [2768169.865695] PGD 3fe20e067 P4D 3fe20e067 PUD 3fe210067 PMD bf9c25067 PTE bf9f81161 [2768169.866895] Oops: 0003 [#1] SMP NOPTI [2768169.867493] CPU: 8 PID: 4105769 Comm: kworker/u24:1 Tainted: PW OE 5.3.0-46-generic #38~18.04.1-Ubuntu [2768169.869154] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.12.0-1 04/01/2014 [2768169.870447] Workqueue: nfsd4 laundromat_main [nfsd] [2768169.871235] RIP: 0010:_raw_spin_lock+0x10/0x30 [2768169.871959] Code: 01 00 00 75 06 48 89 d8 5b 5d c3 e8 0a 13 66 ff 48 89 d8 5b 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 31 c0 ba 01 00 00 00 0f b1 17 75 02 5d c3 89 c6 e8 c1 fa 65 ff 66 90 5d c3 0f 1f 00 [2768169.874528] RSP: 0018:be5ed12f7de0 EFLAGS: 00010246 [2768169.875177] RAX: RBX: be5ed12f7de8 RCX: [2768169.876084] RDX: 0001 RSI: 9508089084e0 RDI: c09451a9 [2768169.876993] RBP: be5ed12f7de0 R08: 077e R09: 0004 [2768169.877942] R10: R11: 0001 R12: c09451a9 [2768169.878793] R13: be5ed12f7e20 R14: be5ed12f7e40 R15: 9508089084e0 [2768169.879627] FS: () GS:950d8fa0() knlGS: [2768169.880624] CS: 0010 DS: ES: CR0: 80050033 [2768169.881359] CR2: c09451a9 CR3: 000bd237c000 CR4: 00340ee0 [2768169.882241] Call Trace: [2768169.882571] unhash_delegation_locked+0x39/0xa0 [nfsd] [2768169.883201] laundromat_main+0x235/0x5a0 [nfsd] [2768169.883756] process_one_work+0x1fd/0x3f0 [2768169.884272] worker_thread+0x34/0x410 [2768169.884725] kthread+0x121/0x140 [2768169.885165] ? process_one_work+0x3f0/0x3f0 [2768169.885730] ? kthread_park+0xb0/0xb0 [2768169.886302] ret_from_fork+0x22/0x40 [2768169.886837] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs cpuid rpcsec_gss_krb5 rbd libceph ipt_REJECT nf_reject_ipv4 xt_set ip_set_hash_ipport xt_ipvs ip_set_hash_ip ip_set_hash_net ip_set dummy xt_tcpudp iptable_raw xt_CT veth xt_MASQUERADE xt_comment xt_mark iptable_nat iptable_filter bpfilter xt_conntrack nf_nat nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo aufs overlay zfs(POE) zunicode(PO) zavl(PO) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) nls_iso8859_1 kvm_amd ccp kvm joydev input_leds irqbypass mac_hid serio_raw qemu_fw_cfg sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi br_netfilter bridge stp llc ip_vs_sh nfsd ip_vs_wrr ip_vs_rr auth_rpcgss ip_vs nfs_acl lockd nf_conntrack grace nf_defrag_ipv6 nf_defrag_ipv4 sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear [2768169.886885] hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cirrus drm_kms_helper aesni_intel syscopyarea aes_x86_64 crypto_simd sysfillrect sysimgblt cryptd fb_sys_fops glue_helper psmouse virtio_scsi virtio_net drm net_failover i2c_piix4 failover pata_acpi floppy [2768169.902274] CR2: c09451a9 [2768169.902777] ---[ end trace dcbbef50958ba3f7 ]--- [2768169.903440] RIP: 0010:_raw_spin_lock+0x10/0x30 [2768169.904064] Code: 01 00 00 75 06 48 89 d8 5b 5d c3 e8 0a 13 66 ff 48 89 d8 5b 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 31 c0 ba 01 00 00 00 0f b1 17 75 02 5d c3 89 c6 e8 c1 fa 65 ff 66 90 5d c3 0f 1f 00 [2768169.907606] RSP: 0018:be5ed12f7de0 EFLAGS: 00010246 [2768169.908641] RAX: RBX: be5ed12f7de8 RCX: [2768169.910010] RDX: 0001 RSI: 9508089084e0 RDI: c09451a9
[Bug 1885265] [NEW] NFSd4 crashes system in unhash_delegation_locked
Public bug reported: After running quite busy NFS4 server with ZFS as backend filesystem for some time we get system crash with weekly regularity. Clients are mounted with delegation propagation enabled and client mount options are as follows: type nfs4 (rw,nosuid,nodev,noexec,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,acregmin=600,acregmax=600,acdirmin=600,acdirmax=600,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=y.y.y.y,local_lock=none,addr=x.x.x.x) Server side configuration is PIPEFS_MOUNTPOINT=/run/rpc_pipefs RPCNFSDARGS="--grace-time 10 32" RPCMOUNTDARGS="--manage-gids --num-threads=8" STATDARGS="" RPCSVCGSSDARGS="" SVCGSSDARGS="" The error happens in executing unhash_delegation_locked function called from laundromat_main. Error on the console before reboot is below: [2768169.862683] BUG: unable to handle page fault for address: c09451a9 [2768169.863924] #PF: supervisor write access in kernel mode [2768169.864790] #PF: error_code(0x0003) - permissions violation [2768169.865695] PGD 3fe20e067 P4D 3fe20e067 PUD 3fe210067 PMD bf9c25067 PTE bf9f81161 [2768169.866895] Oops: 0003 [#1] SMP NOPTI [2768169.867493] CPU: 8 PID: 4105769 Comm: kworker/u24:1 Tainted: PW OE 5.3.0-46-generic #38~18.04.1-Ubuntu [2768169.869154] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.12.0-1 04/01/2014 [2768169.870447] Workqueue: nfsd4 laundromat_main [nfsd] [2768169.871235] RIP: 0010:_raw_spin_lock+0x10/0x30 [2768169.871959] Code: 01 00 00 75 06 48 89 d8 5b 5d c3 e8 0a 13 66 ff 48 89 d8 5b 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 31 c0 ba 01 00 00 00 0f b1 17 75 02 5d c3 89 c6 e8 c1 fa 65 ff 66 90 5d c3 0f 1f 00 [2768169.874528] RSP: 0018:be5ed12f7de0 EFLAGS: 00010246 [2768169.875177] RAX: RBX: be5ed12f7de8 RCX: [2768169.876084] RDX: 0001 RSI: 9508089084e0 RDI: c09451a9 [2768169.876993] RBP: be5ed12f7de0 R08: 077e R09: 0004 [2768169.877942] R10: R11: 0001 R12: c09451a9 [2768169.878793] R13: be5ed12f7e20 R14: be5ed12f7e40 R15: 9508089084e0 [2768169.879627] FS: () GS:950d8fa0() knlGS: [2768169.880624] CS: 0010 DS: ES: CR0: 80050033 [2768169.881359] CR2: c09451a9 CR3: 000bd237c000 CR4: 00340ee0 [2768169.882241] Call Trace: [2768169.882571] unhash_delegation_locked+0x39/0xa0 [nfsd] [2768169.883201] laundromat_main+0x235/0x5a0 [nfsd] [2768169.883756] process_one_work+0x1fd/0x3f0 [2768169.884272] worker_thread+0x34/0x410 [2768169.884725] kthread+0x121/0x140 [2768169.885165] ? process_one_work+0x3f0/0x3f0 [2768169.885730] ? kthread_park+0xb0/0xb0 [2768169.886302] ret_from_fork+0x22/0x40 [2768169.886837] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs cpuid rpcsec_gss_krb5 rbd libceph ipt_REJECT nf_reject_ipv4 xt_set ip_set_hash_ipport xt_ipvs ip_set_hash_ip ip_set_hash_net ip_set dummy xt_tcpudp iptable_raw xt_CT veth xt_MASQUERADE xt_comment xt_mark iptable_nat iptable_filter bpfilter xt_conntrack nf_nat nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo aufs overlay zfs(POE) zunicode(PO) zavl(PO) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) nls_iso8859_1 kvm_amd ccp kvm joydev input_leds irqbypass mac_hid serio_raw qemu_fw_cfg sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi br_netfilter bridge stp llc ip_vs_sh nfsd ip_vs_wrr ip_vs_rr auth_rpcgss ip_vs nfs_acl lockd nf_conntrack grace nf_defrag_ipv6 nf_defrag_ipv4 sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear [2768169.886885] hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cirrus drm_kms_helper aesni_intel syscopyarea aes_x86_64 crypto_simd sysfillrect sysimgblt cryptd fb_sys_fops glue_helper psmouse virtio_scsi virtio_net drm net_failover i2c_piix4 failover pata_acpi floppy [2768169.902274] CR2: c09451a9 [2768169.902777] ---[ end trace dcbbef50958ba3f7 ]--- [2768169.903440] RIP: 0010:_raw_spin_lock+0x10/0x30 [2768169.904064] Code: 01 00 00 75 06 48 89 d8 5b 5d c3 e8 0a 13 66 ff 48 89 d8 5b 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 31 c0 ba 01 00 00 00 0f b1 17 75 02 5d c3 89 c6 e8 c1 fa 65 ff 66 90 5d c3 0f 1f 00 [2768169.907606] RSP: 0018:be5ed12f7de0 EFLAGS: 00010246 [2768169.908641] RAX: RBX: be5ed12f7de8 RCX: [2768169.910010] RDX: 0001 RSI: 9508089084e0 RDI: c09451a9 [2768169.911399] RBP: be5ed12f7de0 R08: 077e R09: 0004 [2768169.912648] R10: R11: 0001 R12: c09451a9 [2768169.913952] R13: be5ed12f7e20 R14: be5ed12f7e40 R15: 9508089084e0 [2768169.915217] FS:
[Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Hello folks. I experience this issue with my three monitor setup (two of which are vertical) using NVIDIA Drivers 440.82 on PopOS 20.04. Monitor layout works with xrandr/arandr and if I hand craft manitors.xml, configuration is preserved. I have posted my details here https://github.com/pop-os/pop/issues/933#issuecomment-643681670 But GUI doesn't work. Also after recovering from suspend layout explodes again. I would be glad to help with investigation, collecting logs, traces, etc (feel free to DM me). ** Bug watch added: github.com/pop-os/pop/issues #933 https://github.com/pop-os/pop/issues/933 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1874567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883243] Re: Hardware issues on lenovo ideapad 5
Just to add details, this laptop series is totally %%""$$$ , I tried in addition mint, manjaro , MX. MX doesn't boot, Fedora - dead touchpad, manjaro - every ~3 rd boot touchpad works + no sound issue (5.4x kernel helps with sound), mint 19.3 - no sound, every ~3rd boot touchpad works, mint 20.0 beta - same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883243 Title: Hardware issues on lenovo ideapad 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
I found a fix for the issues on kde, as I am running kubuntu 20.04, all credit goes to the original poster. My contribution was only to change the DRI setting to 3 not "false" because this caused slowdown. https://forum.manjaro.org/t/how-i-fixed-my-tearing-and-graphical-issues- completely-manjaro-kde/108390 ** Attachment added: "20-intel.conf" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+attachment/5380581/+files/20-intel.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880445] Re: Hercules Classic Link does not work in recent Ubuntu versions (but does in 14.04 and 16.04)
Situation update: web camera works with guvcview, but not with Cheese, Skype or browser -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880445 Title: Hercules Classic Link does not work in recent Ubuntu versions (but does in 14.04 and 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880445] Re: Hercules Classic Link does not work in recent Ubuntu versions (but does in 14.04 and 16.04)
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880445 Title: Hercules Classic Link does not work in recent Ubuntu versions (but does in 14.04 and 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880445] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1880445/+attachment/5376346/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880445 Title: Hercules Classic Link does not work in recent Ubuntu versions (but does in 14.04 and 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880445] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1880445/+attachment/5376347/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880445 Title: Hercules Classic Link does not work in recent Ubuntu versions (but does in 14.04 and 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
