[Bug 1976149] [NEW] Super + key keyboard shortcuts are not intuitive
Public bug reported: Some Super + key keyboard shortcuts are set to launch some Xubuntu applications by default. They are hard to remember, and the shortcuts may be pressed accidentally, so IMO it is better to not set these shortcuts by default. Especially Super + digit shortcuts are unintuitive. User may have better use for those. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xfce4-settings 4.14.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat May 28 14:01:49 2022 InstallationDate: Installed on 2019-12-05 (904 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: xfce4-settings UpgradeStatus: Upgraded to focal on 2020-07-10 (687 days ago) ** Affects: xfce4-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976149 Title: Super + key keyboard shortcuts are not intuitive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1976149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615381] Re: apt-get autoremove may remove current kernel
So there is neither /etc/apt/apt.conf.d/01autoremove-kernels nor /etc/kernel/postinst.d/apt-auto-removal anymore. Anyway I could not make 'apt autoremove' try to remove current kernel anymore. Tested by apt 2.0.8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968154] Re: Only keep 2 kernels
Test passed for apt 2.0.8 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Description changed: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. Workaround: - Unbind "usb" driver from the device manually before suspending. That can be done to work automatically by a special script in /lib/systemd/system-sleep. + Unbind "usb" driver from the device manually before suspending. That can be done to work automatically by a special script in /lib/systemd/system-sleep. Unbinding has the side effect that a new sink is created on resume from suspend. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Description changed: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. + Workaround: + Unbind "usb" driver from the device manually before suspending. That can be done to work automatically by a special script in /lib/systemd/system-sleep. + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: jarnos 1175 F pulseaudio - /dev/snd/controlC0: jarnos 1175 F pulseaudio - /dev/snd/controlC1: jarnos 1175 F pulseaudio - /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: jarnos 1175 F pulseaudio + /dev/snd/controlC0: jarnos 1175 F pulseaudio + /dev/snd/controlC1: jarnos 1175 F pulseaudio + /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: - lono wireless extensions. - - eno1 no wireless extensions. + lono wireless extensions. + + eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.3.0-24-generic N/A - linux-backports-modules-5.3.0-24-generic N/A - linux-firmware1.183.2 + linux-restricted-modules-5.3.0-24-generic N/A + linux-backports-modules-5.3.0-24-generic N/A + linux-firmware1.183.2 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
Still present in 5.13.0-27-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
** Also affects: lightdm Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
** Summary changed: - Nvidia 340 Xorg driver is installed but not loaded after OS upgrade + Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
** Description changed: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. WORKAROUND when using nvidia driver: Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. + + If I use Budgie Desktop instead of Xfce as desktop environment, it will + automatically log out to the LightDM login screen, if I first try to + start that Budgie session and then the HDMI output is used as well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875025] Re: Cannot enter password to unlock session
Please ask in askubuntu.com. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875025 Title: Cannot enter password to unlock session To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-screensaver/+bug/1875025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
Related question: https://askubuntu.com/q/1370465/21005 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
Maybe lightdm could do something differently? What causes HDMI to appear when I log out of session? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
** Description changed: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. + + WORKAROUND when using nvidia driver: + Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
What does the "Report problem..." button in the dialog do, then if I have to use command line to report the crash files? I see "sudo nvidia-xconfig" generates some basic /etc/X11/xorg.conf file. Regardless, I noted the following: If I log out from the Xfce session back to the LightDM greeter the HDMI output is used, too. And if I thereafter log in back to my session, the HDMI output works there, too. I wonder why it does not work right after the first login after boot? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
BTW after every boot I see "System program problem detected?" dialog and every time I choose "Report problem...". I booted today, too. $ LC_ALL=C ls -l /var/crash/ total 4624 -rw-r- 1 jarnos whoopsie 1416740 Oct 14 11:05 _usr_bin_xfce4-power-manager.1000.crash -rw-r- 1 root whoopsie 3314750 Oct 13 16:03 _usr_lib_xorg_Xorg.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
Where can those differences be? I could compare to another machine with the same driver. The graphics card is different, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
Could there be something in upgrading process that caused this that clean install wouldn't have done? Could the relevant parts be clean installed now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
One more thing. I get an error dialog after startup in the desktop. It does not tell what went wrong, but it has an option to report to developers and so I did. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
Hmm. I have another computer that is more successful with nvidia-340 in Xubuntu 20.04. When I compare to Xorg.0.log files, I see differences after line "(II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration". The successful one has "[77.338] (II) xfree86: Adding drm device (/dev/dri/card0) [77.341] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia-340/xorg,/usr/lib/xorg/modules" In the working system there doesn't seem to be a config file: "nvidia-xconfig -t" prints "WARNING: Unable to locate/open X configuration file. Unable to locate/open XConfig file." (with or without run as superuser) so I wonder why this failing one should have? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
I searched for all .conf files in the device for "fbdev" (case insensitive) and found these: /usr/src/linux-headers-5.4.0-84-generic/include/config/auto.conf CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_DRM_FBDEV_EMULATION=y CONFIG_DRM_FBDEV_OVERALLOC=100 /usr/src/linux-headers-5.4.0-84-generic/include/config/tristate.conf CONFIG_XEN_FBDEV_FRONTEND=M /usr/src/linux-headers-5.4.0-88-generic/include/config/auto.conf CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_DRM_FBDEV_EMULATION=y CONFIG_DRM_FBDEV_OVERALLOC=100 /usr/src/linux-headers-5.4.0-88-generic/include/config/tristate.conf CONFIG_XEN_FBDEV_FRONTEND=M -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
There is no string "Default Screen Section" in /usr/share/X11/xorg.conf.d directory. The directory contains files: 10-amdgpu.conf 10-quirks.conf 10-radeon.conf 40-libinput.conf 51-synaptics-quirks.conf 70-synaptics.conf 70-wacom.conf nvidia-drm-outputclass-ubuntu.conf The last one is attached. ** Attachment added: "nvidia-drm-outputclass-ubuntu.conf" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+attachment/5532838/+files/nvidia-drm-outputclass-ubuntu.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
I don't know if it is relevant, but even with Xubuntu 18.04 I had to force pulseaudio sample rate to 44100 to be able to successfully play sound via HDMI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947131] [NEW] HDMI display not recognized
Public bug reported: $ xrandr | grep -i hdmi HDMI-1 disconnected (normal left inverted right x axis y axis) This is even when the monitor is connected. IIRC it has never worked with nouveau, but on the other hand nvidia-340 is unsupported nowadays by Nvidia. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Thu Oct 14 11:55:08 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (889 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947131 Title: HDMI display not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1947131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
** Description changed: - I tried both nouveau and nvidia-340 deivers. It used to work at least by + I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: - $ xrandr + $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm -1920x1200 77.00* + 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 - GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 + GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: - Your system is not currently configured to drive a VGA console - on the primary VGA device. The NVIDIA Linux graphics driver - requires the use of a text-mode VGA console. Use of other console - drivers including, but not limited to, vesafb, may result in - corruption and stability problems, and is not supported. + Your system is not currently configured to drive a VGA console + on the primary VGA device. The NVIDIA Linux graphics driver + requires the use of a text-mode VGA console. Use of other console + drivers including, but not limited to, vesafb, may result in + corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] + NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: - ERROR: Unable to load info from any available system - - - ERROR: Unable to load info from any available system + ERROR: Unable to load info from any available system + + ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to:
[Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
There exists no /etc/X11/xorg.conf file. I already switched to nouveau using "Software & Updates" rebooted, switched back to nvidia-340 by the same application, and rebooted, but it did not help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946987] [NEW] HDMI not recognized after upgrading from 18.04 to 20.04.3
Public bug reported: I tried both nouveau and nvidia-340 deivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: HDMI not recognized after upgrading from 18.04 to 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1946987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872391] Re: underscore not shown in geany editor window
The bug is in Scintilla widget: https://github.com/geany/geany/issues/2502#issuecomment-939463462 Sadly, Ubuntu has an old version of it. ** Bug watch added: github.com/geany/geany/issues #2502 https://github.com/geany/geany/issues/2502 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872391 Title: underscore not shown in geany editor window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1872391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920974] Re: Underscore is not visible in the feed with certain settings
The package available in the PPA fixed the issue. ** Description changed: [Impact] - * Using monospace fonts, some parts of the glyphs might not be visible -(this is especially evident using some monospsace fonts, there the -underscore is not visible). + * Using monospace fonts, some parts of the glyphs might not be visible + (this is especially evident using some monospsace fonts, there the + underscore is not visible). - * This came due to a change in behaviour in Pango 1.44. - * The fix makes use of a newer API for Pango>=1.44 that address this -issue. + * This came due to a change in behaviour in Pango 1.44. + * The fix makes use of a newer API for Pango>=1.44 that address this + issue. [Test Plan] + Select Monospace 9 font in appearance settings of hexchat. + Write something containing '_' in an irc channel. + Check, if the '_' is visible in the feed. [Where problems could occur] - * Messing this patch up means text wouldn't appear in the textbox -anymore. so… - + * Messing this patch up means text wouldn't appear in the textbox + anymore. so… [Other Info] - - * None here. + * None here. [ Original report ] If I have Monospace 9 (default?) as the font in HexChat settings I can not see underscore character '_' in the feed, but if I set it Monospace 10 and set Custom DPI setting in Xfce's Appearance dialog to 94 or smaller, I see the character. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hexchat 2.14.3-3 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Mar 23 18:52:59 2021 InstallationDate: Installed on 2020-05-03 (324 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 SourcePackage: hexchat UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920974 Title: Underscore is not visible in the feed with certain settings To manage notifications about this bug go to: https://bugs.launchpad.net/hexchat-irc/+bug/1920974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Actually this bug report is not about updates stopping working. This is about not being able to remove a kernel with related packages completely by usual ways due to a specific reason, if /boot becomes full enough. There are other bug reports that call for bigger /boot partition or an automatic way of removing unused kernels. You are welcome. Feel free to donate at https://launchpad.net/linux- purge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942703] Re: Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around
** Bug watch added: github.com/mvo5/unattended-upgrades/issues #302 https://github.com/mvo5/unattended-upgrades/issues/302 ** Also affects: unattended-upgrades via https://github.com/mvo5/unattended-upgrades/issues/302 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942703 Title: Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1942703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942703] [NEW] Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around
Public bug reported: If user has linux-generic-hwe-18.04 installed, versioned linux-headers packages depend on versioned linux-hwe-5.4-headers packages that will not get removed. Consequently in time there will be hundreds of thousands of unused files under /usr/src. For example I have about 45 totalling 1.4 GB. The number of inodes may be bigger issue, because file systems have some limitations. I noted the issue when using my linux-purge tool. It is supposed to be able to remove kernels, even if the file system runs out of inodes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.14 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic i686 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: i386 Date: Sun Sep 5 14:38:49 2021 InstallationDate: Installed on 2016-09-05 (1826 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to bionic on 2019-04-06 (882 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-03-26T11:42:30.041160 ** Affects: unattended-upgrades Importance: Unknown Status: Unknown ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942703 Title: Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1942703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922562] Re: Resume from suspend to RAM fails
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Worked with nvidia-340 driver which is no more updated. - When I resume, nothing works. Macbook keyboard lights are on, but - otherwise the machine seems dead. Power button reboot needed. + When I resume, nothing works. Macbook keyboard lights are on, but I get + no response from the machine. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 and xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 and Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922562 Title: Resume from suspend to RAM fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922562] Re: Resume from suspend to RAM fails
Same thing in focal. I also tried 5.13.0-1010-oem kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922562 Title: Resume from suspend to RAM fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1922562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Please check out https://help.ubuntu.com/community/ReportingBugs#Filing_a_general_bug_against_no_particular_package (and the document in general). Please tell me the URL of the report thereafter. You told in #23 that you "Just ran in to this on Ubuntu 20.04", but to be precise it is not even possible, as Ubuntu 20.04 does not have linux- image-extra packages. Do linux-modules packages have some similar effect? Did you even try to remove a kernel by dpkg without running "update-initramfs -d"? Or did you even try removing a kernel by apt before that? It would be helpful if you provided the output of such commands that fail. You also told "The /boot partition is 732Mb, but is filled with initrd.img* files." Still there were no more of those than e.g. vmlinuz-* files in the listings you gave. I have contributed to https://help.ubuntu.com/community/RemoveOldKernels, authored the linux- purge tool, made this bug report and provided the patch. Please follow some accuracy and relevancy in comments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Well, you could search for support in askubuntu.com. I think it may be a bug that you have two flavors of kernels installed, if you did not install the other manually. You might need to make a separate bug report about that; removing the other flavor might be a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Hayden, did you try? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Remove the older generic kernel by linux-purge and then try booting the respective oem kernel via advanced grub menu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Oh, the versions do not match. I do not see how removing the hwe kernels would make it unbootable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922562] Re: Resume from suspend to RAM fails
** Also affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags added: focal ** Description changed: Worked with nvidia-340 driver which is no more updated. When I resume, nothing works. Macbook keyboard lights are on, but otherwise the machine seems dead. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 + and xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Worked with nvidia-340 driver which is no more updated. When I resume, nothing works. Macbook keyboard lights are on, but otherwise the machine seems dead. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 and xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 - Uname: Linux 5.4.0-70-generic x86_64 + Uname: Linux 5.4.0-70-generic x86_64 and Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922562 Title: Resume from suspend to RAM fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1922562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Hayden Clark, so you use "oem" kernels. If you do not need "generic" kernels, you can save a lot of space in /boot by deleting all "generic" kernels. Probably the easiest way to do it in your case is "sudo apt autoremove linux-generic-hwe-20.04". Check that it does not remove any "oem" kernels. If that does not work, you can use "sudo linux-purge --choose --optimize" and choose all "generic" kernels for purging. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
I created the custom default.pa. It adds only two commands when compared to default /etc/pulse/default.pa: load-module module-native-protocol-tcp auth-ip-acl=192.168.100.51 set-card-profile alsa_card.pci-_00_1b.0 input:analog-stereo The first one I need for network access of pulseaudio from a separate server (https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Network/#authorization) and the second one sets up the profile for the integrated alsa_card.pci-_00_1b.0 to use it only for input. I use an USB device for output. Pulseaudio should be able to handle these. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
** Attachment removed: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513625/+files/default.pa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached?field.comment=From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached ** Attachment added: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513625/+files/default.pa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached?field.comment=From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached ** Attachment added: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513624/+files/default.pa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
** Description changed: - First pulseaudio fails for some reason. + First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the + volume control in Xfce panel shows mute after I start session, but I can + not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Could you attach output of "linux-purge --info"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Did you run "sudo linux-purge --keep=1"? (or replace "1" by "0" to purge even more) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513397/+files/syslog ** Description changed: - This is not always reproduceable. + First pulseaudio fails for some reason. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937919] [NEW] Fails to start pulseaudio (No card found by this name or index.)
Public bug reported: This is not always reproduceable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934757] Re: Pulseaudio does not recognize integrated audio device
** Description changed: + I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-stereo" + in "~/.config/pulse/default.pa". It caused pulseaudio to fail with this + version. I removed the line and run pulseaudio. + Unrecognized device: Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) - EDIT: oh, it works again. I'll keep track of this issue. + EDIT: oh, it works again. I'll keep track of this issue. Maybe I should + have started pulseaudio by systemd? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jul 6 12:16:50 2021 InstallationDate: Installed on 2019-12-05 (578 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934757 Title: Pulseaudio does not recognize integrated audio device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934757] Re: Pulseaudio does not recognize integrated audio device
** Description changed: Unrecognized device: Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) + + EDIT: oh, it works again. I'll keep track of this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jul 6 12:16:50 2021 InstallationDate: Installed on 2019-12-05 (578 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934757 Title: Pulseaudio does not recognize integrated audio device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934757] [NEW] Pulseaudio does not recognize integrated audio device
Public bug reported: Unrecognized device: Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jul 6 12:16:50 2021 InstallationDate: Installed on 2019-12-05 (578 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934757 Title: Pulseaudio does not recognize integrated audio device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Did you upgrade from older release or are the files generated when you were using 20.04? Can you provide any logs concerning the issue? Do the extra initrd.img* files match /boot/initrd.img-*.old-dkms, see https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513 ? Or do you still have the respective kernels (vmlinuz-* etc.) there, too? It seems that my modified generate_initramfs function has not been applied in /usr/sbin/update-initramfs in 20.04, so you can not remove a kernel successfully. The modified version should do better job not leaving extra files around IIRC. Anyway, it should be possible with my linux-purge utility (https://launchpad.net/linux-purge). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920974] Re: Underscore is not visible in the feed with certain settings
** Bug watch added: github.com/hexchat/hexchat/issues #2449 https://github.com/hexchat/hexchat/issues/2449 ** Also affects: hexchat-irc via https://github.com/hexchat/hexchat/issues/2449 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920974 Title: Underscore is not visible in the feed with certain settings To manage notifications about this bug go to: https://bugs.launchpad.net/hexchat-irc/+bug/1920974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022858] Re: Guest session asks for a password after switching users
You do not need to switch from guest session to do those nowadays: https://help.ubuntu.com/community/CustomizeGuestSession -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022858 Title: Guest session asks for a password after switching users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775088] Re: Ubuntu Mate guest session locked out when switching from another account
*** This bug is a duplicate of bug 1022858 *** https://bugs.launchpad.net/bugs/1022858 ** This bug has been marked a duplicate of bug 1022858 Guest session asks for a password after switching users -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775088 Title: Ubuntu Mate guest session locked out when switching from another account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1775088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022858] Re: Guest session asks for a password after switching users
Does one need to switch from guest session? Maybe it should be disabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022858 Title: Guest session asks for a password after switching users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt-cache show' is slow
** Description changed:
$ time apt-mark showauto >/dev/null
real 0m0,620s
user 0m0,557s
sys 0m0,052s
When I run the command first time, it is even much slower.
- I could do the job* in fraction of a time using awk in POSIX shell script
- (name it ./apt-mark-showauto.sh):
+ I could do the job* in fraction of a time using an AWK script
+ (name it ./apt-mark-showauto.awk):
- #!/bin/sh
- auto_file='/var/lib/apt/extended_states'
- awk '/^Package:/ {
- pkg=$2
- while (getline > 0 && $0) {
- if ($1 == "Auto-Installed:") {
- if ($2==1) print pkg
- break
- }
+ #!/usr/bin/awk -f
+ BEGIN{
+ file="/var/lib/apt/extended_states"
+ while ((getline < file) > 0) {
+ if ($0 ~ /^Package:/) {
+ pkg=$2
+ while ((getline < file) > 0 && $0) {
+ if ($1 == "Auto-Installed:") {
+ if ($2==1) print pkg
+ break
+ }
+ }
+ }
}
- }' "$auto_file"
+ }
- $ time ./apt-mark-showauto.sh >/dev/null
+ $ time ./apt-mark-showauto.awk >/dev/null
- real 0m0,005s
- user 0m0,002s
- sys 0m0,004s
+ real 0m0,004s
+ user 0m0,004s
+ sys 0m0,000s
- Tested in Ubuntu 20.04.
+ Tested in Ubuntu 20.04 and mawk 1.3.4 as AWK interpreter.
*) The script omits Architecture information, though. And should apt-
config be queried for the extended_states file path?
Similarly
apt-cache show
is slow. (It also shows whether a package is manually or automatically
installed.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.17
ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Aug 26 12:59:00 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-21 (1070 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.cron.daily.apt: [modified]
modified.conffile..etc.kernel.postinst.d.apt.auto.removal: [modified]
mtime.conffile..etc.cron.daily.apt: 2017-05-03T10:27:27.617839
mtime.conffile..etc.kernel.postinst.d.apt.auto.removal:
2017-06-01T14:39:39.236080
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713219
Title:
'apt-mark showauto' and 'apt-cache show' is slow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922562] [NEW] Resume from suspend to RAM fails
Public bug reported: Worked with nvidia-340 driver which is no more updated. When I resume, nothing works. Macbook keyboard lights are on, but otherwise the machine seems dead. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922562 Title: Resume from suspend to RAM fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau-hwe-18.04/+bug/1922562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions
@Sushenjit did you file a bug report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481804 Title: LightDM's guest-account script should disable screen lock universally for guest sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1481804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693900] Re: apt-get update should return exit code != 0 on error
I tried the apt provided by focal-proposed. At least sudo apt-get update -eany gave exit status 100, if I disabled networking. Without -eany it gave 0. I got the source code by 'apt source'. I could not run test-apt-update-failure-propagation: $ sudo ./apt-2.0.5/test/integration/test-apt-update-failure-propagation Cannot find build directory, you might want to set PROJECT_BINARY_DIR E: Looks like the testcases ended prematurely with exitcode: 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693900 Title: apt-get update should return exit code != 0 on error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt-cache show' is slow
** Description changed:
$ time apt-mark showauto >/dev/null
- real 0m0.587s
- user 0m0.552s
- sys 0m0.016s
+ real 0m0,620s
+ user 0m0,557s
+ sys 0m0,052s
When I run the command first time, it is even much slower.
- I could do the job in fraction of a time using awk in POSIX shell
- script:
+ I could do the job* in fraction of a time using awk in POSIX shell script
+ (name it ./apt-mark-showauto.sh):
+ #!/bin/sh
auto_file='/var/lib/apt/extended_states'
- eval $(apt-config shell auto_file Dir::State::extended_states/f)
awk '/^Package:/ {
pkg=$2
- getline; arch=$2
- getline
- if($2==1) print pkg ":" arch
- }' "$auto_file" | CL_ALL=C sort -u
+ while (getline > 0 && $0) {
+ if ($1 == "Auto-Installed:") {
+ if ($2==1) print pkg
+ break
+ }
+ }
+ }' "$auto_file"
- real 0m0.019s
- user 0m0.008s
- sys 0m0.000s
+ $ time ./apt-mark-showauto.sh >/dev/null
- That prints architecture for every package and shows entries in slightly
- different order, though. And the file could be out of date showing
- packages that are not installed?!?
+ real 0m0,005s
+ user 0m0,002s
+ sys 0m0,004s
+
+ Tested in Ubuntu 20.04.
+
+ *) The script omits Architecture information, though. And should apt-
+ config be queried for the extended_states file path?
Similarly
- apt show
+ apt-cache show
is slow. (It also shows whether a package is manually or automatically
installed.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.17
ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Aug 26 12:59:00 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-21 (1070 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.cron.daily.apt: [modified]
modified.conffile..etc.kernel.postinst.d.apt.auto.removal: [modified]
mtime.conffile..etc.cron.daily.apt: 2017-05-03T10:27:27.617839
mtime.conffile..etc.kernel.postinst.d.apt.auto.removal:
2017-06-01T14:39:39.236080
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713219
Title:
'apt-mark showauto' and 'apt-cache show' is slow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
Good, besides simple text file format is easy to parse and check by command line tools, if needed. To my surprise, I have more manually installed packages than automatically installed ones, so listing manually installed instead of automatically installed in the file would not give benefit. 'apt-mark showauto' and 'apt-mark showmanual' are simple filters that do not need any information about dependencies. /var/lib/dpkg/status lists dependencies shown by 'apt-cache show' ** Summary changed: - 'apt-mark showauto' and 'apt show' is slow + 'apt-mark showauto' and 'apt-cache show' is slow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713219 Title: 'apt-mark showauto' and 'apt-cache show' is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
Well, Boolean algebra may have had some influence on that. It is a common practice. 1 is shorter than yes. Oh that is sad, because I am not satisfied with the speed of apt-mark. On the other hand it is good. Another format or data structure may be more efficient. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713219 Title: 'apt-mark showauto' and 'apt show' is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920974] [NEW] Underscore is not visible in the feed with certain settings
Public bug reported: If I have Monospace 9 (default?) as the font in HexChat settings I can not see underscore character '_' in the feed, but if I set it Monospace 10 and set Custom DPI setting in Xfce's Appearance dialog to 94 or smaller, I see the character. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hexchat 2.14.3-3 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Mar 23 18:52:59 2021 InstallationDate: Installed on 2020-05-03 (324 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 SourcePackage: hexchat UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: hexchat (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920974 Title: Underscore is not visible in the feed with certain settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hexchat/+bug/1920974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
Oh, currently missing Auto-Installed field seems to mean the package is manually installed even if the Package field exists. I suppose I can rely on that in the future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713219 Title: 'apt-mark showauto' and 'apt show' is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
Julian, BTW can you tell which version of apt was the latest where value of the Auto-Installed field can be something else than 1 in the file? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713219 Title: 'apt-mark showauto' and 'apt show' is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
Oh, actually I was already using set substraction in my code, but I was also checking for 'Auto-Installed: 0'. Maybe that is necessary with some older version of apt? (There was some bug in my code and that is why it did not work correctly for some packages.) Sorry for blaming and confusing. However, I will change my code just in case you decide to remove the pointless Auto-Installed fields from the file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713219 Title: 'apt-mark showauto' and 'apt show' is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
Well, the script in the description is a bit too simple. In my application, I was looking for 'Auto-Installed:' field with value 0 to find manually installed packages, and due to the change in the way the file is build nowadays I do not find them by the code anymore. Now the field is pointless. I suppose now I could find the packages by set substraction, if I want to optimize my code. "time apt-mark showauto >/dev/null" is slow no matter when I run it. It is about the same if you run it for any single package. Do you call those a borderline cases? It might not be slow by latest and greatest supercomputers though, but I make code for slower hardware, too, and try to strive for reasonable responsiveness in my applications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713219 Title: 'apt-mark showauto' and 'apt show' is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
I wonder why didn't you choose to have only manually installed packages in the file? It would be even smaller file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713219 Title: 'apt-mark showauto' and 'apt show' is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
So the file should only list packages that are installed automatically or what? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713219 Title: 'apt-mark showauto' and 'apt show' is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
Maybe so, but the fact is that the file does not contain information about all packages installed to my system. (apt 2.0.4 (amd64) / Ubuntu 20.04) $ grep -c '^Package:' /var/lib/apt/extended_states 698 $ dpkg -l | grep ^ii | wc -l 1893 My file contains only records for packages that are automatically installed for some reason. (All records have "Auto-Installed: 1") apt-mark showmanual works anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713219 Title: 'apt-mark showauto' and 'apt show' is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
Maybe I should make another bug report about it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713219 Title: 'apt-mark showauto' and 'apt show' is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
I just found out information about packages installed from PPAs are not found in file configured in Dir::State::extended_states, so my script does not work for them. Are they found in some other file then? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713219 Title: 'apt-mark showauto' and 'apt show' is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190696] Re: updatedb.mlocate uses 100% of the hdd IO. The OS is completely unusable.
mlocate does not seem to be included in Ubuntu 20.04 by default, but is included in Xubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190696 Title: updatedb.mlocate uses 100% of the hdd IO. The OS is completely unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1190696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919361] [NEW] Remove super+digit shortcuts
Public bug reported: There are applications bind to super+digit shortcuts in xfce4-keyboard- settings. E.g. Super+2 = pidgin. There shortcuts seem random and user may have better use for such shortcuts so better leave them alone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xfce4-settings 4.14.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Mar 16 20:44:41 2021 InstallationDate: Installed on 2019-12-05 (467 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: xfce4-settings UpgradeStatus: Upgraded to focal on 2020-07-10 (249 days ago) ** Affects: xfce4-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919361 Title: Remove super+digit shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1919361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858027] Re: xscreensaver-command -lock finishes before desktop is invisible
** Changed in: xscreensaver (Ubuntu) Status: New => Opinion ** Description changed: + EDIT: Now if it is generally so that when you lock by xscreensaver + before suspending, suspending happens only after fading has completed, I + withdraw this bug report. + Steps to reproduce 1. Run 'xscreensaver-demo -prefs', activate the daemon, if requested 2. Ensure that "Fade to Black when Blanking" is set up with some non-zero duration. 3. in terminal, run xscreensaver-command -lock /dev/null && paplay /usr/share/sounds/freedesktop/stereo/bell.oga ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xscreensaver 5.42+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 1 15:36:35 2020 InstallationDate: Installed on 2019-12-05 (26 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858027 Title: xscreensaver-command -lock finishes before desktop is invisible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1858027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858027] Re: xscreensaver-command -lock finishes before desktop is invisible
Despite the fact that 'xscreensaver-command -lock' may exit before it has faded screen out in 'xscreensaver-command -lock https://bugs.launchpad.net/bugs/1858027 Title: xscreensaver-command -lock finishes before desktop is invisible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1858027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858027] Re: xscreensaver-command -lock finishes before desktop is invisible
** Description changed: Steps to reproduce 1. Run 'xscreensaver-demo -prefs', activate the daemon, if requested 2. Ensure that "Fade to Black when Blanking" is set up with some non-zero duration. 3. in terminal, run xscreensaver-command -lock /dev/null && paplay /usr/share/sounds/freedesktop/stereo/bell.oga + I found a workaround that seem to work at least in Xubuntu 20.04: + In step 3, run + xscreensaver-command -lock /dev/null && paplay + /usr/share/sounds/freedesktop/stereo/bell.oga + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xscreensaver 5.42+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 1 15:36:35 2020 InstallationDate: Installed on 2019-12-05 (26 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Steps to reproduce 1. Run 'xscreensaver-demo -prefs', activate the daemon, if requested 2. Ensure that "Fade to Black when Blanking" is set up with some non-zero duration. 3. in terminal, run xscreensaver-command -lock /dev/null && paplay /usr/share/sounds/freedesktop/stereo/bell.oga - ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xscreensaver 5.42+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 1 15:36:35 2020 InstallationDate: Installed on 2019-12-05 (26 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858027 Title: xscreensaver-command -lock finishes before desktop is invisible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1858027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858027] Re: xscreensaver-command -lock finishes before desktop is invisible
** Description changed: Steps to reproduce 1. Run 'xscreensaver-demo -prefs', activate the daemon, if requested 2. Ensure that "Fade to Black when Blanking" is set up with some non-zero duration. 3. in terminal, run xscreensaver-command -lock /dev/null && paplay /usr/share/sounds/freedesktop/stereo/bell.oga ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xscreensaver 5.42+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 1 15:36:35 2020 InstallationDate: Installed on 2019-12-05 (26 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858027 Title: xscreensaver-command -lock finishes before desktop is invisible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1858027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917265] Re: Suspending to RAM freezes computer
Well after some kernel update it may be that Nvidia driver does not work anymore so I would have to use nouveau or another card.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917265 Title: Suspending to RAM freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917265] Re: Suspending to RAM freezes computer
I switched to nvidia-340 driver (via "Additional Drivers"), rebooted and tested few times that suspend-resume works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917265 Title: Suspending to RAM freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917265] Re: Suspending to RAM freezes computer
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+attachment/5471858/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917265 Title: Suspending to RAM freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917265] Re: Suspending to RAM freezes computer
I have been using this computer only occasionally. It seems that with 5.4.0-65-generic and later I have had this problem more frequently, but I had this bug problem few times in May 2020, too (or at least I did not resume from suspend), but I had several successful resumes after that (according to journalctl). I wonder, if this could be related to graphics driver? I have been using nouveau instead of nvidia lately. nvidia-340 is no more developed IIRC. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917265 Title: Suspending to RAM freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917265] Re: Suspending to RAM freezes computer
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+attachment/5471857/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917265 Title: Suspending to RAM freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917265] Re: Suspending to RAM freezes computer
I tried a couple of times. It does not work no matter which mode I use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917265 Title: Suspending to RAM freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917265] Re: Suspending to RAM freezes computer
According to above, exiting suspend has failed only in deep mode, but I wonder why there is one s2idle mode. Maybe later I rub some tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917265 Title: Suspending to RAM freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917265] Re: Suspending to RAM freezes computer
Hi Guilherme, I have mixed result: $ LC_ALL=C sudo journalctl | grep "PM: suspend" | tail -n 17 Sep 22 11:19:52 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Sep 22 11:20:14 jarnos-OptiPlex-745 kernel: PM: suspend exit Sep 22 11:20:14 jarnos-OptiPlex-745 kernel: PM: suspend entry (s2idle) Sep 22 11:20:36 jarnos-OptiPlex-745 kernel: PM: suspend exit Sep 22 11:21:26 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Sep 22 11:30:00 jarnos-OptiPlex-745 kernel: PM: suspend exit Dec 04 15:53:23 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Dec 04 17:50:48 jarnos-OptiPlex-745 kernel: PM: suspend exit Dec 04 18:40:19 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Dec 04 18:50:02 jarnos-OptiPlex-745 kernel: PM: suspend exit Dec 04 19:35:56 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Dec 05 01:07:52 jarnos-OptiPlex-745 kernel: PM: suspend exit Feb 14 14:52:33 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Feb 20 22:59:47 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Feb 21 14:21:38 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) Feb 21 18:43:59 jarnos-OptiPlex-745 kernel: PM: suspend exit Feb 28 23:32:29 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917265 Title: Suspending to RAM freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917265] [NEW] Suspending to RAM freezes computer
Public bug reported: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917265 Title: Suspending to RAM freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913869] Re: Invalid regular expressions describing Debian package file naming convention
BTW it is confusing that uppercase letters are allowed for package name in .deb filename, but not in the package name itself: https://www.debian.org/doc/debian-policy/ch-controlfields.html#source -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913869 Title: Invalid regular expressions describing Debian package file naming convention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-reference/+bug/1913869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913869] [NEW] Invalid regular expressions describing Debian package file naming convention
Public bug reported: In chapter 2.5.8. table Table 2.16 there must not be commas in the regular expressions unless comma is a valid character in that name component. Besides if '-' is valid, it should be the last one enumerated; otherwise it is a metacharacter. Also be more specific that these are POSIX Extended Regular Expressions. The bug occurs probably in all language versions, but I provide a patch for the English one. Same valid characters apply in Ubuntu package naming, too, right? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: debian-reference (not installed) ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jan 30 12:11:42 2021 InstallationDate: Installed on 2019-12-05 (421 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: debian-reference UpgradeStatus: Upgraded to focal on 2020-07-10 (203 days ago) ** Affects: debian-reference (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Patch added: "patch for ch02.en.html" https://bugs.launchpad.net/bugs/1913869/+attachment/5458256/+files/fix.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913869 Title: Invalid regular expressions describing Debian package file naming convention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-reference/+bug/1913869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
Oh, do I have to make a different bug report or address this one to another package (which one)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713242] Re: Feature request: option to disable tag shortcut keys and respective first letter coloring in checklist/menu
Could you be more specific about where to discuss this in Debian? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713242 Title: Feature request: option to disable tag shortcut keys and respective first letter coloring in checklist/menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1713242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713242] Re: Feature request: option to disable tag shortcut keys and respective first letter coloring in checklist/menu
Oh, but user is not guided to use debian for bug reporting beforehand, but to use launchpad.net: $ apt-cache show dialog | grep -i bugs Bugs: https://bugs.launchpad.net/ubuntu/+filebug and $ man dialog | grep -A 2 -i bugs BUGS Perhaps. Besides, the issue is present in version 1.3-20190808 (focal). ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713242 Title: Feature request: option to disable tag shortcut keys and respective first letter coloring in checklist/menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1713242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
Booting mainline kernel did not help. Then I added the kernel parameters for it. ** Attachment added: "journal-5.11.0-051100rc4-generic.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+attachment/5456252/+files/journal-5.11.0-051100rc4-generic.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Attachment added: "journalctl -b -1 -k on focal" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+attachment/5453567/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906154] [NEW] xsel does not exit
Public bug reported: Examples: echo foo | xsel -i cat bar | xsel -i xsel process does not terminate, but is in interruptible sleep. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xsel 1.2.0+git9bfc13d.20180109-3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Nov 29 13:10:15 2020 InstallationDate: Installed on 2019-12-05 (359 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: xsel UpgradeStatus: Upgraded to focal on 2020-07-10 (142 days ago) ** Affects: xsel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906154 Title: xsel does not exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xsel/+bug/1906154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643706] Re: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs
Patrick Dinklage, as your employer advises to use /scratch, I suppose your IT administrator could configure the snap apps and mounts so that you could use the local filesystem via a directory under /mnt by applying these instructions: https://askubuntu.com/a/1286929/21005 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643706 Title: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893432] [NEW] Does not display packages that can be updated
Public bug reported: Still the dialog shows that some data will be downloaded, see the attached image. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: update-manager 1:20.04.10.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Aug 28 16:09:36 2020 DpkgHistoryLog.txt: Start-Date: 2020-08-28 16:08:57 Commandline: apt install google-chrome-stable Requested-By: jarnos (1000) Upgrade: google-chrome-stable:amd64 (83.0.4103.116-1, 85.0.4183.83-1) End-Date: 2020-08-28 16:09:11 InstallationDate: Installed on 2020-05-03 (117 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot_2020-08-28_16-07-28.png" https://bugs.launchpad.net/bugs/1893432/+attachment/5405432/+files/Screenshot_2020-08-28_16-07-28.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893432 Title: Does not display packages that can be updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1893432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
