[Bug 1854895] Re: touchpad stopped working after the update
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Had the same issue on a Dell Inspiron 15. Downgrading kernel to 4.15.0-70 solved it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854895 Title: touchpad stopped working after the update To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1854895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello You-Sheng, Thanks for responding. I tried "hpet=disable" on a boot for both -70 and -72. No change. Kernel -72 still just stops, but -70 boots OK. As for the dmesg, I don't seem to be able to get any logging / messaging for -72. The only reference I can find for it is in the dpkg log when it was installed back on 4-Dec-2019. It's as if it does not even start. For what it's worth I've attached the dmesg for the -70 boot with "hpet=disable". ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+attachment/5312469/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821849] Re: LibreOffice Impress 6.2.2.2 Embedded Video Problem
This problem has been fixed for some time now and I no longer get a white screen at the start of a video. I currently have LibreOffice 6.4.3.2 and it works GREAT. Thanks for all the improvements that have been made. ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821849 Title: LibreOffice Impress 6.2.2.2 Embedded Video Problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1821849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856422] Re: always call mokutil with --timeout -1 when enrolling dkms keys
This bug was fixed in the package shim-signed - 1.40 --- shim-signed (1.40) focal; urgency=medium * Pass --timeout -1 to mokutil so that users don't end up with broken systems by missing MokManager on reboot after install. LP: #1856422. * Add a versioned dependency on the mokutil that introduces --timeout. -- Steve Langasek Sat, 14 Dec 2019 20:26:42 -0800 ** Changed in: shim-signed (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856422 Title: always call mokutil with --timeout -1 when enrolling dkms keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1856422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856441] [NEW] installation completed but grub failed to install
Public bug reported: installation completed but grub failed to install ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 11:18:59 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856441 Title: installation completed but grub failed to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1856441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856440] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856440 Title: cpufreq: no or unknown cpufreq driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856440] [NEW] cpufreq: no or unknown cpufreq driver
Public bug reported: Not sure where this goes, but no cpufreq driver is available in 19.10 or 20.04 on AMD CPUs. I'm not sure why this is happening, but no cpufreq driver gets loaded. Output of cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. Output of cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU CPUs which run at the same hardware frequency: Not Available CPUs which need to have their frequency coordinated by software: Not Available maximum transition latency: Cannot determine or is not supported. Not Available available cpufreq governors: Not Available Unable to determine current policy current CPU frequency: Unable to call hardware current CPU frequency: Unable to call to kernel boost state support: Supported: yes Active: yes Boost States: 3 Total States: 8 Pstate-Pb0: 3300MHz (boost state) Pstate-Pb1: 3100MHz (boost state) Pstate-Pb2: 2800MHz (boost state) Pstate-P0: 2600MHz Pstate-P1: 2200MHz Pstate-P2: 1800MHz Pstate-P3: 1400MHz Pstate-P4: 1200MHz Issue is present in 19.10. Upgraded to 20.04 to see if issue persists and it does. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.3.0-24-lowlatency 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: erich 3958 F pulseaudio /dev/snd/controlC3: erich 3958 F pulseaudio /dev/snd/controlC1: erich 3958 F pulseaudio /dev/snd/controlC0: erich 3958 F pulseaudio CurrentDesktop: GNOME Date: Sat Dec 14 20:59:10 2019 InstallationDate: Installed on 2019-02-12 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) MachineType: Dell Inc. Inspiron 5576 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-lowlatency root=UUID=cbf0a967-a34d-43b1-a42e-993daa70b8f7 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-lowlatency N/A linux-backports-modules-5.3.0-24-lowlatency N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-15 (0 days ago) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0HJ6MY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd01/29/2018:svnDellInc.:pnInspiron5576:pvr1.0.7:rvnDellInc.:rn0HJ6MY:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5576 dmi.product.sku: 07E2 dmi.product.version: 1.0.7 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan focal ** Summary changed: - No cpufreq driver available + cpufreq: no or unknown cpufreq driver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856440 Title: cpufreq: no or unknown cpufreq driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856422] Re: always call mokutil with --timeout -1 when enrolling dkms keys
** Description changed: [SRU Justification] The version of MokManager currently in all releases supports a MokTimeout variable, which can be set with mokutil --timeout, to control how long MokManager waits for input instead of having a hard-coded timeout of 10 seconds. If the timeout is reached on boot with no input, MokManager clears the MOK requests and passes control back to shim, which falls back to booting the OS. So if you miss seeing MokManager on boot, you have to restart the key enrollment process from the OS and reboot again. When we are invoking mokutil automatically on behalf of the user as part of key generation for dkms modules, we should disable the timeout. We should never leave the user with broken dkms modules on the system because they were looking away from the console at the wrong point in time during a reboot. [Test case] 1. On a system with SecureBoot enabled, install the virtualbox-dkms package. 2. Set a password to use for MOK enrollment. 3. Reboot. 4. Observe that there is a countdown on MokManager. Let the timer expire. 5. Install the shim-signed package from -proposed. 6. Purge the virtualbox-dkms and dkms packages. 7. sudo rm -rf /var/lib/shim-signed. 8. Repeat steps 1 through 3. 9. Observe that there is no countdown on MokManager, and that it waits indefinitely for input (confirm that this is the case by sitting at the screen for at least 1 minute). + + [Regression potential] + If a wrong version of mokutil is called with this additional argument and doesn't support it and as a result mokutil fails, this could result in users not having their MOK enrolled who otherwise would have. + + This prevents systems which have a pending MOK enrollment due to dkms + from rebooting unattended back to Ubuntu. If anyone is automating + configuration of dkms/shim, during an install or otherwise, and + expecting the system to reboot back to Ubuntu without intervention at + the console, this will stop working. However, such a system is broken + with respect to dkms modules and SecureBoot anyway; the user should + either not install dkms modules, or plan for handling the MOK request at + the console (serial console or otherwise) on the next reboot. + + If the user does not have console access to the system but does have + power access, they can still bypass MokManager by power cycling the + system, again giving them a system which is booted but does not properly + support the dkms modules under SecureBoot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856422 Title: always call mokutil with --timeout -1 when enrolling dkms keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1856422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
"I have no internal mic detected.", that is because the internal mic connects to PCH instead of codec, so it needs the sof driver to enable the internal mic. Please have a try with latest mainline kernel, and upload the dmesg, the dmesg will tell us if your machine need sof driver or not. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc1/ "When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone.", that should not happen. when you plug a headset, the headphone should be the output device, and the mic on the headset should be in the input device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856439] [NEW] Add "Set Application as Default" to the "Open with Other Application" popup.
Public bug reported: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) Ability to set selected application as default. 4) No "Set Application as Default" on "Select Application" popup. ** Affects: gnome-control-center (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/1856439 Title: Add "Set Application as Default" to the "Open with Other Application" popup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1856439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856422] Re: always call mokutil with --timeout -1 when enrolling dkms keys
** Changed in: shim-signed (Ubuntu Bionic) Status: New => In Progress ** Changed in: shim-signed (Ubuntu) Status: New => Fix Committed ** Description changed: - The version of MokManager currently in xenial-updates and later supports - a MokTimeout variable, which can be set with mokutil --timeout, to - control how long MokManager waits for input instead of having a hard- - coded timeout of 10 seconds. + [SRU Justification] + The version of MokManager currently in all releases supports a MokTimeout variable, which can be set with mokutil --timeout, to control how long MokManager waits for input instead of having a hard-coded timeout of 10 seconds. If the timeout is reached on boot with no input, MokManager clears the MOK requests and passes control back to shim, which falls back to booting the OS. So if you miss seeing MokManager on boot, you have to restart the key enrollment process from the OS and reboot again. When we are invoking mokutil automatically on behalf of the user as part of key generation for dkms modules, we should disable the timeout. We should never leave the user with broken dkms modules on the system because they were looking away from the console at the wrong point in time during a reboot. + + [Test case] + 1. On a system with SecureBoot enabled, install the virtualbox-dkms package. + 2. Set a password to use for MOK enrollment. + 3. Reboot. + 4. Observe that there is a countdown on MokManager. Let the timer expire. + 5. Install the shim-signed package from -proposed. + 6. Purge the virtualbox-dkms and dkms packages. + 7. sudo rm -rf /var/lib/shim-signed. + 8. Repeat steps 1 through 3. + 9. Observe that there is no countdown on MokManager, and that it waits indefinitely for input (confirm that this is the case by sitting at the screen for at least 1 minute). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856422 Title: always call mokutil with --timeout -1 when enrolling dkms keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1856422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856438] [NEW] auto suggest previously used commands
Public bug reported: 1) Ubuntu 19.10 2) 3.34.2-1ubuntu1 3) If a user types part of a previously used command, display the suggested command. A user could press the right arrow key to accept the suggested command. 4) No auto suggestion. ** Affects: gnome-terminal (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/1856438 Title: auto suggest previously used commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1856438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856433] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1856433 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856433 Title: do_IRQ: 1.55 No irq handler for vector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856436] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1856436 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856436 Title: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190703/dspkginit-438) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856437] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1856437 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856437 Title: Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380796] Re: LibreOficeWriter does not spellcheck Russian
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380796 Title: LibreOficeWriter does not spellcheck Russian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1380796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279060] Re: MIssing voicemail info for French provider Free
[Expired for mobile-broadband-provider-info (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mobile-broadband-provider-info (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279060 Title: MIssing voicemail info for French provider Free To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1279060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845617] Re: Bluetooth service stop working
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845617 Title: Bluetooth service stop working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827203] Re: 2.02+dfsg1-12ubuntu2: terminal not initialised in GRUB_TIMEOUT_STYLE=menu
[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: grub2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827203 Title: 2.02+dfsg1-12ubuntu2: terminal not initialised in GRUB_TIMEOUT_STYLE=menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1827203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825385] Re: snapd 2.38+18.10 ADT test failure with linux-kvm 4.18.0-1010.10 (because of missing 'go' package)
[Expired for snapd because there has been no activity for 60 days.] ** Changed in: snapd Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825385 Title: snapd 2.38+18.10 ADT test failure with linux-kvm 4.18.0-1010.10 (because of missing 'go' package) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1825385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841384] Re: snapd crashed with SIGSEGV
[Expired for snapd because there has been no activity for 60 days.] ** Changed in: snapd Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841384 Title: snapd crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1841384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847831] Re: pppp
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847831 Title: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825385] Re: snapd 2.38+18.10 ADT test failure with linux-kvm 4.18.0-1010.10 (because of missing 'go' package)
[Expired for snapd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: snapd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825385 Title: snapd 2.38+18.10 ADT test failure with linux-kvm 4.18.0-1010.10 (because of missing 'go' package) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1825385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841384] Re: snapd crashed with SIGSEGV
[Expired for snapd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: snapd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841384 Title: snapd crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1841384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856431] Re: Snap and dangling symlinks
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1856431/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856431 Title: Snap and dangling symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1856431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825528] Re: package shim-signed 1.33.1~16.04.5+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.] ** Changed in: shim-signed (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825528 Title: package shim-signed 1.33.1~16.04.5+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1825528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856437] [NEW] Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline
Public bug reported: 1) Ubuntu 19.10 2) unknown 3) no error. 4) error in log app. ** 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/1856437 Title: Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856436] [NEW] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190703/dspkginit-438)
Public bug reported: 1) Ubuntu 19.10 2) unknown 3) no error. 4) no error log app. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "log" https://bugs.launchpad.net/bugs/1856436/+attachment/5312446/+files/log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856436 Title: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190703/dspkginit-438) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856433] Re: do_IRQ: 1.55 No irq handler for vector
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856433 Title: do_IRQ: 1.55 No irq handler for vector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856434] [NEW] blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Public bug reported: 1) Ubuntu 19.10 2) unknown 3) no error 4) error in log app. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856434 Title: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856434] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1856434 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856434 Title: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856433] [NEW] do_IRQ: 1.55 No irq handler for vector
Public bug reported: 1) Ubuntu 19.10 2) system 3) no error. 4) Error in log app. ** Affects: ubuntu Importance: Undecided Status: New ** Package changed: at-spi2-core (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856433 Title: do_IRQ: 1.55 No irq handler for vector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1856433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856408] Re: zfs-initramfs needs to set FRAMEBUFFER=y
Should it set KEYMAP=y too, like cryptsetup does? I've created a PR upstream and done some light testing: https://github.com/zfsonlinux/zfs/pull/9723 Are you able to confirm that this fixes the issue wherever you were seeing it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856408 Title: zfs-initramfs needs to set FRAMEBUFFER=y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856432] [NEW] Unable to register client with session manager
Public bug reported: 1) Ubuntu 19.10 2) unknown 3) No error. 4) Error in Ubuntu log: Sender: at-spi2-registr Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client ** Affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New ** Description changed: 1) Ubuntu 19.10 2) unknown 3) No error. 4) Error in Ubuntu log: - Failed to register client: - GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to - register client + Sender: at-spi2-registr + Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856432 Title: Unable to register client with session manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1856432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856431] [NEW] Snap and dangling symlinks
Public bug reported: I'm working on Ubuntu 18.04.03, x86_64, fully patched. The Snap package program seems to have a lot of dangling links: $ sudo symlinks -r / | grep dangling dangling: /home/jwalton/snap/gnome-system-monitor/111/.config/gtk-3.0/settings.ini -> /home/jwalton/.config/gtk-3.0/settings.ini dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/themes -> /snap/gnome-system-monitor/111/data-dir/themes dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/DMZ-White/index.theme -> /snap/gnome-system-monitor/111/data-dir/icons/DMZ-White/index.theme dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/DMZ-White/cursor.theme -> /snap/gnome-system-monitor/111/data-dir/icons/DMZ-White/cursor.theme dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/DMZ-White/cursors -> /snap/gnome-system-monitor/111/data-dir/icons/DMZ-White/cursors dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/22x22 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/22x22 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/24x24 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/24x24 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/32x32 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/32x32 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/16x16 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/16x16 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/36x36 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/36x36 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/192x192 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/192x192 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/512x512 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/512x512 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/256x256 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/256x256 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/96x96 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/96x96 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/index.theme -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/index.theme dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/128x128 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/128x128 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/72x72 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/72x72 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/64x64 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/64x64 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/48x48 -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/48x48 dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/symbolic -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/symbolic dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/hicolor/scalable -> /snap/gnome-system-monitor/111/data-dir/icons/hicolor/scalable dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/Papirus-Adapta-Nokto-Maia/index.theme -> /snap/gnome-system-monitor/111/data-dir/icons/Papirus-Adapta-Nokto-Maia/index.theme dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/Papirus-Adapta-Maia/index.theme -> /snap/gnome-system-monitor/111/data-dir/icons/Papirus-Adapta-Maia/index.theme dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/DMZ-Black/index.theme -> /snap/gnome-system-monitor/111/data-dir/icons/DMZ-Black/index.theme dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/DMZ-Black/cursor.theme -> /snap/gnome-system-monitor/111/data-dir/icons/DMZ-Black/cursor.theme dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/DMZ-Black/cursors -> /snap/gnome-system-monitor/111/data-dir/icons/DMZ-Black/cursors dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/Suru/index.theme -> /snap/gnome-system-monitor/111/data-dir/icons/Suru/index.theme dangling: /home/jwalton/snap/gnome-system-monitor/111/.local/share/icons/communitheme/index.theme -> /snap/gnome-system-monitor/111/data-dir/icons/communitheme/index.theme dangling: /home/jwalton/snap/gnome-system-monitor/111/.themes -> /snap/gnome-system-monitor/111/data-dir/themes dangling: /home/jwalton/snap/gnome-system-monitor/common/.cache/immodules/im-ipa.so -> /snap/gnome-system-monitor/111/gnome-platform/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-ipa.so dangling:
[Bug 1856430] [NEW] Gparted and dangling symlinks
Public bug reported: I'm working on Ubuntu 18.04.03, x86_64, fully patched. Running the symlinks utility on the image shows an excessive number of dangling symlinks: $ sudo symlinks -r /usr | grep dangling dangling: /usr/share/omf/gparted/gparted-ru.omf -> ../../omf-langpack/gparted/gparted-ru.omf dangling: /usr/share/omf/gparted/gparted-it.omf -> ../../omf-langpack/gparted/gparted-it.omf dangling: /usr/share/omf/gparted/gparted...@latin.omf -> ../../omf-langpack/gparted/gparted...@latin.omf dangling: /usr/share/omf/gparted/gparted-th.omf -> ../../omf-langpack/gparted/gparted-th.omf dangling: /usr/share/omf/gparted/gparted-cs.omf -> ../../omf-langpack/gparted/gparted-cs.omf dangling: /usr/share/omf/gparted/gparted-sv.omf -> ../../omf-langpack/gparted/gparted-sv.omf dangling: /usr/share/omf/gparted/gparted-el.omf -> ../../omf-langpack/gparted/gparted-el.omf dangling: /usr/share/omf/gparted/gparted-pt_BR.omf -> ../../omf-langpack/gparted/gparted-pt_BR.omf dangling: /usr/share/omf/gparted/gparted-gd.omf -> ../../omf-langpack/gparted/gparted-gd.omf dangling: /usr/share/omf/gparted/gparted-sl.omf -> ../../omf-langpack/gparted/gparted-sl.omf dangling: /usr/share/omf/gparted/gparted-te.omf -> ../../omf-langpack/gparted/gparted-te.omf dangling: /usr/share/omf/gparted/gparted-fr.omf -> ../../omf-langpack/gparted/gparted-fr.omf dangling: /usr/share/omf/gparted/gparted-es.omf -> ../../omf-langpack/gparted/gparted-es.omf dangling: /usr/share/omf/gparted/gparted-ro.omf -> ../../omf-langpack/gparted/gparted-ro.omf dangling: /usr/share/omf/gparted/gparted-sr.omf -> ../../omf-langpack/gparted/gparted-sr.omf dangling: /usr/share/omf/gparted/gparted-de.omf -> ../../omf-langpack/gparted/gparted-de.omf ** Affects: gparted (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/1856430 Title: Gparted and dangling symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1856430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856429] [NEW] Error creating IO channel for /proc/self/mountinfo: Permission denied (g-file-error-quark, 2)
Public bug reported: 1) Ubuntu 19.10 2) unknown 3) no error 4) error in log file. ** 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/1856429 Title: Error creating IO channel for /proc/self/mountinfo: Permission denied (g-file-error-quark, 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1856429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856428] [NEW] Raise minimum key requirements to 2k and disable TLS 1.0 and 1.1
Public bug reported: Raise minimum key requirements to 2k and disable TLS 1.0 and 1.1 As par of focal commitment, we shall raise minimum key requirements and disable obsolete protocols by default. Users can override this behaviour with a config file. ** Affects: gnutls28 (Ubuntu) Importance: Undecided Status: New ** Affects: nss (Ubuntu) Importance: Undecided Status: New ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Also affects: openssl (Ubuntu) Importance: Undecided Status: New ** Also affects: nss (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/1856428 Title: Raise minimum key requirements to 2k and disable TLS 1.0 and 1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1856428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851427] Re: Consider updating GNUTLS for TLSv1.3 and unified config w/Focal
Bionic at point-zero shipped with two OpenSSL series the legacy 1.0.2 and non-lts 1.1.0. We made the call that 1.1.0 series is unsupportable over the 10 years, and thus chose (as one time only event) upgrade to 1.1.1 series. It was primarily driven by supportability and maintenance concern. Note, many applications in bionic, despite using 1.1.1 series do not support TLSv1.3. And many use 1.02. We do not currently have supportability concerns of the GnuTLS 3.5 in bionic over the bionic lifespan. Thus the same premise as to why we went through the painful process of OpenSSL backport do not stand. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851427 Title: Consider updating GNUTLS for TLSv1.3 and unified config w/Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1851427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856427] [NEW] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
Public bug reported: 1) Ubuntu 19.10 2) sensors version 3.5.0 with libsensors version 3.5.0 3) No error. 4) Error in logs. ** Affects: lm-sensors (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/1856427 Title: k8temp :00:18.3: Temperature readouts might be wrong - check erratum #141 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1856427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856426] [NEW] k8temp 0000:00:18.3: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
Public bug reported: 1) Ubuntu 19.10 2) sensors version 3.5.0 with libsensors version 3.5.0 3) No error. 4) Error in logs. ** Affects: lm-sensors (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/1856426 Title: k8temp :00:18.3: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1856426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856425] [NEW] Gnome Shell crashs sporadically
Public bug reported: Ubuntu 19.10, all updated, sporadically (both in terms of timing and as an app I use), the gnome session crashs and re-opened by itself after about 1 second. However, closing the apps I was using, so as to lose everything. Now, just happened I saved all the logs via gnome logs, of 2 episodes where the problem occurred. It happened at a distance of not even a quarter of an hour. It's happened at 16.35 and 16.48. In attached this log. I can see only "bluetoothd: Failed to set mode: Blocked through rfkill (0x12)" of relevant, in both times, but I don't know. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "log.txt" https://bugs.launchpad.net/bugs/1856425/+attachment/5312444/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856425 Title: Gnome Shell crashs sporadically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856420] Re: intel comet lake ethernet device not recognized
Fixed in linux kernel 5.0.0-37.40 released for 18.04 ** Changed in: linux-signed-hwe (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856420 Title: intel comet lake ethernet device not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1856420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856424] [NEW] please add smbios module to the signed grub2 images
Public bug reported: smbios is a new module available in grub2 upstream master, merged shortly after 2.04 release. It allows reading values from various SMBIOS tables to allow detecting vendor, make, model among with other smbios defined handles. In terms of userspace, it can be compared to dmidecode. The premise to include this module in the EFI prebuild images is to allow automatic selection of appropriate kernel and kernel option at boot time of certified or specilized hardware. For example: - allowing to choose linux-hwe kernel on newer generation (query handle 0x37, dmi type 4 Processor information) - allowing to choose linux-oem kernel on OEM certified hardware (query handle 0x1, DMI type 1, Manufactuere / serial number / sku number) - allowing to choose correct DTB for arm64 Laptops The grub module itself is fairly trivial, and basically dumps memory, processes it into various data types, optionally storing them in a variable thus allowing making scripting decisions based on them (i.e. setting the 'default' menuetry) This is a request to review this module for inclusion in the prebuilt UEFI signed images of grub. As a patch: http://git.savannah.gnu.org/cgit/grub.git/commit/?id=688023cd0ac4c985fd0e2ec477fcf1ec33a0e49c Main Files: http://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/commands/smbios.c?id=688023cd0ac4c985fd0e2ec477fcf1ec33a0e49c http://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/commands/i386/pc/smbios.c?id=688023cd0ac4c985fd0e2ec477fcf1ec33a0e49c http://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/commands/efi/smbios.c?id=688023cd0ac4c985fd0e2ec477fcf1ec33a0e49c ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856424 Title: please add smbios module to the signed grub2 images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1856424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856424] Re: please add smbios module to the signed grub2 images
Alternative measures avoiding using this module, would be to attempt a kexec from initrd to the right kernel flavour. Which may increase boot time a little bit, but should otherwise allow similar levels of detection. Note that signed kexec is available these days. ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856424 Title: please add smbios module to the signed grub2 images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1856424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856422] Re: always call mokutil with --timeout -1 when enrolling dkms keys
** Merge proposal linked: https://code.launchpad.net/~ubuntu-installer/ubiquity/+git/ubiquity/+merge/376815 ** Merge proposal linked: https://code.launchpad.net/~ubuntu-installer/ubiquity/+git/ubiquity/+merge/376816 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856422 Title: always call mokutil with --timeout -1 when enrolling dkms keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1856422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856422] [NEW] always call mokutil with --timeout -1 when enrolling dkms keys
Public bug reported: The version of MokManager currently in xenial-updates and later supports a MokTimeout variable, which can be set with mokutil --timeout, to control how long MokManager waits for input instead of having a hard- coded timeout of 10 seconds. If the timeout is reached on boot with no input, MokManager clears the MOK requests and passes control back to shim, which falls back to booting the OS. So if you miss seeing MokManager on boot, you have to restart the key enrollment process from the OS and reboot again. When we are invoking mokutil automatically on behalf of the user as part of key generation for dkms modules, we should disable the timeout. We should never leave the user with broken dkms modules on the system because they were looking away from the console at the wrong point in time during a reboot. ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Affects: shim-signed (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: shim-signed (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu Eoan) Importance: Undecided Status: Won't Fix ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: shim-signed (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: shim-signed (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: - The version of MokManager currently in all releases supports a - MokTimeout variable, which can be set with mokutil --timeout, to control - how long MokManager waits for input instead of having a hard-coded - timeout of 10 seconds. + The version of MokManager currently in xenial-updates and later supports + a MokTimeout variable, which can be set with mokutil --timeout, to + control how long MokManager waits for input instead of having a hard- + coded timeout of 10 seconds. If the timeout is reached on boot with no input, MokManager clears the MOK requests and passes control back to shim, which falls back to booting the OS. So if you miss seeing MokManager on boot, you have to restart the key enrollment process from the OS and reboot again. When we are invoking mokutil automatically on behalf of the user as part of key generation for dkms modules, we should disable the timeout. We should never leave the user with broken dkms modules on the system because they were looking away from the console at the wrong point in time during a reboot. ** Changed in: ubiquity (Ubuntu Eoan) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856422 Title: always call mokutil with --timeout -1 when enrolling dkms keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1856422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856423] [NEW] Lubuntu installer crashed
Public bug reported: I was attemping to install Lubuntu on a flash drive on a computer that has Windows XP. The installer crashed after about 75% of the process had been completed: a process that had already taken several hours. I was trying to install the latest long term support distribution from a DVD. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.4 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 CasperVersion: 1.376.2 Date: Sat Dec 14 19:58:54 2019 InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lubuntu ubiquity-2.21.63.4 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856423 Title: Lubuntu installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1856423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856420] Re: intel comet lake ethernet device not recognized
Seems related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848555 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856420 Title: intel comet lake ethernet device not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1856420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856420] [NEW] intel comet lake ethernet device not recognized
Public bug reported: Intel Comet Lake Ethernet device is not recognized Related to https://bugs.launchpad.net/hwe-next/+bug/1849074 $ lspci 00:00.0 Host bridge: Intel Corporation Device 9b51 00:02.0 VGA compatible controller: Intel Corporation Device 9bca (rev 04) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device 02f9 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Device 02f0 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8 00:15.1 Serial bus controller [0c80]: Intel Corporation Device 02e9 00:16.0 Communication controller: Intel Corporation Device 02e0 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 02a4 00:1f.6 Ethernet controller: Intel Corporation Device 0d4f 03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 $ ip link list 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 $ lspci -vv ... 00:1f.6 Ethernet controller: Intel Corporation Device 0d4f Subsystem: Lenovo Device 2292 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1856420 Title: intel comet lake ethernet device not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1856420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853022] Re: shim-signed package can not be configured on Lenovo Yoga C630 WOS
It is correct, On the yoga C630 WOS normal UEFI variable writting is not supported by the hardware firmware. At most, I have managed to use Windows 10 utilities to override the path of the windows bootloader to point at the grub efi app, and can be done to point at the shim. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853022 Title: shim-signed package can not be configured on Lenovo Yoga C630 WOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1853022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855590] Re: Kernel module failures for mainline kernel 5.4+ - Not supported
I pointed to the Focal PPA after it was setup and package built on December 12th. Installed correctly with kernel 5.4.3 and Linux Firmware 1.184. Thanks to maintainers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855590 Title: Kernel module failures for mainline kernel 5.4+ - Not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1855590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855590] Re: Kernel module failures for mainline kernel 5.4+ - Not supported
Focal PPA resolved the kernel installation issues. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Assignee: (unassigned) => Berg Lloyd-Haig (berglh) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855590 Title: Kernel module failures for mainline kernel 5.4+ - Not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1855590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856418] [NEW] Synaptic in Wayland locks up display
Public bug reported: I'm running Ubuntu (Gnome-shell) 20.04 in a QEMU/KVM vm. When I'm using Wayland, I can open synaptic package manager successfully by inputting my password. So far as I can tell, it then will let me download updates to the repos and allow me to search for packages. (Usually update-manager downloads the updates automatically, so it's mostly not necessary for synaptic to do this. But, when I proceed to install, unless it's a single, small download, synaptic will lock up the display. The mouse "revolving wheel" stops turning, and although I can still move the mouse, nothing else works. I can't select anything with the mouse. I can't even use "Send Key" in the virtual machine manager to select a console. If I leave the machine for a while, the download and install completes successfully in the background. If I connect to the machine over ssh, I can't shut it down or reboot. If I issue those commands, ssh just disconnects and the machine remains running. Only the big red button in the virtual machine manager will do anything. None of this is happening when running Xorg. ** Affects: synaptic (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/1856418 Title: Synaptic in Wayland locks up display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1856418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856414] [NEW] installing linux-modules-nvidia does not remove nvidia-dkms, and the kernel prioritizes the wrong version of the module from disk
Public bug reported: Installing nvidia-driver-430 pulls in nvidia-dkms-430 as a dependency. Installing linux-modules-nvidia-430-generic does not satisfy this dependency in its place; so nvidia-dkms-430 can't be removed without also removing nvidia-driver-430, and then a bunch of other packages also want to be removed as unused: $ sudo apt purge nvidia-dkms-430 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm9:i386 libnvidia-cfg1-430 libnvidia-common-430 libnvidia-compute-430 libnvidia-compute-430:i386 libnvidia-decode-430 libnvidia-decode-430:i386 libnvidia-encode-430 libnvidia-encode-430:i386 libnvidia-fbc1-430 libnvidia-fbc1-430:i386 libnvidia-gl-430 libnvidia-gl-430:i386 libnvidia-ifr1-430 libnvidia-ifr1-430:i386 libpciaccess0:i386 libsensors5:i386 libstdc++6:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 nvidia-compute-utils-430 nvidia-kernel-source-430 nvidia-prime nvidia-settings nvidia-utils-430 screen-resolution-extra xserver-xorg-video-nvidia-430 Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: nvidia-dkms-430* nvidia-driver-430* 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. After this operation, 1,269 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. $ And it's not sufficient to leave both linux-modules-nvidia and nvidia- dkms installed, because when both are present, the kernel erroneously picks up the modules from nvidia-dkms first, and fails to load them if SecureBoot is on and the local MOK is not enrolled. linux-modules-nvidia-430-generic probably needs a versioned Provides: so that it can be installed in place of nvidia-dkms-430. ** Affects: nvidia-graphics-drivers-430 (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/1856414 Title: installing linux-modules-nvidia does not remove nvidia-dkms, and the kernel prioritizes the wrong version of the module from disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1856414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856412] Re: package grub-efi-amd64 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856412 Title: package grub-efi-amd64 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1856412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856412] [NEW] package grub-efi-amd64 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 19.10 Package: grub-efi-amd64 2.04-1ubuntu12.1 ProcVersionSignature: Ubuntu 5.0.0-37.40-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Dec 15 00:01:32 2019 ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 InvalidGrubScript: /etc/grub.d/25_custom ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=99fbd049-7c8f-4c0b-ac81-61ffa3b84eec ro recovery nomodeset Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: grub2 Title: package grub-efi-amd64 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856412 Title: package grub-efi-amd64 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1856412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856413] [NEW] Asus UX580 touchpad stops working
Public bug reported: Periodically after restart touchpad on my UX580 laptop stops working completely. Closing the lid and letting the laptop to suspend, and then re-opening the lid activates the touchpad. Attached xinput list output. This is Ubuntu 19.10, latest kernel. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Attachment added: "xinput list output" https://bugs.launchpad.net/bugs/1856413/+attachment/5312431/+files/xinput.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856413 Title: Asus UX580 touchpad stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762864] Re: kate cannot run as root
Oh, wasn't aware the KDE folks don't see these...Will invade their IRC :) thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762864 Title: kate cannot run as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1762864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856410] [NEW] ubiquity prompts for a MOK password that it then does not use
Public bug reported: When opting to install non-free drivers on my new laptop, ubiquity tells me that: Installing third-party drivers requires configuring Secure Boot. To do this, you need to choose a security key now, and enter it when the system restarts. And it forces me to choose a password. However, the only hardware on my system that has non-free drivers is nvidia; and thanks to linux-restricted-modules, it should not be necessary to use locally-built dkms modules for nvidia (but see also https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules/+bug/1856407). I should not be prompted to create another password for a thing before we know it's actually going to be needed / used. This means ubiquity should know to only prompt for a password and invoke mokutil if proprietary drivers other than linux-modules-nvidia will actually be installed. Also, note that the unlike ubiquity, dkms/shim-signed debconf handling of the secureboot does not use a 'password' field type. This is not a sensitive password that must be kept secret, it is only used to prove to MokManager when running from UEFI that the key enrollment request came from the person who has physical control of the hardware and is used one time, then discarded. So there's really no need to hide the text being entered in this field. ** Affects: ubiquity (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/1856410 Title: ubiquity prompts for a MOK password that it then does not use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1856410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762864] Re: kate cannot run as root
If you want to argue this issue, which is a very deliberate change by upstream KDE, please make your point to them on their bugtracker/forum/IRC/wherever. Not only is it not a bug in Ubuntu, comments here will not be seen by KDE developers. ** Changed in: kate (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762864 Title: kate cannot run as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1762864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856409] [NEW] un haker me volvio a eliminar
Public bug reported: me encontre un haker en la partida que estava jugando y no podia hacer nada ya que el me teletras portaba hacia otro lugar y el servidor me expluso pensando que yo era el haker ** Affects: apache2 (Ubuntu) Importance: Undecided Assignee: steven (josue200) Status: New ** Changed in: apache2 (Ubuntu) Assignee: (unassigned) => steven (josue200) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856409 Title: un haker me volvio a eliminar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1856409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810154] Re: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed
This bug was fixed in the package plymouth - 0.9.4git20190712-0ubuntu5 --- plymouth (0.9.4git20190712-0ubuntu5) focal; urgency=medium * debian/patches/misc-changes.patch: fix an Ubuntu-specific bug in handling plymouth ask-for-password with a --command option that results in a crash, breaking disk unlocking with zfs. Thank to Witold Krecicki for the fix. LP: #1810154. -- Steve Langasek Sat, 14 Dec 2019 10:43:21 -0800 ** Changed in: plymouth (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810154 Title: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762864] Re: kate cannot run as root
Ok, this is stupid, not being able to run an editor as sudo in linux is just plain dumb, no matter how you view it. What's the point? You can Nano, Vim, Emacs, Gedit etc. any file with sudo, why is Kate so special, and why is it such a pain to just let it run like a regular editor, and not throw wrenches in our environments? This is to the author of Kate, while I appreciate the work, me (and everyone else for that matter) would much appreciate if you just grow up and realize we're not babies in no shape or form, we don't need hand holding or whatever you're using as an excuse, give us a possibility to install Kate as a regular editor. Some of us are hardcore linux users, we pretty much know are way around our environments, and no, sudoedit doesn't cut it. Here's what I wish to you, I wish Linus makes a special version of the kernel just for you where you can't sudo anything, you have to add some configuration to "semi" sudo anything, but it will disappear after you restart your machine. Maybe this way you'll feel how we feel with your software. Cheers, and I hope this gets fixed, and I can take back control of my software, otherwise, please put a paypal link so I can pay to use "sudo kate" and mark the software as shareware or something, so people know that they need to pay for ordinary functionality. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762864 Title: kate cannot run as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1762864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762864] Re: kate cannot run as root
** Changed in: kate (Ubuntu) Status: Invalid => Opinion ** Changed in: kate (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762864 Title: kate cannot run as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1762864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856408] [NEW] zfs-initramfs needs to set FRAMEBUFFER=y
Public bug reported: The poorly-named 'FRAMEBUFFER' option in initramfs-tools controls whether the console_setup and plymouth scripts are included and used in the initramfs. These are required for any initramfs which will be prompting for user input: console_setup because without it the user's configured keymap will not be set up, and plymouth because you are not guaranteed to have working video output in the initramfs without it (e.g. some nvidia+UEFI configurations with the default GRUB behavior). The zfs initramfs script may need to prompt the user for passphrases for encrypted zfs datasets, and we don't know definitively whether this is the case or not at the time the initramfs is constructed (and it's difficult to dynamically populate initramfs config variables anyway), therefore the zfs-initramfs package should just set FRAMEBUFFER=yes in a conf snippet the same way that the cryptsetup-initramfs package does (/usr/share/initramfs-tools/conf-hooks.d/cryptsetup). ** Affects: zfs-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/1856408 Title: zfs-initramfs needs to set FRAMEBUFFER=y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724441] Re: No external network access for VMs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-boxes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724441 Title: No external network access for VMs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1724441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised
I'm having the same issue on an ASUS ZenBook S UX391UA in ubuntu 19.10, kernel version 5.4.2-050402-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641290 Title: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1641290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856407] [NEW] nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed modules
Public bug reported: The linux-restricted-modules package exists so that users who install the nvidia drivers can get known-good, signed modules instead of having to locally self-sign and enroll a signing key through MOK. But lrm in eoan is only building driver packages for nvidia 390 and 430, and nvidia 435 is present in eoan. So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the newest driver instead of using the signed 430 driver. We should never allow the archive to get into this situation. We should be enforcing that any version of the nvidia driver that we expect ubuntu-drivers to install by default on any hardware is integrated into linux-restricted-modules, and we should ensure that ubuntu-drivers always prefers the signed drivers over other options. ** Affects: linux-restricted-modules (Ubuntu) Importance: High Status: New ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: High Status: New ** Affects: ubuntu-drivers-common (Ubuntu) Importance: High Status: New ** Changed in: linux-restricted-modules (Ubuntu) Importance: Undecided => High ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856407 Title: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1856407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852634] Re: Long delay before modal dialogs show
Today, nvidia-driver-430 (the long-lived branch available from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) failed to update properly: "Application of patch do-not-call-pci_save_state.patch failed". So, I removed nvidia-driver-430 and re-tested this issue using nouveau. I could not reproduce the delay. I installed nvidia-driver-440 from the same PPA; I cannot reproduce the delay. I'm unsure if this issue would also be fixed with nvidia-driver-430 version 430.64-0ubuntu0~gpu19.10.1, but at least this issue no longer affects me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852634 Title: Long delay before modal dialogs show To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797373] Re: 3D slide transitions don't work at all or tear when played + repeat animations don't work
Same here on Dell XPS 13 (9333) / Xubuntu 19.10 / LO 6.3.3. 3D slide transitions don't work at all, but **only** when I use the **default distro packages**. OpenGL 3D transitions are broken within Debian / Deepin / Ubuntu, Fedora and even Manjaro/Arch Linux (see https://www.reddit.com/r/libreoffice/comments/9g4ets/libreoffice_impress_61_doesnt_show_3d_transitions for example). When I install Impress via FLATPAK or SNAP, 3D transitions/animations work as expected. It is like this for the last 5+ (!) years (just google for "Impress" "3D" "transitions", to get search results ranging anywhere between 2011-2019). Does anyone know why OpenGL 3D transitions are not working in almost ANY distribution by default? How come that nobody fixed it for so many years? It is hard to believe that distribution maintainers did not notice it. And the fact that it works when you download the DEB packages from LibreOffice.org website instead of **the official repo** makes it even more bizarre : / -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797373 Title: 3D slide transitions don't work at all or tear when played + repeat animations don't work To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1797373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856404] [NEW] Software Updater window does not expand on 18.04
Public bug reported: Software Updater window does not expand. The Software updater window should be manually resizable. It should remember its previous expanded size, but by default should be the same width as when not expanded, and tall enough to show six items in the list, with a minimum height of three items. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $ zcat /usr/share/doc/gnome-session-bin/changelog.Debian.gz | head -n1 gnome-session (3.28.1-0ubuntu3) bionic; urgency=medium $ uname -a 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ inxi CPU: Dual core Intel Core i7-4500U (-MT-MCP-) cache: 4096 KB clock speeds: max: 3000 MHz 1: 1553 MHz 2: 1227 MHz 3: 1716 MHz 4: 1697 MHz Graphics: Card: Intel Haswell-ULT Integrated Graphics Controller Display Server: x11 (X.Org 1.19.6 ) driver: i915 OpenGL: renderer: Mesa DRI Intel Haswell Mobile version: 4.5 Mesa 19.0.8 System:Desktop: Gnome 3.28.4 Distro: Ubuntu 18.04.3 LTS $ gnome-shell --version GNOME Shell 3.28.4 Using GUI Open Settings from left panel or application menu. When it opens, navigate to Details -> About GNOME shows 3.28.2 So you can also see, we have three different information for gnome version. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "video clip showing the bug on desktop" https://bugs.launchpad.net/bugs/1856404/+attachment/5312419/+files/cap001.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856404 Title: Software Updater window does not expand on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1856404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
This issue impacts the experience with Ubuntu significantly. Android, Windows, and OS X all sound much better with a Bluetooth headset when on calls, playing games, or listening to music while using the headset microphone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810154] Re: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed
** Description changed: + [SRU Justification] + An Ubuntu-specific patch causes a crash in plymouth that does not occur upstream and breaks one of the standard use cases of the plymouth client, to prompt for passwords. While the specific error does not affect password prompting for LUKS due to a different invocation of plymouth, it does break password prompting for ZFS encryption, leaving users at an initramfs prompt on boot. + + [Test case] + 1. Change to VT3 on your system (so that you are not under a graphical login session) and log in. + 2. As root, run: plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid --tty=/dev/tty8; chvt 8; plymouth --show-splash; plymouth ask-for-password --prompt "This is a password prompt" --command="/bin/cat"; plymouth quit; chvt 3 + 3. Observe that you are immediately returned to VT3 without being shown a password prompt, and the error message "ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed" is printed on the console. + 4. Install the plymouth package from eoan-proposed. + 5. Repeat step 2. + 6. Observe that you are shown a password prompt. + 7. Type something into the field and hit enter. + 8. Observe that you are returned to VT3 and the text you typed in step 7 has been echoed to the screen, with no error messages. + + [Regression potential] + This is an Ubuntu-specific bug due to missing handling of a new upstream message type in an Ubuntu-specific patch. This fixes a crash and has minimal risk of regression. + + ubuntu cosmic plymouth 0.9.3-1ubuntu10 initramfs-tools 0.131ubuntu15 I'm trying to get a password prompt working in the initramfs via plymouth, but I get an assertion error. This is the sample command I'm running: plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something" And this is the output I get: [./plymouth.c:463] on_password_request:Password request [ply-event-loop.c:759] ply_event_loop_stop_watching_fd:stopping watching fd 6 [ply-event-loop.c:775] ply_event_loop_stop_watching_fd:removing destination for fd 6 [./plymouth.c:430] on_password_request_execute:executing password request (command /bin/cat) [ply-event-loop.c:759] ply_event_loop_stop_watching_fd:stopping watching fd 6 [ply-event-loop.c:775] ply_event_loop_stop_watching_fd:removing destination for fd 6 [ply-event-loop.c:759] ply_event_loop_stop_watching_fd:stopping watching fd 6 [ply-event-loop.c:775] ply_event_loop_stop_watching_fd:removing destination for fd 6 plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed. Aborted - plymouth --ping returns 0. It doesn't matter which --command I try. ** Changed in: plymouth (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810154 Title: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855736] Re: Duplicity fails to start
Well that may explain something. I have no python3.X directory. I have python3, and it contains dist-packages. I did try: /usr/lib/python3/dist-packages$ python3 duplicity/dup_main.py Traceback (most recent call last): File "duplicity/dup_main.py", line 54, in from . import asyncscheduler ImportError: attempted relative import with no known parent package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855736] Re: Duplicity fails to start
Sorry, my bad. You needed to be in the /usr/lib/python3.X/site- packages/ directory. This is not trying to execute duplicity, merely to import the installed duplicity/dup_main.py. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428955] Re: out of date F1 Help
Trusty is now EOL. Help pages have been revised in recent releases. ** Changed in: baobab (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428955 Title: out of date F1 Help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1428955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950149] Re: baobab - toolbar icon causes change in toolbar height
Bug refers to old interface. New interface doesn't have a toolbar. Closing as report is no longer valid. ** Changed in: baobab (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950149 Title: baobab - toolbar icon causes change in toolbar height To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/950149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855736] Re: Duplicity fails to start
I'm not quite sure what your last comment means, so here are 4 attempts. PYTHONPATH='.' duplicity/dup_main.py --version bash: duplicity/dup_main.py: No such file or directory duplicity/dup_main.py --version bash: duplicity/dup_main.py: No such file or directory PYTHONPATH='.' python3 duplicity/dup_main.py --version python3: can't open file 'duplicity/dup_main.py': [Errno 2] No such file or directory python3 duplicity/dup_main.py --version python3: can't open file 'duplicity/dup_main.py': [Errno 2] No such file or directory The results are the same with or without --version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1305900] Re: Totem - by clicking on the slider area the movie doesn't seek to this position. To jump video further should drag the slider pointer instead
Did anyone solve this ? I'm getting this error now in linux mint 19.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1305900 Title: Totem - by clicking on the slider area the movie doesn't seek to this position. To jump video further should drag the slider pointer instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1305900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767817] Re: Full text search does not work
thanks Thatoo, can you kindly tell me how to install this on Ubuntu 18.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840890] Re: PKCS#7 signature not signed with a trusted key
Also see this with Nvidia 435.21 from repository -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840890 Title: PKCS#7 signature not signed with a trusted key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1840890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855736] Re: Duplicity fails to start
Sorry, that should be: $ python3 duplicity/dup_main.py in both cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855736] Re: Duplicity fails to start
You're not being difficult, the problem is vexing! Try this: $ PYTHONPATH='.'duplicity/dup_main.py It should work like this too: $ duplicity/dup_main.py In either case there should be no output. Please log whatever happens. Perhaps there's a missing module or something. Python imports don't tell you a lot when they go wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856397] [NEW] Regression: camera and home keys no longer work on Positivo Mobo 5900
Public bug reported: It was noticed that the home and camera keys on the netbook Positivo Mobo 5900 no longer work on Xubuntu 18.04. Originally, this netbook came with Ubuntu 12.04 but that version is now unsupported, so they are being upgraded to newer Ubuntu versions. Most of its functionality was recovered, but the home and camera buttons in the front of the netbook no longer work. When used in tent mode, the only three keys available are the power button, the camera button and the home button. I did tests with the 4.15 kernel and the camera button was working back then while I had no success with the home button. This netbook model is one of the Classmate PC that was distributed to schools, this particular model having a gma500 GPU, being limited in graphical capabilities, thus requiring Xfce with compositing disabled to work decently. Also, its touchscreen requires evdev instead of libinput to work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-37-generic 5.0.0-37.40~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Dec 14 13:04:00 2019 InstallationDate: Installed on 2019-11-16 (28 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Summary changed: - Regresion: camera and home keys no longer work on Positivo Mobo 5900 + Regression: camera and home keys no longer work on Positivo Mobo 5900 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856397 Title: Regression: camera and home keys no longer work on Positivo Mobo 5900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1856397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855891] Re: reprotest has no installable candidate in focal
This is now in the release pocket, so I'm marking this as fixed. ** Changed in: reprotest (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855891 Title: reprotest has no installable candidate in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprotest/+bug/1855891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855891] Re: reprotest has no installable candidate in focal
Released as https://launchpad.net/ubuntu/+source/reprotest/0.7.10build1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855891 Title: reprotest has no installable candidate in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprotest/+bug/1855891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807056] Re: Occasional Keyboard freeze
has there been a resolution to this problem ? it is happening to me and the frequency is increasing and it now happening every 3-4 minutes and it is becoming impossible to use ubuntu. any help would be appreciated. i hate to move away from ubuntu. many thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807056 Title: Occasional Keyboard freeze To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1807056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841762] Re: package nvidia-dkms-430 430.40-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10
*** This bug is a duplicate of bug 1830961 *** https://bugs.launchpad.net/bugs/1830961 After reboot indeed I was back on a low resolution and without Nvidia graphic driver. A complete uninstall via sudo apt remove nvidia* and afterwards installing the opensource 440 driver via additional driver fixed the issue. That was just like under Windows 95 - reboot into safe mode - remove driver - reboot - install lates driver - reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841762 Title: package nvidia-dkms-430 430.40-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1841762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818811] Re: The swapfile on the Btrfs file system is not activated
Hello. Are there any news? Will it be correct for the 20.04 LTS release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818811 Title: The swapfile on the Btrfs file system is not activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853440] Re: Volume either 0 or 100% on Lenovo X1 Carbon G7
With this kernel there is no sound at all. In gnome sound settings there is only the "Dummy Output" device. Just out of curiosity I tried to fix this specific problem following this article: https://www.linuxuprising.com/2018/06/fix-no-sound-dummy-output-issue-in.html But this didn't fix my problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853440 Title: Volume either 0 or 100% on Lenovo X1 Carbon G7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856394] Re: xz
Thank you for taking the time to report this issue and helping to make Ubuntu better. This package failure looks like it was caused by bad ISO download, corrupted install media, or device failure. eg. look in the logs and you'll see messages like these :- Dec 14 13:26:53 ubuntu kernel: [ 289.649693] SQUASHFS error: zlib decompression failed, data probably corrupt Dec 14 13:26:53 ubuntu kernel: [ 289.649699] SQUASHFS error: squashfs_read_data failed to read block 0x372dd231 Examining the information you have given us, this does not appear to be a useful bug report so I am closing it, as it appears to be a bad ISO or faulty device (inc. bad write-to-device). If you believe I'm in error, please leave a comment explaining why and change the status back to 'New'. I suggest you verify your ISO download, and use the 'check disc for defects' option to validate your media before install to ensure a good download & write. Possibly useful : https://tutorials.ubuntu.com/tutorial/tutorial-how-to- verify-ubuntu#0 and https://help.ubuntu.com/community/Installation/CDIntegrityCheck ** Changed in: ubiquity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856394 Title: xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1856394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856394] [NEW] xz
Public bug reported: xz ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 16:44:18 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug eoan ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856394 Title: xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1856394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855534] Re: UI irresponsive Object Clutter.Actor , has been already deallocated
Another traceback trace of the same symptoms c. 14 13:14:40 psycho1-blob org.gnome.Shell.desktop[582]: #3 7ffc78dee6b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7fb4738b0b80 @ 71) déc. 14 13:14:40 psycho1-blob org.gnome.Shell.desktop[582]: #4 7ffc78dee760 b resource:///org/gnome/shell/ui/dnd.js:59 (7fb47352da60 @ 18) déc. 14 13:14:40 psycho1-blob gnome-shell[582]: clutter_actor_get_stage: assertion 'CLUTTER_IS_ACTOR (actor)' failed déc. 14 13:14:40 psycho1-blob gnome-shell[582]: JS ERROR: TypeError: this._dragActor.get_stage(...) is null _dragActorDropped@resource:///org/gnome/shell/ui/dnd.js:490:22 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _onEvent@resource:///org/gnome/shell/ui/dnd.js:227:24 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _getEventHandlerActor/<@resource:///org/gnome/shell/ui/dnd.js:59:20 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855534 Title: UI irresponsive Object Clutter.Actor , has been already deallocated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853731] Re: chromium snap stops working after awhile, fails to render new tabs/pages
Sorry it took me awhile.. run as requested following lockup.. It seems initially it still responds to keystrokes, lets you open new tabs.. but then eventually the whole UI freezes, and attempts to close with the X will get the app DNR dialog. "killall chrome" nukes it, and it can then be re-run until it happens again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853731 Title: chromium snap stops working after awhile, fails to render new tabs/pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853731] Snap.Info.core18.txt
apport information ** Attachment added: "Snap.Info.core18.txt" https://bugs.launchpad.net/bugs/1853731/+attachment/5312405/+files/Snap.Info.core18.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853731 Title: chromium snap stops working after awhile, fails to render new tabs/pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853731] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1853731/+attachment/5312400/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853731 Title: chromium snap stops working after awhile, fails to render new tabs/pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853731] Snap.Info.chromium.txt
apport information ** Attachment added: "Snap.Info.chromium.txt" https://bugs.launchpad.net/bugs/1853731/+attachment/5312403/+files/Snap.Info.chromium.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853731 Title: chromium snap stops working after awhile, fails to render new tabs/pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853731] Snap.Info.gtk-common-themes.txt
apport information ** Attachment added: "Snap.Info.gtk-common-themes.txt" https://bugs.launchpad.net/bugs/1853731/+attachment/5312406/+files/Snap.Info.gtk-common-themes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853731 Title: chromium snap stops working after awhile, fails to render new tabs/pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853731] Snap.ChromiumPrefs.txt
apport information ** Attachment added: "Snap.ChromiumPrefs.txt" https://bugs.launchpad.net/bugs/1853731/+attachment/5312401/+files/Snap.ChromiumPrefs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853731 Title: chromium snap stops working after awhile, fails to render new tabs/pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
