[Touch-packages] [Bug 2058769] Re: proposed-migration for click 0.5.2-2
This bug was fixed in the package click - 0.5.2-2ubuntu4 --- click (0.5.2-2ubuntu4) noble; urgency=medium * Fix preload path harder. -- Steve Langasek Tue, 23 Apr 2024 04:32:56 + ** Changed in: click (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2058769 Title: proposed-migration for click 0.5.2-2 Status in click package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Invalid Bug description: click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on all archs except amd64. In order to be able to run the tests without all-proposed=1, glib 2.0 is needed, which is why I marked it as affected. Excerpt of the test logs: ERROR: test_list_simple (click_package.tests.integration.test_list.TestList.test_list_simple) -- Traceback (most recent call last): File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py", line 29, in test_list_simple self.click_install(path_to_click, name, user) File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py", line 99, in click_install subprocess.check_call(cmd) File "/usr/lib/python3.12/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--user=root', '--allow-unauthenticated', '/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit status 1. == ERROR: test_debsig_install_valid_signature (click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature) -- Traceback (most recent call last): File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 207, in test_debsig_install_valid_signature subprocess.check_call( File "/usr/lib/python3.12/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--user=root', '/tmp/tmpymtfsjg9/org.example.debsig-valid-sig_1.0_all.click']' returned non-zero exit status 1. == ERROR: test_debsig_install_can_install_with_sig_override (click_package.tests.integration.test_signatures.TestSignatureVerificationNoSignature.test_debsig_install_can_install_with_sig_override) -- Traceback (most recent call last): File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 164, in test_debsig_install_can_install_with_sig_override subprocess.check_call( File "/usr/lib/python3.12/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--allow-unauthenticated', '--user=root', '/tmp/tmpheysy9ze/org.example.debsig-no-sig_1.0_all.click']' returned non-zero exit status 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/2058769/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063194] [NEW] Sync capnproto 1.0.1-4 (universe) from Debian unstable (main)
Public bug reported: Please sync capnproto 1.0.1-4 (universe) from Debian unstable (main) Changelog entries since current noble version 1.0.1-3build4: capnproto (1.0.1-4) unstable; urgency=medium * Add patch for FTBFS on 32-bit ARM after the time_t 64 transition. Thank you to Arnd Bergmann, Wookey, Tom Lee, and Andrey Rakhmatullin for their for help resolving this bug. (Closes: #1067916) -- tony mancill Mon, 15 Apr 2024 22:09:51 -0700 ** Affects: capnproto (Ubuntu) Importance: Undecided Assignee: Graham Inggs (ginggs) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to capnproto in Ubuntu. https://bugs.launchpad.net/bugs/2063194 Title: Sync capnproto 1.0.1-4 (universe) from Debian unstable (main) Status in capnproto package in Ubuntu: In Progress Bug description: Please sync capnproto 1.0.1-4 (universe) from Debian unstable (main) Changelog entries since current noble version 1.0.1-3build4: capnproto (1.0.1-4) unstable; urgency=medium * Add patch for FTBFS on 32-bit ARM after the time_t 64 transition. Thank you to Arnd Bergmann, Wookey, Tom Lee, and Andrey Rakhmatullin for their for help resolving this bug. (Closes: #1067916) -- tony mancill Mon, 15 Apr 2024 22:09:51 -0700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/2063194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063194] Re: Sync capnproto 1.0.1-4 (universe) from Debian unstable (main)
** Changed in: capnproto (Ubuntu) Assignee: (unassigned) => Graham Inggs (ginggs) ** Changed in: capnproto (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to capnproto in Ubuntu. https://bugs.launchpad.net/bugs/2063194 Title: Sync capnproto 1.0.1-4 (universe) from Debian unstable (main) Status in capnproto package in Ubuntu: In Progress Bug description: Please sync capnproto 1.0.1-4 (universe) from Debian unstable (main) Changelog entries since current noble version 1.0.1-3build4: capnproto (1.0.1-4) unstable; urgency=medium * Add patch for FTBFS on 32-bit ARM after the time_t 64 transition. Thank you to Arnd Bergmann, Wookey, Tom Lee, and Andrey Rakhmatullin for their for help resolving this bug. (Closes: #1067916) -- tony mancill Mon, 15 Apr 2024 22:09:51 -0700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/2063194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063194] Re: Sync capnproto 1.0.1-4 (universe) from Debian unstable (main)
This bug was fixed in the package capnproto - 1.0.1-4 Sponsored for Skia (hyask) --- capnproto (1.0.1-4) unstable; urgency=medium * Add patch for FTBFS on 32-bit ARM after the time_t 64 transition. Thank you to Arnd Bergmann, Wookey, Tom Lee, and Andrey Rakhmatullin for their for help resolving this bug. (Closes: #1067916) -- tony mancill Mon, 15 Apr 2024 22:09:51 -0700 ** Changed in: capnproto (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to capnproto in Ubuntu. https://bugs.launchpad.net/bugs/2063194 Title: Sync capnproto 1.0.1-4 (universe) from Debian unstable (main) Status in capnproto package in Ubuntu: Fix Released Bug description: Please sync capnproto 1.0.1-4 (universe) from Debian unstable (main) Changelog entries since current noble version 1.0.1-3build4: capnproto (1.0.1-4) unstable; urgency=medium * Add patch for FTBFS on 32-bit ARM after the time_t 64 transition. Thank you to Arnd Bergmann, Wookey, Tom Lee, and Andrey Rakhmatullin for their for help resolving this bug. (Closes: #1067916) -- tony mancill Mon, 15 Apr 2024 22:09:51 -0700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/2063194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056758] Re: ubuntu-bug doesn't let me file bugs for Snap thunderbird
https://github.com/canonical/apport/pull/324 got merged. ** Changed in: apport Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2056758 Title: ubuntu-bug doesn't let me file bugs for Snap thunderbird Status in Apport: Fix Committed Status in apport package in Ubuntu: Triaged Status in thunderbird package in Ubuntu: Incomplete Bug description: I'm trying to report a bug in the new Snap for Thunderbird. When I run "ubuntu-bug thunderbird", it: * Collects information correctly after I input the sudo password * Opens a page like https://bugs.launchpad.net/distros/+filebug/a9564134-dfa6-11ee-85a7-c7116d9f638e?, which does not seem to be valid. This is not the case for Firefox, which works fine with ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:483410:2024-03-11 14:47:26.874792575 +0400:2024-03-11 14:47:27.874792575 +0400:/var/crash/_opt_Citrix_ICAClient_util_storebrowse.1000.crash 640:0:124:29135:2024-03-10 17:02:30.124656623 +0400:2024-03-10 17:02:30.124656623 +0400:/var/crash/_usr_share_apport_apport.0.crash CurrentDesktop: KDE Date: Mon Mar 11 16:54:18 2024 InstallationDate: Installed on 2022-08-29 (560 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to noble on 2024-02-23 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2056758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063200] [NEW] useradd --extrausers --groups tries to lock /etc/group
Public bug reported: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group Status in shadow package in Ubuntu: New Bug description: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990200] Re: goa-daemon crashed with SIGABRT
** Changed in: gnome-online-accounts Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts: Fix Released Status in gnome-online-accounts package in Ubuntu: Invalid Status in librest package in Ubuntu: Fix Released Status in librest source package in Kinetic: Fix Released Bug description: * Impact The gnome-online-accounts sometime crash after resuming from suspend * Test case Install the librest update, restart your system and verify that configured online accounts keep working. Taking a Google account example, calendar events should show in gnome-calendar and the top panel widget, evolution should list your email account and nautilus should be able to browse your gdrive folder. We should also confirm that error reports stop with the library update * Regression potential The patch makes the code better handle an empty payload. The librest rdepends in the archive are gnome-initial-setup/gnome-online- accounts/gnome-maps so we should verify that those keep working as expected. - Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1990200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056758] Re: ubuntu-bug doesn't let me file bugs for Snap thunderbird
Thanks Benjamin! ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Invalid ** Changed in: apport (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2056758 Title: ubuntu-bug doesn't let me file bugs for Snap thunderbird Status in Apport: Fix Committed Status in apport package in Ubuntu: In Progress Status in thunderbird package in Ubuntu: Invalid Bug description: I'm trying to report a bug in the new Snap for Thunderbird. When I run "ubuntu-bug thunderbird", it: * Collects information correctly after I input the sudo password * Opens a page like https://bugs.launchpad.net/distros/+filebug/a9564134-dfa6-11ee-85a7-c7116d9f638e?, which does not seem to be valid. This is not the case for Firefox, which works fine with ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:483410:2024-03-11 14:47:26.874792575 +0400:2024-03-11 14:47:27.874792575 +0400:/var/crash/_opt_Citrix_ICAClient_util_storebrowse.1000.crash 640:0:124:29135:2024-03-10 17:02:30.124656623 +0400:2024-03-10 17:02:30.124656623 +0400:/var/crash/_usr_share_apport_apport.0.crash CurrentDesktop: KDE Date: Mon Mar 11 16:54:18 2024 InstallationDate: Installed on 2022-08-29 (560 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to noble on 2024-02-23 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2056758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
** Changed in: shadow (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group Status in shadow package in Ubuntu: New Bug description: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
Quick repro steps: ❯ lxc launch ubuntu-daily:noble shadow Creating shadow Starting shadow ❯ lxc exec shadow bash root@shadow:~# mv /etc /etc_write root@shadow:~# mkdir /etc root@shadow:~# mount -o bind,ro /etc_write /etc root@shadow:~# useradd --extrausers --groups somegroup somenewuser useradd: cannot lock /etc/group; try again later. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group Status in shadow package in Ubuntu: New Bug description: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058415] Re: Reading binary data in paraview broken by libexpat1 update
VTK has been patched upstream to correctly handle AppendedData elements in .vtu files with the updated/patched libexpat1: https://gitlab.kitware.com/vtk/vtk/-/commit/db8f9efca220c9d16a30958e179abae3379d0011 https://gitlab.kitware.com/vtk/vtk/-/issues/19258 This will need backporting to older VTK releases on ubuntu's where libexpat1's fixes have been backported, which if I'm reading the ubuntu package release dates correctly is Jammy(security, updates), Mantic (security, updates) and potentially Noble (release). ** Bug watch added: gitlab.kitware.com/vtk/vtk/-/issues #19258 https://gitlab.kitware.com/vtk/vtk/-/issues/19258 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/2058415 Title: Reading binary data in paraview broken by libexpat1 update Status in dune-grid package in Ubuntu: New Status in expat package in Ubuntu: Confirmed Status in paraview package in Ubuntu: Confirmed Bug description: The recent update of libexpat1 to version 2.5.0-2ubuntu0.1 broke Paraview. In particular reading vtu files containing binary data fails since this update. When trying to open files that worked fine before, Paraview now reports a parsing error like this one: ERROR: In vtkXMLParser.cxx, line 376 vtkXMLDataParser (0x5b0ac36fc970): Error parsing XML in stream at line 21, column 0, byte index 1036: not well-formed (invalid token) ERROR: In vtkXMLReader.cxx, line 521 vtkXMLUnstructuredGridReader (0x5b0ac3d3b670): Error parsing input file. ReadXMLInformation aborting. The problem disappears when reverting libexpat1 to version 2.5.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dune-grid/+bug/2058415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
I can confirm this is an issue, although it's not caused by Network Manager so I'll go ahead and set it as invalid. After trying to do a "do-release-upgrade -d" from a brand new installation of Jammy 22.04.4, gnome-shell crashed and interrupted the upgrade. After that, this is what "dpkg --list | grep systemd" looks like: ii dbus-user-session 1.14.10-4ubuntu4 amd64simple interprocess messaging system (systemd --user integration) ii gnome-logs42.0-1 amd64viewer for the systemd journal ii libnss-systemd:amd64 249.11-0ubuntu3.12 amd64nss module providing dynamic user and group name resolution ii libpam-systemd:amd64 249.11-0ubuntu3.12 amd64system and service manager - PAM module ii libsystemd-shared:amd64 255.4-1ubuntu8 amd64systemd shared private library ii libsystemd0:amd64 255.4-1ubuntu8 amd64systemd utility library ii networkd-dispatcher 2.1-2ubuntu0.22.04.2 all Dispatcher service for systemd-networkd connection status changes ii python3-systemd 235-1build4 amd64Python 3 bindings for systemd ii systemd 255.4-1ubuntu8 amd64system and service manager ii systemd-dev 255.4-1ubuntu8 all systemd development files ii systemd-hwe-hwdb 249.11.5 all udev rules for hardware enablement (HWE) ii systemd-oomd 249.11-0ubuntu3.12 amd64Userspace out-of-memory (OOM) killer ii systemd-sysv 249.11-0ubuntu3.12 amd64system and service manager - SysV links ii systemd-timesyncd 255.4-1ubuntu8 amd64minimalistic service to synchronize local time with NTP servers and /etc/resolv.conf is a broken link as systemd-resolved is not installed and /run/systemd/resolve doesn't exist: /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf ** Changed in: network-manager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.appor
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058415] Re: Reading binary data in paraview broken by libexpat1 update
** Also affects: vtk7 Importance: Undecided Status: New ** No longer affects: vtk7 ** Also affects: vtk7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/2058415 Title: Reading binary data in paraview broken by libexpat1 update Status in dune-grid package in Ubuntu: New Status in expat package in Ubuntu: Confirmed Status in paraview package in Ubuntu: Confirmed Status in vtk7 package in Ubuntu: New Bug description: The recent update of libexpat1 to version 2.5.0-2ubuntu0.1 broke Paraview. In particular reading vtu files containing binary data fails since this update. When trying to open files that worked fine before, Paraview now reports a parsing error like this one: ERROR: In vtkXMLParser.cxx, line 376 vtkXMLDataParser (0x5b0ac36fc970): Error parsing XML in stream at line 21, column 0, byte index 1036: not well-formed (invalid token) ERROR: In vtkXMLReader.cxx, line 521 vtkXMLUnstructuredGridReader (0x5b0ac3d3b670): Error parsing input file. ReadXMLInformation aborting. The problem disappears when reverting libexpat1 to version 2.5.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dune-grid/+bug/2058415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063154] Re: Wireguard imported with Network manager does not work after latest upgrade, wg-quick using the same config file works
Well, with a new set of upgrades the problem seems to have resolved itself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2063154 Title: Wireguard imported with Network manager does not work after latest upgrade, wg-quick using the same config file works Status in network-manager package in Ubuntu: New Bug description: Until a few days ago, after some upgrade, wireguard config imported with Network manager worked ootb. Now, it does not, there is no handshake. Activating the same config file with wg-quick does work. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-1005.5-oem 6.8.1 Uname: Linux 6.8.0-1005-oem x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 22:41:06 2024 InstallationDate: Installed on 2024-04-08 (14 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408) IpRoute: default via 192.168.173.139 dev wlp1s0 proto dhcp src 192.168.173.61 metric 600 192.168.173.0/24 dev wlp1s0 proto kernel scope link src 192.168.173.61 metric 600 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 MR Net 1 f92fae58-e84a-487e-9bdd-8d1ffbf8ca17 /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback connected (externally) unknown unknown /org/freedesktop/NetworkManager/Devices/1 lo 6fc7aa03-b696-4081-a275-4dc81c74c13e /org/freedesktop/NetworkManager/ActiveConnection/1 P14s_wg wireguard connected (externally) limited limited /org/freedesktop/NetworkManager/Devices/4 P14s_wg 40fadfce-b931-472f-b4cd-9922f77068ee /org/freedesktop/NetworkManager/ActiveConnection/14 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.46.0 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2063154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056758] Re: ubuntu-bug doesn't let me file bugs for Snap thunderbird
** Changed in: apport (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2056758 Title: ubuntu-bug doesn't let me file bugs for Snap thunderbird Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: I'm trying to report a bug in the new Snap for Thunderbird. When I run "ubuntu-bug thunderbird", it: * Collects information correctly after I input the sudo password * Opens a page like https://bugs.launchpad.net/distros/+filebug/a9564134-dfa6-11ee-85a7-c7116d9f638e?, which does not seem to be valid. This is not the case for Firefox, which works fine with ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:483410:2024-03-11 14:47:26.874792575 +0400:2024-03-11 14:47:27.874792575 +0400:/var/crash/_opt_Citrix_ICAClient_util_storebrowse.1000.crash 640:0:124:29135:2024-03-10 17:02:30.124656623 +0400:2024-03-10 17:02:30.124656623 +0400:/var/crash/_usr_share_apport_apport.0.crash CurrentDesktop: KDE Date: Mon Mar 11 16:54:18 2024 InstallationDate: Installed on 2022-08-29 (560 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to noble on 2024-02-23 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2056758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble
** Bug watch added: Busybox Bugzilla #16042 https://bugs.busybox.net/show_bug.cgi?id=16042 ** Also affects: busybox via https://bugs.busybox.net/show_bug.cgi?id=16042 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2062414 Title: busybox 1.36.1 FTBFS with current kernel headers on noble Status in BusyBox: Unknown Status in busybox package in Ubuntu: Fix Released Bug description: The networking/tc.c unit in busybox relies upon the CBQ (class based queue) UAPI in the kernel. Unfortunately this was removed in [1]. At present, there is no upstream patch (or even bug report that I can find), and this close to the release patching the kernel to resolve things is not going to happen. Will attach a patch re-instating the defines from the removed headers. [1]: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df To manage notifications about this bug go to: https://bugs.launchpad.net/busybox/+bug/2062414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group Status in shadow package in Ubuntu: New Bug description: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
** Also affects: e2fsprogs (Ubuntu Noble) Importance: Critical Assignee: Matthew Ruffell (mruffell) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: In Progress Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: In Progress Status in e2fsprogs source package in Jammy: In Progress Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: In Progress Status in e2fsprogs source package in Noble: In Progress Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063204] Re: Desktop-Live ships /etc/netplan/01-network-manager-all.yaml in addition to /usr/lib/netplan/00-network-manager-all.yaml
Arguably, the "/usr/lib/netplan/00-network-manager-all.yaml" should be shipped by the network-manager package, instead of ubuntu-settings... The community flavors using Calamares, might be covered by this PR: https://github.com/calamares/calamares/pull/2284 ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2063204 Title: Desktop-Live ships /etc/netplan/01-network-manager-all.yaml in addition to /usr/lib/netplan/00-network-manager-all.yaml Status in livecd-rootfs package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: The /etc/netplan/01-network-manager-all.yaml, generated by livecd-rootfs, shouldn't exist any more IIUC. That functionality was moved into src:ubuntu-settings and shipped as /usr/lib/netplan/00-network-manager-all.yaml This is according to https://launchpad.net/ubuntu/+source/ubuntu- settings/23.10.1 The duplicated "renderer: NetworkManager" doesn't cause any harm in the live-session, AFAICT. The /etc/netplan/01-network-manager-all.yaml file is carried over into the installed system (target). After "apt install --reinstall ubuntu-settings" the file gets deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2063204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063221] [NEW] Drop libglib2.0-0 transitional package
Public bug reported: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 ** Affects: glib2.0 (Ubuntu) Importance: High Status: Triaged ** Tags: noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: Triaged Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
I attempted an upgrade from a clean Jammy install to Noble so that I could gather upgrade logs. I have attached them here. ** Attachment added: "dist-upgrade.tar.gz" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+attachment/5769726/+files/dist-upgrade.tar.gz ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063222] [NEW] Ghost "unknown display" since upgrading to 24.04 beta
Public bug reported: X11 GNOME NVIDIA 4080 with their driver -> GNOME settings has a "ghost" display called "Unknown Display", its resolution is 1024 x 768 I only have one display attached - a 4K 27" DELL plugged into the NVIDIA ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4) ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 08:55:55 2024 DistUpgraded: 2024-04-14 17:14:28,561 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu DkmsStatus: nvidia/535.171.04, 6.8.0-28-generic, x86_64: installed nvidia/535.171.04, 6.8.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] AlderLake-S GT1 [1462:7d25] NVIDIA Corporation AD103 [GeForce RTX 4080] [10de:2704] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] AD103 [GeForce RTX 4080] [1462:5111] InstallationDate: Installed on 2022-04-30 (724 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7D25 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: root=UUID=43e064ac-5857-4c85-b15d-1dd96cdad27b ro quiet splash vt.handoff=7 initrd=boot\initrd.img-6.8.0-31-generic SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-15 (9 days ago) dmi.bios.date: 11/13/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.F0 dmi.board.asset.tag: Default string dmi.board.name: PRO Z690-A WIFI (MS-7D25) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.F0:bd11/13/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D25 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ubuntu ** Attachment added: "Screenshot from 2024-04-23 08-25-39.png" https://bugs.launchpad.net/bugs/2063222/+attachment/5769727/+files/Screenshot%20from%202024-04-23%2008-25-39.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063222 Title: Ghost "unknown display" since upgrading to 24.04 beta Status in xorg package in Ubuntu: New Bug description: X11 GNOME NVIDIA 4080 with their driver -> GNOME settings has a "ghost" display called "Unknown Display", its resolution is 1024 x 768 I only have one display attached - a 4K 27" DELL plugged into the NVIDIA ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia
[Touch-packages] [Bug 2063222] Re: Ghost "unknown display" since upgrading to 24.04 beta
FWIW - I'm also using GNOME 46 in another distro - Manjaro - and this issue does not exist there -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063222 Title: Ghost "unknown display" since upgrading to 24.04 beta Status in xorg package in Ubuntu: New Bug description: X11 GNOME NVIDIA 4080 with their driver -> GNOME settings has a "ghost" display called "Unknown Display", its resolution is 1024 x 768 I only have one display attached - a 4K 27" DELL plugged into the NVIDIA ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4) ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 08:55:55 2024 DistUpgraded: 2024-04-14 17:14:28,561 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu DkmsStatus: nvidia/535.171.04, 6.8.0-28-generic, x86_64: installed nvidia/535.171.04, 6.8.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] AlderLake-S GT1 [1462:7d25] NVIDIA Corporation AD103 [GeForce RTX 4080] [10de:2704] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] AD103 [GeForce RTX 4080] [1462:5111] InstallationDate: Installed on 2022-04-30 (724 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7D25 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: root=UUID=43e064ac-5857-4c85-b15d-1dd96cdad27b ro quiet splash vt.handoff=7 initrd=boot\initrd.img-6.8.0-31-generic SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-15 (9 days ago) dmi.bios.date: 11/13/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.F0 dmi.board.asset.tag: Default string dmi.board.name: PRO Z690-A WIFI (MS-7D25) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.F0:bd11/13/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D25 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
** Changed in: glib2.0 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822
** Summary changed: - Software sources not correctly updated after upgrade and/or new installs + [SRU] Software Sources is not compatible with deb822 ** Summary changed: - [SRU] Software Sources is not compatible with deb822 + Software Sources is not compatible with deb822 ** Summary changed: - Software Sources is not compatible with deb822 + [SRU] Software Sources is not compatible with deb822 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: [SRU] Software Sources is not compatible with deb822 Status in software-properties package in Ubuntu: Confirmed Bug description: Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 13 11:44:28 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240331) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Adding my journal from the crash. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2055012/+attachment/5769751/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 The problem is that gnome-shell crashes during the upgrade, so packages including systemd-resolved never finish getting installed. Marking as a duplicate of bug 2054761. ** This bug has been marked a duplicate of bug 2054761 gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
** Also affects: glib2.0 (Ubuntu Noble) Importance: High Status: In Progress ** Changed in: glib2.0 (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: In Progress Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822
** Description changed: + [ Impact ] + + Ubuntu 24.04 now uses deb822 to represent software sources for deb + packages, instead of /etc/apt/sources.list. The complete rationale for + this change can be found here: https://discourse.ubuntu.com/t/spec-apt- + deb822-sources-by-default/29333 + + software-properties has two graphical frontends for editing these + software sources, one is GTK-based and the other is Qt-based. When the + underlying change to deb822 sources was made, the GTK-based frontend and + the DBus backend interface gained support. + + The original bug report shown below informed us of the lack of deb822 + support in the Qt frontend, which results in a broken, non-functional + interface when attempting to view or edit most values on the first two + tabs. The fix for this is to implement a Qt dialog for deb822 sources + that somewhat matches the existing GTK interface. + + [ Test Plan ] + + Install software-properties-qt 0.99.48 or earlier. + + Reproducing the bug: + 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. + 2. Observe that all four checkboxes on the Ubuntu Software tab (main, universe, restricted, and multiverse) are unchecked. + 3. Move to the Other Software tab and observe that there are no items in the list. + + Upgrade to software-properties-qt 0.99.49. + + Intended functionality: + 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. + 2. Observe that one or more checkboxes on the Ubuntu Software tab (representing main, universe, restricted, or multiverse) are checked. Toggle one or more of the checkboxes. + 3. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. + 4. Switch to the Other Software tab, there should be one item in the list. + 5. Select that item, then click Edit at the bottom of the dialog. Make a modification to every field on the screen, or a combination of fields you would like to test. All fields should work. + 6. Click the OK button at the bottom of the dialog to confirm the changes, then click Edit for that item again. The changes you made should be reflected (meaning, the changes were saved.) + 7. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. + + [ Where problems could occur ] + + This is well-tested code. That being said, the following small edge cases exist: + - If you create a very large amount of rows, it infinitely expands the dialog without a scroll wheel. This is the same functionality as the GTK frontend. + - Error validation is not performed on the deb822 lines, they are simply written to the ubuntu.sources file. This is good as a starting point, but also relies on the appropriate update notifier handling these errors. This is the same functionality as the GTK frontend. + + In a future update, this functionality could be broken by one or more of the following underlying changes: + - Changes to the software-properties backend which are only implemented for the GTK frontend. + - Changes to the location or formatting of the ubuntu.sources file. + - Regressions in the Python bindings for Qt 5, which are rare but possible. + - Regressions in Python itself. + + [ Other Info ] + + Ubuntu Studio's live ISO and installed system are affected by this. Only Lubuntu's installed system is affected by this. + + [ Original Report ] + Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 13 11:44:28 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240331) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 ** Also affects: software-properties (Ubuntu Noble) Importance: Critical Assignee: Simon Quigley (tsimonq2) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: [SRU] Software Sources is not compatible with deb822 Status in software-properties package in Ubuntu: Confirmed Status in software-properties source package in Noble: Con
[Touch-packages] [Bug 2055088] Re: debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie
** Also affects: software-properties (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2055088 Title: debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie Status in software-properties package in Ubuntu: New Status in software-properties source package in Noble: New Bug description: software-properties-gtk is used on the official gtk desktops such as budgie. Currently in the debian control file it has a recommendation to install the session manager for that desktop - so gnome-session-bin for GNOME based desktops, mate-session for mate desktop and so on. budgie-desktop for noble now uses budgie-session as its session manager instead of gnome-session. Because of the current recommendation, gnome-session-bin is installed on budgie-desktop. It no longer needs to be installed. software-properties needs an update to its alternate recommendations so that budgie-desktop doesnt pull in gnome-session-bin incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063228] [NEW] screen sometimes blinking
Public bug reported: My screen sometimes starts flashing strongly. I move the mouse cursor, it stops. I put the cursor back in its place, it starts again. I notice this with Firefox because I use it a lot, I don't know if this happens with other software. I'm under wayland (xwayland?) Description:Ubuntu 24.04 LTS Release:24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 18:57:50 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84bb] InstallationDate: Installed on 2024-04-07 (16 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Pavilion Laptop 14-ce2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2022 dmi.bios.release: 15.27 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063228 Title: screen sometimes blinking Status in xorg package in Ubuntu: New Bug description: My screen sometimes starts flashing strongly. I move the mouse cursor, it stops. I put the cursor back in its place, it starts again. I notice this with Firefox because I use it a lot, I don't know if this happens with other software. I'm under wayland (xwayland?) Description: Ubuntu 24.04 LTS Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 18:57:50 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84bb] InstallationDate: Installed on 2024-04-07 (16 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Visio
[Touch-packages] [Bug 2063228] Re: screen sometimes blinking
A video. ** Attachment added: "VID_20240423_185405.mp4" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063228/+attachment/5769792/+files/VID_20240423_185405.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063228 Title: screen sometimes blinking Status in xorg package in Ubuntu: New Bug description: My screen sometimes starts flashing strongly. I move the mouse cursor, it stops. I put the cursor back in its place, it starts again. I notice this with Firefox because I use it a lot, I don't know if this happens with other software. I'm under wayland (xwayland?) Description: Ubuntu 24.04 LTS Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 18:57:50 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84bb] InstallationDate: Installed on 2024-04-07 (16 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Pavilion Laptop 14-ce2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2022 dmi.bios.release: 15.27 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063228/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822
** Changed in: software-properties (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: [SRU] Software Sources is not compatible with deb822 Status in software-properties package in Ubuntu: Confirmed Status in software-properties source package in Noble: Confirmed Bug description: [ Impact ] Ubuntu 24.04 now uses deb822 to represent software sources for deb packages, instead of /etc/apt/sources.list. The complete rationale for this change can be found here: https://discourse.ubuntu.com/t/spec- apt-deb822-sources-by-default/29333 software-properties has two graphical frontends for editing these software sources, one is GTK-based and the other is Qt-based. When the underlying change to deb822 sources was made, the GTK-based frontend and the DBus backend interface gained support. The original bug report shown below informed us of the lack of deb822 support in the Qt frontend, which results in a broken, non-functional interface when attempting to view or edit most values on the first two tabs. The fix for this is to implement a Qt dialog for deb822 sources that somewhat matches the existing GTK interface. [ Test Plan ] Install software-properties-qt 0.99.48 or earlier. Reproducing the bug: 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. 2. Observe that all four checkboxes on the Ubuntu Software tab (main, universe, restricted, and multiverse) are unchecked. 3. Move to the Other Software tab and observe that there are no items in the list. Upgrade to software-properties-qt 0.99.49. Intended functionality: 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. 2. Observe that one or more checkboxes on the Ubuntu Software tab (representing main, universe, restricted, or multiverse) are checked. Toggle one or more of the checkboxes. 3. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. 4. Switch to the Other Software tab, there should be one item in the list. 5. Select that item, then click Edit at the bottom of the dialog. Make a modification to every field on the screen, or a combination of fields you would like to test. All fields should work. 6. Click the OK button at the bottom of the dialog to confirm the changes, then click Edit for that item again. The changes you made should be reflected (meaning, the changes were saved.) 7. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. [ Where problems could occur ] This is well-tested code. That being said, the following small edge cases exist: - If you create a very large amount of rows, it infinitely expands the dialog without a scroll wheel. This is the same functionality as the GTK frontend. - Error validation is not performed on the deb822 lines, they are simply written to the ubuntu.sources file. This is good as a starting point, but also relies on the appropriate update notifier handling these errors. This is the same functionality as the GTK frontend. In a future update, this functionality could be broken by one or more of the following underlying changes: - Changes to the software-properties backend which are only implemented for the GTK frontend. - Changes to the location or formatting of the ubuntu.sources file. - Regressions in the Python bindings for Qt 5, which are rare but possible. - Regressions in Python itself. [ Other Info ] Ubuntu Studio's live ISO and installed system are affected by this. Only Lubuntu's installed system is affected by this. [ Original Report ] Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 13 11:44:28 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240331) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/so
[Touch-packages] [Bug 1451978] Re: ubuntu-app-launch fails to install trying to access cache folder of another user
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: click (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1451978 Title: ubuntu-app-launch fails to install trying to access cache folder of another user Status in click package in Ubuntu: Confirmed Bug description: I'm experiencing problems updating my system. The exact issue can be narrowed down to the ubuntu-app-launch package failing to configure because it tries to access the cache folder of another user. > whoami rumo > sudo dpkg --configure ubuntu-app-launch ubuntu-app-launch (0.4+15.04.20150410-0ubuntu1) wird eingerichtet ... Traceback (most recent call last): File "/usr/bin/click", line 86, in sys.exit(main()) File "/usr/bin/click", line 82, in main return mod.run(args) File "/usr/lib/python3/dist-packages/click/commands/hook.py", line 63, in run getattr(hook, per_hook_subcommands[subcommand])(user_name=None) GLib.Error: g-file-error-quark: ensuredir /home/kalikiana/.cache/ubuntu-app-launch/desktop failed: Permission denied (2) dpkg: Fehler beim Bearbeiten des Paketes ubuntu-app-launch (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: ubuntu-app-launch ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-app-launch 0.4+15.04.20150410-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 5 20:38:20 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-07-03 (671 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: ubuntu-app-launch SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to vivid on 2014-11-21 (165 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1451978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: In Progress Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure
Adding Julian Andres Klode as a subscriber as seemingly this could only be due to the recent package update from aspell https://changelogs.ubuntu.com/changelogs/pool/main/a/aspell/aspell_0.60.8.1-1build1/changelog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure Status in aspell package in Ubuntu: New Status in dictionaries-common package in Ubuntu: New Bug description: this is running with LC_ALL=C the following are output in terminal when configuring dictionaries- common Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine &main::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dictionaries-common this worked without issues when I last built images of ubuntu-noble in late February 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809174] Re: apt doesn't detect file corruption in /var/lib/apt/lists
Just saw this on some field units that are iOT type devices and sometimes get shutdown non-cleanly. We run apt-update on startup and we noticed one machine would not update and had no knowledge of any packages in one of the repos in the sources.list. We noticed the Packages file has 0 size, and no amount of apt update or apt-cache clean could fix it besides deleting/removing the corrupt file. Deleting it resolved the issue: ``` $ ls -lat /var/lib/apt/lists/ total 71252 drwx-- 2 _apt root 4096 Apr 23 16:18 partial drwxr-xr-x 5 root root 4096 Apr 23 15:40 .. drwxr-xr-x 4 root root 4096 Apr 22 21:13 . -rw-r--r-- 1 root root 4342 Apr 22 20:12 [redacted-package-server]-experimental_dists_focal_InRelease -rw-r--r-- 1 root root0 Apr 22 20:12 [redacted-package-server]-experimental_dists_focal_main_binary-amd64_Packages -rw-r--r-- 1 root root 4362 Jan 27 2023 [redacted-package-server]-ubuntu-experimental_dists_focal_InRelease ``` Note the 0 file size on the `[redacted-package- server]-experimental_dists_focal_main_binary-amd64_Packages` file. During this time, it would not Get any new information from the package server. Even with updates pushed to the package server. After removing the file, it does a `Get` and now can see all the packages again: $ sudo mv /var/lib/apt/lists/[redacted-package-server]-experimental_dists_focal_main_binary-amd64_Packages $ sudo apt update Hit:1 [redacted-server]-experimental focal InRelease Hit:2 [redacted-server]-ubuntu-experimental focal InRelease Get:3 [redacted-server]-experimental focal/main amd64 Packages [3524 kB] Fetched 3524 kB in 6s (571 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 27 packages can be upgraded. Run 'apt list --upgradable' to see them. ``` Server software is aptly. apt version is `apt 2.0.6 (amd64)` Happy to track this down and submit a patch for checking the file size of 0, or the algorithm as suggested above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1809174 Title: apt doesn't detect file corruption in /var/lib/apt/lists Status in apt package in Ubuntu: Triaged Bug description: The Problem == /var/lib/apt/lists contains the repository index caches or similar; I'm not sure what the correct apt-terminology is. I've installed Chrome on my laptop, so I have: smacdonald@L247:/var/lib/apt/lists$ dir *goog* -rw-r--r-- 1 root root 943 Dec 19 14:02 dl.google.com_linux_chrome_deb_dists_stable_Release -rw-r--r-- 1 root root 819 Dec 19 14:02 dl.google.com_linux_chrome_deb_dists_stable_Release.gpg -rw-r--r-- 1 root root 4457 Dec 19 14:02 dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages for example. dl.google.com_linux_chrome_deb_dists_stable_Release contains checksums for the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages file: smacdonald@L247:/var/lib/apt/lists$ cat dl.google.com_linux_chrome_deb_dists_stable_Release Origin: Google LLC Label: Google Suite: stable Codename: stable Version: 1.0 Date: Wed, 19 Dec 2018 18:51:54 UTC Architectures: amd64 Components: main Description: Google chrome-linux software repository MD5Sum: 9e0d0ad6a4f5ccf8e3971c32e9bb22d3 4457 main/binary-amd64/Packages a17f6de0ef487b82af58ccd91df52d04 1109 main/binary-amd64/Packages.gz 156e5ea7a0c6bed5973a68a45e546dc9 151 main/binary-amd64/Release SHA1: 4c2cde4f71476d7881262d9a07e33cf4506232a7 4457 main/binary-amd64/Packages e002924c9ddfe41ee2033594ec768ed9e4545909 1109 main/binary-amd64/Packages.gz 0f4348c2d4d7cc1f8e59b5934d87f1ca872f6e34 151 main/binary-amd64/Release SHA256: fb0e586c2b5ec5afa17965d0bbc6bd46c2071336f75e2b0f0c7f3e7b090a7844 4457 main/binary-amd64/Packages 2462cff732765679a56373a7ca9a5b8b029fdb445e707b1aba10d01fbdb853b3 1109 main/binary-amd64/Packages.gz c1e3c9318381862306adcdc4fd4fe2d85be8aa4c4f3dcbb40fce80413f588286 151 main/binary-amd64/Release If the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages file has become corrupt in the specific manner of being 0 bytes in length, apt does not detect this, and the repository is effectively unreachable until one of two things occurs: a) the repository has an update causing apt to re-fetch the repository information and accidentally fix-by-over-writing the corrupt 0 byte file, or, b) the user removes the corrupt 0-byte file and does an apt update to refetch the repository information. The Context == Our IoT devices run Ubuntu 16.04, and their main storage is eMMC. Sometimes there are catastrophic
[Touch-packages] [Bug 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure
I'm unsubscribing as I only did a no-change rebuild. I'd generally advise against using LC_ALL=C in any setting however, it's generally a bad idea and you should use LC_ALL=C.UTF-8 instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure Status in aspell package in Ubuntu: New Status in dictionaries-common package in Ubuntu: New Bug description: this is running with LC_ALL=C the following are output in terminal when configuring dictionaries- common Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine &main::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dictionaries-common this worked without issues when I last built images of ubuntu-noble in late February 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
(In reply to dreamsyntax from comment #867) > While audio working, and content is playing (actively outputting to device) > Output is different: > i2cset -y 2 0x38 0x00 0x00 > i2cset -y 2 0x38 0x7f 0x00 > i2cdump -y 2 0x38 > No size specified (using byte-data access) > 0 1 2 3 4 5 6 7 8 9 a b c d e f0123456789abcdef > 00: 00 00 00 28 21 41 00 20 09 02 2a 28 10 93 02 00...(!A. ??*(???. > 10: 84 00 00 08 0a 00 44 80 00 8d 00 62 36 40 00 01?..??.D?.?.b6@.? > 20: 2e 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00.?.. > 30: 00 00 00 00 06 bd ad a8 00 00 00 fc bb dd ff ff...???.. > 40: f6 14 00 02 19 00 00 00 00 04 02 19 80 00 5c 00??.??.\. > 50: 00 06 a3 3c 85 08 81 da 87 84 00 97 d9 81 01 00.?? 60: 21 08 3c 48 84 88 b2 00 04 09 12 63 00 1a 03 00!? 70: 96 02 00 08 00 e0 00 00 0f 00 20 00 a0 00 25 00??.?.?..?. .?.%. > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Kindly follow Comment 872 to force tas2781 to work -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
Save following as tas2781-2dev-on.sh run ". tas2781-2dev-on.sh" in root mode during no sound, and check whether to work? Start### #!/bin/sh # echo Turn on log! # set -x clear function clear_stdin() ( old_tty_settings=`stty -g` stty -icanon min 0 time 0 while read none; do :; done stty "$old_tty_settings" ) if [ $# -ne 1 ]; then echo Kindly specify the i2c bus number. The default i2c bus number is 3. echo Command as following: echo $0 i2c-bus-number i2c_bus=3 else i2c_bus=$1 fi echo i2c bus is $i2c_bus i2c_addr=(0x3f 0x38) count=0 for value in ${i2c_addr[@]}; do val=$((${count} % 2)) i2cset -f -y $i2c_bus $value 0x00 0x00 i2cset -f -y $i2c_bus $value 0x7f 0x00 i2cset -f -y $i2c_bus $value 0x01 0x01 i2cset -f -y $i2c_bus $value 0x0e 0xc4 i2cset -f -y $i2c_bus $value 0x0f 0x40 i2cset -f -y $i2c_bus $value 0x5c 0xd9 i2cset -f -y $i2c_bus $value 0x60 0x10 if [ $val -eq 0 ]; then i2cset -f -y $i2c_bus $value 0x0a 0x1e else i2cset -f -y $i2c_bus $value 0x0a 0x2e fi i2cset -f -y $i2c_bus $value 0x0d 0x01 i2cset -f -y $i2c_bus $value 0x16 0x40 i2cset -f -y $i2c_bus $value 0x00 0x01 i2cset -f -y $i2c_bus $value 0x17 0xc8 i2cset -f -y $i2c_bus $value 0x00 0x04 i2cset -f -y $i2c_bus $value 0x30 0x00 i2cset -f -y $i2c_bus $value 0x31 0x00 i2cset -f -y $i2c_bus $value 0x32 0x00 i2cset -f -y $i2c_bus $value 0x33 0x01 i2cset -f -y $i2c_bus $value 0x00 0x08 i2cset -f -y $i2c_bus $value 0x18 0x00 i2cset -f -y $i2c_bus $value 0x19 0x00 i2cset -f -y $i2c_bus $value 0x1a 0x00 i2cset -f -y $i2c_bus $value 0x1b 0x00 i2cset -f -y $i2c_bus $value 0x28 0x40 i2cset -f -y $i2c_bus $value 0x29 0x00 i2cset -f -y $i2c_bus $value 0x2a 0x00 i2cset -f -y $i2c_bus $value 0x2b 0x00 i2cset -f -y $i2c_bus $value 0x00 0x0a i2cset -f -y $i2c_bus $value 0x48 0x00 i2cset -f -y $i2c_bus $value 0x49 0x00 i2cset -f -y $i2c_bus $value 0x4a 0x00 i2cset -f -y $i2c_bus $value 0x4b 0x00 i2cset -f -y $i2c_bus $value 0x58 0x40 i2cset -f -y $i2c_bus $value 0x59 0x00 i2cset -f -y $i2c_bus $value 0x5a 0x00 i2cset -f -y $i2c_bus $value 0x5b 0x00 i2cset -f -y $i2c_bus $value 0x00 0x00 i2cset -f -y $i2c_bus $value 0x02 0x00 count=$((${count} + 1)) done; clear_stdin End### -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WI
[Touch-packages] [Bug 1958019]
# . tas2781-2dev-on.sh 2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
(In reply to Tintin from comment #869) > kindly run > #i2cdetect -r 2 > and run following command during no sound issue > dmesg -c > kernel-mute.log Forgot to get the dmesg even though I did look at the dmesg output (*facepalm*). There are no messages related to this in dmesg when this occurs. But next time it happens, I'll get this to you to be thorough and Just In Case. i2cdetect -r 2 # When it's working: i2cdetect -y -r 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- 3f 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- # When it's not working: i2cdetect -y -r 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- 3f 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- I tried on i2cbus 0 and 1, no changes there either. This time I finally remembered to try hibernating (suspend to disk). Resuming didn't fix the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063257] [NEW] Noble: default pam config for login tries do load non-existent pam_lastlog.so
Public bug reported: pam_lastlog.so was dropped by upstream in 1.5.3[1][4]. It's still there in the code, but not built by default. And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2) does. This does not prevent console logins, but generates an error in the logs: Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so Debian's shadow package is also still shipping this config[2]. If you think we should re-enable pam_lastlog, then this becomes a bug in the src:pam package, but keep in mind upstream is keen on removing it, and we might be better off switching to an alternative, perhaps pam_lastlog2[3]. 1. https://github.com/linux-pam/linux-pam/blob/cec36a8cd2c69cc87eacc21da471334fbef128ee/NEWS#L65 2. https://salsa.debian.org/debian/shadow/-/blob/master/debian/login.pam?ref_type=heads#L82 3. https://wiki.debian.org/PamLastlog2 4. https://github.com/linux-pam/linux-pam/commit/357a4ddbe9b4b10ebd805d2af3e32f3ead5b8816 ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Affects: shadow (Ubuntu Noble) Importance: Undecided Status: New ** Affects: shadow (Debian) Importance: Unknown Status: Unknown ** Summary changed: - Default pam config for login tries do load non-existent pam module pam_lastlog.so + Noble: default pam config for login tries do load non-existent pam module pam_lastlog.so ** Also affects: shadow (Ubuntu Noble) Importance: Undecided Status: New ** Summary changed: - Noble: default pam config for login tries do load non-existent pam module pam_lastlog.so + Noble: default pam config for login tries do load non-existent pam_lastlog.so ** Description changed: pam_lastlog.so was dropped by upstream in 1.5.3[1]. It's still there in the code, but not built by default. And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2) does. - This does not prevent console logins, but generates an error in the logs: Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so + Debian's shadow package is also still shipping this config[2]. - Debian's shadow package is also still shipping this config[2]. + If you think we should re-enable pam_lastlog, then this becomes a bug in + the src:pam package, but keep in mind upstream is keen on removing it, + and we might be better off switching to an alternative, perhaps + pam_lastlog2[3]. 1. https://github.com/linux-pam/linux-pam/blob/cec36a8cd2c69cc87eacc21da471334fbef128ee/NEWS#L65 2. https://salsa.debian.org/debian/shadow/-/blob/master/debian/login.pam?ref_type=heads#L82 + 3. https://wiki.debian.org/PamLastlog2 ** Bug watch added: Debian Bug tracker #1068229 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068229 ** Also affects: shadow (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068229 Importance: Unknown Status: Unknown ** Description changed: - pam_lastlog.so was dropped by upstream in 1.5.3[1]. It's still there in - the code, but not built by default. + pam_lastlog.so was dropped by upstream in 1.5.3[1][4]. It's still there + in the code, but not built by default. And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2) does. This does not prevent console logins, but generates an error in the logs: Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so Debian's shadow package is also still shipping this config[2]. If you think we should re-enable pam_lastlog, then this becomes a bug in the src:pam package, but keep in mind upstream is keen on removing it, and we might be better off switching to an alternative, perhaps pam_lastlog2[3]. - 1. https://github.com/linux-pam/linux-pam/blob/cec36a8cd2c69cc87eacc21da471334fbef128ee/NEWS#L65 2. https://salsa.debian.org/debian/shadow/-/blob/master/debian/login.pam?ref_type=heads#L82 3. https://wiki.debian.org/PamLastlog2 + 4. https://github.com/linux-pam/linux-pam/commit/357a4ddbe9b4b10ebd805d2af3e32f3ead5b8816 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063257 Title: Noble: default pam config for login tries do load non-existent pam_lastlog.so Status in shadow package in Ubuntu: New Status in shadow source package in Noble: New Status in shadow package in Debian: Unknown Bug description: pam_lastlog.so was dropped by
[Touch-packages] [Bug 2063257] Re: Noble: default pam config for login tries do load non-existent pam_lastlog.so
** Changed in: shadow (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063257 Title: Noble: default pam config for login tries do load non-existent pam_lastlog.so Status in shadow package in Ubuntu: New Status in shadow source package in Noble: New Status in shadow package in Debian: New Bug description: pam_lastlog.so was dropped by upstream in 1.5.3[1][4]. It's still there in the code, but not built by default. And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2) does. This does not prevent console logins, but generates an error in the logs: Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so Debian's shadow package is also still shipping this config[2]. If you think we should re-enable pam_lastlog, then this becomes a bug in the src:pam package, but keep in mind upstream is keen on removing it, and we might be better off switching to an alternative, perhaps pam_lastlog2[3]. 1. https://github.com/linux-pam/linux-pam/blob/cec36a8cd2c69cc87eacc21da471334fbef128ee/NEWS#L65 2. https://salsa.debian.org/debian/shadow/-/blob/master/debian/login.pam?ref_type=heads#L82 3. https://wiki.debian.org/PamLastlog2 4. https://github.com/linux-pam/linux-pam/commit/357a4ddbe9b4b10ebd805d2af3e32f3ead5b8816 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039294] Re: apparmor docker
Forgot to attach the profile. Attached here. ** Attachment added: "docker-default" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2039294/+attachment/5769855/+files/docker-default -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2039294 Title: apparmor docker Status in docker: New Status in apparmor package in Ubuntu: Incomplete Bug description: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic Docker version 24.0.5, build 24.0.5-0ubuntu1 Graceful shutdown doesn't work anymore due to SIGTERM and SIGKILL (maybe all signals?) doesn't reach the target process. Works when apparmor is uninstalled. [17990.085295] audit: type=1400 audit(1697213244.019:981): apparmor="DENIED" operation="signal" class="signal" profile="docker-default" pid=172626 comm="runc" requested_mask="receive" denied_mask="receive" signal=term peer="/usr/sbin/runc" [17992.112517] audit: type=1400 audit(1697213246.043:982): apparmor="DENIED" operation="signal" class="signal" profile="docker-default" pid=172633 comm="runc" requested_mask="receive" denied_mask="receive" signal=kill peer="/usr/sbin/runc" To manage notifications about this bug go to: https://bugs.launchpad.net/docker/+bug/2039294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039294] Re: apparmor docker
As a temporary workaround, put the file I have attached to /etc/apparmor.d/docker-default and load it with "apparmor_parser -Kr /etc/apparmor.d/docker-default". This will make dockerd skip loading its builtin profile and use this one instead. The only difference between the builtin one and this one is the following rule: # runc may send signals to container processes signal (receive) peer=runc, I've opened PRs upstream: - https://github.com/containerd/containerd/pull/10123 - https://github.com/moby/moby/pull/47749 I think I'll need to work a little bit more on them to add rules only for profiles that exist. (It works even if they don't exist though.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2039294 Title: apparmor docker Status in docker: New Status in apparmor package in Ubuntu: Incomplete Bug description: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic Docker version 24.0.5, build 24.0.5-0ubuntu1 Graceful shutdown doesn't work anymore due to SIGTERM and SIGKILL (maybe all signals?) doesn't reach the target process. Works when apparmor is uninstalled. [17990.085295] audit: type=1400 audit(1697213244.019:981): apparmor="DENIED" operation="signal" class="signal" profile="docker-default" pid=172626 comm="runc" requested_mask="receive" denied_mask="receive" signal=term peer="/usr/sbin/runc" [17992.112517] audit: type=1400 audit(1697213246.043:982): apparmor="DENIED" operation="signal" class="signal" profile="docker-default" pid=172633 comm="runc" requested_mask="receive" denied_mask="receive" signal=kill peer="/usr/sbin/runc" To manage notifications about this bug go to: https://bugs.launchpad.net/docker/+bug/2039294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063271] Re: Illegal opcode in libssl
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2063271 Title: Illegal opcode in libssl Status in openssh package in Ubuntu: New Bug description: Many programs using openssl now fail, typically with messages such as Illegal instruction (core dumped) This seems to be a serious error, since it affects, for example, update-manager. Since this makes it harder to get security updates, I would also consider it a security vulnerability. The issue seems to be that openssl seems to be an attempt to use an illegal opcode. A few sample entries in /var/log/syslog are: Apr 21 19:16:39 einstein kernel: [495465.431588] traps: update-manager[396881] trap invalid opcode ip:740964b8ac6b sp:7409552125b0 error:0 in libssl.so.3[740964b7a000+5b000] Apr 21 19:16:55 einstein kernel: [495482.104658] traps: python3[396949] trap invalid opcode ip:73607be8ac6b sp:736074d8d5b0 error:0 in libssl.so.3[73607be7a000+5b000] Apr 21 19:40:05 einstein kernel: [496871.653271] traps: chrome-gnome-sh[397293] trap invalid opcode ip:79432ffa7c6b sp:7ffd6bc03e70 error:0 in libssl.so.3[79432ff97000+5b000] Apr 22 16:23:08 einstein kernel: [501744.765118] traps: check-new-relea[400397] trap invalid opcode ip:797c7cc8ac6b sp:797c6cace5b0 error:0 in libssl.so.3[797c7cc7a000+5b000] Apr 23 15:08:03 einstein kernel: [518701.050526] traps: wget[443588] trap invalid opcode ip:73a8b2eb4c6b sp:7ffc04918740 error:0 in libssl.so.3[73a8b2ea4000+5b000] Apr 23 15:12:55 einstein kernel: [518992.493020] traps: curl[443851] trap invalid opcode ip:7e4e3951dc6b sp:7ffc804d2ed0 error:0 in libssl.so.3[7e4e3950d000+5b000] Apr 23 15:13:32 einstein kernel: [519029.181422] traps: apport-gtk[04] trap invalid opcode ip:7039180f5c6b sp:703902bfaad0 error:0 in libssl.so.3[7039180e5000+5b000] This bug report itself had to be submitted manually since ubuntu-bug now itself fails. lsb_release -rd reports: Description:Ubuntu 22.04.4 LTS Release:22.04 apt-cache policy openssl reports: openssl: Installed: 3.0.2-0ubuntu1.15 Candidate: 3.0.2-0ubuntu1.15 Version table: *** 3.0.2-0ubuntu1.15 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages /proc/version for my computer gives Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 14:39:20 UTC 2 /proc/cpuinfo for my computer starts processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 78 model name: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz stepping : 3 microcode : 0xf0 cpu MHz : 500.018 cache size: 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid: 0 initial apicid: 0 fpu : yes fpu_exception : yes cpuid level : 22 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds mmio_stale_data retbleed gds bogomips : 5199.98 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2063271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063271] Re: Illegal opcode in libssl
Thanks for reporting this issue - but it is strange since this update has been published since 2024-02-27 and this is the first such report of any issues. Also given this update has been available for nearly 2 months it is surprising you are seeing errors from it so much later - I wonder if instead whether the on-disk binary has been corrupted? Can you please try reinstalling libssl3 and see if that resolves the issue: sudo apt install --reinstall libssl3 If this does resolve the issue, it might be worth checking whether you have any failing hardware / disks etc that may have led to this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2063271 Title: Illegal opcode in libssl Status in openssh package in Ubuntu: New Bug description: Many programs using openssl now fail, typically with messages such as Illegal instruction (core dumped) This seems to be a serious error, since it affects, for example, update-manager. Since this makes it harder to get security updates, I would also consider it a security vulnerability. The issue seems to be that openssl seems to be an attempt to use an illegal opcode. A few sample entries in /var/log/syslog are: Apr 21 19:16:39 einstein kernel: [495465.431588] traps: update-manager[396881] trap invalid opcode ip:740964b8ac6b sp:7409552125b0 error:0 in libssl.so.3[740964b7a000+5b000] Apr 21 19:16:55 einstein kernel: [495482.104658] traps: python3[396949] trap invalid opcode ip:73607be8ac6b sp:736074d8d5b0 error:0 in libssl.so.3[73607be7a000+5b000] Apr 21 19:40:05 einstein kernel: [496871.653271] traps: chrome-gnome-sh[397293] trap invalid opcode ip:79432ffa7c6b sp:7ffd6bc03e70 error:0 in libssl.so.3[79432ff97000+5b000] Apr 22 16:23:08 einstein kernel: [501744.765118] traps: check-new-relea[400397] trap invalid opcode ip:797c7cc8ac6b sp:797c6cace5b0 error:0 in libssl.so.3[797c7cc7a000+5b000] Apr 23 15:08:03 einstein kernel: [518701.050526] traps: wget[443588] trap invalid opcode ip:73a8b2eb4c6b sp:7ffc04918740 error:0 in libssl.so.3[73a8b2ea4000+5b000] Apr 23 15:12:55 einstein kernel: [518992.493020] traps: curl[443851] trap invalid opcode ip:7e4e3951dc6b sp:7ffc804d2ed0 error:0 in libssl.so.3[7e4e3950d000+5b000] Apr 23 15:13:32 einstein kernel: [519029.181422] traps: apport-gtk[04] trap invalid opcode ip:7039180f5c6b sp:703902bfaad0 error:0 in libssl.so.3[7039180e5000+5b000] This bug report itself had to be submitted manually since ubuntu-bug now itself fails. lsb_release -rd reports: Description:Ubuntu 22.04.4 LTS Release:22.04 apt-cache policy openssl reports: openssl: Installed: 3.0.2-0ubuntu1.15 Candidate: 3.0.2-0ubuntu1.15 Version table: *** 3.0.2-0ubuntu1.15 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages /proc/version for my computer gives Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 14:39:20 UTC 2 /proc/cpuinfo for my computer starts processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 78 model name: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz stepping : 3 microcode : 0xf0 cpu MHz : 500.018 cache size: 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid: 0 initial apicid: 0 fpu : yes fpu_exception : yes cpuid level : 22 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds mmio_stale_data retbleed gds bogomips : 5199.98 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 b
[Touch-packages] [Bug 2063228] Re: screen sometimes blinking
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063228 Title: screen sometimes blinking Status in xorg package in Ubuntu: Confirmed Bug description: My screen sometimes starts flashing strongly. I move the mouse cursor, it stops. I put the cursor back in its place, it starts again. I notice this with Firefox because I use it a lot, I don't know if this happens with other software. I'm under wayland (xwayland?) Description: Ubuntu 24.04 LTS Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 18:57:50 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84bb] InstallationDate: Installed on 2024-04-07 (16 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Pavilion Laptop 14-ce2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2022 dmi.bios.release: 15.27 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063228/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063271] Re: Illegal opcode in libssl
Thank you for your quick and helpful reply. A few quick checks make it appear that reinstalling libssl as you suggested has completely resolved the problem. Thanks also for your suggestion about checking failing hardware. There seems to be no sign of any errors in my drive, but I'll continue to test the drive and my RAM. Perhaps it was just a stray cosmic ray. Thanks again and best wishes to successful bug smashing! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2063271 Title: Illegal opcode in libssl Status in openssh package in Ubuntu: New Bug description: Many programs using openssl now fail, typically with messages such as Illegal instruction (core dumped) This seems to be a serious error, since it affects, for example, update-manager. Since this makes it harder to get security updates, I would also consider it a security vulnerability. The issue seems to be that openssl seems to be an attempt to use an illegal opcode. A few sample entries in /var/log/syslog are: Apr 21 19:16:39 einstein kernel: [495465.431588] traps: update-manager[396881] trap invalid opcode ip:740964b8ac6b sp:7409552125b0 error:0 in libssl.so.3[740964b7a000+5b000] Apr 21 19:16:55 einstein kernel: [495482.104658] traps: python3[396949] trap invalid opcode ip:73607be8ac6b sp:736074d8d5b0 error:0 in libssl.so.3[73607be7a000+5b000] Apr 21 19:40:05 einstein kernel: [496871.653271] traps: chrome-gnome-sh[397293] trap invalid opcode ip:79432ffa7c6b sp:7ffd6bc03e70 error:0 in libssl.so.3[79432ff97000+5b000] Apr 22 16:23:08 einstein kernel: [501744.765118] traps: check-new-relea[400397] trap invalid opcode ip:797c7cc8ac6b sp:797c6cace5b0 error:0 in libssl.so.3[797c7cc7a000+5b000] Apr 23 15:08:03 einstein kernel: [518701.050526] traps: wget[443588] trap invalid opcode ip:73a8b2eb4c6b sp:7ffc04918740 error:0 in libssl.so.3[73a8b2ea4000+5b000] Apr 23 15:12:55 einstein kernel: [518992.493020] traps: curl[443851] trap invalid opcode ip:7e4e3951dc6b sp:7ffc804d2ed0 error:0 in libssl.so.3[7e4e3950d000+5b000] Apr 23 15:13:32 einstein kernel: [519029.181422] traps: apport-gtk[04] trap invalid opcode ip:7039180f5c6b sp:703902bfaad0 error:0 in libssl.so.3[7039180e5000+5b000] This bug report itself had to be submitted manually since ubuntu-bug now itself fails. lsb_release -rd reports: Description:Ubuntu 22.04.4 LTS Release:22.04 apt-cache policy openssl reports: openssl: Installed: 3.0.2-0ubuntu1.15 Candidate: 3.0.2-0ubuntu1.15 Version table: *** 3.0.2-0ubuntu1.15 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages /proc/version for my computer gives Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 14:39:20 UTC 2 /proc/cpuinfo for my computer starts processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 78 model name: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz stepping : 3 microcode : 0xf0 cpu MHz : 500.018 cache size: 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid: 0 initial apicid: 0 fpu : yes fpu_exception : yes cpuid level : 22 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds mmio_stale_data retbleed gds bogomips : 5199.98 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2063271/+subscriptions -- Mailing list: ht
[Touch-packages] [Bug 2061869] Re: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3
*** This bug is a duplicate of bug 2061851 *** https://bugs.launchpad.net/bugs/2061851 ** This bug has been marked a duplicate of bug 2061851 linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression with new apparmor profiles/features -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2061869 Title: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3 Status in apparmor package in Ubuntu: Confirmed Status in linux-lowlatency package in Ubuntu: Confirmed Bug description: After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no longer connect to network. I tried downgrading snapd from edge, still no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also add apparmor in case this is an apparmor issue as well. Marking as "critical" priority as this affects all installs of Ubuntu Studio and affects Firefox and Thunderbird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063271] Re: Illegal opcode in libssl
** Package changed: openssh (Ubuntu) => openssl (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2063271 Title: Illegal opcode in libssl Status in openssl package in Ubuntu: New Bug description: Many programs using openssl now fail, typically with messages such as Illegal instruction (core dumped) This seems to be a serious error, since it affects, for example, update-manager. Since this makes it harder to get security updates, I would also consider it a security vulnerability. The issue seems to be that openssl seems to be an attempt to use an illegal opcode. A few sample entries in /var/log/syslog are: Apr 21 19:16:39 einstein kernel: [495465.431588] traps: update-manager[396881] trap invalid opcode ip:740964b8ac6b sp:7409552125b0 error:0 in libssl.so.3[740964b7a000+5b000] Apr 21 19:16:55 einstein kernel: [495482.104658] traps: python3[396949] trap invalid opcode ip:73607be8ac6b sp:736074d8d5b0 error:0 in libssl.so.3[73607be7a000+5b000] Apr 21 19:40:05 einstein kernel: [496871.653271] traps: chrome-gnome-sh[397293] trap invalid opcode ip:79432ffa7c6b sp:7ffd6bc03e70 error:0 in libssl.so.3[79432ff97000+5b000] Apr 22 16:23:08 einstein kernel: [501744.765118] traps: check-new-relea[400397] trap invalid opcode ip:797c7cc8ac6b sp:797c6cace5b0 error:0 in libssl.so.3[797c7cc7a000+5b000] Apr 23 15:08:03 einstein kernel: [518701.050526] traps: wget[443588] trap invalid opcode ip:73a8b2eb4c6b sp:7ffc04918740 error:0 in libssl.so.3[73a8b2ea4000+5b000] Apr 23 15:12:55 einstein kernel: [518992.493020] traps: curl[443851] trap invalid opcode ip:7e4e3951dc6b sp:7ffc804d2ed0 error:0 in libssl.so.3[7e4e3950d000+5b000] Apr 23 15:13:32 einstein kernel: [519029.181422] traps: apport-gtk[04] trap invalid opcode ip:7039180f5c6b sp:703902bfaad0 error:0 in libssl.so.3[7039180e5000+5b000] This bug report itself had to be submitted manually since ubuntu-bug now itself fails. lsb_release -rd reports: Description:Ubuntu 22.04.4 LTS Release:22.04 apt-cache policy openssl reports: openssl: Installed: 3.0.2-0ubuntu1.15 Candidate: 3.0.2-0ubuntu1.15 Version table: *** 3.0.2-0ubuntu1.15 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages /proc/version for my computer gives Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 14:39:20 UTC 2 /proc/cpuinfo for my computer starts processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 78 model name: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz stepping : 3 microcode : 0xf0 cpu MHz : 500.018 cache size: 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid: 0 initial apicid: 0 fpu : yes fpu_exception : yes cpuid level : 22 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds mmio_stale_data retbleed gds bogomips : 5199.98 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2063271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063222] Re: Ghost "unknown display" since upgrading to 24.04 beta
*** This bug is a duplicate of bug 2060268 *** https://bugs.launchpad.net/bugs/2060268 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2060268, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535 (Ubuntu) ** This bug has been marked a duplicate of bug 2060268 Phantom monitor (simpledrm) shown in Settings after installing the Nvidia driver -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063222 Title: Ghost "unknown display" since upgrading to 24.04 beta Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: X11 GNOME NVIDIA 4080 with their driver -> GNOME settings has a "ghost" display called "Unknown Display", its resolution is 1024 x 768 I only have one display attached - a 4K 27" DELL plugged into the NVIDIA ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4) ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 08:55:55 2024 DistUpgraded: 2024-04-14 17:14:28,561 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu DkmsStatus: nvidia/535.171.04, 6.8.0-28-generic, x86_64: installed nvidia/535.171.04, 6.8.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] AlderLake-S GT1 [1462:7d25] NVIDIA Corporation AD103 [GeForce RTX 4080] [10de:2704] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] AD103 [GeForce RTX 4080] [1462:5111] InstallationDate: Installed on 2022-04-30 (724 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7D25 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: root=UUID=43e064ac-5857-4c85-b15d-1dd96cdad27b ro quiet splash vt.handoff=7 initrd=boot\initrd.img-6.8.0-31-generic SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-15 (9 days ago) dmi.bios.date: 11/13/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.F0 dmi.board.asset.tag: Default string dmi.board.name: PRO Z690-A WIFI (MS-7D25) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.F0:bd11/13/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D25 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouv
[Touch-packages] [Bug 1811295] Re: systemctl daemon-reexec does not update group membership
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1811295 Title: systemctl daemon-reexec does not update group membership Status in systemd package in Ubuntu: Expired Bug description: On Ubuntu 16.04.4 LTS using Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Changes the group membership are not picked up by the systemd process for a logged-in user or for a user with enable-linger set regardless of login status. Evidently the systemctl --user daemon-reexec command preserves group membership across the daemon restart. This is bad. It means that only a reboot or sudo loginctl terminate-user will update the group membership to the proper set. Both of those things are extreme disruptions for a system/user that runs servers. Can systemctl daemon-reexec be made to update group membership for the user in the systemd process? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063298] [NEW] deprecate ubuntu-fan in Noble
Public bug reported: [Impact] In order to provide ubuntu-fan we need to maintain additional kernel SAUCE patches that are currently conflicting with upstream code, potentially breaking networking eBPF APIs. To prevent such incompatibility the whole patch set requires a major redesign. However, after investigations and a detailed assessment we have not found any relevant real-world use-case that still requuires ubuntu-fan, as most of its features are now available in the upstream kernel and user-space tools, using alternative solutions. Moreover, maintaining ubuntu-fan is also slowing down / preventing the development of other packages (see for example LP: #2051672). Therefore, we are proposing to deprecate ubuntu-fan starting with noble. [Test case] We have ubuntu-fan test cases in our regression testing suite. Such tests are expected to fail with the noble kernel, so we can hint/disable them in Noble. [Fix] Drop (do not apply) the ubuntu-fan SAUCE patch set from the Ubuntu kernel. [Regression potential] There are still some existing tools/systems that may still rely on ubuntu-fan, so we may experience regressions when such systems are moving to noble. However, the potential of breaking eBPF networking has a much higher impact, so we can probably workaround any potential ubuntu-fan regression using alternative upstream solutions. ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Affects: iproute2 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: iproute2 (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/2063298 Title: deprecate ubuntu-fan in Noble Status in iproute2 package in Ubuntu: New Status in iproute2 source package in Noble: New Bug description: [Impact] In order to provide ubuntu-fan we need to maintain additional kernel SAUCE patches that are currently conflicting with upstream code, potentially breaking networking eBPF APIs. To prevent such incompatibility the whole patch set requires a major redesign. However, after investigations and a detailed assessment we have not found any relevant real-world use-case that still requuires ubuntu- fan, as most of its features are now available in the upstream kernel and user-space tools, using alternative solutions. Moreover, maintaining ubuntu-fan is also slowing down / preventing the development of other packages (see for example LP: #2051672). Therefore, we are proposing to deprecate ubuntu-fan starting with noble. [Test case] We have ubuntu-fan test cases in our regression testing suite. Such tests are expected to fail with the noble kernel, so we can hint/disable them in Noble. [Fix] Drop (do not apply) the ubuntu-fan SAUCE patch set from the Ubuntu kernel. [Regression potential] There are still some existing tools/systems that may still rely on ubuntu-fan, so we may experience regressions when such systems are moving to noble. However, the potential of breaking eBPF networking has a much higher impact, so we can probably workaround any potential ubuntu-fan regression using alternative upstream solutions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2063298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063228] Re: screen sometimes blinking
Please try adding a kernel parameter: i915.enable_psr=0 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063228 Title: screen sometimes blinking Status in linux package in Ubuntu: Incomplete Bug description: My screen sometimes starts flashing strongly. I move the mouse cursor, it stops. I put the cursor back in its place, it starts again. I notice this with Firefox because I use it a lot, I don't know if this happens with other software. I'm under wayland (xwayland?) Description: Ubuntu 24.04 LTS Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 18:57:50 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84bb] InstallationDate: Installed on 2024-04-07 (16 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Pavilion Laptop 14-ce2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2022 dmi.bios.release: 15.27 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063228/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2061856] Re: Apps are closing immediately instead of launching
** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2061856 Title: Apps are closing immediately instead of launching Status in Ubuntu: Incomplete Bug description: Ola Bomdia Eu estou com um problema no terminal shell do ubuntu ele esta fechando assim que clico para abrir elefecha automaticamente ja tentetei usar outro terminal e tambem faz a mesma coisa eu tenho o fish instalado tambem mas esta fazendo a mesma coisa fechando automaticamente, o unico que funciona e o terminal do vscode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Apr 16 12:04:00 2024 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Core Processor Integrated Graphics Controller [1019:1324] InstallationDate: Installed on 2023-07-23 (267 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) Lsusb: Bus 002 Device 006: ID 04f3:0210 Elan Microelectronics Corp. Optical Mouse Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEGAWARE H55H-CM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic root=UUID=3cfdb2f5-e8ec-4728-844a-29c984321037 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MW-H55H-CM dmi.board.vendor: MEGAWARE dmi.board.version: 1.0 dmi.chassis.asset.tag: M0418501001 dmi.chassis.type: 3 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/18/2010:svnMEGAWARE:pnH55H-CM:pvrMEGAWARE:rvnMEGAWARE:rnMW-H55H-CM:rvr1.0:cvnMEGAWARE:ct3:cvr1.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: H55H-CM dmi.product.version: MEGAWARE dmi.sys.vendor: MEGAWARE version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.15 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Apr 4 13:22:01 2024 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPS/2+USB Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062550] Re: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit statu
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2062550 Title: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Upgrade from 22.04 LTS to 23.10 ProblemType: Package DistroRelease: Ubuntu 23.10 Package: systemd-resolved 253.5-1ubuntu6.1 ProcVersionSignature: Ubuntu 6.5.0-1020.21-oem 6.5.13 Uname: Linux 6.5.0-1020-oem x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 19 16:01:52 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-24 (178 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1.1 apt 2.7.3ubuntu0.1 SourcePackage: systemd Title: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2024-04-19 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-10-30T21:36:27.073262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2062550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
Thank you for your report! However, processing it in order to get sufficient information for the developers failed as the report has a core dump which is invalid. The corruption may have happened on the system which the crash occurred or during transit. Thank you for your understanding, and sorry for the inconvenience! ** Changed in: mesa (Ubuntu) Status: Triaged => Invalid ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2062146/+attachment/5767410/+files/CoreDump.gz ** Tags removed: need-arm64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile Status in Mesa: New Status in mesa package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: In Progress Status in yelp package in Ubuntu: New Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp