[Kernel-packages] [Bug 1975454] Re: [Dell XPS 15 7590] Cannot resume after suspend
Hi, here's the needed log, finally :D ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975454/+attachment/5605240/+files/prevboot.txt ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975454 Title: [Dell XPS 15 7590] Cannot resume after suspend Status in linux package in Ubuntu: New Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1975454] Re: [Dell XPS 15 7590] Cannot resume after suspend
P.S. No, tlp is not installed on my machine $ sudo apt purge tlp Reading package lists... Done Building dependency tree... Done Reading state information... Done Package 'tlp' is not installed, so not removed I update this as soon as I'm able to get the journal log you need. Have a good day! -- 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/1975454 Title: [Dell XPS 15 7590] Cannot resume after suspend Status in linux package in Ubuntu: Incomplete Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1975454] Re: [Dell XPS 15 7590] Cannot resume after suspend
Hi Daniel, this just happened again but it seems I had no persistent journaling.. $ journalctl -b-1 > prevboot.txt An error was encountered while opening journal file or directory /var/log/journal, ignoring file: Not a directory Specifying boot ID or boot offset has no effect, no persistent journal was found. I'm now setting it up following this guide: https://gist.github.com/JPvRiel/b7c185833da32631fa6ce65b40836887 I filed another bug report related to this, but for something that happened after the reboot: - Bluetooth icon appears and disappears after reboot https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1981117 -- 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/1975454 Title: [Dell XPS 15 7590] Cannot resume after suspend Status in linux package in Ubuntu: Incomplete Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
[Kernel-packages] [Bug 1981117] Re: Bluetooth icon appears and disappears after reboot
** Attachment added: "Clip showing the icon appearing / disappearing" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1981117/+attachment/5602108/+files/2022-07-09%2010-27-38.mp4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1981117 Title: Bluetooth icon appears and disappears after reboot Status in bluez package in Ubuntu: New Bug description: This morning I tried to use my laptop. I think it was suspended, but not deep suspended (screen off, but was attached to AC). When I tried resuming it, the screen went on, but instead of the gnome login, I was greeted by a black screen with some errors. ``` Bluetooth: hci0: Timed out waiting for suspend events Bluetooth: hci0: Suspend timeout bit: 6 Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` As I could do nothing, I rebooted the laptop (force off with power button and turned on). As I logged in, the Bluetooth indicator in the top right panel started appearing and disappearing continuously. I normally have a Bluetooth mouse connected, so I thought it was trying to pair with it. So I went into the Bluetooth tab from Settings and I was asked permission to pair the device. After allowing that permission appear / disappear issue went out. I think something is wrong with this flow. I think the service for the Bluetooth should handle these issues better, not blinking, but asking such permission that it required from the beginning. As it is it looks broken and poorly discoverable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 10:31:18 2022 InstallationDate: Installed on 2020-04-03 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 84:C5:A6:94:9C:96 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:233857 acl:2324 sco:0 events:14387 errors:0 TX bytes:892713 acl:1283 sco:0 commands:8484 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1981117/+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 1981117] Re: Bluetooth icon appears and disappears after reboot
** Attachment added: "Dialog asking pairing permission" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1981117/+attachment/5602107/+files/Screenshot%20from%202022-07-09%2010-28-36.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1981117 Title: Bluetooth icon appears and disappears after reboot Status in bluez package in Ubuntu: New Bug description: This morning I tried to use my laptop. I think it was suspended, but not deep suspended (screen off, but was attached to AC). When I tried resuming it, the screen went on, but instead of the gnome login, I was greeted by a black screen with some errors. ``` Bluetooth: hci0: Timed out waiting for suspend events Bluetooth: hci0: Suspend timeout bit: 6 Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` As I could do nothing, I rebooted the laptop (force off with power button and turned on). As I logged in, the Bluetooth indicator in the top right panel started appearing and disappearing continuously. I normally have a Bluetooth mouse connected, so I thought it was trying to pair with it. So I went into the Bluetooth tab from Settings and I was asked permission to pair the device. After allowing that permission appear / disappear issue went out. I think something is wrong with this flow. I think the service for the Bluetooth should handle these issues better, not blinking, but asking such permission that it required from the beginning. As it is it looks broken and poorly discoverable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 10:31:18 2022 InstallationDate: Installed on 2020-04-03 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 84:C5:A6:94:9C:96 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:233857 acl:2324 sco:0 events:14387 errors:0 TX bytes:892713 acl:1283 sco:0 commands:8484 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1981117/+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 1981117] [NEW] Bluetooth icon appears and disappears after reboot
Public bug reported: This morning I tried to use my laptop. I think it was suspended, but not deep suspended (screen off, but was attached to AC). When I tried resuming it, the screen went on, but instead of the gnome login, I was greeted by a black screen with some errors. ``` Bluetooth: hci0: Timed out waiting for suspend events Bluetooth: hci0: Suspend timeout bit: 6 Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` As I could do nothing, I rebooted the laptop (force off with power button and turned on). As I logged in, the Bluetooth indicator in the top right panel started appearing and disappearing continuously. I normally have a Bluetooth mouse connected, so I thought it was trying to pair with it. So I went into the Bluetooth tab from Settings and I was asked permission to pair the device. After allowing that permission appear / disappear issue went out. I think something is wrong with this flow. I think the service for the Bluetooth should handle these issues better, not blinking, but asking such permission that it required from the beginning. As it is it looks broken and poorly discoverable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 10:31:18 2022 InstallationDate: Installed on 2020-04-03 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 84:C5:A6:94:9C:96 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:233857 acl:2324 sco:0 events:14387 errors:0 TX bytes:892713 acl:1283 sco:0 commands:8484 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1981117 Title: Bluetooth icon appears and disappears after reboot Status in bluez package in Ubuntu: New Bug description: This morning I tried to use my laptop. I think it was suspended, but not deep suspended (screen off, but was attached to AC). When I tried resuming it, the screen went on, but instead of the gnome login, I was greeted by a black screen with some errors. ``` Bluetooth: hci0: Timed out waiting for suspend events Bluetooth: hci0: Suspend timeout bit: 6 Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` As I could do nothing, I rebooted the laptop (force off with power button and turned on). As I logged in, the Bluetooth indicator in the top right panel started appearing and disappearing continuously. I normally have a Bluetooth mouse connected, so I thought it was trying to pair with it. So I went into the Bluetooth tab from Settings and I was asked permission to pair the device. After allowing that permission appear / disappear issue went out. I think something is wrong with this flow. I think the service for the Bluetooth should handle these issues better, not blinking, but asking such permission that it required from the beginning. As it is it looks broken and poorly discoverable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 10:31:18 2022 InstallationDate: Installed on 2020-04-03 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage:
[Kernel-packages] [Bug 1881120] Re: linux-oem-5.6-tools-common and -tools-host should be dropped
It's likely bug 1877849 is related to this: it's for issues with dependencies between linux-oem-5.6-tools-common and linux-tools-common. -- 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/1881120 Title: linux-oem-5.6-tools-common and -tools-host should be dropped Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] linux-oem-5.6 built -tools-common and -tools-host, which conflict with the master kernel versions. These shouldn't be built at all. [Test case] Check that upgrade removes the oem versions. [Regression potential] shouldn't be any -- Updating 20.04, unaware of details package linux-oem-5.6-tools-common 5.6.0-1008.8 [modified: usr/share /bash-completion/completions/bpftool usr/share/man/man1/cpupower.1.gz usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf- archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1 /perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1 /perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1 /perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1 /perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1 /perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script- perl.1.gz usr/share/man/man1/perf-script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf- timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1 /perf-trace.1.gz usr/share/man/man1/perf-version.1.gz usr/share/man/man1/perf.1.gz usr/share/man/man8/bpftool-map.8.gz usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.4.0-31.35 ProblemType: Package DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 28 07:43:09 2020 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.4.0-31.35 InstallationDate: Installed on 2020-04-28 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: linux-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881120/+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 1877849] Re: conflicting packages while installing perf
Temporary fix: ``` sudo dpkg --remove linux-oem-5.6-tools-common sudo apt-get install --fix-broken ``` -- 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/1877849 Title: conflicting packages while installing perf Status in linux package in Ubuntu: Confirmed Bug description: I was trying to run perf, but I discovered it was not installed ``` $ perf stat -d so4/so-benchmark 100 Command 'perf' not found, but can be installed with: sudo apt install linux-oem-5.6-tools-common # version 5.6.0-1008.8, or sudo apt install linux-tools-common # version 5.4.0-29.33 ``` So I decided to install the latest version, so as `linux-oem-5.6-tools-common`. ``` $ sudo apt install linux-oem-5.6-tools-common Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: linux-oem-5.6-tools-common 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 174 kB of archives. After this operation, 395 kB of additional disk space will be used. Get:1 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-oem-5.6-tools-common all 5.6.0-1008.8 [174 kB] Fetched 174 kB in 0s (446 kB/s) Selecting previously unselected package linux-oem-5.6-tools-common. (Reading database ... 326483 files and directories currently installed.) Preparing to unpack .../linux-oem-5.6-tools-common_5.6.0-1008.8_all.deb ... Progress: [ 0%] [.] Unpacking linux-oem-5.6-tools-common (5.6.0-1008.8) ...] Setting up linux-oem-5.6-tools-common (5.6.0-1008.8) ...#..] Progress: [ 60%] [#] Processing triggers for man-db (2.9.1-1) ...#..] ``` Then it finished, so I wanted to run perf finally. ``` $ perf stat -d so4/so-benchmark 100 WARNING: perf not found for kernel 5.4.0-28 You may need to install the following packages for this specific kernel: linux-tools-5.4.0-28-generic linux-cloud-tools-5.4.0-28-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic ``` Ok, so I discover that my kernel is not compatible with version 5.6. But apt suggests to install one of those, so I pick `linux-tools- generic` so it stays up to date. ``` $ sudo apt install linux-tools-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-tools-5.4.0-29 linux-tools-5.4.0-29-generic linux-tools-common The following NEW packages will be installed: linux-tools-5.4.0-29 linux-tools-5.4.0-29-generic linux-tools-common linux-tools-generic 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 5 759 kB of archives. After this operation, 25,7 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-common all 5.4.0-29.33 [186 kB] Get:2 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-5.4.0-29 amd64 5.4.0-29.33 [5 568 kB] Get:3 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-5.4.0-29-generic amd64 5.4.0-29.33 [1 988 B] Get:4 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-generic amd64 5.4.0.29.34 [2 604 B] Fetched 5 759 kB in 7s (878 kB/s) Selecting previously unselected package linux-tools-common. (Reading database ... 326549 files and directories currently installed.) Preparing to unpack .../linux-tools-common_5.4.0-29.33_all.deb ... Progress: [ 0%] [.] Unpacking linux-tools-common (5.4.0-29.33) ] dpkg: error processing archive /var/cache/apt/archives/linux-tools-common_5.4.0-29.33_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package linux-tools-5.4.0-29.
[Kernel-packages] [Bug 1877849] [NEW] conflicting packages while installing perf
Public bug reported: I was trying to run perf, but I discovered it was not installed ``` $ perf stat -d so4/so-benchmark 100 Command 'perf' not found, but can be installed with: sudo apt install linux-oem-5.6-tools-common # version 5.6.0-1008.8, or sudo apt install linux-tools-common # version 5.4.0-29.33 ``` So I decided to install the latest version, so as `linux-oem-5.6-tools-common`. ``` $ sudo apt install linux-oem-5.6-tools-common Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: linux-oem-5.6-tools-common 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 174 kB of archives. After this operation, 395 kB of additional disk space will be used. Get:1 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-oem-5.6-tools-common all 5.6.0-1008.8 [174 kB] Fetched 174 kB in 0s (446 kB/s) Selecting previously unselected package linux-oem-5.6-tools-common. (Reading database ... 326483 files and directories currently installed.) Preparing to unpack .../linux-oem-5.6-tools-common_5.6.0-1008.8_all.deb ... Progress: [ 0%] [.] Unpacking linux-oem-5.6-tools-common (5.6.0-1008.8) ...] Setting up linux-oem-5.6-tools-common (5.6.0-1008.8) ...#..] Progress: [ 60%] [#] Processing triggers for man-db (2.9.1-1) ...#..] ``` Then it finished, so I wanted to run perf finally. ``` $ perf stat -d so4/so-benchmark 100 WARNING: perf not found for kernel 5.4.0-28 You may need to install the following packages for this specific kernel: linux-tools-5.4.0-28-generic linux-cloud-tools-5.4.0-28-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic ``` Ok, so I discover that my kernel is not compatible with version 5.6. But apt suggests to install one of those, so I pick `linux-tools-generic` so it stays up to date. ``` $ sudo apt install linux-tools-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-tools-5.4.0-29 linux-tools-5.4.0-29-generic linux-tools-common The following NEW packages will be installed: linux-tools-5.4.0-29 linux-tools-5.4.0-29-generic linux-tools-common linux-tools-generic 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 5 759 kB of archives. After this operation, 25,7 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-common all 5.4.0-29.33 [186 kB] Get:2 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-5.4.0-29 amd64 5.4.0-29.33 [5 568 kB] Get:3 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-5.4.0-29-generic amd64 5.4.0-29.33 [1 988 B] Get:4 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-generic amd64 5.4.0.29.34 [2 604 B] Fetched 5 759 kB in 7s (878 kB/s) Selecting previously unselected package linux-tools-common. (Reading database ... 326549 files and directories currently installed.) Preparing to unpack .../linux-tools-common_5.4.0-29.33_all.deb ... Progress: [ 0%] [.] Unpacking linux-tools-common (5.4.0-29.33) ] dpkg: error processing archive /var/cache/apt/archives/linux-tools-common_5.4.0-29.33_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package linux-tools-5.4.0-29. Preparing to unpack .../linux-tools-5.4.0-29_5.4.0-29.33_amd64.deb ... Unpacking linux-tools-5.4.0-29 (5.4.0-29.33) ..] Selecting previously unselected package linux-tools-5.4.0-29-generic...] Preparing to unpack .../linux-tools-5.4.0-29-generic_5.4.0-29.33_amd64.deb ... Unpacking linux-tools-5.4.0-29-generic (5.4.0-29.33)
[Kernel-packages] [Bug 1872367] Re: Cannot resume from suspend
These are some logs labelled as important before the laptop stopped logging: apr 12 18:23:50 kernel: iwlwifi :3b:00.0: failed to update MAC 84:c5:a6:94:9c:92 apr 12 14:54:52 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=762435 end=762436) time 1022 us, min 1073, max 1079, scanline start 1064, end 1130 apr 12 14:54:52 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=762435 end=762436) time 1022 us, min 1073, max 1079, scanline start 1064, end 1130 apr 12 14:54:50 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=762294 end=762295) time 916 us, min 1073, max 1079, scanline start 1049, end 1108 apr 12 14:54:49 kernel: iwlwifi :3b:00.0: PHY ctxt cmd error. ret=-5 apr 12 13:29:56 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=456662 end=456663) time 1229 us, min 1073, max 1079, scanline start 1049, end 1122 apr 12 13:29:55 kernel: iwlwifi :3b:00.0: PHY ctxt cmd error. ret=-5 apr 12 13:29:47 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=456096 end=456097) time 1395 us, min 1073, max 1079, scanline start 1046, end 1139 -- 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/1872367 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I often keep my laptop for some hours without using it, with the charging cable plugged. Sometimes when I want to use it again, the screen stays off, and cannot say if it's still suspended or just the screen doesn't turn on. One thing that I find suspicious is that checking the logs I have some only until some time after I last used it (few hours later) and then none util the next boot. To reboot the laptop I kept the power button down for about 10 seconds to turn it on, and then I could turn it on again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabio 2019 F pulseaudio CurrentDesktop: GNOME Date: Mon Apr 13 00:33:26 2020 InstallationDate: Installed on 2020-04-03 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872367/+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 1872367] [NEW] Cannot resume from suspend
Public bug reported: I often keep my laptop for some hours without using it, with the charging cable plugged. Sometimes when I want to use it again, the screen stays off, and cannot say if it's still suspended or just the screen doesn't turn on. One thing that I find suspicious is that checking the logs I have some only until some time after I last used it (few hours later) and then none util the next boot. To reboot the laptop I kept the power button down for about 10 seconds to turn it on, and then I could turn it on again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabio 2019 F pulseaudio CurrentDesktop: GNOME Date: Mon Apr 13 00:33:26 2020 InstallationDate: Installed on 2020-04-03 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1872367 Title: Cannot resume from suspend Status in linux package in Ubuntu: New Bug description: I often keep my laptop for some hours without using it, with the charging cable plugged. Sometimes when I want to use it again, the screen stays off, and cannot say if it's still suspended or just the screen doesn't turn on. One thing that I find suspicious is that checking the logs I have some only until some time after I last used it (few hours later) and then none util the next boot. To reboot the laptop I kept the power button down for about 10 seconds to turn it on, and then I could turn it on again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabio 2019 F pulseaudio CurrentDesktop: GNOME Date: Mon Apr 13 00:33:26 2020 InstallationDate: Installed on 2020-04-03 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872367/+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 1839773] Re: MicroSD not mounted when inserted, used to work correctly
I'm not sure, you can close it, I'll eventually file a new one if this behaviour happens again. -- 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/1839773 Title: MicroSD not mounted when inserted, used to work correctly Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an adaptor in my laptop's SD slot, but it was not mounted nor apparently detected. I'm certain that until few weeks ago it was working correctly, so I suppose the cause to be an update regression. I tested the same card on another laptop using Ubuntu 18.04 LTS and it works correctly. Also, I have tested another card (16GB) on the 19.10 laptop, and it's detected and mounted correctly. Summary: - 16GB SD card, FAT32 - Works with all Ubuntu versions - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 19.10, at least 2 weeks ago was still working. I'd be happy to help debugging this issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-10-generic 5.2.0-10.11 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fabio 2086 F pulseaudio /dev/snd/controlC0: fabio 2086 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 19:50:53 2019 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=0e34c56e-8605-499f-9588-f09829ff1e81 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-02-03 (188 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 19:51:12.078: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to eoan on 2019-07-21 (21 days ago) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JK dmi.product.sku: ASUS-NotebookSKU 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/1839773/+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 1839773] Re: MicroSD not mounted when inserted, used to work correctly
I could now make it work, reinserting it again after removing it.. -- 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/1839773 Title: MicroSD not mounted when inserted, used to work correctly Status in linux package in Ubuntu: New Bug description: Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an adaptor in my laptop's SD slot, but it was not mounted nor apparently detected. I'm certain that until few weeks ago it was working correctly, so I suppose the cause to be an update regression. I tested the same card on another laptop using Ubuntu 18.04 LTS and it works correctly. Also, I have tested another card (16GB) on the 19.10 laptop, and it's detected and mounted correctly. Summary: - 16GB SD card, FAT32 - Works with all Ubuntu versions - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 19.10, at least 2 weeks ago was still working. I'd be happy to help debugging this issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-10-generic 5.2.0-10.11 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fabio 2086 F pulseaudio /dev/snd/controlC0: fabio 2086 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 19:50:53 2019 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=0e34c56e-8605-499f-9588-f09829ff1e81 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-02-03 (188 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 19:51:12.078: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to eoan on 2019-07-21 (21 days ago) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JK dmi.product.sku: ASUS-NotebookSKU 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/1839773/+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 1839773] Re: MicroSD not mounted when inserted, used to work correctly
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287] (rev 01) Subsystem: ASUSTeK Computer Inc. RTL8411B PCI Express Card Reader [1043:202f] Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at f7815000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at f780 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [b0] MSI-X: Enable- Count=1 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [170] Latency Tolerance Reporting Capabilities: [178] L1 PM Substates Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci -- 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/1839773 Title: MicroSD not mounted when inserted, used to work correctly Status in linux package in Ubuntu: New Bug description: Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an adaptor in my laptop's SD slot, but it was not mounted nor apparently detected. I'm certain that until few weeks ago it was working correctly, so I suppose the cause to be an update regression. I tested the same card on another laptop using Ubuntu 18.04 LTS and it works correctly. Also, I have tested another card (16GB) on the 19.10 laptop, and it's detected and mounted correctly. Summary: - 16GB SD card, FAT32 - Works with all Ubuntu versions - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 19.10, at least 2 weeks ago was still working. I'd be happy to help debugging this issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-10-generic 5.2.0-10.11 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fabio 2086 F pulseaudio /dev/snd/controlC0: fabio 2086 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 19:50:53 2019 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=0e34c56e-8605-499f-9588-f09829ff1e81 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-02-03 (188 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 19:51:12.078: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to eoan on 2019-07-21 (21 days ago) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JK dmi.product.sku: ASUS-NotebookSKU 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/1839773/+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 1839773] [NEW] MicroSD not mounted when inserted, used to work correctly
Public bug reported: Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an adaptor in my laptop's SD slot, but it was not mounted nor apparently detected. I'm certain that until few weeks ago it was working correctly, so I suppose the cause to be an update regression. I tested the same card on another laptop using Ubuntu 18.04 LTS and it works correctly. Also, I have tested another card (16GB) on the 19.10 laptop, and it's detected and mounted correctly. Summary: - 16GB SD card, FAT32 - Works with all Ubuntu versions - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 19.10, at least 2 weeks ago was still working. I'd be happy to help debugging this issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-10-generic 5.2.0-10.11 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fabio 2086 F pulseaudio /dev/snd/controlC0: fabio 2086 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 19:50:53 2019 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=0e34c56e-8605-499f-9588-f09829ff1e81 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-02-03 (188 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 19:51:12.078: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to eoan on 2019-07-21 (21 days ago) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an adaptor in my laptop's SD slot, but it was not mounted nor apparently detected. I'm certain that until few weeks ago it was working correctly, so I suppose the cause to be an update regression. I tested the same card on another laptop using Ubuntu 18.04 LTS and it works correctly. Also, I have tested another card (16GB) on the 19.10 laptop, and it's detected and mounted correctly. Summary: - 16GB SD card, FAT32 - Works with all Ubuntu versions - - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 19.04, at least 2 weeks ago was still working. + - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 19.10, at least 2 weeks ago was still working. I'd be happy to help debugging this issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-10-generic 5.2.0-10.11 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: fabio 2086 F pulseaudio - /dev/snd/controlC0: fabio 2086 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: fabio 2086 F pulseaudio + /dev/snd/controlC0: fabio 2086 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 19:50:53 2019 GvfsMonitorError: - This tool has been deprecated, use 'gio mount' instead. - See 'gio help mount' for more info. + This tool has been
[Kernel-packages] [Bug 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]
I think tlp was responsible for the issue, as after uninstalling it, I could not reproduce it consistently (only happens very rarely). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1788807 Title: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565] Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Bug description: When I suspend my laptop, it often happens that the bluetooth stops working. From gnome settings it is shown like if I had no bluetooth device at all. $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 'blue|firm' 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter [1a3b:2130] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287] (rev 01) -- 04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1043:200f] Kernel driver in use: r8169 Kernel modules: r8169 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4.15.0-32-generic [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [ 35.407491] Bluetooth: Core ver 2.22 [ 35.407504] Bluetooth: HCI device and connection manager initialized [ 35.407506] Bluetooth: HCI socket layer initialized [ 35.407507] Bluetooth: L2CAP socket layer initialized [ 35.407510] Bluetooth: SCO socket layer initialized [ 53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 53.501780] Bluetooth: BNEP filters: protocol multicast [ 53.501783] Bluetooth: BNEP socket layer initialized [ 87.220137] Bluetooth: RFCOMM TTY layer initialized [ 87.220143] Bluetooth: RFCOMM socket layer initialized [ 87.220149] Bluetooth: RFCOMM ver 1.11 [ 1675.503865] usb 1-5: device firmware changed [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err [ 1681.095546] Bluetooth: Loading patch file failed [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=10248 label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined" Trying to use bluetooth from bluetoothctl $ bluetoothctl Agent registered [bluetooth]# scan on No default controller available Trying to restart the bluetooth service doesn't produce any effect: $ sudo service bluetooth restart Getting bluetooth service status: $ sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago Docs: man:bluetoothd(8) Main PID: 24999 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─24999 /usr/lib/bluetooth/bluetoothd elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service... elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service. elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service... elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48 elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service. elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management interface 1 lines 1-17/17 (END) Reloading the driver: $ sudo modprobe -r btusb; sudo modprobe btusb; $ sudo service bluetooth restart None of these attempts could solve the issue. What happens? Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth controller is no longer recognised and bluetooth service cannot be used anymore. What would you expect? Bluetooth controller to be recognised and working also after resume. ProblemType: Bug DistroRelease:
[Kernel-packages] [Bug 1794847] Re: Installing proprietary drivers causes font glitches
I fixed the issue deleting some fontconfig configurations in my home folder. I don't really know how this caused the issue, and how the files were created in first place. Use with caution: rm -rf ~/.local/share/fontconfig ~/.fonts.conf.d ~/.fonts.conf ** 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/1794847 Title: Installing proprietary drivers causes font glitches Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: I recently enabled the nvidia proprietary drivers and since then I'm experiencing font glitches which are making it difficult for me to read the text. The glitch consist in slight "shadow" lines on the right or left of a letter, in red or green. I recently also installed wine and wine-staging, with their recommended packages. My graphic card is an optimus one, so I have both an nvidia and Intel card. Unfortunately when I try to switch back to the Intel card, the nouveau drivers are loaded instead, so I cannot test if reverting to Intel can solve the glitch. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 20:30:28 2018 InstallationDate: Installed on 2017-08-21 (402 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) 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/1794847/+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 1794847] Re: Installing proprietary drivers causes font glitches
** Description changed: I recently enabled the nvidia proprietary drivers and since then I'm experiencing font glitches which are making it difficult for me to read the text. + + The glitch consist in slight "shadow" lines on the right or left of a + letter, in red or green. + + I recently also installed wine and wine-staging, with their recommended + packages. + + My graphic card is an optimus one, so I have both an nvidia and Intel + card. Unfortunately when I try to switch back to the Intel card, the + nouveau drivers are loaded instead, so I cannot test if reverting to + Intel can solve the glitch. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 20:30:28 2018 InstallationDate: Installed on 2017-08-21 (402 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1794847 Title: Installing proprietary drivers causes font glitches Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I recently enabled the nvidia proprietary drivers and since then I'm experiencing font glitches which are making it difficult for me to read the text. The glitch consist in slight "shadow" lines on the right or left of a letter, in red or green. I recently also installed wine and wine-staging, with their recommended packages. My graphic card is an optimus one, so I have both an nvidia and Intel card. Unfortunately when I try to switch back to the Intel card, the nouveau drivers are loaded instead, so I cannot test if reverting to Intel can solve the glitch. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 20:30:28 2018 InstallationDate: Installed on 2017-08-21 (402 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) 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/1794847/+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 1794847] [NEW] Installing proprietary drivers causes font glitches
Public bug reported: I recently enabled the nvidia proprietary drivers and since then I'm experiencing font glitches which are making it difficult for me to read the text. The glitch consist in slight "shadow" lines on the right or left of a letter, in red or green. I recently also installed wine and wine-staging, with their recommended packages. My graphic card is an optimus one, so I have both an nvidia and Intel card. Unfortunately when I try to switch back to the Intel card, the nouveau drivers are loaded instead, so I cannot test if reverting to Intel can solve the glitch. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 20:30:28 2018 InstallationDate: Installed on 2017-08-21 (402 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "Screenshot of my current font rendering" https://bugs.launchpad.net/bugs/1794847/+attachment/5193688/+files/Screenshot%20from%202018-09-27%2020-35-43.png -- 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/1794847 Title: Installing proprietary drivers causes font glitches Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I recently enabled the nvidia proprietary drivers and since then I'm experiencing font glitches which are making it difficult for me to read the text. The glitch consist in slight "shadow" lines on the right or left of a letter, in red or green. I recently also installed wine and wine-staging, with their recommended packages. My graphic card is an optimus one, so I have both an nvidia and Intel card. Unfortunately when I try to switch back to the Intel card, the nouveau drivers are loaded instead, so I cannot test if reverting to Intel can solve the glitch. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 20:30:28 2018 InstallationDate: Installed on 2017-08-21 (402 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) 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/1794847/+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 1752336] [NEW] BUG: Bad page map in process CompositorTileW pte:94aadfb0 pmd:943ae067
Public bug reported: This just happened ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm3937 F pulseaudio fabio 4501 F pulseaudio /dev/snd/controlC0: gdm3937 F pulseaudio fabio 4501 F pulseaudio Date: Wed Feb 28 16:18:53 2018 Failure: oops HibernationDevice: RESUME=UUID=f6770099-4a42-48e3-b4ab-588190b2a701 InstallationDate: Installed on 2017-08-21 (191 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 008: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 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: kerneloops-daemon N/A SourcePackage: linux Title: BUG: Bad page map in process CompositorTileW pte:94aadfb0 pmd:943ae067 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic kernel-oops -- 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/1752336 Title: BUG: Bad page map in process CompositorTileW pte:94aadfb0 pmd:943ae067 Status in linux package in Ubuntu: Confirmed Bug description: This just happened ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm3937 F pulseaudio fabio 4501 F pulseaudio /dev/snd/controlC0: gdm3937 F pulseaudio fabio 4501 F pulseaudio Date: Wed Feb 28 16:18:53 2018 Failure: oops HibernationDevice: RESUME=UUID=f6770099-4a42-48e3-b4ab-588190b2a701 InstallationDate: Installed on 2017-08-21 (191 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 008: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 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: kerneloops-daemon N/A SourcePackage: linux Title: BUG: Bad page map in process CompositorTileW pte:94aadfb0 pmd:943ae067 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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:
