[Kernel-packages] [Bug 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen
** Attachment added: "Screenshot" https://bugs.launchpad.net/dellserver/+bug/1779605/+attachment/5158528/+files/PCCT_error.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779605 Title: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen Status in dellserver: New Status in linux package in Ubuntu: New Bug description: When installing and booting to Ubuntu 18.04 Server, we see this error being shown on screen (Attached Screenshot) Setup details- Take a DellEMC 14G server and start installation of Ubuntu 18.04 Server. Observe this message in #dmesg. Cosmetic error message, no functionality loss. Upstream patch details: https://www.spinics.net/lists/linux-acpi/msg81863.html Please include these in future builds of Ubuntu 18.04. Uploading the #dmesg logs. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1779605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779605] [NEW] [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen
Public bug reported: When installing and booting to Ubuntu 18.04 Server, we see this error being shown on screen (Attached Screenshot) Setup details- Take a DellEMC 14G server and start installation of Ubuntu 18.04 Server. Observe this message in #dmesg. Cosmetic error message, no functionality loss. Upstream patch details: https://www.spinics.net/lists/linux-acpi/msg81863.html Please include these in future builds of Ubuntu 18.04. Uploading the #dmesg logs. ** Affects: dellserver Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1779605/+attachment/5158527/+files/dmesg.txt ** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779605 Title: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen Status in dellserver: New Status in linux package in Ubuntu: New Bug description: When installing and booting to Ubuntu 18.04 Server, we see this error being shown on screen (Attached Screenshot) Setup details- Take a DellEMC 14G server and start installation of Ubuntu 18.04 Server. Observe this message in #dmesg. Cosmetic error message, no functionality loss. Upstream patch details: https://www.spinics.net/lists/linux-acpi/msg81863.html Please include these in future builds of Ubuntu 18.04. Uploading the #dmesg logs. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1779605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756092] Re: Screen freeze for some time when unlocking
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756092 Title: Screen freeze for some time when unlocking Status in gdm3 package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: When trying to unlock the machine, sometimes the screen freezes entirely (including mouse and keyboard input) for a long time either right away or after submitting the password. The freeze lasts for 10-20s, and sometimes the display goes into suspend. I've seen this behavior on both my computers, both fresh 18.04 installs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 15:09:26 2018 InstallationDate: Installed on 2018-02-25 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-11 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Tags: bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768225] Re: SD card not mounted
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768225 Title: SD card not mounted Status in linux package in Ubuntu: Expired Bug description: Ubuntu 18.04 after fresh install: HW: Macbook Pro Retina 13" SD cards are not recognized nor mounted. The sdhci driver is not loaded by default. Manual loading of sdhci and sdhci-pci does not make the SD card mount or be recognized (loading the driver is acknowledged in the syslog) Adding a configuration file under /etc/modprobe.d with options sdhci debug_quirks2=4 does not remedy the situation. (the cards and adapters tested work fine on other - older - Macs) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf 1636 F pulseaudio /dev/snd/controlC1: wolf 1636 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 1 13:05:54 2018 HibernationDevice: RESUME=UUID=539744c7-33c6-44da-a8b5-8bcf95f7845d InstallationDate: Installed on 2018-04-30 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756092] Re: Screen freeze for some time when unlocking
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756092 Title: Screen freeze for some time when unlocking Status in gdm3 package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: When trying to unlock the machine, sometimes the screen freezes entirely (including mouse and keyboard input) for a long time either right away or after submitting the password. The freeze lasts for 10-20s, and sometimes the display goes into suspend. I've seen this behavior on both my computers, both fresh 18.04 installs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 15:09:26 2018 InstallationDate: Installed on 2018-02-25 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-11 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Tags: bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778270] Re: hibernate/resume failure [non-free: wl] ubuntu 18.04
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778270 Title: hibernate/resume failure [non-free: wl] ubuntu 18.04 Status in linux package in Ubuntu: Fix Released Bug description: I have a problem that hibernation did not work correctly. After running "sudo pm-hibernate" and "sudo systemctl hibernate" commands the laptop swithced off, making me think that every thing was good. After rebooting it start as it was not hibernated. I did some research and tested some solutions but no luck. I did some tests that may help resolve this problem that I will attach them here. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3937 F pulseaudio majdis 4358 F pulseaudio Date: Fri Jun 22 21:31:38 2018 DuplicateSignature: hibernate/resume:Hewlett-Packard HP Pavilion g6 Notebook PC:F.34 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1527718789 Failure: hibernate/resume HibernationDevice: RESUME=UUID=68bfd3fc-e77d-406c-851d-acecfd2f3a12 InstallationDate: Installed on 2018-06-21 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterpreterPath: /usr/bin/python3.6 MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=4d8fb0a7-28ed-4aed-b0d8-9334257e7192 ro resume=UUID=/dev/68bfd3fc-e77d-406c-851d-acecfd2f3a12 no_console_suspend initcall_debug PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux Title: [Hewlett-Packard HP Pavilion g6 Notebook PC] hibernate/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/28/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1670 dmi.board.vendor: Hewlett-Packard dmi.board.version: 09.37 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.34:bd09/28/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1670:rvr09.37:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.version: 05931120461620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio devices no longer work
Can you 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767181 Title: Upgrade to Bionic and USB audio devices no longer work Status in linux package in Ubuntu: Confirmed Bug description: I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop for conference calls, hangouts, etc. Yesterday (and ever since I bought the device) I was able to use this device for audio output and input on Xenial. Today, after upgrading to Bionic, I am no longer able to use the device. Plugging it in shows that it's recognized correctly when plugging it into a USB3 port (via dmesg): [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420 [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00 [14133.075895] usb 3-2.1.4: USB disconnect, device number 5 [14145.362837] usb 3-2.4: USB disconnect, device number 7 [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 [14240.079238] usb 3-2.1.3: USB disconnect, device number 8 [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 And it appears on the USB bus: bladernr@galactica:~$ lsusb Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510 Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub And when I open the sound settings (I am using Unity 7) the Jabra device appears as both an available input and output device. However, when I select it, and try a test sound, the output STILL comes out of the desktop's line-out and NOT the USB audio device. Likewise, on the Input tab, if I select the Jabra, no sound is detected when I speak. Thinking this might be because I'm using a USB hub, I disconnected the hub and plugged the device in directly to an onboard USB3 port but the problem persists. The device appears as an available output and input source, but sound does not come out of it (it still comes out the line-out despite the fact I have selected the USB device) and no sound is detected when testing the input side. I also plugged in a USB webcam that has a built in microphone, LIke the Jabra Speak 510, my USB webcam Microphone appears as an available input device and like the Jabra, no sound is detected when I select the webcam microphone. USB audio seems to be completely inoperative on Bionic. Looking at the Sound Settings menu, I notice that the title changes with each device I choose, however it does NOT change when I choose the USB devices. See attached screen shots for more info there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic
[Kernel-packages] [Bug 1778323] Re: Touchpad doesn't work in 4.17 or later
Can you 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778323 Title: Touchpad doesn't work in 4.17 or later Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: Using the builds at http://kernel.ubuntu.com/~kernel-ppa/mainline/ I can successfully install and run 4.16.17 (Linux version 4.16.17-041617-generic (kernel@tangerine) (gcc version 7.3.0 (Ubuntu 7.3.0-23ubuntu2)) #201806201630 SMP Wed Jun 20 20:32:55 UTC 2018) but not 4.17.2 or 4.18-rc1. In the later ones, the touchpad does not work after boot and rebooting stalls: Jun 18 15:42:50 pkxps kernel: [ 242.366528] INFO: task systemd-udevd:309 blocked for more than 120 seconds. Jun 18 15:42:50 pkxps kernel: [ 242.366540] Not tainted 4.17.2-041702-generic #201806160433 Jun 18 15:42:50 pkxps kernel: [ 242.366545] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 18 15:42:50 pkxps kernel: [ 242.366551] systemd-udevd D0 309 273 0x8104 Jun 18 15:42:50 pkxps kernel: [ 242.366558] Call Trace: Jun 18 15:42:50 pkxps kernel: [ 242.366576] __schedule+0x291/0x870 Jun 18 15:42:50 pkxps kernel: [ 242.366582] ? __switch_to_asm+0x34/0x70 Jun 18 15:42:50 pkxps kernel: [ 242.366587] ? __switch_to_asm+0x40/0x70 Jun 18 15:42:50 pkxps kernel: [ 242.366596] ? get_work_pool+0x40/0x40 Jun 18 15:42:50 pkxps kernel: [ 242.366602] schedule+0x2c/0x80 Jun 18 15:42:50 pkxps kernel: [ 242.366609] schedule_timeout+0x1db/0x360 Jun 18 15:42:50 pkxps kernel: [ 242.366615] ? __schedule+0x299/0x870 Jun 18 15:42:50 pkxps kernel: [ 242.366623] ? get_work_pool+0x40/0x40 Jun 18 15:42:50 pkxps kernel: [ 242.366629] wait_for_completion+0xba/0x140 Jun 18 15:42:50 pkxps kernel: [ 242.366637] ? wake_up_q+0x80/0x80 Jun 18 15:42:50 pkxps kernel: [ 242.366645] flush_work+0x127/0x1e0 Jun 18 15:42:50 pkxps kernel: [ 242.366652] ? worker_detach_from_pool+0xa0/0xa0 Jun 18 15:42:50 pkxps kernel: [ 242.31] __cancel_work_timer+0x131/0x1b0 Jun 18 15:42:50 pkxps kernel: [ 242.39] cancel_delayed_work_sync+0x13/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366676] power_supply_unregister+0x37/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366682] devm_power_supply_release+0x11/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366692] release_nodes+0x110/0x1f0 Jun 18 15:42:50 pkxps kernel: [ 242.366701] devres_release_group+0x7c/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366718] wacom_remove+0xce/0x120 [wacom] Jun 18 15:42:50 pkxps kernel: [ 242.366733] hid_device_remove+0x55/0xb0 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366741] device_release_driver_internal+0x15b/0x220 Jun 18 15:42:50 pkxps kernel: [ 242.366751] ? __hid_bus_driver_added+0x40/0x40 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366760] ? hid_destroy_device+0x60/0x60 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366766] device_release_driver+0x12/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366771] device_reprobe+0x30/0x50 Jun 18 15:42:50 pkxps kernel: [ 242.366782] __hid_bus_reprobe_drivers+0x4b/0x60 [hid] Jun 18 15:42:50 pkxps kernel: [ 242.366793] bus_for_each_dev+0x74/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366803] __hid_bus_driver_added+0x2c/0x40 [hid] -- Jun 18 15:42:50 pkxps kernel: [ 242.366859] ? __vunmap+0x81/0xb0 Jun 18 15:42:50 pkxps kernel: [ 242.366867] ? _cond_resched+0x19/0x40 Jun 18 15:42:50 pkxps kernel: [ 242.366874] ? kmem_cache_alloc_trace+0xb8/0x1c0 Jun 18 15:42:50 pkxps kernel: [ 242.366883] ? do_init_module+0x27/0x209 Jun 18 15:42:50 pkxps kernel: [ 242.366892] do_init_module+0x5f/0x209 Jun 18 15:42:50 pkxps kernel: [ 242.366900] load_module+0x1987/0x1f10 Jun 18 15:42:50 pkxps kernel: [ 242.366913] __do_sys_finit_module+0xfc/0x120 Jun 18 15:42:50 pkxps kernel: [ 242.366919] ? __do_sys_finit_module+0xfc/0x120 Jun 18 15:42:50 pkxps kernel: [ 242.366929] __x64_sys_finit_module+0x1a/0x20 Jun 18 15:42:50 pkxps kernel: [ 242.366936] do_syscall_64+0x5a/0x120 Jun 18 15:42:50 pkxps kernel: [ 242.366942] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 18 15:42:50 pkxps kernel: [ 242.366948] RIP:
[Kernel-packages] [Bug 1779358] Re: linux-aws: 4.15.0-1012.12 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1779358 Title: linux-aws: 4.15.0-1012.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1779354 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775016] 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775016 Title: [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and similar programs until reboot. Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: Ubuntu/Xubuntu 18.04 LTS bug What should have happened: Keyboard should have been working no matter the processes What happened instead: Keyboard stops working in the middle of typing when running firefox and when running the terminal as (sudo su) and similar programs. I cannot even type a password. Keyboard only works again after a reboot. xserver-xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-input-all: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Jun 4 22:13:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0493] InstallationDate: Installed on 2018-06-04 (0 days ago) InstallationMedia: Moment Plus OS amd64 2.5.6 "Aethereal" MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=13c4faa3-4e88-42db-b523-8ac6c7a793f8 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0X8R3Y dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0X8R3Y:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779358] Re: linux-aws: 4.15.0-1012.12 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.15.0-1012.12 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1779358 Title: linux-aws: 4.15.0-1012.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1779354 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775016] Re: [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and simi
** Summary changed: - Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and similar programs until reboot. + [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and similar programs until reboot. ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775016 Title: [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and similar programs until reboot. Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Ubuntu/Xubuntu 18.04 LTS bug What should have happened: Keyboard should have been working no matter the processes What happened instead: Keyboard stops working in the middle of typing when running firefox and when running the terminal as (sudo su) and similar programs. I cannot even type a password. Keyboard only works again after a reboot. xserver-xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-input-all: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Jun 4 22:13:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0493] InstallationDate: Installed on 2018-06-04 (0 days ago) InstallationMedia: Moment Plus OS amd64 2.5.6 "Aethereal" MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=13c4faa3-4e88-42db-b523-8ac6c7a793f8 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0X8R3Y dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0X8R3Y:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-bluetooth (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779361] Re: linux-gcp: 4.15.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1779361 Title: linux-gcp: 4.15.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1779354 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779485] Re: bluetooth not saving mouse connection. Having to reconnect each ubuntu start.
*** This bug is a duplicate of bug 1779289 *** https://bugs.launchpad.net/bugs/1779289 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1779289, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1779289 [regression] bluetooth mouse not reconnected on reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779485 Title: bluetooth not saving mouse connection. Having to reconnect each ubuntu start. Status in bluez package in Ubuntu: New Bug description: Each time I start Ubuntu, I have to turn the mouse on. Version 18.04 is not saving the setting. I don't remember having this problem with previous versions of Ubuntu. Last version I used was 16.04.4. Please fix, it's really annoying. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 12:39:30 2018 InstallationDate: Installed on 2018-06-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Sony Corporation VPCSC41FM ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=3bf4784c-157a-4e30-a49b-8f1a34d4f64c ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: INSYDE dmi.bios.version: R2087H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSC41FM:pvrC60A8X35:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCSC41FM dmi.product.version: C60A8X35 dmi.sys.vendor: Sony Corporation hciconfig: hci0:Type: Primary Bus: USB BD Address: 64:27:37:CA:4D:B1 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:16064 acl:815 sco:0 events:143 errors:0 TX bytes:6645 acl:47 sco:0 commands:81 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775016] Re: Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and similar programs until reb
And yes, no usb wireless keyboard, and no usb mouse and keyboard combo. Only a Rapoo wireless mouse (white) and a laptop keyboard in Dell Latitude E6420. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775016 Title: Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and similar programs until reboot. Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu/Xubuntu 18.04 LTS bug What should have happened: Keyboard should have been working no matter the processes What happened instead: Keyboard stops working in the middle of typing when running firefox and when running the terminal as (sudo su) and similar programs. I cannot even type a password. Keyboard only works again after a reboot. xserver-xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-input-all: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Jun 4 22:13:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0493] InstallationDate: Installed on 2018-06-04 (0 days ago) InstallationMedia: Moment Plus OS amd64 2.5.6 "Aethereal" MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=13c4faa3-4e88-42db-b523-8ac6c7a793f8 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0X8R3Y dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0X8R3Y:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779363] Re: linux-kvm: 4.15.0-1013.13 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.15.0-1013.13 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1779363 Title: linux-kvm: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1779354 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775016] Re: Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and similar programs until reb
I'm using a laptop keyboard alone. No USB Keyboard, only a Rapoo wireless mouse. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775016 Title: Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and similar programs until reboot. Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu/Xubuntu 18.04 LTS bug What should have happened: Keyboard should have been working no matter the processes What happened instead: Keyboard stops working in the middle of typing when running firefox and when running the terminal as (sudo su) and similar programs. I cannot even type a password. Keyboard only works again after a reboot. xserver-xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-input-all: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Jun 4 22:13:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0493] InstallationDate: Installed on 2018-06-04 (0 days ago) InstallationMedia: Moment Plus OS amd64 2.5.6 "Aethereal" MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=13c4faa3-4e88-42db-b523-8ac6c7a793f8 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0X8R3Y dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0X8R3Y:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775016] Re: Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and similar programs until reb
Please also clarify what kind of keyboard is failing. Is it wireless? Is it USB wired? Is it built-in? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775016 Title: Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and similar programs until reboot. Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu/Xubuntu 18.04 LTS bug What should have happened: Keyboard should have been working no matter the processes What happened instead: Keyboard stops working in the middle of typing when running firefox and when running the terminal as (sudo su) and similar programs. I cannot even type a password. Keyboard only works again after a reboot. xserver-xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-input-all: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Jun 4 22:13:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0493] InstallationDate: Installed on 2018-06-04 (0 days ago) InstallationMedia: Moment Plus OS amd64 2.5.6 "Aethereal" MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=13c4faa3-4e88-42db-b523-8ac6c7a793f8 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0X8R3Y dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0X8R3Y:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779361] Re: linux-gcp: 4.15.0-1011.11 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 4.15.0-1011.11 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1779361 Title: linux-gcp: 4.15.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1779354 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779289] Re: bluetooth mouse not reconeected on reboot
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Summary changed: - bluetooth mouse not reconeected on reboot + [regression] bluetooth mouse not reconeected on reboot ** Summary changed: - [regression] bluetooth mouse not reconeected on reboot + [regression] bluetooth mouse not reconnected on reboot ** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Bug description: This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Note that if the workarounds at the top of this bug don't work for you then you're subscribed to the wrong bug. In that case, please open a new one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772610] Re: Adding back alx WoL feature
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772610 Title: Adding back alx WoL feature Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The WoL feature is a must to pass Energy Star 6.1 and above. The power consumption will be measured during S3 with WoL is enabled. [Test case] Verified pass on new Dell machines without the wake up issue. [Regression potential] No regression. We disable this feature by default, so the driver behavior will be the same. We'll leave this feature disabled by default before we can fix the unintentional wake up issue. [Misc] Upstream maintainer insists to fix the wake up issue before we can add this feature back to the driver, so make the patch stay in Ubuntu kernel only. We'll verify WoL on every new machines and try to fix this issue when we encounter it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1772610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734242] Re: Intel 9260/9462/9560 driver support
** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1734242 Title: Intel 9260/9462/9560 driver support Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-oem source package in Xenial: Fix Released Bug description: Some new 9260/9462/9560 module doesn't work on artful kernel(v4.13) and require some commits They are https://marc.info/?l=linux-wireless=151076478931107=2 https://marc.info/?l=linux-wireless=151082205418762=2 https://marc.info/?l=linux-wireless=151082213518769=2 Those commits have not been merged into iwlwifi-next yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776333] Re: linux: 4.13.0-46.51 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-artful ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776333 Title: linux: 4.13.0-46.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776335 (linux-gcp), bug 1776336 (linux-hwe), bug 1776337 (linux-oem) derivatives: bug 1776334 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776340] Re: linux-oem: 4.15.0-1009.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1776340 Title: linux-oem: 4.15.0-1009.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1776338 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776337] Re: linux-oem: 4.13.0-1031.35 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1776337 Title: linux-oem: 4.13.0-1031.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1776333 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776338] Re: linux: 4.15.0-24.26 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776338 Title: linux: 4.15.0-24.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776346 (linux-azure), bug 1776347 (linux-azure-edge), bug 1776348 (linux-hwe-edge) derivatives: bug 1776339 (linux-raspi2), bug 1776340 (linux-oem), bug 1776341 (linux-aws), bug 1776342 (linux-azure), bug 1776344 (linux-gcp), bug 1776345 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776345] Re: linux-kvm: 4.15.0-1012.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1776345 Title: linux-kvm: 4.15.0-1012.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1776338 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776344] Re: linux-gcp: 4.15.0-1010.10 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1776344 Title: linux-gcp: 4.15.0-1010.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1776338 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776341] Re: linux-aws: 4.15.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1776341 Title: linux-aws: 4.15.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1776338 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776829] Re: linux-aws: 4.4.0-1062.71 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1776829 Title: linux-aws: 4.4.0-1062.71 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1776822 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776822] Re: linux: 4.4.0-130.156 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776822 Title: linux: 4.4.0-130.156 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776823 (linux-lts-xenial), bug 1776824 (linux-aws) derivatives: bug 1776357 (linux-euclid), bug 1776826 (linux-kvm), bug 1776359 (linux-raspi2), bug 1776361 (linux-snapdragon), bug 1776829 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776824] Re: linux-aws: 4.4.0-1024.25 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-trusty ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1776824 Title: linux-aws: 4.4.0-1024.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1776822 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776820] Re: linux-lts-trusty: 3.13.0-153.203~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-precise ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1776820 Title: linux-lts-trusty: 3.13.0-153.203~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1776819 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776819] Re: linux: 3.13.0-153.203 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-trusty ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776819 Title: linux: 3.13.0-153.203 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776820 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776826] Re: linux-kvm: 4.4.0-1029.34 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1776826 Title: linux-kvm: 4.4.0-1029.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1776822 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779354] Re: linux: 4.15.0-25.27 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.15.0-25.27 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779354 Title: linux: 4.15.0-25.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1779364 (linux-azure), bug 1779366 (linux-azure-edge), bug 1779367 (linux-gcp), bug 1779371 (linux-hwe), bug 1779372 (linux-hwe-edge) derivatives: bug 1779355 (linux-raspi2), bug 1779357 (linux-oem), bug 1779358 (linux-aws), bug 1779360 (linux-azure), bug 1779361 (linux-gcp), bug 1779363 (linux-kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754759] Re: LAN connection keeps connecting and disconnecting in an infinite loop
Markus Baumann: >"Does it make sense to try the mainline kernel, since the error is obviously fixed with 18.04?" No, it doesn't. Given you reproduced this in 17.10 (which is EOL July 2018 as per https://wiki.ubuntu.com/Releases ), when you upgrade soon to 18.04, the issue would be gone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754759 Title: LAN connection keeps connecting and disconnecting in an infinite loop Status in linux package in Ubuntu: Invalid Bug description: With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop: - Boot from live-ISO - Click on network icon in title bar and edit LAN-connection - Change MTU from Auto to 1492 - Connect LAN cable => LAN network keeps connecting and disconnecting in an infinite loop (No wireless network is configured.) The error did not occur on Xubuntu 16.04. The same situation occurs with Xubuntu installed on the SSD. I took the ISO for this bug report, in order to exclude wrong settings on the installed system. WORKAROUND: Don't adjust the MTU. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CasperVersion: 1.387 CurrentDesktop: XFCE Date: Fri Mar 9 20:26:21 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.110.120.1 dev enp0s25 proto static metric 100 10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 db135360-f229-3472-bd3a-eb8d6bc8b601 802-3-ethernet 1520627169 Fr 09 Mär 2018 20:26:09 UTC yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp0s25 activated /org/freedesktop/NetworkManager/ActiveConnection/32 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 db135360-f229-3472-bd3a-eb8d6bc8b601 /org/freedesktop/NetworkManager/ActiveConnection/32 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu3822 F pulseaudio CasperVersion: 1.387 DistroRelease: Ubuntu 17.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.110.120.1 dev enp0s25 proto static metric 100 10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) MachineType: LENOVO 2333B15 Package: network-manager 1.8.4-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 Tags: artful
[Kernel-packages] [Bug 1754759] Re: LAN connection keeps connecting and disconnecting in an infinite loop
Does it make sense to try the mainline kernel, since the error is obviously fixed with 18.04? Unfortunately, I also do not know how to try the mainline kernel. Can I test this with a live image (I do not want to destroy my production machine)? Is the mainline kernel compatible with 17.10? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754759 Title: LAN connection keeps connecting and disconnecting in an infinite loop Status in linux package in Ubuntu: Invalid Bug description: With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop: - Boot from live-ISO - Click on network icon in title bar and edit LAN-connection - Change MTU from Auto to 1492 - Connect LAN cable => LAN network keeps connecting and disconnecting in an infinite loop (No wireless network is configured.) The error did not occur on Xubuntu 16.04. The same situation occurs with Xubuntu installed on the SSD. I took the ISO for this bug report, in order to exclude wrong settings on the installed system. WORKAROUND: Don't adjust the MTU. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CasperVersion: 1.387 CurrentDesktop: XFCE Date: Fri Mar 9 20:26:21 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.110.120.1 dev enp0s25 proto static metric 100 10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 db135360-f229-3472-bd3a-eb8d6bc8b601 802-3-ethernet 1520627169 Fr 09 Mär 2018 20:26:09 UTC yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp0s25 activated /org/freedesktop/NetworkManager/ActiveConnection/32 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 db135360-f229-3472-bd3a-eb8d6bc8b601 /org/freedesktop/NetworkManager/ActiveConnection/32 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu3822 F pulseaudio CasperVersion: 1.387 DistroRelease: Ubuntu 17.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.110.120.1 dev enp0s25 proto static metric 100 10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) MachineType: LENOVO 2333B15 Package: network-manager 1.8.4-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 Tags: artful
[Kernel-packages] [Bug 1572132] Re: SMBv2+ does not show all files when mounting a windows share
** Changed in: cifs-utils (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1572132
Title:
SMBv2+ does not show all files when mounting a windows share
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in cifs-utils package in Debian:
Confirmed
Bug description:
When using the SMBv2 Protocol to mount a top level windows share (such
as C:\) not all files (or directories) are shown that exist on the
server side. Exactly 2 files are always missing...
Steps to reproduce:
On a windows7 PC (or Server) e.g. C:\ must be published as Share (must be top
level share - a subfolder like C:\data\ seems to work)
sudo mount -t cifs //SERVER/SHARE_NAME /mnt -o
domain=DOMAIN_NAME,username=${USER},uid=1000,gid=1000,nounix,vers=2.0
As a result always 2 Files (or directories) are missing in the mounted
directory of the ubuntu installation.
Seems to be a kernel bug (source tree: linux/fs/cifs).
The ubuntu versions I have checked:
Ubuntu 14.04LTS amd64
Ubuntu 15.10 amd64
Ubuntu 16.04 amd64
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.12
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Tue Apr 19 14:50:02 2016
InstallationDate: Installed on 2016-04-19 (0 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160417.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1572132/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
Bluetooth doesn't turn on, fresh install on formatted disk on Lenovo
G50, single OS.
lsusb | grep -i blue
Bus 002 Device 006: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth
4.0
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename: bionic
dmesg | grep -i blue
[ 15.902210] Bluetooth: Core ver 2.22
[ 15.902232] Bluetooth: HCI device and connection manager initialized
[ 15.902236] Bluetooth: HCI socket layer initialized
[ 15.902239] Bluetooth: L2CAP socket layer initialized
[ 15.902247] Bluetooth: SCO socket layer initialized
[ 15.916264] Bluetooth: hci0: don't support firmware rome 0x3101
[ 22.243557] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 22.243559] Bluetooth: BNEP filters: protocol multicast
[ 22.243563] Bluetooth: BNEP socket layer initialized
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764645
Title:
Bluetooth not working
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was discovered in Bionic. The regression was introduced by
mainline commit f44cb4b19ed4, which then made it's way into Bionic in
4.15.0-14 as commit c91729972ac6 via stable updates.
This regression is fixed by mainline commit 803cdb8ce584. Commit
803cdb8ce584 was also cc'd to stable. However, it has not landed in
upstream stable 4.15 or Bionic.
== Fix ==
803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012
models")
== Regression Potential ==
Low. This fix has also been cc'd to upstream stable, so it has had
additonal upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I've installed the Ubuntu Bionic Beta 2 and everything works fine but
the bluetooth (perfectly working with Xenial). In bluetooth control
panel the slider is impossible to move to "on".
1) Ubuntu Release (via 'lsb_release -rd')
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) Version of package (apt-cache policy gnome-bluetooth)
gnome-bluetooth:
Installato: 3.28.0-2
Candidato: 3.28.0-2
Tabella versione:
*** 3.28.0-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
I expected to switch on the bluetooth.
4) What happened instead
Bluetooth won't switch on.
5) Output of rfkill list is:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
Network Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
size Mini PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
Ethernet [1969:10a1] (rev 10)
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 17.715399] Bluetooth: Core ver 2.22
[ 17.715414] Bluetooth: HCI device and connection manager initialized
[ 17.715416] Bluetooth: HCI socket layer initialized
[ 17.715418] Bluetooth: L2CAP socket layer initialized
[ 17.715422] Bluetooth: SCO socket layer initialized
[ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
[ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.600649] Bluetooth: BNEP filters: protocol multicast
[ 18.600651] Bluetooth: BNEP socket layer initialized
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stormy 1484 F pulseaudio
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
In addition to my comment #53
uname -a
Linux system 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764645
Title:
Bluetooth not working
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was discovered in Bionic. The regression was introduced by
mainline commit f44cb4b19ed4, which then made it's way into Bionic in
4.15.0-14 as commit c91729972ac6 via stable updates.
This regression is fixed by mainline commit 803cdb8ce584. Commit
803cdb8ce584 was also cc'd to stable. However, it has not landed in
upstream stable 4.15 or Bionic.
== Fix ==
803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012
models")
== Regression Potential ==
Low. This fix has also been cc'd to upstream stable, so it has had
additonal upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I've installed the Ubuntu Bionic Beta 2 and everything works fine but
the bluetooth (perfectly working with Xenial). In bluetooth control
panel the slider is impossible to move to "on".
1) Ubuntu Release (via 'lsb_release -rd')
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) Version of package (apt-cache policy gnome-bluetooth)
gnome-bluetooth:
Installato: 3.28.0-2
Candidato: 3.28.0-2
Tabella versione:
*** 3.28.0-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
I expected to switch on the bluetooth.
4) What happened instead
Bluetooth won't switch on.
5) Output of rfkill list is:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
Network Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
size Mini PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
Ethernet [1969:10a1] (rev 10)
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 17.715399] Bluetooth: Core ver 2.22
[ 17.715414] Bluetooth: HCI device and connection manager initialized
[ 17.715416] Bluetooth: HCI socket layer initialized
[ 17.715418] Bluetooth: L2CAP socket layer initialized
[ 17.715422] Bluetooth: SCO socket layer initialized
[ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
[ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.600649] Bluetooth: BNEP filters: protocol multicast
[ 18.600651] Bluetooth: BNEP socket layer initialized
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stormy 1484 F pulseaudio
/dev/snd/controlC0: stormy 1484 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 17 08:46:30 2018
HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: ASUSTeK COMPUTER INC. G750JH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-15-generic N/A
[Kernel-packages] [Bug 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1804
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1776211
Title:
kdump fails to take dump with smt set to 2, hmc dumpstart
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in makedumpfile package in Ubuntu:
Incomplete
Status in linux source package in Artful:
In Progress
Status in makedumpfile source package in Artful:
Incomplete
Bug description:
== SRU Justification ==
IBM has requested these three commits in Artful. In Artful, kdump fails to
capture dump when smt=2 or off.
Including these three commits allows kdump to work properly.
== Fixes ==
4388c9b3a6ee ("powerpc: Do not send system reset request through the oops
path")
04b9c96eae72 ("powerpc/crash: Remove the test for cpu_online in the IPI
callback")
4552d128c26e ("powerpc: System reset avoid interleaving oops using die
synchronisation")
== Regression Potential ==
Low. Fixes are limited to powerpc.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
--Problem Description---
kdump fails to take dump with smt set to 2, hmc dumpstart
---Issue observed---
[0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
[0.004118] SMP NR_CPUS=2048
[0.004120] NUMA
[0.004125] pSeries
[0.004132] Modules linked in:
[0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic
#13-Ubuntu
[0.004153] task: c00046715900 task.stack: c00046134000
[0.004162] NIP: c0006468 LR: c801764c CTR:
006cdc70
[0.004173] REGS: c00047fe3ce0 TRAP: 0700 Not tainted
(4.13.0-12-generic)
[0.004181] MSR: 80081031
[0.004193] CR: 8804 XER: 2003
[0.004204] CFAR: c0006454 SOFTE: 0
[0.004204] GPR00: c801764c c00047fe3f60 c95e3000
[0.004204] GPR04: 0001 0002
ffdf
[0.004204] GPR08: 2804 0002
0002
[0.004204] GPR12: cfff c00046137f90
0b5452d8
[0.004204] GPR16: fffd 089ffd10 0136
0b55d378
[0.004204] GPR20: 0060 1eca 0a6c
0007
[0.004204] GPR24: c9621ed0
[0.004204] GPR28: c00046134000 c00046137c80
c9105df8
[0.004328] NIP [c0006468] 0xc0006468
[0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
[0.004345] Call Trace:
[0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0
(unreliable)
[0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
[0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
[0.004393] [c00046137c10] [c8008ac4]
hardware_interrupt_common+0x114/0x120
[0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
[0.004409] LR = arch_local_irq_restore+0x40/0x90
[0.004423] [c00046137f00] [0005] 0x5 (unreliable)
[0.004436] [c00046137f20] [c8049824]
start_secondary+0x324/0x350
[0.004450] [c00046137f90] [c800aa6c]
start_secondary_prolog+0x10/0x14
[0.004460] Instruction dump:
[0.004467]
[0.004484]
[0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
[0.004512]
[0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
[0.004525] SMP NR_CPUS=2048
[0.004526] NUMA
[0.004532] pSeries
[0.004540] Modules linked in:
[0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G D
4.13.0-12-generic #13-Ubuntu
[0.004561] task: c9579f00 task.stack: c95dc000
[0.004569] NIP: c0006460 LR: c80b6e80 CTR:
[0.004580] REGS: c95dfb20 TRAP: 0700 Tainted: G D
(4.13.0-12-generic)
[0.004589] MSR: 80081031
[0.004599] CR: 22002228 XER: 2004
[0.004611] CFAR: c000493c SOFTE: 0
[0.004611] GPR00: c95dfda0 c95e3000
[0.004611] GPR04:
[0.004611] GPR08: 22002228 7fff
0008
[0.004611] GPR12: cfff0a80 c00c7e137f90
[Kernel-packages] [Bug 1696049] Re: xfstest sanity checks on seek operations fails
** Tags removed: targetmilestone-inin16043 ** Tags added: targetmilestone-inin16044 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696049 Title: xfstest sanity checks on seek operations fails Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Bug description: == Comment: #0 - Harish Sriram Issue: -- xfstest fails with sanity checks on seek operations # uname -a Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with xfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.config for running with created loop device 5. Run xfstests-dev test : ./check tests/generic/285 or ./check tests/generic/436 The test 285 fails with following ... ... 07. Test file with unwritten extents, only have dirty pages 07.01 SEEK_HOLE expected 0 or 45056, got 0. succ 07.02 SEEK_HOLE expected 1 or 45056, got 1. succ 07.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 07.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08. Test file with unwritten extents, only have unwritten pages 08.01 SEEK_HOLE expected 0 or 45056, got 0. succ 08.02 SEEK_HOLE expected 1 or 45056, got 1. succ 08.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL The test 436 fails with ... ... 14. Test file with unwritten extents, small hole after pagevec dirty pages 14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ 14.04 SEEK_DATA expected 0 or 0, got 0. succ 14.05 SEEK_DATA expected 1 or 1, got 1. succ 14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ seek sanity check failed! Full log is attached. == Comment: #6 - Harish Sriram commit 5375023ae1266553a7baa0845e82917d8803f48c Author: Jan Kara Date: Thu May 18 16:36:22 2017 -0700 xfs: Fix missed holes in SEEK_HOLE implementation XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command: xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k" -c "seek -h 0" file wrote 57344/57344 bytes at offset 0 56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec) wrote 8192/8192 bytes at offset 131072 8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec) Whence Result HOLE139264 Where we can see that hole at offset 56k was just ignored by SEEK_HOLE implementation. The bug is in xfs_find_get_desired_pgoff() which does not properly detect the case when pages are not contiguous. Fix the problem by properly detecting when found page has larger offset than expected. CC: sta...@vger.kernel.org Fixes: d126d43f631f996daeee5006714fed914be32368 Signed-off-by: Jan Kara Reviewed-by: Brian Foster Reviewed-by: Darrick J. Wong Signed-off-by: Darrick J. Wong The above commit fixes the generic/436 test, but generic/285 still FAILS. The generic/285 failure is reproducible on most P8/P9 systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777194] Comment bridged from LTC Bugzilla
--- Comment From kalsh...@in.ibm.com 2018-07-01 10:35 EDT---
(In reply to comment #36)
> SRU request submitted:
> https://lists.ubuntu.com/archives/kernel-team/2018-June/093481.html
Do we get this fix added to 18.04.1 builds?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1777194
Title:
Hard LOCKUP observed on stressing Ubuntu 18 04
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
IBM has seen hard lockups when running stress tests against Bionic.
These test sometimes lead to rcu_stalls. IBM found that this bug is
resolved with commits 6bed3237624e and ac61c1156623.
== Fixes ==
6bed3237624e ("powerpc: use NMI IPI for smp_send_stop")
ac61c1156623 ("powerpc: Fix smp_send_stop NMI IPI handling")
== Regression Potential ==
Low. Limited to powerpc.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
--Problem Description--
Hard LOCKUP on stressing Ubuntu 18 04
---Issue observed---
Hard LOCKUP on stressing Ubuntu 18 04 using Ubuntu 18 04, sometimes leads to
rcu_stalls.
Apr 17 00:00:23 lep8d kernel: [ 4309.786755] Watchdog CPU:3 Hard LOCKUP
Apr 17 00:00:23 lep8d kernel: [ 4309.786759] Modules linked in: algif_rng
salsa20_generic userio camellia_generic cast6_generic cast_common snd_seq
snd_seq_device snd_timer snd soundcore vhost_net serpent_generic tap
twofish_generic twofish_common vhost_vsock vmw_vsock_virtio_transport_common
vhost vsock lrw unix_diag algif_skcipher cuse sctp tgr192 wp512 rmd320 rmd256
rmd160 hci_vhci rmd128 bluetooth ecdh_generic dccp_ipv4 md4 uhid hid algif_hash
dccp af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack
nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc
ebtable_filter ebtables devlink ip6table_filter ip6_tables iptable_filter
kvm_hv kvm binfmt_misc uio_pdrv_genirq uio vmx_crypto ibmpowernv
powernv_op_panel ipmi_powernv
Apr 17 00:00:23 lep8d kernel: [ 4309.786899] ipmi_devintf ipmi_msghandler
powernv_rng leds_powernv crct10dif_vpmsum sch_fq_codel ip_tables x_tables
autofs4 ses enclosure scsi_transport_sas btrfs xor zstd_compress raid6_pq uas
usb_storage crc32c_vpmsum tg3 ipr
Apr 17 00:00:23 lep8d kernel: [ 4309.786944] CPU: 3 PID: 28361 Comm:
stress-ng-hrtim Not tainted 4.15.0-15-generic #16-Ubuntu
Apr 17 00:00:23 lep8d kernel: [ 4309.786950] NIP: c0d0c8b8 LR:
c0120dbc CTR: c0024480
Apr 17 00:00:23 lep8d kernel: [ 4309.786956] REGS: c7f7fd80 TRAP:
0900 Not tainted (4.15.0-15-generic)
Apr 17 00:00:23 lep8d kernel: [ 4309.786957] MSR: 90009033
CR: 28000442 XER: 2000
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] CFAR: c0120db8 SOFTE: 0
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR00: c0120dbc
c02d51377ba0 c16eb400 c02d512b0f88
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR04:
0001 01f40668 0001
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR08: 0001
8003
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR12: c0024480
c7a22100 000186a0
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR16: 7fffed3687e0
0abda98e5db8 8005 00040100
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR20:
418004fc 003c 0843
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR24: c02d512b0f88
c02d51377d30 c02d52d47c00
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR28: c02d51377d50
c02d51377d50 c02d52f04500 c02d512b0f88
Apr 17 00:00:23 lep8d kernel: [ 4309.787035] NIP [c0d0c8b8]
_raw_spin_lock+0x38/0xe0
Apr 17 00:00:23 lep8d kernel: [ 4309.787045] LR [c0120dbc]
dequeue_signal+0xcc/0x260
Apr 17 00:00:23 lep8d kernel: [ 4309.787046] Call Trace:
Apr 17 00:00:23 lep8d kernel: [ 4309.787052] [c02d51377bd0]
[c0120dac] dequeue_signal+0xbc/0x260
Apr 17 00:00:23 lep8d kernel: [ 4309.787059] [c02d51377c20]
[c012459c] get_signal+0x13c/0x7a0
Apr 17 00:00:23 lep8d kernel: [ 4309.787066] [c02d51377d10]
[c001dacc] do_signal+0x7c/0x2c0
Apr 17 00:00:23 lep8d kernel: [ 4309.787072] [c02d51377e00]
[c001deb0] do_notify_resume+0xd0/0x100
Apr 17 00:00:23 lep8d kernel: [ 4309.787083] [c02d51377e30]
[c000b7c4] ret_from_except_lite+0x70/0x74
Apr 17 00:00:23 lep8d kernel: [ 4309.787085]
[Kernel-packages] [Bug 1778222] Re: Ubuntu LIVECD kernel panic
Additional information ** Attachment added: "kernel-4.11_dmidecode.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+attachment/5158334/+files/kernel-4.11_dmidecode.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778222 Title: Ubuntu LIVECD kernel panic Status in linux package in Ubuntu: Confirmed Bug description: I’ve encounter a problem, not sure if it’s a bug or an intentional change to the Linux kernel. I normally don’t mess with the kernel as suggested by many on the Internet. But with new releases of Linux Mint 19.0 or Ubuntu 18.04 out, I decided to try them with the new LiveCD’s. With Ubuntu now using Gnome, I decided to give the LiveCD for 18.04 a try since I haven’t used Ubuntu since Unity, but then ‘Bamm’ the boot of the LiveCD locks up with a kernel panic. So I tried the Linux Mint 19.0 LiveCD and had the same failure. Looking further at the problem I started installing different kernels in my Linux Mint 18.3 system. I found that my system will operate with different kernels up to an including 4.11. When I tried kernels 4.13 or 4.15 both failed to boot with the same kernel panic. Everything locks up and I have to do a power off, power on operation to recover. So kernel 4.11 is the last one I can use. I found that the LiveCD’s both use kernel 4.15 which does not work on my system. I have included a picture of the screen when the boot fails. Would like to use the latest versions but the kernel problem prevents me from doing so. This is my uname data: uname -a Linux 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I have the dmidecode data and the lspci data if needed for kernel 4.11.(From a good boot) With further testing I have found that, Linux Mint 19.0 LiveCD (in compatibility mode) or Ubuntu 18.04 LiveCD with the ‘noacpi’ option, will both boot into a usable live operating system. I’m afraid though that if I installed either to my hard drive that neither would boot. I would like to have help resolving this problem so I can continue to use Linux. Thanks! Ps.there are no newer bios updates for my computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778222] Re: Ubuntu LIVECD kernel panic
Additional info ** Attachment added: "kernel-4.11_lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+attachment/5158335/+files/kernel-4.11_lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778222 Title: Ubuntu LIVECD kernel panic Status in linux package in Ubuntu: Confirmed Bug description: I’ve encounter a problem, not sure if it’s a bug or an intentional change to the Linux kernel. I normally don’t mess with the kernel as suggested by many on the Internet. But with new releases of Linux Mint 19.0 or Ubuntu 18.04 out, I decided to try them with the new LiveCD’s. With Ubuntu now using Gnome, I decided to give the LiveCD for 18.04 a try since I haven’t used Ubuntu since Unity, but then ‘Bamm’ the boot of the LiveCD locks up with a kernel panic. So I tried the Linux Mint 19.0 LiveCD and had the same failure. Looking further at the problem I started installing different kernels in my Linux Mint 18.3 system. I found that my system will operate with different kernels up to an including 4.11. When I tried kernels 4.13 or 4.15 both failed to boot with the same kernel panic. Everything locks up and I have to do a power off, power on operation to recover. So kernel 4.11 is the last one I can use. I found that the LiveCD’s both use kernel 4.15 which does not work on my system. I have included a picture of the screen when the boot fails. Would like to use the latest versions but the kernel problem prevents me from doing so. This is my uname data: uname -a Linux 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I have the dmidecode data and the lspci data if needed for kernel 4.11.(From a good boot) With further testing I have found that, Linux Mint 19.0 LiveCD (in compatibility mode) or Ubuntu 18.04 LiveCD with the ‘noacpi’ option, will both boot into a usable live operating system. I’m afraid though that if I installed either to my hard drive that neither would boot. I would like to have help resolving this problem so I can continue to use Linux. Thanks! Ps.there are no newer bios updates for my computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778222] Re: Ubuntu LIVECD kernel panic
Additional information ** Attachment added: "kernel-4.11_kernel-log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+attachment/5158336/+files/kernel-4.11_kernel-log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778222 Title: Ubuntu LIVECD kernel panic Status in linux package in Ubuntu: Confirmed Bug description: I’ve encounter a problem, not sure if it’s a bug or an intentional change to the Linux kernel. I normally don’t mess with the kernel as suggested by many on the Internet. But with new releases of Linux Mint 19.0 or Ubuntu 18.04 out, I decided to try them with the new LiveCD’s. With Ubuntu now using Gnome, I decided to give the LiveCD for 18.04 a try since I haven’t used Ubuntu since Unity, but then ‘Bamm’ the boot of the LiveCD locks up with a kernel panic. So I tried the Linux Mint 19.0 LiveCD and had the same failure. Looking further at the problem I started installing different kernels in my Linux Mint 18.3 system. I found that my system will operate with different kernels up to an including 4.11. When I tried kernels 4.13 or 4.15 both failed to boot with the same kernel panic. Everything locks up and I have to do a power off, power on operation to recover. So kernel 4.11 is the last one I can use. I found that the LiveCD’s both use kernel 4.15 which does not work on my system. I have included a picture of the screen when the boot fails. Would like to use the latest versions but the kernel problem prevents me from doing so. This is my uname data: uname -a Linux 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I have the dmidecode data and the lspci data if needed for kernel 4.11.(From a good boot) With further testing I have found that, Linux Mint 19.0 LiveCD (in compatibility mode) or Ubuntu 18.04 LiveCD with the ‘noacpi’ option, will both boot into a usable live operating system. I’m afraid though that if I installed either to my hard drive that neither would boot. I would like to have help resolving this problem so I can continue to use Linux. Thanks! Ps.there are no newer bios updates for my computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778222] Re: Ubuntu LIVECD kernel panic
I went back and installed kernel 4.12.14 and it works fine so something definitely changed in kernel 4.13 that keeps my machine from booting. Attached is my CPU information, ** Attachment added: "Cpu info" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+attachment/5158333/+files/Cpu%20info -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778222 Title: Ubuntu LIVECD kernel panic Status in linux package in Ubuntu: Confirmed Bug description: I’ve encounter a problem, not sure if it’s a bug or an intentional change to the Linux kernel. I normally don’t mess with the kernel as suggested by many on the Internet. But with new releases of Linux Mint 19.0 or Ubuntu 18.04 out, I decided to try them with the new LiveCD’s. With Ubuntu now using Gnome, I decided to give the LiveCD for 18.04 a try since I haven’t used Ubuntu since Unity, but then ‘Bamm’ the boot of the LiveCD locks up with a kernel panic. So I tried the Linux Mint 19.0 LiveCD and had the same failure. Looking further at the problem I started installing different kernels in my Linux Mint 18.3 system. I found that my system will operate with different kernels up to an including 4.11. When I tried kernels 4.13 or 4.15 both failed to boot with the same kernel panic. Everything locks up and I have to do a power off, power on operation to recover. So kernel 4.11 is the last one I can use. I found that the LiveCD’s both use kernel 4.15 which does not work on my system. I have included a picture of the screen when the boot fails. Would like to use the latest versions but the kernel problem prevents me from doing so. This is my uname data: uname -a Linux 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I have the dmidecode data and the lspci data if needed for kernel 4.11.(From a good boot) With further testing I have found that, Linux Mint 19.0 LiveCD (in compatibility mode) or Ubuntu 18.04 LiveCD with the ‘noacpi’ option, will both boot into a usable live operating system. I’m afraid though that if I installed either to my hard drive that neither would boot. I would like to have help resolving this problem so I can continue to use Linux. Thanks! Ps.there are no newer bios updates for my computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio devices no longer work
Same as bladernr, the reboot helped me, but I don't think reboot should be necessary for USB plug-n-play devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767181 Title: Upgrade to Bionic and USB audio devices no longer work Status in linux package in Ubuntu: Confirmed Bug description: I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop for conference calls, hangouts, etc. Yesterday (and ever since I bought the device) I was able to use this device for audio output and input on Xenial. Today, after upgrading to Bionic, I am no longer able to use the device. Plugging it in shows that it's recognized correctly when plugging it into a USB3 port (via dmesg): [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420 [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00 [14133.075895] usb 3-2.1.4: USB disconnect, device number 5 [14145.362837] usb 3-2.4: USB disconnect, device number 7 [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 [14240.079238] usb 3-2.1.3: USB disconnect, device number 8 [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 And it appears on the USB bus: bladernr@galactica:~$ lsusb Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510 Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub And when I open the sound settings (I am using Unity 7) the Jabra device appears as both an available input and output device. However, when I select it, and try a test sound, the output STILL comes out of the desktop's line-out and NOT the USB audio device. Likewise, on the Input tab, if I select the Jabra, no sound is detected when I speak. Thinking this might be because I'm using a USB hub, I disconnected the hub and plugged the device in directly to an onboard USB3 port but the problem persists. The device appears as an available output and input source, but sound does not come out of it (it still comes out the line-out despite the fact I have selected the USB device) and no sound is detected when testing the input side. I also plugged in a USB webcam that has a built in microphone, LIke the Jabra Speak 510, my USB webcam Microphone appears as an available input device and like the Jabra, no sound is detected when I select the webcam microphone. USB audio seems to be completely inoperative on Bionic. Looking at the Sound Settings menu, I notice that the title changes with each device I choose, however it does NOT change when I choose the USB devices. See attached screen shots for more info there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 26 15:24:56 2018 InstallationDate: Installed on 2016-02-11 (805 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Kernel-packages] [Bug 159356] Re: System freeze on high memory usage when DMA is disabled
jecks (slayerproof32), it is most unhelpful to post comments or attachments here, or give pastebin links. If you want to motivate developers to want to look into your issue, file a new report. If you want developers to ignore your problem, continue posting here. marco (nazgul17), one may always file a report manually via https://bugs.launchpad.net/ubuntu/+source/linux/+filebug . For more on this, please see https://help.ubuntu.com/community/ReportingBugs . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
