[Bug 1848413] Re: Wireless networking "not working" during install.
*** This bug is a duplicate of bug 1848404 *** https://bugs.launchpad.net/bugs/1848404 ** This bug has been marked a duplicate of bug 1848404 ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848413 Title: Wireless networking "not working" during install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848439] Re: generic/562 from ubuntu_xfstests_btrfs failed on D
** Patch added: "btrfs-generic-562-output.diff" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848439/+attachment/5297778/+files/btrfs-generic-562-output.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848439 Title: generic/562 from ubuntu_xfstests_btrfs failed on D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848333] Re: wifi problem delays boot in live mode
attached photo showing the waiting ** Attachment added: "lubuntu-waiting-90s.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333/+attachment/5297779/+files/lubuntu-waiting-90s.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848333 Title: wifi problem delays boot in live mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848439] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Disco) 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/1848439 Title: generic/562 from ubuntu_xfstests_btrfs failed on D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848404] Re: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking
Reproduced on 19.10 Ubuntu image (http://cdimage.ubuntu.com/daily- live/20191016.5/eoan-desktop-amd64.iso) on a Dell XPS 13 running with UEFI and Secure Boot. Steps to reproduce: 1. Boot the 19.10 image 2. Select "Install Ubuntu" 3. Try to connect to a WiFi network → after a while, an error window is shown, suggesting you report the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848404 Title: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847967] Re: oem kernel packages treated differently from generic kernel ones
Maybe the best solution is to install such links in every kernel related source packages built kernel image packages themselves. :X -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847967 Title: oem kernel packages treated differently from generic kernel ones To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786244] Re: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 1
@Christian LP: #1844738 doesn't happen to Bionic, it only happens to customized Bionic server image. Thanks for your help. It has been fixed by new customized image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786244 Title: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-legacy-ec2/+bug/1786244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848445] [NEW] Kernel needs a special workaround argument to boot
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 19.10 Release: 19.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 3) What you expected to happen Boot 4) What happened instead Freezes (see below for workaround), no visible sign of interaction possible. Caps lock "led" doesn't work indicating keyboard isn't working. Just a white cursor (non blinking) on screen, CPU doesn't seem to do anything since fan stops after a while. This is more likely a Linux "bug". Unless you pass acpi_osi= argument to Linux kernel, it won't boot, appear and behave frozen with a (non blinking) cursor on top left. There is no further information given to user further complicating things. Previously on 4.x kernels, system would boot using acpi=off argument creating more problems on this particular laptop model (HP Pavilion X360 13 inch). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ilgaz 21270 F pulseaudio /dev/snd/controlC1: ilgaz 21270 F pulseaudio /dev/snd/pcmC1D0p: ilgaz 21270 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 10:02:44 2019 HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae InstallationDate: Installed on 2019-10-13 (3 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: Hewlett-Packard HP Pavilion 13 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi= RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago) dmi.bios.date: 06/21/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.41 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2341 dmi.board.vendor: Hewlett-Packard dmi.board.version: 07.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 13 x360 PC dmi.product.sku: L0B89EA#AB8 dmi.product.version: 097712405F0410180 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848445 Title: Kernel needs a special workaround argument to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828409] Re: please remove htslib on i386
I think i386 status quo changed... ** Changed in: htslib (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828409 Title: please remove htslib on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/htslib/+bug/1828409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848439] Re: generic/562 from ubuntu_xfstests_btrfs failed on D
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848439 Title: generic/562 from ubuntu_xfstests_btrfs failed on D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847021] Re: Cannot input Chinese if only "Chinese (Intelligent Pinyin)" is set
Thanks for updating libpinyin packages! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847021 Title: Cannot input Chinese if only "Chinese (Intelligent Pinyin)" is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1847021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848404] Re: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking
** Description changed: - Ubuntu MATE 19.10 20191016 + Ubuntu (and all flavors) 19.10 20191016 - Install to bare metal. T430 and nv56r laptops connecting to wireless - networks that have been used in prior ISO testing. + Test Case + 1. Boot the ubiquity-dm + 2. Select "Install Ubuntu" + 3. On the wifi page configure a wifi connection + + Actual result + This crash + + Expected result + connection established successfully. + + == Original description == + Install to bare metal. T430 and nv56r laptops connecting to wireless networks that have been used in prior ISO testing. Installer hangs after entering password. After several minutes installer will crash from Wireless screen and drop to desktop. Am able to click on desktop icon and complete installation from there. Crash screen appears. Installer has encountered an unrecoverable error. - More details to come -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848404 Title: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848447] [NEW] package ndiswrapper-dkms 1.60-8ubuntu1 failed to install/upgrade: installed ndiswrapper-dkms package post-installation script subprocess returned error exit status 10
Public bug reported: Issue while upgrading from 19.01 to 19.10 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: ndiswrapper-dkms 1.60-8ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Thu Oct 17 02:44:21 2019 ErrorMessage: installed ndiswrapper-dkms package post-installation script subprocess returned error exit status 10 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, 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: ndiswrapper Title: package ndiswrapper-dkms 1.60-8ubuntu1 failed to install/upgrade: installed ndiswrapper-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) ** Affects: ndiswrapper (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/1848447 Title: package ndiswrapper-dkms 1.60-8ubuntu1 failed to install/upgrade: installed ndiswrapper-dkms package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1848447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848404] Re: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking
This happens also when Secure Boot is disabled. If, instead of selecting "Install Ubuntu", I choose "Try Ubuntu", log into the live session and select "Install Ubuntu", then the connection to WiFi process works as expected, as per comment #9. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848404 Title: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848447] Re: package ndiswrapper-dkms 1.60-8ubuntu1 failed to install/upgrade: installed ndiswrapper-dkms package post-installation script subprocess returned error exit status 10
** 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/1848447 Title: package ndiswrapper-dkms 1.60-8ubuntu1 failed to install/upgrade: installed ndiswrapper-dkms package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1848447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843381] Re: Dell system takes a long time to connect network with external dock
@ddstreet Tested on bionic/disco/eoan. All of them do not rename the second usbnet with MAC passthrough function, it keeps ifname eth0. Thank you so much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843381 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847980] Re: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work
Would it be possible for you to do a kernel bisection? First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the good version you found) $ git bisect bad $(the bad version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If the issue still happens, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847980 Title: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1847980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848445] 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/1848445 Title: Kernel needs a special workaround argument to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo
Would it be possible for you to do a kernel bisection? First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the good version you found) $ git bisect bad $(the bad version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If the issue still happens, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Yes, by using the F12 key, I can display the EFI start menu and start Windows with the "Windows Boot Manager" line. This is a test machine that follows the development of "Ubuntu next". Initially installed with Ubuntu 17.10 beta, it has followed the updates of all Ubuntu development versions (18.04, 18.10, ...) until today. Now in 19.10, it will soon switch to Ubuntu Focal 20.04). The Windows part has been re-installed from scratch with an Windows 10 18.03 USB flash drive installer and regularly updated. Now running W10-19.03. After installing Windows, Grub was re-installed by starting the machine with Ubuntu-Live 18.04 and then entering the following commands: $ sudo mount /dev/sda2 /mnt $ for i in dev sys proc dev/pts; do sudo mount -o bind /$i /mnt/$i; done $ sudo chroot /mnt # apt purge grub-common grub-efi grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common # apt install grub-common grub-efi grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common # update-grub (... reboot → Ubuntu ...) $ sudo update-grub Everything was working well until more or less half-time of 19.10 developpement. Here my partitioning : $ sudo parted /dev/sda print Model: ATA M4-CT512M4SSD2 (scsi) Disk /dev/sda: 512GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 1049kB 1075MB 1074MB fat32esp boot, esp 2 1075MB 207GB 206GB ext4 Ubuntu 3 207GB 345GB 137GB ntfs data msftdata 4 345GB 345GB 16.8MB Microsoft reserved partition msftres 5 345GB 512GB 167GB ntfs Basic data partition msftdata 6 512GB 512GB 520MB ntfs hidden, diag -- 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 longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847892] Re: large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel
Would it be possible for you to do a kernel bisection? First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the good version you found) $ git bisect bad $(the bad version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If the issue still happens, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847892 Title: large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848445] Re: Kernel needs a special workaround argument to boot
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc3/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848445 Title: Kernel needs a special workaround argument to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847838] Re: [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8
47f50d610765 xhci: Fix USB 3.1 capability detection on early xHCI 1.1 spec based hosts here is the fix in 5.4-rc3, please backport it into 19.04 if possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847838 Title: [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1847838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847126] Re: Glyphs for space and basic punctuation not substituted from other fonts
I'm still unable to reproduce this behaviour following your instructions (see attached) ** Attachment added: "Screenshot 2019-10-17 at 08.50.05.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1847126/+attachment/5297808/+files/Screenshot%202019-10-17%20at%2008.50.05.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847126 Title: Glyphs for space and basic punctuation not substituted from other fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1847126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by lsusb(usbutils)
Good News Its working in 19.10 adriaan@Dell7577:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5301 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0c45:6a08 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by lsusb(usbutils) To manage notifications about this bug go to: https://bugs.launchpad.net/usbutils/+bug/1721909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847838] Re: [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8
sorry it is 19.10. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847838 Title: [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1847838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848413] Re: Wireless networking "not working" during install.
*** This bug is a duplicate of bug 1848404 *** https://bugs.launchpad.net/bugs/1848404 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (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/1848413 Title: Wireless networking "not working" during install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847948] Re: Improve NVMe guest performance on Bionic QEMU
Thanks Murilo, I need no test with the basic kernel yet. But later when we really SRU this it will be good to do both a old and a HWE kernel check. Let me add that to the verification steps ... ** Description changed: [Impact] - * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO. -But there can be platforms (like ppc64 spapr) that can and want to do -exactly that. + * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO. + But there can be platforms (like ppc64 spapr) that can and want to do + exactly that. - * Backport two patches from upstream (in since qemu 2.12 / Disco). + * Backport two patches from upstream (in since qemu 2.12 / Disco). - * Due to that there is a tremendous speedup, especially useful with page -size bigger than 4k. This avoids that being split into chunks and makes -direct MMIO access possible for the guest. + * Due to that there is a tremendous speedup, especially useful with page + size bigger than 4k. This avoids that being split into chunks and makes + direct MMIO access possible for the guest. [Test Case] - * On ppc64 pass through an NVME device to the guest and run I/O -benchmarks, see below for Details how to set that up. -Note this needs the HWE kernel or another kernel fixup for [1]. + * On ppc64 pass through an NVME device to the guest and run I/O + benchmarks, see below for Details how to set that up. + Note: this needs the HWE kernel or another kernel fixup for [1]. +Note: the test should also be done with the non-HWE kernel, the +expectation there is that it would not show the perf benefits, but +still work fine [Regression Potential] - * Changes: -a) if the host driver allows mapping of MSI-X data the entire BAR is - mapped. This is only done if the kernel reports that capability [1]. - This ensures that only on kernels able to do so qemu does expose the - new behavior (safe against regression in that regard) -b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local - to just this HW and will not affect other HW. + * Changes: + a) if the host driver allows mapping of MSI-X data the entire BAR is + mapped. This is only done if the kernel reports that capability [1]. + This ensures that only on kernels able to do so qemu does expose the + new behavior (safe against regression in that regard) + b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local + to just this HW and will not affect other HW. -Generally the regressions that come to mind are slight changes in -behavior (real HW vs the former emulation) that on some weird/old -guests could cause trouble. But then it is limited to only PPC where -only a small set of certified HW is really allowed. + Generally the regressions that come to mind are slight changes in + behavior (real HW vs the former emulation) that on some weird/old + guests could cause trouble. But then it is limited to only PPC where + only a small set of certified HW is really allowed. -The mapping that might be added even on other platforms should not -consume too much extra memory as long as it isn't used. Further since -it depends on the kernel capability it isn't randomly issues on kernels -where we expect it to fail. + The mapping that might be added even on other platforms should not + consume too much extra memory as long as it isn't used. Further since + it depends on the kernel capability it isn't randomly issues on kernels + where we expect it to fail. -So while it is quite a change, it seems safe to me. + So while it is quite a change, it seems safe to me. [Other Info] - - * I know, one could as well call that a "feature", but it really is a -performance bug fix more than anything else. Also the SRU policy allows -exploitation/toleration of new HW especially for LTS releases. -Therefore I think this is fine as SRU. + + * I know, one could as well call that a "feature", but it really is a + performance bug fix more than anything else. Also the SRU policy allows + exploitation/toleration of new HW especially for LTS releases. + Therefore I think this is fine as SRU. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a32295c612c57990d17fb0f41e7134394b2f35f6 - == Comment: #0 - Murilo Opsfelder Araujo - 2019-10-11 14:16:14 == ---Problem Description--- Back-port the following patches to Bionic QEMU to improve NVMe guest performance by more than 200%: ?vfio-pci: Allow mmap of MSIX BAR? https://git.qemu.org/?p=qemu.git;a=commit;h=ae0215b2bb56a9d5321a185dde133bfdd306a4c0 ?ppc/spapr, vfio: Turn off MSIX emulation for VFIO devices? https://git.qemu.org/?p=qemu.git;a=commit;h=fcad0d2121976df4b422b4007a5eb7fcaac01134 ---uname output--- na ---
[Bug 1847948] Re: Improve NVMe guest performance on Bionic QEMU
I opened up the MP for review again after pushing the extra patches that you tested. Once that is done I can push it to the SRU teams queue ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847948 Title: Improve NVMe guest performance on Bionic QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1847948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775378] Re: fanotify06 in LTP syscall test failed with T kernel
Test with the proposed Trusty kernel. This patch works as expected. Thanks. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Trusty) 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/1775378 Title: fanotify06 in LTP syscall test failed with T kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848413] Re: Wireless networking "not working" during install.
*** This bug is a duplicate of bug 1848404 *** https://bugs.launchpad.net/bugs/1848404 I can confirm this bug, tested in a Toshiba laptop http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/ I booted without 'quiet splash" and noted a delay for 1 min 30 seconds. Could this bug be related to the delay bug reported at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848413 Title: Wireless networking "not working" during install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846454] Re: laptop mode tools gui cannot be opened through the start menu
And you may also consider reporting bugs to Upstream project here, https://github.com/rickysarraf/laptop-mode-tools, if you think they are generic and apply to upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846454 Title: laptop mode tools gui cannot be opened through the start menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1846454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846454] Re: laptop mode tools gui cannot be opened through the start menu
I don't remember if it went into 1.71 or not. But the GUI has integration with PolicyKit. You could try running either `pkexec lmt-config-gui` or `lmt-config-gui-pkexec`. This will only work on Xorg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846454 Title: laptop mode tools gui cannot be opened through the start menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1846454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/
Is there a separate bug somewhere about actually implementing custom policies? Since 19.10 switched Chromium to Snap this means that not having those is an actual regression compared to 18.10 or 19.04, so I'd say this warrants a slightly higher priority now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714244 Title: [snap] apparmor denials on /etc/chromium-browser/policies/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
Test result on Trusty: startup='Sat Oct 5 00:28:40 2019' tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.42.9 (4-Feb-2014) tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s fanotify10.c:331: INFO: Test #0: ignore mount events created on a specific file fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8205 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8205 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8205 fd=30 fanotify10.c:398: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:331: INFO: Test #1: ignore exec mount events created on a specific file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #2: don't ignore mount events created on another file fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8206 fd=30 fanotify10.c:331: INFO: Test #3: don't ignore exec mount events created on another file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #4: ignore inode events created on a specific mount point fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8207 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8207 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8207 fd=30 fanotify10.c:392: FAIL: group 0 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 1 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 2 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 0 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 1 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 2 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:331: INFO: Test #5: ignore exec inode events created on a specific mount point fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #6: don't ignore inode events created on another mount point fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8208 fd=30 fanotify10.c:331: INFO: Test #7: don't ignore exec inode events created on another mount point fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #8: ignore fs events created on a specific file fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:331: INFO: Test #9: ignore exec fs events created on a specific file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #10: don't ignore mount events created on another file fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:331: INFO: Test #11: don't ignore exec mount events created on another file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #12: ignore fs events created on a specific mount point fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:331: INFO: Test #13: ignore exec fs events created on a specific mount point fanotify10.c:226:
[Bug 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
Actually this issue *is* affecting Ubuntu Mate 19.10, it's just not as noticeable but definitely there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819413] Re: [ICL] S0ix Enabling
oem-osp1 was handled via bug 1836012, and 19.10 ships with 5.3 ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => 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/1819413 Title: [ICL] S0ix Enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1819413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848459] [NEW] Make xserver-xorg-hwe-18.04 recommend linux-generic-hwe-18.04 | linux-oem-osp1 | linux-oem
Public bug reported: [Impact] We already preloaded many Ubuntu OEM images with the combinations of linux-oem and xserver-xorg-hwe-18.04, or linux-oem-osp1 and xserver-xorg-hwe-18.04 on bionic. Right now, we planed to make OEM meta packages for each OEM platforms. Recently we found the system will install linux-generic-hwe-18.04 when we make the OEM meta package to depend on linux-oem and xserver-xorg-hwe-18.04. Please make xserver-xorg-hwe-18.04 recommend linux-generic-hwe-18.04 | linux-oem-osp1 | linux-oem so we can make it soomthly. [Test case] Check that the generic kernel is not pulled in. [Regression potential] None, only adds alternatives to an existing Recommends. ** Affects: xorg-hwe-18.04 (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/1848459 Title: Make xserver-xorg-hwe-18.04 recommend linux-generic-hwe-18.04 | linux- oem-osp1 | linux-oem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-hwe-18.04/+bug/1848459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848439] Re: generic/562 from ubuntu_xfstests_btrfs failed on D
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848439 Title: generic/562 from ubuntu_xfstests_btrfs failed on D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848333] Re: wifi problem delays boot in live mode
** Description changed: This problem is rather new. It did not affect Lubuntu Eoan zsynced 9 days ago (Oct 6). Now there is a delay of 1 min 30 sec during booting, and I think there is something wrong with the recognition of the wifi hardware or maybe matching of driver and hardware. It happens in 'this' computer, a middle-aged Toshiba laptop with a generation 3 Intel i5 cpu and also in a Dell Latitude E7240 with a generation 4 Intel i5 cpu and I guess another wifi chip. In both cases both ethernet and wifi works. I see available wifi routers and can connect (when I have the password). - I tested also with the Xubuntu eoan iso file, and the same delay - happened there. + I tested also with the Kubuntu and Xubuntu eoan iso files, and the same + delay happened there. I think the drivers are OK, but something in the logic for recognition of them might be bad. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: lubuntu2316 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: lubuntu2316 F pulseaudio CasperVersion: 1.426 CurrentDesktop: LXQt Date: Wed Oct 16 11:36:22 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015) MachineType: TOSHIBA SATELLITE PRO C850-19W ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed persistent --- RelatedPackageVersions: - linux-restricted-modules-5.3.0-18-generic N/A - linux-backports-modules-5.3.0-18-generic N/A - linux-firmware1.183 + linux-restricted-modules-5.3.0-18-generic N/A + linux-backports-modules-5.3.0-18-generic N/A + linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: PLCSF8 dmi.board.vendor: Intel dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: SATELLITE PRO C850-19W dmi.product.sku: PSCBXE dmi.product.version: PSCBXE-00C00VN5 dmi.sys.vendor: TOSHIBA -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848333 Title: wifi problem delays boot in live mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848459] Re: Make xserver-xorg-hwe-18.04 recommend linux-generic-hwe-18.04 | linux-oem-osp1 | linux-oem
** Description changed: + [Impact] We already preloaded many Ubuntu OEM images with the combinations of linux-oem and xserver-xorg-hwe-18.04, or linux-oem-osp1 and xserver-xorg-hwe-18.04 on bionic. Right now, we planed to make OEM meta packages for each OEM platforms. Recently we found the system will install linux-generic-hwe-18.04 when we make the OEM meta package to depend on linux-oem and xserver-xorg-hwe-18.04. Please make xserver-xorg-hwe-18.04 recommend linux-generic-hwe-18.04 | linux-oem-osp1 | linux-oem so we can make it soomthly. + + [Test case] + Check that the generic kernel is not pulled in. + + [Regression potential] + None, only adds alternatives to an existing Recommends. ** Also affects: xorg-hwe-18.04 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: xorg-hwe-18.04 (Ubuntu) Status: New => Invalid ** Changed in: xorg-hwe-18.04 (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848459 Title: Make xserver-xorg-hwe-18.04 recommend linux-generic-hwe-18.04 | linux- oem-osp1 | linux-oem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-hwe-18.04/+bug/1848459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847975] Re: extension does not start, sometime when starting crashes gnome-shell
** Changed in: gnome-shell-extension-show-ip (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/1847975 Title: extension does not start, sometime when starting crashes gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-show-ip/+bug/1847975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Here the details of /boot file (with EFI partition mounted) ** Attachment added: "find /boot output (with EFI partition mounted)" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+attachment/5297817/+files/find_in_boot_dir.output -- 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 longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846454] Re: laptop mode tools gui cannot be opened through the start menu
@rss: Yeah, I see that your patches made it into release 1.72, so an update of the Ubuntu package to that release would do it. No idea if the package manager would be keen to do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846454 Title: laptop mode tools gui cannot be opened through the start menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1846454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdb (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/1848200 Title: gdb not stopping on breakpoint in a 32-bit program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846250] Re: trusty/linux: 3.13.0-174.225 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 14. October 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: precise/linux-lts-trusty: bug 1846248 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846250 Title: trusty/linux: 3.13.0-174.225 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848004] Re: test_maps from ubuntu_bpf failed with sockmap creation on D-KVM
Spotted on B-KVM as well. ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Summary changed: - test_maps from ubuntu_bpf failed with sockmap creation on D-KVM + test_maps from ubuntu_bpf failed with sockmap creation on B/D-KVM ** Tags added: 4.15 ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848004 Title: test_maps from ubuntu_bpf failed with sockmap creation on B/D-KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848460] [NEW] no touchpad
Public bug reported: touchpad (as well as touch-screen) not detected, working under Win10 TREKSTOR Primebook C11B ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 1429 F pulseaudio /dev/snd/pcmC0D0p: frank 1429 F...m pulseaudio /dev/snd/controlC1: frank 1429 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 10:32:57 2019 InstallationDate: Installed on 2019-10-01 (16 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TREKSTOR Primebook C11B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=2a410d09-1936-4a4d-b969-d7d09d196707 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.178.5 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-10-11 (5 days ago) dmi.bios.date: 05/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.1.2 dmi.board.asset.tag: Default string dmi.board.name: Apollolake_alk_V01 dmi.board.vendor: TS_weibu dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.1.2:bd05/03/2018:svnTREKSTOR:pnPrimebookC11B:pvrDefaultstring:rvnTS_weibu:rnApollolake_alk_V01:rvrDefaultstring:cvn:ct31:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: Primebook C11B dmi.product.sku: CFALKWW03 dmi.product.version: Default string dmi.sys.vendor: TREKSTOR ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848460 Title: no touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Is that a duplicate of https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317 ? ** Changed in: grub2 (Ubuntu Eoan) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846250] Re: trusty/linux: 3.13.0-174.225 -proposed tracker
3.13.0-174.225 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) emulator (bug 1824291) eventinj (bug 1824293) ioapic (bug 1824289) realmode (bug 1824294) svm (bug 1821903) umip should be skipped (bug 1821905) ubuntu_ltp_syscalls - fanotify07 won't fix (bug 1775165) fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) fcntl35 / fcntl35_64 (bug 1774394) fanotify09 (bug 1775153) fanotify10 (bug 1802454) keyctl02 (bug 1798022) keyctl06 (bug 1798025) openat03 (bug 1798027) request_key03 (bug 1798052) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) libhugetlbfs - noresv-preserve-resv-page failed (bug 1747823) chunk-overcommit failed (bug 1747828) ubuntu_kvm_smoke_test - getlogin will fail to open /proc/self/loginuid (bug 1770245) ubuntu_ltp_syscalls - fanotify07 won't fix (bug 1775165) fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) fcntl35 / fcntl35_64 (bug 1774394) fanotify09 (bug 1775153) fanotify10 (bug 1802454) keyctl02 (bug 1798022) keyctl06 (bug 1798025) open14 (bug 1798061) openat03 (bug 1798027) request_key03 (bug 1798052) ubuntu_qrt_kernel_security - test_130_config_debug_rodata (bug 1747850) test 021, 022 (bug 1747847) test 050 (bug 1684776) Issue to note in i386: ubuntu_kvm_smoke_test - Unable to start KVM, timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ltp_syscalls - fanotify07 won't fix (bug 1775165) fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) fcntl35 / fcntl35_64 (bug 1774394) fanotify09 (bug 1775153) fanotify10 (bug 1802454) keyctl02 (bug 1798022) keyctl06 (bug 1798025) openat03 (bug 1798027) request_key03 (bug 1798052) Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_kvm_smoke_test - no supported architecture for 'hvm' (bug 1752550) ubuntu_ltp_syscalls - fanotify07 won't fix (bug 1775165) fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) fanotify09 (bug 1775153) fanotify10 (bug 1802454) keyctl02 (bug 1798022) keyctl06 (bug 1798025) open14 (bug 1798061) openat03 (bug 1798027) prctl04 (bug 1836839) readahead02 (bug 1836845) ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846250 Title: trusty/linux: 3.13.0-174.225 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833396] Re: ubuntu_bpf test failed on KVM kernels
*** This bug is a duplicate of bug 1848005 *** https://bugs.launchpad.net/bugs/1848005 Bug split into: D: 3 tests in test_verifier failed (bug 1848005) test_maps failed with sockmap creation (bug 1848004) B: test_maps failed with sockmap creation (bug 1848004) ** This bug has been marked a duplicate of bug 1848005 3 tests in test_verifier from ubuntu_bpf failed with D-KVM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833396 Title: ubuntu_bpf test failed on KVM kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1833396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790855] Re: [MIR] gpsd
3.19-2 is now in Debian/unstable and will soon sync to Ubuntu. That means the changes in 3.18 to resolve the packaging issues are in too. Thanks Bernd for all the work. In addition 3.19 has an apparmor profile and while 3.18 added py3 3.19 now dropped py2 which makes this a clear MIR ack now. It already is on the security Teams list, lets also reflect that in the bug assignment. ** Changed in: gpsd (Ubuntu) Assignee: MIR approval team (ubuntu-mir) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790855 Title: [MIR] gpsd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1790855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841956] Re: ubuntu_sysdig fails on kvm kernels
** Changed in: ubuntu-kernel-tests 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/1841956 Title: ubuntu_sysdig fails on kvm kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1841956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812318] Re: ftrace test in ubuntu_kernel_selftests failed on KVM kernels
Could be found in E-kvm 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/1812318 Title: ftrace test in ubuntu_kernel_selftests failed on KVM kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
The fix is now in upstream. Please refer to the patch for justification: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=1099f48457d06b816359fb43ac32a4a07e33219b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812318] Re: ftrace test in ubuntu_kernel_selftests failed on KVM kernels
Solved on B-kvm with the following commit for bug 1841956: UBUNTU: [Config] linux-kvm: CONFIG_FTRACE=y ** Changed in: ubuntu-kernel-tests Status: Confirmed => Fix Released ** Changed in: linux-kvm (Ubuntu Bionic) Status: Confirmed => Fix Released ** No longer affects: linux-kvm (Ubuntu Cosmic) ** Changed in: linux-kvm (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/1812318 Title: ftrace test in ubuntu_kernel_selftests failed on KVM kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Hi @cyphermox, I have tested with F12 on my Alienware Alpha: * F12 * Select Windows Boot Manager * Goes straight to grub So no difference regardless of which boot option I select. How was the installation done? I installed Ubuntu 19.04 the upgraded to 19.10. Here's my disk layout: ~> sudo parted /dev/sda print Model: ATA Samsung SSD 860 (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 1049kB 512MB 511MB fat32 boot, esp 2 512MB 513GB 512GB ext4 3 513GB 513GB 16.8MB Microsoft reserved partition msftres 4 513GB 1000GB 488GB ntfs Basic data partition msftdata Could you please describe how the disk was partitioned for dual-booting, and the steps taked in the installer? I can't remember exactly what I did, as it was quite a while ago. However, the basic steps were: * Install Ubuntu using 512GB * Install Win10 into the remaining space * Boot the Ubuntu usb and chroot into the installed ubuntu and re-install grub there. Is there any extra info you want me to collect about my PC? -- 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 longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848404] Re: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking
Diff of the manifest between 14 and 15 ** Description changed: - Ubuntu (and all flavors) 19.10 20191016 + Ubuntu (and all flavors) 19.10 20191015 + + Last known good build: 20191014 Test Case 1. Boot the ubiquity-dm 2. Select "Install Ubuntu" 3. On the wifi page configure a wifi connection Actual result This crash Expected result connection established successfully. == Original description == Install to bare metal. T430 and nv56r laptops connecting to wireless networks that have been used in prior ISO testing. Installer hangs after entering password. After several minutes installer will crash from Wireless screen and drop to desktop. Am able to click on desktop icon and complete installation from there. Crash screen appears. Installer has encountered an unrecoverable error. More details to come ** Patch added: "20191014-20191015.manifest.diff" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848404/+attachment/5297838/+files/20191014-20191015.manifest.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848404 Title: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848460] 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/1848460 Title: no touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846130] Re: xenial/linux-hwe: 4.15.0-66.75~16.04.1 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/sKXoCKll/167-xenial-hwe-linux- image-4150-66-generic-4150-667516041 ** Changed in: kernel-sru-workflow/certification-testing 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/1846130 Title: xenial/linux-hwe: 4.15.0-66.75~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723392] Re: Please update backuppc to 4.x release (now 4.2.1) - major improvements and lots of bugfixes
** Bug watch added: github.com/backuppc/backuppc/issues #206 https://github.com/backuppc/backuppc/issues/206 ** Also affects: backuppc via https://github.com/backuppc/backuppc/issues/206 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723392 Title: Please update backuppc to 4.x release (now 4.2.1) - major improvements and lots of bugfixes To manage notifications about this bug go to: https://bugs.launchpad.net/backuppc/+bug/1723392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
** Changed in: linux (Ubuntu) Status: Won't Fix => 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/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822309] Re: vmx_apic_passthrough_thread in kvm_unit_tests failed with X-KVM
Found on B-kvm as well. Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_apic_passthrough_thread' BUILD_HEAD=e2c275c4 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.hVGn3USjeg -smp 2 -cpu host,+vmx -m 2048 -append vmx_apic_passthrough_thread_test # -initrd /tmp/tmp.nbOg8fbs4J enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_apic_passthrough_thread_test FAIL: x86/vmx_tests.c:7705: Assertion failed: (0) == ((int)ioapic_read_redir(0xf).remote_irr) LHS: 00 - ''''''''''''''' - 0 RHS: 0x0001 - '''''''''''''''0001 - 1 IOAPIC pass-through: remote_irr=0 after EOI STACK: 4085ae 4085c6 4015bd 403aea 400312 SUMMARY: 5 tests, 1 unexpected failures FAIL vmx_apic_passthrough_thread (5 tests, 1 unexpected failures) ** Tags added: 4.15 bionic ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: sru-20190930 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822309 Title: vmx_apic_passthrough_thread in kvm_unit_tests failed with X-KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827866] Re: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X-KVM
** Tags added: 4.15 4.4 ** Tags added: sru-20190930 ** Summary changed: - vmx_apicv_test in ubuntu_kvm_unit_tests failed on X-KVM + vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827866 Title: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822308] Re: vmx_hlt_with_rvi_test in kvm_unit_tests fails
** Also affects: linux-kvm (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/1822308 Title: vmx_hlt_with_rvi_test in kvm_unit_tests fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826181] Re: Add DMIC support to oem-kernel
for the UCM config file in #7, you also can get it from this PPA (Bionic, Disco, Eoan supported): https://launchpad.net/~xueshengyao/+archive/ubuntu/dmic/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826181 Title: Add DMIC support to oem-kernel To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1826181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784535] Re: ubuntu_quota_smoke_test failed with KVM kernel
** Changed in: ubuntu-kernel-tests 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/1784535 Title: ubuntu_quota_smoke_test failed with KVM kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1784535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846130] Re: xenial/linux-hwe: 4.15.0-66.75~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846131 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Thursday, 03. October 2019 22:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: xenial/linux-deeplens: bug 1846128 xenial/linux-hwe-edge: bug 1846127 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846130 Title: xenial/linux-hwe: 4.15.0-66.75~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846454] Re: laptop mode tools gui cannot be opened through the start menu
Also the Debian package beginning with "buster" is newer than the Ubuntu one: https://packages.debian.org/buster/laptop-mode-tools I have downloaded the package and installed it by hand on Ubuntu 18.04 LTS. The start menu link gets updated to show up the pkexec form and the GUI seems to have been ported from Qt4 to Qt5. So far so good everything seems to be working now! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846454 Title: laptop mode tools gui cannot be opened through the start menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1846454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835858] Re: [needs-packaging] backport-iwlwifi-dkms
Hello, your repo version (8042) is working perfectly fine on Ubuntu 19.10 with kernel 5.3.0-18-generic, thank you for your work, really appreciate. Note that the official version (7906) wasn't compiling too on eoan. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835858 Title: [needs-packaging] backport-iwlwifi-dkms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1835858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848468] [NEW] package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: »neues lxd-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück
Public bug reported: Following an lxd upgrade abort due to non-reachable snap repo. ===> Aborting at user request dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/lxd_1%3a0.7_all.deb (--unpack): »neues lxd-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück invoke-rc.d: could not determine current runlevel Vorbereitung zum Entpacken von .../libisns0_0.97-3_amd64.deb ... Entpacken von libisns0:amd64 (0.97-3) über (0.97-2build1) ... Vorbereitung zum Entpacken von .../open-iscsi_2.0.874-5ubuntu15_amd64.deb ... Entpacken von open-iscsi (2.0.874-5ubuntu15) über (2.0.874-5ubuntu2.7) ... ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/lxd.0.crash' Vorbereitung zum Entpacken von .../poppler-data_0.4.9-2_all.deb ... Entpacken von poppler-data (0.4.9-2) über (0.4.8-2) ... Vorbereitung zum Entpacken von .../libss2_1.44.6-1ubuntu0.1_amd64.deb ... Entpacken von libss2:amd64 (1.44.6-1ubuntu0.1) über (1.44.1-1ubuntu1.2) ... Fehler traten auf beim Bearbeiten von: /var/cache/apt/archives/lxd_1%3a0.7_all.deb Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 19.04 Package: lxd 3.0.3-0ubuntu1~18.04.1 ProcVersionSignature: Microsoft 4.4.0-18362.1-Microsoft 4.4.35 Uname: Linux 4.4.0-18362-Microsoft x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 11:04:46 2019 Dmesg: [0.004059] Microsoft 4.4.0-18362.1-Microsoft 4.4.35 ErrorMessage: »neues lxd-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.6ubuntu1.1 apt 1.8.3 SourcePackage: lxd Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: »neues lxd-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to disco on 2019-10-17 (0 days ago) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848468 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: »neues lxd-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1848468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830675] Re: hackbench01 / hackbench02 from sched test suite in LTP failed with KVM kernel
hackbench02 failed with the same error message on B-4.15 KVM: tag=hackbench02 stime=1571094873 dur=1 exit=exited stat=255 core=no cu=0 cs=4 startup='Mon Oct 14 23:14:33 2019' Running with 20*40 (== 800) tasks. pthread_create failed: Resource temporarily unavailable (11) ** Summary changed: - hackbench01 from sched test suite in LTP failed with KVM kernel + hackbench01 / hackbench02 from sched test suite in LTP failed with KVM kernel ** Tags added: 4.15 ** Tags added: sru-20190930 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830675 Title: hackbench01 / hackbench02 from sched test suite in LTP failed with KVM kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848460] Re: no touchpad
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc3/ Which has this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=37d960a4d7536 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848460 Title: no touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848404] Re: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking
** Also affects: casper (Ubuntu) Importance: Undecided Status: New ** Changed in: casper (Ubuntu Eoan) Status: New => Triaged ** Changed in: casper (Ubuntu Eoan) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848404 Title: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1848404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
I have exactly the same problem too with the same computer. I also have ubuntu on a dual boot with Windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723392] Re: Please update backuppc to 4.x release (now 4.2.1) - major improvements and lots of bugfixes
** Changed in: backuppc Status: Unknown => 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/1723392 Title: Please update backuppc to 4.x release (now 4.2.1) - major improvements and lots of bugfixes To manage notifications about this bug go to: https://bugs.launchpad.net/backuppc/+bug/1723392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848367] Re: Disco update: upstream stable patchset 2019-10-16
** Changed in: linux (Ubuntu Disco) Status: In Progress => 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/1848367 Title: Disco update: upstream stable patchset 2019-10-16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847590] Re: Check for CPU Measurement sampling
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) 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/1847590 Title: Check for CPU Measurement sampling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1847590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847590] Re: Check for CPU Measurement sampling
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: In Progress => 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/1847590 Title: Check for CPU Measurement sampling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1847590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed
affecting B-4.15 KVM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829979 Title: memcg_max_usage_in_bytes from controllers test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758243] Re: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0
@Rocko Hello, Thank you for your help. Unfortunately your solution isn't working for me. I enabled the "NVIDIA On-Demand" parameter from nvidia-settings, then restarted my computer and exported all the env variables. I tried to launch a game, CS:GO for example, and when I type "mat_info" to see on which graphic chip it started, it tells me "Intel Graphics 630". It is starting on my Nvidia chip only if I force it in "PRIME Profiles" from nvidia-settings panel. Maybe if I make an "Application Profile" for all the programs that need graphic ressources I can get around the problem.. I run on a Dell XPS 15 7590, with Ubuntu 19.10 installed and kernel 5.3.0-18-generic. The installed Nvidia driver is 435.21-0ubuntu2. If someone have a suggestion, please let me know :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758243 Title: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723392] Re: Please update backuppc to 4.x release (now 4.2.1) - major improvements and lots of bugfixes
FYI: I pinged on the Debian ITP to get an idea if/who worked on this already and to which amount. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723392 Title: Please update backuppc to 4.x release (now 4.2.1) - major improvements and lots of bugfixes To manage notifications about this bug go to: https://bugs.launchpad.net/backuppc/+bug/1723392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847967] Re: oem kernel packages treated differently from generic kernel ones
So before the merge proposal[1] is accepted, you can take following
steps to file a bug with all the information for kernel packages:
1. find out the source package name for the binary kernel package. It
should be "linux-signed-oem[-osp1]" for signed kernel packages, and
"linux-oem[-osp1]" for unsigned ones.
$ apt show ${pkg} | grep ^Source:
2. create symlinks for apport:
$ sudo ln -s source_linux.py /usr/share/apport/package-
hooks/source_${srcpkg}.py
3. appport-bug ${pkg}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847967
Title:
oem kernel packages treated differently from generic kernel ones
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847967/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847590] Re: Check for CPU Measurement sampling
** Changed in: ubuntu-z-systems Status: In Progress => 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/1847590 Title: Check for CPU Measurement sampling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1847590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847139] Re: [linux-azure] Request of mainline commit f73f8a504e27 in azure 16.04 and 18.04
** Changed in: linux-azure (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux-azure (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/1847139 Title: [linux-azure] Request of mainline commit f73f8a504e27 in azure 16.04 and 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1847139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package xse
There is no upgrading issue when using nvidia-graphics-drivers-430 430.50-0ubuntu1~0.18.04.3 on ppa:albertomilone/lp1847979. However xserver-xorg-video-nvidia-418 is removed and xserver-xorg-video-nvidia-430 is not installed. ** Attachment added: "apt.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1847979/+attachment/5297876/+files/apt.log ** Changed in: oem-priority Status: Triaged => 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/1847979 Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848404] Re: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking
When booting live, there is a delay of 1 min 30 seconds (tested in Kubuntu, Lubuntu and Xubuntu, but not in standard Ubuntu. It can be seen when booted (live) without 'quiet splash'. I think the delay is caused by the logic concerning wifi, and I suspect that it is connected to the issue of this bug report. There is a bug report with more details about the delay issue at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848404 Title: ubiquity crashes on wireless installation with gi.repository.GLib.GError: nm-manager-error-quark: Not authorized to control networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1848404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848473] [NEW] cgroup_fj_stress_* in controllers from ubuntu_ltp failed with dir creation / fork on B-KVM
Public bug reported: It looks like the test failed with cannot fork, and the following test will failed with mkdir. Take this one for example: tag=cgroup_fj_stress_perf_event_2_9_each stime=1571098406 dur=7 exit=exited stat=2 core=no cu=451 cs=280 ... ... cgroup_fj_stress_perf_event_2_9_each 1 TINFO: Attaching task 1326 to /sys/fs/cgroup/perf_event/ltp/2/1/1/2/1/2/1 cgroup_fj_stress_perf_event_2_9_each 1 TINFO: Attaching task 1329 to /sys/fs/cgroup/perf_event/ltp/2/1/1/2/1/2/1/1 /opt/ltp/testcases/bin/cgroup_fj_stress.sh: 53: /opt/ltp/testcases/bin/cgroup_fj_stress.sh: Cannot fork tag=cgroup_fj_stress_perf_event_10_3_each stime=1571098419 dur=2 exit=exited stat=2 core=no cu=134 cs=84 startup='Tue Oct 15 00:13:39 2019' cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Subsystem perf_event is mounted at /sys/fs/cgroup/perf_event cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Creating subgroups ... mkdir: cannot create directory ‘/sys/fs/cgroup/perf_event/ltp’: File exists cgroup_fj_stress_perf_event_10_3_each 1 TBROK: mkdir /sys/fs/cgroup/perf_event/ltp failed cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Removing all ltp subgroups... Failed test cases sorted alphabetically: cgroup_fj_stress_blkio_10_3_each-mkdir cgroup_fj_stress_blkio_2_9_each -cannot fork cgroup_fj_stress_cpu_10_3_each -mkdir cgroup_fj_stress_cpu_2_9_each -cannot fork cgroup_fj_stress_cpuacct_10_3_each -mkdir cgroup_fj_stress_cpuacct_2_9_each -cannot fork cgroup_fj_stress_cpuset_10_3_each -mkdir cgroup_fj_stress_cpuset_2_9_each-cannot fork cgroup_fj_stress_devices_10_3_each -mkdir cgroup_fj_stress_devices_2_9_each -cannot fork cgroup_fj_stress_freezer_10_3_each -mkdir cgroup_fj_stress_freezer_2_9_each -cannot fork cgroup_fj_stress_hugetlb_10_3_each -mkdir cgroup_fj_stress_hugetlb_2_9_each -cannot fork cgroup_fj_stress_memory_10_3_each -mkdir cgroup_fj_stress_memory_2_9_each-cannot fork cgroup_fj_stress_net_cls_10_3_each -mkdir cgroup_fj_stress_net_cls_2_9_each -cannot fork cgroup_fj_stress_net_prio_10_3_each -mkdir cgroup_fj_stress_net_prio_2_9_each -cannot fork cgroup_fj_stress_perf_event_10_3_each -mkdir cgroup_fj_stress_perf_event_2_9_each-cannot fork ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: 4.15 bionic linux-kvm sru-20190930 ubuntu-ltp ** Tags added: 4.15 bionic linux-kvm ubuntu-ltp ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags added: sru-20190930 ** Also affects: linux-kvm (Ubuntu Bionic) 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/1848473 Title: cgroup_fj_stress_* in controllers from ubuntu_ltp failed with dir creation / fork on B-KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package xse
Regarding comment #5, xserver-xorg-video-nvidia-430 depends on xserver-xorg-core so it is not installed. This platform is using xserver-xorg-core-hwe-18.04 instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847979 Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847297] Re: bionic/linux-hwe-edge: 5.3.0-18.19~18.04.2 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1847298 packages: main: linux-hwe-edge meta: linux-meta-hwe-edge signed: linux-signed-hwe-edge phase: Ready for Promote to Proposed phase-changed: Wednesday, 16. October 2019 21:47 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847297 Title: bionic/linux-hwe-edge: 5.3.0-18.19~18.04.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848476] [NEW] [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all
Public bug reported: Ubuntu 18.04.3 LTS The sound works until I plug the headphones and then it never works again, even without them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.3.6-050306-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniela2692 F pulseaudio /dev/snd/pcmC0D0c: daniela2692 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 11:03:37 2019 InstallationDate: Installed on 2019-09-18 (28 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1426 F pulseaudio daniela2692 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX534FT.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX534FT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX534FT.204:bd06/10/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX534FT_UX534FT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX534FT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX534FT_UX534FT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848476 Title: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1848476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848475] [NEW] TB with Gnome - main window size problem
Public bug reported:
New TB w. 19.10 shows unpleasant behaviour:
- dragging non-maximized window to top left left does not resize to
half-screen-width anymore
- it is not possible to resize width below about 2 third of screen width
Any hints on this?
Kind regards, dsto
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: thunderbird 1:68.1.2+build1-0ubuntu1
Uname: Linux 4.20.0-042000-generic x86_64
NonfreeKernelModules: binder_linux ashmem_linux
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
BuildID: 20191010144232
Channel: Unavailable
CurrentDesktop: GNOME
Date: Thu Oct 17 11:58:37 2019
DefaultProfileIncompatibleExtensions: Thunderbird (default) -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
DefaultProfilePrefSources: prefs.js
EcryptfsInUse: Yes
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2018-02-05 (618 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MostRecentCrashID: bp-f3e38668-9150-40db-9571-9d7bd0180523
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
Profile1PrefSources: prefs.js
Profile1Prefs:
extensions.lastAppVersion: "68.0" (prefs.js)
security.sandbox.plugin.tempDirSuffix: "c50f1684-95ba-4509-b70d-60a988a5f236"
(prefs.js)
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=68.0/20190826194726 (Out of date)
Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/10/2018
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J01 v02.32
dmi.board.asset.tag: CZC1365RZ5
dmi.board.name: 1495
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC1365RZ5
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrJ01v02.32:bd05/10/2018:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq 8200 Elite SFF PC
dmi.product.sku: XL510AV
dmi.sys.vendor: Hewlett-Packard
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848475
Title:
TB with Gnome - main window size problem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1848475/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848047] Re: Eoan update: v5.3.5 upstream stable release
** Changed in: linux (Ubuntu Eoan) Status: Confirmed => 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/1848047 Title: Eoan update: v5.3.5 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848445] Re: Kernel needs a special workaround argument to boot
I just tested, without acpi_osi= , it freezes. I'd love to provide more details but as I said, it is just a blank screen with cursor, external HDD light is off, caps lock doesn't seem to work. uname -ar Linux ilgaz-HP-Pavilion-13-x360-PC 5.4.0-050400rc3-generic #201910132031 SMP Mon Oct 14 00:33:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848445 Title: Kernel needs a special workaround argument to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848080] Re: [snap] missing --temp-profile option
Implemented with https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from- source/commit/?id=0dbafa6a46fa94c4910cd4eb04068380bccce55b. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => 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/1848080 Title: [snap] missing --temp-profile option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848045] Re: Eoan update: v5.3.3 upstream stable release
** Changed in: linux (Ubuntu Eoan) Status: Confirmed => 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/1848045 Title: Eoan update: v5.3.3 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846790] Re: Saving files with a '#' in the name silently(!) fails on GVFS smb:// paths (Samba share)
Sure, here you go: https://bugs.documentfoundation.org/show_bug.cgi?id=128196. I've added some more info there as well, most importantly that LO will silently overwrite anything that already exists with the truncated name, e.g. trying to save "clobber#1.odt" will overwrite an existing "clobber". ** Bug watch added: Document Foundation Bugzilla #128196 https://bugs.documentfoundation.org/show_bug.cgi?id=128196 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846790 Title: Saving files with a '#' in the name silently(!) fails on GVFS smb:// paths (Samba share) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1846790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1758243] Re: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0
Hi! I thought NVIDIA On-demand would be enabled with the next version of xserver. Wouldn't it? Marcos Alano Linux System Administrator marcoshal...@gmail.com On Thu, Oct 17, 2019, 06:41 Mathieu Reho <1758...@bugs.launchpad.net> wrote: > @Rocko > > Hello, > Thank you for your help. Unfortunately your solution isn't working for me. > I enabled the "NVIDIA On-Demand" parameter from nvidia-settings, then > restarted my computer and exported all the env variables. I tried to launch > a game, CS:GO for example, and when I type "mat_info" to see on which > graphic chip it started, it tells me "Intel Graphics 630". > It is starting on my Nvidia chip only if I force it in "PRIME Profiles" > from nvidia-settings panel. > Maybe if I make an "Application Profile" for all the programs that need > graphic ressources I can get around the problem.. > > I run on a Dell XPS 15 7590, with Ubuntu 19.10 installed and kernel > 5.3.0-18-generic. > The installed Nvidia driver is 435.21-0ubuntu2. > > If someone have a suggestion, please let me know :) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1758243 > > Title: > bumblebee needs configuration changes to work with nvidia-driver-390 > and libglvnd0 > > Status in bumblebee package in Ubuntu: > Confirmed > > Bug description: > bumblebee fails to work in Ubuntu 18.04 with nvidia-driver-390 unless > these configuration changes are made: > > 1. For optirun to work, /etc/bumblebee/bumblebee.conf needs two > library paths changed (because of the changes for GLVND): > > [driver-nvidia] > LibraryPath=/usr/lib/x86_64-linux-gnu:/usr/lib/i386-linux-gnu > > XorgModulePath=/usr/lib/x86_64-linux-gnu/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules/input > > With these changes, optirun works correctly on my laptop (using the > primus bridge) but primusrun still fails. > > 2. For power management to work (ie turning the nvidia card off whilst > not in use), the nouveau and nvidia modules need blacklisting so they > don't load on boot, and nvidia_drm and nvidia_modeset need aliasing to > off so they never load. Otherwise, nvidia_drm attaches to > drm_kms_helper and then bumblebee can't unload the nvidia module and > turn off the card. This configuration file in /etc/modprobe.d/nvidia- > bl.conf works for me: > > blacklist nouveau > blacklist nvidia > blacklist nvidia_drm > blacklist nvidia_modeset > alias nouveau off > alias nvidia_drm off > alias nvidia_modeset off > > (The first two lines are already in bumblebee.conf. I found I also had > to alias nouveau to off because gdm?/mutter? so desperately wants to > load it.) > > Update: aliasing nouveau to off doesn't stop the nvidia-fallback > service from loading the nouveau module, so if nouveau is still > loading, you could try running this command: > > systemctl disable nvidia-fallback.service > > You'll need to reboot because nouveau is already loaded, but the > change should be permanent unless something else re-enables the > nvidia-fallback service. > > Finally, to run mesa applications, you need to set this variable: > > export __GLVND_DISALLOW_PATCHING=1 > > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: bumblebee 3.2.1-17 > Uname: Linux 4.16.0-041600rc6-generic x86_64 > ApportVersion: 2.20.8-0ubuntu10 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Mar 23 12:18:02 2018 > InstallationDate: Installed on 2017-08-16 (218 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > SourcePackage: bumblebee > UpgradeStatus: Upgraded to bionic on 2017-11-17 (125 days ago) > modified.conffile..etc.bumblebee.xorg.conf.nouveau: [modified] > modified.conffile..etc.bumblebee.xorg.conf.nvidia: [modified] > mtime.conffile..etc.bumblebee.bumblebee.conf: 2018-03-23T12:17:54.683287 > mtime.conffile..etc.bumblebee.xorg.conf.nouveau: > 2018-03-22T14:01:52.732698 > mtime.conffile..etc.bumblebee.xorg.conf.nvidia: > 2018-03-22T14:57:34.141995 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758243 Title: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848046] Re: Eoan update: v5.3.4 upstream stable release
The following patch has already been applied for bug #1847478: ipv6: do not free rt if FIB_LOOKUP_NOREF is set on suppress rule ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => 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/1848046 Title: Eoan update: v5.3.4 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790973] Re: Windows only move from one task bar to the other when the window is minimized
I also have this issue with an identical setup. Another thing I noticed is that when I move the window from monitor A to B, the button stays on A. When I move the window back from B to A, then the button suddenly appears on B (where the window isn't present anymore) but disappears from A (where the window is now). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790973 Title: Windows only move from one task bar to the other when the window is minimized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1790973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
