[Kernel-packages] [Bug 1792045] Re: Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04
Would it be possible for you to do a kernel bisection? First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the good version you found) $ git bisect bad $(the bad version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If the issue still happens, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792045 Title: Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04 Status in linux package in Ubuntu: Confirmed Bug description: I cannot get my external 8TB sata hard drive (attached via USB 3) to write faster than about 10 megabytes per second under Ubuntu 18.04. I have another that writes at the expected full speed or close enough (100+ MBps). I have tried: * Changing the enclosure from the stock to a new one * Using usb-storage "quirks" options in modprobe conf files to work around any UAS incompatibilities with the bridge (many reports of the drive working at full performance when disabling UAS, no such luck for me) * Checking the disk for errors * Updating the kernel to the most recent mainline (4.18.6 at the time) * Checking UEFI settings (I'm already on the most recent revision of the firmware) * Applying all available updates * Changing USB ports * Checking dmesg for any obvious errors (dead end, I googled everything) Again, a different external 3TB USB 3 drive does not have any write speed issues at all, so it's not the computer (Intel NUC7PJYH). However, the very same drive in both of the enclosures I have used works *perfectly* in Ubuntu 16.04 on kernel 4.15.0-34 in both a live session and installed. I am not sure what the difference is between the two LTS versions that is causing this, but unfortunately I think I've reached the end of my know-how on this. Thank you for your time, and please let me know what other information I can provide. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Sep 11 18:33:46 2018 InstallationDate: Installed on 2018-09-06 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 1997:2433 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7PJYH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=b40fd1a1-0de5-40bb-b598-7f4cd53daee1 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/21/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0044.2018.0821.1915 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67969-401 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrJYGLKCPX.86A.0044.2018.0821.1915:bd08/21/2018:svnIntelCorporation:pnNUC7PJYH:pvrJ67992-401:rvnIntelCorporation:rnNUC7JYB:rvrJ67969-401:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC7PJYH dmi.product.version: J67992-401 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-package
[Kernel-packages] [Bug 1780452] Re: 14e4:43ba Broadcom BCM43602 doesn't see 5GHz APs
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780452 Title: 14e4:43ba Broadcom BCM43602 doesn't see 5GHz APs Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: On a MacBookPro14,2 (2018 model), the wireless works with the brcmfmac on a Bionic install out of the box, but cannot see any APs on the 5GHz range, even though there are APs broadasting on 5GHz. $ sudo lspci -vnn -d 14e4: 02:00.0 Network controller [0280]: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 02) Subsystem: Apple Inc. BCM43602 802.11ac Wireless LAN SoC [106b:0157] Flags: bus master, fast devsel, latency 0, IRQ 75 Memory at 8240 (64-bit, non-prefetchable) [size=32K] Memory at 8200 (64-bit, non-prefetchable) [size=4M] Capabilities: [48] Power Management version 3 Capabilities: [58] MSI: Enable+ Count=1/16 Maskable- 64bit+ Capabilities: [68] Vendor Specific Information: Len=44 Capabilities: [ac] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Device Serial Number 9b-95-98-ff-ff-03-f0-18 Capabilities: [150] Power Budgeting Capabilities: [160] Virtual Channel Capabilities: [1b0] Latency Tolerance Reporting Capabilities: [220] #15 Capabilities: [240] L1 PM Substates Kernel driver in use: brcmfmac Kernel modules: brcmfmac, wl $ sudo iwlist wlp2s0 scan | grep Freq Frequency:2.437 GHz (Channel 6) Frequency:2.412 GHz (Channel 1) Frequency:2.412 GHz (Channel 1) Frequency:2.462 GHz (Channel 11) Frequency:2.412 GHz (Channel 1) Frequency:2.462 GHz (Channel 11) Found bug reports https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663711 and https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1487524, but there are no solutions for Bionic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 3080 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jul 6 16:43:32 2018 InstallationDate: Installed on 2018-07-05 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookPro14,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=8c4cc8cd-f9a2-4e84-9e5e-0f7d6bb49a01 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP142.88Z.0175.B00.1804091703 dmi.board.name: Mac-CAD6701F7CEA0921 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,2 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-CAD6701F7CEA0921 dmi.modalias: dmi:bvnAppleInc.:bvrMBP142.88Z.0175.B00.1804091703:bd04/09/2018:svnAppleInc.:pnMacBookPro14,2:pvr1.0:rvnAppleInc.:rnMac-CAD6701F7CEA0921:rvrMacBookPro14,2:cvnAppleInc.:ct9:cvrMac-CAD6701F7CEA0921: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780452/+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 1780452] Re: 14e4:43ba Broadcom BCM43602 doesn't see 5GHz APs
[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780452 Title: 14e4:43ba Broadcom BCM43602 doesn't see 5GHz APs Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: On a MacBookPro14,2 (2018 model), the wireless works with the brcmfmac on a Bionic install out of the box, but cannot see any APs on the 5GHz range, even though there are APs broadasting on 5GHz. $ sudo lspci -vnn -d 14e4: 02:00.0 Network controller [0280]: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 02) Subsystem: Apple Inc. BCM43602 802.11ac Wireless LAN SoC [106b:0157] Flags: bus master, fast devsel, latency 0, IRQ 75 Memory at 8240 (64-bit, non-prefetchable) [size=32K] Memory at 8200 (64-bit, non-prefetchable) [size=4M] Capabilities: [48] Power Management version 3 Capabilities: [58] MSI: Enable+ Count=1/16 Maskable- 64bit+ Capabilities: [68] Vendor Specific Information: Len=44 Capabilities: [ac] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Device Serial Number 9b-95-98-ff-ff-03-f0-18 Capabilities: [150] Power Budgeting Capabilities: [160] Virtual Channel Capabilities: [1b0] Latency Tolerance Reporting Capabilities: [220] #15 Capabilities: [240] L1 PM Substates Kernel driver in use: brcmfmac Kernel modules: brcmfmac, wl $ sudo iwlist wlp2s0 scan | grep Freq Frequency:2.437 GHz (Channel 6) Frequency:2.412 GHz (Channel 1) Frequency:2.412 GHz (Channel 1) Frequency:2.462 GHz (Channel 11) Frequency:2.412 GHz (Channel 1) Frequency:2.462 GHz (Channel 11) Found bug reports https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663711 and https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1487524, but there are no solutions for Bionic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 3080 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jul 6 16:43:32 2018 InstallationDate: Installed on 2018-07-05 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookPro14,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=8c4cc8cd-f9a2-4e84-9e5e-0f7d6bb49a01 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP142.88Z.0175.B00.1804091703 dmi.board.name: Mac-CAD6701F7CEA0921 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,2 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-CAD6701F7CEA0921 dmi.modalias: dmi:bvnAppleInc.:bvrMBP142.88Z.0175.B00.1804091703:bd04/09/2018:svnAppleInc.:pnMacBookPro14,2:pvr1.0:rvnAppleInc.:rnMac-CAD6701F7CEA0921:rvrMacBookPro14,2:cvnAppleInc.:ct9:cvrMac-CAD6701F7CEA0921: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780452/+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 1792849] Re: nvidia_supported have error excluding lot of supported video card
** Attachment added: "nvidia_supported.diff.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1792849/+attachment/5189694/+files/nvidia_supported.diff.txt -- 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/1792849 Title: nvidia_supported have error excluding lot of supported video card Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I have a Nvidia GT 720M in my laptop and the only Drivers Ubuntu supply me is 340 which is dated from 2014. I think that OLD version was left in the repo because of the bug I'm talking about here. nvidia_supported script that generate a list of PCI ID from the README.txt have a problem that exclude a lot of PCI ID because of scripting error. Since 340 version, Nvidia changed the README.txt format, and the person who edited the nvidia_supported did some error there. This patch should resolve this and allow a LOT of Nvidia video card user to use modern and supported Drivers including support for VDPAU which finally give hardware video decoding support ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1792849/+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 1792849] [NEW] nvidia_supported have error excluding lot of supported video card
Public bug reported: I have a Nvidia GT 720M in my laptop and the only Drivers Ubuntu supply me is 340 which is dated from 2014. I think that OLD version was left in the repo because of the bug I'm talking about here. nvidia_supported script that generate a list of PCI ID from the README.txt have a problem that exclude a lot of PCI ID because of scripting error. Since 340 version, Nvidia changed the README.txt format, and the person who edited the nvidia_supported did some error there. This patch should resolve this and allow a LOT of Nvidia video card user to use modern and supported Drivers including support for VDPAU which finally give hardware video decoding support ! ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- 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/1792849 Title: nvidia_supported have error excluding lot of supported video card Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I have a Nvidia GT 720M in my laptop and the only Drivers Ubuntu supply me is 340 which is dated from 2014. I think that OLD version was left in the repo because of the bug I'm talking about here. nvidia_supported script that generate a list of PCI ID from the README.txt have a problem that exclude a lot of PCI ID because of scripting error. Since 340 version, Nvidia changed the README.txt format, and the person who edited the nvidia_supported did some error there. This patch should resolve this and allow a LOT of Nvidia video card user to use modern and supported Drivers including support for VDPAU which finally give hardware video decoding support ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1792849/+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 1690085]
Hi, update from me, as promised. First my system for reference: 2700X B450 Chipset - Gigabyte B450 AORUS PRO with F2 BIOS PSU from 2018 which is "Haswell compatible". Typical Current Idle AND disabling global c-states didn't help. Running Ubuntu 18.04 LTS with its stock kernel 4.15.0-34 right now. I am having some success (4 days now) with all of that AND idle=nomwait kernel parameter - although I only read that to be related to resets and not freezes. Anyways. will keep my system on. I would like to trade in the LEDs on GPU and mainboard for vendors effort to get some stability in their systems. Any update from someone who really knows what is going on would be really appreciated. We're playing around with settings which are not explained anywhere. -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I'm also running the ASPM patch and haven't had problems for the last month or so. Any idea when this will get merged? -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmli
[Kernel-packages] [Bug 443131] Re: volume control mute when volume is lower than 21%
This helped: https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#No_sound_below_a_volume_cutoff -- 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/443131 Title: volume control mute when volume is lower than 21% Status in linux package in Ubuntu: Won't Fix Bug description: Binary package hint: gnome-media Hi, i've so old, but SoundBlaster Audigy (lspci reports "01:06.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)"). Everything works perfect with gnome 2.28, but when i'm scrolling volume down by lower than 21%, everything's mutes! 1) Ubuntu 9.10 (beta) version on my pc 2) gnome-media with version 2.28.0 3) I wan't to set volume down 4) When volume lower than 21% there is no sound on my Sound Blaster Audigy ZS 2 card. ProblemType: Bug Architecture: i386 Date: Mon Oct 5 21:12:33 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gnome-media 2.28.0-0ubuntu1 ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.38-generic SourcePackage: gnome-media Uname: Linux 2.6.31-11-generic i686 XsessionErrors: (gnome-settings-daemon:1605): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:1605): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:1700): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1663): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/443131/+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 443131] Re: volume control mute when volume is lower than 21%
It apparently only happens to my headphones, which for some reason can't be adjusted in alsamixer. -- 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/443131 Title: volume control mute when volume is lower than 21% Status in linux package in Ubuntu: Won't Fix Bug description: Binary package hint: gnome-media Hi, i've so old, but SoundBlaster Audigy (lspci reports "01:06.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)"). Everything works perfect with gnome 2.28, but when i'm scrolling volume down by lower than 21%, everything's mutes! 1) Ubuntu 9.10 (beta) version on my pc 2) gnome-media with version 2.28.0 3) I wan't to set volume down 4) When volume lower than 21% there is no sound on my Sound Blaster Audigy ZS 2 card. ProblemType: Bug Architecture: i386 Date: Mon Oct 5 21:12:33 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gnome-media 2.28.0-0ubuntu1 ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.38-generic SourcePackage: gnome-media Uname: Linux 2.6.31-11-generic i686 XsessionErrors: (gnome-settings-daemon:1605): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:1605): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:1700): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1663): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/443131/+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 443131] Re: volume control mute when volume is lower than 21%
All the pages linked in the posts do not exist anymore, but I have the exact same issue on Kubuntu 18.04. What is going on here? -- 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/443131 Title: volume control mute when volume is lower than 21% Status in linux package in Ubuntu: Won't Fix Bug description: Binary package hint: gnome-media Hi, i've so old, but SoundBlaster Audigy (lspci reports "01:06.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)"). Everything works perfect with gnome 2.28, but when i'm scrolling volume down by lower than 21%, everything's mutes! 1) Ubuntu 9.10 (beta) version on my pc 2) gnome-media with version 2.28.0 3) I wan't to set volume down 4) When volume lower than 21% there is no sound on my Sound Blaster Audigy ZS 2 card. ProblemType: Bug Architecture: i386 Date: Mon Oct 5 21:12:33 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gnome-media 2.28.0-0ubuntu1 ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.38-generic SourcePackage: gnome-media Uname: Linux 2.6.31-11-generic i686 XsessionErrors: (gnome-settings-daemon:1605): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:1605): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:1700): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1663): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/443131/+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 1792813] 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/1792813 Title: iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10 Status in linux package in Ubuntu: Confirmed Bug description: On Cosmic, iio-sensor-proxy 2.4, with default 4.18 kernel as well as latest mainline 4.19.0-041900rc3-generic. There is no rotation lock button in the gnome-shell panel menu. Gnome Settings > Device Display shows rotation buttons There is no directory /sys/bus/iio Reproduction: 1. Rotate device, fold display back to tent and tablet modes: -> Rotation is not detected. When folding to tablet mode, device goes to suspend as if display had been closed normally. iio-sensor-proxy finds no sensors: ~$ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static; vendor preset: enabled) Active: inactive (dead) I reported issue as https://github.com/hadess/iio-sensor- proxy/issues/236 and was advised: "Looks like there's no supported sensors, or just no sensors inside this machine. Nothing that we can do about it, except asking your vendor for support (eg. is there one or multiple sensors, and if so, why aren't they supported in the kernel)" I posted the issue in Dell's Project Sputnik's Google+ community ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 2139 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Sep 16 20:20:48 2018 InstallationDate: Installed on 2018-09-13 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.fastboot=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792813/+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 1761751] Re: Black screen on 18.04 + AMD RX460
HI guys, Im trying to use my second Monitor with this videocard, i do not know if i have the same issue but my HDMI monitor just would not work. it worked before the update and only with kernels until 4.13... i don't know if i have to put some info here or somewhere else. thanks. -- 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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1792813] [NEW] iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10
Public bug reported: On Cosmic, iio-sensor-proxy 2.4, with default 4.18 kernel as well as latest mainline 4.19.0-041900rc3-generic. There is no rotation lock button in the gnome-shell panel menu. Gnome Settings > Device Display shows rotation buttons There is no directory /sys/bus/iio Reproduction: 1. Rotate device, fold display back to tent and tablet modes: -> Rotation is not detected. When folding to tablet mode, device goes to suspend as if display had been closed normally. iio-sensor-proxy finds no sensors: ~$ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static; vendor preset: enabled) Active: inactive (dead) I reported issue as https://github.com/hadess/iio-sensor- proxy/issues/236 and was advised: "Looks like there's no supported sensors, or just no sensors inside this machine. Nothing that we can do about it, except asking your vendor for support (eg. is there one or multiple sensors, and if so, why aren't they supported in the kernel)" I posted the issue in Dell's Project Sputnik's Google+ community ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 2139 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Sep 16 20:20:48 2018 InstallationDate: Installed on 2018-09-13 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.fastboot=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session ** Summary changed: - "iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10 + iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792813 Title: iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10 Status in linux package in Ubuntu: New Bug description: On Cosmic, iio-sensor-proxy 2.4, with default 4.18 kernel as well as latest mainline 4.19.0-041900rc3-generic. There is no rotation lock button in the gnome-shell panel menu. Gnome Settings > Device Display shows rotation buttons There is no directory /sys/bus/iio Reproduction: 1. Rotate device, fold display back to tent and tablet modes: -> Rotation is not detected. When folding to tablet mode, device goes to suspend as if display had been closed normally. iio-sensor-proxy finds no sensors: ~$ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static; vendor preset: enabled) Active: inactive (dead) I reported issue as https://github.com/hadess/iio-sensor- proxy/issues/236 and was advised: "Looks like there's no supported sensors, or just no sensors inside this machine. Nothing that we can do about it, except asking your vendor for support (eg. is there one or multiple sensors, and if so, why aren't they supported in the kernel)" I posted the issue in Dell's Project Sputnik's Google+ community ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10
[Kernel-packages] [Bug 1792811] [NEW] Transmission-gtk startup crash: doesn't start on 18.10
Public bug reported: It's impossibile to run transmission-gtk (segmentation fault). transmission-gtk 2.94 (d8e60ee44f) warning: core file may not match specified executable file. [New LWP 19206] [New LWP 19207] [New LWP 19210] [New LWP 19209] [New LWP 19211] [New LWP 19213] [New LWP 19212] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `transmission-gtk /tmp/mozilla_intilinux0/edubuntu-12.04.5-dvd-i386.iso.torrent'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fbbb9be123f in gtk_css_node_ensure_style (cssnode=0x5594cd1f1a20, current_time=current_time@entry=8576248389) at ../../../../gtk/gtkcssnode.c:987 987 ../../../../gtk/gtkcssnode.c: No such file or directory. [Current thread is 1 (Thread 0x7fbbb14c6c80 (LWP 19206))] ** Affects: transmission (Ubuntu) Importance: Undecided Assignee: Gianfranco Costamagna (costamagnagianfranco) Status: New ** Attachment added: "_usr_bin_transmission-gtk.1000.crash" https://bugs.launchpad.net/bugs/1792811/+attachment/5189554/+files/_usr_bin_transmission-gtk.1000.crash ** Package changed: linux (Ubuntu) => transmission (Ubuntu) ** Description changed: - It's impossibile to run transmission.gtk (segmentation fault). + It's impossibile to run transmission-gtk (segmentation fault). + transmission-gtk 2.94 (d8e60ee44f) + warning: core file may not match specified executable file. [New LWP 19206] [New LWP 19207] [New LWP 19210] [New LWP 19209] [New LWP 19211] [New LWP 19213] [New LWP 19212] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `transmission-gtk /tmp/mozilla_intilinux0/edubuntu-12.04.5-dvd-i386.iso.torrent'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fbbb9be123f in gtk_css_node_ensure_style (cssnode=0x5594cd1f1a20, current_time=current_time@entry=8576248389) at ../../../../gtk/gtkcssnode.c:987 987 ../../../../gtk/gtkcssnode.c: No such file or directory. [Current thread is 1 (Thread 0x7fbbb14c6c80 (LWP 19206))] -- 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/1792811 Title: Transmission-gtk startup crash: doesn't start on 18.10 Status in transmission package in Ubuntu: New Bug description: It's impossibile to run transmission-gtk (segmentation fault). transmission-gtk 2.94 (d8e60ee44f) warning: core file may not match specified executable file. [New LWP 19206] [New LWP 19207] [New LWP 19210] [New LWP 19209] [New LWP 19211] [New LWP 19213] [New LWP 19212] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `transmission-gtk /tmp/mozilla_intilinux0/edubuntu-12.04.5-dvd-i386.iso.torrent'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fbbb9be123f in gtk_css_node_ensure_style (cssnode=0x5594cd1f1a20, current_time=current_time@entry=8576248389) at ../../../../gtk/gtkcssnode.c:987 987 ../../../../gtk/gtkcssnode.c: No such file or directory. [Current thread is 1 (Thread 0x7fbbb14c6c80 (LWP 19206))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1792811/+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 1644981] Re: ExFAT Formatted SD Cards not mounted
This bug outlived my Zenbook and I reformatted all my exFAT SD cards to FAT32 in the meantime to be able to use them, so I can't help anymore. Sorry. -- 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/1644981 Title: ExFAT Formatted SD Cards not mounted Status in linux package in Ubuntu: Incomplete Bug description: ExFAT formatted SD cards aren't mounted ob Ubuntu 16.04. The cards work perfectly on 12.04, 14.04 and Windows. Nov 26 11:21:22 bnasws02 kernel: [93798.228489] usb 1-8: new high-speed USB device number 7 using xhci_hcd Nov 26 11:21:22 bnasws02 kernel: [93798.358675] usb 1-8: New USB device found, idVendor=058f, idProduct=6366 Nov 26 11:21:22 bnasws02 kernel: [93798.358678] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 26 11:21:22 bnasws02 kernel: [93798.358680] usb 1-8: Product: Flash Card Reader/Writer Nov 26 11:21:22 bnasws02 kernel: [93798.358682] usb 1-8: Manufacturer: Generic Nov 26 11:21:22 bnasws02 kernel: [93798.358683] usb 1-8: SerialNumber: 058F63666485 Nov 26 11:21:22 bnasws02 kernel: [93798.359894] usb-storage 1-8:1.0: USB Mass Storage device detected Nov 26 11:21:22 bnasws02 kernel: [93798.359950] scsi host7: usb-storage 1-8:1.0 Nov 26 11:21:22 bnasws02 mtp-probe: checking bus 1, device 7: "/sys/devices/pci:00/:00:14.0/usb1/1-8" Nov 26 11:21:22 bnasws02 mtp-probe: bus: 1, device: 7 was not an MTP device Nov 26 11:21:23 bnasws02 kernel: [93799.357754] scsi 7:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 4 Nov 26 11:21:23 bnasws02 kernel: [93799.358491] sd 7:0:0:0: Attached scsi generic sg1 type 0 Nov 26 11:21:27 bnasws02 kernel: [93802.408280] sd 7:0:0:0: [sdb] Attached SCSI removable disk ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.47.50 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: sebastian 2240 F pulseaudio /dev/snd/controlC1: sebastian 2240 F pulseaudio CurrentDesktop: GNOME Date: Sat Nov 26 11:22:03 2016 HibernationDevice: RESUME=UUID=bdba64aa-c323-4ba7-a32d-bc49a2716cc7 InstallationDate: Installed on 2015-08-06 (477 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-11-21 (4 days ago) dmi.bios.date: 07/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305LA.204:bd07/06/2015:svnASUSTeKCOMPUTERINC.:pnUX305LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644981/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
found how to set the tag and marked status as confirmed. ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu Bionic) Status: In Progress => 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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1792790] Re: mismatch on package
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+question/674023 -- 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/1792790 Title: mismatch on package Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: LANG=C; sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 The following NEW packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 0 upgraded, 2 newly installed, 0 to remove and 4 not upgraded. 3 not fully installed or removed. Need to get 0 B/29.1 MB of archives. After this operation, 147 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 256831 files and directories currently installed.) Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_i386.deb ... diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb (--unpack): new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_amd64.deb ... diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb (--unpack): new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1792790/+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 1792790] Re: mismatch on package
What to do next, I cannot update my desktop. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** No longer affects: apport (Ubuntu) -- 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/1792790 Title: mismatch on package Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: LANG=C; sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 The following NEW packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 0 upgraded, 2 newly installed, 0 to remove and 4 not upgraded. 3 not fully installed or removed. Need to get 0 B/29.1 MB of archives. After this operation, 147 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 256831 files and directories currently installed.) Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_i386.deb ... diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb (--unpack): new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_amd64.deb ... diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb (--unpack): new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1792790/+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 1792789] Re: package libnvidia-compute-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different fro
** Tags removed: need-duplicate-check -- 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/1792789 Title: package libnvidia-compute-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: i don't have details ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-compute-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-35.38-generic 4.15.18 Uname: Linux 4.15.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sat Sep 15 13:14:22 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libnvidia-compute-390:390.77-0ubuntu0.18.04.1 Unpacking libnvidia-compute-390:amd64 (390.77-0ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-bXH9rr/35-libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2018-09-14 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 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/1792789/+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 1792789] [NEW] package libnvidia-compute-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different f
Public bug reported: i don't have details ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-compute-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-35.38-generic 4.15.18 Uname: Linux 4.15.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sat Sep 15 13:14:22 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libnvidia-compute-390:390.77-0ubuntu0.18.04.1 Unpacking libnvidia-compute-390:amd64 (390.77-0ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-bXH9rr/35-libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2018-09-14 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict package-from-proposed -- 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/1792789 Title: package libnvidia-compute-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: i don't have details ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-compute-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-35.38-generic 4.15.18 Uname: Linux 4.15.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sat Sep 15 13:14:22 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libnvidia-compute-390:390.77-0ubuntu0.18.04.1 Unpacking libnvidia-compute-390:amd64 (390.77-0ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-bXH9rr/35-libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2018-09-14 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 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/1792789/+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 1644981] Re: ExFAT Formatted SD Cards not mounted
Sebastian Nohn - please kindly provide the requested information, so that information about this bug is not lost. ** Changed in: linux (Ubuntu) Status: Expired => In Progress ** Changed in: linux (Ubuntu) Status: In Progress => 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/1644981 Title: ExFAT Formatted SD Cards not mounted Status in linux package in Ubuntu: Incomplete Bug description: ExFAT formatted SD cards aren't mounted ob Ubuntu 16.04. The cards work perfectly on 12.04, 14.04 and Windows. Nov 26 11:21:22 bnasws02 kernel: [93798.228489] usb 1-8: new high-speed USB device number 7 using xhci_hcd Nov 26 11:21:22 bnasws02 kernel: [93798.358675] usb 1-8: New USB device found, idVendor=058f, idProduct=6366 Nov 26 11:21:22 bnasws02 kernel: [93798.358678] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 26 11:21:22 bnasws02 kernel: [93798.358680] usb 1-8: Product: Flash Card Reader/Writer Nov 26 11:21:22 bnasws02 kernel: [93798.358682] usb 1-8: Manufacturer: Generic Nov 26 11:21:22 bnasws02 kernel: [93798.358683] usb 1-8: SerialNumber: 058F63666485 Nov 26 11:21:22 bnasws02 kernel: [93798.359894] usb-storage 1-8:1.0: USB Mass Storage device detected Nov 26 11:21:22 bnasws02 kernel: [93798.359950] scsi host7: usb-storage 1-8:1.0 Nov 26 11:21:22 bnasws02 mtp-probe: checking bus 1, device 7: "/sys/devices/pci:00/:00:14.0/usb1/1-8" Nov 26 11:21:22 bnasws02 mtp-probe: bus: 1, device: 7 was not an MTP device Nov 26 11:21:23 bnasws02 kernel: [93799.357754] scsi 7:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 4 Nov 26 11:21:23 bnasws02 kernel: [93799.358491] sd 7:0:0:0: Attached scsi generic sg1 type 0 Nov 26 11:21:27 bnasws02 kernel: [93802.408280] sd 7:0:0:0: [sdb] Attached SCSI removable disk ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.47.50 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: sebastian 2240 F pulseaudio /dev/snd/controlC1: sebastian 2240 F pulseaudio CurrentDesktop: GNOME Date: Sat Nov 26 11:22:03 2016 HibernationDevice: RESUME=UUID=bdba64aa-c323-4ba7-a32d-bc49a2716cc7 InstallationDate: Installed on 2015-08-06 (477 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-11-21 (4 days ago) dmi.bios.date: 07/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305LA.204:bd07/06/2015:svnASUSTeKCOMPUTERINC.:pnUX305LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644981/+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 1792600] 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 1792600 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/1792600 Title: cross-toolchain-base ftbfs with linux-4.18 Status in cross-toolchain-base package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: according to the build logs, the build process changed and calls the host compiler even for building the header files. This worked in 4.15, but not anymore in 4.18. To limit the build to one cross arch: CROSS_ARCHS=arm64 DEB_BUILD_OPTIONS=... dpkg-buildpackage -b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cross-toolchain-base/+bug/1792600/+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 1792600] Re: cross-toolchain-base ftbfs with linux-4.18
The better solution for this would be a build profile in the linux source that just builds the linux-libc-dev package. That way the cross- toolchain-base packaging would be independent from the linux build system. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Milestone: None => ubuntu-18.09 ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel (canonical-kernel) -- 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/1792600 Title: cross-toolchain-base ftbfs with linux-4.18 Status in cross-toolchain-base package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: according to the build logs, the build process changed and calls the host compiler even for building the header files. This worked in 4.15, but not anymore in 4.18. To limit the build to one cross arch: CROSS_ARCHS=arm64 DEB_BUILD_OPTIONS=... dpkg-buildpackage -b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cross-toolchain-base/+bug/1792600/+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
