[Bug 1865216] Re: Cannot launch virtual machine (KVM) on new hwe kernel 5.3.0-40

Fixed in 5.3.0-42-generic ** Changed in: linux-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/1865216 Title: Cannot launch virtual machine (KVM) on

[Bug 1864188] Re: Intel Wireless-AC 9462 [8086:02f0] Subsystem [8086:42a4]: After the upgrade of 19.10 on 2020-02-18, wifi does not exist

*** This bug is a duplicate of bug 1865962 *** https://bugs.launchpad.net/bugs/1865962 Seems to affect any new Dell inspiron sold in Brazil. In particular, both my 15" and my wife 14" do not have wifi with standard 19.10 kernel! -- You received this bug notification because you are a member

[Bug 1832988] Re: Intel 8260 Bluetooth not working

As a workaround I'm currently doing rmmod btusb && modprobe btusb after every boot which seem to do the magic. Attaching the dmesg for that just in case. ** Attachment added: "dmesg2.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832988/+attachment/5335332/+files/dmesg2.log --

[Bug 1832988] Re: Intel 8260 Bluetooth not working

Still failing with the same error on latest Eoan (kernel 5.3.0-40-generic). Dmesg with default kernel and usbcore.dyndbg=+p attached. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832988/+attachment/5335331/+files/dmesg.log -- You received this bug

[Bug 1865063] Re: snapd package hangs on deb postinst

I also can confirm the solution from @zanyrain forks for me as well -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865063 Title: snapd package hangs on deb postinst To manage notifications about

[Bug 1865063] Re: snapd package hangs on deb postinst

And I think here is relevant syslog entries: Feb 29 16:26:06 ubuntu-2004 kernel: [ 175.438250] pool-org.gnome.[8110]: segfault at 8 ip 7f36e9df9b62 sp 7f36e8a03960 error 4 in libgs_plugin_snap.so (deleted)[7f36e9df2000+1a000] Feb 29 16:26:06 ubuntu-2004 kernel: [ 175.438258] Code: d5

[Bug 1865063] Re: snapd package hangs on deb postinst

I can confirm that it also happens to me, the latest daily-live, just installed inside vmware player. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865063 Title: snapd package hangs on deb

[Bug 1865216] Re: Cannot launch virtual machine (KVM) on new hwe kernel 5.3.0-40

** Description changed: + Ubuntu 18.04 LTS. If I try to start a VM, for example with a command "virsh start win2", this command never completes and the VM never starts. Also I cannot normally reboot, because Virtualization Daemon seems frozen and has very high timeout (several minutes).

[Bug 1865216] Re: Cannot launch virtual machine (KVM) on new hwe kernel 5.3.0-40

** Description changed: If I try to start a VM, for example with a command "virsh start win2", this command never completes and the VM never starts. Also I cannot normally reboot, because Virtualization Daemon seems frozen and has very high timeout (several minutes). Thanks. I can

[Bug 1865216] [NEW] Cannot launch virtual machine (KVM) on new hwe kernel 5.3.0-40

Public bug reported: If I try to start a VM, for example with a command "virsh start win2", this command never completes and the VM never starts. Also I cannot normally reboot, because Virtualization Daemon seems frozen and has very high timeout (several minutes). Thanks. I can provide more

[Bug 1864964] [NEW] package xserver-xorg-video-nvidia-390 (not installed) failed to install/upgrade: zkouším přepsat soubor „/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so“, který je také v balík

Public bug reported: Asus N73SV impossible install NVidia M540 drivers. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: xserver-xorg-video-nvidia-390 (not installed) ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion:

[Bug 1863183] [NEW] Error during installation

Public bug reported: Error during installation 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:

[Bug 1862981] [NEW] Failed installation of ubuntu 18.04

Public bug reported: I'm trying to install OSGeoLive on a SSD disk alongside windows. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion:

[Bug 1860907] Re: gnome-shell crashes when using touchscreen

I reproduced the issue again, and sent the info per the instructions, it is here: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1861542 Sorry about not reading the instructions properly the first time, and thanks for your patience :) -- You received this bug notification because

[Bug 1860907] Re: gnome-shell crashes when using touchscreen

