[Bug 1929048] Re: Speed up resume time on HP laptops
This is upstream [commit 79d341e26ebc](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79d341e26ebcdbc622348b6f8f89b6fdb25f). Thank you for upstreaming it. It’d be great, if you also documented the measurements. Do you still have them, and can add them here as a comment? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929048 Title: Speed up resume time on HP laptops To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] Re: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices
My bad, actually looking on the device, *brltty* was installed for a long time. :-( /var/log/dpkg.log.12.gz:2020-06-24 18:24:40 upgrade brltty:amd64 5.6-11ubuntu2 6.0+dfsg-4ubuntu6 Sorry about the confusion. It looks like the user tested this exact USB serial converter (0403:6001) the first time. ``` Mai 30 12:14:14 Ixpees kernel: Linux version 5.15.0-33-generic (buildd@lcy02-amd64-037) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #34-Ubuntu SMP Wed May 18 13:34:26 UTC 2022 (Ubuntu 5.15.0-33.34-generic 5.15.30) […] Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: new full-speed USB device number 4 using xhci_hcd Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: Product: USB Serial Converter Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: Manufacturer: FTDI Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: SerialNumber: FTFCV4W7 Mai 30 12:16:13 Ixpees mtp-probe[3062]: checking bus 3, device 4: "/sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1" Mai 30 12:16:13 Ixpees mtp-probe[3062]: bus: 3, device: 4 was not an MTP device Mai 30 12:16:13 Ixpees snapd[1117]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data Mai 30 12:16:13 Ixpees snapd[1117]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data Mai 30 12:16:13 Ixpees systemd[1]: Starting Braille Device Support... Mai 30 12:16:13 Ixpees kernel: calling usb_serial_init+0x0/0x1000 [usbserial] @ 3008 Mai 30 12:16:13 Ixpees kernel: usbcore: registered new interface driver usbserial_generic Mai 30 12:16:13 Ixpees kernel: usbserial: USB Serial support registered for generic Mai 30 12:16:13 Ixpees kernel: initcall usb_serial_init+0x0/0x1000 [usbserial] returned 0 after 105 usecs Mai 30 12:16:13 Ixpees kernel: calling usb_serial_module_init+0x0/0x1000 [ftdi_sio] @ 3008 Mai 30 12:16:13 Ixpees kernel: usbcore: registered new interface driver ftdi_sio Mai 30 12:16:13 Ixpees kernel: usbserial: USB Serial support registered for FTDI USB Serial Device Mai 30 12:16:13 Ixpees kernel: ftdi_sio 3-1.1:1.0: FTDI USB Serial Device converter detected Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: Detected FT232RL Mai 30 12:16:13 Ixpees kernel: usb 3-1.1: FTDI USB Serial Device converter now attached to ttyUSB0 Mai 30 12:16:13 Ixpees kernel: initcall usb_serial_module_init+0x0/0x1000 [ftdi_sio] returned 0 after 2817 usecs Mai 30 12:16:13 Ixpees mtp-probe[3069]: checking bus 3, device 4: "/sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1" Mai 30 12:16:13 Ixpees mtp-probe[3069]: bus: 3, device: 4 was not an MTP device Mai 30 12:16:13 Ixpees snapd[1117]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data Mai 30 12:16:13 Ixpees brltty[3064]: BRLTTY 6.4 rev BRLTTY-6.4 [https://brltty.app/] Mai 30 12:16:13 Ixpees brltty[3064]: BRLTTY 6.4 rev BRLTTY-6.4 [https://brltty.app/] Mai 30 12:16:13 Ixpees brltty[3064]: executing as the invoking user: root Mai 30 12:16:13 Ixpees brltty[3064]: brltty: executing as the invoking user: root Mai 30 12:16:13 Ixpees brltty[3064]: brltty: directory created: /var/lib/brltty Mai 30 12:16:13 Ixpees brltty[3064]: directory created: /var/lib/brltty ``` In the past 0403:6015 was used for example: ``` Aug 26 10:33:08 Ixpees kernel: Linux version 5.8.0-050800-generic (kernel@gloin) (gcc (Ubuntu 9.3.0-13ubuntu1) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #202007052030 SMP Mon Jul 6 00:37:33 UTC 2020 […] Aug 26 10:37:24 Ixpees kernel: usb 1-1: new full-speed USB device number 13 using xhci_hcd Aug 26 10:37:24 Ixpees kernel: usb 1-1: New USB device found, idVendor=0403, idProduct=6015, bcdDevice=10.00 Aug 26 10:37:24 Ixpees kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 26 10:37:24 Ixpees kernel: usb 1-1: Product: FT230X Basic UART Aug 26 10:37:24 Ixpees kernel: usb 1-1: Manufacturer: FTDI Aug 26 10:37:24 Ixpees kernel: usb 1-1: SerialNumber: D307FNWS Aug 26 10:37:24 Ixpees mtp-probe[3194]: checking bus 1, device 13: "/sys/devices/pci:00/:00:14.0/usb1/1-1" Aug 26 10:37:24 Ixpees mtp-probe[3194]: bus: 1, device: 13 was not an MTP device Aug 26 10:37:24 Ixpees kernel: calling usb_serial_init+0x0/0x1000 [usbserial] @ 3193 Aug 26 10:37:24 Ixpees kernel: usbcore: registered new interface driver usbserial_generic Aug 26 10:37:24 Ixpees kernel: usbserial: USB Serial support registered for generic Aug 26 10:37:24 Ixpees kernel: initcall usb_serial_init+0x0/0x1000 [usbserial] returned 0 after 119 usecs Aug 26 10:37:24 Ixpees kernel: calling usb_serial_module_init+0x0/0x1000 [ftdi_sio] @ 3193 Aug 26 10:37:24 Ixpees kernel: usbcore:
[Bug 1976293] VarLogDistupgradeScreenlog.txt
apport information ** Attachment added: "VarLogDistupgradeScreenlog.txt" https://bugs.launchpad.net/bugs/1976293/+attachment/5594312/+files/VarLogDistupgradeScreenlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] VarLogDistupgradeApttermlog.txt
apport information ** Attachment added: "VarLogDistupgradeApttermlog.txt" https://bugs.launchpad.net/bugs/1976293/+attachment/5594309/+files/VarLogDistupgradeApttermlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] VarLogDistupgradeMainlog.txt
apport information ** Attachment added: "VarLogDistupgradeMainlog.txt" https://bugs.launchpad.net/bugs/1976293/+attachment/5594311/+files/VarLogDistupgradeMainlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] VarLogDistupgradeLspcitxt.txt
apport information ** Attachment added: "VarLogDistupgradeLspcitxt.txt" https://bugs.launchpad.net/bugs/1976293/+attachment/5594310/+files/VarLogDistupgradeLspcitxt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] VarLogDistupgradeAptclonesystemstate.tar.gz
apport information ** Attachment added: "VarLogDistupgradeAptclonesystemstate.tar.gz" https://bugs.launchpad.net/bugs/1976293/+attachment/5594307/+files/VarLogDistupgradeAptclonesystemstate.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] VarLogDistupgradeAptlog.txt
apport information ** Attachment added: "VarLogDistupgradeAptlog.txt" https://bugs.launchpad.net/bugs/1976293/+attachment/5594308/+files/VarLogDistupgradeAptlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1976293/+attachment/5594305/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] VarLogDistupgradeAptHistorylog.txt
apport information ** Attachment added: "VarLogDistupgradeAptHistorylog.txt" https://bugs.launchpad.net/bugs/1976293/+attachment/5594306/+files/VarLogDistupgradeAptHistorylog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1976293/+attachment/5594303/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1976293/+attachment/5594304/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] Re: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices
apport information ** Tags added: apport-collected dist-upgrade jammy wayland-session ** Description changed: On a default Ubuntu desktop installation (with GNOME) doing `do-release- upgrade` from 21.10 to 22.04 installed *brltty* breaking FTDI USB serial devices. ``` [ 2435.150025] usb 1-2: new full-speed USB device number 6 using xhci_hcd [ 2435.305646] usb 1-2: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 [ 2435.305660] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2435.305666] usb 1-2: Product: USB Serial Converter [ 2435.305671] usb 1-2: Manufacturer: FTDI [ 2435.305675] usb 1-2: SerialNumber: FTFCV4W7 [ 2435.311747] ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected [ 2435.311824] usb 1-2: Detected FT232RL [ 2435.313260] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0 [ 2437.583625] usb 1-2: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1 [ 2437.585095] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 2437.585168] ftdi_sio 1-2:1.0: device disconnected ``` The brltty problem is tracked in the Debian BTS as #667616 [1], and the solution is to remove the package with `sudo apt purge brltty`. The question is though, why `do-release-upgrade` installed it in the first place. I do not remember the problem from earlier release upgrades. [1]: https://bugs.debian.org/667616 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CrashDB: ubuntu + CrashReports: + 644:0:116:0:2022-05-31 15:11:54.155275593 +0200:2022-05-31 15:11:53.683275612 +0200:/var/crash/kdump_lock + 644:0:116:325:2022-05-31 15:11:57.819275442 +0200:2019-08-23 14:33:45.567141279 +0200:/var/crash/kexec_cmd + CurrentDesktop: GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2017-03-20 (1898 days ago) + InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) + Package: ubuntu-release-upgrader (not installed) + ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 + Tags: wayland-session jammy dist-upgrade + Uname: Linux 5.15.0-33-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-05-06 (26 days ago) + UserGroups: adm lpadmin sambashare sudo + VarLogDistupgradeXorgFixuplog: + INFO:root:/usr/bin/do-release-upgrade running + INFO:root:No xorg.conf, exiting + _MarkForUpload: True ** Attachment added: "CurrentDmesg.txt.txt" https://bugs.launchpad.net/bugs/1976293/+attachment/5594302/+files/CurrentDmesg.txt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958224] Re: brltty claiming cp210x devices on 22.04
1. This is Debian bug report #667616. 2. *brltty* was installed when doing `do-release-upgrade` from 21.10 to 22.04 [2]. [1]: https://bugs.debian.org/667616 [2]: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293 ** Bug watch added: Debian Bug tracker #667616 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667616 ** Also affects: brltty (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667616 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976293] [NEW] 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices
Public bug reported: On a default Ubuntu desktop installation (with GNOME) doing `do-release- upgrade` from 21.10 to 22.04 installed *brltty* breaking FTDI USB serial devices. ``` [ 2435.150025] usb 1-2: new full-speed USB device number 6 using xhci_hcd [ 2435.305646] usb 1-2: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 [ 2435.305660] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2435.305666] usb 1-2: Product: USB Serial Converter [ 2435.305671] usb 1-2: Manufacturer: FTDI [ 2435.305675] usb 1-2: SerialNumber: FTFCV4W7 [ 2435.311747] ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected [ 2435.311824] usb 1-2: Detected FT232RL [ 2435.313260] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0 [ 2437.583625] usb 1-2: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1 [ 2437.585095] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 2437.585168] ftdi_sio 1-2:1.0: device disconnected ``` The brltty problem is tracked in the Debian BTS as #667616 [1], and the solution is to remove the package with `sudo apt purge brltty`. The question is though, why `do-release-upgrade` installed it in the first place. I do not remember the problem from earlier release upgrades. [1]: https://bugs.debian.org/667616 ** Affects: ubuntu-release-upgrader (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/1976293 Title: 21.10 → 22.04: Installs *brltty* breaking FTDI USB serial devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960592] Re: `apt build-dep qemu-system-ppc` fails
Thank you all for your help. $ apt-cache policy qemu gcc-powerpc64-linux-gnu qemu: Installed: (none) Candidate: 1:6.0+dfsg-2expubuntu1.1 Version table: 1:6.0+dfsg-2expubuntu1.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports impish-updates/universe ppc64el Packages 1:6.0+dfsg-2expubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports impish/universe ppc64el Packages N: Unable to locate package gcc-powerpc64-linux-gnu But: $ apt-cache policy gcc-powerpc-linux-gnu gcc-powerpc-linux-gnu: Installed: (none) Candidate: 4:11.2.0-1ubuntu1 Version table: 4:11.2.0-1ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports impish/universe ppc64el Packages Thank you for telling me about `--arch-only`. That seems to be it. $ sudo eatmydata apt --arch-only build-dep qemu Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. As I had manually installed the dependencies before, nothing happened as expected. ** Changed in: qemu (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960592 Title: `apt build-dep qemu-system-ppc` fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1960592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960592] [NEW] `apt build-dep qemu-system-ppc` fails
Public bug reported: On Ubuntu 21.10 (ppc64le) trying to install QEMU’s build dependencies fails with: ``` $ sudo apt build-dep qemu-system-ppc Reading package lists... Done Picking 'qemu' as source package instead of 'qemu-system-ppc' Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: builddeps:qemu : Depends: gcc-alpha-linux-gnu but it is not installable Depends: gcc-powerpc64-linux-gnu but it is not installable Depends: gcc-sparc64-linux-gnu but it is not installable Depends: gcc-hppa-linux-gnu but it is not installable E: Unable to correct problems, you have held broken packages. ``` ** Affects: qemu (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/1960592 Title: `apt build-dep qemu-system-ppc` fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1960592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956147] Re: bluetooth: Google Nest not working
The system was updated from Ubuntu 20.04 to 21.10, but it’s still not working out of the box without the script `a2dp.py`. I am not able to work more on the issue, as I do not have the environment, but maybe Canonical and Google should work more closely together on the QA side. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956147 Title: bluetooth: Google Nest not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1956147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827452] Re: null pointer dereference in uvcvideo
I read at [1] about the issue. @kaihengfeng, I suggest to send the patch upstream for review even with no tests. Maybe there will be testers on the Linux kernel mailing list. [1]: https://etbe.coker.com.au/2022/01/09/video-conferencing-lca/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827452 Title: null pointer dereference in uvcvideo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956147] Re: bluetooth: Google Nest not working
Yes, thank you for assigning the right component. Personally, for desktops, I would always recommend the latest release. I think a lot of users do not know the difference, and just click the green button. > We also have the latest BlueZ in Ubuntu already. Do you mean 21.10, which has 5.60-0ubuntu2.1? Ubuntu 20.04 has 5.53-0ubuntu3.4. Also, as written, `bluetoothd` seemed to have crashed several times, and the user allowed the crash reporter to upload the traces. Where can those be found? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956147 Title: bluetooth: Google Nest not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1956147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956147] Re: bluetooth: Google Nest not working
I understand, that bugs are probably fixed in newer versions. https://ubuntu.com/#download still offers Ubuntu 20.04 for desktops, and even highlighted green. So what functionality can users expect? Anyway, I just wanted to report it, and, as it is not my device, I am also unable to debug more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956147 Title: bluetooth: Google Nest not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1956147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956147] Re: bluetooth: Google Nest not working
** Attachment added: "a2dp.py fixing the problem" https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1956147/+attachment/5550575/+files/a2dp-0.6.2.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956147 Title: bluetooth: Google Nest not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1956147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956147] Re: bluetooth: Google Nest not working
This is not my system, so I cannot debug a lot. Linux kernel 5.4.x is used, and Linux logs hci related messages, and bluetoothd also segfaults. (Ubuntu noticed the crash, and should have uploaded the resulting dumps.) What fixed it was using `a2dp.py`: ``` $ curl "https://gist.githubusercontent.com/pylover/d68be364adac5f946887b85e6ed6e7ae/raw/install.sh; | sh % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 314 100 3140 0664 0 --:--:-- --:--:-- --:--:-- 670 % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 11977 100 119770 0 27402 0 --:--:-- --:--:-- --:--:-- 27470 a2dp installation was successfull. Run a2dp.py [-h/--help] and enjoy the HiFi music! $ a2dp.py Connection MADE Selecting device: 1. XXX 2. XXX 3. 14:C1:4E:99:XX:XX Office speaker 4. XXX 5. XXX Select device[1]: 3 Device MAC: 14:C1:4E:99:XX:XX Device ID: bluez_card.14_C1_4E_99_XX_XX Sink: bluez_sink.14_C1_4E_99_XX_XX Updating default sink to bluez_sink.14_C1_4E_99_XX_XX Setting the off profile Disconnecting the device. Connecting again. Device ID: bluez_card.14_C1_4E_99_XX_XX Setting the a2dp profile Updating default sink to bluez_sink.14_C1_4E_99_XX_XX Ignoring: Command: pacmd list-sink-inputs | grep "index:" failed with status: 1 stderr: Exiting bluetoothctl "Enjoy" the HiFi stereo music ``` ** Package changed: ubuntu => gnome-bluetooth (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956147 Title: bluetooth: Google Nest not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1956147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956147] [NEW] bluetooth: Google Nest not working
Public bug reported: Connect a Google Nest to a ASUS laptop running Ubuntu 20.04, the devices pair, and *Office Speaker* shows up as an output device in the *Sound* settings, but no sound is heard (also doing the speaker test). In Debian sid/unstable with GNOME Shell 41.2 and *gnome-bluetooth* 3.34.5-4, there is one more row in the audio settings allowing to set up some codecs. After changing that around, it finally works. Ubuntu probably needs something similar. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "Screenshot of audio/sound dialog in Debian sid/unstable" https://bugs.launchpad.net/bugs/1956147/+attachment/5550544/+files/debian-sid-unstable.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956147 Title: bluetooth: Google Nest not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1956147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751508] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n") from InitOutput()
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1279
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1279
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1279
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751508
Title:
Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("Couldn't add screen\n") from InitOutput()
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1751508/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750199] Re: Blurry Icons on HighDPI
Under *Tools* → *Options* → *View*, what theme do you have selected? Even with *Elementary (SVG)* I get blurry icons with *libreoffice* 7.2.1-3 from Debian sid/unstable. I reported the issue [upstream][1]. [1]: https://bugs.documentfoundation.org/show_bug.cgi?id=144583 ** Bug watch added: Document Foundation Bugzilla #144583 https://bugs.documentfoundation.org/show_bug.cgi?id=144583 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750199 Title: Blurry Icons on HighDPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937245] Re: ppc64le: Fails to load HTTPS pages with `Error code: SSL_ERROR_BAD_SERVER`
The article *Firefox 90 on POWER (and a JIT progress report)* [1] summarizes the issue in NSS. It’s upstream bug report 1566124 [2], and there are two simple patches to be applied to NSS 3.66. Starting Firefox with `NSS_DISABLE_PPC_GHASH=1` works around the issue. [1]: https://www.talospace.com/2021/07/firefox-90-on-power-and-jit-progress.html [2]: https://bugzilla.mozilla.org/show_bug.cgi?id=1566124 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937245 Title: ppc64le: Fails to load HTTPS pages with `Error code: SSL_ERROR_BAD_SERVER` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1937245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937245] Re: ppc64le: Fails to load HTTPS pages with `Error code: SSL_ERROR_BAD_SERVER`
** Bug watch added: Mozilla Bugzilla #1566124 https://bugzilla.mozilla.org/show_bug.cgi?id=1566124 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937245 Title: ppc64le: Fails to load HTTPS pages with `Error code: SSL_ERROR_BAD_SERVER` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1937245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937245] [NEW] ppc64le: Fails to load HTTPS pages with `Error code: SSL_ERROR_BAD_SERVER`
Public bug reported: Firefox 90.0+build1-0ubuntu0.21.04.1 fails to load HTTPS URLs with the error: > Secure Connection Failed > > An error occurred during a connection to blog.fefe.de. The client has > encountered bad data from the server. > > Error code: SSL_ERROR_BAD_SERVER > > * The page you are trying to view cannot be shown because the authenticity > of the received data could not be verified. > * Please contact the website owners to inform them of this problem. Nothing related is logged in the terminal window, Firefox was started from. ** Affects: firefox (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/1937245 Title: ppc64le: Fails to load HTTPS pages with `Error code: SSL_ERROR_BAD_SERVER` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1937245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
I am also seeing this on a the AMD Ryzen desktop system Dell OptiPlex 5055 with Linux 5.13-rc7. [0.00] DMI: Dell Inc. OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.25 05/03/2021 […] [ 12.810715] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found [ 12.820176] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) Alex, to summarize, this is a firmware bug, so needs to be reported to Dell? Is there any way to check, what features do not work? Then it’d be easier to verify that and talk to the Dell support. Lastly, the Dell Linux maintainers could be contacted too. DELL SMBIOS WMI DRIVER L: dell.client.ker...@dell.com L: platform-driver-...@vger.kernel.org S: Maintained F: drivers/platform/x86/dell/dell-smbios-wmi.c F: tools/wmi/dell-smbios-example.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890467 Title: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931630] Re: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail
** Package changed: procps (Ubuntu) => linux-meta-kvm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931630 Title: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-kvm/+bug/1931630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931630] Re: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail
In #ubuntu-ser...@irc.libera.chat I was told to move this issue to *linux-image-kvm*. How can I do that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931630 Title: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1931630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931630] [NEW] Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail
Public bug reported: *procps* ships `/etc/sysctl.d/10-magic-sysrq.conf:kernel.sysrq = 176`, which is run by `systemd-sysctl.service`. This fails on a system run with a Linux image built for virtual machines *linux-image-kvm*, which has `CONFIG_MAGIC_SYSRQ` not set. ``` $ sudo /lib/systemd/systemd-sysctl Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Couldn't write '4194304' to 'kernel/pid_max': Invalid argument $ grep SYSRQ /boot/config-5.4.0-1009-kvm # CONFIG_MAGIC_SYSRQ is not set ``` ** Affects: procps (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/1931630 Title: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1931630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927540] [NEW] /var/lib/dpkg/info/nis.postinst: 76: [: -eq: unexpected operator
Public bug reported: With `/bin/sh` being dash and not Bash, the postinst script fails. ``` $ sudo apt reinstall nis Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 14.2 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://de.ports.ubuntu.com/ubuntu-ports hirsute/universe ppc64el nis all 4.2 [14.2 kB] Fetched 14.2 kB in 0s (110 kB/s) (Reading database ... 420369 files and directories currently installed.) Preparing to unpack .../apt/archives/nis_4.2_all.deb ... update-rc.d: error: unable to read /etc/init.d/nis Unpacking nis (4.2) over (4.2) ... Setting up nis (4.2) ... /var/lib/dpkg/info/nis.postinst: 76: [: -eq: unexpected operator ``` Using `/bin/bash` and doing `dpkg -a --configure` seems to fix this issue. The bashism can probably be rewritten. ** Affects: nis (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/1927540 Title: /var/lib/dpkg/info/nis.postinst: 76: [: -eq: unexpected operator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1927540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923714] Re: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1
Rico is right. I only had the entry below. No idea, if I only added the line below several versions ago or some upgrade changed it. (Probably the former.) deb http://de.ports.ubuntu.com groovy-proposed main restricted Following https://wiki.ubuntu.com/Testing/EnableProposed I added `multiverse universe`, and now the upgrade went through. Sorry for the noise. Please close the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923714 Title: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1923714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923714] [NEW] groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1
Public bug reported: Among other, package *libreoffice* 7.0.5-0ubunt0.20.10.1 is missing in the *groovy-proposed* archives. ``` $ more /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-poli cy" VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy $ apt list --upgradable Listing... Done libreoffice-base-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-calc/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-draw/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gnome/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gtk3/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-impress/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-math/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-writer/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] python3-uno/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] ``` ``` $ apt-cache policy libreoffice-math libreoffice-math: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.5-0ubuntu0.20.10.1 Version table: 1:7.0.5-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com groovy-proposed/main ppc64el Packages *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/main ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/main ppc64el Packages $ apt-cache policy libreoffice libreoffice: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.3-0ubuntu0.20.10.1 Version table: *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/universe ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/universe ppc64el Packages ``` ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Summary changed: - ppc64le: Unable to upgrade + groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923714 Title: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1923714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
Please create a separate bug report, as the error type is different from the original report here. Also, in the new report (best upstream), give more information (firmware version, extension cards, …), and also *attach* (not paste) the output of `lspci -tvnn` and `sudo lspci -vvxxx`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
For every one affected, at least attach the output of `lspci -nn`, `dmesg`, and give details for your system. As this bug has gotten long, and causes go from firmware, firmware configuration to hardware issues, it’s better if you opened a separate report directly upstream, after testing the current Linux kernel using Ubuntu PPA repository [1]. [1]: https://kernel.ubuntu.com/~kernel-ppa/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922082] [NEW] Exec binary '/usr/libexec/evolution-data-server/evolution-alarm-notify' does not exist: No such file or directory
Public bug reported: On ppc64le and Ubuntu 20.10 with *evolution-data-server* 3.38.1-1, the logs contain, when starting an Xfce session over X2Go. [98982.444956] systemd-xdg-autostart-generator[297820]: Exec binary '/usr/libexec/evolution-data-server/evolution-alarm-notify' does not exist: No such file or directory [98982.444963] systemd-xdg-autostart-generator[297820]: Not generating service for XDG autostart app-org.gnome.Evolution\x2dalarm\x2dnotify-autostart.service, error parsing Exec= line: No such file or directory The executable is missing. $ dpkg -S /usr/libexec/evolution-data-server/evolution-alarm-notify dpkg-query: no path found matching pattern /usr/libexec/evolution-data-server/evolution-alarm-notify (In Debian sid/unstable it is present.) ** Affects: evolution-data-server (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/1922082 Title: Exec binary '/usr/libexec/evolution-data-server/evolution-alarm- notify' does not exist: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1922082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919121] [NEW] /usr/bin/grub-editenv: error: invalid environment block.
Public bug reported: Upgrading GRUB on a ppc64le machine (8335-GCA (IBM Power System S822LC)) 2021-03-15 08:20:23 upgrade grub-common:ppc64el 2.04-1ubuntu26.8 2.04-1ubuntu26.11 `grub-initrd-fallback.service` failed to restart. ``` $ sudo journalctl -xe […] Mar 15 08:20:30 s822lc grub-editenv[2481630]: /usr/bin/grub-editenv: error: invalid environment block. Mar 15 08:20:30 s822lc systemd[1]: grub-initrd-fallback.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit grub-initrd-fallback.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Mar 15 08:20:30 s822lc systemd[1]: grub-initrd-fallback.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit grub-initrd-fallback.service has entered the 'failed' state with result 'exit-code'. Mar 15 08:20:30 s822lc systemd[1]: Failed to start GRUB failed boot detection. -- Subject: A start job for unit grub-initrd-fallback.service has failed ``` ** Affects: grub2 (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/1919121 Title: /usr/bin/grub-editenv: error: invalid environment block. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1919121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915007] Re: ppc64le: `/usr/lib/grub/powerpc-ieee1275/prep-bootdev` hangs during upgrade
** Attachment added: "Output of `strace -ff prep-bootdev -l`" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915007/+attachment/5461237/+files/strace-prep-bootdev-l.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915007 Title: ppc64le: `/usr/lib/grub/powerpc-ieee1275/prep-bootdev` hangs during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915007] [NEW] ppc64le: `/usr/lib/grub/powerpc-ieee1275/prep-bootdev` hangs during upgrade
Public bug reported:
Doing `apt upgrade`
2021-02-08 10:41:20 upgrade grub-ieee1275:ppc64el 2.04-1ubuntu26
2.04-1ubuntu26.8
the postinst hangs:
```
root 236284 0.0 0.0 18304 9536 ?S09:59 0:00 sudo apt
full-upgrade
root 236285 0.0 0.0 77376 64256 ?S09:59 0:04 \_ apt
full-upgrade
root 253209 0.0 0.0 21440 14336 pts/1Ss+ 11:10 0:04 \_
/usr/bin/dpkg --status-fd 45 --configure --pending
root 305396 0.0 0.0 33408 24896 pts/1S+ 11:19 0:00 \_
/usr/bin/perl -w /usr/share/debconf/frontend
/var/lib/dpkg/info/grub-ieee1275.postinst configure 2.04-1ubuntu26
root 305407 0.0 0.0 12032 5632 pts/1S+ 11:19 0:00
\_ /bin/bash /var/lib/dpkg/info/grub-ieee1275.postinst configure 2.04-1ubuntu26
root 305520 0.0 0.0 8960 3328 pts/1D+ 11:19 0:00
\_ /usr/lib/grub/powerpc-ieee1275/prep-bootdev
```
Trying to debug a little `sudo /usr/lib/grub/powerpc-ieee1275/prep-
bootdev -l` hangs too. strace shows, that it hangs when opening the non-
existing `/dev/sdf`:
```
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop17:10 65.3M 1 loop /snap/lxd/19012
loop27:2054M 1 loop /snap/core18/1987
loop37:30 91.1M 1 loop /snap/core/10582
loop47:4054M 1 loop /snap/core18/1946
loop57:50 91.1M 1 loop /snap/core/10575
loop67:60 65.3M 1 loop /snap/lxd/19163
sda 8:01 931.5G 0 disk
├─sda1 8:11 7M 0 part
└─sda2 8:21 931.5G 0 part /var/lib/docker/btrfs
sdb 8:16 1 931.5G 0 disk /amd/flughafenberlinbrandenburgwillybrandt/0
sr0 11:01 1024M 0 rom
sr1 11:11 1024M 0 rom
sr2 11:21 1024M 0 rom
sr3 11:31 1024M 0 rom
$ sudo strace -ff /usr/lib/grub/powerpc-ieee1275/prep-bootdev -l
[…]
lstat("/dev", {st_mode=S_IFDIR|0755, st_size=4920, ...}) = 0
lstat("/dev/sdc", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x8, 0x20), ...}) = 0
stat("/dev/sdc", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x8, 0x20), ...}) = 0
openat(AT_FDCWD, "/dev/sdc", O_RDONLY) = -1 ENOMEDIUM (No medium found)
openat(AT_FDCWD, "/dev/sdc", O_RDONLY) = -1 ENOMEDIUM (No medium found)
lstat("/dev", {st_mode=S_IFDIR|0755, st_size=4920, ...}) = 0
lstat("/dev/sdd", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x8, 0x30), ...}) = 0
stat("/dev/sdd", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x8, 0x30), ...}) = 0
openat(AT_FDCWD, "/dev/sdd", O_RDONLY) = -1 ENOMEDIUM (No medium found)
openat(AT_FDCWD, "/dev/sdd", O_RDONLY) = -1 ENOMEDIUM (No medium found)
lstat("/dev", {st_mode=S_IFDIR|0755, st_size=4920, ...}) = 0
lstat("/dev/sde", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x8, 0x40), ...}) = 0
stat("/dev/sde", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x8, 0x40), ...}) = 0
openat(AT_FDCWD, "/dev/sde", O_RDONLY) = -1 ENOMEDIUM (No medium found)
openat(AT_FDCWD, "/dev/sde", O_RDONLY) = -1 ENOMEDIUM (No medium found)
lstat("/dev", {st_mode=S_IFDIR|0755, st_size=4920, ...}) = 0
lstat("/dev/sdf", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x8, 0x50), ...}) = 0
stat("/dev/sdf", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x8, 0x50), ...}) = 0
openat(AT_FDCWD, "/dev/sdf", O_RDONLY
```
```
$ sudo fdisk -l
Disk /dev/loop1: 65.28 MiB, 68444160 bytes, 133680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop2: 54.4 MiB, 56668160 bytes, 110680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop3: 91.6 MiB, 95477760 bytes, 186480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop4: 53.99 MiB, 56590336 bytes, 110528 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop5: 91.6 MiB, 95477760 bytes, 186480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop6: 65.29 MiB, 68456448 bytes, 133704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000NX0313
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 242ACBC1-F70A-4E15-91B8-8340D055F79B
Device StartEndSectors Size Type
/dev/sda1 2048 16383 14336 7M PowerPC PReP boot
/dev/sda2 16384 1953523711 1953507328 931.5G Linux filesystem
Disk /dev/sdb: 931.53 GiB, 1000204886016
[Bug 1883065] Re: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable
I create upstream issue https://github.com/intel/Intel-Linux-Processor- Microcode-Data-Files/issues/35. ** Bug watch added: github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues #35 https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/35 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883065 Title: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1883065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901815] [NEW] Release 20.10 announced despite already running it
Public bug reported: Ubuntu announces the 20.10 release, despite it running already. Probably related to some poor integration of *oem-release* (purged) or *oem- config* . ``` user@helmut-XPS-13-9310:~$ ssh helmut@192.168.0.3 Welcome to Ubuntu 20.10 (GNU/Linux 5.10.0-rc1+ x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage 0 Aktualisierungen können sofort installiert werden. 0 dieser Aktualisierung sind Sicherheitsaktualisierungen. New release '20.10' available. Run 'do-release-upgrade' to upgrade to it. Last login: Tue Oct 27 16:47:23 2020 from 192.168.0.7 user@helmut-XPS-13-9310:~$ more /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy ** Affects: update-manager (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/1901815 Title: Release 20.10 announced despite already running it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1901815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901765] [NEW] Unable to deal with release upgrades
Public bug reported: On a Dell XPS 13 9310 with shipped Dell Ubuntu 20.04.1, after allowing release upgrades, and running `sudo do-release-upgrade` and upgrading to 20.10, looking at `/etc/os-release` still showed 20.04, as it was redirected to `/usr/lib/os-release.oem`. The integration really needs to be improved to allow users to upgrade. ** Affects: oem-config (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/1901765 Title: Unable to deal with release upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1901765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901670] [NEW] gdbus crashed with segmentation fault
Public bug reported: With (Dell) Ubuntu 20.04.1 on a Dell XPS 13 9310, after allowing release upgrades, the process crashed the first time. ``` $ sudo do-release-upgrade Neue Veröffentlichungen von Ubuntu werden gesucht Holen:1 Signatur der Aktualisierungsanwendung [819 B] Holen:2 Aktualisierungsanwendung [1.338 kB] Es wurden 1.339 kB in 0 s geholt (0 B/s) »groovy.tar.gz« wird gegenüber »groovy.tar.gz.gpg« legitimiert »groovy.tar.gz« wird entpackt Zwischenspeicher wird gelesen Speicherzugriffsfehler ``` ``` $ dmesg […] [42711.249670] gdbus[38237]: segfault at a0 ip 7fb16b69f0cd sp 7fb163ffea60 error 4 in libc-2.31.so[7fb16b67b000+178000] [42711.249681] Code: fd ff 49 83 c5 02 41 0f b7 6d fe 49 89 c6 4c 8d 78 fe 4d 85 e4 75 13 eb cc 0f 1f 40 00 4c 8b 63 08 48 83 c3 08 4d 85 e4 74 bb <66> 41 3b 2c 24 75 ec 49 8d 7c 24 02 4c 89 fa 4c 89 ee e8 9c c4 fd […] ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.28 [origin: unknown] ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 Uname: Linux 5.6.0-1032-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 10:45:53 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-10-16 (10 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-10-27 (0 days ago) VarLogDistupgradeAptlog: Log time: 2020-10-27 10:45:21.955323 Log time: 2020-10-27 10:45:24.032294 modified.conffile..etc.update-manager.release-upgrades: [modified] mtime.conffile..etc.update-manager.release-upgrades: 2020-10-27T10:40:13.677932 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901670 Title: gdbus crashed with segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897745] Re: Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver
The output of `ubuntu-bug` is attached, and contains everything that’s needed as far as I can see. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897745 Title: Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897745] [NEW] Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver
Public bug reported: On the Surface Pro 4 with USB Marvell Bluetooth/WLAN device, upgrading from Ubuntu 18.04 with Linux 4.15.x to Ubuntu 20.04 with Linux 5.4.x, only WPA2 Enterprise networks stop working, but other continue to work. WPA: Failed to set GTK to the driver (alg=2 keylen=32 keyidx=1) Starting Ubuntu 20.04.1 with Linux 4.15.x, the problem is gone. Testing Ubuntu’s Linux mainline builds [1], the problem is still there in 5.4.68, but gone in 5.5-rc1. We do not have the resources to bisect this further, as the user needs the device back now. [1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release ** Attachment added: "Output of `ubuntu-bug --save /dev/shm/… linux-image-5.4.0-48-generic" https://bugs.launchpad.net/bugs/1897745/+attachment/5415294/+files/20200929%E2%80%93linux-5.4.0-48%E2%80%93dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897745 Title: Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
>From the manual page capabilities(7): CAP_SYS_NICE * Lower the process nice value (nice(2), setpriority(2)) and change the nice value for arbitrary processes; * set real-time scheduling policies for calling process, and set scheduling policies and priorities for arbitrary processes (sched_setscheduler(2), sched_setparam(2), sched_setattr(2)); * set CPU affinity for arbitrary processes (sched_setaffin‐ ity(2)); * set I/O scheduling class and priority for arbitrary processes (ioprio_set(2)); * apply migrate_pages(2) to arbitrary processes and allow pro‐ cesses to be migrated to arbitrary nodes; * apply move_pages(2) to arbitrary processes; * use the MPOL_MF_MOVE_ALL flag with mbind(2) and move_pages(2) No idea, if cups-browsed should be allowed to change the nice value of *arbitrary* processes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897369 Title: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873764] Re: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id
*** This bug is a duplicate of bug 1872564 *** https://bugs.launchpad.net/bugs/1872564 The original report contains two issues, where only the second one is fixed in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564. For the first audit messages for `cups-browsed` [ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 comm="cups-browsed" capability=23 capname="sys_nice" I created https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873764 Title: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1873764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897369] [NEW] apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
Public bug reported: In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents `/usr/sbin/cups-browsed` to change its nice value. $ sudo dmesg | grep apparmor [541870.509461] audit: type=1400 audit(1600898428.089:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=62030 comm="cups-browsed" capability=23 capname="sys_nice" [628298.779668] audit: type=1400 audit(1600984854.115:61): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=66850 comm="cups-browsed" capability=23 capname="sys_nice" [714667.424963] audit: type=1400 audit(1601071220.527:62): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=76828 comm="cups-browsed" capability=23 capname="sys_nice" ** Affects: cups (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/1897369 Title: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660316] Re: apparmor denial of CUPS
@skliarie, your pasted log message is actually a different issue, and I just reported https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369 for it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660316 Title: apparmor denial of CUPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1660316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1882943] Re: Dell Latitude 5591, i7-8850H, sig=0x906ea/20200609, Boot freezes silently after 'intel-microcode' upgrade
Am 18.09.20 um 13:55 schrieb Mirek Ingr: > Okay, please find the attached journal. Thank you. There it is: Sep 18 08:15:43 B4 kernel: DMI: Dell Inc. Latitude 5591/0DVVG1, BIOS 1.13.1 07/14/2020 Sep 18 08:15:43 B4 kernel: microcode: sig=0x906ea, pf=0x20, revision=0xd6 So, it is the same microcode update version, that break back in June? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882943 Title: Dell Latitude 5591, i7-8850H, sig=0x906ea/20200609, Boot freezes silently after 'intel-microcode' upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1882943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1882943] Re: Dell Latitude 5591, i7-8850H, sig=0x906ea/20200609, Boot freezes silently after 'intel-microcode' upgrade
Am 18.09.20 um 09:40 schrieb Mirek Ingr: > Sure thing, here you are: > $ grep -i microcode /proc/cpuinfo > microcode : 0xd6 > microcode : 0xd6 > microcode : 0xd6 > microcode : 0xd6 > microcode : 0xd6 > microcode : 0xd6 > microcode : 0xd6 > microcode : 0xd6 > microcode : 0xd6 > microcode : 0xd6 > microcode : 0xd6 > microcode : 0xd6 Thank you. > The output of 'dmesg' is attached as a file. Ah. Your buffer is too small. As it’s a ring buffer, earlier messages get overridden. Either increase the size on the Linux command line with for example `log_buf_len=4M`, or, if the systemd journal is running, it should store all Linux kernel messages too: $ journalctl -k -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882943 Title: Dell Latitude 5591, i7-8850H, sig=0x906ea/20200609, Boot freezes silently after 'intel-microcode' upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1882943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1882943] Re: Dell Latitude 5591, i7-8850H, sig=0x906ea/20200609, Boot freezes silently after 'intel-microcode' upgrade
Am 18.09.20 um 09:13 schrieb Mirek Ingr: > $ dmesg | grep microcode > Please attach the whole output. > $ iucode-tool -Sv > iucode-tool: system has processor(s) with signature 0x000906ea > iucode-tool: assuming all processors have the same type, family and model > > > $ lscpu > Architecture:x86_64 > CPU op-mode(s): 32-bit, 64-bit > Byte Order: Little Endian > Address sizes: 39 bits physical, 48 bits virtual > CPU(s): 12 > On-line CPU(s) list: 0-11 > Thread(s) per core: 2 > Core(s) per socket: 6 > Socket(s): 1 > NUMA node(s):1 > Vendor ID: GenuineIntel > CPU family: 6 > Model: 158 > Model name: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz > Stepping:10 […] Please also paste the output of `grep -i microcode /proc/cpuinfo`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882943 Title: Dell Latitude 5591, i7-8850H, sig=0x906ea/20200609, Boot freezes silently after 'intel-microcode' upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1882943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882943] Re: Dell Latitude 5591, i7-8850H, sig=0x906ea/20200609, Boot freezes silently after 'intel-microcode' upgrade
@mirek-ingr, can you please attach the output of `dmesg` when running the updated firmware? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882943 Title: Dell Latitude 5591, i7-8850H, sig=0x906ea/20200609, Boot freezes silently after 'intel-microcode' upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1882943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883065] Re: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable
It looks like microcode update revision 0xd6 is still the officially shipped version. The often occurring hangs without the power cable plugged in, are still happening. Booting with `maxcpus=1` and adding earlyprintk=efi earlycon=efifb debug to the Linux command, the last messages are: […] random: crng done (trusting CPU's manufacturer) Console: colour dummy device 80x25 printk: console [tty0] enabled printk: bootconsole [efifb0] disabled So, it might indeed be related to bug 1862751. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883065 Title: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1883065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887959] Re: Unable to upgrade several qt5 packages (libqt5gui5, …)
Shouldn’t the metadata (Conflicts, Replaces, …) reflect that, so apt can find an upgrade path? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887959 Title: Unable to upgrade several qt5 packages (libqt5gui5, …) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1887959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887959] Re: Unable to upgrade several qt5 packages (libqt5gui5, …)
Thank you for the quick response. Yes, with that apt seems to be able to resolve the conflicts. ``` $ sudo apt install libqt5core5a Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 libqt5sql5 libqt5svg5 libqt5widgets5 libqt5xml5 Suggested packages: qt5-image-formats-plugins qtwayland5 Recommended packages: qttranslations5-l10n qt5-gtk-platformtheme libqt5sql5-sqlite | libqt5sql5-mysql | libqt5sql5-odbc | libqt5sql5-psql | libqt5sql5-tds | libqt5sql5-ibase The following packages will be REMOVED: automoc kdelibs-bin kdelibs5-dev kdoctools libattica0.4 libdbusmenu-qt2 libkcmutils4 libkde3support4 libkdeclarative5 libkdecore5 libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4 libkfile4 libkhtml5 libkidletime4 libkimproxy4 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4 libknewstuff2-4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4 libkprintutils4 libkpty4 libkrosscore4 libkrossui4 libktexteditor4 libkunitconversion4 libkutils4 libphonon-dev libphonon4 libplasma3 libqca2 libqt4-dbus libqt4-declarative libqt4-designer libqt4-dev libqt4-dev-bin libqt4-help libqt4-network libqt4-opengl libqt4-qt3support libqt4-script libqt4-scripttools libqt4-sql libqt4-svg libqt4-test libqt4-xml libqt4-xmlpatterns libqtcore4 libqtdbus4 libqtgui4 libqtwebkit4 libsolid4 libthreadweaver4 phonon-backend-null qdbus qt4-linguist-tools The following packages will be upgraded: libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 libqt5sql5 libqt5svg5 libqt5widgets5 libqt5xml5 9 upgraded, 0 newly installed, 64 to remove and 3 not upgraded. Need to get 9,045 kB of archives. After this operation, 207 MB disk space will be freed. ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887959 Title: Unable to upgrade several qt5 packages (libqt5gui5, …) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1887959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887959] [NEW] Unable to upgrade several qt5 packages (libqt5gui5, …)
Public bug reported: After upgrading from Ubuntu 19.10 (maybe 18.04) to 20.04, I am unable to upgrade the packages below. The following packages have been kept back: libboost-date-time-dev libboost-dev libboost-filesystem-dev libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 libqt5sql5 libqt5svg5 libqt5widgets5 libqt5xml5 ** Affects: qtbase-opensource-src (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/1887959 Title: Unable to upgrade several qt5 packages (libqt5gui5, …) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1887959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887959] Re: Unable to upgrade several qt5 packages (libqt5gui5, …)
``` $ apt list --upgradable Listing... Done libboost-date-time-dev/focal 1.71.0.0ubuntu2 ppc64el [upgradable from: 1.67.0.2] libboost-dev/focal 1.71.0.0ubuntu2 ppc64el [upgradable from: 1.67.0.2] libboost-filesystem-dev/focal 1.71.0.0ubuntu2 ppc64el [upgradable from: 1.67.0.2] libqt5core5a/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5dbus5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5gui5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5network5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5printsupport5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5sql5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5svg5/focal 5.12.8-0ubuntu1 ppc64el [upgradable from: 5.12.4-1] libqt5widgets5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] libqt5xml5/focal 5.12.8+dfsg-0ubuntu1 ppc64el [upgradable from: 5.12.4+dfsg-4ubuntu1.1] ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887959 Title: Unable to upgrade several qt5 packages (libqt5gui5, …) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1887959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 313514] Re: MASTER: evdev driver ignores keycodes > 255
Is this still a problem with *xserver-xorg-input-libinput*, which replaces *xserver-xorg-input-evdev*? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/313514 Title: MASTER: evdev driver ignores keycodes > 255 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/313514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 30562] Re: Acer € and $ + special laptop keys: outside supported X keycode range
*** This bug is a duplicate of bug 313514 *** https://bugs.launchpad.net/bugs/313514 If this still an issue, please check with the libinput tools. sudo libinput debug-events I got the currency keys working on the Acer TravelMate 5735Z [1]. [1]: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/commit/5ea031eb4998726dc5a00ba1fb2253b21cdbe366 "Map `KEY_DOLLAR` and `KEY_EURO` to `dollar` and `EuroSign`" -- 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/30562 Title: Acer € and $ + special laptop keys: outside supported X keycode range To manage notifications about this bug go to: https://bugs.launchpad.net/debian-goodies/+bug/30562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862751] Re: Hard lockups using microcode releases 20191115 on Intel Whiskey Lake
PS: The Linux command line parameter `dis_ucode_ldr` can be used to disable applying microcode updates [1]. [1]: https://lkml.org/lkml/2020/6/11/651 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862751 Title: Hard lockups using microcode releases 20191115 on Intel Whiskey Lake To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1862751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862751] Re: Hard lockups using microcode releases 20191115 on Intel Whiskey Lake
Trying to find out, if bug #1883065 [1] is a duplicate of this one. Is this a laptop? If yes, does having the power cable plugged in make a difference? Starting with `maxcpus=1` and then trying to bring more CPUs online, on the Dell Precision 3540 with dedicated AMD graphics card, it always hangs after one or two more CPUs when on battery. With the power cable, it often works, but I saw it also failing. I reported the issue to the Linux Kernel Mailing List *Intel laptop: Starting with `maxcpus=1` and then bringing other CPUs online freezes system* [2]. [1]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883065 [2]: https://lkml.org/lkml/2020/6/11/474 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862751 Title: Hard lockups using microcode releases 20191115 on Intel Whiskey Lake To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1862751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883065] Re: Dell Latitude/Precision: Linux hangs without plugged in power cable
[0.00] microcode: microcode updated early to revision 0xd6, date = 2020-04-23 The system was given to a user, so I won’t be able to test. Maybe this bug is about two issues. 1. Sometimes boot failures (cold boot and from hibernate) with no power cable plugged in. (Yesteday, I wasn’t unable to reproduce it.) 2. SMP(?) issues due to latest microcode updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883065 Title: Dell Latitude/Precision: Linux hangs without plugged in power cable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1883065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883065] Re: Dell Latitude/Precision: Linux hangs without plugged in power cable
It might be related to the latest microcode updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883065 Title: Dell Latitude/Precision: Linux hangs without plugged in power cable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883065] [NEW] Dell Latitude/Precision: Linux hangs without plugged in power cable
Public bug reported: Already present reported in project *dell-sputnik*. (Note, it happened here also without suspend/resume.): 1. https://bugs.launchpad.net/dell-sputnik/+bug/1661741 2. Quote from https://bugs.launchpad.net/dell-sputnik/+bug/1661741/comments/26: > A similar bug affects several Dell laptop models: > - Dell 5480/5488 : > https://bugs.launchpad.net/dell-sputnik/+bug/1866343 > - Dell E5470 : > https://bugs.launchpad.net/dell-sputnik/+bug/1661741 > (Note that the bug https://bugs.launchpad.net/dell-sputnik/+bug/1661741 is not fixed; it has been changed, by error, to fixed. Please, it will be nice if somebody can change the status to "confirmed") > - Dell 7740 : > https://bugs.launchpad.net/dell-sputnik/+bug/1871491 > > I suppose that the bug can also affect Dell precision 7730 After experiencing this already on the Dell Latitude 5480/5488 (https://bugs.launchpad.net/dell-sputnik/+bug/1866343), we have seen this now too with the Dell Precision 3540 (with dedicated AMD graphics card). Without the power cord plugged in, the system started fine, then updating packages, including the Linux kernel, turning the system off, and right back on, it went to GRUB, and GRUB was able to load Linux and initrd, and starting Linux it hung. Num lock key didn’t respond (but also didn’t blink – no idea if this should work), and Ctrl + Alt + Del didn’t work either. So, the system had to be powered off by pressing the power button for some (ten(?)) seconds. Subsequent tries didn’t help, until we remembered the issues with the other device, and plugging in the power cord fixed it. With the power cable unplugged, it didn’t boot. The state of the connected power cable only mattered, when starting the Linux kernel. That means, plugging it in, when GRUB was active, the system booted. Removing the cable, when GRUB was running, Linux hung. I tried to get Linux messages, but `debug nomodeset earlyprintk=efi` didn’t get Linux to output any messages. ### Workarounds ### I was able to get Linux booting by adding either one of the following Linux kernel parameters. 1. `maxcpus=1` (once it started with `maxcpus=2`) 2. `nosmp` 2. `acpi=off` 3. `nolapic` In this state, there was only one CPU online. Trying to bring one more online, the system always froze instantly. echo 1 | sudo tee /sys/devices/system/cpu/cpu1/online (Nothing in pstore either.) (Where maxcpus=2` worked, we were able to bring a third CPU online, but the system froze when trying the fourth.) ### Reproducibilty ### Letting the system sit over night, and trying again in the morning, unfortunately, we did *not* test without a power cable plugged in, as we had an idea to test the non-USB-Type-C power cable. With that the system started. Powering the system off, and unplugging the cable, the system booted without issues. So something changed. We weren’t able to get it into a state, where it doesn’t boot in the last hour, but we would like this investigated, as we are giving these systems to our users. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "Linux messages with `debug maxcpus=2`" https://bugs.launchpad.net/bugs/1883065/+attachment/5382816/+files/morley-maxcpus2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883065 Title: Dell Latitude/Precision: Linux hangs without plugged in power cable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883019] Re: Dell Precision 3540: Starting with acpi=off does not power off
Here are the Linux messages. ** Attachment added: "Linux messages with `acpi=off debug` on the Linux command line" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883019/+attachment/5382802/+files/morley-acpi-off.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883019 Title: Dell Precision 3540: Starting with acpi=off does not power off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883019] [NEW] Dell Precision 3540: Starting with acpi=off does not power off
Public bug reported: With Ubuntu 20.04 (and 18.04) Starting the Dell Precision with `acpi=off` (to debug power cable issue) powering of the system, it halts but does not power off. [1]: https://bugs.launchpad.net/bugs/1661741 [2]: https://bugs.launchpad.net/dell-sputnik/+bug/1871491 ** 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/1883019 Title: Dell Precision 3540: Starting with acpi=off does not power off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
@piscvau, the original report is not about a crash, so your issue is unrelated. Please create a separate report for the crash Ubuntu 20.04. (Also mention there, if it is a system crash/hang? Does the numlock key still work? Can you switch to a virtual console with Ctrl + Alt + F4? Can you still ping the system in the network?) Good luck! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804591] Re: tsc: Fast TSC calibration failed
This is a common problem on AMD Zen systems. Patches were posted to LKML (Linux Kernel Mailing List) in February 2019, but version 2 still needs to rewrite a comment, and v3 wasn’t posted since then. [1]: https://lkml.org/lkml/2019/2/14/1145 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804591 Title: tsc: Fast TSC calibration failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804589] Re: AMD-Vi write error
Just a note, on the Dell OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.20 05/31/2019 (AGESA SummitPI-AM4 1.0.0.7a) I am only seeing the interrupt warning. Performance counters are supported there. [0.870894] pci :00:00.2: AMD-Vi: IOMMU performance counters supported [0.871377] pci :00:00.2: can't derive routing for PCI INT A [0.871732] pci :00:00.2: PCI INT A: not connected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804589 Title: AMD-Vi write error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804589] Re: AMD-Vi write error
I am also seeing this with current Linux (5.7-rc7) on an MSI B350M MORTAR and a Dell OptiPlex 5055. Both are AMD Ryzen systems, so this seems to affect all of those. The IOMMU subsystem maintainer responded to report this issue to the mainboard vendor, so they fix the firmware [1]. Everybody experiencing this, please contact the mainboard vendor to fix this. I already did, and the more contact them, the higher it will rise in their ticketing system. [1]: https://lists.linuxfoundation.org/pipermail/iommu/2018-July/028925.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804589 Title: AMD-Vi write error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804589] Re: AMD-Vi write error
It’d be great if Canonical also used their Dell and AMD contacts to get this fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804589 Title: AMD-Vi write error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878972] [NEW] Package installation fails if TMPDIR is automounted directory
Public bug reported: The update from Ubuntu 19.04 to 19.10 *and* 19.10 to 20.04 failed with the message (for 20.04 upgrade) below. […] Unpacking autofs (5.1.6-2) over (5.1.5-1ubuntu1) ... dpkg-deb: error: failed to read archive '/scratch/local/apt-dpkg-install-UI1Lh9/71-autofs_5.1.6-2_ppc64el.deb': No such file or directory dpkg: error processing archive /scratch/local/apt-dpkg-install-UI1Lh9/71-autofs_5.1.6-2_ppc64el.deb (--unpack): dpkg-deb --fsys-tarfile subprocess returned error exit status 2 update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Preparing to unpack .../72-libattr1_1%3a2.4.48-5_ppc64el.deb ... […] The reason seems to be that TMPDIR points to `/scratch/local` which is automounted on our systems. ** Affects: autofs (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/1878972 Title: Package installation fails if TMPDIR is automounted directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1878972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
@magean, I believe you are having a different issue here, so please create a separate bug report, and, as you reproduced this with Linux 5.4 (also try https://kernel.ubuntu.com/~kernel-ppa/), contact linux- p...@vger.kernel.org and the PCI subsystem maintainers directly, and attach `dmesg` to your message for starters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
@ads-launchpad, that looks like a separate issue. Please make a new report (especially as this is in the project(?)/category(?) *dell- sputnik* in Launchpad, and also upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57
[Sorry, I wasn’t subscribed to the notifications.] @hui.wang, your attached firmware, what version is that? $ md5sum sof-icl.ri 2ca373e6254b0e9b37439f7a31984973 /dev/shm/sof-icl.ri @adamfubuntu, do you still have the problem *without* `dsp_driver=0` on an up-to-date Ubuntu 19.10 with Linux 5.5-rc6? ** Bug watch added: Red Hat Bugzilla #1772498 https://bugzilla.redhat.com/show_bug.cgi?id=1772498 ** Bug watch added: github.com/thesofproject/sof/issues #2126 https://github.com/thesofproject/sof/issues/2126 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856366 Title: PCI/internal sound card not detected on a Swift SF314-57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57
And in Clear Linux: https://community.clearlinux.org/t/new-installation- no-sound-swift-5-i7-1065gt-iris-plus/2407/14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856366 Title: PCI/internal sound card not detected on a Swift SF314-57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57
A Fedora user reported the same issue in https://bugzilla.redhat.com/show_bug.cgi?id=1772498#c16, and the created an upstream GitHub issue https://github.com/thesofproject/sof/issues/2126. Please update the meta-information of this bug accordingly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856366 Title: PCI/internal sound card not detected on a Swift SF314-57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738774] Re: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display
This is still an issue, and due to HiDPI getting more and more common, Ubuntu should really look into this to give users a good experience with the setups. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738774 Title: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1738774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488620] Re: Add LZ4 support to initramfs-tools
Can this be closed/tagged as fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488620 Title: Add LZ4 support to initramfs-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1488620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856366] Re: PCI/internal sound card not detected
Off-topic: Adam, you should also install the other firmware files like for graphics. ``` [1.029518] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.029567] i915 :00:02.0: Direct firmware load for i915/icl_dmc_ver1_09.bin failed with error -2 [1.029569] i915 :00:02.0: Failed to load DMC firmware i915/icl_dmc_ver1_09.bin. Disabling runtime power management. [1.029569] i915 :00:02.0: DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ``` `apt install linux-firmware` should fix that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856366 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856366] Re: PCI/internal sound card not detected
It should work out of the box without the user having to specify any options. 1. There does not seem to be an Ubuntu package for Sound Open Firmware yet. Adam, does the pre-built firmware file from https://github.com/thesofproject/sof/releases work? Linux 5.3, 5.4, 5.5-rc1? 2. With the firmware file installed, does Linux 5.3 work with `dsp_driver=0`? Please attach the Linux messages from the non-working and working boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856366 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845548] Re: implicitclass crashed with SIGABRT in __malloc_assert()
Upstream issue: https://github.com/OpenPrinting/cups-filters/issues/162 ** Bug watch added: github.com/OpenPrinting/cups-filters/issues #162 https://github.com/OpenPrinting/cups-filters/issues/162 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845548 Title: implicitclass crashed with SIGABRT in __malloc_assert() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1845548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845548] Re: implicitclass crashed with SIGABRT in __malloc_assert()
The same issues exists with cups-filters 1.25.6 in Debian Sid/unstable. >From `/var/log/cups/error_log`: ``` D [01/Oct/2019:11:15:54 +0200] [Job 168] Removing cups-browsed-dest-printer option from argumentsmalloc.c:2389: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)\' failed. D [01/Oct/2019:11:15:54 +0200] [Job 168] PID 14123 (/usr/lib/cups/filter/pdftopdf) exited with no errors. D [01/Oct/2019:11:15:54 +0200] [Job 168] PID 14124 (/usr/lib/cups/backend/implicitclass) crashed on signal 6. D [01/Oct/2019:11:15:54 +0200] [Job 168] Hint: Try setting the LogLevel to "debug" to find out more. D [01/Oct/2019:11:15:54 +0200] [Job 168] Backend returned status -134 (crashed) ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845548 Title: implicitclass crashed with SIGABRT in __malloc_assert() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1845548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
@andre-miras, we do not experience the problem with Ubuntu 18.10(?) and 19.04 anymore. Please try to update, or test these releases. No idea, what the cause and solution was in the end. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784349] Re: SEGV during startup on Power 8 system
I tested this yesterday with Ubuntu 18.10, and Firefox did crash anymore. So this can be tagged as solved. I do not know the first fixed version though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784349 Title: SEGV during startup on Power 8 system To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1784349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
On a ppc64le system I verified, that the version in cosmic-proposed fixes this issue. A big thanks to everyone, fixing this so quickly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
It worked with bionic-proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
On 25.03.19 07:53, Christian Ehrhardt wrote: > @Paul - you were so active before - thanks for checking the PPAs and > all that. But I still have no NFS server uncoorperative enough to > trigger this; Could you for the (final) SRU verification as asked on > the comments #18 and #19 confirm that this works in your setup with > the changes that are in proposed [1]. Aren’t they identical to the packages in your PPA? Anyway, I can test the proposed packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
I checked, that your packages fix the problem on both Bionic and Cosmic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
@Paul - please test the PPA on Disco (19.04) [1] and let me know if it works fine. I just tested this. With autofs 5.1.2-4ubuntu1 it does *not* work, with autofs 5.1.2-4ubuntu2~ppa1 it does work. [1]: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1818121-autofs- nfs4.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
Ubuntu Disco is 19.04, right? I’ll try to test this properly today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
Our NFS server is not a Ubuntu system. It’s basically an LFS based set- up [1]. The autofs client installed on our system has no trouble connecting to the server, so some minor detail seems to be different, that it doesn’t work with the Ubuntu client out of the box. [1]: https://github.molgen.mpg.de/mariux64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
Our NFS server does not advertise/support NFSv3 for example. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
Thank you for trying to reproduce the issue, and sorry for missing out
information. In this case, due to NFS 4.2 issues, we have specified the
exact NFS version.
joey -vers=4.0 claptrap:/amd/claptrap/2/home/edv/joey
Bisecting the fix in autofs 5.1.4, results in the commit aa1f4321
(autofs-5.1.3 - handle additional nfs versions in mount_nfs.c).
commit aa1f432180f3878c303088def8d647f1bd50b10b (refs/bisect/fixed)
Author: Ian Kent
Date: Thu Oct 19 08:48:44 2017 +0800
autofs-5.1.3 - handle additional nfs versions in mount_nfs.c
Since NFSv4 can now have a subversion it needs to be allowed for.
It's enough to check for an options string starting with "vers=4" or
"nfsvers=4" because it's used only to set a flag used for special
casing the availibility probe for any NFS version 4 version.
Signed-off-by: Ian Kent
diff --git a/CHANGELOG b/CHANGELOG
index 2da2cdc..3a1e4a6 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -35,6 +35,7 @@ xx/xx/2017 autofs-5.1.4
- make map source reference message debug only.
- improve description of mount_nfs_default_protocol.
- the port option should not behave like nobind option.
+- handle additional nfs versions in mount_nfs.c.
24/05/2017 autofs-5.1.3
===
diff --git a/modules/mount_nfs.c b/modules/mount_nfs.c
index 5245d96..d3ebd92 100644
--- a/modules/mount_nfs.c
+++ b/modules/mount_nfs.c
@@ -147,8 +147,9 @@ int mount_mount(struct autofs_point *ap, const char *root,
const char *name, int
} else if (_strncmp("use-weight-only", cp, o_len) == 0)
{
flags |= MOUNT_FLAG_USE_WEIGHT_ONLY;
} else {
- if (_strncmp("vers=4", cp, o_len) == 0 ||
- _strncmp("nfsvers=4", cp, o_len) == 0)
+ /* Is any version of NFSv4 in the options */
+ if (_strncmp("vers=4", cp, 6) == 0 ||
+ _strncmp("nfsvers=4", cp, 9) == 0)
vers = NFS4_VERS_MASK | TCP_SUPPORTED;
else if (_strncmp("vers=3", cp, o_len) == 0 ||
_strncmp("nfsvers=3", cp, o_len) == 0)
{
Reading the commit message and looking at the change, it makes sense,
that this fixes the issue. Could you please apply this to the package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818121
Title:
NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no
hosts available
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
** Summary changed: - NFSv4 shares are not mounted: mount(nfs): no hosts available + NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818121] [NEW] NFSv4 shares are not mounted: mount(nfs): no hosts available
Public bug reported:
With Ubuntu 18.10 and autofs 5.1.2-4ubuntu1, mounting NFSv4 shares does
not work. Directly mounting them with `mount.nfs` works.
```
Feb 28 18:08:30 nfsclient automount[22978]: expire_proc: exp_proc =
131147807650128 path /home_mariux
Feb 28 18:08:30 nfsclient automount[22978]: expire_cleanup: got thid
131147807650128 path /home_mariux stat 0
Feb 28 18:08:30 nfsclient automount[22978]: expire_cleanup: sigchld: exp
131147807650128 finished, switching from 2 to 1
Feb 28 18:08:30 nfsclient automount[22978]: st_ready: st_ready(): state = 2
path /home_mariux
Feb 28 18:08:32 nfsclient automount[22978]: handle_packet: type = 3
Feb 28 18:08:32 nfsclient automount[22978]: handle_packet_missing_indirect:
token 46, name joey, request pid 28647
Feb 28 18:08:32 nfsclient automount[22978]: attempting to mount entry
/home_mariux/joey
Feb 28 18:08:32 nfsclient automount[22978]: lookup_mount: lookup(file): looking
up joey
Feb 28 18:08:32 nfsclient automount[22978]: lookup_mount: lookup(file): joey ->
claptrap:/amd/claptrap/2/home/edv/joey
Feb 28 18:08:32 nfsclient automount[22978]: parse_mount: parse(sun): expanded
entry: claptrap:/amd/claptrap/2/home/edv/joey
Feb 28 18:08:32 nfsclient automount[22978]: parse_mount: parse(sun): gathered
options: nosuid
Feb 28 18:08:32 nfsclient automount[22978]: parse_mount: parse(sun):
dequote("claptrap:/amd/claptrap/2/home/edv/joey") ->
claptrap:/amd/claptrap/2/home/edv/bucz
Feb 28 18:08:32 nfsclient automount[22978]: parse_mount: parse(sun): core of
entry: options=nosuid, loc=claptrap:/amd/claptrap/2/home/edv/joey
Feb 28 18:08:32 nfsclient automount[22978]: sun_mount: parse(sun): mounting
root /home_mariux, mountpoint joey, what
claptrap:/amd/claptrap/2/home/edv/joey, f
Feb 28 18:08:32 nfsclient automount[22978]: mount_mount: mount(nfs):
root=/home_mariux name=joey what=claptrap:/amd/claptrap/2/home/edv/joey,
fstype=nfs, opti
Feb 28 18:08:32 nfsclient automount[22978]: mount_mount: mount(nfs): nfs
options="nosuid", nobind=0, nosymlink=0, ro=0
Feb 28 18:08:32 nfsclient automount[22978]: get_nfs_info: called with host
claptrap(141.14.16.132) proto 6 version 0x30
Feb 28 18:08:32 nfsclient automount[22978]: get_nfs_info: called with host
claptrap(141.14.16.132) proto 17 version 0x30
Feb 28 18:08:32 nfsclient automount[22978]: mount(nfs): no hosts available
Feb 28 18:08:32 nfsclient automount[22978]: dev_ioctl_send_fail: token = 46
Feb 28 18:08:32 nfsclient automount[22978]: failed to mount /home_mariux/joey
Feb 28 18:08:32 nfsclient automount[22978]: st_readmap: state 1 path
/home_mariux
Feb 28 18:08:32 nfsclient automount[22978]: handle_packet: type = 3
Feb 28 18:08:32 nfsclient automount[22978]: handle_packet_missing_indirect:
token 47, name joey, request pid 28647
Feb 28 18:08:32 nfsclient automount[22978]: dev_ioctl_send_fail: token = 47
Feb 28 18:08:32 nfsclient automount[22978]: re-reading map for /home_mariux
Feb 28 18:08:32 nfsclient automount[22978]: lookup_nss_read_map: reading map
file /etc/automount/auto.home
Feb 28 18:08:32 nfsclient automount[22978]: do_init: parse(sun): init gathered
global options: nosuid
Feb 28 18:08:32 nfsclient automount[22978]: st_ready: st_ready(): state = 4
path /home_mariux
```
** Affects: autofs (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/1818121
Title:
NFSv4 shares are not mounted: mount(nfs): no hosts available
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
