[Bug 2056356] [NEW] Screen blank with only curson - Ubuntu 20.04.6 + Intel + X1 Carbon Gen11
Public bug reported: It seems an intel video driver update is needed to get Ubuntu 20.04.6 working on the Lenovo X1 Carbon Gen 11. On boot, only a blank screen appears with a blinking cursor. Here are some details: # lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 # apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.99.917+git20200226-1 Candidate: 2:2.99.917+git20200226-1 uname -a Linux hostname 5.15.0-97-generic #107~20.04.1-Ubuntu SMP Fri Feb 9 14:20:11 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux lshw -C video *-display UNCLAIMED description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 04 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list configuration: latency=0 resources: iomemory:600-5ff iomemory:400-3ff memory:603d00-603dff memory:40-400fff ioport:2000(size=64) memory:c-d memory:401000-4016ff memory:402000-40 # Xorg -configure X.Org X Server 1.20.13 X Protocol Version 11, Revision 0 Build Operating System: linux Ubuntu Current Operating System: Linux hostname 5.15.0-97-generic #107~20.04.1-Ubuntu SMP Fri Feb 9 14:20:11 UTC 2024 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-5.15.0-97-generic root=/dev/mapper/ub2004-root_vol ro i915.enable_psr=0 pci=noaer quiet splash vt.handoff=7 Build Date: 29 January 2024 12:44:21PM xorg-server 2:1.20.13-1ubuntu1~20.04.15 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 17:03:45 2024 List of video drivers: amdgpu ati intel nouveau qxl radeon vmware modesetting fbdev vesa (++) Using config file: "/root/xorg.conf.new" (==) Using system config directory "/usr/share/X11/xorg.conf.d" modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.15.0-97-generic intel: waited 2020 ms for i915.ko driver to load Number of created screens does not match number of detected devices. Configuration failed. (EE) Server terminated with error (2). Closing log file. Of particular note is this portion of the prior command: modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.15.0-97-generic intel: waited 2020 ms for i915.ko driver to load Additionally, here are some errors and warnings from a log file: /var/lib/gdm3/.local/share/xorg# grep "EE\|WW" Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [63.123] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [63.123] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [63.123] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [63.123] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [63.123] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [63.131] (WW) Falling back to old probe method for modesetting [63.131] (EE) open /dev/fb0: Permission denied [63.131] (WW) Falling back to old probe method for fbdev [63.132] (EE) open /dev/fb0: Permission denied [63.132] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [63.132] (EE) Screen 0 deleted because of no matching config section. [63.132] (EE) Screen 1 deleted because of no matching config section. [63.132] (EE) [63.132] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices [63.132] (EE) [63.132] (EE) [63.132] (EE) Please also check the log file at "/var/lib/gdm3/.local/share/xorg/Xorg.0.log" for additional information. [63.132] (EE) [63.136] (EE) Server terminated with error (1). Closing log file. # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 12 On-line CPU(s) list:0-11 Thread(s) per core: 1 Core(s) per socket: 10 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 186 Model name: 13th Gen Intel(R) Core(TM) i7-1355U Stepping: 3 CPU MHz:
[Bug 1971209] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.147-0ub
Public bug reported: package nvidia-390 (not installed) failed to install/upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18 Uname: Linux 4.15.0-176-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 Date: Tue May 3 02:28:55 2022 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.147-0ubuntu0.18.04.1 InstallationDate: Installed on 2022-05-02 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.147-0ubuntu0.18.04.1 UpgradeStatus: Upgraded to bionic on 2022-05-02 (0 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971209 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.147-0ubuntu0.18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1971209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971210] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.147-0ub
Public bug reported: package nvidia-390 (not installed) failed to install/upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18 Uname: Linux 4.15.0-176-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 Date: Tue May 3 02:28:55 2022 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.147-0ubuntu0.18.04.1 InstallationDate: Installed on 2022-05-02 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.147-0ubuntu0.18.04.1 UpgradeStatus: Upgraded to bionic on 2022-05-02 (0 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971210 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.147-0ubuntu0.18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1971210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971000] [NEW] EC keys do not provide OSSL_PKEY_PARAM_MANDATORY_DIGEST
Public bug reported: $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy tpm2-openssl tpm2-openssl: Installed: 1.0.1-1 Candidate: 1.0.1-1 Version table: *** 1.0.1-1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Please see: https://github.com/tpm2-software/tpm2-openssl/issues/34 Essentially, any mandatory digest in a public key is ignored by tpm2-openssl. ** Affects: tpm2-openssl (Ubuntu) Importance: Undecided Status: New ** Summary changed: - xxx + EC keys do not provide OSSL_PKEY_PARAM_MANDATORY_DIGEST -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971000 Title: EC keys do not provide OSSL_PKEY_PARAM_MANDATORY_DIGEST To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-openssl/+bug/1971000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970999] [NEW] Cannot load certificate stored in NVM
Public bug reported: $ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 $ apt-cache policy tpm2-openssl tpm2-openssl: Installed: 1.0.1-1 Candidate: 1.0.1-1 Version table: *** 1.0.1-1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Please see https://github.com/tpm2-software/tpm2-openssl/issues/35. ** Affects: tpm2-openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970999 Title: Cannot load certificate stored in NVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-openssl/+bug/1970999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1970749] Re: Ubuntu upgrade to 22 stops do to package named ubuntu-desktop
Thanks for the reply. Had to use Synaptic package manager but I got it removed and upgraded to Jammy. Have a great day! On Thu, Apr 28, 2022 at 9:40 AM Nick Rosbrook <1970...@bugs.launchpad.net> wrote: > Looking at the attached VarLogDistupgradeAptlog.txt, the upgrade is > failing on a broken 'libwacom-surface' package. This package is not in > the Ubuntu archive, and appears to come from > pkg.surfacelinux.com/debian. > > Please try using the tool ppa-purge to remove the PPA, and then try the > upgrade again. > > ** Summary changed: > > - Ubuntu upgrade to 22 stops do to package named unbuntu-desktop > + Ubuntu upgrade to 22 stops do to package named ubuntu-desktop > > ** Changed in: ubuntu-release-upgrader (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1970749 > > Title: > Ubuntu upgrade to 22 stops do to package named ubuntu-desktop > > Status in ubuntu-release-upgrader package in Ubuntu: > Incomplete > > Bug description: > 2022-04-28 07:27:54,368 DEBUG Marking 'ubuntu-desktop' for upgrade > 2022-04-28 07:27:54,632 WARNING Can't mark 'ubuntu-desktop' for upgrade > (E:Unable to correct problems, you have held broken packages.) > > ProblemType: Bug > DistroRelease: Ubuntu 21.10 > Package: ubuntu-release-upgrader-core 1:21.10.9 > Uname: Linux 5.16.17-surface x86_64 > ApportVersion: 2.20.11-0ubuntu71.1 > Architecture: amd64 > CasperMD5CheckResult: unknown > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > Date: Thu Apr 28 07:28:45 2022 > InstallationDate: Installed on 2022-04-03 (24 days ago) > InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 > (20220223) > PackageArchitecture: all > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: ubuntu-release-upgrader > UpgradeStatus: Upgraded to impish on 2022-04-28 (0 days ago) > VarLogDistupgradeTermlog: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1970749/+subscriptions > > -- Regards, Jim O'Neil oneil@gmail.com 612-802-1984 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970749 Title: Ubuntu upgrade to 22 stops do to package named ubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1970749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970749] [NEW] Ubuntu upgrade to 22 stops do to package named unbuntu-desktop
Public bug reported: 2022-04-28 07:27:54,368 DEBUG Marking 'ubuntu-desktop' for upgrade 2022-04-28 07:27:54,632 WARNING Can't mark 'ubuntu-desktop' for upgrade (E:Unable to correct problems, you have held broken packages.) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.9 Uname: Linux 5.16.17-surface x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 07:28:45 2022 InstallationDate: Installed on 2022-04-03 (24 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to impish on 2022-04-28 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade impish third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970749 Title: Ubuntu upgrade to 22 stops do to package named unbuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1970749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930880] Re: Booting Ubuntu 21.04 from DVD takes more than 30 minutes and its environment are corrupted
I was able to get this to work using the workaround "fsck.mode=skip" with the 22.04 desktop DVD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930880 Title: Booting Ubuntu 21.04 from DVD takes more than 30 minutes and its environment are corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1930880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 29622]
and btw, the page prints to 0.25" margins unfortunately despite 0.5 setting in file, page setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/29622 Title: Many web browsers not print the headers and footers. To manage notifications about this bug go to: https://bugs.launchpad.net/bugzilla/+bug/29622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 29622]
I have these problems. I was going to put in a bug report (found this one) "not using 0.5 print margins, multipage large table overwriting print headers and footers". it's set with fit-to-page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/29622 Title: Many web browsers not print the headers and footers. To manage notifications about this bug go to: https://bugs.launchpad.net/bugzilla/+bug/29622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967936] [NEW] Boot errors
Public bug reported: I'm seeing many acpi errors on boot up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 664:1000:124:0:2022-04-03 11:05:22.480003508 -0400:2022-04-03 11:05:22.480003508 -0400:/var/crash/_usr_libexec_gnome-shell-portal-helper.1000.upload 640:1000:124:6640217:2022-04-03 11:05:21.380003452 -0400:2022-04-03 11:05:22.488003509 -0400:/var/crash/_usr_libexec_gnome-shell-portal-helper.1000.crash 600:117:124:37:2022-04-03 11:06:17.586441333 -0400:2022-04-03 11:06:17.586441333 -0400:/var/crash/_usr_libexec_gnome-shell-portal-helper.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:16:14 2022 InstallationDate: Installed on 2022-04-03 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967936 Title: Boot errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1967936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966084] Re: Nautilus file/folder highlight color won't follow accent color change until restart the file manager
** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966084 Title: Nautilus file/folder highlight color won't follow accent color change until restart the file manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1966084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966084] [NEW] Nautilus file/folder highlight color won't follow accent color change until restart the file manager
Public bug reported: Thanks for the new accent color option under 'Appearance' settings page. However, the text background of highlighted file or folder in file manager does not follow the accent color change, until restart Nautilus (via nautilus -q). How to Reproduce: 1. Open 'Files' and select a file or folder. 2. Open 'Settings' and select another color under 'Appearance' settings page. 3. The background of filename or folder name still use the previous color. 1) Ubuntu version: Ubuntu 22.04 development branch. 2) Software version: gnome-control-center 1:41.4-1ubuntu8 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966084 Title: Nautilus file/folder highlight color won't follow accent color change until restart the file manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1966084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965622] Re: Gnome Shell color sticks to Light mode after selected non-default accent color
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965622 Title: Gnome Shell color sticks to Light mode after selected non-default accent color To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965622] [NEW] Gnome Shell color sticks to Light mode after selected non-default accent color
Public bug reported: 1.) Ubuntu version: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2.) Gnome Control Center version: 1:41.4-1ubuntu6 3.) Expected behavior: Switch Light and Dark in 'Appearance' page change full system colors: app window color and Gnome Shell color (colors of system menu, app icon context menu, etc). 4.) What happened instead: But, after changed accent color from orange to another, system menu, app icon context menu, etc (except desktop & nautilus' context menu) always have Light color. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 10:20:50 2022 InstallationDate: Installed on 2022-03-06 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965622 Title: Gnome Shell color sticks to Light mode after selected non-default accent color To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962596] [NEW] package grub-efi-amd64-signed 1.167~16.04.6+2.04-1ubuntu44.1.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: appears when updating ProblemType: Package DistroRelease: Ubuntu 16.04 Package: grub-efi-amd64-signed 1.167~16.04.6+2.04-1ubuntu44.1.2 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Mon Feb 28 16:54:55 2022 DpkgHistoryLog: Start-Date: 2022-02-28 16:54:35 Commandline: aptdaemon role='role-commit-packages' sender=':1.82' Upgrade: ubuntu-advantage-tools:amd64 (27.5~16.04.1, 27.6~16.04.1), google-chrome-stable:amd64 (97.0.4692.99-1, 98.0.4758.102-1), opera-stable:amd64 (83.0.4254.19, 84.0.4316.21) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-22 (2138 days ago) InstallationMedia: RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.167~16.04.6+2.04-1ubuntu44.1.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962596 Title: package grub-efi-amd64-signed 1.167~16.04.6+2.04-1ubuntu44.1.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1962596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962549] [NEW] openssl cms -decrypt doesn't work properly when using an engine
Public bug reported: I'm using: bsci@ip-10-132-42-225:~/test$ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 bsci@ip-10-132-42-225:~/test$ apt-cache policy openssl openssl: Installed: 1.1.1f-1ubuntu2.10 Candidate: 1.1.1f-1ubuntu2.10 Version table: *** 1.1.1f-1ubuntu2.10 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.1f-1ubuntu2.8 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1.1.1f-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages I have a private EC key held in a TPM 2.0 platform hierarchy. I'm encrypting a message like this: openssl cms -encrypt -in message.txt -out message.cipher transport.pem Here, transport.pem is the cert. for the EC key held in the TPM. I'm attempting to decrypt like this: openssl cms -decrypt -in message.cipher -out /dev/stdout -inkey 0x8181 -keyform engine -engine tpm2tss -recip transport.pem Instead of seeing the original message text, I'm getting the following error: engine "tpm2tss" set. Error decrypting CMS using private key 139626757388096:error:1010107D:elliptic curve routines:ecdh_simple_compute_key:missing private key:../crypto/ec/ecdh_ossl.c:61: It seems that the code is expecting the actual private key instead of using the key held in the TPM? ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962549 Title: openssl cms -decrypt doesn't work properly when using an engine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1962549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962231] [NEW] systemd generator fails with more than one config
Public bug reported: The systemd generator for openvpn (filesystem: /lib/systemd/system- generators/openvpn-generator; git: openvpn/debian/openvpn-generator) does not seem to work correctly with multiple configurations. When run a second time the symlinks exist and the generator fails on the first config and does not make it through the loop of all configs. This means if a config is added later and glob sorts after the first config it will never be linked. I believe the ln -s invocation should be ln -sf root@host:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Codename: focal dir=/tmp/tmp.JmcFdf9b6s # First run succeeds: root@host:~# SYSTEMD_LOG_LEVEL=debug sh -x /lib/systemd/system-generators/openvpn-generator "$dir" "$dir" "$dir" + set -eu + GENDIR=/tmp/tmp.JmcFdf9b6s + WANTDIR=/tmp/tmp.JmcFdf9b6s/openvpn.service.wants + SERVICEFILE=/lib/systemd/system/openvpn@.service + AUTOSTART=all + CONFIG_DIR=/etc/openvpn + mkdir -p /tmp/tmp.JmcFdf9b6s/openvpn.service.wants + test -e /etc/default/openvpn + . /etc/default/openvpn ++ OPTARGS= ++ OMIT_SENDSIGS=0 ++ AUTOSTART=all + test xall = xnone + test xall = xall -o -z all ++ cd /etc/openvpn ++ ls network-one.conf network-two.conf + for CONFIG in `cd $CONFIG_DIR; ls *.conf 2> /dev/null` + NAME=network-one + ln -s /lib/systemd/system/openvpn@.service /tmp/tmp.JmcFdf9b6s/openvpn.service.wants/openvpn@network-one.service + for CONFIG in `cd $CONFIG_DIR; ls *.conf 2> /dev/null` + NAME=network-two + ln -s /lib/systemd/system/openvpn@.service /tmp/tmp.JmcFdf9b6s/openvpn.service.wants/openvpn@network-two.service + exit 0 # Second run fails: root@host:~# SYSTEMD_LOG_LEVEL=debug sh -x /lib/systemd/system-generators/openvpn-generator "$dir" "$dir" "$dir" + set -eu + GENDIR=/tmp/tmp.JmcFdf9b6s + WANTDIR=/tmp/tmp.JmcFdf9b6s/openvpn.service.wants + SERVICEFILE=/lib/systemd/system/openvpn@.service + AUTOSTART=all + CONFIG_DIR=/etc/openvpn + mkdir -p /tmp/tmp.JmcFdf9b6s/openvpn.service.wants + test -e /etc/default/openvpn + . /etc/default/openvpn ++ OPTARGS= ++ OMIT_SENDSIGS=0 ++ AUTOSTART=all + test xall = xnone + test xall = xall -o -z all ++ cd /etc/openvpn ++ ls network-one.conf network-two.conf + for CONFIG in `cd $CONFIG_DIR; ls *.conf 2> /dev/null` + NAME=network-one + ln -s /lib/systemd/system/openvpn@.service /tmp/tmp.JmcFdf9b6s/openvpn.service.wants/openvpn@network-one.service ln: failed to create symbolic link '/tmp/tmp.JmcFdf9b6s/openvpn.service.wants/openvpn@network-one.service': File exists ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962231 Title: systemd generator fails with more than one config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1962231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961530] [NEW] CUPS driver does not send anything to printer during test print
Public bug reported: Downloaded and installed Turboprint driver for Canon iP90 but balked at the high ($55 USD) price. The 30 day free trial ended and I found that the iP90 printer would operate after installing the iP110 driver (with the iP90-Cups or the iP90-Gutenprint drivers, it would only output 25 or so blank pages with faint printing at the top of the page). Canon didn't make a Linux driver for the iP90 printer that I can find. Today, tried to uninstall Turboprint but it seems to be all over my printer config setup. As part of that, I uninstalled the 'working' iP110 driver setup. Deleted it from the printer window. Now when I install the CUPS generic iP110 driver, and try to print a test page, it does nothing. Doesn't even wink the printers activity light and doesn't show the print job in the print queue. So it seems that Turboprint insinuated itself into the system in a way that prevents it's total removal and is somehow blocking the CUPS drivers. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: cups 2.3.3op2-7ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Feb 20 10:26:57 2022 Lpstat: device for Canon-iP90: usb://Canon/iP90?serial=31A4B2 MachineType: Gigabyte Technology Co., Ltd. A520M S2H Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-iP90.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-iP90.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=c201ceca-9f5a-4845-b650-e68fc9d5230f ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to impish on 2021-10-15 (128 days ago) dmi.bios.date: 07/27/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: A520M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnA520MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA520MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: A520 MB dmi.product.name: A520M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961530 Title: CUPS driver does not send anything to printer during test print To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1961530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951314] Re: [BPO] Please backport tpm2-tss-engine 1.1.0-2 (universe) from jammy
Having this functionality in Focal would be an asset to our organization too. We maintain a local compilation of a different OpenSSL TPM engine. Having _any_ OpenSSL TPM engine as part of Focal would eliminate the use of this local build and maintenance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951314 Title: [BPO] Please backport tpm2-tss-engine 1.1.0-2 (universe) from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tss-engine/+bug/1951314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953379] [NEW] terminal terminates on large select all
Public bug reported: Description:Ubuntu 20.04.3 LTS Release:20.04 Repo: 1. Open a new terminal and turn on menu bar 2. Turn off scrollback limit in Preferences 3. Run a command that produces a lot of output. For example, enable 'locate' command, and use it to produce thousands of lines with something like 'locate a' 4. Go to Edit, Select All Result: terminal process will end and terminal disappears; seems to crash on out of memory Expected: Select All works, or, a popup with an error such as "Select All requires 19 GiB, but memory is insufficient." Note: I have VMWare installed; not sure if VMWare clipboard crashes, or if it is the terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 6 12:29:45 2021 InstallationDate: Installed on 2020-11-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953379 Title: terminal terminates on large select all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1953379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
I can reproduce this with sudo mount -t cifs -o noauto,rw,uid=1000,gid=1000,guest,nounix,noserverino,file_mode=0660,dir_mode=0755,iocharset=utf8,vers=2.1 //192.168.1.1/backup/ /media/grumpy/brick followed by running nautilus The network drive is a USB hard disk attached to my router. It's formatted to NTFS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951075] [NEW] Nautilus doesn't load and gives GVFS-WARNING
Public bug reported: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer-to- peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939959] Re: liferea sometimes displays images too large
Upgraded to Ubuntu 21.10 yesterday and noticed today that the issue with the overly large images is not happening anymore. Working ok with or without the above mentioned change to .config/liferea/liferea.css (BTW if I modify that change with 'max-width: 50%' the image width does shrink in half) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939959 Title: liferea sometimes displays images too large To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1939959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939725] Re: neverball chase camera with gamepad
Gave this a quick try on Ubuntu 21.10 (in a VirtualBox VM), and the bug still exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939725 Title: neverball chase camera with gamepad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neverball/+bug/1939725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940079] Re: Strongswan doesn't support TPM 2.0 through the TSS2 interface
On my Focal ipsec client machine, I added the following PPA: deb http://archive.ubuntu.com/ubuntu/ focal-proposed restricted main multiverse universe I installed various strongswan packages: charon-systemd/focal-proposed,now 5.8.2-1ubuntu3.2 amd64 [installed] libstrongswan-extra-plugins/focal-proposed,now 5.8.2-1ubuntu3.2 amd64 [installed] libstrongswan-standard-plugins/focal-proposed,now 5.8.2-1ubuntu3.2 amd64 [installed] libstrongswan/focal-proposed,now 5.8.2-1ubuntu3.2 amd64 [installed,automatic] strongswan-libcharon/focal-proposed,now 5.8.2-1ubuntu3.2 amd64 [installed,automatic] strongswan-pki/focal-proposed,now 5.8.2-1ubuntu3.2 amd64 [installed] strongswan-swanctl/focal-proposed,now 5.8.2-1ubuntu3.2 amd64 [installed,automatic] I can confirm the ability to read TPM NVRAM keys and certificates successfully using the pki tool. I am also able to confirm successfully being able to complete an ipsec connection from my client machine via those same TPM-based credentials to my ipsec server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940079 Title: Strongswan doesn't support TPM 2.0 through the TSS2 interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1940079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940079] Re: Strongswan doesn't support TPM 2.0 through the TSS2 interface
Hi Paride, I added your Focal PPA and installed the various strongswan packages on my client machine: strongswan, strongswan-swanctl, libstrongswan-extra- plugins, libstrongswan-standard-plugins, and strongswan-pki. I am able to confirm the ability to read TPM nvram keys and certificates successfully using the pki tool. I am also able to confirm successfully being able to complete an ipsec connection from my client machine via those same TPM-based credentials. Thumbs up from me! Jim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940079 Title: Strongswan doesn't support TPM 2.0 through the TSS2 interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1940079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940079] Re: Strongswan doesn't support TPM 2.0 through the TSS2 interface
Paride, Thank you for all your diligence. I will try to provide focal testing results by early next week. Jim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940079 Title: Strongswan doesn't support TPM 2.0 through the TSS2 interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1940079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943166] Re: Diodon doesn't display clips until after reboot
I had 66 items in Diodon so figured this was a good time to test the task bar Diodon app and sure enough, it cleared, but leaves a blank drop down and any new copies don't show up in the drop down list. So then I right clicked on the task bar icon...no way to 'Quit'. So then I went to Mates drop down menu, clicked on Diodon, and then quit. Restarted it, and it's working fine. AND I tested it from Mate's menu and it's working fine there too...saves and displays any new copies. So it's only the Diodon in the task bar that causes trouble and calling it up from the menu is the work around. I tried to do that debug but it shows as empty. Doesn't show anything except a black box for a cursor. Are you sure that's how it's written into Linux format in Term? Doesn't look right to me but I'm no expert. I would prefer if all Diodon's functions worked from the task bar, but at least now with the work around, I don't need to reboot. So thanks for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943166 Title: Diodon doesn't display clips until after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/diodon/+bug/1943166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943166] Re: Diodon doesn't display clips until after reboot
I will do that but it'll take a while because the bug doesn't show up until there's near or beyond the 100 links I have it set for. Dunno exactly how many. BTW, this bug is persistent as it's been there since I installed Diodon a year or so ago? Long time ago anyway. And I do the upgrades to Mate and to Ubuntu as they come along. If upgrades to Diodon are occasionally released as part of those upgrades, then I've upgraded it too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943166 Title: Diodon doesn't display clips until after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/diodon/+bug/1943166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943166] [NEW] Diodon doesn't display clips until after reboot
Public bug reported: When using the 'Clear' feature of Diodon when there are nearly 100 'saves': The Diodon saved area is cleared but does not show any new copies until reboot. Then it does show all the items a user has used CTRL+C for since after the 'Clear'. Ubuntu 21.04 LTS diodon: Installed: 1.11.1~ubuntu20.04.1 Candidate: 1.11.1~ubuntu20.04.1 Version table: *** 1.11.1~ubuntu20.04.1 100 100 /var/lib/dpkg/status 1.11.0-1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages Expected: That Diodon would successfully 'Clear' all those older copied items AND accept any new CTRL+C's in the same session and display them in the Diodon dropdown. What happened instead: After one or multiple CTRL+C's, the Diodon drop down box is empty. Have to reboot computer for them to show up. All the missing copies are there, but only after reboot. ** Affects: diodon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943166 Title: Diodon doesn't display clips until after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diodon/+bug/1943166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866619] Re: OverflowError when machine suspends and resumes after a longer while
I manually applied this and it worked fine, thanks. It is worth noting that the upstream package has been archived [1]: From [1]: DSTAT development has been terminated Due to actions taken by RedHat to hijack the DSTAT name, further development of this project has ceased. Development of this project is taking place on the Dool fork [2]. So long and thanks for all the fish [1] https://github.com/dstat-real/dstat [2] https://github.com/scottchiefbaker/dool -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866619 Title: OverflowError when machine suspends and resumes after a longer while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dstat/+bug/1866619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940079] Re: Strongswan in Focal doesn't support TPM 2.0 through the TSS2 interface...
I need to jump into this one... Right now, a number of our projects are dependent on the Focal LTS release. These projects cannot wait for 22.04 as they will go to market over the course of the next several months. These same projects make heavy use of TPM 2.0. They do use the TSS 2.0 components which _are currently_ available in Focal. Strongswan has had TSS 2.0 support for quite awhile, and Strongswan is key to making our projects successful. I can say that I've put the --enable-tss-tss2 into our local Focal build and have been successfully running Strongswan with TSS 2.0 support. I'm uncomfortable with having a local build as it's just another entity to remember to manage across the lifetime of our products. This functionality needs to be put into Focal. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940079 Title: Strongswan in Focal doesn't support TPM 2.0 through the TSS2 interface... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1940079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940079] Re: Strongswan in Focal doesn't support TPM 2.0 through TSS2 interface...
** Summary changed: - Strongswan in Focal doesn't support TPM 2.0... + Strongswan in Focal doesn't support TPM 2.0 through TSS2 interface... ** Description changed: The Strongswan 5.8.2 (5.8.2-1ubuntu3) for Focal configuration elides the - --enable-tss-tss2 option. Without this option, TPM 2.0 is effectively - unavailable. + --enable-tss-tss2 option. Without this option, TPM 2.0 is unavailable + through the TSS2 interface. ** Summary changed: - Strongswan in Focal doesn't support TPM 2.0 through TSS2 interface... + Strongswan in Focal doesn't support TPM 2.0 through the TSS2 interface... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940079 Title: Strongswan in Focal doesn't support TPM 2.0 through the TSS2 interface... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1940079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940079] [NEW] Strongswan in Focal doesn't support TPM 2.0...
Public bug reported: The Strongswan 5.8.2 (5.8.2-1ubuntu3) for Focal configuration elides the --enable-tss-tss2 option. Without this option, TPM 2.0 is effectively unavailable. ** Affects: strongswan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940079 Title: Strongswan in Focal doesn't support TPM 2.0... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1940079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939959] Re: liferea sometimes displays images too large
Is there a way I can try out 1.13.5-2 on Ubuntu 21.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939959 Title: liferea sometimes displays images too large To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1939959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939959] [NEW] liferea sometimes displays images too large
Public bug reported:
When viewing feeds that have large images, the images are not scaled
down to fit into the window like browsers typically do.
To reproduce:
- add feed like https://www.monkeyuser.com/feed.xml that has lots of large
images
- make sure your liferea window isn't too wide (width of about 1000px should be
good)
- view most any item in that feed (I was using the one dated Aug 2)
- see that the image extends beyond the content pane thus adding a horizontal
scroll bar
I expected that the image width to be scaled to fit into current content
pane. This was happening in a earlier version (Ubuntu 20.10 I believe)
I tried an old workaround from
https://www.keypressure.com/blog/shrink-liferea-images/ that said to add the
following to ~/.config/liferea/liferea.css
div.content img {
max-width: 100%;
height: auto;
}
That did not work.
I also tried adding the --debug-html to liferea to have it save the
generated html in ~/.cache/liferea/output.html and then viewed that in a
web browser (firefox). The image was scaled as expected there (with or
without the above mentioned liferea.css change). Furthermore, changing
the max-with to something like 50% the browser showed the change when
viewing the output.html file, but liferea always just displayed the
image at full size.
Description:Ubuntu 21.04
Release:21.04
liferea1.13.5-1
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: liferea 1.13.5-1
ProcVersionSignature: Ubuntu
5.11.0-7620.21~1626191760~21.04~55de9c3~dev-generic 5.11.21
Uname: Linux 5.11.0-7620-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sat Aug 14 14:41:50 2021
SourcePackage: liferea
UpgradeStatus: Upgraded to hirsute on 2021-06-22 (53 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2015-11-30T17:42:30.112000
** Affects: liferea (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939959
Title:
liferea sometimes displays images too large
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1939959/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938626] Re: PPS API broken
I have verified the kernel pps_api only looks at CD by building a patch cable to map the PPS signal into the CD pin and now all the pps_api calls work as expected. It is still my position that the kernel pps_api should look at all commonly used control lines for PPS just like the pps-tools package does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938626 Title: PPS API broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939858] [NEW] Bluetooth not working
Public bug reported: Bluetooth was working but not connecting to speaker but said it was connected. Then today bluetooth not working at all. Description:Ubuntu 20.04.2 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jim1526 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 13 00:51:32 2021 InstallationDate: Installed on 2020-05-25 (444 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X712FA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X712FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX712FA.308:bd06/03/2019:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX712FA_X712FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX712FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X712FA_X712FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939858 Title: Bluetooth not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1939858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939725] [NEW] neverball chase camera with gamepad
Public bug reported: I recently noticed a change in behavior in neverball (Ubuntu 21.04) from what it was last year or so (circa 19.10 and/or 20.04) the joystick/gamepad doesn't work like it use to. When using the joystick and setting camera mode to chase (I see the same behavior with lazy) everything looks ok until using the joystick to manually move the camera. Once that happens, it is like chase mode gets disabled (i.e. it acts like manual). Even changing the camera mode to something else and back to chase doesn't correct the issue. This does not happen if doing the same thing (manually moving camera angle while in chase or lazy mode) with keyboard or mouse. After moving the camera angle on the joystick, if I then move the camera angle via keyboard or mouse, then chase mode will start working again. I also noticed that sometimes, when doing the camera angle change via the keyboard (after doing so via joystick), it'll keep turning after releasing the key until the other direction key is pressed. I tried unplugging the joystick and plugging it back it, but that didn't change anything. Nor did rebooting. I installed Ubuntu 20.04 in a VirtualBox VM and installed the neverball package. It worked as expected there using the same gamepad/joystick. Description: Ubuntu 21.04 Release: 21.04 neverball: Installed: 1.6.0+git20180603-3 Candidate: 1.6.0+git20180603-3 Version table: *** 1.6.0+git20180603-3 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 100 /var/lib/dpkg/status Bus 001 Device 013: ID 046d:c216 Logitech, Inc. F310 Gamepad [DirectInput Mode] ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: neverball 1.6.0+git20180603-3 ProcVersionSignature: Ubuntu 5.11.0-7620.21~1626191760~21.04~55de9c3~dev-generic 5.11.21 Uname: Linux 5.11.0-7620-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Aug 12 12:36:02 2021 SourcePackage: neverball UpgradeStatus: Upgraded to hirsute on 2021-06-22 (51 days ago) 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: 2015-11-30T17:42:30.112000 ** Affects: neverball (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939725 Title: neverball chase camera with gamepad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neverball/+bug/1939725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938626] Re: PPS API broken
According to linux/drivers/pps/clients/Kconfig config PPS_CLIENT_LDISC tristate "PPS line discipline" depends on TTY help If you say yes here you get support for a PPS source connected with the CD (Carrier Detect) pin of your serial port. If this is true, CTS needs to be added for modern devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938626 Title: PPS API broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938626] Re: PPS API broken
A possible cause for this bug has occurred to me, but I wouldn't know where in the kernel code to check for this. Note: When I talk about a control line, I am using the DTE, i.e computer, end connector reference. In years past there was no standardization for which line on a serial port carried the PPS signal for a GPS and it was a mix of DCD, RTS, and occasionally CTS. Current commercial devices, such as the one I have, seem to mostly use CTS. Is is possible the current kernel code is not looking at ALL those lines for PPS? This would also explain why you have not gotten lots of bug reports as very few people would be running such a device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938626 Title: PPS API broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938626] Re: PPS API broken
I have rebooted with the oldest installed kernel, 5.4.0-54, and it too has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938626 Title: PPS API broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1938626] Re: PPS API broken
I had been running with a USB GPS for years and recently purchased a GOOD GNSS device, so I have not had anything on this machine that accesses the pps_api until a few days ago. FYI I have a Raspberry Pi with Ubuntu where the pps_api works with raspberrypi-kernel 1:1.2010727-1 if that is of any help. I see two other kernels installed: 5.4.0-54 and 5.4.0-77. Any suggestion on which to try as it is somewhat of a PITA to do this, would rather do it just once, and will have to schedule a time, hopefully in a day or so. Also I have had no reason to do this for years and have forgotten how. As I recall, it is just hold down a key while rebooting to get to the menu to select a kernel, but don't remember which key. On Wednesday, August 4, 2021, 6:30:46 AM PDT, Kleber Sacilotto de Souza <1938...@bugs.launchpad.net> wrote: Hello Jim, Did it work before with your system and got broken after a kernel update? If yes, would you be able to identify the kernel version which was working before? If you didn't run this use case before, would you be able to boot with an older kernel version and check whether it works? Thanks. ** Also affects: linux (Ubuntu Focal)  Importance: Undecided    Status: New -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1938626 Title:  PPS API broken Status in linux package in Ubuntu:  New Status in linux source package in Focal:  New Bug description:  The kernel PPS API appears to be broken. I have a serial GPS with PPS  attached to /dev/ttyS4. If I use gpsd to create /dev/pps0, gpsd fails  to see PPS data. If I disable gpsd and create /dev/pps0 with ldattach,  any app or tool run against ttyS4 works fine and does see the CTS  transitions every second, i.e. gpsmon and ppscheck. Anything run  against pps0 fails, i.e. ppstest, ppswatch. ntpd gets data from ttyS4  but not pps0.  There are some issues with stock apparmor with gpsd and ntpd, but I  have solved those.  ProblemType: Bug  DistroRelease: Ubuntu 20.04  Package: linux-image-5.4.0-80-generic 5.4.0-80.90  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124  Uname: Linux 5.4.0-80-generic x86_64  ApportVersion: 2.20.11-0ubuntu27.18  Architecture: amd64  AudioDevicesInUse:  USER    PID ACCESS COMMAND  /dev/snd/controlC1: jimp   6811 F pulseaudio  CasperMD5CheckResult: skip  CurrentDesktop: GNOME-Flashback:GNOME  Date: Sat Jul 31 16:41:32 2021  HibernationDevice: RESUME=UUID=90289c8f-5a00-46c4-8f1f-79dd26128f39  InstallationDate: Installed on 2016-08-05 (1820 days ago)  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)  ProcEnviron:  TERM=xterm-256color  PATH=(custom, no user)  XDG_RUNTIME_DIR=  LANG=en_US.UTF-8  SHELL=/bin/bash  ProcFB: 0 i915drmfb  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=389dcb0d-84f2-4340-ad6c-e4f1dbe55b67 ro quiet splash vt.handoff=7  RelatedPackageVersions:  linux-restricted-modules-5.4.0-80-generic N/A  linux-backports-modules-5.4.0-80-generic N/A  linux-firmware              1.187.15  SourcePackage: linux  UpgradeStatus: Upgraded to focal on 2020-11-09 (264 days ago)  dmi.bios.date: 11/26/2009  dmi.bios.vendor: Intel Corp.  dmi.bios.version: TYG4110H.86A.0036.2009.1126.2047  dmi.board.asset.tag: To be filled by O.E.M.  dmi.board.name: DG41TY  dmi.board.vendor: Intel Corporation  dmi.board.version: AAE47335-302  dmi.chassis.type: 3  dmi.modalias: dmi:bvnIntelCorp.:bvrTYG4110H.86A.0036.2009.1126.2047:bd11/26/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41TY:rvrAAE47335-302:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938626/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938626 Title: PPS API broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938626] [NEW] PPS API broken
Public bug reported: The kernel PPS API appears to be broken. I have a serial GPS with PPS attached to /dev/ttyS4. If I use gpsd to create /dev/pps0, gpsd fails to see PPS data. If I disable gpsd and create /dev/pps0 with ldattach, any app or tool run against ttyS4 works fine and does see the CTS transitions every second, i.e. gpsmon and ppscheck. Anything run against pps0 fails, i.e. ppstest, ppswatch. ntpd gets data from ttyS4 but not pps0. There are some issues with stock apparmor with gpsd and ntpd, but I have solved those. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-80-generic 5.4.0-80.90 ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 Uname: Linux 5.4.0-80-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jimp 6811 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Sat Jul 31 16:41:32 2021 HibernationDevice: RESUME=UUID=90289c8f-5a00-46c4-8f1f-79dd26128f39 InstallationDate: Installed on 2016-08-05 (1820 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=389dcb0d-84f2-4340-ad6c-e4f1dbe55b67 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-09 (264 days ago) dmi.bios.date: 11/26/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TYG4110H.86A.0036.2009.1126.2047 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41TY dmi.board.vendor: Intel Corporation dmi.board.version: AAE47335-302 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTYG4110H.86A.0036.2009.1126.2047:bd11/26/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41TY:rvrAAE47335-302:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938626 Title: PPS API broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934701] [NEW] external USB drive hangs and unable to recover without hard reset
Public bug reported: As also reported on the Raspberry Pi bug report: https://github.com/raspberrypi/linux/issues/3981 I'm experiencing this with all 5.x kernels usually within a day or 2 of a restart: Jun 29 20:20:35 tiny-myth kernel: [85834.433030] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jun 29 20:20:35 tiny-myth kernel: [85834.433052] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jun 29 20:20:35 tiny-myth kernel: [85834.565209] usb 9-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd Jun 29 20:21:06 tiny-myth kernel: [85865.665815] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jun 29 20:21:06 tiny-myth kernel: [85865.665838] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jun 29 20:21:06 tiny-myth kernel: [85865.805725] usb 9-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd I've rolled back to 4.19 kernel and error did occur once but appears to happen less frequently (running for a few days now and hasn't triggered). This is on a device that's been running fine since 2012 with none of these issues until I upgraded to 20.04 in January 2021, at which point I've had to reboot the device constantly to re-attach to storage. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934701 Title: external USB drive hangs and unable to recover without hard reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932205] [NEW] Canon iP90 Ptr outputs blank pgs in 20.04, works in Win10
Public bug reported: Ver: Ubuntu 20.04.2 LTS Expected: CUPS to print to an iP90 inkjet printer. What happens: Whenever I try to print anything to the iP90, it outputs ~14 blank pages with a ghostly thin line across the top of the page. It hesitates after drawing the sheet of paper into the machine so that's where it's printing that single line (or multiple lines but very tiny), and then spits out the page without printing anything else. That squished line on top is so small, and with the rest of the page blank, I reuse that paper when I leave Ubuntu and boot to Win10. Then I can print to the iP90 all day and the pages come out fine. What I've tried: I've loaded and deleted the CUPS driver for the iP90 numerous times to no avail. CUPS recognizes the USB printer is attached and it's name & model number. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jun 16 14:13:05 2021 Lpstat: device for Canon-iP90: usb://Canon/iP90?serial=31A4B2 device for Canon-MG2900-series: usb://Canon/MG2900%20series?serial=473C59=1 MachineType: Gigabyte Technology Co., Ltd. A520M S2H Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-MG2900-series.ppd', '/etc/cups/ppd/Canon-iP90.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-MG2900-series.ppd: Permission denied grep: /etc/cups/ppd/Canon-iP90.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=c201ceca-9f5a-4845-b650-e68fc9d5230f ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: A520M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnA520MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA520MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: A520 MB dmi.product.name: A520M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932205 Title: Canon iP90 Ptr outputs blank pgs in 20.04, works in Win10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1932205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931891] Re: Touchpad stopped working after updating kernel from 5.8.0-53-generic to 5.8.0-55-generic
Thank you for responding. Today I booted using 5.8.0-55-generic and the touchpad works again. It must've been something other than the kernel update. Sorry for the false alarm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931891 Title: Touchpad stopped working after updating kernel from 5.8.0-53-generic to 5.8.0-55-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931891] [NEW] Touchpad stopped working after updating kernel from 5.8.0-53-generic to 5.8.0-55-generic
Public bug reported: Ubuntu 20.04.2 LTS Lenovo ThinkPad P14s Gen 1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931891 Title: Touchpad stopped working after updating kernel from 5.8.0-53-generic to 5.8.0-55-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1896482] Re: acpi event detection crashes (fwd)
Hi Alex, just to make sure that I reinstalled one of the kernels that was supposed to be good (perhaps by accident I reinstalled a bad one), could you direct me to a good kernel on your ftp site? best, Jim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1896482] Re: acpi event detection crashes (fwd)
Hi Alex, unfortunately that bug has come back. It just took longer to manifest itself after booting. It also affects recognition of the power state and the brightness buttons, which I hadn't noticed before. --Jim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928942] [NEW] Installer said it had failed; auto report was sent
Public bug reported: Was installing Ubuntu from a USB memory stick. Chose option to retain an existing Windows 10 partition and choose Ubuntu or Win at start-up. Partition size set to 250GB for Win and 250GB for Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.19 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Wed May 19 13:51:53 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANGUAGE=en_GB.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.19 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928942 Title: Installer said it had failed; auto report was sent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1928942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926918] Re: cannot install libc6-dev, requires old libc6 version
Balint, what is the accepted method to downgrade an installed package to a prior version? I can think of three or four ways to accomplish it, but I can think of ways it could bite me in the butt having done so just as easily. :) This is especially a problem for this particular package, because simply removing libc6 would break enormous swathes of the system... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926918 Title: cannot install libc6-dev, requires old libc6 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1926918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926918] [NEW] cannot install libc6-dev, requires old libc6 version
Public bug reported: Current version of libc6:amd64 in Focal is 2.31-0ubuntu9.3. libc6-dev requires 2.31-0ubuntu9.2 **only**. This prevents installation of libc6-dev (as originally discovered while trying to install build- essential, which also requires libc6-dev). root@nel-lg-gram:/home/nel# apt -f install libc6-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libc6-dev : Depends: libc6 (= 2.31-0ubuntu9.2) but 2.31-0ubuntu9.3 is to be installed E: Unable to correct problems, you have held broken packages. root@nel-lg-gram:/home/nel# dpkg --get-selections | grep libc6 libc6:amd64 install libc6-dbg:amd64 install root@nel-lg-gram:/home/nel# apt policy libc6 libc6: Installed: 2.31-0ubuntu9.3 Candidate: 2.31-0ubuntu9.3 Version table: *** 2.31-0ubuntu9.3 100 100 /var/lib/dpkg/status 2.31-0ubuntu9.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2.31-0ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libc6-dev (not installed) ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 2 17:58:02 2021 InstallationDate: Installed on 2020-10-31 (183 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926918 Title: cannot install libc6-dev, requires old libc6 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1926918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924752] Re: mac fails to boot after hirsute release upgrade (secureboot)
Yes, it is EFI v1.10: [0.00] efi: EFI v1.10 by Apple [0.484667] fb0: EFI VGA frame buffer device [0.532601] EFI Variables Facility v0.08 2004-May-17 [0.984410] fb0: switching to radeondrmfb from EFI VGA -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924752 Title: mac fails to boot after hirsute release upgrade (secureboot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924752] Re: mac fails to boot after hirsute release upgrade (secureboot)
Using boot-repair to disable secureboot (purging and reinstalling GRUB2) now allows booting again. ** Summary changed: - mac fails to boot after hirsute release upgrade + mac fails to boot after hirsute release upgrade (secureboot) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924752 Title: mac fails to boot after hirsute release upgrade (secureboot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924752] Re: mac fails to boot after hirsute release upgrade
** Attachment added: "apt.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924752/+attachment/5488870/+files/apt.log ** Description changed: After today trying `do-release-upgrade -d` on an iMac running Kubuntu 20.10, the system now fails to boot, staying at the initial Mac white screen. + + (Trying to manually chroot/update-grub or using Boot-Repair does not + solve the problem.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924752 Title: mac fails to boot after hirsute release upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924752] Re: mac fails to boot after hirsute release upgrade
** Attachment added: "xorg_fixup.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924752/+attachment/5488868/+files/xorg_fixup.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924752 Title: mac fails to boot after hirsute release upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924752] Re: mac fails to boot after hirsute release upgrade
** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924752/+attachment/5488869/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924752 Title: mac fails to boot after hirsute release upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924752] [NEW] mac fails to boot after hirsute release upgrade
Public bug reported: After today trying `do-release-upgrade -d` on an iMac running Kubuntu 20.10, the system now fails to boot, staying at the initial Mac white screen. (Trying to manually chroot/update-grub or using Boot-Repair does not solve the problem.) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Attachment added: "main.log" https://bugs.launchpad.net/bugs/1924752/+attachment/5488867/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924752 Title: mac fails to boot after hirsute release upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909002] Re: Kernel 5.4.0-58
I tried many different ways to resolve this issue manually adding and removing modules or editing driver files as suggested in different forums and it didn't work (I only have a basic knowledge of Linux) anyway I'm pleased to say that it is working again from Kernel 5.4.0-67. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909002 Title: Kernel 5.4.0-58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921542] [NEW] lubuntu crashed on install on old netbook hd
Public bug reported: none - will check the drive and the install media to be sure there is no hardware issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 CasperVersion: 1.376.2 Date: Fri Mar 26 14:21:43 2021 InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170216) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lubuntu ubiquity-2.21.63.3 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921542 Title: lubuntu crashed on install on old netbook hd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921527] [NEW] Call to cupsGetDestMediaDefault always returns Letter
Public bug reported: The following always returns size of Letter regardless of what the default is set to at localhost:631. This is the case for multiple printers and printer manufacturers. cups_size_t size; int count = cupsGetDestMediaDefault(CUPS_HTTP_DEFAULT, m_dest, m_info, 0, ); Ubuntu 20.04 CUPS 2.3.1-9ubuntu1.1 gcc 9.3.0 For driverless printers, the PPD file shows the correct default. ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921527 Title: Call to cupsGetDestMediaDefault always returns Letter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1921527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920187] Re: Installer failure Lenovo Yoga
I shut down, then reinstalled from usb. All up and running ok. I didn't want to go through the MS Windows setup (which I find particularly irksome, cumbersome and intrusive) which is probably why the Windows cache contained the metadata. I only sent the failure through in case there were any bugs in the installer that may have needed patching. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920187 Title: Installer failure Lenovo Yoga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1920187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920187] [NEW] Installer failure Lenovo Yoga
Public bug reported: Failure of the installer process (not recoverable) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 Date: Fri Mar 19 23:38:58 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920187 Title: Installer failure Lenovo Yoga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1920187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
** Also affects: debconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634508 Title: Clients cannot connect when MIR_SOCKET="" To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917705] Re: "profile will be deleted" at startup after chromium 89 update
If the profile is managed, it seems that local data is deleted - at least it becomes unusable, so it might as well be deleted. If that is avoidable, it would be good to do so. I can understand why you would want to delete the local data associated with a managed profile in some circumstances, but "Google deprecated an API" doesn't seem like one of them. Another mitigation would be to provide a message that makes it clearer that the problem is with Chromium and not with the managed account. That would save a lot of wasted time between employees and their company tech support. (Though maybe it's too late for this to be useful - perhaps everyone who is going to hit this bug has done so already.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917705 Title: "profile will be deleted" at startup after chromium 89 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917713] Re: [snap] Logged out of Chromium after latest update to 89
I think I am also hitting this same bug. I'm running Chromium 1506 from Snap on Ubuntu 20.04. I have two Chromium profiles. One of them is managed by my employer. When I try to start that one, I get the error message: "Your account is no longer allowed as the primary account. Because this account is managed by , your bookmarks, history, passwords and other settings will be cleared from this device." This profile seems to now be unusable - when I ack the error message, Chromium immediately quits. The other is my personal account. I can use this account, but although I am logged in to my Google account, Chromium itself is no longer logged in - I have a blank icon in the top right where my user avatar should be. When I open the dropdown, it says "Not logged in". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917713 Title: [snap] Logged out of Chromium after latest update to 89 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915828] [NEW] pacemaker fails to release clustered filesystem dlm locks on failover
Public bug reported: When a clustered node is detected as failed the remaining node tries to fence the resources. When using pacemaker with gfs2 on an lvm2 logical volume dlm_controld calls out to dlm_stonith to release any locks held. Due to a build issue with the version of libqb that pacemaker is compiled against, the call to QB_LOG_INIT_DATA which is #defined to CRM_TRACE_INIT_DATA, fails with an assertion. This prevents the lock manager from releasing any held locks on the failed node. At this point the gfs2 filesystem cannot be accessed and after any resource timeouts are met, the resource is marked as failed. Calling dlm_stonith by hand with the data that is passed to it by dlm_controld shows the assertion. root@u2004-1:~# /usr/sbin/dlm_stonith -n 2 -t 1612361398 dlm_stonith: utils.c:57: common: Assertion `"implicit callsite section is observable, otherwise target's and/or libqb's build is at fault, preventing reliable logging" && work_s1 != NULL && work_s2 != NULL' failed. It would appear that the code in libqb is over aggressive on the sanity checking, or assumes that QB_LOG_INIT_DATA will only be called by the library. External programs such as pacemaker that end up calling CRM_TRACE_INIT_DATA will suffer the same assertion. This patch from clusterlabs is an attempt to resolve the assertion, but is still not sufficient. https://lists.clusterlabs.org/pipermail/users/2018-February/023614.html Taking out the assertion in and recompiling pacemaker appears to be the only way to allow dlm_stonith to work. journalctl shows dlm_controld keeps trying to get a successful response from dlm_stonith Feb 16 13:11:57 u2004-1 dlm_controld[9344]: 4389 fence result 2 pid 26568 result -1 term signal 6 Feb 16 13:11:57 u2004-1 dlm_controld[9344]: 4389 fence status 2 receive -1 from 1 walltime 1613481117 local 4389 Feb 16 13:11:57 u2004-1 dlm_controld[9344]: 4389 fence request 2 pid 26607 nodedown time 1613481102 fence_all dlm_stonith Feb 16 13:11:58 u2004-1 dlm_controld[9344]: 4391 fence result 2 pid 26607 result -1 term signal 6 Feb 16 13:11:58 u2004-1 dlm_controld[9344]: 4391 fence status 2 receive -1 from 1 walltime 1613481118 local 4391 Feb 16 13:11:58 u2004-1 dlm_controld[9344]: 4391 fence request 2 pid 26637 nodedown time 1613481102 fence_all dlm_stonith Feb 16 13:12:00 u2004-1 dlm_controld[9344]: 4392 fence result 2 pid 26637 result -1 term signal 6 Feb 16 13:12:00 u2004-1 dlm_controld[9344]: 4392 fence status 2 receive -1 from 1 walltime 1613481120 local 4392 Feb 16 13:12:00 u2004-1 dlm_controld[9344]: 4392 fence request 2 pid 26693 nodedown time 1613481102 fence_all dlm_stonith Calling 'dlm_tool fence_ack 2' by hand immediately releases the dlm resource locks. root@u2004-1:~# lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 root@u2004-1:~# apt-cache policy pacemaker pacemaker: Installed: 2.0.3-3ubuntu4.1 Candidate: 2.0.3-3ubuntu4.1 Version table: *** 2.0.3-3ubuntu4.1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.0.3-3ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: pacemaker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915828 Title: pacemaker fails to release clustered filesystem dlm locks on failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1915828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1898389] Re: browser frequently crashing with trap int3
My workaround is to close chromium frequently (closing its x-window rather than normal exit from the browser) and restart it, in order to save all my open tabs. This seems to release the excess memory and CPU that is being hogged by this atrocious piece of software. On Tue, 26 Jan 2021, Fevrin wrote: > Just to note, the kernel trap int3 issue persists for me, even in the > latest Chromium release for Ubuntu 20.04.1, Version 88.0.4324.96 > (Official Build) snap (64-bit). > > Here's my kernel info: > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Linux cweeks-XPS-13-9380 5.4.0-59-generic #65-Ubuntu SMP Thu Dec 10 12:01:51 > UTC 2020 x86_64 x86_64 x86_64 GNU/Linux > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > I'm seeing errors like the following: > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Jan 26 13:25:14 XPS-13-9380 kernel: traps: chrome[2013993] trap int3 > ip:562b6998b3de sp:7ffe6c8b6a30 error:0 in chrome[562b64e8d000+7548000] > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.176240:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.178190:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.179527:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.180881:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1898389 > > Title: > browser frequently crashing with trap int3 > > Status in chromium-browser package in Ubuntu: > Expired > > Bug description: > I used to be able to have many tabs open with Chromium without > problems. Lately it crashes or gives "aw snap" errors (see kernel > messages below) if I start to keep more than 25 or so open. > > Description:Ubuntu 16.04.7 LTS > Release:16.04 > > chromium-browser: >Installed: 85.0.4183.83-0ubuntu0.16.04.2 >Candidate: 85.0.4183.121-0ubuntu0.16.04.1 >Version table: > 85.0.4183.121-0ubuntu0.16.04.1 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe > amd64 Packages > 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 > Packages > *** 85.0.4183.83-0ubuntu0.16.04.2 100 > 100 /var/lib/dpkg/status > 49.0.2623.108-0ubuntu1.1233 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 18.0.1025.151~r130497-0ubuntu1 500 > 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages > > > dmesg: > > [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 > sp:7ffdfc31ca70 error:0 > [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 > sp:7ffd8fc04770 error:0 > [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 > sp:7ffdfc31b2c0 error:0 > [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be > sp:7ffdfc31bd40 error:0 > [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 > sp:7ffdfc31cab0 error:0 > [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 > sp:7ffdfc31b300 error:0 > [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 > sp:7ffdfc31c640 error:0 > [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be > sp:7ffdfc31a6a0 error:0 > [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 > sp:7fe1dcaf95e0 error:0 > [519367.329864] traps: chromium-browse[24588] trap invalid opcode > ip:558478cb1962
[Bug 1773859] Re: Upgrades to 18.04 fail due to systemd-shim
** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Jim Denny (bluedanser) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: Upgrades to 18.04 fail due to systemd-shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912774] [NEW] can't install grub
Public bug reported: hp microserver gen8 tried to install boot loader on other drives than the ssd connected to the ODD port including internal micro sd card, usb drive and other hd. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445 Date: Fri Jan 22 11:59:51 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912774 Title: can't install grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1912774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906770] Re: Kernel 5.4.0-56 Wi-Fi does not connect
Problem is back in 5.4.0-62-generic. That version was recently released by Ubuntu and installed on my system during a regular update. However, when I run it and with that TP-Link AC-600 installed, I am again seeing the symptoms I observed in my original bug https://bugs.launchpad.net/bugs/1907764 . - Networking won't start. Network Settings shows "NetManager not running" - "ip addr" just hangs - Firefox never displays a window Rebooted under the developer version 5.4.0-61-generic, and things are working again (my AC-600 is still enabled and connected). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906770 Title: Kernel 5.4.0-56 Wi-Fi does not connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912285] [NEW] n2n /etc/default/n2n uses wrong env variable name
Public bug reported: /etc/default/n2n provides an: N2N_DAEMON_OPTS="" but the /etc/init.d/n2n script actually uses the more generically named: DAEMON_OPTS ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: n2n 1.3.1~svn3789-7 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 19 12:58:27 2021 InstallationDate: Installed on 2020-06-06 (226 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RebootRequiredPkgs:  linux-image-5.8.0-34-generic  linux-image-5.8.0-36-generic  linux-image-5.8.0-38-generic SourcePackage: n2n UpgradeStatus: Upgraded to groovy on 2020-11-04 (76 days ago) modified.conffile..etc.default.n2n: [modified] mtime.conffile..etc.default.n2n: 2021-01-19T10:52:35.529667 ** Affects: n2n (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Description changed: /etc/default/n2n provides an: N2N_DAEMON_OPTS="" - but the /etc/init.d/n2n script acutally uses the more generically named: + but the /etc/init.d/n2n script actually uses the more generically named: DAEMON_OPTS ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: n2n 1.3.1~svn3789-7 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 19 12:58:27 2021 InstallationDate: Installed on 2020-06-06 (226 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RebootRequiredPkgs: - linux-image-5.8.0-34-generic - linux-image-5.8.0-36-generic - linux-image-5.8.0-38-generic +  linux-image-5.8.0-34-generic +  linux-image-5.8.0-36-generic +  linux-image-5.8.0-38-generic SourcePackage: n2n UpgradeStatus: Upgraded to groovy on 2020-11-04 (76 days ago) modified.conffile..etc.default.n2n: [modified] mtime.conffile..etc.default.n2n: 2021-01-19T10:52:35.529667 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912285 Title: n2n /etc/default/n2n uses wrong env variable name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/n2n/+bug/1912285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906770] Re: Kernel 5.4.0-56 Wi-Fi does not connect
I reported bug 1907764, deemed a duplicate of this. I've installed the latest proposed Ubuntu kernel, 5.4.0-61-generic, under AMD64 and the system is stable with my TP-Link AC-600 adapter installed. It even works! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906770 Title: Kernel 5.4.0-56 Wi-Fi does not connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)
This bug affects me, too, on an amd64 system after an in-place do- release-upgrade upgrade from 18.04 LTS yesterday. I have no interactions with an OpenWRT box, though. My config is currently a WiFi connection away from home, with an automatic OpenVPN tunnel to my router at home, using split DNS to resolve a private .prv domain for my home network. The problem did not exist with 18.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906331 Title: systemd-resolve crashes fairly often (and reports various assertions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909492] [NEW] quadrapassel locked up. Frozen screen.
Public bug reported: === Info === PID: 11176 (quadrapassel) UID: 1000 (jim) GID: 1000 (jim) Signal: 5 (TRAP) Timestamp: Sun 2020-12-27 17:47:33 EST (18h ago) Command Line: quadrapassel Executable: /usr/games/quadrapassel Control Group: /user.slice/user-1000.slice/session-c2.scope Unit: session-c2.scope Slice: user-1000.slice Session: c2 Owner UID: 1000 (jim) Boot ID: 00779cd3939045efbbc09e0d1ebfbbba Machine ID: 2e6db7b3feeb408ba59f7482257bc249 Hostname: jim-broom Storage: /var/lib/systemd/coredump/core.quadrapassel.1000.00779cd3939045efbbc09e0d1ebfbbba.11176.1609109253.lz4 Message: Process 11176 (quadrapassel) of user 1000 dumped core. Stack trace of thread 11176: #0 0x7f58d7e940d5 n/a (libglib-2.0.so.0 + 0x580d5) #1 0x7f58d7e96abc g_log_writer_default (libglib-2.0.so.0 + 0x5aabc) #2 0x7f58d7e94d17 g_log_structured_array (libglib-2.0.so.0 + 0x58d17) #3 0x7f58d7e95744 g_log_structured_standard (libglib-2.0.so.0 + 0x59744) #4 0x7f58d713fcea n/a (libgdk-3.so.0 + 0x68cea) #5 0x7f58d714cd13 n/a (libgdk-3.so.0 + 0x75d13) #6 0x7f58d6f9d0db _XError (libX11.so.6 + 0x410db) #7 0x7f58d5940baf n/a (libGLX_mesa.so.0 + 0x38baf) #8 0x7f58d59438c0 n/a (libGLX_mesa.so.0 + 0x3b8c0) #9 0x7f58d72842ac n/a (libcogl.so.20 + 0x7b2ac) #10 0x7f58d8373c08 n/a (libclutter-1.0.so.0 + 0x47c08) #11 0x7f58d83e4e80 n/a (libclutter-1.0.so.0 + 0xb8e80) #12 0x7f58d83cde49 n/a (libclutter-1.0.so.0 + 0xa1e49) #13 0x7f58d7e8dfbd g_main_context_dispatch (libglib-2.0.so.0 + 0x51fbd) #14 0x7f58d7e8e240 n/a (libglib-2.0.so.0 + 0x52240) #15 0x7f58d7e8e2e3 g_main_context_iteration (libglib-2.0.so.0 + 0x522e3) #16 0x7f58d822dfd5 g_application_run (libgio-2.0.so.0 + 0xe2fd5) #17 0x55e7c75ea2a9 n/a (quadrapassel + 0x152a9) #18 0x7f58d733b0b3 __libc_start_main (libc.so.6 + 0x270b3) #19 0x55e7c75dd59e n/a (quadrapassel + 0x859e) Stack trace of thread 11179: #0 0x7f58d6e06376 futex_wait_cancelable (libpthread.so.0 + 0x10376) #1 0x7f58d448662b n/a (r600_dri.so + 0x47c62b) #2 0x7f58d448623b n/a (r600_dri.so + 0x47c23b) #3 0x7f58d6dff609 start_thread (libpthread.so.0 + 0x9609) #4 0x7f58d7436293 __clone (libc.so.6 + 0x122293) Stack trace of thread 11184: #0 0x7f58d7429aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f58d7e8e1ae n/a (libglib-2.0.so.0 + 0x521ae) #2 0x7f58d7e8e2e3 g_main_context_iteration (libglib-2.0.so.0 + 0x522e3) #3 0x7f58d7e8e331 n/a (libglib-2.0.so.0 + 0x52331) #4 0x7f58d7eb7931 n/a (libglib-2.0.so.0 + 0x7b931) #5 0x7f58d6dff609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f58d7436293 __clone (libc.so.6 + 0x122293) Stack trace of thread 11180: #0 0x7f58d6e06376 futex_wait_cancelable (libpthread.so.0 + 0x10376) #1 0x7f58d448662b n/a (r600_dri.so + 0x47c62b) #2 0x7f58d448623b n/a (r600_dri.so + 0x47c23b) #3 0x7f58d6dff609 start_thread (libpthread.so.0 + 0x9609) #4 0x7f58d7436293 __clone (libc.so.6 + 0x122293) Stack trace of thread 11183: #0 0x7f58d6e06376 futex_wait_cancelable (libpthread.so.0 + 0x10376) #1 0x7f58d448662b n/a (r600_dri.so + 0x47c62b) #2 0x7f58d448623b n/a (r600_dri.so + 0x47c23b) #3 0x7f58d6dff609 start_thread (libpthread.so.0 + 0x9609) #4 0x7f58d7436293 __clone (libc.so.6 + 0x122293) Stack trace of thread 11182: #0 0x7f58d6e06376 futex_wait_cancelable (libpthread.so.0 + 0x10376) #1 0x7f58d448662b n/a (r600_dri.so + 0x47c62b) #2 0x7f58d448623b n/a (r600_dri.so + 0x47c23b) #3 0x7f58d6dff609 start_thread (libpthread.so.0 + 0x9609) #4 0x7f58d7436293 __clone (libc.so.6 + 0x122293) Stack trace of thread 11186
[Bug 1909372] [NEW] PS2 mouse stopped working the upgrade before this one, still not working. FIX IT PLS!
Public bug reported: Last upgrade, having the PS2 mouse connected caused Ubuntu 20.04.1 to lock up the computer on a black screen. ASUS Mobo, Quad core AMD, 64-bit; 1 TB WD HDD. Mobo is a circa 2014 so still well within it's life. Withdrawing support for PS2 equipment at this EARLY stage makes us computer owners wonder why as there's no reason to do that this early. They are still making and selling brand new PS2 mice and keyboards! This bug likely applies to PS2 keyboards as well though I didn't test that. This upgrade, first one since Ubuntu stopped supporting PS2 equipmnet a couple three weeks ago (it's 12/26/20 today), it didn't lock up the computer this time so that was fixed, but PS2 mice still don't work!?? Why?? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Dec 26 13:09:17 2020 InstallationDate: Installed on 2018-05-09 (962 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LD_PRELOAD= SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) 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-12-26T13:05:25.187611 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909372 Title: PS2 mouse stopped working the upgrade before this one, still not working. FIX IT PLS! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1909372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909002] Re: Kernel 5.4.0-58
I tried running that command and I get ERROR: The python3-launchpadlib package is not installed. This functionality is not available. However as I had to uninstall 5.4.0-58 I don't know if this will show any information, the mouse does not move and if I run lsusb on 5.4.0-58 it shows: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub If I use lsusb on 5.4.0-54 it shows: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909002 Title: Kernel 5.4.0-58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909002] [NEW] Kernel 5.4.0-58
Public bug reported: After installing Kernel 5.4.0-58 in Mint, I lost the wireless USB LOGITECH mouse and keyboard, had to go back to 5.4.0-54. Description:Linux Mint 19.3 Tricia Release:19.3 ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909002 Title: Kernel 5.4.0-58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1909002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908935] [NEW] An unresolvable problem occurred while calculating the upgrade.
Public bug reported: Upgrading from 18.04 to focal fails with unresolvable problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.41 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 14:54:15 2020 InstallationDate: Installed on 2012-11-23 (2949 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-12-21 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908935 Title: An unresolvable problem occurred while calculating the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907764] Re: Wi-fi causes unstable behaviour with this kernel version
Downloaded new build and ran "sudo dpkg -i *5.4.0-59*deb" uname -r reports: 5.4.0-59-generic All seems fine. Think you got it. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907764 Title: Wi-fi causes unstable behaviour with this kernel version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
I've had the "Desktop Icons" disabled for a while now, and it doesn't solve the problem but it feels like it is less frequent. It most often happens when I open a new terminal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
Is there any workaround to this issue? This is a huge productivity killer for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907764] Re: Wi-fi causes unstable behaviour with this kernel version
Downloaded linux-headers-5.10.0-051000rc6_5.10.0-051000rc6 and
{image,modules}-generic.
Installed via "dpkg -i ..."
Rebooted.
Problem appears resolved. Just to verify I'm running the right version:
~/Downloads$ uname -r
5.10.0-051000rc6-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907764
Title:
Wi-fi causes unstable behaviour with this kernel version
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907764/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907764] Re: Wi-fi causes unstable behaviour with this kernel version
Please be aware (as noted above) that while I reported this bug under
linux-image-5.4.0-54 that's only because the latest version
linux-image-5.4.0-56 which exhibits the problem isn't stable enough to collect
information on the problematic wifi device.
lsusb says "Bus 001 Device 002: ID 148f:761a Ralink Technology, Corp. MT7610U
("Archer T2U" 2.4G+5G WLAN Adapter". It's marketed as TP-Link AC-600.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907764
Title:
Wi-fi causes unstable behaviour with this kernel version
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907764/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907764] [NEW] Wi-fi causes unstable behaviour with this kernel version
Public bug reported:
After a recent update to linux-image-5.4.0-56, my Ubuntu install has become
unusable. Some symptoms:
- Firefox would apparently launch but window would never appear
- Thunderbird would launch but hang shortly after displaying window
- "ip addr" would hang
- "sudo " would hang without ever prompting for password
- The "Settings" dialog would complain that NetManager was not running
Based on a bit of internet research, I removed my wi-fi USB device and
rebooted, and now the system will run. So, it seems this latest version has
some issue with the wifi support needed for my card which lsusb describes as:
Bus 001 Device 002: ID 148f:761a Ralink Technology, Corp. MT7610U ("Archer
T2U" 2.4G+5G WLAN Adapter
Note that I'm currently running under the next-to-last version installed
,linux-image-5.4.0-54, which supports this card just fine.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-54-generic 5.4.0-54.60
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: jim3040 F.... pulseaudio
/dev/snd/controlC1: jim3040 F.... pulseaudio
/dev/snd/controlC0: jim3040 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Dec 11 01:56:58 2020
InstallationDate: Installed on 2020-03-27 (259 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: System manufacturer System Product Name
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic
root=UUID=1b434c2a-987e-4daf-bd3d-fa7d3e4b5049 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-54-generic N/A
linux-backports-modules-5.4.0-54-generic N/A
linux-firmware1.187.6
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0604
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B450M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907764
Title:
Wi-fi causes unstable behaviour with this kernel version
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907764/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
I second that!! This is pathetic. On November 24, 2020 3:58:16 PM EST, BloodyIron <1828...@bugs.launchpad.net> wrote: >I AM STILL GETTING THIS ISSUE TO THIS DAY. WILL THIS EVER BE FIXED? >This >issue was reported over 1.5 YEARS ago and a fix was already made, but >HAS NOT BEEN RELEASED TO UBUNTU 20.04 WHICH IS THE LONG TERM SUPPORT >VERSION. WHEN WILL THIS BE FIXED? > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1828107 > >Title: > gvfs can't list shares from smb servers that disabled SMB1 > >Status in gvfs: > Unknown >Status in gvfs package in Ubuntu: > Triaged > >Bug description: > After bug #1778322 is fixed (just needs a gvfs rebuild with newer > samba), samba machines will start to show up again in the "windows > network" tab in nautilus. But if a server has disabled the SMB1 > protocol, nautilus will show an error when that server is clicked on, > instead of showing the shares list. > > Even with SMB1 disabled, it should still be technically possible to > get a share list, since smbclient can do it: > > andreas@nsnx:~$ nmblookup -A 192.168.122.101 > Looking up status of 192.168.122.101 > D-NO-SMB1 <00> - B > D-NO-SMB1 <03> - B > D-NO-SMB1 <20> - B > ..__MSBROWSE__. <01> - B > WORKGROUP <00> - B > WORKGROUP <1d> - B > WORKGROUP <1e> - B > > MAC Address = 00-00-00-00-00-00 > > andreas@nsnx:~$ smbclient -L 192.168.122.101 -N > WARNING: The "syslog" option is deprecated > > Sharename Type Comment > - --- > print$ Disk Printer Drivers > pub_no_smb1 Disk > IPC$IPC IPC Service (d-no-smb1 server (Samba, >Ubuntu)) > Reconnecting with SMB1 for workgroup listing. > protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE > Failed to connect with SMB1 -- no workgroup available > >andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U >ubuntu%ubuntu -m NT1 > WARNING: The "syslog" option is deprecated > protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE > >andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U >ubuntu%ubuntu -m SMB2 > WARNING: The "syslog" option is deprecated > Try "help" to get a list of possible commands. > smb: \> dir >. D0 Fri May 3 18:16:38 >2019 >.. D0 Fri May 3 18:15:24 >2019 >hello.txt N 21 Fri May 3 18:16:12 >2019 >hello-from-nsnx.txt A9 Fri May 3 18:16:38 >2019 > > 20509264 blocks of size 1024. 13121800 blocks > available > >To manage notifications about this bug go to: >https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904581] [NEW] package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: I am attempting to upgrade from xenial through bionic to focal. The upgrade to bionic went fine, but this error prevented the upgrade to focal. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.4 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 17 08:19 seq crw-rw 1 root audio 116, 33 Nov 17 08:19 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Tue Nov 17 08:18:46 2020 Dependencies: Ec2AMI: ami-0257d667d23f263ad Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: m3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU PackageArchitecture: all PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-124-generic root=UUID=d4f2aafc-946a-4514-930d-4c45e676f198 ro console=tty1 console=ttyS0 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-11-17 (0 days ago) dmi.bios.date: 08/24/2006 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ec2-images focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904581 Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1904581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1896482] Re: acpi event detection crashes (fwd)
Hi Alex, I see that I am currently running 5.4.0-48-generic, which I think is the same version that you originally sent me. But livepatch alters the running kernel without changing its version number, doesn't it? That's what makes me still wonder if it is the culprit. thanks--Jim On Tue, 3 Nov 2020, Jim Cline wrote: > > > > -- Forwarded message -- > Date: Mon, 02 Nov 2020 23:24:48 - > From: Alex Hung <1896...@bugs.launchpad.net> > To: gxgilt...@gmail.com > Subject: [Bug 1896482] Re: acpi event detection crashes > > @jim, > > You can check your kernel version by "uname -r". > > I also built a rebased one: > https://people.canonical.com/~alexhung/LP1896482/Ubuntu-5.4.0-52.57/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1898389] Re: browser frequently crashing with trap int3
the new version of Chromium seems to be a disaster when I try to go to full screen in YouTube. It scatters parts of the screen amongst my various virtual desktops and creates a huge mess, forcing me to kill chromium from the command line. On Fri, 30 Oct 2020, Olivier Tilloy wrote: > Thanks for the report Gerald, and sorry for the lack of a timely response. > Is this still happening with the latest update available for Ubuntu 16.04 > (version 86.0.4240.75-0ubuntu0.16.04.1)? > > ** Changed in: chromium-browser (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1898389 > > Title: > browser frequently crashing with trap int3 > > Status in chromium-browser package in Ubuntu: > Incomplete > > Bug description: > I used to be able to have many tabs open with Chromium without > problems. Lately it crashes or gives "aw snap" errors (see kernel > messages below) if I start to keep more than 25 or so open. > > Description:Ubuntu 16.04.7 LTS > Release:16.04 > > chromium-browser: >Installed: 85.0.4183.83-0ubuntu0.16.04.2 >Candidate: 85.0.4183.121-0ubuntu0.16.04.1 >Version table: > 85.0.4183.121-0ubuntu0.16.04.1 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe > amd64 Packages > 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 > Packages > *** 85.0.4183.83-0ubuntu0.16.04.2 100 > 100 /var/lib/dpkg/status > 49.0.2623.108-0ubuntu1.1233 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 18.0.1025.151~r130497-0ubuntu1 500 > 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages > > > dmesg: > > [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 > sp:7ffdfc31ca70 error:0 > [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 > sp:7ffd8fc04770 error:0 > [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 > sp:7ffdfc31b2c0 error:0 > [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be > sp:7ffdfc31bd40 error:0 > [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 > sp:7ffdfc31cab0 error:0 > [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 > sp:7ffdfc31b300 error:0 > [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 > sp:7ffdfc31c640 error:0 > [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be > sp:7ffdfc31a6a0 error:0 > [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 > sp:7fe1dcaf95e0 error:0 > [519367.329864] traps: chromium-browse[24588] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.357674] traps: chromium-browse[24558] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 > sp:7ffdfc316260 error:0 > [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 > sp:7ffdfc31abd0 error:0 > [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be > sp:7ffdfc31bbb0 error:0 > [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 > sp:7ffdfc31d020 error:0 > [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 > sp:7ffdfc3165c0 error:0 > [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 > sp:7ffdfc3164c0 error:0 > [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 > sp:7ffdfc31c5b0 error:0 > [519429.841404] traps: chromium-browse[24906] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898389 Title: browser frequently crashing with trap int3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1898389] Re: browser frequently crashing with trap int3
thanks, I will try with the updated version and keep you posted On Fri, 30 Oct 2020, Olivier Tilloy wrote: > Thanks for the report Gerald, and sorry for the lack of a timely response. > Is this still happening with the latest update available for Ubuntu 16.04 > (version 86.0.4240.75-0ubuntu0.16.04.1)? > > ** Changed in: chromium-browser (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1898389 > > Title: > browser frequently crashing with trap int3 > > Status in chromium-browser package in Ubuntu: > Incomplete > > Bug description: > I used to be able to have many tabs open with Chromium without > problems. Lately it crashes or gives "aw snap" errors (see kernel > messages below) if I start to keep more than 25 or so open. > > Description:Ubuntu 16.04.7 LTS > Release:16.04 > > chromium-browser: >Installed: 85.0.4183.83-0ubuntu0.16.04.2 >Candidate: 85.0.4183.121-0ubuntu0.16.04.1 >Version table: > 85.0.4183.121-0ubuntu0.16.04.1 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe > amd64 Packages > 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 > Packages > *** 85.0.4183.83-0ubuntu0.16.04.2 100 > 100 /var/lib/dpkg/status > 49.0.2623.108-0ubuntu1.1233 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 18.0.1025.151~r130497-0ubuntu1 500 > 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages > > > dmesg: > > [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 > sp:7ffdfc31ca70 error:0 > [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 > sp:7ffd8fc04770 error:0 > [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 > sp:7ffdfc31b2c0 error:0 > [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be > sp:7ffdfc31bd40 error:0 > [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 > sp:7ffdfc31cab0 error:0 > [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 > sp:7ffdfc31b300 error:0 > [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 > sp:7ffdfc31c640 error:0 > [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be > sp:7ffdfc31a6a0 error:0 > [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 > sp:7fe1dcaf95e0 error:0 > [519367.329864] traps: chromium-browse[24588] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.357674] traps: chromium-browse[24558] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 > sp:7ffdfc316260 error:0 > [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 > sp:7ffdfc31abd0 error:0 > [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be > sp:7ffdfc31bbb0 error:0 > [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 > sp:7ffdfc31d020 error:0 > [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 > sp:7ffdfc3165c0 error:0 > [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 > sp:7ffdfc3164c0 error:0 > [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 > sp:7ffdfc31c5b0 error:0 > [519429.841404] traps: chromium-browse[24906] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898389 Title: browser frequently crashing with trap int3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1896482] Re: acpi event detection crashes
Hi Alex, my problem came back. Is it possible that livepatch has replaced my working kernel with the broken one again? --Jim On Thu, 24 Sep 2020, Alex Hung wrote: > A test kernel with target patches ready for SRU is available @ > https://people.canonical.com/~alexhung/LP1896482/fixes/ > > The patch in #23 requires three precedent patches. See SRU.log file for > more details. > > Note it is rebased Ubuntu-5.4.0-48.52 now. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? >
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
This is happening to me a few times every day lately. I do not have any icons on the desktop. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x556612c6552a in dump_gjs_stack_on_signal_handler (signo=5) at ../src/main.c:421 #2 0x7f17472b6210 in () at /lib/x86_64-linux-gnu/libc.so.6 #3 _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 #4 0x7f17480f8159 in g_log_default_handler (log_domain=, log_level=, message=, unused_data=) at ../../../glib/gmessages.c:3123 #5 0x556612c655ee in default_log_handler (log_domain=0x7f1747836e20 "Gjs", log_level=6, message=0x55661bb3aca0 "toggling down object GInotifyFileMonitor that's already queued to toggle up\n", data=0x0) at ../src/main.c:363 #6 0x7f17480f839c in g_logv (log_domain=0x7f1747836e20 "Gjs", log_level=G_LOG_LEVEL_ERROR, format=, args=args@entry=0x7ffc2bb6e820) at ../../../glib/gmessages.c:1350 #7 0x7f17480f8583 in g_log (log_domain=log_domain@entry=0x7f1747836e20 "Gjs", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7f174783c308 "toggling down object %s that's already queued to toggle %s\n") at ../../../glib/gmessages.c:1415 #8 0x7f17477e40a7 in wrapped_gobj_toggle_notify(void*, GObject*, gboolean) (gobj=0x556615cd10b0 [GInotifyFileMonitor], is_last_ref=) at ../gi/object.cpp:1274 #9 0x7f17477f7058 in ToggleQueue::handle_toggle(void (*)(_GObject*, ToggleQueue::Direction)) (this=0x7f17478a14a0 , handler=0x7f17477e3f20 ) at ../gi/toggle.cpp:125 #10 0x7f17477f70df in ToggleQueue::idle_handle_toggle(void*) (data=0x7f17478a14a0 ) at ../gi/toggle.cpp:69 #11 0x7f17480f0e8e in g_main_dispatch (context=0x5566149c1350) at ../../../glib/gmain.c:3309 #12 g_main_context_dispatch (context=context@entry=0x5566149c1350) at ../../../glib/gmain.c:3974 #13 0x7f17480f1240 in g_main_context_iterate (context=0x5566149c1350, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4047 #14 0x7f17480f1533 in g_main_loop_run (loop=0x556614e05dc0) at ../../../glib/gmain.c:4241 #15 0x7f174751aaf0 in meta_run () at /lib/x86_64-linux-gnu/libmutter-6.so.0 #16 0x556612c64d7d in main (argc=, argv=) at ../src/main.c:634 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1896482] Re: acpi event detection crashes
last one you sent with the commit? It is working. On Fri, 25 Sep 2020, Alex Hung wrote: > @jcline-physics, > > can you give kernel in #24 a try? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20 11:35:33 laxmi kernel: [232492.303666] > acpi_ev_address_space_dispatch+0x2f7/0x39f > Sep 20 11:35:33 laxmi kernel: [232492.303668] ? ec_transaction+0x70/0x70 > Sep 20
Re: [Bug 1896482] Re: acpi event detection crashes
thanks a lot Alex On Thu, 24 Sep 2020, Alex Hung wrote: > A test kernel with target patches ready for SRU is available @ > https://people.canonical.com/~alexhung/LP1896482/fixes/ > > The patch in #23 requires three precedent patches. See SRU.log file for > more details. > > Note it is rebased Ubuntu-5.4.0-48.52 now. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20
Re: [Bug 1896482] Re: acpi event detection crashes
that one seems to be fine. On Thu, 24 Sep 2020, Alex Hung wrote: > Next one: > https://people.canonical.com/~alexhung/LP1896482/937d1d5d752513b8/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20 11:35:33 laxmi kernel: [232492.303666] > acpi_ev_address_space_dispatch+0x2f7/0x39f > Sep 20 11:35:33 laxmi kernel: [232492.303668] ? ec_transaction+0x70/0x70 > Sep 20
Re: [Bug 1896482] Re: acpi event detection crashes
that one also seems to be good. On Wed, 23 Sep 2020, Alex Hung wrote: > Next one is @ > https://people.canonical.com/~alexhung/LP1896482/c271d18b523bb58e/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20 11:35:33 laxmi kernel: [232492.303666] > acpi_ev_address_space_dispatch+0x2f7/0x39f > Sep 20 11:35:33 laxmi kernel: [232492.303668] ? ec_transaction+0x70/0x70 >
Re: [Bug 1896482] Re: acpi event detection crashes
this one seems to be good On Wed, 23 Sep 2020, Alex Hung wrote: > @jcline-physics, > > Thanks for testing. The next is available @ > https://people.canonical.com/~alexhung/LP1896482/31be3e3551d09f20/ > > ** Changed in: linux (Ubuntu) > Status: Confirmed => In Progress > > ** Changed in: linux (Ubuntu) > Assignee: (unassigned) => Alex Hung (alexhung) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] >
Re: [Bug 1896482] Re: acpi event detection crashes
okay, so that kernel has the problem again. On Wed, 23 Sep 2020, Alex Hung wrote: > Thanks mfo for helping out how to disable secure boot and install kernel > > I uploaded a test kernel @ > https://people.canonical.com/~alexhung/LP1896482/0a8c35897f60b202/ > > There are 17 patches so it requires 4 times to identify the fixing > kernel patch. The included patches are listed in ec_bisect1.log in the > above link. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep
