[Touch-packages] [Bug 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
Oh, in that case you'll want to look at /usr/share/apport/general- hooks/ubuntu.py which is provided by the apport package. -- 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/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2021956] Re: crash cups-proxyd
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2021956 Title: crash cups-proxyd Status in cups package in Ubuntu: Expired Bug description: Ubuntu IOT Desktop 22.04 LTS # cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy Kernel Version: 5.15.0-1028-intel-iotg # journalctl --no-hostname -b --no-pager | grep cups-proxyd mai 31 11:51:22 cups.cupsd[949]: + PROXY_DAEMON=cups-proxyd mai 31 11:51:22 cups.cupsd[3032]: exec cups-proxyd /var/snap/cups/common/run/cups.sock /run/cups/cups.sock -l --logdir /var/snap/cups/872/var/log mai 31 11:51:23 audit[3032]: SECCOMP auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:23 kernel: audit: type=1326 audit(1685523083.773:85): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:24 kernel: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Error: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Snap list: # snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base chromium 113.0.5672.1262477 latest/stable canonical✓ - core20 20230503 1891 latest/stable canonical✓ base core22 20230503 634latest/stable canonical✓ base cups 2.4.2-5 872latest/stable openprinting✓ - firefox111.0-2 2432 latest/stable/… mozilla✓ - gnome-3-38-20040+git.6f39565 140latest/stable/… canonical✓ - gnome-42-2204 0+git.587e965 102latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-71-g709398e 959latest/stable/… canonical✓ - snapd 2.59.219122 latest/stable canonical✓ snapd snapd-desktop-integration 0.9 83 latest/stable/… canonical✓ - Reproduced: At every boot OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2021956/+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 2027987] Re: Ubuntu mate mantic 23.10 failed to completely reboot into installed OS
[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/2027987 Title: Ubuntu mate mantic 23.10 failed to completely reboot into installed OS Status in systemd package in Ubuntu: Expired Bug description: QA Testing Build 20230717 Ubuntu mate mantic 23.10 failed to completely reboot into installed OS Systemd crashed OS failed to completely reboot into installed OS. Had to manually shutdown/restart virtual box to make bug report. Installer worked fine until the reboot. The remove media to reboot came on/ hit enter/Crashed..No reboot. Reproduced 2 times..same result. What should of happened- click remove media to reboot. Reboot into installed OS. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: systemd 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Jul 17 08:45:10 2023 InstallationDate: Installed on 2023-07-17 (0 days ago) InstallationMedia: Ubuntu-MATE 23.10 "Mantic Minotaur" - Daily amd64 (20230717) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic root=UUID=c396954f-1b91-404e-ad9d-599038ddfcf8 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2027987/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
I meant all bug reports, not just gnome-shell. But gnome-shell is the best place to start. -- 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/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 1870554] Re: ip-netns(8) unmounts /sys filesystem hierarchy within namespace
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iproute2 (Ubuntu) Status: New => Confirmed -- 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/1870554 Title: ip-netns(8) unmounts /sys filesystem hierarchy within namespace Status in iproute2 package in Ubuntu: Confirmed Bug description: Filesystems ordinarily mounted beneath /sys, particularly /sys/fs/cgroup, are not mounted within network namespaces created by ip-netns(8), as lib/namespace.c:netns_switch() explicitly remounts /sys. The patch enclosed removes the offending calls to umount2(2) and mount(2), leaving the /sys hierarchy intact within network namespaces. $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://fr2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Nota bene: this bug was reported in [1] (unresolved) and, on Arch Linux, [2]. References: [1] https://answers.launchpad.net/ubuntu/+source/iproute2/+question/659146 [2] https://bugs.archlinux.org/task/33328 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1870554/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
gnome-shell already ships an apport package hook which is installed in /usr/share/apport/package-hooks/source_gnome-shell.py and that seems to be debian/source_gnome-shell.py from the source package. It should be relatively straight forward to modify that and an update to it is something the SRU team would likely (I say likely due to the install base of gnome-shell) as an stable release update to the package. It is something the Ubuntu Release team would definitely accept as an update post Feature Freeze. -- 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/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
Indeed I've been meaning to learn about apport because I would like ALL bug reports to automatically come with: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt -- 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/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2018656] Re: login process frozen in between username and password
Still with the same error, I have already uninstalled Ubuntu and it continues to freeze when logging in. -- 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/2018656 Title: login process frozen in between username and password Status in gnome-online-accounts package in Ubuntu: Expired Bug description: MY SYSTEM No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 gnome-online-accounts: Installed: 3.48.0-1 Candidate: 3.48.0-1 Version table: *** 3.48.0-1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status I have tested this on my desktop running 23.04 on Intel I-9, and the second desktop running the same (23.04) but on Intel I-7, and both of them show the same problem. -PROBLEM--- When I entered my email address in my Google account, I could provide my email address, and after I clicked on the following form to enter my password. The form was able to pick up my email address and moved to the following form for password entry; it just froze in between. Sometimes, the password form could pick up the first keyboard character but never go past 2nd character. Sometimes, it just froze without being able to pick up the first keyboard character. Then a bit later, the whole box of gnome-online-accounts blacks out. Closing with X didn't work, so I had to xkill the app. -TYPICAL BEHAVIOR--- Usually, on 22.04, I never had a problem adding online accounts, particularly for Google accounts. The first form asked for my email address, and quickly moved on to the following form asking for a password. Once the password is accepted, it will move on to the next form requesting my authorization for GNOME to connect to my account on Google before adding it to my Ubuntu system (I'd see the drive folder on the bar on Nautilus). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-online-accounts 3.48.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 6 13:51:07 2023 InstallationDate: Installed on 2023-05-04 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2018656/+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 1971242] Re: printing PDF appears always grey, no color
Marc, thanks a lot for completing this one, as it has badly coincided
with my trip to India. And sorry for having let anyone to wait so long
...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Released
Status in cups source package in Lunar:
Fix Released
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
I added gnome-control-center and gnome-online-accounts tasks to help people find this issue easier. ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged -- 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/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in Webkit: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: Incomplete Status in webkit2gtk package in Debian: Confirmed Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of
[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
This behavior is not present in Mantic, so nothing to do there. I have staged fixes for Jammy and Lunar. ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: systemd (Ubuntu Lunar) Status: Triaged => In Progress ** Changed in: systemd (Ubuntu) Status: Triaged => 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: In Progress Status in systemd source package in Lunar: In Progress Bug description: [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/10-lxc.yaml # Use whatever editor you like $ cat /etc/netplan/10-lxc.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
** Description changed: [Impact] - When all interfaces "not required for online", e.g. when they are marked - "optional: true" in netplan, systemd-networkd-wait-online will timeout. - Or, in other words, systemd-networkd-wait-online will timeout even - though all interfaces are ignored, hence none of them will ever be + When all interfaces are "not required for online", e.g. when they are + marked "optional: true" in netplan, systemd-networkd-wait-online will + timeout. Or, in other words, systemd-networkd-wait-online will timeout + even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/10-lxc.yaml # Use whatever editor you like $ cat /etc/netplan/10-lxc.yaml network: - version: 2 - ethernets: - eth0: - dhcp4: true - dhcp-identifier: mac - optional: true + version: 2 + ethernets: + eth0: + dhcp4: true + dhcp-identifier: mac + optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re- introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Lunar: Triaged Bug description: [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/10-lxc.yaml # Use whatever editor you like $ cat /etc/netplan/10-lxc.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of
[Touch-packages] [Bug 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
Couldn't we modify the apport hook for gnome-shell to gather the relevant log file when ever there is a 'Signal: 6' in the crash report? -- 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/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2035778] Re: upstream autopkgtests fail to build test images
** Changed in: systemd (Ubuntu) Status: Triaged => Fix Committed -- 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/2035778 Title: upstream autopkgtests fail to build test images Status in systemd package in Ubuntu: Fix Committed Bug description: Example test log: https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/amd64/s/systemd/20230912_054033_0b699@/log.gz Basically every upstream test fails with odd errors. Early in the tests, a common default.img is supposed to be built, but this fails: 2614s I: Install time zones 2614s D: Installing /usr/share/zoneinfo/Asia/Seoul 2614s D: Installing /usr/share/zoneinfo/Asia/Vladivostok 2614s D: Installing /usr/share/zoneinfo/Australia/Sydney 2614s D: Installing /usr/share/zoneinfo/Europe/Berlin 2614s D: Installing /usr/share/zoneinfo/Europe/Dublin 2614s make: *** [Makefile:4: setup] Error 1 But, the tests continue anyways, without a complete test image, hence the odd errors. Looking at the test script, I found that it it is failing trying to install /usr/share/zoneinfo/Europe/Kiev, which is now called /usr/share/zoneinfo/Europe/Kyiv. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035778/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
** Description changed: + [Impact] + + When all interfaces "not required for online", e.g. when they are marked + "optional: true" in netplan, systemd-networkd-wait-online will timeout. + Or, in other words, systemd-networkd-wait-online will timeout even + though all interfaces are ignored, hence none of them will ever be + marked as "ready." Depending on what units depend on network- + online.target, this can delay boot by 120 seconds (the default timeout + for systemd-networkd-wait-online). + + [Test Plan] + + 1. Create a new LXD container. These instructions assume jammy is the + release, but the same can be done for lunar. + + $ lxc launch ubuntu-daily:jammy jammy + $ lxc exec jammy bash + + 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so + that eth0 is configured with "optional: true": + + $ vi /etc/netplan/10-lxc.yaml # Use whatever editor you like + $ cat /etc/netplan/10-lxc.yaml + network: + version: 2 + ethernets: + eth0: + dhcp4: true + dhcp-identifier: mac + optional: true + + 3. Re-generate and apply the netplan configuration. + + $ netplan generate + $ netplan apply + + 4. Manually run systemd-networkd-wait-online, and observe that all links + are ignored, and the command times out: + + $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 + Found link lo(1) + Found link eth0(19) + lo: link is ignored + eth0: link is ignored + Timeout occurred while waiting for network connectivity. + + [Where problems could occur] + + This patch partially re-instates a patch remove in bug 1982218. However, + instead of exiting if all links are unmanaged, we exit if all links are + ignored in manager_configured(). If the patch was wrong, we may re- + introduce bug 1982218, so as part of this SRU verification, that bug + should be tested too. Any other regressions would also be related to + systemd-networkd-wait-online behavior. + + [Original Description] + On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Lunar: Triaged Bug description: [Impact] When all interfaces "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/10-lxc.yaml # Use whatever editor you like $ cat /etc/netplan/10-lxc.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change
[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
I will work on re-instating the previous patch in some fashion to fix this bug without regressing 1982218. -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Lunar: Triaged Bug description: On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2036611] [NEW] FFe: Mesa 23.2.0
Public bug reported: Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is almost seven weeks past it's original release date. But at least we have an rc3 which is "only" two weeks old. Yes, we are getting close to mantic release but this series is something we want for Intel Meteor Lake support. This is now fresh in Debian unstable, and has been in Fedora 39/40 for a month already without any apparent drama. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Summary changed: - FFe: 23.2.0 + FFe: Mesa 23.2.0 -- 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/2036611 Title: FFe: Mesa 23.2.0 Status in mesa package in Ubuntu: New Bug description: Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is almost seven weeks past it's original release date. But at least we have an rc3 which is "only" two weeks old. Yes, we are getting close to mantic release but this series is something we want for Intel Meteor Lake support. This is now fresh in Debian unstable, and has been in Fedora 39/40 for a month already without any apparent drama. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2036611/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Also affects: systemd (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Jammy) Status: New => Triaged ** Changed in: systemd (Ubuntu Lunar) Status: New => Triaged ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu Lunar) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu Jammy) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd (Ubuntu Lunar) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Lunar: Triaged Bug description: On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2009808] Re: Doesn't display the correct livepatch service status
This was released in version 27.14 of ubuntu-advantage-tools but I forgot to include the LP number in the changelog so it didn't get automatically closed. Marking Fix Released now for u-a-t ** Changed in: ubuntu-advantage-tools (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2009808 Title: Doesn't display the correct livepatch service status Status in software-properties package in Ubuntu: Triaged Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Bug description: Starting a focal VM which didn't get updated the livepatch icon in the panel shows an orange warning and the popdown display a string saying it hit an error fetching the status $ canonical-livepatch status last check: 58 seconds ago kernel: 5.15.0-56.62~20.04.1-generic server check-in: failed: livepatch check failed: unauthorized patch state: ✗ kernel version not supported The software-properties tab doesn't give any clue about that though, maybe it should? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2009808/+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 2036598] Re: Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes
*** This bug is a duplicate of bug 2036358 *** https://bugs.launchpad.net/bugs/2036358 Thanks for the additional information. I am going to mark this bug as a duplicate to consolidate. ** This bug has been marked a duplicate of bug 2036358 systemd wait-online now times out after jammy and lunar upgrade -- 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/2036598 Title: Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes Status in systemd package in Ubuntu: Confirmed Bug description: After the update of systemd to version 249.11-0ubuntu3.10, the boot on the HiFive Unmatched board is stalled by about 2 minutes by systemd- networkd-wait-online. The error messages from /var/log/syslog: Sep 18 08:34:49 riscv64 systemd-networkd-wait-online[2898]: Timeout occurred while waiting for network connectivity. Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. This occurs on both Ubuntu 22.04 and 23.04 for riscv64. lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 apt-cache policy systemd systemd: Installed: 249.11-0ubuntu3.10 Candidate: 249.11-0ubuntu3.10 Version table: *** 249.11-0ubuntu3.10 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main riscv64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main riscv64 Packages 249.11-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main riscv64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036598/+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 2036598] Re: Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes
On SiFive HiFive Unmatched with Ubuntu Mantic (23.10): $ uname -a Linux unmatched2 6.2.0-19-generic grep -n wait-online /var/log/syslog 2023-09-19T13:38:34.120018+00:00 unmatched2 systemd[1]: Starting systemd-networkd-wait-online.service - Wait for Network to be Configured... 2023-09-19T13:38:36.306411+00:00 unmatched2 systemd[1]: Starting NetworkManager-wait-online.service - Network Manager Wait Online... $ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 end0 etherroutableconfigured 2 links listed. $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link end0(2) lo: link is ignored end0: link is configured by networkd and online. -- 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/2036598 Title: Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes Status in systemd package in Ubuntu: Confirmed Bug description: After the update of systemd to version 249.11-0ubuntu3.10, the boot on the HiFive Unmatched board is stalled by about 2 minutes by systemd- networkd-wait-online. The error messages from /var/log/syslog: Sep 18 08:34:49 riscv64 systemd-networkd-wait-online[2898]: Timeout occurred while waiting for network connectivity. Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. This occurs on both Ubuntu 22.04 and 23.04 for riscv64. lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 apt-cache policy systemd systemd: Installed: 249.11-0ubuntu3.10 Candidate: 249.11-0ubuntu3.10 Version table: *** 249.11-0ubuntu3.10 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main riscv64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main riscv64 Packages 249.11-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main riscv64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036598/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
It also affects Ubuntu Server 22.04 after updating to 249.11-0ubuntu3.10, since I'm on a headless server, I'm not using NetworkManager. On boot systemd-networkd-wait-online hangs and fails after a timeout. Here's my netplan configuration: $ cat /etc/netplan/00-installer-config.yaml # This is the network config written by 'subiquity' network: ethernets: enp2s0: addresses: [192.168.178.116/24] nameservers: addresses: [1.1.1.1,1.0.0.1] routes: - to: default via: 192.168.178.1 dhcp4: false dhcp6: false optional: true enp3s0: dhcp4: false dhcp6: false optional: true enp4s0: dhcp4: false dhcp6: false optional: true enp5s0: dhcp4: false dhcp6: false optional: true enp6s0: dhcp4: false dhcp6: false optional: true enp7s0: dhcp4: false dhcp6: false optional: true version: 2 cat /run/systemd/network/10-netplan-enp2s0.network [Match] Name=enp2s0 [Link] RequiredForOnline=no [Network] LinkLocalAddressing=ipv6 Address=192.168.178.116/24 DNS=1.1.1.1 DNS=1.0.0.1 [Route] Destination=0.0.0.0/0 Gateway=192.168.178.1 --- Other interfaces have also RequiredForOnline=no, hence they should be ignored by systemd-networkd-wait-online and it should not hang at boot. Also for me running SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd- networkd-wait-online --timeout=5 --any yelds: --- Found link 7 Found link 6 Found link 5 Found link 4 Found link 3 Found link 2 Found link 1 enp4s0: link is ignored enp6s0: link is ignored enp5s0: link is ignored enp2s0: link is ignored enp3s0: link is ignored lo: link is ignored enp7s0: link is ignored --- -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Confirmed Bug description: On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2036598] Re: Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes
Just a note, I did add --timeout=10 to systemd-networkd-wait- online.service to mitigate the issue. -- 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/2036598 Title: Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes Status in systemd package in Ubuntu: Confirmed Bug description: After the update of systemd to version 249.11-0ubuntu3.10, the boot on the HiFive Unmatched board is stalled by about 2 minutes by systemd- networkd-wait-online. The error messages from /var/log/syslog: Sep 18 08:34:49 riscv64 systemd-networkd-wait-online[2898]: Timeout occurred while waiting for network connectivity. Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. This occurs on both Ubuntu 22.04 and 23.04 for riscv64. lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 apt-cache policy systemd systemd: Installed: 249.11-0ubuntu3.10 Candidate: 249.11-0ubuntu3.10 Version table: *** 249.11-0ubuntu3.10 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main riscv64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main riscv64 Packages 249.11-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main riscv64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036598/+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 2036598] Re: Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes
$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 etherroutableconfigured 2 links listed. $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 rtnl: message parse - overwriting repeated attribute Found link 2 Found link 1 eth0: link is ignored lo: link is ignored Timeout occurred while waiting for network connectivity. -- 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/2036598 Title: Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes Status in systemd package in Ubuntu: Confirmed Bug description: After the update of systemd to version 249.11-0ubuntu3.10, the boot on the HiFive Unmatched board is stalled by about 2 minutes by systemd- networkd-wait-online. The error messages from /var/log/syslog: Sep 18 08:34:49 riscv64 systemd-networkd-wait-online[2898]: Timeout occurred while waiting for network connectivity. Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. This occurs on both Ubuntu 22.04 and 23.04 for riscv64. lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 apt-cache policy systemd systemd: Installed: 249.11-0ubuntu3.10 Candidate: 249.11-0ubuntu3.10 Version table: *** 249.11-0ubuntu3.10 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main riscv64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main riscv64 Packages 249.11-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main riscv64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036598/+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 2036598] Re: Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes
Thanks for your report. We have seen a similar report in bug 2036358. Before I mark it as duplicate, can you please provide output from the following commands: $ networkctl $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** 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/2036598 Title: Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes Status in systemd package in Ubuntu: Confirmed Bug description: After the update of systemd to version 249.11-0ubuntu3.10, the boot on the HiFive Unmatched board is stalled by about 2 minutes by systemd- networkd-wait-online. The error messages from /var/log/syslog: Sep 18 08:34:49 riscv64 systemd-networkd-wait-online[2898]: Timeout occurred while waiting for network connectivity. Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. This occurs on both Ubuntu 22.04 and 23.04 for riscv64. lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 apt-cache policy systemd systemd: Installed: 249.11-0ubuntu3.10 Candidate: 249.11-0ubuntu3.10 Version table: *** 249.11-0ubuntu3.10 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main riscv64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main riscv64 Packages 249.11-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main riscv64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036598/+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 2036598] [NEW] Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes
Public bug reported: After the update of systemd to version 249.11-0ubuntu3.10, the boot on the HiFive Unmatched board is stalled by about 2 minutes by systemd- networkd-wait-online. The error messages from /var/log/syslog: Sep 18 08:34:49 riscv64 systemd-networkd-wait-online[2898]: Timeout occurred while waiting for network connectivity. Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. This occurs on both Ubuntu 22.04 and 23.04 for riscv64. lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 apt-cache policy systemd systemd: Installed: 249.11-0ubuntu3.10 Candidate: 249.11-0ubuntu3.10 Version table: *** 249.11-0ubuntu3.10 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main riscv64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main riscv64 Packages 249.11-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main riscv64 Packages ** Affects: systemd (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/2036598 Title: Recent update of systemd stalls the boot on HiFive Unmatched for 2 minutes Status in systemd package in Ubuntu: New Bug description: After the update of systemd to version 249.11-0ubuntu3.10, the boot on the HiFive Unmatched board is stalled by about 2 minutes by systemd- networkd-wait-online. The error messages from /var/log/syslog: Sep 18 08:34:49 riscv64 systemd-networkd-wait-online[2898]: Timeout occurred while waiting for network connectivity. Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Sep 18 08:34:49 riscv64 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. This occurs on both Ubuntu 22.04 and 23.04 for riscv64. lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 apt-cache policy systemd systemd: Installed: 249.11-0ubuntu3.10 Candidate: 249.11-0ubuntu3.10 Version table: *** 249.11-0ubuntu3.10 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main riscv64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main riscv64 Packages 249.11-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main riscv64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036598/+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 1850804] Re: Tab completion warnings with ubuntu-bug when using alias for ls
Fix for it: https://github.com/canonical/apport/pull/222
You can apply the fix manually be editing /usr/share/bash-
completion/completions/apport-bug and changing the function to:
_apport_symptoms ()
{
local filename path symptoms
for path in /usr/share/apport/symptoms/*; do
[[ -e "$path" ]] || continue
filename="${path##*/}"
# hide utility files and symptoms that don't have a run() function
[[ ! "$filename" =~ ^_.* ]] || continue
grep -Eq "^def run\s*\(.*\):" "$path" || continue
symptoms+=("${filename%.py}")
done
echo "${symptoms[*]}"
}
** Changed in: apport
Status: New => In Progress
** 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/1850804
Title:
Tab completion warnings with ubuntu-bug when using alias for ls
Status in Apport:
In Progress
Status in apport package in Ubuntu:
In Progress
Bug description:
When running ubuntu-bug on the command line, and tab completing the
package name, the following warnings are printed:
/usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory
This happens when following alias is set:
alias ls='ls -N --color=yes --time-style=long-iso'
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apport 2.20.11-0ubuntu8.1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog:
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Oct 31 10:54:43 2019
InstallationDate: Installed on 2017-08-16 (805 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1850804/+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 1850804] Re: Tab completion warnings with ubuntu-bug when using alias for ls
** Also affects: apport Importance: Undecided Status: New ** Changed in: apport Milestone: None => 2.28.0 -- 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/1850804 Title: Tab completion warnings with ubuntu-bug when using alias for ls Status in Apport: New Status in apport package in Ubuntu: Triaged Bug description: When running ubuntu-bug on the command line, and tab completing the package name, the following warnings are printed: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory This happens when following alias is set: alias ls='ls -N --color=yes --time-style=long-iso' ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 31 10:54:43 2019 InstallationDate: Installed on 2017-08-16 (805 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1850804/+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 2036592] [NEW] Slow reported boot in VM
Public bug reported: systemd-analyze reports a slow boot in a virtual machine. Steps to reproduce: 1. Install ubuntu-23.04-desktop-amd64.iso in a VM (8 cores, 4 GB memory). Select all default but unselect requiring to enter the password to login 2. Reboot and install all updates 3. Reboot the virtual machine. The machine will take several seconds to boot and login 4. Open a terminal and enter systemd-analyze Expected total reported boot time on my hardware: around 3.5 seconds But I got: $ systemd-analyze Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs $ systemctl list-jobs JOB UNIT TYPE STATE 170 systemd-update-utmp-runlevel.service start waiting 156 system-getty.slice start waiting 1 graphical.target start waiting 104 plymouth-quit-wait.service start running 2 multi-user.targetstart waiting 40 setvtrgb.service start waiting 6 jobs listed. $ sleep 20 && systemd-analyze Startup finished in 1.603s (kernel) + 21.500s (userspace) = 23.103s graphical.target reached after 21.436s in userspace. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: systemd 252.5-2ubuntu3.1 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:49 2023 InstallationDate: Installed on 2023-09-19 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=45c33f38-bb4c-4a7c-8abc-9359992c8cb5 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.0-debian-1.16.0-5 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-5:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- 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/2036592 Title: Slow reported boot in VM Status in systemd package in Ubuntu: New Bug description: systemd-analyze reports a slow boot in a virtual machine. Steps to reproduce: 1. Install ubuntu-23.04-desktop-amd64.iso in a VM (8 cores, 4 GB memory). Select all default but unselect requiring to enter the password to login 2. Reboot and install all updates 3. Reboot the virtual machine. The machine will take several seconds to boot and login 4. Open a terminal and enter systemd-analyze Expected total reported boot time on my hardware: around 3.5 seconds But I got: $ systemd-analyze Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs $ systemctl list-jobs JOB UNIT TYPE STATE 170 systemd-update-utmp-runlevel.service start waiting 156 system-getty.slice start waiting 1 graphical.target start waiting 104 plymouth-quit-wait.service start running 2 multi-user.targetstart waiting 40 setvtrgb.service start waiting 6 jobs listed. $ sleep 20 && systemd-analyze Startup finished in 1.603s (kernel) + 21.500s (userspace) = 23.103s graphical.target reached after 21.436s in userspace. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: systemd 252.5-2ubuntu3.1 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:49 2023
[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug
I can confirm the behavior by setting the ls alias. Unsetting the alias will solve the issue. So apport should be made more robust against the alias. ** Changed in: apport (Ubuntu) Status: Confirmed => Triaged ** Description changed: When running ubuntu-bug on the command line, and tab completing the package name, the following warnings are printed: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory + + This happens when following alias is set: + + alias ls='ls -N --color=yes --time-style=long-iso' ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: - + ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 31 10:54:43 2019 InstallationDate: Installed on 2017-08-16 (805 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago) ** Tags added: lunar ** Summary changed: - Tab completion warnings with ubuntu-bug + Tab completion warnings with ubuntu-bug when using alias for ls -- 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/1850804 Title: Tab completion warnings with ubuntu-bug when using alias for ls Status in apport package in Ubuntu: Triaged Bug description: When running ubuntu-bug on the command line, and tab completing the package name, the following warnings are printed: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory This happens when following alias is set: alias ls='ls -N --color=yes --time-style=long-iso' ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 31 10:54:43 2019 InstallationDate: Installed on 2017-08-16 (805 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850804/+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 2036580] Re: Bluetooth won't turn on after upgrade to 23.10
*** This bug is a duplicate of bug 2036428 ***
https://bugs.launchpad.net/bugs/2036428
Looks like kernel 6.5 is missing required firmware?
[ 38.846558] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 38.846638] Bluetooth: hci0: Failed to load Intel firmware file
intel/ibt-19-0-4.sfi (-2)
[ 38.847516] Bluetooth: hci0: Reading supported features failed (-56)
[ 38.847533] Bluetooth: hci0: Error reading debug features
[ 38.848512] Bluetooth: hci0: Failed to read MSFT supported features (-56)
** Package changed: bluez (Ubuntu) => linux (Ubuntu)
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Bluetooth won't turn on after upgrade to 23.10
+ [Lenovo ThinkPad X1 Carbon Gen 8] Bluetooth won't turn on after upgrade to
23.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2036580
Title:
[Lenovo ThinkPad X1 Carbon Gen 8] Bluetooth won't turn on after
upgrade to 23.10
Status in linux package in Ubuntu:
New
Status in linux-firmware package in Ubuntu:
New
Bug description:
After upgrading from Ubuntu 23.04 to 23.10, Bluetooth won't turn on. I
click on the Unity gear wheel icon, then click on System Settings,
then on Bluetooth. The "Bluetooth" toggle is set to off, and the box
on the left says "Bluetooth is disabled". Clicking the toggle turns
the toggle on, but nothing else changes. The box on the left still
says that Bluetooth is disabled, and no Bluetooth icon shows on the
menu bar despite "Show Bluetooth status in the menu bar" being
enabled.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluetooth 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Sep 19 11:20:23 2023
InstallationDate: Installed on 2020-07-14 (1162 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro loglevel=4 splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to mantic on 2023-09-16 (3 days ago)
dmi.bios.date: 08/30/2022
dmi.bios.release: 1.28
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET38W (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias:
dmi:bvnLENOVO:bvrN2WET38W(1.28):bd08/30/2022:br1.28:efr1.15:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:55 acl:0 sco:0 events:4 errors:0
TX bytes:15 acl:0 sco:0 commands:4 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036580/+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 1850804] Re: Tab completion warnings with ubuntu-bug
This is still happening after upgrading to 23.10. -- 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/1850804 Title: Tab completion warnings with ubuntu-bug Status in apport package in Ubuntu: Confirmed Bug description: When running ubuntu-bug on the command line, and tab completing the package name, the following warnings are printed: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 31 10:54:43 2019 InstallationDate: Installed on 2017-08-16 (805 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850804/+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 2036580] [NEW] Bluetooth won't turn on after upgrade to 23.10
Public bug reported:
After upgrading from Ubuntu 23.04 to 23.10, Bluetooth won't turn on. I
click on the Unity gear wheel icon, then click on System Settings, then
on Bluetooth. The "Bluetooth" toggle is set to off, and the box on the
left says "Bluetooth is disabled". Clicking the toggle turns the toggle
on, but nothing else changes. The box on the left still says that
Bluetooth is disabled, and no Bluetooth icon shows on the menu bar
despite "Show Bluetooth status in the menu bar" being enabled.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluetooth 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Sep 19 11:20:23 2023
InstallationDate: Installed on 2020-07-14 (1162 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro loglevel=4 splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to mantic on 2023-09-16 (3 days ago)
dmi.bios.date: 08/30/2022
dmi.bios.release: 1.28
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET38W (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias:
dmi:bvnLENOVO:bvrN2WET38W(1.28):bd08/30/2022:br1.28:efr1.15:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:55 acl:0 sco:0 events:4 errors:0
TX bytes:15 acl:0 sco:0 commands:4 errors:0
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2036580
Title:
Bluetooth won't turn on after upgrade to 23.10
Status in bluez package in Ubuntu:
New
Bug description:
After upgrading from Ubuntu 23.04 to 23.10, Bluetooth won't turn on. I
click on the Unity gear wheel icon, then click on System Settings,
then on Bluetooth. The "Bluetooth" toggle is set to off, and the box
on the left says "Bluetooth is disabled". Clicking the toggle turns
the toggle on, but nothing else changes. The box on the left still
says that Bluetooth is disabled, and no Bluetooth icon shows on the
menu bar despite "Show Bluetooth status in the menu bar" being
enabled.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluetooth 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Sep 19 11:20:23 2023
InstallationDate: Installed on 2020-07-14 (1162 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro loglevel=4 splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to mantic on 2023-09-16 (3 days ago)
dmi.bios.date: 08/30/2022
dmi.bios.release: 1.28
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET38W (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias:
dmi:bvnLENOVO:bvrN2WET38W(1.28):bd08/30/2022:br1.28:efr1.15:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
[Touch-packages] [Bug 2033639] Re: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error
debug-me - 1.20221231-1ubuntu1 is available in PPA xypron/merge-from- debian. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2033639 Title: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error Status in binutils package in Ubuntu: New Status in debug-me package in Ubuntu: Triaged Bug description: debug-me 1.20221231-1 fails to build from source on ppc64el due to internal ld.gold error (binutils 2.41-4ubuntu1): ``` Linking dist/build/debug-me/debug-me ... /usr/bin/ld.gold: internal error in set_xindex, at ../../gold/object.h:1050 collect2: error: ld returned 1 exit status `powerpc64le-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1) ``` Full log: https://launchpadlibrarian.net/684538812/buildlog_ubuntu- mantic-ppc64el.debug-me_1.20221231-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2033639/+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 2033639] Re: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error
** Patch added: "debug-me-1.20221231-1..1.20221231-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/debug-me/+bug/2033639/+attachment/5701944/+files/debug-me-1.20221231-1..1.20221231-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2033639 Title: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error Status in binutils package in Ubuntu: New Status in debug-me package in Ubuntu: Triaged Bug description: debug-me 1.20221231-1 fails to build from source on ppc64el due to internal ld.gold error (binutils 2.41-4ubuntu1): ``` Linking dist/build/debug-me/debug-me ... /usr/bin/ld.gold: internal error in set_xindex, at ../../gold/object.h:1050 collect2: error: ld returned 1 exit status `powerpc64le-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1) ``` Full log: https://launchpadlibrarian.net/684538812/buildlog_ubuntu- mantic-ppc64el.debug-me_1.20221231-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2033639/+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 2033639] Re: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error
Building on ppc64el succeeds if LTO is disabled. ** Changed in: debug-me (Ubuntu) Assignee: (unassigned) => Heinrich Schuchardt (xypron) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2033639 Title: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error Status in binutils package in Ubuntu: New Status in debug-me package in Ubuntu: Triaged Bug description: debug-me 1.20221231-1 fails to build from source on ppc64el due to internal ld.gold error (binutils 2.41-4ubuntu1): ``` Linking dist/build/debug-me/debug-me ... /usr/bin/ld.gold: internal error in set_xindex, at ../../gold/object.h:1050 collect2: error: ld returned 1 exit status `powerpc64le-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1) ``` Full log: https://launchpadlibrarian.net/684538812/buildlog_ubuntu- mantic-ppc64el.debug-me_1.20221231-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2033639/+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 2036302] Re: apparmor 4.0.0~alpha2-0ubuntu3 ships same file as liblxc-common
This bug was fixed in the package apparmor - 4.0.0~alpha2-0ubuntu4 --- apparmor (4.0.0~alpha2-0ubuntu4) mantic; urgency=medium * Remove conflicting profile for usr.bin.lxc-start (LP: #2036302) - d/p/u/userns-unconfined-profiles.patch: Don't ship a profile for usr.bin.lxc-start as this is already shipped in liblxc-common - debian/apparmor.install: Remove usr.bin.lxc-start profile -- Alex Murray Mon, 18 Sep 2023 10:59:37 +0930 ** Changed in: apparmor (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2036302 Title: apparmor 4.0.0~alpha2-0ubuntu3 ships same file as liblxc-common Status in apparmor package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Bug description: When running apt-get distupgrade I saw this message: Preparing to unpack .../apparmor_4.0.0~alpha2-0ubuntu3_amd64.deb ... Unpacking apparmor (4.0.0~alpha2-0ubuntu3) over (4.0.0~alpha2-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/apparmor_4.0.0~alpha2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/etc/apparmor.d/usr.bin.lxc-start', which is also in package liblxc-common 1:5.0.1-0ubuntu6 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) The problem could be overcome with: sudo apt-get install liblxc-common --reinstall which resulted in output Preparing to unpack .../liblxc-common_1%3a5.0.1-0ubuntu6_amd64.deb ... Unpacking liblxc-common (1:5.0.1-0ubuntu6) over (1:5.0.1-0ubuntu6) ... I have seen the same type of problem before with other packages. I would have expected apt-get to correctly sequence all necessary actions on its own. These are related events in my apt history: Start-Date: 2022-10-30 05:33:09 Commandline: apt-get install lxc Requested-By: ubuntu (1000) Install: liblxc-common:amd64 (1:5.0.0~git2209-g5a7b9ce67-0ubuntu3, automatic) Start-Date: 2023-01-28 11:06:34 Commandline: apt-get dist-upgrade Requested-By: ubuntu (1000) Upgrade: liblxc-common:amd64 (1:5.0.0~git2209-g5a7b9ce67-0ubuntu3, 1:5.0.1-0ubuntu6) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apt 2.7.3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Sep 16 11:12:36 2023 InstallationDate: Installed on 2021-07-01 (807 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2036302/+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
