[Kernel-packages] [Bug 1794995] Re: 18.04 can't adjust brightness on ASUS T300F. Worked fine on 16.04.
If the system is upgraded from 16.04, there should be some older kernels still in your system. See if those kernels still work. -- 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/1794995 Title: 18.04 can't adjust brightness on ASUS T300F. Worked fine on 16.04. Status in linux package in Ubuntu: Invalid Bug description: Title of my display under Settings is "Unknown Display". I think there's no proper display driver for my laptop in this new distribution, "18.04", because the setting for my display works fine before I upgrade from 16.04. While I said "works fine", I meant, I could use the "fn" button plus with the brightness adjusting button, which is "f5" and "f6" on my laptop, to adjust the brightness. Other than the "fn" combination button not working, I can't even adjust the brightness in the setting and inside the main menu bar, which I think there might have since a control center is one of the features of this version upgrade. So, thanks for reading my problem, and please help, otherwise, it's so unhealthy for my eyes for looking at a screen with too bright for so long and I have to look at the screen for so long. Thanks in advance. Ps, in case it's needed, the model of my laptop is, ASUS T300F. A transform 2-in-one laptop. The fact that my laptop can "transform" might be the reason why I got this issue, the drive that serves all just fail to meet its needs. I'm sorry. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.17.0-041700rc3-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 28 21:44:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd] InstallationDate: Installed on 2018-04-04 (177 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: ASUSTeK COMPUTER INC. T300FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro quiet splash nomodeset vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300FA.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T300FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Fri Sep 28 21:43:24 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794995/+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 1806472] Re: RTL8822BE WiFi Disabled in Kernel 4.18.0-12
The drivers in staging won't get loaded when lockdown is enabled to provide safety. There's a list to override behavior though. The r8822be in its current form defaults to enable debugfs, which can be less secure as it exposes and extra interface to userspace. But we are not sure if the driver still works once the debugfs gets disabled, so please test this kernel: https://people.canonical.com/~khfeng/lp1806472/ Once we are sure r8822be still works when debugfs is disabled, we can include this fix to Cosmic. -- 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/1806472 Title: RTL8822BE WiFi Disabled in Kernel 4.18.0-12 Status in linux package in Ubuntu: Confirmed Bug description: ===SRU Justification=== [Impact] Realtek 8822be doesn't work under kernel lockdown. [Fix] Add r8822be.ko to signature-inclusion, so it can be signed and be loaded when lockdown is enabled. [Test] Since I can't signed the kernel so it's not tested. [Regression Potential] Low. The driver is maintained by a Realtek guy, so bugs are actually getting fixed. ===Original Bug Report=== Received kernel patch 4.18.0-12 today on my machine. On reboot my WiFi appears to be unavailable. lspci still recognises the installed RTL8822BE card and a reboot back to the previous kernel version (4.18.0-11) seems to resolve the problem. We tried some debugging in the IRC channel and didn't get very far. The r8822be module alias is intact, trying to modprobe it or insert results in a "operation not permitted" error. Modprobing mac80211 and cfg80211 which r8822be depends on did not seem to help. KMod Lists for -12 and -11 kernels: https://paste.ubuntu.com/p/pwx5mKszVt/ `ls -latr /lib/modules/4.18.0-12-*/ ; grep -i B822 /lib/modules/4.18.0-12-*/modules.alias` : https://paste.ubuntu.com/p/5zcCbXyM5g/ ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: callum 2989 F pulseaudio /dev/snd/controlC0: callum 2989 F pulseaudio CurrentDesktop: KDE Date: Mon Dec 3 19:27:16 2018 InstallationDate: Installed on 2018-11-10 (22 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 90H90015UK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=d5f81e09-382c-4759-8a6d-2503fe6959b4 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2018 dmi.bios.vendor: LENOVO dmi.bios.version: O3FKT26A dmi.board.name: 36E1 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259620440547 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO3FKT26A:bd06/15/2018:svnLENOVO:pn90H90015UK:pvrLegionY720T-34ASU:rvnLENOVO:rn36E1:rvrSDK0J40709WIN3259620440547:cvnLENOVO:ct3:cvrNone: dmi.product.family: Legion Y720T-34ASU dmi.product.name: 90H90015UK dmi.product.sku: LENOVO_MT_90H9_BU_LENOVO_FM_Legion Y720T-34ASU dmi.product.version: Legion Y720T-34ASU dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806472/+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 1805631] Re: Freeze when usb-data-collision with usb-mouse
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v5.20-rc2 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc2/ -- 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/1805631 Title: Freeze when usb-data-collision with usb-mouse Status in linux package in Ubuntu: Confirmed Bug description: To my computer I have connected a USB-hub and to that I have attached a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes freezes completely and power button is the only escape. This happens when I scroll the mouse, press a button or moves the mouse (any event from the mouse). This can happen in any running program: Firefox, pdf-viewer, Libreoffice Writer... Most often this comes with my usb-to-ethernet LEDs switch off (during blink), but not always. Seems to be a collision event between my USB-mouse and USB-to-ethernet adapter, i.e mutex. An other computer without the USB-to-ethernet adapter never freezes. Configured in the same way. (I used Ubuntu 14.04 for a long time and this freeze never happened. In 18.04 this happens at least every two weeks. It is the same hardware.) $ uname -a Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 5276 F pulseaudio /dev/snd/controlC0: user 5276 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 MachineType: TOSHIBA SATELLITE Z30-B Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers wireshark WifiSyslog: _MarkForUpload: False dmi.bios.date: 04/09/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.20 dmi.board.asset.tag: 00 dmi.board.name: SATELLITE Z30-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.family: 00 dmi.product.name: SATELLITE Z30-B dmi.product.version: PT258E-007015N5 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805631/+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 1792134] Re: Upgrading to 4.15.0-33 caused the system to fail to boot
[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/1792134 Title: Upgrading to 4.15.0-33 caused the system to fail to boot Status in linux package in Ubuntu: Expired Bug description: A routine upgrade upgraded the kernel to 4.15.0-34 upon which the machine would not boot and instead booted to initramfs. Attempts to boot into recovery mode resulted in the error "Warning failed to connect to lvmetad. Falling back to device scanning." Reverting to 4.15.0-33 allowed me to boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: connor 4127 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 12:30:06 2018 HibernationDevice: RESUME=UUID=af5bdbd9-e688-4d55-a263-0d649f9b59d4 InstallationDate: Installed on 2018-07-23 (51 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HNS1KE00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET52W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HNS1KE00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET52W(1.30):bd03/20/2018:svnLENOVO:pn20HNS1KE00:pvrThinkPadX270:rvnLENOVO:rn20HNS1KE00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HNS1KE00 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792134/+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 1803340] Re: stuck on installing kernel
[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/1803340 Title: stuck on installing kernel Status in linux package in Ubuntu: Expired Bug description: installation is stuck on installing kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803340/+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 1811406] Re: linux: 4.18.0-14.15 -proposed tracker
** Description changed: 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 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- - phase: Packaging -- ready to package - phase-changed: Friday, 11. January 2019 16:29 UTC + phase: Packaging -- packaging in progress + phase-changed: Monday, 14. January 2019 02:04 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- 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/1811406 Title: linux: 4.18.0-14.15 -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 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 Cosmic: 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 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- phase: Packaging -- packaging in progress phase-changed: Monday, 14. January 2019 02:04 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811406/+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 1811406] Re: linux: 4.18.0-14.15 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.18.0-14.15 -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/1811406 Title: linux: 4.18.0-14.15 -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 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 Cosmic: 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 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- phase: Packaging -- ready to package phase-changed: Friday, 11. January 2019 16:29 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811406/+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 1811419] Re: linux: 4.15.0-44.47 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Description changed: 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 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 1811435 (linux-hwe-edge), bug 1811436 (linux-oracle) derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 (linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 (linux-kvm), bug 1811427 (linux-oracle) -- swm properties -- - phase: Packaging -- ready to package - phase-changed: Friday, 11. January 2019 16:31 UTC + phase: Packaging -- packaging in progress + phase-changed: Sunday, 13. January 2019 21:33 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- 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/1811419 Title: linux: 4.15.0-44.47 -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-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: 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 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 1811435 (linux-hwe-edge), bug 1811436 (linux-oracle) derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 (linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 (linux-kvm), bug 1811427 (linux-oracle) -- swm properties -- phase: Packaging -- packaging in progress phase-changed: Sunday, 13. January 2019 21:33 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811419/+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 1811419] Re: linux: 4.15.0-44.47 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.15.0-44.47 -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/1811419 Title: linux: 4.15.0-44.47 -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-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 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 1811435 (linux-hwe-edge), bug 1811436 (linux-oracle) derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 (linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 (linux-kvm), bug 1811427 (linux-oracle) -- swm properties -- phase: Packaging -- ready to package phase-changed: Friday, 11. January 2019 16:31 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811419/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
Same problem here: Lenovo ThinkPad T410s Intel i5 (1st gen, 2.53Ghz) NVidia NVS3100M graphics Kernel 4.4 in 16.04 idles at 35°C - 37°C (fresh, high-quality thermal paste applied a week ago). Kernel 4.15 in 18.04 idles at 48°C - 52°C. Only Dropbox and Megasync in the background; htop shows very low CPU use from these 2 apps. Overall system CPU usage (idle) doesn't go above 1.3% - 2% range. Same workflow from 16.04 + kernel 4.4 runs 20°C hotter in 18.04 + kernel 4.15. Regular operation with Chromium and Emacs drives temperature to 76°C - 80°C. Critical temperature is 95°C before shutdown. This is running really hot. -- 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/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 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.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.asset.tag: To be filled by O.E.M.
[Kernel-packages] [Bug 1805079] Re: click/pop noise in the headphone on several lenovo laptops
Hui Wang, BTW, in case the sound card distinguishes between headphone out and line out modes, thus may be relevant: my headphones have impedance of 70Ω. Vadim. -- 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/1805079 Title: click/pop noise in the headphone on several lenovo laptops Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] Lenovo told us that some linux uers reported headphone noise on Lenovo's website. After investigating, we found those Lenovo laptop mdoels all have the codec of alc285, and we can reproduce the noise problem too. [Fix] Don't use the DAC of headphone, let headphone share the DAC with speaker, the noise disappears. [Test Case] After applying this patch, we tested on Lenovo P52, P72, X1 carbon and X1 Yoda2, no noise anymore [Regression Potential] Low. This patch only apply to several lenovo machines, and after applying this patch, both speaker and headphone still work very well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079/+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 1811595] Re: 18.04 laggy login but works fine off of boot usb
A workaround I found from here (https://askubuntu.com/questions/1070862 /ubuntu-server-18-04-graphics-in-console-is-extremely-slow) sudo vim /etc/default/grub uncomment GRUB_GFXMODE=640x480 and change to GRUB_GFXMODE=1027x768 then sudo update-grub Next disable ast driver sudo vim /etc/modprobe.d/blacklist.conf append line blacklist ast then sudo update-initramfs -u reboot -- 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/1811595 Title: 18.04 laggy login but works fine off of boot usb Status in linux package in Ubuntu: Incomplete Bug description: Running 18.04 off a boot usb stick works flawlessly, however after a clean install the login screen is very laggy and once I enter my password the screen resolution is all messed up and unreadable. If I reboot and hold down shift to get the Grub menu and choose Advanced then recovery mode and then without altering anything I choose resume from the recovery menu and the login screen works perfectly. All system updates are done. System Specs Processor : Intel(R) Xeon(R) Silver 4110 CPU @ 2.10GHz Memory: 131656MB (2342MB used) Machine Type : Supermicro Operating System : Ubuntu 18.04.1 LTS Date/Time : Sun 13 Jan 2019 01:28:23 PM AST -Display- Resolution: 1024x768 pixels OpenGL Renderer : llvmpipe (LLVM 6.0, 256 bits) X11 Vendor: The X.Org Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811595/+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 1811595] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1811595 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811595 Title: 18.04 laggy login but works fine off of boot usb Status in linux package in Ubuntu: Incomplete Bug description: Running 18.04 off a boot usb stick works flawlessly, however after a clean install the login screen is very laggy and once I enter my password the screen resolution is all messed up and unreadable. If I reboot and hold down shift to get the Grub menu and choose Advanced then recovery mode and then without altering anything I choose resume from the recovery menu and the login screen works perfectly. All system updates are done. System Specs Processor : Intel(R) Xeon(R) Silver 4110 CPU @ 2.10GHz Memory: 131656MB (2342MB used) Machine Type : Supermicro Operating System : Ubuntu 18.04.1 LTS Date/Time : Sun 13 Jan 2019 01:28:23 PM AST -Display- Resolution: 1024x768 pixels OpenGL Renderer : llvmpipe (LLVM 6.0, 256 bits) X11 Vendor: The X.Org Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811595/+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 1810108] Re: Failure to boot as QEMU guest when using -device virtio-vga, virgl=true
I can no longer reproduce this with newer Xubuntu Bionic Daily images, the guest is booting normally with 4.15.0-43. -- 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/1810108 Title: Failure to boot as QEMU guest when using -device virtio-vga,virgl=true Status in linux package in Ubuntu: Incomplete Bug description: Installed Xubuntu 18.04 in a QEMU virtual machine using -device virtio-vga,virgl=true fails to boot. Even setting to output boot messages to a serial console no messages appear as if it never tried to boot at all. What makes this strange is that the live media works correctly using -device virtio-vga,virgl=true, but then, on reboot, the installed system fails to boot. To make the guest work it's required to remove the option ,virgl=true from the command line. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Sun Dec 30 17:33:21 2018 InstallationDate: Installed on 2018-12-30 (0 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20181230) IwConfig: ens2 no wireless extensions. lono wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 virtiodrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=15c2a9cf-1159-4e4a-a06c-68ad2ad82d12 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810108/+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 1811595] [NEW] 18.04 laggy login but works fine off of boot usb
Public bug reported: Running 18.04 off a boot usb stick works flawlessly, however after a clean install the login screen is very laggy and once I enter my password the screen resolution is all messed up and unreadable. If I reboot and hold down shift to get the Grub menu and choose Advanced then recovery mode and then without altering anything I choose resume from the recovery menu and the login screen works perfectly. All system updates are done. System Specs Processor : Intel(R) Xeon(R) Silver 4110 CPU @ 2.10GHz Memory : 131656MB (2342MB used) Machine Type: Supermicro Operating System: Ubuntu 18.04.1 LTS Date/Time : Sun 13 Jan 2019 01:28:23 PM AST -Display- Resolution : 1024x768 pixels OpenGL Renderer : llvmpipe (LLVM 6.0, 256 bits) X11 Vendor : The X.Org Foundation ** Affects: linux (Ubuntu) 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/1811595 Title: 18.04 laggy login but works fine off of boot usb Status in linux package in Ubuntu: New Bug description: Running 18.04 off a boot usb stick works flawlessly, however after a clean install the login screen is very laggy and once I enter my password the screen resolution is all messed up and unreadable. If I reboot and hold down shift to get the Grub menu and choose Advanced then recovery mode and then without altering anything I choose resume from the recovery menu and the login screen works perfectly. All system updates are done. System Specs Processor : Intel(R) Xeon(R) Silver 4110 CPU @ 2.10GHz Memory: 131656MB (2342MB used) Machine Type : Supermicro Operating System : Ubuntu 18.04.1 LTS Date/Time : Sun 13 Jan 2019 01:28:23 PM AST -Display- Resolution: 1024x768 pixels OpenGL Renderer : llvmpipe (LLVM 6.0, 256 bits) X11 Vendor: The X.Org Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811595/+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 1807375]
Created attachment 280449 Add IC_INFO(a99e, 826c) to load rtl8821c firmware With this patch, it has been working fine for a week using Bluetooth mouse. Other things tested: - File transfer - A2DP Source -- 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/1807375 Title: Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev 826c, hci ver 0008 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 13.388386] Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev 826c, hci ver 0008 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 08:30:39 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807375/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"
** Attachment added: "trace.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+attachment/5228879/+files/trace.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/1803929 Title: Summary: Kernel bug (unhandled paging request) on "udisksctl power- off" Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 uname -a Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Steps (1) to reproduce: 1) Plug in a USB3 hard drive. 2) Right click on launcher icon. 3) Select "Safely Remove". After finding this: https://askubuntu.com/a/532691 ...the following steps also reproduce the problem. Steps (2) to reproduce: 1) Plugin in a USB3 hard drive. 2) udisksctl unmount -b /dev/sdXY 3) udisksctl power-off -b /dev/sdX System completely locks and becomes unresponsive, such that even the Magic SysRq key combination does nothing. Most of the time the fans on my laptop go crazy (so the CPU must get stuck in some loop), but once they did not and the system was just locked (without the fans going nuts). I can't get a textual copy of the kernel bug log (because I have to do a hard reset to regain control of the system and the output doesn't get flushed to disk), but I did manage to get a photo of some of it (please refer to attachment). --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio /dev/snd/controlC1: matt 2754 F pulseaudio /dev/snd/controlC0: matt 2754 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0 InstallationDate: Installed on 2016-04-23 (940 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Notebook N150SD/N155SD NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 RelatedPackageVersions: linux-restricted-modules-4.4.0-139-generic N/A linux-backports-modules-4.4.0-139-generic N/A linux-firmware 1.157.20 Tags: xenial Uname: Linux 4.4.0-139-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150SD/N155SD dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: N150SD/N155SD dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"
I was also able to reproduce this in kernels 4.4.0-139, -140 and -141. Kernel 4.4.0-138 worked fine. On kernel 4.4.0-140, the freeze didn't occur instantly but after about 20 seconds, so I was able to capture a stacktrace. -- 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/1803929 Title: Summary: Kernel bug (unhandled paging request) on "udisksctl power- off" Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 uname -a Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Steps (1) to reproduce: 1) Plug in a USB3 hard drive. 2) Right click on launcher icon. 3) Select "Safely Remove". After finding this: https://askubuntu.com/a/532691 ...the following steps also reproduce the problem. Steps (2) to reproduce: 1) Plugin in a USB3 hard drive. 2) udisksctl unmount -b /dev/sdXY 3) udisksctl power-off -b /dev/sdX System completely locks and becomes unresponsive, such that even the Magic SysRq key combination does nothing. Most of the time the fans on my laptop go crazy (so the CPU must get stuck in some loop), but once they did not and the system was just locked (without the fans going nuts). I can't get a textual copy of the kernel bug log (because I have to do a hard reset to regain control of the system and the output doesn't get flushed to disk), but I did manage to get a photo of some of it (please refer to attachment). --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio /dev/snd/controlC1: matt 2754 F pulseaudio /dev/snd/controlC0: matt 2754 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0 InstallationDate: Installed on 2016-04-23 (940 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Notebook N150SD/N155SD NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 RelatedPackageVersions: linux-restricted-modules-4.4.0-139-generic N/A linux-backports-modules-4.4.0-139-generic N/A linux-firmware 1.157.20 Tags: xenial Uname: Linux 4.4.0-139-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150SD/N155SD dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: N150SD/N155SD dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
Same symptoms here and no nvidia GPU, only "simple" Intel. Since this version, temp is very high. Between 70 and 80 by default, and up to 90 and more with a youtube video and even more with a 3D game like Minetest… and then it shutdowns (like max 5-10min on Minetest). It was clearly not the case with previous versions. Last year I remember watching hours of videos or playing hours of Tuxracer or Minetest with my son, and no overheating nor shutdowns. Never. Processeur : Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz Mémoire : 12180MB (4073MB utilisé) Machine Type: Notebook Systeme d'exploitation : Ubuntu 18.04.1 LTS Résolution : 1600x900 pixels OpenGL Renderer : Mesa DRI Intel(R) Ivybridge Mobile X11 Vendor : The X.Org Foundation -- 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/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 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.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups:
[Kernel-packages] [Bug 1811578] [NEW] package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.1
Public bug reported: After a sequence of the following commands: nvidia-smi Command 'nvidia-smi' not found, but can be installed with: sudo apt install nvidia-340 sudo apt install nvidia-utils-390 - sudo apt install nvidia-340 (installed) sudo apt install nvidia-utils-390 (not installed - error) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-utils-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: libcuda1-340:amd64: Remove nvidia-opencl-icd-340:amd64: Remove libnvidia-compute-390:amd64: Install nvidia-utils-390:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Jan 13 12:14:10 2019 ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107-0ubuntu0.18.04.1 InstallationDate: Installed on 2019-01-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107-0ubuntu0.18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1811578 Title: package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107-0ubuntu0.18.04.1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: After a sequence of the following commands: nvidia-smi Command 'nvidia-smi' not found, but can be installed with: sudo apt install nvidia-340 sudo apt install nvidia-utils-390 - sudo apt install nvidia-340 (installed) sudo apt install nvidia-utils-390 (not installed - error) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-utils-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: libcuda1-340:amd64: Remove nvidia-opencl-icd-340:amd64: Remove libnvidia-compute-390:amd64: Install nvidia-utils-390:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Jan 13 12:14:10 2019 ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107-0ubuntu0.18.04.1 InstallationDate: Installed on 2019-01-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107-0ubuntu0.18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1811578/+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 262408] Re: SysRq key equivalent needed
** Description changed: MacBook keyboards and other Apple keyboards lack a SysRq key and therefore lack important kernel functionality that is designed to save catastrophic data loss if the computer freezes. An equivalent keystroke should be assigned, for example Fn + Eject, to preserve the functionality of the Magic SysRq key in linux on a Mactel. I believe this is a bug and not a feature request because the current implementation assumes that all keyboards have a SysRq key which is an incorrect assumption and therefore a mistake, or bug. + + Workaround: + https://askubuntu.com/a/896806/21005 -- 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/262408 Title: SysRq key equivalent needed Status in Mactel Support: New Status in linux package in Ubuntu: Confirmed Bug description: MacBook keyboards and other Apple keyboards lack a SysRq key and therefore lack important kernel functionality that is designed to save catastrophic data loss if the computer freezes. An equivalent keystroke should be assigned, for example Fn + Eject, to preserve the functionality of the Magic SysRq key in linux on a Mactel. I believe this is a bug and not a feature request because the current implementation assumes that all keyboards have a SysRq key which is an incorrect assumption and therefore a mistake, or bug. Workaround: https://askubuntu.com/a/896806/21005 To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/262408/+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 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.
@sforshee: No, wifi had been stable on Bionic before that. Somehow it seems quite stable again now. I got this laptop in September, so I installed Bionic directly. I have checked my syslog, and I don't see the microcode loading errors anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1804841 Title: iwlwifi Microcode SW error detected. Restarting 0x200. Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Bug description: This seems to be a return of an existing bug, in newer hardware and microcode versions. Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78) Firmware version: 34.0.1 Description:Ubuntu 18.04.1 LTS Frequent errors as soon as I connect to wifi: Microcode SW error detected. Restarting 0x200. Expected to happen: Great and stable wifi like a couple of weeks ago What happens: very slow, intermittent internet access, lots of ping loss Found a suggestion of a workaround: adding these lines to /etc/NetworkManager/NetworkManager.conf [device] wifi.scan-rand-mac-address=no These lines were already there, not added by me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode] ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 23 15:23:54 2018 Dependencies: InstallationDate: Installed on 2018-09-03 (81 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804841/+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 1811566] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1811566 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811566 Title: Backported commit breaks audio (fixed upstream) Status in linux package in Ubuntu: Incomplete Bug description: It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was backported to ubuntu's 4.18 kernel. That commit breaks audio for some devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are fixed, with patch on commit: 47148001ae12292984ba1b38d9babefb9a46cd3e ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty Bug reported: https://bugzilla.kernel.org/show_bug.cgi?id=201787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811566/+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 1811566] Re: Backported commit breaks audio (fixed upstream)
No need of logs, as is reported and fixed upstream ** Changed in: linux (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/1811566 Title: Backported commit breaks audio (fixed upstream) Status in linux package in Ubuntu: New Bug description: It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was backported to ubuntu's 4.18 kernel. That commit breaks audio for some devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are fixed, with patch on commit: 47148001ae12292984ba1b38d9babefb9a46cd3e ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty Bug reported: https://bugzilla.kernel.org/show_bug.cgi?id=201787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811566/+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 1811566] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1811566 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811566 Title: Backported commit breaks audio (fixed upstream) Status in linux package in Ubuntu: Incomplete Bug description: It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was backported to ubuntu's 4.18 kernel. That commit breaks audio for some devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are fixed, with patch on commit: 47148001ae12292984ba1b38d9babefb9a46cd3e ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty Bug reported: https://bugzilla.kernel.org/show_bug.cgi?id=201787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811566/+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 1811566] Re: Backported commit breaks audio (fixed upstream)
** Tags added: 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/1811566 Title: Backported commit breaks audio (fixed upstream) Status in linux package in Ubuntu: Incomplete Bug description: It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was backported to ubuntu's 4.18 kernel. That commit breaks audio for some devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are fixed, with patch on commit: 47148001ae12292984ba1b38d9babefb9a46cd3e ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty Bug reported: https://bugzilla.kernel.org/show_bug.cgi?id=201787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811566/+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 1811566] [NEW] Backported commit breaks audio (fixed upstream)
Public bug reported: It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was backported to ubuntu's 4.18 kernel. That commit breaks audio for some devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are fixed, with patch on commit: 47148001ae12292984ba1b38d9babefb9a46cd3e ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty Bug reported: https://bugzilla.kernel.org/show_bug.cgi?id=201787 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: audio kernel-bug regression ** Description changed: It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was - backported to 4.18 kernel. That commit breaks audio for some devices - (from 4.19 on). Now 4.19, 4.20, 5.0 are fixed, with patch on commit: + backported to ubuntu's 4.18 kernel. That commit breaks audio for some + devices (from 4.19 on). Now 4.19, 4.20, 5.0 are fixed, with patch on + commit: 47148001ae12292984ba1b38d9babefb9a46cd3e ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty - Bug reported: https://bugzilla.kernel.org/show_bug.cgi?id=201787 ** Description changed: It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was backported to ubuntu's 4.18 kernel. That commit breaks audio for some - devices (from 4.19 on). Now 4.19, 4.20, 5.0 are fixed, with patch on - commit: + devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are + fixed, with patch on commit: 47148001ae12292984ba1b38d9babefb9a46cd3e ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty Bug reported: https://bugzilla.kernel.org/show_bug.cgi?id=201787 -- 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/1811566 Title: Backported commit breaks audio (fixed upstream) Status in linux package in Ubuntu: Incomplete Bug description: It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was backported to ubuntu's 4.18 kernel. That commit breaks audio for some devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are fixed, with patch on commit: 47148001ae12292984ba1b38d9babefb9a46cd3e ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty Bug reported: https://bugzilla.kernel.org/show_bug.cgi?id=201787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811566/+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 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound
I did, it didn't work I forgot to mention -- 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/1810861 Title: USB type C audio adapter (from a Pixel 3) doesn't produce any sound Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I use a logitech z200 that works fine, i use it with a usb type c adapter that came with my pixel 3, my speakers arent shown at all in the settings or make sound, its not the usb c adapter because it works fine on my windows dual boot and has worked at one point on ubuntu, regardless of the fact that ubuntu has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i use lsusb, one of the results is google inc., which is my headphone adapter, i can tell because when i unplug it it goes away, even when i plug it into the 3.5 mm headphone jack it doesn't work, i don't know if im forgetting something or not, this is the second time im typing this because i accidentally closed the first tab of this, whats interesting, is now that i go to alsamixer, and press f6 i see option 1.Headphone Adapter, i select it and set the volume all the way up and go to something that makes audio and nothing happens, then i unplug it and see if it disappears, surely enough it does --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-21 (78 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 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.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/05/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.00 dmi.board.name: AB350 Gaming K4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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
