[Kernel-packages] [Bug 1942133] Re: Nvidia driver packages prevent suspend due to leftover Systemd units
Thanks for reporting this. I can confirm the bug and the proposed solution. I ran into issues with the 470 driver and hence uninstalled it. Since then my computer refused to suspend or hibernate. I always just got logged out. After deleting the following files, it works so far: /etc/systemd/system/systemd-suspend-service.requires/nvidia-suspend.service /etc/systemd/system/systemd-suspend-service.requires/nvidia-resume.service /etc/systemd/system/systemd-hibernate-service.requires/nvidia-suspend.service /etc/systemd/system/systemd-hibernate-service.requires/nvidia-resume.service Operating System: Kubuntu 21.10 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-28-generic (64-bit) Graphics Platform: X11 Processors: 16 × 11th Gen Intel® Core™ i9-11950H @ 2.60GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1942133 Title: Nvidia driver packages prevent suspend due to leftover Systemd units Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: When the nvidia driver packages are uninstalled, they leave some symlinks that prevent suspend. I whink that, when attempting to suspend, the error is logged as this (edited): ModemManager[3287]: [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying upowerd[5771]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying dbus-daemon[2888]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.53' (uid=1000 pid=8227 comm="/usr/lib/x86_64-linux-gnu/indicator-session/indica" label="unconfined") systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: systemd-logind.service: Failed with result 'exit-code'. systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 7. systemd[1]: Stopped Login Service. systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. systemd[1]: Starting Login Service... I've deleted the problematic symlinks while trying to solving the problem, however, they should be these: /etc/systemd/system/systemd-suspend-service.requires/nvidia-suspend.service /etc/systemd/system/systemd-suspend-service.requires/nvidia-resume.service /etc/systemd/system/systemd-hibernate-service.requires/nvidia-suspend.service /etc/systemd/system/systemd-hibernate-service.requires/nvidia-resume.service I've briefly checked before removing them; at least a couple of them were masked, but they were still causing the problem. I don't see any reason why they should hang around the systemd configuration once the packages are purged. Additionally, this is a problem that is not easy to diagnose. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-470 (not installed) ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: MATE Date: Mon Aug 30 21:10:52 2021 LiveMediaBuild: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-470 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-470/+bug/1942133/+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 1811164] [NEW] apt cannot find linux-libc-dev
Public bug reported: Running: xenial Problem: After running apt-get update, I still get this upon apt-get install: Err:60 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-libc-dev amd64 4.4.0-140.166 404 Not Found [IP: 91.189.88.161 80] All other packages install fine. Looking at the package repo at http://archive.ubuntu.com/ubuntu/dists /xenial-updates/main/ it appears the amd64 entry was updated today, so I assume that's when the error was introduced. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: linux-libc-dev xenial-updates -- 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/1811164 Title: apt cannot find linux-libc-dev Status in linux package in Ubuntu: Incomplete Bug description: Running: xenial Problem: After running apt-get update, I still get this upon apt-get install: Err:60 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-libc-dev amd64 4.4.0-140.166 404 Not Found [IP: 91.189.88.161 80] All other packages install fine. Looking at the package repo at http://archive.ubuntu.com/ubuntu/dists /xenial-updates/main/ it appears the amd64 entry was updated today, so I assume that's when the error was introduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811164/+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 1217640] Re: Kernelpanic when accessing defect SD-card
kernel-bug-exists-upstream (don't know where to set this status.) With acutal kernel 3.11, kernelpanic occurs also. Different output, see picture of screen, attached. ** Attachment added: "DSC_3330.JPG" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217640/+attachment/3792958/+files/DSC_3330.JPG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217640 Title: Kernelpanic when accessing defect SD-card Status in “linux” package in Ubuntu: Incomplete Bug description: Somehow crashed my SD-card when using in a digital camera. The camera suddenly mentioned the card to be defect. Card: SanDisk Extreme 16GB, 45MB/s SDHC Inserting was fine, in the Taskbar, a new USB-Device appeared. But when accessing either with dolphin or trying to mount manually, a kernelpanic occured. See attached picture. The same kernelpanic occured when trying to access the card with photorec. Photorec doesn't mount, but accesses the raw device /dev/sdx. There seems to be a bug in the USB-stack which was probably not tested, due to a missing defect SD-card. If this is not a Ubuntu-Kernel issue, please forward to kernel.org, or wherever appropriate. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mf 2043 F pulseaudio /dev/snd/pcmC0D0p: mf 2043 F...m pulseaudio Date: Wed Aug 28 03:12:54 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=435a747d-5ac6-472c-a4af-e6613dbda420 InstallationDate: Installed on 2013-07-17 (41 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. UX32VD MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=b6447f8b-7100-4523-a347-d55220bcaf12 ro quiet splash "acpi_osi=!Windows 2012" pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 i915.i915_enable_rc6=1 resume=/dev/sda5 rootfstype=ext4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A linux-firmware1.106 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD 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/1217640/+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 1217640] [NEW] Kernelpanic when accessing defect SD-card
Public bug reported: Somehow crashed my SD-card when using in a digital camera. The camera suddenly mentioned the card to be defect. Card: SanDisk Extreme 16GB, 45MB/s SDHC Inserting was fine, in the Taskbar, a new USB-Device appeared. But when accessing either with dolphin or trying to mount manually, a kernelpanic occured. See attached picture. The same kernelpanic occured when trying to access the card with photorec. Photorec doesn't mount, but accesses the raw device /dev/sdx. There seems to be a bug in the USB-stack which was probably not tested, due to a missing defect SD-card. If this is not a Ubuntu-Kernel issue, please forward to kernel.org, or wherever appropriate. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mf 2043 F pulseaudio /dev/snd/pcmC0D0p: mf 2043 F...m pulseaudio Date: Wed Aug 28 03:12:54 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=435a747d-5ac6-472c-a4af-e6613dbda420 InstallationDate: Installed on 2013-07-17 (41 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. UX32VD MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=b6447f8b-7100-4523-a347-d55220bcaf12 ro quiet splash "acpi_osi=!Windows 2012" pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 i915.i915_enable_rc6=1 resume=/dev/sda5 rootfstype=ext4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A linux-firmware1.106 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug raring staging ** Attachment added: "DSC_3003.JPG" https://bugs.launchpad.net/bugs/1217640/+attachment/3790956/+files/DSC_3003.JPG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217640 Title: Kernelpanic when accessing defect SD-card Status in “linux” package in Ubuntu: Confirmed Bug description: Somehow crashed my SD-card when using in a digital camera. The camera suddenly mentioned the card to be defect. Card: SanDisk Extreme 16GB, 45MB/s SDHC Inserting was fine, in the Taskbar, a new USB-Device appeared. But when accessing either with dolphin or trying to mount manually, a kernelpanic occured. See attached picture. The same kernelpanic occured when trying to access the card with photorec. Photorec doesn't mount, but accesses the raw device /dev/sdx. There seems to be a bug in the USB-stack which was probably not tested, due to a missing defect SD-card. If this is not a Ubuntu-Kernel issue, please forward to kernel.org, or wherever appropriate. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mf 2043 F pulseaudio /dev/snd/pcmC0D0p: mf 2043 F...m pulseaudio Date: Wed Aug 28 03:12:54 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=435a747d-5ac6-472c-a4af-e6613dbda420 InstallationDate: Installed on 2013-07-17 (41 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. UX32VD MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=b6447f8b-7100-4523-a347-d55220bcaf12 ro quiet splash "acpi_osi=!Windows 2012" pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 i915.i915_enable_rc6=1 resume=/dev/sda5 rootfstype=ext4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A l
