[Touch-packages] [Bug 1895370] Re: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit
I got these lib already installed root@work ~ [0|1]# dpkg -l|grep libiptc ii libiptc-dev:amd64 1.8.4-3ubuntu2 amd64Common development files for libiptc ii libiptc0:amd64 1.8.4-3ubuntu2 amd64transitional dummy package ii libiptcdata-bin1.0.5-2.1ubuntu4 amd64Library to parse IPTC metadata (programs) ii libiptcdata0 1.0.5-2.1ubuntu4 amd64Library to parse IPTC metadata root@work ~# but problems is still. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1895370 Title: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit Status in systemd package in Ubuntu: New Bug description: Last run apt update and apt upgrade and reboot render my system unbootable because systemd failed with message: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit So I tried to reset to the previous state and re-run the update and after the re-run update I try to run the systemd command and having the same result. root@work ~# apt update; apt upgrade Get:1 http://au.archive.ubuntu.com/ubuntu focal InRelease [265 kB] Get:2 http://au.archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB] Get:3 http://au.archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Get:4 http://ppa.launchpad.net/audio-recorder/ppa/ubuntu focal InRelease [15.9 kB] Get:5 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB] Get:6 http://dl.google.com/linux/chrome/deb stable InRelease [1,811 B] Get:7 http://au.archive.ubuntu.com/ubuntu focal/main amd64 Packages [970 kB] Get:9 http://au.archive.ubuntu.com/ubuntu focal/main i386 Packages [718 kB] Get:10 http://au.archive.ubuntu.com/ubuntu focal/main Translation-en_AU [1,836 B] Get:11 http://au.archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB] Get:12 https://packages.microsoft.com/repos/ms-teams stable InRelease [17.5 kB] Get:13 http://au.archive.ubuntu.com/ubuntu focal/main amd64 DEP-11 Metadata [494 kB] Get:14 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 48x48 Icons [98.4 kB] Get:15 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 64x64 Icons [163 kB] Get:16 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 64x64@2 Icons [15.8 kB] Get:17 https://packages.microsoft.com/repos/ms-teams stable/main amd64 Packages [6,403 B] Get:18 http://au.archive.ubuntu.com/ubuntu focal/main amd64 c-n-f Metadata [29.5 kB] Get:19 http://au.archive.ubuntu.com/ubuntu focal/restricted i386 Packages [8,112 B] Ign:20 http://ppa.launchpad.net/hermlnx/dislocker/ubuntu focal InRelease Get:21 http://au.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [22.0 kB] Get:22 http://au.archive.ubuntu.com/ubuntu focal/restricted Translation-en_AU [1,144 B] Get:23 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1,163 B] Get:24 http://au.archive.ubuntu.com/ubuntu focal/restricted Translation-en [6,212 B] Get:25 http://au.archive.ubuntu.com/ubuntu focal/restricted
[Touch-packages] [Bug 1895370] [NEW] systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit
Public bug reported: Last run apt update and apt upgrade and reboot render my system unbootable because systemd failed with message: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit So I tried to reset to the previous state and re-run the update and after the re-run update I try to run the systemd command and having the same result. root@work ~# apt update; apt upgrade Get:1 http://au.archive.ubuntu.com/ubuntu focal InRelease [265 kB] Get:2 http://au.archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB] Get:3 http://au.archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Get:4 http://ppa.launchpad.net/audio-recorder/ppa/ubuntu focal InRelease [15.9 kB] Get:5 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB] Get:6 http://dl.google.com/linux/chrome/deb stable InRelease [1,811 B] Get:7 http://au.archive.ubuntu.com/ubuntu focal/main amd64 Packages [970 kB] Get:9 http://au.archive.ubuntu.com/ubuntu focal/main i386 Packages [718 kB] Get:10 http://au.archive.ubuntu.com/ubuntu focal/main Translation-en_AU [1,836 B] Get:11 http://au.archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB] Get:12 https://packages.microsoft.com/repos/ms-teams stable InRelease [17.5 kB] Get:13 http://au.archive.ubuntu.com/ubuntu focal/main amd64 DEP-11 Metadata [494 kB] Get:14 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 48x48 Icons [98.4 kB] Get:15 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 64x64 Icons [163 kB] Get:16 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 64x64@2 Icons [15.8 kB] Get:17 https://packages.microsoft.com/repos/ms-teams stable/main amd64 Packages [6,403 B] Get:18 http://au.archive.ubuntu.com/ubuntu focal/main amd64 c-n-f Metadata [29.5 kB] Get:19 http://au.archive.ubuntu.com/ubuntu focal/restricted i386 Packages [8,112 B] Ign:20 http://ppa.launchpad.net/hermlnx/dislocker/ubuntu focal InRelease Get:21 http://au.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [22.0 kB] Get:22 http://au.archive.ubuntu.com/ubuntu focal/restricted Translation-en_AU [1,144 B] Get:23 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1,163 B] Get:24 http://au.archive.ubuntu.com/ubuntu focal/restricted Translation-en [6,212 B] Get:25 http://au.archive.ubuntu.com/ubuntu focal/restricted amd64 c-n-f Metadata [392 B] Get:26 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages [8,628 kB] Get:8 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease [23.5 kB] Get:27 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages [69.9 kB] Get:28 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu focal InRelease [17.5 kB] Err:29 http://ppa.launchpad.net/hermlnx/dislocker/ubuntu focal Release 404 Not Found [IP: 91.189.95.83 80] Get:30 http://au.archive.ubuntu.com/ubuntu focal/universe i386 Packages [4,642 kB] Get:31 http://security.ubuntu.com/ubuntu focal-security/main amd64
[Touch-packages] [Bug 1895360] Re: Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 in 20.10
Oh, thanks for pointing that out. It's not exactly clear to me how this situation arose, but I'm glad it's just a me problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1895360 Title: Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 in 20.10 Status in libffi package in Ubuntu: Invalid Bug description: When I launch Terminal, I see the following error (st and urxvt are still launchable, as are Discord and Spotify, among others): Sep 11 18:22:39 arctic systemd[1918]: Started Application launched by gnome-shell. Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[18808]: Traceback (most recent call last): Sep 11 18:22:39 arctic gnome-shell[18808]: File "/usr/bin/gnome-terminal", line 9, in Sep 11 18:22:39 arctic gnome-shell[18808]: from gi.repository import GLib, Gio Sep 11 18:22:39 arctic gnome-shell[18808]: File "/home/alichtman/.local/lib/python3.8/site-packages/gi/__init__.py", line 42, in Sep 11 18:22:39 arctic gnome-shell[18808]: from . import _gi Sep 11 18:22:39 arctic gnome-shell[18808]: ImportError: libffi.so.7: cannot open shared object file: No such file or directory And then Terminal never launches. libffi.so.8 is found in /usr/lib/x86_64-linux-gnu/, but libffi.so.7 is missing. $ lsb_release -rd Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1895360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895360] Re: Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 in 20.10
> /home/alichtman/.local/lib/python3.8/site-packages/gi/__init__.py This is not a bug in libffi. You have a local gi python module on your path which depends on library versions other than those which are current in 20.10. It is inadvisable to put modules on your default python path that shadow system modules. ** Changed in: libffi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1895360 Title: Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 in 20.10 Status in libffi package in Ubuntu: Invalid Bug description: When I launch Terminal, I see the following error (st and urxvt are still launchable, as are Discord and Spotify, among others): Sep 11 18:22:39 arctic systemd[1918]: Started Application launched by gnome-shell. Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[18808]: Traceback (most recent call last): Sep 11 18:22:39 arctic gnome-shell[18808]: File "/usr/bin/gnome-terminal", line 9, in Sep 11 18:22:39 arctic gnome-shell[18808]: from gi.repository import GLib, Gio Sep 11 18:22:39 arctic gnome-shell[18808]: File "/home/alichtman/.local/lib/python3.8/site-packages/gi/__init__.py", line 42, in Sep 11 18:22:39 arctic gnome-shell[18808]: from . import _gi Sep 11 18:22:39 arctic gnome-shell[18808]: ImportError: libffi.so.7: cannot open shared object file: No such file or directory And then Terminal never launches. libffi.so.8 is found in /usr/lib/x86_64-linux-gnu/, but libffi.so.7 is missing. $ lsb_release -rd Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1895360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895360] Re: Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7
Fixed by: $ wget https://launchpad.net/ubuntu/+source/libffi/3.3-4/+build/18885702/+files/libffi7_3.3-4_amd64.debwget $ sudo dpkg -i libffi7_3.3-4_amd64.deb Thanks to TJ- and sarnold in the Ubuntu freenode server for the help. ** Summary changed: - Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 + Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 in 20.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1895360 Title: Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 in 20.10 Status in libffi package in Ubuntu: New Bug description: When I launch Terminal, I see the following error (st and urxvt are still launchable, as are Discord and Spotify, among others): Sep 11 18:22:39 arctic systemd[1918]: Started Application launched by gnome-shell. Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[18808]: Traceback (most recent call last): Sep 11 18:22:39 arctic gnome-shell[18808]: File "/usr/bin/gnome-terminal", line 9, in Sep 11 18:22:39 arctic gnome-shell[18808]: from gi.repository import GLib, Gio Sep 11 18:22:39 arctic gnome-shell[18808]: File "/home/alichtman/.local/lib/python3.8/site-packages/gi/__init__.py", line 42, in Sep 11 18:22:39 arctic gnome-shell[18808]: from . import _gi Sep 11 18:22:39 arctic gnome-shell[18808]: ImportError: libffi.so.7: cannot open shared object file: No such file or directory And then Terminal never launches. libffi.so.8 is found in /usr/lib/x86_64-linux-gnu/, but libffi.so.7 is missing. $ lsb_release -rd Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1895360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895360] [NEW] Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7
Public bug reported: When I launch Terminal, I see the following error (st and urxvt are still launchable, as are Discord and Spotify, among others): Sep 11 18:22:39 arctic systemd[1918]: Started Application launched by gnome-shell. Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[18808]: Traceback (most recent call last): Sep 11 18:22:39 arctic gnome-shell[18808]: File "/usr/bin/gnome-terminal", line 9, in Sep 11 18:22:39 arctic gnome-shell[18808]: from gi.repository import GLib, Gio Sep 11 18:22:39 arctic gnome-shell[18808]: File "/home/alichtman/.local/lib/python3.8/site-packages/gi/__init__.py", line 42, in Sep 11 18:22:39 arctic gnome-shell[18808]: from . import _gi Sep 11 18:22:39 arctic gnome-shell[18808]: ImportError: libffi.so.7: cannot open shared object file: No such file or directory And then Terminal never launches. libffi.so.8 is found in /usr/lib/x86_64-linux-gnu/, but libffi.so.7 is missing. $ lsb_release -rd Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 ** Affects: libffi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1895360 Title: Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 Status in libffi package in Ubuntu: New Bug description: When I launch Terminal, I see the following error (st and urxvt are still launchable, as are Discord and Spotify, among others): Sep 11 18:22:39 arctic systemd[1918]: Started Application launched by gnome-shell. Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[18808]: Traceback (most recent call last): Sep 11 18:22:39 arctic gnome-shell[18808]: File "/usr/bin/gnome-terminal", line 9, in Sep 11 18:22:39 arctic gnome-shell[18808]: from gi.repository import GLib, Gio Sep 11 18:22:39 arctic gnome-shell[18808]: File "/home/alichtman/.local/lib/python3.8/site-packages/gi/__init__.py", line 42, in Sep 11 18:22:39 arctic gnome-shell[18808]: from . import _gi Sep 11 18:22:39 arctic gnome-shell[18808]: ImportError: libffi.so.7: cannot open shared object file: No such file or directory And then Terminal never launches. libffi.so.8 is found in /usr/lib/x86_64-linux-gnu/, but libffi.so.7 is missing. $ lsb_release -rd Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1895360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
** Changed in: wpa (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Released Status in wpa package in Debian: Fix Released Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798369] Re: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock"
** Merge proposal linked: https://code.launchpad.net/~mfo/ubiquity/+git/ubiquity/+merge/390637 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1798369 Title: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock" Status in APT: New Status in ubiquity: New Status in apt package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Status in apt source package in Eoan: Invalid Status in ubiquity source package in Eoan: Won't Fix Bug description: When trying to reinstall an existing Ubuntu cosmic installation using latest 18.10 desktop images, the install shows an error dialog around the end of the installation with an "Error restoring installed applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: * Download latest cosmic image * Install cosmic on the whole disk (can be on a VM) * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu * Finish configuration The install itself doesn't fail, but around the end of the installation process the error dialog appears. System is still bootable but left with old packages. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1798369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895349] [NEW] Sync libgweather 3.36.1-1 (main) from Debian unstable (main)
Public bug reported: Please sync libgweather 3.36.1-1 (main) from Debian unstable (main) It's a bug-fix release. Changelog entries since current groovy version 3.36.0-1: libgweather (3.36.1-1) unstable; urgency=medium * Team upload * New upstream release - This version works around the unavailability of the NOAA weather services by using very short-term forecasts as current weather conditions. (Closes: #968909) -- Simon McVittie Fri, 28 Aug 2020 23:36:23 +0100 ** Affects: libgweather (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1895349 Title: Sync libgweather 3.36.1-1 (main) from Debian unstable (main) Status in libgweather package in Ubuntu: New Bug description: Please sync libgweather 3.36.1-1 (main) from Debian unstable (main) It's a bug-fix release. Changelog entries since current groovy version 3.36.0-1: libgweather (3.36.1-1) unstable; urgency=medium * Team upload * New upstream release - This version works around the unavailability of the NOAA weather services by using very short-term forecasts as current weather conditions. (Closes: #968909) -- Simon McVittie Fri, 28 Aug 2020 23:36:23 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1895349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895339] [NEW] display has stopped autorotating once logged-in
Public bug reported: My modern Spin 5 (SP513-54N) is able to flip display into both "tent" mode and/or "tablet" mode (almost 360°) and it used to flip OS screen automatically, too. Recently, the automatic rotation works only at login screen (before I log in), once logged-in, flipping display keeps screen unrotated :( What might be the cause? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 20:18:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:8a5a] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:141f] InstallationDate: Installed on 2020-06-19 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=415eed75-e8aa-4b5a-a49d-51f5b103641e ro quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1895339 Title: display has stopped autorotating once logged-in Status in xorg package in Ubuntu: New Bug description: My modern Spin 5 (SP513-54N) is able to flip display into both "tent" mode and/or "tablet" mode (almost 360°) and it used to flip OS screen automatically, too. Recently, the automatic rotation works only at login screen (before I log in), once logged-in, flipping display keeps screen unrotated :( What might be the cause? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 20:18:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:8a5a] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:141f] InstallationDate: Installed on 2020-06-19 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=415eed75-e8aa-4b5a-a49d-51f5b103641e ro quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri
[Touch-packages] [Bug 1895339] Re: display has stopped autorotating once logged-in
Ah, my fault I am sorry, I've just found out there is a "Lock Screen Rotation" button in notification area which has been enabled (although accidentally). Please close this issue, thanks and sorry. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1895339 Title: display has stopped autorotating once logged-in Status in xorg package in Ubuntu: New Bug description: My modern Spin 5 (SP513-54N) is able to flip display into both "tent" mode and/or "tablet" mode (almost 360°) and it used to flip OS screen automatically, too. Recently, the automatic rotation works only at login screen (before I log in), once logged-in, flipping display keeps screen unrotated :( What might be the cause? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 20:18:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:8a5a] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:141f] InstallationDate: Installed on 2020-06-19 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=415eed75-e8aa-4b5a-a49d-51f5b103641e ro quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around
Nor the upgrade after that, ugh. Fixing. ** Changed in: base-files (Ubuntu) Importance: Undecided => High ** Changed in: base-files (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1895302 Title: groovy debootstrap leaves /e/d/motd-news.wasremoved around Status in base-files package in Ubuntu: In Progress Bug description: When debootstrapping groovy, we see an empty /etc/default/motd- news.wasremoved file. - groovy: base-files 11ubuntu12 -rw-r--r-- 1 root root 0 set 11 10:20 /etc/default/motd-news.wasremoved If motd-news-config is later installed, maybe via ubuntu-server, then the presence of this file will disable motd-news by default, which is unintended as it's meant to be enabled on a server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1895302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
syslog shows : Sep 11 20:03:43 orion kernel: [ 104.062316] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20570500 Sep 11 20:03:44 orion kernel: [ 105.065317] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20670500 Sep 11 20:03:45 orion kernel: [ 106.072545] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20770500 Sep 11 20:03:46 orion kernel: [ 107.075711] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20870500 Sep 11 20:03:47 orion kernel: [ 108.078909] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 11 20:03:48 orion kernel: [ 109.091307] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 11 20:03:49 orion kernel: [ 110.099662] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 11 20:03:50 orion kernel: [ 111.107911] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 11 20:03:52 orion kernel: [ 112.144229] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x202f8100 Sep 11 20:03:53 orion kernel: [ 113.152440] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x202f8100 Sep 11 20:03:54 orion kernel: [ 114.160509] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20170500 Sep 11 20:03:55 orion kernel: [ 115.168750] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20370500 Sep 11 20:03:56 orion kernel: [ 116.176862] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470500 Sep 11 20:03:57 orion kernel: [ 117.188948] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20570500 Sep 11 20:03:58 orion kernel: [ 118.192973] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20670500 Sep 11 20:03:59 orion kernel: [ 119.205012] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20770500 Sep 11 20:04:00 orion kernel: [ 120.216980] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20870500 Sep 11 20:04:01 orion kernel: [ 121.228946] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 11 20:04:02 orion kernel: [ 122.240854] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 -- kern.log shows : Sep 11 20:03:34 orion kernel: [ 94.967128] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 11 20:03:35 orion kernel: [ 95.977126] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 11 20:03:36 orion kernel: [ 96.979389] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 11 20:03:37 orion kernel: [ 97.985740] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 11 20:03:38 orion kernel: [ 99.020209] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x202f8100 Sep 11 20:03:39 orion kernel: [ 100.030810] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x202f8100 Sep 11 20:03:40 orion kernel: [ 101.037589] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20170500 Sep 11 20:03:41 orion kernel: [ 102.044399] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20370500 Sep 11 20:03:42 orion kernel: [ 103.055305] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470500 Sep 11 20:03:43 orion kernel: [ 104.062316] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20570500 Sep 11 20:03:44 orion kernel: [ 105.065317] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20670500 Sep 11 20:03:45 orion kernel: [ 106.072545] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20770500 Sep 11 20:03:46 orion kernel: [ 107.075711] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20870500 Sep 11 20:03:47 orion kernel: [ 108.078909] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 11 20:03:48 orion kernel: [ 109.091307] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 11 20:03:49 orion kernel: [ 110.099662] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 11 20:03:50 orion kernel: [ 111.107911] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 11 20:03:52 orion kernel: [ 112.144229] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x202f8100 Sep
[Touch-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
syslog ** Attachment added: "syslog.gz" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894881/+attachment/5409904/+files/syslog.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: kernel 5.4.0-47-generic #51 upgraded today to this new kernel sound is now totally broken kern.org and syslog are filling with those messages every second, in loop, with no end to it : Sep 8 19:42:34 orion kernel: [ 147.398030] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 8 19:42:35 orion kernel: [ 148.410043] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 8 19:42:36 orion kernel: [ 149.413955] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 8 19:42:37 orion kernel: [ 150.421890] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 8 19:42:38 orion kernel: [ 151.453799] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:39 orion kernel: [ 152.461793] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:41 orion kernel: [ 153.473734] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:42 orion kernel: [ 154.477653] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:43 orion kernel: [ 155.481576] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:44 orion kernel: [ 156.489620] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:45 orion kernel: [ 157.497553] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:46 orion kernel: [ 158.509530] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:47 orion kernel: [ 159.513471] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Because of this, machine has become very slow and response time is awful Login into the machine, even trying to launch a simple program can take up to 30 seconds of wait before anything happens. Sound was working fine with previous kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gf 1758 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 19:42:19 2020 InstallationDate: Installed on 2020-08-29 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
kern.log ** Attachment added: "kern.log.gz" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894881/+attachment/5409903/+files/kern.log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: kernel 5.4.0-47-generic #51 upgraded today to this new kernel sound is now totally broken kern.org and syslog are filling with those messages every second, in loop, with no end to it : Sep 8 19:42:34 orion kernel: [ 147.398030] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 8 19:42:35 orion kernel: [ 148.410043] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 8 19:42:36 orion kernel: [ 149.413955] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 8 19:42:37 orion kernel: [ 150.421890] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 8 19:42:38 orion kernel: [ 151.453799] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:39 orion kernel: [ 152.461793] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:41 orion kernel: [ 153.473734] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:42 orion kernel: [ 154.477653] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:43 orion kernel: [ 155.481576] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:44 orion kernel: [ 156.489620] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:45 orion kernel: [ 157.497553] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:46 orion kernel: [ 158.509530] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:47 orion kernel: [ 159.513471] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Because of this, machine has become very slow and response time is awful Login into the machine, even trying to launch a simple program can take up to 30 seconds of wait before anything happens. Sound was working fine with previous kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gf 1758 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 19:42:19 2020 InstallationDate: Installed on 2020-08-29 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
Just booted my machine from being off. No sound. Messages filling kern.log and syslog. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: kernel 5.4.0-47-generic #51 upgraded today to this new kernel sound is now totally broken kern.org and syslog are filling with those messages every second, in loop, with no end to it : Sep 8 19:42:34 orion kernel: [ 147.398030] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 8 19:42:35 orion kernel: [ 148.410043] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 8 19:42:36 orion kernel: [ 149.413955] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 8 19:42:37 orion kernel: [ 150.421890] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 8 19:42:38 orion kernel: [ 151.453799] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:39 orion kernel: [ 152.461793] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:41 orion kernel: [ 153.473734] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:42 orion kernel: [ 154.477653] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:43 orion kernel: [ 155.481576] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:44 orion kernel: [ 156.489620] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:45 orion kernel: [ 157.497553] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:46 orion kernel: [ 158.509530] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:47 orion kernel: [ 159.513471] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Because of this, machine has become very slow and response time is awful Login into the machine, even trying to launch a simple program can take up to 30 seconds of wait before anything happens. Sound was working fine with previous kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gf 1758 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 19:42:19 2020 InstallationDate: Installed on 2020-08-29 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite
pcsc-lite source package provides pcscd and libpcsclite1 and thus is needed for smartcard deployment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: New Status in pcsc-lite package in Ubuntu: Incomplete Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and Debian policy. [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant
[Touch-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite
pcscd is required. When removed, I am not able to get any info from the driver about the reader or the smartcard. pcscd loads the smartcard driver and coordinates communications. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: New Status in pcsc-lite package in Ubuntu: Incomplete Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and Debian policy. [Maintenance] The desktop team will subscribe to bugs, however it is
[Touch-packages] [Bug 1004829] Re: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all
mic connected to front is not working with this motherboard in ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1004829 Title: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: Mic doesn't work on Ubuntu 12.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: srinivas 2967 F pulseaudio /dev/snd/controlC0: srinivas 2967 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC887-VD' Components : 'HDA:10ec0887,1458a002,00100302' Controls : 42 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 19' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100200' Controls : 24 Simple ctrls : 4 Date: Sat May 26 14:20:32 2012 InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: 2967 2967 srinivas F pulseaudio /dev/snd/controlC0: srinivas F pulseaudio Symptom_Jack: Pink Mic, Front Symptom_Type: No sound at all Title: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all UpgradeStatus: Upgraded to precise on 2012-04-27 (29 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1004829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1004829] Re: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all
i think i should say: does not work. i cannot test that computer now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1004829 Title: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: Mic doesn't work on Ubuntu 12.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: srinivas 2967 F pulseaudio /dev/snd/controlC0: srinivas 2967 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC887-VD' Components : 'HDA:10ec0887,1458a002,00100302' Controls : 42 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 19' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100200' Controls : 24 Simple ctrls : 4 Date: Sat May 26 14:20:32 2012 InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: 2967 2967 srinivas F pulseaudio /dev/snd/controlC0: srinivas F pulseaudio Symptom_Jack: Pink Mic, Front Symptom_Type: No sound at all Title: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all UpgradeStatus: Upgraded to precise on 2012-04-27 (29 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1004829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895325] [NEW] driver does not detect usb-printer
Public bug reported: masha@masha-Lenovo-G50-80:~$ lsmod | grep usb rtsx_usb_ms24576 0 memstick 20480 1 rtsx_usb_ms btusb 57344 0 btrtl 24576 1 btusb btbcm 16384 1 btusb btintel24576 1 btusb usblp 24576 0 bluetooth 581632 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm rtsx_usb_sdmmc 32768 0 usbhid 57344 0 hid 131072 3 hid_a4tech,usbhid,hid_generic rtsx_usb 28672 2 rtsx_usb_sdmmc,rtsx_usb_ms masha@masha-Lenovo-G50-80:~$ tail -f /var/log/syslog Sep 11 19:35:55 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c00106. Sep 11 19:35:55 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c0010a. Sep 11 19:36:04 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c00114. Sep 11 19:36:23 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c0011b. Sep 11 19:36:23 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c0011f. Sep 11 19:36:28 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c00129. Sep 11 19:36:37 masha-Lenovo-G50-80 kernel: [13784.532617] usb 1-3: USB disconnect, device number 11 Sep 11 19:36:37 masha-Lenovo-G50-80 kernel: [13784.533279] usblp0: removed Sep 11 19:36:39 masha-Lenovo-G50-80 gnome-shell[1854]: Source ID 181143 was not found when attempting to remove it Sep 11 19:36:47 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c00130. Sep 11 19:37:16 masha-Lenovo-G50-80 gnome-shell[1854]: Source ID 181573 was not found when attempting to remove it Sep 11 19:37:21 masha-Lenovo-G50-80 gnome-shell[1854]: Source ID 181611 was not found when attempting to remove it Sep 11 19:37:24 masha-Lenovo-G50-80 gnome-shell[1854]: Source ID 181625 was not found when attempting to remove it Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.671345] usb 1-3: new high-speed USB device number 12 using xhci_hcd Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.824523] usb 1-3: New USB device found, idVendor=04a9, idProduct=181e, bcdDevice= 1.01 Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.824530] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.824534] usb 1-3: Product: E410 series Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.824537] usb 1-3: Manufacturer: Canon Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.824540] usb 1-3: SerialNumber: D22179 Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.834767] usblp 1-3:1.1: usblp0: USB Bidirectional printer dev 12 if 1 alt 0 proto 2 vid 0x04A9 pid 0x181E Sep 11 19:40:01 masha-Lenovo-G50-80 systemd[1]: Started Configure Plugged-In Printer. Sep 11 19:40:01 masha-Lenovo-G50-80 udev-configure-printer: add usb-001-012 Sep 11 19:40:02 masha-Lenovo-G50-80 udev-configure-printer: device devpath is /devices/pci:00/:00:14.0/usb1/1-3 Sep 11 19:40:02 masha-Lenovo-G50-80 udev-configure-printer: Device already handled Sep 11 19:40:02 masha-Lenovo-G50-80 systemd[1]: configure-printer@usb-001-012.service: Main process exited, code=exited, status=1/FAILURE Sep 11 19:40:02 masha-Lenovo-G50-80 systemd[1]: configure-printer@usb-001-012.service: Failed with result 'exit-code'. Sep 11 19:40:04 masha-Lenovo-G50-80 kernel: [13991.650602] usb 1-3: USB disconnect, device number 12 Sep 11 19:40:04 masha-Lenovo-G50-80 kernel: [13991.651070] usblp0: removed Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.451332] usb 1-3: new high-speed USB device number 13 using xhci_hcd Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.607883] usb 1-3: New USB device found, idVendor=04a9, idProduct=181e, bcdDevice= 1.01 Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.607889] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.607893] usb 1-3: Product: E410 series Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.607896] usb 1-3: Manufacturer: Canon Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.607899] usb 1-3: SerialNumber: D22179 Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.619190] usblp 1-3:1.1: usblp0: USB Bidirectional printer dev 13 if 1 alt 0 proto 2 vid 0x04A9 pid 0x181E Sep 11 19:40:05 masha-Lenovo-G50-80 systemd[1]: Started Configure Plugged-In Printer. Sep 11 19:40:05 masha-Lenovo-G50-80 udev-configure-printer: add usb-001-013 Sep 11 19:40:05 masha-Lenovo-G50-80 udev-configure-printer: device devpath is
[Touch-packages] [Bug 1895317] Re: Intel driver not working
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1895317 Title: Intel driver not working Status in xorg package in Ubuntu: New Bug description: i upgraded my sony vaio model VPCEB1E0E from windows 7 to ubuntu but lost my intel driver before i upgraded. problem caused is a black dead screen on my laptop but i have access to a monitor which im currently using to use ubuntu. i need the driver for my laptop screen (primary screen) to work. please give me a solution. thanks in advance ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 17:06:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.66, 5.4.0-050400-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Core Processor Integrated Graphics Controller [104d:9071] InstallationDate: Installed on 2020-09-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Sony Corporation VPCEB1E0E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=700fef99-f312-4e95-a170-69e4f1a09494 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0230Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0230Y8:bd01/26/2010:svnSonyCorporation:pnVPCEB1E0E:pvrC603YD6R:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCEB1E0E dmi.product.sku: N/A dmi.product.version: C603YD6R dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102+git2009040630.77687f~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2009101930.2f62a4~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895317] [NEW] Intel driver not working
You have been subscribed to a public bug: i upgraded my sony vaio model VPCEB1E0E from windows 7 to ubuntu but lost my intel driver before i upgraded. problem caused is a black dead screen on my laptop but i have access to a monitor which im currently using to use ubuntu. i need the driver for my laptop screen (primary screen) to work. please give me a solution. thanks in advance ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 17:06:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.66, 5.4.0-050400-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Core Processor Integrated Graphics Controller [104d:9071] InstallationDate: Installed on 2020-09-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Sony Corporation VPCEB1E0E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=700fef99-f312-4e95-a170-69e4f1a09494 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0230Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0230Y8:bd01/26/2010:svnSonyCorporation:pnVPCEB1E0E:pvrC603YD6R:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCEB1E0E dmi.product.sku: N/A dmi.product.version: C603YD6R dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102+git2009040630.77687f~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2009101930.2f62a4~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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 third-party-packages ubuntu -- Intel driver not working https://bugs.launchpad.net/bugs/1895317 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)
** Patch added: "This is the (tested) debdiff with the proposed SRU, for Bionic
only."
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+attachment/5409870/+files/bionic_systemd_lp1830746.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting in systemd (pid 1) too low for containers (bionic)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Cosmic:
Won't Fix
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[Impact]
* Since systemd commit fb3ae275cb ("main: bump RLIMIT_NOFILE for the root
user substantially") [https://github.com/systemd/systemd/commit/fb3ae275cb],
which is present in Bionic, the memlock ulimit value was bumped to 16M. It's an
adjustable limit, but the default (in previous Ubuntu releases/systemd
versions) was really small.
* Although bumping this value was a good thing, 16M is not enough and we can
see failures on mlock'ed allocations on Bionic, like the one hereby reported by
Kees or the recent introduced cryptsetup build failures (due to PPA builder
updates to Bionic) - see https://bugs.launchpad.net/bugs//1891473.
* It's especially harmful in containers to have such "small" limit, so
we are hereby SRUing a more recent bump from upstream systemd, in the
form of commit 91cfdd8d29 ("core: bump mlock ulimit to 64Mb")
[https://github.com/systemd/systemd/commit/91cfdd8d29]. Latest Ubuntu
releases, like Focal and subsequent ones, already include this patch
so effectively we're putting Bionic on-par with newer releases.
* A discussion about this topic (leading to this SRU) is present in
ubuntu-devel ML: https://lists.ubuntu.com/archives/ubuntu-
devel/2020-September/041159.html.
[Test Case]
* The straightforward test is to just look "ulimit -l" and "ulimit -Hl" in a
current Bionic system, and then install an updated version with the hereby
proposed SRU to see such limit bump from 16M to 64M (after a reboot) - a
version containing this fix is available at my PPA as of 2020-09-10 [0] (likely
to be deleted in next month or so).
* A more interesting test is to run a Focal container in a current
Bionic system and try to build the cryptsetup package - it'll fail in
some tests. After updating the host (Bionic) systemd to include the
mlock bump patch, the build succeeds in the Focal container.
[Regression Potential]
* Since it's a simple bump and it makes Bionic behave like Focal, I don't
foresee regressions. One potential issue would be if some users rely on the
lower default limit (16M) and this value is bumped by a package update, but
that could be circumvented by setting a lower limit in limits.conf. The
benefits for such bump are likely much bigger than any "regression" caused for
users relying on such default limit.
[0] https://launchpad.net/~gpiccoli/+archive/ubuntu/test1830746
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)
** Description changed:
- See also https://discuss.linuxcontainers.org/t/limits-kernel-memlock-
- cannot-exceed-16777216/4856/5
+ [Impact]
+ * Since systemd commit fb3ae275cb ("main: bump RLIMIT_NOFILE for the root
user substantially") [https://github.com/systemd/systemd/commit/fb3ae275cb],
which is present in Bionic, the memlock ulimit value was bumped to 16M. It's an
adjustable limit, but the default (in previous Ubuntu releases/systemd
versions) was really small.
+ * Although bumping this value was a good thing, 16M is not enough and we can
see failures on mlock'ed allocations on Bionic, like the one hereby reported by
Kees or the recent introduced cryptsetup build failures (due to PPA builder
updates to Bionic) - see https://bugs.launchpad.net/bugs//1891473.
- In containers, the limits.kernel.memlock cannot exceed 16777216 when the
- container is bionic. The memlock setting is set to 16M in systemd and
- cannot be bumped up in an unprivileged container.
+ * It's especially harmful in containers to have such "small" limit, so
+ we are hereby SRUing a more recent bump from upstream systemd, in the
+ form of commit 91cfdd8d29 ("core: bump mlock ulimit to 64Mb")
+ [https://github.com/systemd/systemd/commit/91cfdd8d29]. Latest Ubuntu
+ releases, like Focal and subsequent ones, already include this patch so
+ effectively we're putting Bionic on-par with newer releases.
- This is fixed in upstream systemd.
+ * A discussion about this topic (leading to this SRU) is present in
+ ubuntu-devel ML: https://lists.ubuntu.com/archives/ubuntu-
+ devel/2020-September/041159.html.
- Container ubuntu version:
- Distributor ID: Ubuntu
- Description: Ubuntu 18.04.2 LTS
- Release: 18.04
- Codename: bionic
+ [Test Case]
+ * The straightforward test is to just look "ulimit -l" and "ulimit -Hl" in a
current Bionic system, and then install an updated version with the hereby
proposed SRU to see such limit bump from 16M to 64M (after a reboot) - a
version containing this fix is available at my PPA as of 2020-09-10 [0] (likely
to be deleted in next month or so).
- systemd package version: 237-3ubuntu10.21
+ * A more interesting test is to run a Focal container in a current
+ Bionic system and try to build the cryptsetup package - it'll fail in
+ some tests. After updating the host (Bionic) systemd to include the
+ mlock bump patch, the build succeeds in the Focal container.
+
+ [Regression Potential]
+ * Since it's a simple bump and it makes Bionic behave like Focal, I don't
foresee regressions. One potential issue would be if some users rely on the
lower default limit (16M) and this value is bumped by a package update, but
that could be circumvented by setting a lower limit in limits.conf. The
benefits for such bump are likely much bigger than any "regression" caused for
users relying on such default limit.
+
+
+ [0] https://launchpad.net/~gpiccoli/+archive/ubuntu/test1830746
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Tags removed: patch rls-dd-incoming
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting in systemd (pid 1) too low for containers (bionic)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Cosmic:
Won't Fix
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[Impact]
* Since systemd commit fb3ae275cb ("main: bump RLIMIT_NOFILE for the root
user substantially") [https://github.com/systemd/systemd/commit/fb3ae275cb],
which is present in Bionic, the memlock ulimit value was bumped to 16M. It's an
adjustable limit, but the default (in previous Ubuntu releases/systemd
versions) was really small.
* Although bumping this value was a good thing, 16M is not enough and we can
see failures on mlock'ed allocations on Bionic, like the one hereby reported by
Kees or the recent introduced cryptsetup build failures (due to PPA builder
updates to Bionic) - see https://bugs.launchpad.net/bugs//1891473.
* It's especially harmful in containers to have such "small" limit, so
we are hereby SRUing a more recent bump from upstream systemd, in the
form of commit 91cfdd8d29 ("core: bump mlock ulimit to 64Mb")
[https://github.com/systemd/systemd/commit/91cfdd8d29]. Latest Ubuntu
releases, like Focal and subsequent ones, already include this patch
so effectively we're putting
[Touch-packages] [Bug 1775219] Re: incorrectly reports package as unsupported if apt cache is empty
** Branch linked: lp:~tdaitx/ubuntu/groovy/apport/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1775219
Title:
incorrectly reports package as unsupported if apt cache is empty
Status in apport package in Ubuntu:
Confirmed
Bug description:
Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:
$ ubuntu-bug coreutils
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.
*** Problem in coreutils
The problem cannot be reported:
This is not an official Ubuntu package. Please remove any third
party package and try again.
A simpler recreate is:
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
False
$ sudo apt update -qq
All packages are up to date.
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
True
Desired result:
The message should instruct the user to run 'apt update' as root if
they think this is in error. That would improve usability and avoid
false reports about apport incorrectly flagging a package as
unsupported.
Additionally, if the user is root (and optionally if the set of
package candidates only contains a 'now' component)
self._cache.update(); self._cache.open() could be called to download
lists.
Alternatively it could just check to see if lists have been
downloaded.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775219/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package
I filed https://bugs.launchpad.net/ubuntu/+source/base- files/+bug/1895302 for that. Do you happen to know a good way to test the first-time installation of base-files with debootstrap? It would be awesome if I could give it a ppa to consider, in addition to the archive, and it would then just pick my test base-files instead of the one from the archive. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in ubuntu-meta source package in Xenial: Fix Released Status in base-files source package in Bionic: Fix Released Status in ubuntu-meta source package in Bionic: Fix Released Status in base-files source package in Focal: Fix Released Status in ubuntu-meta source package in Focal: Fix Released Status in base-files source package in Groovy: Fix Released Status in ubuntu-meta source package in Groovy: Fix Released Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) [Regression Potential] This update is about config file ownership transfer: /e/d/motd-news belonged to base-files, now it belongs to motd-news-config. We tried to handle two important cases here: a) /e/d/motd-news config was changed while it belonged to base-files. For example, an user could have set ENABLED=0. We need to transfer that change to the motd-news-config package when it is installed, otherwise this SRU would jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's configure case. b) /e/d/motd-news config file was *removed* while it belonged to base-files. In such a case, a normal upgrade of the package (base-files in this example) would not reinstate the file. Much less this upgrade here, which has an explicit rm_conffile maintscript-helper for it. But the motd-news-config package that could be installed in the
[Touch-packages] [Bug 1894907] Re: FTBFS with sphinx 3.2
** Changed in: cyrus-sasl2 Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1894907 Title: FTBFS with sphinx 3.2 Status in Cyrus-sasl2: New Status in cyrus-sasl2 package in Ubuntu: Triaged Status in cyrus-sasl2 package in Debian: New Bug description: cyrus-sasl2 ships with a sphinx extension to build its documentation, and this extension was based on a very old sphinx version. It no longer builds with sphinx 3.2.1 from groovy, failing in several places: a) "NoUri" Extension error: Could not import extension sphinxlocal.builders.manpage (exception: cannot import name 'NoUri' from 'sphinx.environment' (/usr/lib/python3/dist-packages/sphinx/environment/__init__.py)) make[2]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2 make[2]: Leaving directory '/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal' make[1]: *** [Makefile:686: all-recursive] Error 1 make[1]: Leaving directory '/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal' make: *** [Makefile:556: all] Error 2 Debian has a bug report already at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=955095 b) MACRO_DEF Extension error: Could not import extension sphinxlocal.builders.manpage (exception: cannot import name 'MACRO_DEF' from 'sphinx.writers.manpage' (/usr/lib/python3/dist-packages/sphinx/writers/manpage.py)) make[4]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2 make[4]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' make[3]: *** [Makefile:686: all-recursive] Error 1 make[3]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' make[2]: *** [Makefile:556: all] Error 2 make[2]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' dh_auto_build: error: cd build-heimdal && make -j4 sasldir=/usr/lib/x86_64-linux-gnu/sasl2 returned exit code 2 make[1]: *** [debian/rules:164: override_dh_auto_build] Error 25 make[1]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2' make: *** [debian/rules:122: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/1894907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895302] Re: groovy debootstrap leaves /e/d/motd-news.wasremoved around
I think this postinst bit never considered the fresh install case:
# special case of having /etc/default/motd-news removed by hand
# signal the motd-news-config package that this happened, so that
# it does not put back the file with default contents which would
# re-enable motd-news
motd_news_config="/etc/default/motd-news"
if [ ! -e ${motd_news_config} ]; then
if [ ! -e ${motd_news_config}.dpkg-remove ]; then
if [ ! -e ${motd_news_config}.dpkg-backup ]; then
touch ${motd_news_config}.wasremoved
fi
fi
fi
Having it only act on upgrades might be the easier fix. I'll test.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1895302
Title:
groovy debootstrap leaves /e/d/motd-news.wasremoved around
Status in base-files package in Ubuntu:
New
Bug description:
When debootstrapping groovy, we see an empty /etc/default/motd-
news.wasremoved file.
- groovy: base-files 11ubuntu12
-rw-r--r-- 1 root root 0 set 11 10:20 /etc/default/motd-news.wasremoved
If motd-news-config is later installed, maybe via ubuntu-server, then
the presence of this file will disable motd-news by default, which is
unintended as it's meant to be enabled on a server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1895302/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894907] Re: FTBFS with sphinx 2.4
** Summary changed: - FTBFS with sphinx 2.4: cannot import name 'NoUri' + FTBFS with sphinx 2.4 ** Description changed: - Getting this failure to build on groovy: + cyrus-sasl2 ships with a sphinx extension to build its documentation, + and this extension was based on a very old sphinx version. It no longer + builds with sphinx 3.2.1 from groovy, failing in several places: + a) "NoUri" Extension error: Could not import extension sphinxlocal.builders.manpage (exception: cannot import name 'NoUri' from 'sphinx.environment' (/usr/lib/python3/dist-packages/sphinx/environment/__init__.py)) make[2]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2 make[2]: Leaving directory '/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal' make[1]: *** [Makefile:686: all-recursive] Error 1 make[1]: Leaving directory '/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal' make: *** [Makefile:556: all] Error 2 + Debian has a bug report already at https://bugs.debian.org/cgi- + bin/bugreport.cgi?bug=955095 - Debian has a bug report already at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955095 + b) MACRO_DEF + Extension error: + Could not import extension sphinxlocal.builders.manpage (exception: cannot import name 'MACRO_DEF' from 'sphinx.writers.manpage' (/usr/lib/python3/dist-packages/sphinx/writers/manpage.py)) + make[4]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2 + make[4]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' + make[3]: *** [Makefile:686: all-recursive] Error 1 + make[3]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' + make[2]: *** [Makefile:556: all] Error 2 + make[2]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' + dh_auto_build: error: cd build-heimdal && make -j4 sasldir=/usr/lib/x86_64-linux-gnu/sasl2 returned exit code 2 + make[1]: *** [debian/rules:164: override_dh_auto_build] Error 25 + make[1]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2' + make: *** [debian/rules:122: build] Error 2 + dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 ** Summary changed: - FTBFS with sphinx 2.4 + FTBFS with sphinx 3.2 ** Bug watch added: github.com/cyrusimap/cyrus-sasl/issues #624 https://github.com/cyrusimap/cyrus-sasl/issues/624 ** Also affects: cyrus-sasl2 via https://github.com/cyrusimap/cyrus-sasl/issues/624 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1894907 Title: FTBFS with sphinx 3.2 Status in Cyrus-sasl2: Unknown Status in cyrus-sasl2 package in Ubuntu: Triaged Status in cyrus-sasl2 package in Debian: New Bug description: cyrus-sasl2 ships with a sphinx extension to build its documentation, and this extension was based on a very old sphinx version. It no longer builds with sphinx 3.2.1 from groovy, failing in several places: a) "NoUri" Extension error: Could not import extension sphinxlocal.builders.manpage (exception: cannot import name 'NoUri' from 'sphinx.environment' (/usr/lib/python3/dist-packages/sphinx/environment/__init__.py)) make[2]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2 make[2]: Leaving directory '/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal' make[1]: *** [Makefile:686: all-recursive] Error 1 make[1]: Leaving directory '/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal' make: *** [Makefile:556: all] Error 2 Debian has a bug report already at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=955095 b) MACRO_DEF Extension error: Could not import extension sphinxlocal.builders.manpage (exception: cannot import name 'MACRO_DEF' from 'sphinx.writers.manpage' (/usr/lib/python3/dist-packages/sphinx/writers/manpage.py)) make[4]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2 make[4]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' make[3]: *** [Makefile:686: all-recursive] Error 1 make[3]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' make[2]: *** [Makefile:556: all] Error 2 make[2]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' dh_auto_build: error: cd build-heimdal && make -j4 sasldir=/usr/lib/x86_64-linux-gnu/sasl2 returned exit code 2 make[1]: *** [debian/rules:164: override_dh_auto_build] Error 25 make[1]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2' make: *** [debian/rules:122: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/1894907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1895006] Re: FTBFS with sphinx 2.4: cannot import name 'MACRO_DEF'
*** This bug is a duplicate of bug 1894907 *** https://bugs.launchpad.net/bugs/1894907 ** This bug has been marked a duplicate of bug 1894907 FTBFS with sphinx 2.4: cannot import name 'NoUri' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1895006 Title: FTBFS with sphinx 2.4: cannot import name 'MACRO_DEF' Status in cyrus-sasl2 package in Ubuntu: Triaged Status in cyrus-sasl2 package in Debian: New Bug description: sed -e 's,[@]LIB_DOOR[@],,g' -e 's,[@]SASL_DL_LIB[@],-ldl,g' -e 's,[@]LIBS[@],-lresolv ,g' -e 's,[@]VERSION[@],2.1.27,g' -e 's,[@]libdir[@],/usr/lib/x86_64-linux-gnu,g' -e 's,[@]prefix[@],/usr,g' -e 's,[@]exec_prefix[@],/usr,g' -e 's,[@]includedir[@],/usr/include,g' < ../libsasl2.pc.in > libsasl2.pc /usr/bin/sphinx-build -d docsrc/.doctrees -n -q -b cyrman ./docsrc ./man Extension error: Could not import extension sphinxlocal.builders.manpage (exception: cannot import name 'MACRO_DEF' from 'sphinx.writers.manpage' (/usr/lib/python3/dist-packages/sphinx/writers/manpage.py)) make[4]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2 make[4]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' make[3]: *** [Makefile:686: all-recursive] Error 1 make[3]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' make[2]: *** [Makefile:556: all] Error 2 make[2]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' dh_auto_build: error: cd build-heimdal && make -j4 sasldir=/usr/lib/x86_64-linux-gnu/sasl2 returned exit code 2 make[1]: *** [debian/rules:164: override_dh_auto_build] Error 25 make[1]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2' make: *** [debian/rules:122: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1895006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895294] Re: Fix Raccoon vulnerability (CVE-2020-1968)
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-1968 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1895294 Title: Fix Raccoon vulnerability (CVE-2020-1968) Status in openssl package in Ubuntu: New Bug description: Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been patched yet against the Raccoon Attack (CVE-2020-1968): - https://www.openssl.org/news/secadv/20200909.txt - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968 - https://raccoon-attack.com/ Ubuntu's CVE tracker still lists this as NEEDED for Xenial: - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html Other supported Ubuntu releases use versions of OpenSSL that are not affected. Indeed: $ apt-cache policy openssl openssl: Installed: 1.0.2g-1ubuntu4.16 $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched" Not patched What is the status? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895302] [NEW] groovy debootstrap leaves /e/d/motd-news.wasremoved around
Public bug reported: When debootstrapping groovy, we see an empty /etc/default/motd- news.wasremoved file. - groovy: base-files 11ubuntu12 -rw-r--r-- 1 root root 0 set 11 10:20 /etc/default/motd-news.wasremoved If motd-news-config is later installed, maybe via ubuntu-server, then the presence of this file will disable motd-news by default, which is unintended as it's meant to be enabled on a server. ** Affects: base-files (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1895302 Title: groovy debootstrap leaves /e/d/motd-news.wasremoved around Status in base-files package in Ubuntu: New Bug description: When debootstrapping groovy, we see an empty /etc/default/motd- news.wasremoved file. - groovy: base-files 11ubuntu12 -rw-r--r-- 1 root root 0 set 11 10:20 /etc/default/motd-news.wasremoved If motd-news-config is later installed, maybe via ubuntu-server, then the presence of this file will disable motd-news by default, which is unintended as it's meant to be enabled on a server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1895302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: kernel 5.4.0-47-generic #51 upgraded today to this new kernel sound is now totally broken kern.org and syslog are filling with those messages every second, in loop, with no end to it : Sep 8 19:42:34 orion kernel: [ 147.398030] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 8 19:42:35 orion kernel: [ 148.410043] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 8 19:42:36 orion kernel: [ 149.413955] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 8 19:42:37 orion kernel: [ 150.421890] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 8 19:42:38 orion kernel: [ 151.453799] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:39 orion kernel: [ 152.461793] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:41 orion kernel: [ 153.473734] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:42 orion kernel: [ 154.477653] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:43 orion kernel: [ 155.481576] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:44 orion kernel: [ 156.489620] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:45 orion kernel: [ 157.497553] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:46 orion kernel: [ 158.509530] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:47 orion kernel: [ 159.513471] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Because of this, machine has become very slow and response time is awful Login into the machine, even trying to launch a simple program can take up to 30 seconds of wait before anything happens. Sound was working fine with previous kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gf 1758 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 19:42:19 2020 InstallationDate: Installed on 2020-08-29 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
The impression that I get is that will never be fixed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895294] Re: Fix Raccoon vulnerability (CVE-2020-1968)
** Description changed: Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been - patched yet against the Racoon Attack (CVE-2020-1968): + patched yet against the Raccoon Attack (CVE-2020-1968): - https://www.openssl.org/news/secadv/20200909.txt - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968 - https://raccoon-attack.com/ Ubuntu's CVE tracker still lists this as NEEDED for Xenial: - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html - - Other supported Ubuntu releases use versions of OpenSSL that are not affected. - + Other supported Ubuntu releases use versions of OpenSSL that are not + affected. Indeed: - $ apt-cache policy openssl - openssl: - Installed: 1.0.2g-1ubuntu4.16 + $ apt-cache policy openssl + openssl: + Installed: 1.0.2g-1ubuntu4.16 - $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched" - Not patched - + $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched" + Not patched What is the status? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1895294 Title: Fix Raccoon vulnerability (CVE-2020-1968) Status in openssl package in Ubuntu: New Bug description: Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been patched yet against the Raccoon Attack (CVE-2020-1968): - https://www.openssl.org/news/secadv/20200909.txt - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968 - https://raccoon-attack.com/ Ubuntu's CVE tracker still lists this as NEEDED for Xenial: - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html Other supported Ubuntu releases use versions of OpenSSL that are not affected. Indeed: $ apt-cache policy openssl openssl: Installed: 1.0.2g-1ubuntu4.16 $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched" Not patched What is the status? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895294] [NEW] Fix Raccoon vulnerability (CVE-2020-1968)
Public bug reported: Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been patched yet against the Racoon Attack (CVE-2020-1968): - https://www.openssl.org/news/secadv/20200909.txt - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968 - https://raccoon-attack.com/ Ubuntu's CVE tracker still lists this as NEEDED for Xenial: - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html Other supported Ubuntu releases use versions of OpenSSL that are not affected. Indeed: $ apt-cache policy openssl openssl: Installed: 1.0.2g-1ubuntu4.16 $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched" Not patched What is the status? ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1895294 Title: Fix Raccoon vulnerability (CVE-2020-1968) Status in openssl package in Ubuntu: New Bug description: Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been patched yet against the Racoon Attack (CVE-2020-1968): - https://www.openssl.org/news/secadv/20200909.txt - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968 - https://raccoon-attack.com/ Ubuntu's CVE tracker still lists this as NEEDED for Xenial: - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html Other supported Ubuntu releases use versions of OpenSSL that are not affected. Indeed: $ apt-cache policy openssl openssl: Installed: 1.0.2g-1ubuntu4.16 $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched" Not patched What is the status? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895293] [NEW] After last upgrade systemd uses 100% CPU
Public bug reported: I'm not sure, but none of the already reported bugs seems to fit. At shutdown I get for a moment many messages concerning "automatic report enabled but not possible" (roughly) and after showing these the shutdown lasts about one Minute. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: openafs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 11 14:30:32 2020 InstallationDate: Installed on 2020-09-01 (10 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=8d55d30d-adfe-4f99-9e71-193677d1ec1e ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.release: 3.96 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.96 dmi.board.asset.tag: CZC4123JXT dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: CZC4123JXT dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: LJ449AV dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1895293 Title: After last upgrade systemd uses 100% CPU Status in systemd package in Ubuntu: New Bug description: I'm not sure, but none of the already reported bugs seems to fit. At shutdown I get for a moment many messages concerning "automatic report enabled but not possible" (roughly) and after showing these the shutdown lasts about one Minute. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: openafs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 11 14:30:32 2020 InstallationDate: Installed on 2020-09-01 (10 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=8d55d30d-adfe-4f99-9e71-193677d1ec1e ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.release: 3.96 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.96 dmi.board.asset.tag: CZC4123JXT dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: CZC4123JXT dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: LJ449AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to:
[Touch-packages] [Bug 1895284] Re: Some issues...
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1895284 Title: Some issues... Status in xorg package in Ubuntu: New Bug description: Mozilla would not respond to closing windows. Took a long time to respond. Screen could not be awoken after going to sleep. Stayed black. HD kept running. Forced shut down. Rebooted fine. Launched Mozilla and it got stuck on program startup. Forced shut down again. Reooted fne. Ran Xdiagnose. Got redirected here after bug reporting. Mozilla works fine now! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: i386 CompositorRunning: None Date: Fri Sep 11 12:48:35 2020 DistUpgraded: 2020-05-29 12:17:15,420 DEBUG /openCache(), new cache size 62484 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics Controller (primary) [1043:14e2] Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1043:14e2] InstallationDate: Installed on 2017-07-12 (1156 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: ASUSTeK Computer Inc. A8E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=8064a5cd-fa12-4277-a7b0-317979a30b37 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-05-29 (105 days ago) dmi.bios.date: 03/24/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: A8E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr302:bd03/24/2008:svnASUSTeKComputerInc.:pnA8E:pvr1.0:rvnASUSTeKComputerInc.:rnA8E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: A8E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Aug 17 10:23:03 2018 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17476 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895284/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895284] [NEW] Some issues...
You have been subscribed to a public bug: Mozilla would not respond to closing windows. Took a long time to respond. Screen could not be awoken after going to sleep. Stayed black. HD kept running. Forced shut down. Rebooted fine. Launched Mozilla and it got stuck on program startup. Forced shut down again. Reooted fne. Ran Xdiagnose. Got redirected here after bug reporting. Mozilla works fine now! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: i386 CompositorRunning: None Date: Fri Sep 11 12:48:35 2020 DistUpgraded: 2020-05-29 12:17:15,420 DEBUG /openCache(), new cache size 62484 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics Controller (primary) [1043:14e2] Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1043:14e2] InstallationDate: Installed on 2017-07-12 (1156 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: ASUSTeK Computer Inc. A8E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=8064a5cd-fa12-4277-a7b0-317979a30b37 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-05-29 (105 days ago) dmi.bios.date: 03/24/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: A8E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr302:bd03/24/2008:svnASUSTeKComputerInc.:pnA8E:pvr1.0:rvnASUSTeKComputerInc.:rnA8E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: A8E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Aug 17 10:23:03 2018 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17476 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- Some issues... https://bugs.launchpad.net/bugs/1895284 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] Re: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)
*** This bug is a duplicate of bug 1894452 *** https://bugs.launchpad.net/bugs/1894452 ** Package changed: cups (Ubuntu) => cups-filters (Ubuntu) ** This bug has been marked a duplicate of bug 1894452 shutdown delay because of cups -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups-filters package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Hard to believe there is no kernel developer impacted by this issue... Am about to have to buy a wired headset just to make calls on Teams. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] Re: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)
Those log files are from kernel 5.4.0; I had selected that kernel manually in grub a while ago and didn't remember. Anyways, I just tested this stuff again running the current 20.10 kernel (5.8.0-18-generic), and the same thing happens there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409690/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409689/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409687/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409684/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409686/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409688/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409685/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409681/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] PrintingPackages.txt
apport information ** Attachment added: "PrintingPackages.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409683/+files/PrintingPackages.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409675/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409678/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] Locale.txt
apport information ** Attachment added: "Locale.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409677/+files/Locale.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409676/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409679/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409682/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409680/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] Re: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)
apport information ** Tags added: apport-collected groovy wayland-session ** Description changed: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. - This problem hangs shutdown for 90 seconds, so it quite badly affects - the user experience of Ubuntu as a whole, even for users who never use - cups. + This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu45 + Architecture: amd64 + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2019-11-26 (289 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Lpstat: + device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null + device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ + device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null + MachineType: Dell Inc. XPS 15 9575 + Package: cups 2.3.3-3ubuntu1 + PackageArchitecture: amd64 + Papersize: a4 + PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied + ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + Tags: wayland-session groovy + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) + UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video + _MarkForUpload: True + dmi.bios.date: 05/25/2020 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.12.1 + dmi.board.name: 0C32VW + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 31 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 15 9575 + dmi.product.sku: 080D + dmi.sys.vendor: Dell Inc. ** Attachment added: "CupsErrorLog.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409673/+files/CupsErrorLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session
[Touch-packages] [Bug 1895265] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1895265/+attachment/5409674/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-11-26 (289 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/ device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null MachineType: Dell Inc. XPS 15 9575 Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: wayland-session groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] [NEW] cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)
Public bug reported: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895265] Re: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)
Sorry, I forgot to mention that this issue affects cups-browsed 1.28.1-1 from Ubuntu 20.10 Groovy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895265 Title: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM) Status in cups package in Ubuntu: New Bug description: The cups-browsed service fails to exit when systemd tries to stop it, seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a SIGTERM signal. Here are all the relevant logs in journald when trying to stop cups- browsed using `sudo systemctl stop cups-browsed`: Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 11 10:17:26 ubun sudo[3370]: martin : TTY=pts/2 ; PWD=/home/martin ; USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for user root by (uid=0) Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available locally... Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' timed out. Killing. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 (cups-browsed) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 (gdbus) with signal SIGKILL. Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, code=killed, status=9/KILL Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 'timeout'. Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available locally. Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for user root As you can see, I run the command at 10:17:26, then nothing happens for 90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56. This problem hangs shutdown for 90 seconds, so it quite badly affects the user experience of Ubuntu as a whole, even for users who never use cups. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Kernel-packages] [Bug 1890913] Re: init is using 100% of processor
I am experiencing this same problem and I can confirm that when I mask the apport-autoreport.service the problem stops. I am on Ubuntu 20.10 with Kernel 5.8.0-18-generic. I also have Ubuntu 20.04 with Kernel 5.8.0-05-generic and can confirm the problem does not happen there John -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890913 Title: init is using 100% of processor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894369] Re: apport-autoreport.service fails to start in groovy after upgrading from focal
I have this issue too. It causes systemd's PID 1 (`/sbin/init splash` in htop) to use 100% CPU, which seems unfortunate. When it happens, the log is filled with a whole lot of lines like this: Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Followed by logs like this: Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 11 10:00:02 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 11 10:00:02 ubun whoopsie-upload-all[25552]: /var/crash/_usr_bin_stacer.0.crash already marked for upload, skipping Sep 11 10:00:02 ubun whoopsie-upload-all[25552]: All reports processed Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Succeeded. Sep 11 10:00:02 ubun systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 11 10:00:02 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 11 10:00:02 ubun whoopsie-upload-all[25605]: /var/crash/_usr_bin_stacer.0.crash already marked for upload, skipping Sep 11 10:00:02 ubun whoopsie-upload-all[25605]: All reports processed Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Succeeded. Sep 11 10:00:02 ubun systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 11 10:00:02 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 11 10:00:03 ubun whoopsie-upload-all[25622]: /var/crash/_usr_bin_stacer.0.crash already marked for upload, skipping Sep 11 10:00:03 ubun whoopsie-upload-all[25622]: All reports processed Sep 11 10:00:03 ubun systemd[1]: apport-autoreport.service: Succeeded. Sep 11 10:00:03 ubun systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 11 10:00:03 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1894369 Title: apport-autoreport.service fails to start in groovy after upgrading from focal Status in apport package in Ubuntu: Confirmed Bug description: apport-autoreport.service fails to start with that CPU load increases significantly making computer unusable. disabling the service and path and stopping both normalizes CPU load as it was supposed to be. for test purposes i started apport-autoreport.service and after checking its status i get state: degraded and 2 units failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1894369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895262] [NEW] Installer windows do not fit on screen, when live-CD only boots with 800x600 screen resolution
Public bug reported: I recently got a new laptop, ThinkPad E14 G2 with AMD Ryzen 7 4700U with Radeon Graphics. The live-system boots only with a screen resolution of 800x600, which cannot be increased. The problem is that the windows of the installer do not fit the screen so that the buttons for "cancel", "back" and, most importantly, "continue" are not visible on the screen. Thus any novice trying to install Ubuntu/Linux on a recent laptop with AMD hardware will surely despair and be turned off from using Ubuntu/Linux. I suggest that the windows of the installer get a scroll bar to make it feasible to install Ubuntu in such cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 16:01:52 2020 InstallationDate: Installed on 2015-11-05 (1771 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-09-10 (0 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T21:28:39.455024 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1895262 Title: Installer windows do not fit on screen, when live-CD only boots with 800x600 screen resolution Status in ubuntu-meta package in Ubuntu: New Bug description: I recently got a new laptop, ThinkPad E14 G2 with AMD Ryzen 7 4700U with Radeon Graphics. The live-system boots only with a screen resolution of 800x600, which cannot be increased. The problem is that the windows of the installer do not fit the screen so that the buttons for "cancel", "back" and, most importantly, "continue" are not visible on the screen. Thus any novice trying to install Ubuntu/Linux on a recent laptop with AMD hardware will surely despair and be turned off from using Ubuntu/Linux. I suggest that the windows of the installer get a scroll bar to make it feasible to install Ubuntu in such cases. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 16:01:52 2020 InstallationDate: Installed on 2015-11-05 (1771 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-09-10 (0 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T21:28:39.455024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1895262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766503] Re: ibus-* randomly use high CPU
Wait, there's more If I do multiple CTRL-z + Enter in gnome-calculator, the CPU goes HIGHER , and it stays there until ANY action is made ( either opening an app ( mouse or kbd shortcut, doesn't matter ) , or switch window by alt-tab or mouse ) Seems like an ibus (big?) problem . Also seems ibus is running on multiple processes/cores ( and hangs on all of them in the end ) , is this intended ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in GNOME Shell: Unknown Status in The Ubuntu Power Consumption Project: Confirmed Status in gnome-shell package in Ubuntu: Opinion Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1766503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766503] Re: ibus-* randomly use high CPU
Just after finished previous comment, gnome-calculator crashed ( most probably related to CTRL-z ) . >From syslog : Sep 11 10:44:58 valyelitebook kernel: [1645692.175240] traps: gnome-calculato[9355] trap int3 ip:7f302aceeea1 sp:7ffca1a8ae90 error:0 in libglib-2.0.so.0.5600.4[7f302ac9d000+114000] Sep 11 10:44:58 valyelitebook systemd[1]: Started Process Core Dump (PID 13784/UID 0). Sep 11 10:44:58 valyelitebook systemd-coredump[13785]: Process 9355 (gnome-calculato) of user 1002 dumped core.#012#012Stack trace of thread 9355:#012#0 0x7f302aceeea1 n/a (libglib-2.0.so.0)#012#1 0x7f302acf1819 g_log_writer_default (libglib-2.0.so.0)#012#2 0x7f302acefa8e g_log_structured_array (libglib-2.0.so.0)#012#3 0x7f302acf04ce g_log_structured_standard (libglib-2.0.so.0)#012#4 0x7f3029eabc41 n/a (libgdk-3.so.0)#012#5 0x7f3029eb8ac3 n/a (libgdk-3.so.0)#012#6 0x7f30279068fa _XError (libX11.so.6)#012#7 0x7f302790382b n/a (libX11.so.6)#012#8 0x7f30279038d5 n/a (libX11.so.6)#012#9 0x7f3027904830 _XReply (libX11.so.6)#012#10 0x7f30276ba004 XIGetClientPointer (libXi.so.6)#012#11 0x7f3029ea7030 n/a (libgdk-3.so.0)#012#12 0x7f3029ea85a4 n/a (libgdk-3.so.0)#012#13 0x7f3029eb3810 n/a (libgdk-3.so.0)#012#14 0x7f3029eb3329 n/a (libgdk-3.so.0)#012#15 0x7f3029e7dd70 gdk_display_get_event (libgdk-3.so.0)#012#16 0x7f3029eb2f82 n/a (libgdk-3.so.0)#012#17 0x7f302ace9417 g_main_context_dispatch (libglib-2.0.so.0)#012#18 0x7f302ace9650 n/a (libglib-2.0.so.0)#012#19 0x7f302ace96dc g_main_context_iteration (libglib-2.0.so.0)#012#20 0x7f3029928efd g_application_run (libgio-2.0.so.0)#012#21 0x5613cd84fbd3 n/a (gnome-calculator)#012#22 0x7f30286c9b97 __libc_start_main (libc.so.6)#012#23 0x5613cd84de3a n/a (gnome-calculator)#012#012Stack trace of thread 9358:#012#0 0x7f30287bccf9 __GI___poll (libc.so.6)#012#1 0x7f302ace95c9 n/a (libglib-2.0.so.0)#012#2 0x7f302ace96dc g_main_context_iteration (libglib-2.0.so.0)#012#3 0x7f30173bc36d n/a (libdconfsettings.so)#012#4 0x7f302ad11175 n/a (libglib-2.0.so.0)#012#5 0x7f302821e6db start_thread (libpthread.so.0)#012#6 0x7f30287c9a3f __clone (libc.so.6)#012#012Stack trace of thread 9356:#012#0 0x7f30287bccf9 __GI___poll (libc.so.6)#012#1 0x7f302ace95c9 n/a (libglib-2.0.so.0)#012#2 0x7f302ace96dc g_main_context_iteration (libglib-2.0.so.0)#012#3 0x7f302ace9721 n/a (libglib-2.0.so.0)#012#4 0x7f302ad11175 n/a (libglib-2.0.so.0)#012#5 0x7f302821e6db start_thread (libpthread.so.0)#012#6 0x7f30287c9a3f __clone (libc.so.6)#012#012Stack trace of thread 9357:#012#0 0x7f30287bccf9 __GI___poll (libc.so.6)#012#1 0x7f302ace95c9 n/a (libglib-2.0.so.0)#012#2 0x7f302ace9962 g_main_loop_run (libglib-2.0.so.0)#012#3 0x7f3029955276 n/a (libgio-2.0.so.0)#012#4 0x7f302ad11175 n/a (libglib-2.0.so.0)#012#5 0x7f302821e6db start_thread (libpthread.so.0)#012#6 0x7f30287c9a3f __clone (libc.so.6) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in GNOME Shell: Unknown Status in The Ubuntu Power Consumption Project: Confirmed Status in gnome-shell package in Ubuntu: Opinion Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1766503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766503] Re: ibus-* randomly use high CPU
Hi, I'm using Mint 19.2 , I noticed if I do CTRL-z ( undo ) either in xed or gnome-calc , this will trigger high usage in ibus-daemon, ibus-x11 and xed However, in pluma it does not . After some seconds the CPU goes down . I noticed it in the CPU monitor applet . 100% reproductible . xed is 2.2.3+tina gnome-calculator is 1:3.28.2 ~ubuntu 18.04.3 ibus is 1.5.17-3ubuntu5.3 pluma is 1.20.1-3ubuntu1 lsb_release -a No LSB modules are available. Distributor ID: LinuxMint Description:Linux Mint 19.2 Tina Release:19.2 Codename: tina uname -a Linux valyelitebook 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Hope it helps, it's really frustrating , and I think it affects more applications ( Idea IDE and Android Studio also have strange behaviours - they did not on 18.x ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in GNOME Shell: Unknown Status in The Ubuntu Power Consumption Project: Confirmed Status in gnome-shell package in Ubuntu: Opinion Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1766503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
