[Kernel-packages] [Bug 1860253] Re: After kernel upgrade, the screen has got stuck when in running programs on GUI.
Hi, Ubuntu I did try to run the command as you told, but failed. Because the command tried to open up a new browser window but didn't work and got stuck. I want to provide the logs to reproduce the symptom but, can't for that reason. Thank you ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1860253 Title: After kernel upgrade, the screen has got stuck when in running programs on GUI. Status in linux package in Ubuntu: Confirmed Bug description: Hi, Ubuntu First of all, Ubuntu Version: 18.04.3 LTS Kernel Version: linux-image-5.0.0-37-generic H/W Info: Processor - AMD Phenom II X3 720 Chipset - NVIDIA GeForce 8200 Package Repository: JAIST (JP) Summary: A problem with Linux kernel linux-image-5.3.0-26-generic Today, I got a notice from update manager that there are some upgrade packages. So, I did press the button 'Upgrade'. After the upgrade, I reboot the machine and login as usual via gdm. To run web browser, I clicked Firefox icon but got stuck, also other apps like Settings. I did investigate what packages have updated and found out that the kernel package has upgraded to 5.3.0-26 from 5.0.0-37 So, I did boot up my machine with 5.0.0-37 instead 5.3.0-26 and the machine works very well. I hereby request you to investigate kernel package 5.3.0-26. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860253/+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 1860253] 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 1860253 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/1860253 Title: After kernel upgrade, the screen has got stuck when in running programs on GUI. Status in linux package in Ubuntu: Incomplete Bug description: Hi, Ubuntu First of all, Ubuntu Version: 18.04.3 LTS Kernel Version: linux-image-5.0.0-37-generic H/W Info: Processor - AMD Phenom II X3 720 Chipset - NVIDIA GeForce 8200 Package Repository: JAIST (JP) Summary: A problem with Linux kernel linux-image-5.3.0-26-generic Today, I got a notice from update manager that there are some upgrade packages. So, I did press the button 'Upgrade'. After the upgrade, I reboot the machine and login as usual via gdm. To run web browser, I clicked Firefox icon but got stuck, also other apps like Settings. I did investigate what packages have updated and found out that the kernel package has upgraded to 5.3.0-26 from 5.0.0-37 So, I did boot up my machine with 5.0.0-37 instead 5.3.0-26 and the machine works very well. I hereby request you to investigate kernel package 5.3.0-26. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860253/+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 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
same bug (apparently), killer 1435 QCA6174, upgraded board-2.bin and fimware-6.bin to the latest available on the ath10k but still experience disconnection, though with slightly more time in between drops (from every 1-5 minutes to once every 5-10) -- 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/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Released Status in linux-firmware source package in Artful: Fix Released Bug description: After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my WiFi would stop working after every 20 minutes or so. The problem initially seems related to some DNS services crashing because of what happend in browsers and other software that usually rely on DNS but I've noticed I couldn't ping my router and other local devices for which I knew the IP addresses. The connection is still presented as being connected, but it just doesn't work. After googling a lot, I came across this question on askubuntu.com https://askubuntu.com/questions/967355/wifi-unstable- after-17-10-update Which led me to this bug report on Debian's bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184 Which led me to this bug in upstream: http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html I've tested the proposed fixes myself and I can confirm they work. What causes the WiFi to stop working is a bug related to the group rekeying routines. It seems it only happens in >4.12 kernels, hence why I've only had problems after 4.13 was pushed as the current rolling HWE kernel for 16.04.3. kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1 of the firmware-6.bin file, which is the current one present in upstream. Updating the firmware-6.bin (and board-2.bin, optionally) to any version equal or later than that fixes the issue completely. - SRU Justification: [Impact] Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, silently stops working after the second group rekeying, which is usually few minutes after the user has connected to a WiFi network. The connection status remains unchanged but there's no connectivity at all. This effectively disconnects the user without notifying it of what's occurred. Additionally, this happens for the only HWE kernel that's been patched against the recent Meltdown vulnerability, leaving the user without the option of using a recent kernel and a secure kernel at the same time. [Test Case] After applying the required firmwares, check if the connectivity is unaffected after the second group rekeying, which can be checked with $ cat /var/log/syslog | grep wpa_.*rekeying [How to fix it] Update the firmware-6.bin file to version WLAN.RM.4.4.1-00051-QCARMSWP-1 or later. [Regression Potential] The new firmware overwrites the old one, but since it's been in upstream since October 2017, it should be good. - Description: Ubuntu 16.04.3 LTS Release: 16.04 linux-firmware: Instalado: 1.157.14 Candidato: 1.157.14 Tabela de versão: *** 1.157.14 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 1.157 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+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 988799]
I'm a professional web developer and you can checkout my portfolio on https://quyumshub.com;>Quyumshub and I also provide you with all latest online registration guides, web platform reviews and tech tutorials on https://registerhow.net;>Registerhow. I'm also the official blogger of the popular musician https://kissdaniel.com.ng;>Kizz Daniel. I love writing and here is one of my articles on https://registerhow.net/how-to- set-up-cash-app/">how to set up cash app, https://registerhow.net/recharge-and-get-paid-ragp-review-and- registration/">recharge and get paid review -- 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/988799 Title: Precise freezes under heavy i/o Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Whilst creating a VM with 20 GB persistent HD and my system froze until the disk was created. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gema 2526 F pulseaudio /dev/snd/controlC0: gema 2526 F pulseaudio /dev/snd/controlC1: gema 2526 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,104383c4,0010' Controls : 45 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:081d' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 16 Mono: Capture 12 [75%] [24.00dB] [on] Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Thu Apr 26 11:59:11 2012 HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IwConfig: lono wireless extensions. virbr0no wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days ago) dmi.bios.date: 03/26/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D-E LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd03/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/988799/+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 1860253] [NEW] After kernel upgrade, the screen has got stuck when in running programs on GUI.
Public bug reported: Hi, Ubuntu First of all, Ubuntu Version: 18.04.3 LTS Kernel Version: linux-image-5.0.0-37-generic H/W Info: Processor - AMD Phenom II X3 720 Chipset - NVIDIA GeForce 8200 Package Repository: JAIST (JP) Summary: A problem with Linux kernel linux-image-5.3.0-26-generic Today, I got a notice from update manager that there are some upgrade packages. So, I did press the button 'Upgrade'. After the upgrade, I reboot the machine and login as usual via gdm. To run web browser, I clicked Firefox icon but got stuck, also other apps like Settings. I did investigate what packages have updated and found out that the kernel package has upgraded to 5.3.0-26 from 5.0.0-37 So, I did boot up my machine with 5.0.0-37 instead 5.3.0-26 and the machine works very well. I hereby request you to investigate kernel package 5.3.0-26. Thank you ** 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/1860253 Title: After kernel upgrade, the screen has got stuck when in running programs on GUI. Status in linux package in Ubuntu: New Bug description: Hi, Ubuntu First of all, Ubuntu Version: 18.04.3 LTS Kernel Version: linux-image-5.0.0-37-generic H/W Info: Processor - AMD Phenom II X3 720 Chipset - NVIDIA GeForce 8200 Package Repository: JAIST (JP) Summary: A problem with Linux kernel linux-image-5.3.0-26-generic Today, I got a notice from update manager that there are some upgrade packages. So, I did press the button 'Upgrade'. After the upgrade, I reboot the machine and login as usual via gdm. To run web browser, I clicked Firefox icon but got stuck, also other apps like Settings. I did investigate what packages have updated and found out that the kernel package has upgraded to 5.3.0-26 from 5.0.0-37 So, I did boot up my machine with 5.0.0-37 instead 5.3.0-26 and the machine works very well. I hereby request you to investigate kernel package 5.3.0-26. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860253/+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 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 - xenial/linux-hwe: bug 1859704, bug 1860122 + xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs -- 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/1860123 Title: bionic/linux: 4.15.0-76.86 -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: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Confirmed 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+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 1860248] Re: No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after modprobe sof
** Description changed: - On the machine: + [Impact] + When we boot the kernel on a Dell machchine which has a discrete + nvidia graphic card, the sof driver will fail to initialize sometimes, + and after investigation, we found if let nvidia hdmi audio load the + codec driver first, the sof driver will fail to initialize 100%. - cd /lib/modules/5.0.0-1033-oem-osp1/kernel/sound/soc/sof + [Fix] + Intel release a patch to fix this issue, after applying this patch, + the sof driver could work even the nividia hdmi audio initializes + first. - mv sof-pci-dev.ko sof-pci-dev.ko-bak - sudo reboot + [Test Case] + We test this patch, the issue could be reproduced anymore in + 100 times reboot. - after booting up, please check nv hdmi, it is initialized successfully - (check /proc/asound/cards) - - Then cd /lib/modules/5.0.0-1033-oem-osp1/kernel/sound/soc/sof - - mv sof-pci-dev.ko-bak sof-pci-dev.ko - - sudo modprobe sof-pci-dev - - check dmesg, you will find the sof driver fails to initialize: - - skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: CODEC DAI intel-hdmi- - hifi1 not registered + [Regression Risk] + Low, Intel released the patch to us, and we already did large + numbers of audio test in the oem project. -- 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/1860248 Title: No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after modprobe sof Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] When we boot the kernel on a Dell machchine which has a discrete nvidia graphic card, the sof driver will fail to initialize sometimes, and after investigation, we found if let nvidia hdmi audio load the codec driver first, the sof driver will fail to initialize 100%. [Fix] Intel release a patch to fix this issue, after applying this patch, the sof driver could work even the nividia hdmi audio initializes first. [Test Case] We test this patch, the issue could be reproduced anymore in 100 times reboot. [Regression Risk] Low, Intel released the patch to us, and we already did large numbers of audio test in the oem project. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1860248/+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 620074]
I'm a professional web developer and you can checkout my portfolio on https://quyumshub.com;>Quyumshub and I also provide you with all latest online registration guides, web platform reviews and tech tutorials on https://registerhow.net;>Registerhow. I'm also the official blogger of the popular musician https://kissdaniel.com.ng;>Kizz Daniel. I love writing and here is one of my articles on https://registerhow.net/how-to- set-up-cash-app/">how to set up cash app, https://registerhow.net/recharge-and-get-paid-ragp-review-and- registration/">recharge and get paid review -- 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/620074 Title: Thrashing turns system unusable Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Thrashing on Ubuntu seems to make it almost impossible to interact with the system. It can be minutes before any interaction has an effect, including remote connections. This means that if a program either misbehaves or simply needs more memory than available RAM, it might be hard or impossible to stop it, either locally or remotely. This can be both an annoyance and a security threat (since a process without elevated privileges can effectively hang the system). It is not hard to make a system go into thrashing, especially if it is low on memory (that's probably true in general, not only of Ubuntu). On my ASUS netbook running Ubuntu 10.04, with only 1GB RAM, thrashing can occur as easily as running both Chromium (which is a bit of a memory hog) and the Resynthesizer plugin in the GIMP at the same time. Running these programs plus another memory-intensive program like Mathematica can generate thrashing even when 2GB or 4GB of physical memory are available. I am including a short C++ program that allocates and accesses a large amount of memory, guaranteeing thrashing will occur on any system. Using this or any other memory-intensive program, the steps required to reproduce the condition I described are 1. Start one or more memory-intensive programs. 2. As RAM is filled, paging will start, and if the programs try to access the memory that has been swapped out, thrashing occurs. What happens? - Interactivity with the system drops to almost zero. Mouse barely moves, keyboard interaction has huge delays (tens of seconds), starting a terminal or switching to one if one is already open can take minutes, as is the case with remote (e.g. SSH) connections. What I would expect/want to happen? - The system should keep interactivity levels high at all times. While I'm not at all an expert on this, I would think this could be achieved by either not allowing paging out of essential user-interface elements, or more generally by giving processes that generate a lot of page faults comparatively lower priority than other processes, especially processes that are just starting, or are part of the user interface. To use the included program, compile with g++ -o bug bug.cc and run with ./bug where is the amount of memory in MB to be allocated. One can run several instances of the program at the same time, to compete for memory. One can use top, free or the System Monitor to check when RAM is completely filled, and thrashing starts. PS: This seems to be a long-standing issue with Linux, it's not limited to the current version of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-24-generic 2.6.32-24.39 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tibi 1596 F pulseaudio /dev/snd/pcmC0D0p: tibi 1596 F...m pulseaudio /dev/snd/controlC1: tibi 1596 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfe02 irq 21' Mixer name : 'Nvidia MCP78 HDMI' Components : 'HDA:10ec0888,10250153,00100202 HDA:10de0002,10de0101,0010' Controls : 37 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x8da'/'USB Device 0x46d:0x8da at usb-:00:04.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB046d:08da' Controls : 3 Simple ctrls : 2 Date: Wed Aug 18 13:01:30 2010 HibernationDevice: RESUME=UUID=9464cfb9-e39a-46ab-bf3a-01a7f2194ab1 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: eMachines EL1210-09 ProcCmdLine:
[Kernel-packages] [Bug 1860248] 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 1860248 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/1860248 Title: No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after modprobe sof Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: On the machine: cd /lib/modules/5.0.0-1033-oem-osp1/kernel/sound/soc/sof mv sof-pci-dev.ko sof-pci-dev.ko-bak sudo reboot after booting up, please check nv hdmi, it is initialized successfully (check /proc/asound/cards) Then cd /lib/modules/5.0.0-1033-oem-osp1/kernel/sound/soc/sof mv sof-pci-dev.ko-bak sof-pci-dev.ko sudo modprobe sof-pci-dev check dmesg, you will find the sof driver fails to initialize: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: CODEC DAI intel-hdmi- hifi1 not registered To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1860248/+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 1860248] [NEW] No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after modprobe sof
Public bug reported: On the machine: cd /lib/modules/5.0.0-1033-oem-osp1/kernel/sound/soc/sof mv sof-pci-dev.ko sof-pci-dev.ko-bak sudo reboot after booting up, please check nv hdmi, it is initialized successfully (check /proc/asound/cards) Then cd /lib/modules/5.0.0-1033-oem-osp1/kernel/sound/soc/sof mv sof-pci-dev.ko-bak sof-pci-dev.ko sudo modprobe sof-pci-dev check dmesg, you will find the sof driver fails to initialize: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: CODEC DAI intel-hdmi- hifi1 not registered ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1858774 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: originate-from-1858774 somerville -- 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/1860248 Title: No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after modprobe sof Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: On the machine: cd /lib/modules/5.0.0-1033-oem-osp1/kernel/sound/soc/sof mv sof-pci-dev.ko sof-pci-dev.ko-bak sudo reboot after booting up, please check nv hdmi, it is initialized successfully (check /proc/asound/cards) Then cd /lib/modules/5.0.0-1033-oem-osp1/kernel/sound/soc/sof mv sof-pci-dev.ko-bak sof-pci-dev.ko sudo modprobe sof-pci-dev check dmesg, you will find the sof driver fails to initialize: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: CODEC DAI intel-hdmi- hifi1 not registered To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1860248/+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 1860172] Re: Crashes all the time
Recent updates seem to have fixed the issue. Its relatively stable again, besides the usual crashes in tf2 that probably get fixed with kernel 5.4 vega64 firmware. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1860172 Title: Crashes all the time Status in linux package in Ubuntu: Fix Released Bug description: Setup: ubuntu 19.10, x570-f motherboard, Vega64 graphic, ryzen 1700x, tridentz royal ram clocked to 3200. Issue: Firefox, minecraft, team fortress2 crashing all the time. it did work nearly stable a few updates earlier. Its probably an issue with the x570 chipset driver just guessing. Sometimes its just an application crash Sometimes im suddenly back at login screen Sometimes audio doesnt work until restart Sometimes whole OS freezes anyway ty guys for all the opensource work ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-generic 5.3.0.26.30 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Fri Jan 17 21:01:07 2020 InstallationDate: Installed on 2019-12-20 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_CH:de TERM=xterm-256color PATH=(custom, no user) LANG=de_CH.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=cdedb704-c0c5-4692-bd0e-591087449435 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860172/+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 1859692] Re: eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859694 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 16. January 2020 23:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2-5.3: bug 1859691 eoan/linux-raspi2/pi-kernel: bug 1859690 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1859692 Title: eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859694 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 16. January 2020 23:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2-5.3: bug 1859691 eoan/linux-raspi2/pi-kernel: bug 1859690 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859692/+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 1859817] Re: eoan/linux-aws: 5.3.0-1010.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859694 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 16. January 2020 23:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1859816 variant: debs -- 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/1859817 Title: eoan/linux-aws: 5.3.0-1010.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-lrm 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859694 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 16. January 2020 23:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1859816 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859817/+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 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 - xenial/linux-hwe: bug 1860122, bug 1859704 + xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs -- 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/1860123 Title: bionic/linux: 4.15.0-76.86 -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: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Confirmed 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
@rphair Please try the package @hui.wang posted and upload the asked alsa- info.txt, that way it can be possibly fixed. -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1860196] Re: kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI
I changed titile to kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI ** Summary changed: - kernel-5.3.0-26 could not use appliicatins on core2 Duo + kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI -- 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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860182] Re: zpool scrub malfunction after kernel upgrade
Update: The scrub back on 4.15 went as expected. I rebooted with 5.3 kernel and tried the scrub again. I saw the same behaviour: the scrub started, with a very fast rate and short time estimate (3-5 minutes), and then reached 100% after about that time. However it continued to say it was in progress, despite saying 100.00% done. It did not calcualte a time estimate, saying the rate was slow, however, it did complete after 3h36 (so fast than it used to on kernel 4.15). eric@eric-8700K:~$ zpool status pool: storagepool1 state: ONLINE scan: scrub repaired 0B in 3h36m with 0 errors on Sat Jan 18 14:50:16 2020 config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 errors: No known data errors I started a scrub again to see whether it was just the first time with this kernel, but again the % complete seems inaccurate, and the time remaining is definitely inaccurate (0h0m shortly after starting). So at the very least it is clear that zpool status is not accurately reporting the scrub process on kernel 5.3. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1860182 Title: zpool scrub malfunction after kernel upgrade Status in zfs-linux package in Ubuntu: Triaged Bug description: I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly: eric@eric-8700K:~$ zpool status pool: storagepool1 state: ONLINE scan: scrub repaired 1M in 4h21m with 0 errors on Fri Jan 17 07:01:24 2020 config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 I ran zpool scrub after upgrading the kernel and rebooting, and now it fails to work properly. It appeared to finish in about 5 minutes but did not, and says it is going slow: eric@eric-8700K:~$ sudo zpool status pool: storagepool1 state: ONLINE scan: scrub in progress since Fri Jan 17 15:32:07 2020 1.89T scanned out of 1.89T at 589M/s, (scan is slow, no estimated time) 0B repaired, 100.00% done config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 errors: No known data errors ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.7 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 16:22:01 2020 InstallationDate: Installed on 2018-03-07 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: zfs-linux UpgradeStatus: Upgraded to bionic on 2018-08-02 (533 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1860182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1860228] Re: addition of zfsutils-linux scrib every 2nd sunday
This was added a LONG time ago. The interesting question here is: if you
previously deleted it, why did it come back? Had you deleted it though?
It sounds like you weren’t aware of this file.
You might want to edit it in place, even just to comment out the job.
That would force dpkg to give you a conffile merge prompt instead of
being able to silently put it back.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860228
Title:
addition of zfsutils-linux scrib every 2nd sunday
Status in zfs-linux package in Ubuntu:
New
Bug description:
FULL REF: https://github.com/zfsonlinux/zfs/issues/9858 (initially
submitted there mistakenly)
==System information==
{{{
Type Version/Name
Distribution Name Ubuntu
Distribution Version 18.04.3 LTS
Linux Kernel 4.15.0-73-generic
Architecture x86_64
ZFS Version 0.7.5-1ubuntu16.6
SPL Version 0.7.5-1ubuntu2
Describe the problem you're observing
}}}
==When did this file get added into zfsonlinux ecosystem?==
{{{
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ]
&& /usr/lib/zfs-linux/scrub
}}}
I've been a ZoL user for many years now, and have had my own cron setup
tailored to distribute pool scrubs once per month, spread across the month to
avoid system I/O overload on any one day of the month, like this:
{{{
# zfsmain scrub: 2:30AM 7th of every month
30 02 7 * * /sbin/zpool scrub zfsmain
# zstorage scrub: 2:30AM 5th of every month
30 02 5 * * /sbin/zpool scrub zstorage
# zmedia scrub: 1:00AM 14th of every month
00 01 14 * * /sbin/zpool scrub zmedia
# zstorage scrub: 2:30AM 21st of every month
30 02 21 * * /sbin/zpool scrub ztank
}}}
However suddenly I noticed in an adhoc check of zpool status that ALL my
pools were scrubbed on Sunday January 12th 2020!
{{{
# zpool status | grep -i "scrub"
scan: scrub repaired 0B in 0h13m with 0 errors on Sun Jan 12 00:37:31 2020
scan: scrub repaired 0B in 11h24m with 0 errors on Tue Jan 14 12:24:33 2020
<-- (one of my own since the Jan12 mega scrub)
scan: scrub repaired 0B in 0h45m with 0 errors on Sun Jan 12 01:09:40 2020
scan: scrub repaired 0B in 7h10m with 0 errors on Sun Jan 12 07:34:11 2020
}}}
this is NOT what I had configured, so I went digging and found that zfsutil
cron file :(
{{{
# cat /usr/lib/zfs-linux/scrub
#!/bin/sh -eu
# Scrub all healthy pools.
zpool list -H -o health,name 2>&1 | \
awk 'BEGIN {FS="\t"} {if ($1 ~ /^ONLINE/) print $2}' | \
while read pool
do
zpool scrub "$pool"
done
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ]
&& /usr/lib/zfs-linux/scrub
}}}
This MAY be a desirable default for some system admins, but having it
suddenly appear IMO is at the same time undesirable for many.
==Describe how to reproduce the problem==
* Having been a ZoL user sys admin for many years.
* Be a decent sys admin and know the basics, you've configured your own
cron/schedule for pool scrubbing per guidelines and individual needs.
* Follow stable upgrade channels. (for me this is Ubuntu LTS 16.04, then
18.04)
* Suddenly after some upgrade version XX(?) your pools start scrubbing on the
2nd Sunday of every month without your having configured it or asked for that.
==Expectations==
Hoping we can:
1. Confirm when and why this was rolled out to all systems by default (does
the explanation make sense? is it really OK to do this? how was it
communicated?)
2. Ensure "how to disable" is documented and supported (i.e. if I just
delete that cron file, will some future upgrade replace and re-enable it?)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zfsutils-linux 0.7.5-1ubuntu16.7
ProcVersionSignature: Ubuntu 4.15.0-73.82-generic 4.15.18
Uname: Linux 4.15.0-73-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
Date: Sat Jan 18 13:41:29 2020
InstallationDate: Installed on 2015-06-28 (1664 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
SourcePackage: zfs-linux
UpgradeStatus: Upgraded to bionic on 2019-05-10 (253 days ago)
modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission
denied: '/etc/sudoers.d/zfs']
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1860228/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 1860231] Re: 5.4.0-11 crash on cryptsetup open
This model file is used to build both the spread test image and the manually built image. The two generated images, however, seem to behave differently regarding the conditions leading to the crash: while it always happen in the spread test, higher KDF iteration times values allow the encrypted device to be opened correctly in the image created using the steps described in the bug description. Michael Vogt also reports that the crash doesn't happen in a classic system running the same kernel version. ** Attachment added: "Model file used to build the image" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+attachment/5321427/+files/ubuntu-core-20-amd64.model -- 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/1860231 Title: 5.4.0-11 crash on cryptsetup open Status in linux package in Ubuntu: Incomplete Bug description: An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc-kernel_374.snap. Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: 1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image 1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work) 2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,if=virtio \ -bios /usr/share/OVMF/OVMF_CODE.ms.fd 2.3. In the grub menu, edit the default option to include parameter "systemd.debug-shell=1" in the kernel command line 2.4. Boot the kernel 3. Crash the kernel 3.1. When the system boots to the "Press enter to configure" message, press ALT-F9 to enter the debug shell. 3.2. The system should have two partitions in /dev/vda. Create a third one with fdisk. 3.3. Create a LUKS encrypted partition: # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 (the system will complain about a missing locking directory, just ignore it.) 3.4. Open the encrypted device: # echo 123|cryptsetup open --key-file - /dev/vda name 3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem to be caused by a race between dm-crypt loading and cryptsetup luksFormat for example). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+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 1860231] Re: 5.4.0-11 crash on cryptsetup open
Snap versions used to build the image: pc-kernel_374.snap pc_83.snap snapd_6113.snap core20_322.snap -- 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/1860231 Title: 5.4.0-11 crash on cryptsetup open Status in linux package in Ubuntu: Incomplete Bug description: An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc-kernel_374.snap. Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: 1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image 1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work) 2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,if=virtio \ -bios /usr/share/OVMF/OVMF_CODE.ms.fd 2.3. In the grub menu, edit the default option to include parameter "systemd.debug-shell=1" in the kernel command line 2.4. Boot the kernel 3. Crash the kernel 3.1. When the system boots to the "Press enter to configure" message, press ALT-F9 to enter the debug shell. 3.2. The system should have two partitions in /dev/vda. Create a third one with fdisk. 3.3. Create a LUKS encrypted partition: # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 (the system will complain about a missing locking directory, just ignore it.) 3.4. Open the encrypted device: # echo 123|cryptsetup open --key-file - /dev/vda name 3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem to be caused by a race between dm-crypt loading and cryptsetup luksFormat for example). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+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 1860231] 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 1860231 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/1860231 Title: 5.4.0-11 crash on cryptsetup open Status in linux package in Ubuntu: Incomplete Bug description: An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc-kernel_374.snap. Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: 1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image 1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work) 2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,if=virtio \ -bios /usr/share/OVMF/OVMF_CODE.ms.fd 2.3. In the grub menu, edit the default option to include parameter "systemd.debug-shell=1" in the kernel command line 2.4. Boot the kernel 3. Crash the kernel 3.1. When the system boots to the "Press enter to configure" message, press ALT-F9 to enter the debug shell. 3.2. The system should have two partitions in /dev/vda. Create a third one with fdisk. 3.3. Create a LUKS encrypted partition: # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 (the system will complain about a missing locking directory, just ignore it.) 3.4. Open the encrypted device: # echo 123|cryptsetup open --key-file - /dev/vda name 3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem to be caused by a race between dm-crypt loading and cryptsetup luksFormat for example). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
Tested again after kernel jump to 5.3 (5.3.0-26-generic): still a problem. Nice "optimisation" fellas. I guess most of the world doesn't experience this because they are either have grounded speakers or a motherboard that grounds the output, so they don't hear a buzz when a signal isn't coming from the sound card? (I have cheap speakers and a 10+ year old motherboard.) -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1860231] Re: 5.4.0-11 crash on cryptsetup open
** Attachment added: "Screenshot of the procedure to trigger the crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+attachment/5321426/+files/Screenshot%20from%202020-01-18%2016-16-19.png -- 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/1860231 Title: 5.4.0-11 crash on cryptsetup open Status in linux package in Ubuntu: New Bug description: An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc-kernel_374.snap. Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: 1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image 1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work) 2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,if=virtio \ -bios /usr/share/OVMF/OVMF_CODE.ms.fd 2.3. In the grub menu, edit the default option to include parameter "systemd.debug-shell=1" in the kernel command line 2.4. Boot the kernel 3. Crash the kernel 3.1. When the system boots to the "Press enter to configure" message, press ALT-F9 to enter the debug shell. 3.2. The system should have two partitions in /dev/vda. Create a third one with fdisk. 3.3. Create a LUKS encrypted partition: # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 (the system will complain about a missing locking directory, just ignore it.) 3.4. Open the encrypted device: # echo 123|cryptsetup open --key-file - /dev/vda name 3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem to be caused by a race between dm-crypt loading and cryptsetup luksFormat for example). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+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 1860231] [NEW] 5.4.0-11 crash on cryptsetup open
Public bug reported: An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc- kernel_374.snap. Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: 1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image 1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work) 2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,if=virtio \ -bios /usr/share/OVMF/OVMF_CODE.ms.fd 2.3. In the grub menu, edit the default option to include parameter "systemd.debug-shell=1" in the kernel command line 2.4. Boot the kernel 3. Crash the kernel 3.1. When the system boots to the "Press enter to configure" message, press ALT-F9 to enter the debug shell. 3.2. The system should have two partitions in /dev/vda. Create a third one with fdisk. 3.3. Create a LUKS encrypted partition: # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 (the system will complain about a missing locking directory, just ignore it.) 3.4. Open the encrypted device: # echo 123|cryptsetup open --key-file - /dev/vda name 3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem to be caused by a race between dm-crypt loading and cryptsetup luksFormat for example). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Kernel backtrace" https://bugs.launchpad.net/bugs/1860231/+attachment/5321425/+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/1860231 Title: 5.4.0-11 crash on cryptsetup open Status in linux package in Ubuntu: New Bug description: An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc-kernel_374.snap. Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: 1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image 1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work) 2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,if=virtio \
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 - xenial/linux-hwe: bug 1859704, bug 1860122 + xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs -- 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/1860123 Title: bionic/linux: 4.15.0-76.86 -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: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Confirmed 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+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 1860228] [NEW] addition of zfsutils-linux scrib every 2nd sunday
Public bug reported:
FULL REF: https://github.com/zfsonlinux/zfs/issues/9858 (initially
submitted there mistakenly)
==System information==
{{{
TypeVersion/Name
Distribution Name Ubuntu
Distribution Version18.04.3 LTS
Linux Kernel4.15.0-73-generic
Architecturex86_64
ZFS Version 0.7.5-1ubuntu16.6
SPL Version 0.7.5-1ubuntu2
Describe the problem you're observing
}}}
==When did this file get added into zfsonlinux ecosystem?==
{{{
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] &&
/usr/lib/zfs-linux/scrub
}}}
I've been a ZoL user for many years now, and have had my own cron setup
tailored to distribute pool scrubs once per month, spread across the month to
avoid system I/O overload on any one day of the month, like this:
{{{
# zfsmain scrub: 2:30AM 7th of every month
30 02 7 * * /sbin/zpool scrub zfsmain
# zstorage scrub: 2:30AM 5th of every month
30 02 5 * * /sbin/zpool scrub zstorage
# zmedia scrub: 1:00AM 14th of every month
00 01 14 * * /sbin/zpool scrub zmedia
# zstorage scrub: 2:30AM 21st of every month
30 02 21 * * /sbin/zpool scrub ztank
}}}
However suddenly I noticed in an adhoc check of zpool status that ALL my pools
were scrubbed on Sunday January 12th 2020!
{{{
# zpool status | grep -i "scrub"
scan: scrub repaired 0B in 0h13m with 0 errors on Sun Jan 12 00:37:31 2020
scan: scrub repaired 0B in 11h24m with 0 errors on Tue Jan 14 12:24:33 2020
<-- (one of my own since the Jan12 mega scrub)
scan: scrub repaired 0B in 0h45m with 0 errors on Sun Jan 12 01:09:40 2020
scan: scrub repaired 0B in 7h10m with 0 errors on Sun Jan 12 07:34:11 2020
}}}
this is NOT what I had configured, so I went digging and found that zfsutil
cron file :(
{{{
# cat /usr/lib/zfs-linux/scrub
#!/bin/sh -eu
# Scrub all healthy pools.
zpool list -H -o health,name 2>&1 | \
awk 'BEGIN {FS="\t"} {if ($1 ~ /^ONLINE/) print $2}' | \
while read pool
do
zpool scrub "$pool"
done
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] &&
/usr/lib/zfs-linux/scrub
}}}
This MAY be a desirable default for some system admins, but having it
suddenly appear IMO is at the same time undesirable for many.
==Describe how to reproduce the problem==
* Having been a ZoL user sys admin for many years.
* Be a decent sys admin and know the basics, you've configured your own
cron/schedule for pool scrubbing per guidelines and individual needs.
* Follow stable upgrade channels. (for me this is Ubuntu LTS 16.04, then 18.04)
* Suddenly after some upgrade version XX(?) your pools start scrubbing on the
2nd Sunday of every month without your having configured it or asked for that.
==Expectations==
Hoping we can:
1. Confirm when and why this was rolled out to all systems by default (does
the explanation make sense? is it really OK to do this? how was it
communicated?)
2. Ensure "how to disable" is documented and supported (i.e. if I just delete
that cron file, will some future upgrade replace and re-enable it?)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zfsutils-linux 0.7.5-1ubuntu16.7
ProcVersionSignature: Ubuntu 4.15.0-73.82-generic 4.15.18
Uname: Linux 4.15.0-73-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
Date: Sat Jan 18 13:41:29 2020
InstallationDate: Installed on 2015-06-28 (1664 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
SourcePackage: zfs-linux
UpgradeStatus: Upgraded to bionic on 2019-05-10 (253 days ago)
modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission
denied: '/etc/sudoers.d/zfs']
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
** Description changed:
FULL REF: https://github.com/zfsonlinux/zfs/issues/9858 (initially
submitted there mistakenly)
+ ```
System information
Type Version/Name
Distribution Name Ubuntu
Distribution Version 18.04.3 LTS
Linux Kernel 4.15.0-73-generic
Architecture x86_64
ZFS Version 0.7.5-1ubuntu16.6
SPL Version 0.7.5-1ubuntu2
Describe the problem you're observing
+ ```
When did this file get added into zfsonlinux ecosystem?
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ]
&& /usr/lib/zfs-linux/scrub
I've been a ZoL user for many years now, and have had my own cron setup
tailored to distribute pool scrubs once per month, spread across the
month to avoid
[Kernel-packages] [Bug 1860226] 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 1860226 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/1860226 Title: broadcom wifi broken at 5.3.0.26.95 kernel update Status in linux package in Ubuntu: Incomplete Bug description: Kernel came in with regular maintenance. I DID notice some error messages in Update Manager log about broadcom drivers, but didn't realize it was for real. Upon boot, couldn't access wifi. Booted using 5.0 kernel and all is well again. ubuntu-bug linux output -- N/A version.log attached lspci-vnvn.log attached Update Manager log (apt-term.log) attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860226/+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 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome
I found the real reason for the crashes. The problematic package is the `gstreamer1.0-vaapi` (see https://packages.ubuntu.com/focal/gstreamer1.0-vaapi). It is a dependency of `ubuntu-restricted-addons` (see https://packages.ubuntu.com/focal/ubuntu-restricted-addons). So ubuntu-mate-welcome and for example Cheese may be fixed by removing this package with ``` sudo apt-get purge gstreamer1.0-vaapi sudo apt-get autoremove --purge # to remove libgstreamer-plugins-bad1.0-0 (is not a problem) ``` So please carefully analyze the crash dumps for errors in `gstreamer1.0-vaapi` and fix this package. -- 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/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome Status in gstreamer-vaapi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in ubuntu-mate-meta package in Ubuntu: Invalid Status in ubuntu-mate-welcome package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Won't Fix Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
[Kernel-packages] [Bug 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome
** Changed in: ubuntu-mate-meta (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-mate-welcome (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Also affects: gstreamer-vaapi (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/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome Status in gstreamer-vaapi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in ubuntu-mate-meta package in Ubuntu: Invalid Status in ubuntu-mate-welcome package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Won't Fix Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
[Kernel-packages] [Bug 1860226] [NEW] broadcom wifi broken at 5.3.0.26.95 kernel update
Public bug reported: Kernel came in with regular maintenance. I DID notice some error messages in Update Manager log about broadcom drivers, but didn't realize it was for real. Upon boot, couldn't access wifi. Booted using 5.0 kernel and all is well again. ubuntu-bug linux output -- N/A version.log attached lspci-vnvn.log attached Update Manager log (apt-term.log) attached ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "KernelBugReport.tar.gz" https://bugs.launchpad.net/bugs/1860226/+attachment/5321399/+files/KernelBugReport.tar.gz -- 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/1860226 Title: broadcom wifi broken at 5.3.0.26.95 kernel update Status in linux package in Ubuntu: New Bug description: Kernel came in with regular maintenance. I DID notice some error messages in Update Manager log about broadcom drivers, but didn't realize it was for real. Upon boot, couldn't access wifi. Booted using 5.0 kernel and all is well again. ubuntu-bug linux output -- N/A version.log attached lspci-vnvn.log attached Update Manager log (apt-term.log) attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860226/+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 1843873] Re: Sound distored on Hades Canyon NUC
Finally I can confirm that issue has been fixed with kernel 5.5-rc5 suggested by Kai-Heng Feng. Thank you very much. -- 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/1843873 Title: Sound distored on Hades Canyon NUC Status in linux package in Ubuntu: Confirmed Bug description: On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted (unusable). Problem does not occur with a fresh install of Ubuntu 18.10 Full Specs for the device can be found here : https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sparky 1447 F pulseaudio /dev/snd/controlC1: sparky 1447 F pulseaudio /dev/snd/pcmC1D10p: sparky 1447 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-09-25 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Intel(R) Client Systems NUC8i7HVK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646 dmi.board.name: NUC8i7HVB dmi.board.vendor: Intel Corporation dmi.board.version: J68196-504 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i7HVK dmi.product.version: J71485-504 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843873/+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 1796437] 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/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome Status in linux package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Status in ubuntu-mate-welcome package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Won't Fix Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome
With virt-manager the crashes occur with Cirrus, QXL, VGA video drivers. But does not occur with VMVGA video driver. Possibly kernel (drm) issue. ** Also 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/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome Status in linux package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Confirmed Status in ubuntu-mate-welcome package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Won't Fix Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796437/+subscriptions -- Mailing
[Kernel-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Hi everyone, Thank you very much Daniel for your attention and recommendations but ..; 1. I installed ubuntu 20.04, everything started fine, but it failed again in the same way as in ubuntu 18, before this I was testing fedora 31 and the same errors were presented for both ubuntu 18, 20 and fedora 31, (screen crash, black screen with the message [2658.28 ...] systemd-journald [378]: failed to write entry (22 items, 749 bytes), ignoring: read-only file system). 2. Thinking that it may be a hardware error especially of the micron m2 SSD, contact dell technical service and just have an answer from them I will comment on it by this means. 3. I also cannot get the id of the .crash file, but when I select to report the error, an error window appears indicating the following: "The problem cannot be reported: It has some packages installed with obsolete versions bsdutils, libblkid1, libmount1, libsmartcols1, libuuid1, mount, utillinux, uuid-runtime " Any advice to fix those versions of the packages? Thank you very much to all! ** Attachment added: "crash.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1859730/+attachment/5321393/+files/crash.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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root 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 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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/1859730/+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 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 - xenial/linux-hwe: bug 1860122, bug 1859704 + xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs -- 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/1860123 Title: bionic/linux: 4.15.0-76.86 -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: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Confirmed 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+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 1860172] Re: Crashes all the time
added syslog ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860172/+attachment/5321346/+files/syslog -- 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/1860172 Title: Crashes all the time Status in linux package in Ubuntu: Confirmed Bug description: Setup: ubuntu 19.10, x570-f motherboard, Vega64 graphic, ryzen 1700x, tridentz royal ram clocked to 3200. Issue: Firefox, minecraft, team fortress2 crashing all the time. it did work nearly stable a few updates earlier. Its probably an issue with the x570 chipset driver just guessing. Sometimes its just an application crash Sometimes im suddenly back at login screen Sometimes audio doesnt work until restart Sometimes whole OS freezes anyway ty guys for all the opensource work ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-generic 5.3.0.26.30 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Fri Jan 17 21:01:07 2020 InstallationDate: Installed on 2019-12-20 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_CH:de TERM=xterm-256color PATH=(custom, no user) LANG=de_CH.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=cdedb704-c0c5-4692-bd0e-591087449435 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860172/+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 1846995] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
Nope. Stock kernel. -- 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/1846995 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Doing a do-release-upgrade -d from 19.04 to 19.10. The upgrade crashed out part way through, automatically reporting this bug. update-initramfs: Generating /boot/initrd.img-5.3.0-13-generic Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.39.2-3) ... Processing triggers for libc-bin (2.30-0ubuntu2) ... Processing triggers for menu (2.1.47ubuntu3) ... Errors were encountered while processing: nvidia-dkms-390 nvidia-driver-390 Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (624.7 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 390.129-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 01:17:46 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-04-23 (531 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846995/+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 1843385] Re: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
Probably the same as Bug #1851162 -- 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/1843385 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Just upgraded the distro to 19.10 (dev) ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 (not installed) ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Tue Sep 10 08:08:26 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2016-02-03 (1314 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.3 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1843385/+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 1853196] Re: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build
*** This bug is a duplicate of bug 1851162 *** https://bugs.launchpad.net/bugs/1851162 ** This bug has been marked a duplicate of bug 1851162 nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 -- 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/1853196 Title: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: i tried to install nvidia drivers from this link https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-19-10-eoan-ermine-linux . My video card is nvdia Gforce GT610. Sometimes on boot there is pixel "scratches" (on the pink screen). ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-kernel-source-390 390.129-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 DKMSKernelVersion: 5.3.0-23-generic Date: Tue Nov 19 22:29:16 2019 Dependencies: PackageVersion: 390.129-0ubuntu2 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build 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/1853196/+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 1851162] Re: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- 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/1851162 Title: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 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/1851162/+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 1844613] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 1851162 *** https://bugs.launchpad.net/bugs/1851162 ** This bug has been marked a duplicate of bug 1851162 nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 -- 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/1844613 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: each time the pc starts, the error message is shown, but if i close that i can work w/o any problem ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 390.129-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Tue Sep 17 23:42:51 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-02-09 (587 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.3 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1844613/+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 1846995] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
Did you build a custom kernel? -- 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/1846995 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Doing a do-release-upgrade -d from 19.04 to 19.10. The upgrade crashed out part way through, automatically reporting this bug. update-initramfs: Generating /boot/initrd.img-5.3.0-13-generic Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.39.2-3) ... Processing triggers for libc-bin (2.30-0ubuntu2) ... Processing triggers for menu (2.1.47ubuntu3) ... Errors were encountered while processing: nvidia-dkms-390 nvidia-driver-390 Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (624.7 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 390.129-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 01:17:46 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-04-23 (531 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846995/+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 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Pending -- ready for review trackers: + bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 - xenial/linux-hwe: bug 1860122 + xenial/linux-azure: bug 1859798 + xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs -- 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/1860123 Title: bionic/linux: 4.15.0-76.86 -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: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Confirmed 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+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 1857378] Re: Please drop i386 dkms package, as there are no i386 kernel
Or don't. https://discourse.ubuntu.com/t/intel-32bit-packages-on-ubuntu-from-19-10-onwards/11263/90 ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Invalid -- 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/1857378 Title: Please drop i386 dkms package, as there are no i386 kernel Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Please drop i386 dkms package, as there are no i386 kernel Systems should enable amd64 archive and install amd64 kernel & the amd64 dkms package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1857378/+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 1851162] Re: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
The HWE package now force-upgrades to 5.3.0, rendering that entire package useless. -- 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/1851162 Title: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 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/1851162/+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 1858533] Re: bionic/linux-azure: 5.0.0-1029.31~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858534 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1858532 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1858533 Title: bionic/linux-azure: 5.0.0-1029.31~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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-lrm 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858534 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1858532 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858533/+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 1859798] Re: xenial/linux-azure: 4.15.0-1067.72 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1859705 + kernel-stable-master-bug: '1860123' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1859797 xenial/linux-azure/azure-kernel: bug 1859796 variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1859797 xenial/linux-azure/azure-kernel: bug 1859796 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1859798 Title: xenial/linux-azure: 4.15.0-1067.72 -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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1859797 xenial/linux-azure/azure-kernel: bug 1859796 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859798/+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
Re: [Kernel-packages] [Bug 1851956] Re: Initialization too slow, about 2 minutes. After is normal.
Ok!!! Thanks Em qui., 5 de dez. de 2019 às 06:56, Daniel van Vugt < daniel.van.v...@canonical.com> escreveu: > It sounds like the problem is already fixed in a later kernel. Maybe > just try installing a newer kernel then: > > https://kernel.ubuntu.com/~kernel-ppa/mainline/ > > and see what was the earliest version to fix the problem. > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > ** Summary changed: > > - Initialization too slow, about 2 minutes. After is normal. > + [Sony Vaio VPCEE45FB] Initialization too slow, about 2 minutes. After is > normal. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851956 > > Title: > [Sony Vaio VPCEE45FB] Initialization too slow, about 2 minutes. After > is normal. > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > When init the grub boot, stop and wait for 2 minutes, circa... > After this time, normal speed and OS load normally, no problem !!! > Ubuntu Studio 18.04 LTS. Sony Vaio VPCEE45B. > Ubuntu Studio 20.04 (Daily) work fine, without wait > Thanks > > > (My english is bad,,,sorry) > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-66.75-lowlatency 4.15.18 > Uname: Linux 4.15.0-66-lowlatency x86_64 > ApportVersion: 2.20.9-0ubuntu7.9 > Architecture: amd64 > CompositorRunning: None > Date: Sat Nov 9 16:26:42 2019 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD > 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) > Subsystem: Sony Corporation RS880M [Mobility Radeon HD 4225/4250] > [104d:9077] > InstallationDate: Installed on 2019-11-08 (1 days ago) > InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release > amd64 (20180426) > MachineType: Sony Corporation VPCEE45FB > ProcEnviron: >LANGUAGE=pt_BR >PATH=(custom, no user) >LANG=pt_BR.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-lowlatency > root=/dev/mapper/ubuntu--studio--vg-root ro locale=pt_BR quiet splash > vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/09/2010 > dmi.bios.vendor: Insyde Corp. > dmi.bios.version: R0200Z5 > 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:bvnInsydeCorp.:bvrR0200Z5:bd12/09/2010:svnSonyCorporation:pnVPCEE45FB:pvrC8002NHR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: > dmi.product.family: VAIO > dmi.product.name: VPCEE45FB > dmi.product.version: C8002NHR > dmi.sys.vendor: Sony Corporation > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 > 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 > xserver.bootTime: Sat Nov 9 15:54:20 2019 > xserver.configfile: default > xserver.errors: > > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.19.6-1ubuntu4.3 > xserver.video_driver: radeon > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851956/+subscriptions > -- 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/1851956 Title: [Sony Vaio VPCEE45FB] Initialization too slow, about 2 minutes. After is normal. Status in linux package in Ubuntu: Incomplete Bug description: When init the grub boot, stop and wait for 2 minutes, circa... After this time, normal speed and OS load normally, no problem !!! Ubuntu Studio 18.04 LTS. Sony Vaio VPCEE45B. Ubuntu Studio 20.04 (Daily) work fine, without wait Thanks (My english is bad,,,sorry) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-66.75-lowlatency 4.15.18 Uname: Linux 4.15.0-66-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Sat Nov 9 16:26:42 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard:
[Kernel-packages] [Bug 1859820] Re: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859694 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1859819 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1859820 Title: eoan/linux-azure: 5.3.0-1010.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-lrm 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859694 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1859819 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859820/+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 1850439] Re: No sound on ASUS UX534FT
Same problem on ASUS Zenbook 15 UX533FTC-A8157R # hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.9G5mT1GK4nF SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x02c8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1a61 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable) Memory Range: 0xc410-0xc41f (rw,non-prefetchable) IRQ: 148 (1016 events) Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci is active Driver Activation Cmd: "modprobe snd_sof_pci" Config Status: cfg=new, avail=yes, need=no, active=unknown -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1859795] Re: bionic/linux-aws: 4.15.0-1058.60 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1859705 + kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 16. January 2020 10:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1859801 bionic/linux-aws/aws-kernel: bug 1859794 xenial/linux-aws-hwe: bug 1859802 variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 16. January 2020 10:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1859801 bionic/linux-aws/aws-kernel: bug 1859794 xenial/linux-aws-hwe: bug 1859802 variant: debs -- 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/1859795 Title: bionic/linux-aws: 4.15.0-1058.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 16. January 2020 10:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1859801 bionic/linux-aws/aws-kernel: bug 1859794 xenial/linux-aws-hwe: bug 1859802 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859795/+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 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support
Taha, Did the screenpad work out of the box or did you have to download/setup additional drivers ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1846090 Title: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad and screen - all in one) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Oct 1 00:53:26 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.0.0-29-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1021] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:180e] InstallationDate: Installed on 2019-09-27 (3 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GDX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GDX 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.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+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 1860185] Re: kernel-5.3.0-26 could not boot up notePC
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1860185 Title: kernel-5.3.0-26 could not boot up notePC Status in linux package in Ubuntu: Confirmed Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment( two PCs) are updated and boot up fine. but notePC ( Intel celeron N3450 1.1GHz ) boot up and displayed many messages, and I found a same message displayed, then power off PC force. then power on notePC, boot up normaly. I send log soon. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1469 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Jumper EZbook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=9bd92ce9-20ef-4afc-a6e8-5b42dd5ec991 ro ipv6.disable=1 quiet ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/01/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02 dmi.board.asset.tag: Default string dmi.board.name: EZbook dmi.board.vendor: Jumper dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: EZbook dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Jumper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860185/+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 1860185] 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/1860185 Title: kernel-5.3.0-26 could not boot up notePC Status in linux package in Ubuntu: Confirmed Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment( two PCs) are updated and boot up fine. but notePC ( Intel celeron N3450 1.1GHz ) boot up and displayed many messages, and I found a same message displayed, then power off PC force. then power on notePC, boot up normaly. I send log soon. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1469 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Jumper EZbook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=9bd92ce9-20ef-4afc-a6e8-5b42dd5ec991 ro ipv6.disable=1 quiet ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/01/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02 dmi.board.asset.tag: Default string dmi.board.name: EZbook dmi.board.vendor: Jumper dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: EZbook dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Jumper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860185/+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 1860196] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321296/+files/ProcInterrupts.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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860196] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321300/+files/WifiSyslog.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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860196] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321292/+files/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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860196] Re: kernel-5.3.0-26 could not use appliicatins on core2 Duo
I boot up 5.3.0-26 recovery mode. apport-collect 1860196 -- 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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860196] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321291/+files/CurrentDmesg.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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860196] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321294/+files/ProcCpuinfo.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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860196] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321293/+files/Lsusb.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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860196] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321297/+files/ProcModules.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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860196] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321290/+files/CRDA.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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860196] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321295/+files/ProcCpuinfoMinimal.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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860196] Re: kernel-5.3.0-26 could not use appliicatins on core2 Duo
apport information ** Tags added: apport-collected bionic ** Description changed: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: nakasima 1711 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-08-30 (140 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) + IwConfig: + enp2s0no wireless extensions. + + lono wireless extensions. + MachineType: System manufacturer P5K/EPU + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ja_JP.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 + ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-26-generic N/A + linux-backports-modules-5.3.0-26-generic N/A + linux-firmware1.173.14 + RfKill: + + Tags: bionic + Uname: Linux 5.3.0-26-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/06/2008 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0304 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: P5K/EPU + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: P5K/EPU + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321289/+files/AlsaInfo.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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer
[Kernel-packages] [Bug 1860196] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321298/+files/PulseList.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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860196] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321299/+files/UdevDb.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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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