ubuntu-bug is telling me some packages were not the newest versions, I'm trying to reproduce again after upgrading my packages ** Attachment removed: "_usr_bin_gnome-shell.1000.crash"

[Bug 1860907] Re: gnome-shell crashes when using touchscreen

Thanks for the guidance, Daniel I have uninstalled the extensions, rebooted, and was still able to reproduce the crash. I have uploaded the .crash file per the instructions you linked. Please let me know if there's anything else I can do to aid in the investigation. ** Attachment added:

[Bug 1294391] Re: 8086:0a06 [Acer C720] Screen freeze during use of chrome/chromium

Looks like this was fixed upstream (https://bugs.freedesktop.org/show_bug.cgi?id=76574 was marked as a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=77207 which was fixed) ** Bug watch added: freedesktop.org Bugzilla #77207 https://bugs.freedesktop.org/show_bug.cgi?id=77207 **

[Bug 1860907] [NEW] gnome-shell crashes when using touchscreen

Public bug reported: The crash isn't immediate, but reliably reproducible when using the touchscreen to interact with multiple full-screen native steam games. Typically happens within 30-120 minutes of normal use. (Same games don't crash at all if the touchscreen is not used.) I've reproduced the

[Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

I tried it and it didn't work for me. In fact, I lost all sound and I had to revert the changes and reboot to fix. Still it might be something small that needs to be changed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location

I do not have a problem with the snap dev team deciding that this issue has no priority for them. That is absolutely fine. It an individual project, it's their project, nobody tells anyone else what to do with their time. To think that they owe us to fix it would be disrespectful imo. But I do

[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location

Sorry, but no. As developers and apps creators, snaps are being pushed on us everywhere and cornering us into change practices and toolchains. This is a lot of time that we have to invest, not knowing whether it's going to pay off, because some company made a decision to vouch for yet another app

[Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

Hi Lewi S. Kristianto, this works for me... thanks ... and sorry for the questions and all the support etc. I'm making a mistake here, i will know for the next time ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

Hi all, can someone tell me how to fix this issue, its getting annoying. Is it going to be new update on this, im not sure about using the ppa. Is there any other safety way to be patched ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

When the new patch/update will come up for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic To

[Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

Hi all, I have Dell Vostro 15 and i have the same problem, can some one give me step by step how to fix it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854798 Title: Synaptics s3203 touchpad

[Bug 1856534] Re: Touchpad not working after update

Hi Chris, Seems like it but i can't find a solution for it ... Here are some additional logs [18.736] (**) Synaptics TM3253-001: always reports core events [18.736] (II) XINPUT: Adding extended input device "Synaptics TM3253-001" (type: TOUCHPAD, id 12) [18.736] (**) synaptics:

[Bug 1856534] Re: Touchpad not working after update

Xorg.logs ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856534/+attachment/5312886/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1856534] Re: Touchpad not working after update

Here is some additional information logs ... ** Attachment added: "evtest01" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856534/+attachment/5312875/+files/evtest01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1856534] Re: Touchpad not working after update

Another file ** Attachment added: "evtest02" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856534/+attachment/5312879/+files/evtest02 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856534

[Bug 1856534] [NEW] Touchpad not working after update

Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ivan 2936 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 09:59:54 2019 HibernationDevice: RESUME=UUID=46c57e98-ae21

[Bug 1855941] Re: hwdb rules for remapping keys are not taking effect in X session

To whom it may concern or in case if someone will find this issue through search engines - try to delete hwdb.bin and regenerate it again - here is what I did: ``` $ sudo rm /etc/udev/hwdb.bin $ sudo udevadm hwdb --update $ sudo udevadm control --reload-rules $ sudo udevadm trigger $ sudo

[Bug 1855941] Re: hwdb rules for remapping keys are not taking effect in X session

I haven't done packages' upgrade for a month. I did parse the list of updated packages from /var/log/apt/history.log. I haven't done packages' upgrade for a month until I haven't done `apt -y dist-upgrade' at the last week. I made a pretty output of upgraded packages to whom it may concern

[Bug 1855941] [NEW] hwdb rules for remapping keys are not taking effect in X session

Public bug reported: Steps to reproduce: - add custom hwdb rules for remapping keys (see the attach of my `cat /etc/udev/hwdb.d/61-ThinkPad-X240-keyboard.hwdb" for example) - run: $ sudo udevadm hwdb --update && sudo udevadm control --reload-rules && sudo udevadm trigger - and reboot PC to

[Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 686859] Re: "Bootloader install failed" cannot be closed

Appears to be present in 19.10 too. I found this bug from a xubuntu live session, during a failed install. The bug is 10 years old and TJ's comment #15 contains a proposed fix, that's gotten zero attention in 2 years. This is fucking insane! -- You received this bug notification because you

[Bug 1852140] [NEW] package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package hplip-data is already installed and configured

Public bug reported: he conseguido agregar la impresora a pesar del error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hplip-data 3.16.3+repack0-1 ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-66-generic i686 ApportVersion: 2.20.1-0ubuntu2.21

[Bug 1852025] [NEW] [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem

Public bug reported: Everytime I boot there is no sound. With QasMixer I am able to fix it by selecting hw:0 (HDA Intel) and increasing the second slider from bottom to top, that slider says "auriculares" in spanish which is "headphones". I am not using headphones though and I didn't found any

[Bug 1852023] [NEW] Wayland doesn't work in GMA500

Public bug reported: I had to disable Wayland in GDM3 in order to be able to login. I guess an udev rule to disable Wayland for GMA500 is all that is needed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname:

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

I can confirm grub2 from eoan-proposed fixes the issue and I'm able to boot both Windows and Linux on a system without SB and without shim. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

Given that my patch fixes the issue for me means: This works: grub_load_and_start_image(boot_image); grub_file_close (file); grub_loader_set (grub_chainloader_boot, grub_chainloader_unload, 0); return 0; This doesn't: grub_file_close (file); grub_loader_set

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

This patch may be wrong but it fixes the issue for me. I already tested it on my actual system (not just VirtualBox). Now to your comments: 1. shim is not dependency of grub2. My 18.04, 18.10 and 19.04 installations had only these packages and no shim: grub-common, grub2-common,

[Bug 1850009] Re: Issue with detecting new state in dhclient-enter-hooks.d/resolved

This bug is also being handled in #1805183. Comment #9 has a much better patch (along the same lines as mine but also captures STDERR from md5sum). Though it doesn't have Eoan included in the list of affected versions. -- You received this bug notification because you are a member of Ubuntu

[Bug 1839317] Re: Grub fails to chainload the Windows Boot Manager on aarch64 laptops

I'm testing the fix for a similar amd64 bug 1845289 but I have a feeling it may also help on arm64. Feel free to test it https://launchpad.net /~xeron-oskom/+archive/ubuntu/grub2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

For anyone trying to reproduce: VirtualBox with EFI enabled with Win 10 Pro x86_64 installed first and Ubuntu 19.10 installed after Windows to the latest additional partition of /dev/sda. On fresh install with all updates: 1. Make sure you can boot both Windows and Ubuntu 2. Purge all shim* and

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

PPA with this patch – https://launchpad.net/~xeron- oskom/+archive/ubuntu/grub2 Reproduced this big in VirtualBox and tested this PPA and it fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

Possible patch. Untested, just an idea. ** Patch added: "Patch to keep shim protocol for chainload but fix boot when SB disabled" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+attachment/5301074/+files/xeron-fix-no-sb-chainload-2.patch -- You received this bug notification

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

Possible fix is to change chainloader to check `grub_efi_secure_boot()` and not `grub_linuxefi_secure_validate()`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

Well may be grub_linuxefi_secure_validate() should still return 1 as intended by this code to skip validation in some cases but then chainloader should not depend on this value. I hope grub2 package maintainers will find some time to take a look at this. -- You received this bug notification

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

Take a look at this diff between disco and eoan: --- grub2-2.02+dfsg1/grub-core/loader/efi/linux.c 2019-10-29 00:23:53.0 + +++ grub2-2.04/grub-core/loader/efi/linux.c 2019-10-29 00:10:44.0 + @@ -23,6 +23,7 @@ #include #include #include +#include

[Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

I've found the patch applied to Eoan was the broken version where it used the bash'ism instead of the much more basic (and more portable) sh'ism of redirecting both STDOUT and STDERR. I have confirmed this behaviour in Eoan (see bug #1850009) after doing an upgrade to this release. I did a quick

[Bug 1850009] [NEW] Issue with detecting new state in dhclient-enter-hooks.d/resolved

systemctl try-reload-or-restart systemd-resolved.service fi === END PATCH === Also, the script removes the script removes the $oldstate file but doesn't remove the $newstate file. Not sure how this made it through QA testing... But breaking DHCP client shouldn't

[Bug 1383858] Re: expr-simplify optimization slows click/snap policy compilation

Hello. Can you guys take a look at this suggestion please? https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1830502/comments/18 Thanks!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383858

[Bug 1830502] Re: apparmor uses excessive memory leading to oom kill

The biggest problem is that it isn't easily disabled because it is hardcoded in the script instead of being in /etc/apparmor/parser.conf. Instead of hardcoding, it would had been better to just update that conffile and let dpkg update it if the user didn't change it (which is highly likely) or

[Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)

I am seeing the same behaviour. The system was installed with the 19.10 beta on LVM and kept up to date. $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1259:00 477G 0 disk ├─nvme0n1p1259:10 512M 0 part /boot/efi └─nvme0n1p2259:2

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

Downgraded to 2.02 and everything works again. Major difference in debug output on 2.02 is the line which says: 2.02: shim bla bla not available shim_lock bla bla linuxefi_secure_validate: 0 2.04: SecureBoot: 0 SetupMode: 1 secure boot not enabled, not validating bla bla

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

For the sake of testing I've updated to the latest grub from 19.10 (2.04-1ubuntu12) and I can't boot Windows anymore. My exact steps were: 0. Ubuntu 19.10 with grub from 19.04. Everything works 1. Move /etc/grub.d/07_os-prober back to /etc/grub.d/30_os-prober to rule this change out 2. sudo apt

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

Bug 1839317 looks too similar to ignore the possibility of the same underlying issue. There's other person there besides me who reports the same behavior on amd64. My Windows bootloader is fine. I can boot Windows using my motherboard's EFI boot menu selector. I can boot Windows if I downgrade

[Bug 1792085] Re: MTP not working/very slow on Bionic

Same problem on Ubuntu 18.04.3 LTS. ls hangs in /run/user/1000/gvfs/mtp:host=... . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic To manage

[Bug 1839317] Re: Grub fails to chainload the Windows Boot Manager

I have the same issue. I can boot Windows 10 from BIOS/EFI boot menu, but can't boot it from grub. Setting debug=chain shows that grub tries to use SecureBoot, but it's disabled. Wiping my grub installation, downgrading to 2.02 from disco and reinstalling it fixed the issue. -- You received

[Bug 1797717] Re: fstrim -av tries to trim read only mounted ntfs-3g and fails

** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797717 Title: fstrim -av tries to trim read only mounted ntfs-3g and fails To manage notifications about this bug go to:

[Bug 1839317] Re: Grub fails to chainload the Windows Boot Manager

** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839317 Title: Grub fails to chainload the Windows Boot Manager To manage notifications about this bug go to:

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

This is probably duplicate of https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317. I have the same issue. I can boot Windows 10 from BIOS/EFI boot menu, but can't boot it from grub. Setting debug=chain shows that grub tries to use SecureBoot, but it's disabled. -- You received this

[Bug 1848090] Re: [snap] Unable to install Extensions

I have tested further installing the Chromium snap in Kubuntu and Xubuntu. Both allow me to install extensions. My Ubuntu install still has the issue. ~/snap/chromium/current/ has a symbolic link to ~/snap/chromium/861 which is empty All folders under ~/snap/chromium/ (861, 881, and common) are

[Bug 1848090] [NEW] [snap] Unable to install Extensions

Public bug reported: When attempting to install an extension in the Snap version of Chromium I'm presented with an error message "An error has occurred Could not create download directory" Steps to recreate: Menu > More tools > Extensions Select any extension to install ** Affects:

[Bug 1619753] Re: systemd-fsck does not show results of rootfs filesystem check in logs or journald

But it should be persisted by default in /var/log, so there should be a unit somewhere that if the log has information then it appends it in a file and gets logrotated. That way, if a server or PC is acting strange, one could look there to see if something strange happened to the filesystem and

[Bug 1797717] Re: fstrim -av tries to trim read only mounted ntfs-3g and fails

** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797717 Title: fstrim -av tries to trim read only mounted ntfs-3g and fails To manage notifications about this bug go to:

[Bug 1830359] Re: cpuset_base_ops from controller test suite in LTP failed

the failure, cpuset_base_ops 37 TFAIL: cpuset.cpus: Test result - Expected string - "0" are from testing the $/bin/echo "0-" > "$CPUSET/1/cpuset.cpus" and expecting "0" but got invalid parameter on cpuset_base_ops_testset.sh else base_op_test

[Bug 1829982] Re: ltp_acpi from kernel_misc test suite in LTP failed

fix patch sent for review, https://github.com/linux-test-project/ltp/pull/578 ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1829982] Re: ltp_acpi from kernel_misc test suite in LTP failed

** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Ivan Hu (ivan.hu) ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.ne

[Bug 1829982] Re: ltp_acpi from kernel_misc test suite in LTP failed

[ 504.084541] ltp_acpi_test: get register: 11 val: [ 504.084944] ltp_acpi_test: get register: 12 val: [ 504.085318] ACPI Exception: AE_BAD_ADDRESS, acpi_read_bit_register the fail is on read ID 0x13, which is on PM2 control bit 0(ARB_DIS). this failure is caused by the PM2 aren't

[Bug 1273764] Re: Grub ignores TIMEOUT options on /etc/default/grub

@estanislao-gonzalez-r GRUB doesn't support writes to LVM so it always treats previous boot as failed. Sad but true. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273764 Title: Grub ignores

[Bug 1757202] Re: xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time

Same issue with Xubuntu 18.04.3 Used workaround with "Files" section, but I had to use /usr/lib/x86_64-linux-gnu/nvidia-430 path. /usr/lib/x86_64-linux-gnu/nvidia/xorg and /usr/lib/x86_64-linux-gnu/xorg do not exist in my system. -- You received this bug notification because you are a member

[Bug 1801540]

Gigabyte X470 AORUS ULTRA ALC1220, [1022:1457] subsys [1458:a0c3] Test Fis Patch no.5 on kernel 5.1.5: - sound playback OK - sound recording OK ( crackling disappeared ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1840995] [NEW] check_stamp() function of apt.systemd.daily should not assume interval is a number

Public bug reported: In the second half of the function there is # Calculate the interval in seconds depending on the unit specified if [ "${interval%s}" != "$interval" ] ; then interval="${interval%s}" elif [ "${interval%m}" != "$interval" ] ; then

[Bug 1825128] Re: grub-efi-amd64-signed should depends on mokutil

shim-signed package has already depended on mokutil. When secureboot enabled, shim is needed and mokutil should be installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825128 Title:

[Bug 1833297] Re: Ubuntu 19.04's Linux kernel 5.0.0-17 has regressed TPM2 functionality

The fix patch has been included in the latest disco kernel. I've tested it with version 5.0.0-23-generic, it worked. ** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1822043] Re: as enrolling mok, the font is too small in hi-dpi monitor

The patch has been upstreamed, https://github.com/rhboot/shim/pull/182 ** Changed in: shim (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822043 Title:

[Bug 1822043] Re: as enrolling mok, the font is too small in hi-dpi monitor

attached the test mmx64.efi ** Attachment added: "mmx64.tar.gz" https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1822043/+attachment/5278810/+files/mmx64.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1835838] [NEW] FTP/SFTP support missing because dar-static was compiled without libcurl support

Public bug reported: On Ubuntu Bionic (but using the dar-static package from Disco), dar_static v2.6.2-1 is compiled without libcurl support which effectively disables FTP/SFTP support, which is one of the main selling points of the DAR v2.6 branch $ dar_static -v -v -v -c ftp://example.org

[Bug 1833297] Re: Ubuntu 19.04's Linux kernel 5.0.0-17 has regressed TPM2 functionality

** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833297 Title: Ubuntu 19.04's Linux kernel 5.0.0-17 has regressed TPM2

[Bug 1833297] Re: Ubuntu 19.04's Linux kernel 5.0.0-17 has regressed TPM2 functionality

** Description changed: Hi, With all updates installed to Ubuntu disco it is impossible to use TPM2 device on the machine. Most of the TPM2 commands seem to fail due to Linux kernel having async access problem that is fixed in linux kernel 5.0.10 release. With previous Ubuntu

[Bug 1784757] Re: rabbitmq-server does not properly shutdown

I'm not sure why I did not mention originally, sorry for that, but there is a chance that what makes it reproducible is starting the daemon inside the lxd/lxc For those who don't use lxd - the commands would be (I don't have access to linuxes or my infrastructure at the moment, so might be a bit

[Bug 1825128] Re: grub-efi-amd64-signed should depends on mokutil

What does grub-check-signatures use mokutil for? It makes more sense mokutil depends on shim not grub. Can mokutil depend on shim package solve your issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1366322] Re: private/cord_pos.h missing from package

This bug should be closed (it is fixed in v7.4.2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366322 Title: private/cord_pos.h missing from package To manage notifications about this bug go to:

[Bug 1815699] Re: installed ejabberd package post-installation script subprocess returned error exit status 1

@Philipp Huebner I personally use the following systemd service override: ``` [Service] PrivateTmp=false ProtectHome=false ProtectSystem=false ``` Speaking of detection: `systemd-detect-virt` in an lxd/lxc container returns `lxc\n` -- You received this bug notification because you are a

[Bug 116300] Fw (1): cc

Surprise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/116300 Title: eclipse crashes when spawning DTD/XSD license agreement confirmation screen To manage notifications

[Bug 1580123] Re: xrandr --scale (again) confines mouse to native solution

VMWare has this cursor issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution To manage notifications about this bug go to:

[Bug 1596562] Re: devscripts doesn't depend on equivs (for mk-build-deps)

still present in bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596562 Title: devscripts doesn't depend on equivs (for mk-build-deps) To manage notifications about this bug go to:

[Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

and https://bugs.freedesktop.org/show_bug.cgi?id=102646 ** Bug watch added: freedesktop.org Bugzilla #102646 https://bugs.freedesktop.org/show_bug.cgi?id=102646 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

has already https://bugs.freedesktop.org/show_bug.cgi?id=110199 ** Bug watch added: freedesktop.org Bugzilla #110199 https://bugs.freedesktop.org/show_bug.cgi?id=110199 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

Ok, I found a problem commit. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.18.y=d9ef158adf04b81772a7e9d682a054614ebac2fd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

But following the description, the commit canceled the previous patch due to some problems. I think you need a more detailed study of the problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813701

[Bug 726844] Re: needs porting for SMP support on armel

As of libatomic_ops v7.6.6, arm, aarch64, x86, x64 use gcc atomics by default. ** Changed in: libatomic-ops (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on some AMI's firmwares

Here are testing procedures, 1. Install Ubuntu 18.04 and connect to internet 2. Perform Firmware Update, base on 10-3 (expeted fail due to capsule header issue) $sudo fwupdate -a {guid} 1AUOK.bin $sudo efibootmgr (check boot entry, next boot is create or not) $sudo reboot It failed to do

[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on some AMI's firmwares

Got confirmed from AMI Taipei team. This version fixes the Capsule issue on AMI's firmware. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1821484] [NEW] La instalacion falló por que el pc ibernó

Public bug reported: Estaba instalando Ubuntu y el pc apagó la pantalla, moví el mouse y despues continuó con la instalacion, pero unos minutos despues apareció el aviso de que se habia dañado el instalador ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 [modified:

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

Forgot to add: Ubuntu 18.04.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected To manage notifications about this bug

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

I confirm the bug exists and workarounds work, both with lightdm and ExecStartPre line. Also, adding xinit to ExecStartPre messes up suspend functionality. That is a pity... Laptop: Thinkpad P1 with nvidia graphics -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1821108] [NEW] vga error when discconect and connect

Public bug reported: I have a HP elitebook G1. My problem appears when I disconnect the VGA cable, I can not display anything until reboot my computer each one! please, help!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu

[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on some AMI's firmwares

It seems the proposed release packages still be pending, amd64 - Pending publication arm64 - Pending publication armhf - Pending publication i386 - Pending publication https://launchpad.net/ubuntu/+source/fwupdate -- You received this bug notification because you are a member of Ubuntu Bugs,

<    1   2   3   4   5   6   7   8   9   10   >