[Touch-packages] [Bug 2045754] Re: [A770] Graphics card driver crash
It looks like kwin didn't crash until after the kernel errors started so
let's make this about the kernel errors.
** Summary changed:
- Graphics card driver crash
+ [A770] Graphics card driver crash
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- [A770] Graphics card driver crash
+ [Arc A770] Graphics card driver crash
** Tags added: i915
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2045754
Title:
[Arc A770] Graphics card driver crash
Status in linux package in Ubuntu:
New
Bug description:
I was just browsing the web when the bottom half of the display became black,
the cursor froze, and everything started flickering.
I think eventually KDE crashed and some terminal messages were shown.
I Ctrl+alt+f3 to a terminal and shut down from there.
The terminal was glitchy with random artifacts but visible.
After reboot everything is working again for now.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Dec 6 12:03:24 2023
DistUpgraded: 2023-11-06 09:55:34,023 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation DG2 [Arc A770] [8086:1020]
InstallationDate: Installed on 2022-10-30 (402 days ago)
InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet
cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1
root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-06 (30 days ago)
dmi.bios.date: 05/18/2023
dmi.bios.release: 16.18
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1618
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X670E-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1618:bd05/18/2023:br16.18:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045754/+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 2045817] Re: [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in Ubuntu 23.10
** Summary changed: - Bluetooth issues in Ubuntu 23.10 + [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in Ubuntu 23.10 ** Package changed: bluez (Ubuntu) => linux (Ubuntu) -- 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/2045817 Title: [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in Ubuntu 23.10 Status in linux package in Ubuntu: New Bug description: similar to Bug #2019152, only in 23.10 with 6.5.0-12 thru 6.5.0-14 generic kernels. ❯ uname -a; lsb_release -a Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.10 Release: 23.10 Codename: mantic 2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c 2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception info failed (-16) 2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode 2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL 2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | trm_hw_status0 2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | trm_hw_status1 2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | branchlink2 2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink1 2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink2 2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1 2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2 2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3 2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon time 2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low 2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi 2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1 2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2 2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode revision type 2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode version major 2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode version minor 2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version 2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board version 2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd 2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0 2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1 2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2 2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3 2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4 2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd Id 2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event 2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | l2p_control 2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | l2p_duration 2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | l2p_mhvalid 2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | l2p_addr_match 2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | lmpm_pmg_sel 2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp 2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | flow_handler 2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 7 2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | ADVANCED_SYSASSERT 2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac branchlink1 2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac branchlink2 2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac interruptlink1 2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac interruptlink2 2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1
[Touch-packages] [Bug 2045753] Re: Ubuntu stuck on the boot screen
Thanks for the bug report.
Since you have both an unsupported Nvidia driver and unsupported kernel
installed, I'm going to close this bug.
Please uninstall the Nvidia driver and revert to an Ubuntu-provided
kernel, then reboot and reproduce the problem without 'nomodeset'. Once
you have done that, please reboot again with 'nomodeset' and run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file to a new bug.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2045753
Title:
Ubuntu stuck on the boot screen
Status in Ubuntu:
Invalid
Bug description:
I'm using nomodeset option as a workaround, but I'd prefer a permanent
solution.
I have no idea what I'm doing, so if I'm not specific enough, just ask.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
Uname: Linux 6.5.0-060500-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 6 11:42:55 2023
DistUpgraded: 2023-10-18 10:12:58,820 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
bbswitch/0.8, 6.5.0-060500-generic, x86_64: installed
bbswitch/0.8, 6.5.0-14-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-060500-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620]
[103c:8537]
InstallationDate: Installed on 2020-05-20 (1295 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-060500-generic
root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7
nomodeset
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-10-18 (49 days ago)
dmi.bios.date: 04/27/2020
dmi.bios.release: 11.1
dmi.bios.vendor: HP
dmi.bios.version: R71 Ver. 01.11.01
dmi.board.name: 8537
dmi.board.vendor: HP
dmi.board.version: KBC Version 51.2A.00
dmi.chassis.asset.tag: 5CD0097RK4
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 81.42
dmi.modalias:
dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:br11.1:efr81.42:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:sku5PQ09EA#AKD:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 440 G6
dmi.product.sku: 5PQ09EA#AKD
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2045753/+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 2043234] Re: Symlink for resolv.conf is wrong on fresh install
Well, I guess, it was only me then =D please close the ticket until issue will arise. Thanks -- 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/2043234 Title: Symlink for resolv.conf is wrong on fresh install Status in systemd package in Ubuntu: Invalid Bug description: Hello. Sorry for disturb, may I ask you please to confirm if im not doing anything wrong with new installation? Its being a while since the problem exists AT LEAST IN MY CASE with "faulty path" for symlinc at resolv.conf I believe its keep happening since 18.04 version and even now in 22.04 So, in the fresh install the path looks like this: lrwxrwxrwx 1 root root 39 Feb 17 2023 resolv.conf -> ../run/systemd/resolve/stub-resolv.conf but once im running : sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf everything works fine. By everything I mean when I run nslookup. Regards, Vitalii Sharapov To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234/+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 1986481] Re: Change value of ENCRYPT_METHOD option to YESCRYPT in /etc/login.defs
Any news about that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1986481 Title: Change value of ENCRYPT_METHOD option to YESCRYPT in /etc/login.defs Status in shadow package in Ubuntu: New Bug description: I'm using Ubuntu Kinetic and I found out the option ENCRYPT_METHOD in /etc/login.defs is still set to SHA512, even the recommended is to set to the same value as PAM (which is YESCRYPT). The idea it would change the value to YESCRYPT to keep the same value as PAM, that already uses yescrypt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1986481/+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 2045817] Re: Bluetooth issues in Ubuntu 23.10
** Package changed: ubuntu => bluez (Ubuntu) -- 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/2045817 Title: Bluetooth issues in Ubuntu 23.10 Status in bluez package in Ubuntu: New Bug description: similar to Bug #2019152, only in 23.10 with 6.5.0-12 thru 6.5.0-14 generic kernels. ❯ uname -a; lsb_release -a Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.10 Release: 23.10 Codename: mantic 2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c 2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception info failed (-16) 2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode 2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL 2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | trm_hw_status0 2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | trm_hw_status1 2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | branchlink2 2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink1 2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink2 2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1 2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2 2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3 2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon time 2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low 2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi 2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1 2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2 2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode revision type 2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode version major 2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode version minor 2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version 2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board version 2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd 2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0 2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1 2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2 2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3 2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4 2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd Id 2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event 2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | l2p_control 2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | l2p_duration 2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | l2p_mhvalid 2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | l2p_addr_match 2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | lmpm_pmg_sel 2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp 2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | flow_handler 2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 7 2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | ADVANCED_SYSASSERT 2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac branchlink1 2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac branchlink2 2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac interruptlink1 2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac interruptlink2 2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1 2023-12-06T16:03:58,985185-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data2 2023-12-06T16:03:58,985187-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data3 2023-12-06T16:03:58,985189-06:00 iwlwifi :00:14.3:
[Touch-packages] [Bug 2045817] [NEW] Bluetooth issues in Ubuntu 23.10
You have been subscribed to a public bug: similar to Bug #2019152, only in 23.10 with 6.5.0-12 thru 6.5.0-14 generic kernels. ❯ uname -a; lsb_release -a Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.10 Release: 23.10 Codename: mantic 2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c 2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception info failed (-16) 2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode 2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL 2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | trm_hw_status0 2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | trm_hw_status1 2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | branchlink2 2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink1 2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink2 2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1 2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2 2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3 2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon time 2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low 2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi 2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1 2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2 2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode revision type 2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode version major 2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode version minor 2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version 2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board version 2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd 2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0 2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1 2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2 2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3 2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4 2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd Id 2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event 2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | l2p_control 2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | l2p_duration 2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | l2p_mhvalid 2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | l2p_addr_match 2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | lmpm_pmg_sel 2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp 2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | flow_handler 2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 7 2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | ADVANCED_SYSASSERT 2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac branchlink1 2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac branchlink2 2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac interruptlink1 2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac interruptlink2 2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1 2023-12-06T16:03:58,985185-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data2 2023-12-06T16:03:58,985187-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data3 2023-12-06T16:03:58,985189-06:00 iwlwifi :00:14.3: 0x0053 | umac major 2023-12-06T16:03:58,985191-06:00 iwlwifi :00:14.3: 0xE8F84E98 | umac minor 2023-12-06T16:03:58,985193-06:00 iwlwifi :00:14.3: 0x7C0B3384 | frame pointer 2023-12-06T16:03:58,985195-06:00 iwlwifi :00:14.3: 0xC0886BE0 | stack pointer 2023-12-06T16:03:58,985197-06:00 iwlwifi :00:14.3: 0x00ED019C | last host cmd 2023-12-06T16:03:58,985199-06:00 iwlwifi :00:14.3: 0x |
[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap
@wallento and @jose+ubu1, could you please run the command ps aux | grep cups-proxyd and post the output here and also could you attach the files /var/snap/cups/current/var/log/cups-proxyd_log /var/snap/cups/current/var/log/error_log /var/log/cups/error_log Attach the files one by one, in separate comments, and do not compress them, this way I will be able to easily read right out of the browser. -- 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 2045570] Re: dnsmasq crash when no servers in resolv.conf
I was able to reproduce this after a few attempts. Good enough for a test plan/case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2045570 Title: dnsmasq crash when no servers in resolv.conf Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Triaged Bug description: upstream discussion: https://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2022q3/016563.html in my journal, my dns service crash and restart just after: Dec 04 17:18:38 dnsmasq[199333]: no servers found in /run/NetworkManager/no-stub-resolv.conf, will retry oops report: https://errors.ubuntu.com/oops/29cf5e2e-92b1-11ee-9bdf- fa163ec44ecd ubuntu jammy, dnsmasq-base 2.86-1.1ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2045570/+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
Re: [Touch-packages] [Bug 2023322] Re: GTK internal browser does not render with Nvidia drivers
I just recently upgraded to Ubuntu 23.10 and the issues are gone. I was able to create my google account just fine under 23.10 On Tue, Dec 5, 2023 at 7:50 PM Jeremy Bícha <2023...@bugs.launchpad.net> wrote: > That bug was filed before we fixed Jammy on 2023-11-20 > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2027737). > https://bugs.launchpad.net/bugs/2023322 > > Title: > GTK internal browser does not render with Nvidia drivers > > Status in Webkit: > Confirmed > Status in gnome-control-center package in Ubuntu: > Invalid > Status in gnome-online-accounts package in Ubuntu: > Invalid > Status in webkit2gtk package in Ubuntu: > Fix Released > Status in yelp package in Ubuntu: > Invalid > Status in webkit2gtk package in Debian: > Fix Released > > 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 Temporary Directories. > Jun
[Touch-packages] [Bug 2043234] Re: Symlink for resolv.conf is wrong on fresh install
Yes, I am aware of the path. This is what I see on a fresh jammy install: nr@clean-jammy-amd64:~$ readlink /etc/resolv.conf ../run/systemd/resolve/stub-resolv.conf nr@clean-jammy-amd64:~$ nslookup google.com Server: 127.0.0.53 Address:127.0.0.53#53 Non-authoritative answer: Name: google.com Address: 142.251.40.142 Name: google.com Address: 2607:f8b0:4006:80f::200e -- 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/2043234 Title: Symlink for resolv.conf is wrong on fresh install Status in systemd package in Ubuntu: Invalid Bug description: Hello. Sorry for disturb, may I ask you please to confirm if im not doing anything wrong with new installation? Its being a while since the problem exists AT LEAST IN MY CASE with "faulty path" for symlinc at resolv.conf I believe its keep happening since 18.04 version and even now in 22.04 So, in the fresh install the path looks like this: lrwxrwxrwx 1 root root 39 Feb 17 2023 resolv.conf -> ../run/systemd/resolve/stub-resolv.conf but once im running : sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf everything works fine. By everything I mean when I run nslookup. Regards, Vitalii Sharapov To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234/+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 2024680] Re: Dell XPS 9730 no sound, I have tried the 22.04 lts same issue
Had encountered the same issue on 22.04. Applying this patch https://github.com/torvalds/linux/commit/43e354dada62c0425db900f327a6e11babefcf5c seems to work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2024680 Title: Dell XPS 9730 no sound, I have tried the 22.04 lts same issue Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've tried various fixes without success, I did manage to get the NVIDA HDMI in the sound options but I've never had the inbuilt Intel Media Hardware working for sound. 22.04 LTS had the same issue and I've upgraded to the new version 23.04 which looks good. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2245 F wireplumber /dev/snd/seq:daniel 2241 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 22 17:30:27 2023 InstallationDate: Installed on 2023-06-16 (5 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 067X4F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd03/23/2023:br1.2:efr1.1:svnDellInc.:pnXPS179730:pvr:rvnDellInc.:rn067X4F:rvrA00:cvnDellInc.:ct10:cvr:sku0BDB: dmi.product.family: XPS dmi.product.name: XPS 17 9730 dmi.product.sku: 0BDB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2024680/+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 2045570] Re: dnsmasq crash when no servers in resolv.conf
** Changed in: dnsmasq (Ubuntu Jammy) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2045570 Title: dnsmasq crash when no servers in resolv.conf Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Triaged Bug description: upstream discussion: https://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2022q3/016563.html in my journal, my dns service crash and restart just after: Dec 04 17:18:38 dnsmasq[199333]: no servers found in /run/NetworkManager/no-stub-resolv.conf, will retry oops report: https://errors.ubuntu.com/oops/29cf5e2e-92b1-11ee-9bdf- fa163ec44ecd ubuntu jammy, dnsmasq-base 2.86-1.1ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2045570/+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 2020838] Re: [regression][jammy] augenrules Error sending add rule data request (No such file or directory)
@Seth I just want to say that I am that person! I signed up specifically to thank @Chuan and you for getting to the bottom of this. I had the exact same error and setting `ProtectHome=false` solved the issue, thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/2020838 Title: [regression][jammy] augenrules Error sending add rule data request (No such file or directory) Status in audit package in Ubuntu: New Bug description: The rule '-a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged' can not be loaded during system boot up. # lsb_release -rc Release: 22.04 Codename: jammy # dpkg -l|grep audit ii auditd 1:3.0.7-1build1 amd64User space tools for security auditing ii libaudit-common 1:3.0.7-1build1 all Dynamic library for security auditing - common files ii libaudit1:amd64 1:3.0.7-1build1 amd64Dynamic library for security auditing ii libauparse0:amd64 1:3.0.7-1build1 amd64Dynamic library for parsing security auditing # cat /etc/audit/rules.d/audit.rules|grep -v ^#|grep -v ^$ -D -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts -b 8192 --backlog_wait_time 6 -f 1 # ls -l /home/ubuntu/test.sh -rwxr-xr-x 1 root ubuntu 19 May 25 14:19 /home/ubuntu/test.sh # cat /home/ubuntu/test.sh #!/bin/bash echo 1 # >/etc/audit/audit.rules reboot the system, no rule can be loaded # auditctl -l No rules syslog: May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: Error sending add rule data request (No such file or directory) May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: There was an error in line 5 of /etc/audit/audit.rules May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: No rules May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0 # cat /etc/audit/audit.rules ## This file is automatically generated from /etc/audit/rules.d -D -b 8192 -f 1 -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts --backlog_wait_time 6 But I can manually load the rule file. Seems this issue only happen during system boot up. # auditctl -R /etc/audit/audit.rules No rules enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 4 backlog_wait_time 15000 backlog_wait_time_actual 0 enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 4 backlog_wait_time 15000 backlog_wait_time_actual 0 enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 14 backlog_wait_time 6 backlog_wait_time_actual 0 # auditctl -l -a always,exit -S all -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=-1 -F key=mounts If I move the file /home/ubuntu/test.sh to / opt/test.sh or /etc/test.sh /usr/bin/test.sh, then I can not reproduce the issue. Additionally, I have ruled out AppArmor as a factor. I have already disabled the AppArmor service and append "apparmor=0" into the kernel command line before rebooting. Moreover, I can NOT reproduce this issue on Focal(1:2.8.5-2ubuntu6) There are 2 issues here, I think 1) If the rules can
[Touch-packages] [Bug 2031252] Re: Playing video with audio freezes
This is still happening for me under Ubuntu 23.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2031252 Title: Playing video with audio freezes Status in alsa-driver package in Ubuntu: New Bug description: I'm not sure when this started, but any video I play with audio is not working properly - it severely lags and/or freezes. This happens in Youtube on both Chrome and Firefox, and in the regular GNOME media player. Audio by itself works fine, and video with audio muted works fine. I tried restarting and downgrading the kernel, to no avail. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ari2679 F pipewire ari2700 F wireplumber /dev/snd/seq:ari2679 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 13 17:22:56 2023 InstallationDate: Installed on 2022-06-07 (432 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-07-20 (23 days ago) dmi.bios.date: 06/12/2023 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET85W (1.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrN32ET85W(1.61):bd06/12/2023:br1.61:efr1.34:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2031252/+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 2045756] Re: systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected
Thanks Nick, your suggestion works fine. Let's see where it makes sense
to add the overlay to our images.
** Changed in: cloud-init (Ubuntu)
Status: New => 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/2045756
Title:
systemd-networkd-wait-online.service fails to complete if one of the
network interfaces is not physically connected
Status in cloud-init package in Ubuntu:
Invalid
Status in netplan.io package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
Bug description:
My StarFive VisionFive 2 board has two network interfaces of which I
have only connected one to a switch. The systemd-networkd-wait-
online.service always fails delaying boot by 150 s. The problem does
not occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network
interface that is not physically connected.
As described in
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
the physical link state can be determined via
/sys/class/net//carrier.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Dec 6 10:57:52 2023
InstallationDate: Installed on 2023-12-04 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2045756/+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 2045577] Re: Demote isc-dhcp-server to universe
Thanks, Christian! WONTFIX MIR LP bug: LP: #2045771 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2045577 Title: Demote isc-dhcp-server to universe Status in isc-dhcp package in Ubuntu: Fix Released Bug description: Following up on the isc-kea promotion (LP: #2002861) as the new supported DHCP server, it is now time to demote isc-dhcp-server. All the packages that are in. While we are not ready to demote all isc-dhcp packages (there are still packages in main that reverse depend/recommend isc-dhcp-client), we are ready to demote isc-dhcp-server. $ reverse-depends isc-dhcp-server Reverse-Recommends == * fai-server Reverse-Depends === * fai-quickstart * isc-dhcp-server-ldap [amd64 arm64 armhf ppc64el s390x] Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b isc-dhcp-server Reverse-Testsuite-Triggers == * chrony * dracut As shown there are no reverse dependencies for isc-dhcp-server in main. There are Reverse-Testsuite-Triggers in main, but these should not be considered for demotion matters here. The seeds at https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/?h=noble contain 2 entries for isc-dhcp- server: $ grep -r isc-dhcp-server * supported-maas: * isc-dhcp-server supported-misc-servers: * isc-dhcp-server I will proceed with removing the supported-misc-servers entry. Once this is removed from supported-maas, the package will no longer be seeded (we should then get a component mismatch) and can be safely demoted to universe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2045577/+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 2045771] [NEW] [MIR] isc-dhcp-server
Public bug reported: This was demoted due to LP: #2045577. This will keep showing in component mismatches as ipmitool for now. Please, do not move it back to main for the time being. See LP: #2045577 for further reference. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: Won't Fix ** Changed in: isc-dhcp (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2045771 Title: [MIR] isc-dhcp-server Status in isc-dhcp package in Ubuntu: Won't Fix Bug description: This was demoted due to LP: #2045577. This will keep showing in component mismatches as ipmitool for now. Please, do not move it back to main for the time being. See LP: #2045577 for further reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2045771/+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 2045576] Re: Please merge 0.52.24-1 into noble
** Changed in: newt (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/2045576 Title: Please merge 0.52.24-1 into noble Status in newt package in Ubuntu: Fix Committed Bug description: The upstream version 0.52.24-1 should be merged into noble. The current version is 0.52.23-1ubuntu2. * PPA for review: https://launchpad.net/~mateus- morais/+archive/ubuntu/newt-merge Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/2045576/+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 2045577] Re: Demote isc-dhcp-server to universe
Hi Athos, agreed: According to [1] all that is holding it back is MAAS still referrring to it. But I'm afraid of doing the demotion last minute as a surprise to the wider Ubuntu. The MAAS team has been involved in planning and preparing for this. They have committed to get rid of their dependency. And then OTOH the supported-maas seed also does depend and show imptools all the time and it was left open. So ack, we want to demote this right now to make sure everyone, and not just MAAS, is more even more aware. The source can not yet move as Foundations works on letting the client fully go. Demoted in proposed and will go to noble in full once 4.4.3-P1-4ubuntu1 migrates. Override component to universe isc-dhcp-server 4.4.3-P1-4ubuntu1 in noble amd64: main/net/optional/100% -> universe isc-dhcp-server 4.4.3-P1-4ubuntu1 in noble arm64: main/net/optional/100% -> universe isc-dhcp-server 4.4.3-P1-4ubuntu1 in noble armhf: main/net/optional/100% -> universe isc-dhcp-server 4.4.3-P1-4ubuntu1 in noble ppc64el: main/net/optional/100% -> universe isc-dhcp-server 4.4.3-P1-4ubuntu1 in noble riscv64: main/net/optional/100% -> universe isc-dhcp-server 4.4.3-P1-4ubuntu1 in noble s390x: main/net/optional/100% -> universe Override [y|N]? y 6 publications overridden @Athos - please create a MIR bug saying "Won't Fix" and some reference to this and the rest of the history. To be found by component mismatches, otherwise another friendly archive admin will just re-promote it. [1]: https://ubuntu-archive-team.ubuntu.com/germinate- output/ubuntu.jammy/rdepends/isc-dhcp/isc-dhcp-server ** Changed in: isc-dhcp (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 isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2045577 Title: Demote isc-dhcp-server to universe Status in isc-dhcp package in Ubuntu: Fix Released Bug description: Following up on the isc-kea promotion (LP: #2002861) as the new supported DHCP server, it is now time to demote isc-dhcp-server. All the packages that are in. While we are not ready to demote all isc-dhcp packages (there are still packages in main that reverse depend/recommend isc-dhcp-client), we are ready to demote isc-dhcp-server. $ reverse-depends isc-dhcp-server Reverse-Recommends == * fai-server Reverse-Depends === * fai-quickstart * isc-dhcp-server-ldap [amd64 arm64 armhf ppc64el s390x] Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b isc-dhcp-server Reverse-Testsuite-Triggers == * chrony * dracut As shown there are no reverse dependencies for isc-dhcp-server in main. There are Reverse-Testsuite-Triggers in main, but these should not be considered for demotion matters here. The seeds at https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/?h=noble contain 2 entries for isc-dhcp- server: $ grep -r isc-dhcp-server * supported-maas: * isc-dhcp-server supported-misc-servers: * isc-dhcp-server I will proceed with removing the supported-misc-servers entry. Once this is removed from supported-maas, the package will no longer be seeded (we should then get a component mismatch) and can be safely demoted to universe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2045577/+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 2045576] Re: Please merge 0.52.24-1 into noble
** Changed in: newt (Ubuntu) Assignee: Mateus Rodrigues de Morais (mateus-morais) => Graham Inggs (ginggs) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/2045576 Title: Please merge 0.52.24-1 into noble Status in newt package in Ubuntu: In Progress Bug description: The upstream version 0.52.24-1 should be merged into noble. The current version is 0.52.23-1ubuntu2. * PPA for review: https://launchpad.net/~mateus- morais/+archive/ubuntu/newt-merge Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/2045576/+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 2045756] Re: systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected
cloud-init could check the availability of the carrier at installation
time and add 'optional: true' in cloudinit/net/netplan.py. But this
would only reflect the state at the time of installation.
--
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/2045756
Title:
systemd-networkd-wait-online.service fails to complete if one of the
network interfaces is not physically connected
Status in cloud-init package in Ubuntu:
New
Status in netplan.io package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
Bug description:
My StarFive VisionFive 2 board has two network interfaces of which I
have only connected one to a switch. The systemd-networkd-wait-
online.service always fails delaying boot by 150 s. The problem does
not occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network
interface that is not physically connected.
As described in
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
the physical link state can be determined via
/sys/class/net//carrier.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Dec 6 10:57:52 2023
InstallationDate: Installed on 2023-12-04 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2045756/+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 2045756] Re: systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected
As Yu said on the upstream bug, this is the expected default behavior
for systemd-networkd-wait-online. You can make it more tailored to your
use case, e.g. by writing an override like this:
# /etc/systemd/system/systemd-networkd-wait-online.service.d/override.conf
[Service]
ExecStart=
ExecStart=/lib/systemd/systemd-networkd-wait-online --any
Or, if you always want the same interface, pass --interface $name
instead.
--
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/2045756
Title:
systemd-networkd-wait-online.service fails to complete if one of the
network interfaces is not physically connected
Status in cloud-init package in Ubuntu:
New
Status in netplan.io package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
Bug description:
My StarFive VisionFive 2 board has two network interfaces of which I
have only connected one to a switch. The systemd-networkd-wait-
online.service always fails delaying boot by 150 s. The problem does
not occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network
interface that is not physically connected.
As described in
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
the physical link state can be determined via
/sys/class/net//carrier.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Dec 6 10:57:52 2023
InstallationDate: Installed on 2023-12-04 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2045756/+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 2045756] Re: systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected
Probably cloud-init's cloudinit/net/netplan.py should add "optional:
true" to interfaces that have no carrier.
** Changed in: netplan.io (Ubuntu)
Status: Incomplete => Invalid
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => 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/2045756
Title:
systemd-networkd-wait-online.service fails to complete if one of the
network interfaces is not physically connected
Status in cloud-init package in Ubuntu:
New
Status in netplan.io package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
Bug description:
My StarFive VisionFive 2 board has two network interfaces of which I
have only connected one to a switch. The systemd-networkd-wait-
online.service always fails delaying boot by 150 s. The problem does
not occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network
interface that is not physically connected.
As described in
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
the physical link state can be determined via
/sys/class/net//carrier.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Dec 6 10:57:52 2023
InstallationDate: Installed on 2023-12-04 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2045756/+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 2045576] Re: Please merge 0.52.24-1 into noble
** Merge proposal linked: https://code.launchpad.net/~mateus-morais/ubuntu/+source/newt/+git/newt/+merge/456970 ** Description changed: The upstream version 0.52.24-1 should be merged into noble. The current version is 0.52.23-1ubuntu2. - * PPA for review: - + * PPA for review: https://launchpad.net/~mateus- + morais/+archive/ubuntu/newt-merge Note: this is a tracking bug ** Changed in: newt (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/2045576 Title: Please merge 0.52.24-1 into noble Status in newt package in Ubuntu: In Progress Bug description: The upstream version 0.52.24-1 should be merged into noble. The current version is 0.52.23-1ubuntu2. * PPA for review: https://launchpad.net/~mateus- morais/+archive/ubuntu/newt-merge Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/2045576/+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 2045756] Re: systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected
The netplan configuration is in /etc/netplan/50-cloud-init.yaml.
"optional: true" works, with "ignore-carrier: true" I still get the
failure.
--
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/2045756
Title:
systemd-networkd-wait-online.service fails to complete if one of the
network interfaces is not physically connected
Status in netplan.io package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
New
Bug description:
My StarFive VisionFive 2 board has two network interfaces of which I
have only connected one to a switch. The systemd-networkd-wait-
online.service always fails delaying boot by 150 s. The problem does
not occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network
interface that is not physically connected.
As described in
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
the physical link state can be determined via
/sys/class/net//carrier.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Dec 6 10:57:52 2023
InstallationDate: Installed on 2023-12-04 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2045756/+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 2045756] Re: systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected
The RequiredForOnline=no flag can be controlled using Netplan's "optional:
true" setting.
In your specific case (cable not connected) you might also be interested in
Netplan's "ignore-carrier: true" setting, which brings up the interface
regardless.
Please check /etc/netplan/ for those settings (or "sudo netplan get").
Those initial settings might have been written by cloud-init or
subiquity or some other means of deployment.
** Changed in: netplan.io (Ubuntu)
Status: New => Incomplete
--
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/2045756
Title:
systemd-networkd-wait-online.service fails to complete if one of the
network interfaces is not physically connected
Status in netplan.io package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
New
Bug description:
My StarFive VisionFive 2 board has two network interfaces of which I
have only connected one to a switch. The systemd-networkd-wait-
online.service always fails delaying boot by 150 s. The problem does
not occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network
interface that is not physically connected.
As described in
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
the physical link state can be determined via
/sys/class/net//carrier.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Dec 6 10:57:52 2023
InstallationDate: Installed on 2023-12-04 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2045756/+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 2045768] [NEW] Proposal to Assign a Fixed Group ID to the render Group
Public bug reported: Problem Statement: The lack of a fixed Group ID (GID) for the render group in Ubuntu leads to compatibility and security challenges, particularly in environments utilizing GPU resources. Description: This proposal recommends assigning GID 59 to the render group in the base-passwd/group.master file. The initiative aims to standardize GPU resource management across installations, enhancing system security and application compatibility. The transition of /dev/dri/renderD* from the video to the render group in SystemD has led to issues due to the lack of a fixed GID for render. This has impacted various projects and forced the community to adopt workarounds. https://github.com/systemd/systemd/commit/4e15a7343cb389e97f3eb4f49699161862d8b8b2#diff-8a70fecf0ff724cf610bf2a50eb64d8cb310079007e56d362987c4aefd5d21bb Proposed Change: Assign GID 59 to the render group or another GID that is more appropriate. Rationale: Consistency: A standardized GID ensures uniform access controls across various Linux installations. Security: Establishes clear and predictable permissions for GPU resources, reducing the need for elevated permissions. Compatibility: Supports applications that depend on GPU access, avoiding conflicts and permissions issues. Context and Documented Issues: Some examples of issues around this: https://github.com/blakeblackshear/frigate/issues/7640 https://unix.stackexchange.com/questions/747523/docker-permissions-issue-accessing-dev-dri-device https://github.com/linuxserver/docker-plex/issues/211 https://support.xilinx.com/s/question/0D52E6mfsHaSAI/permission-denied-when-running-hardware?language=en_US https://github.com/jellyfin/jellyfin/issues/9229 Impact on Ubuntu Versions: This issue affects versions such as Ubuntu 20.04 and 22.04, particularly in Docker environments where the render group is not consistently recognized. Request for Feedback: Seeking feedback and discussion from the Ubuntu community and maintainers. ** Affects: base-passwd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/2045768 Title: Proposal to Assign a Fixed Group ID to the render Group Status in base-passwd package in Ubuntu: New Bug description: Problem Statement: The lack of a fixed Group ID (GID) for the render group in Ubuntu leads to compatibility and security challenges, particularly in environments utilizing GPU resources. Description: This proposal recommends assigning GID 59 to the render group in the base-passwd/group.master file. The initiative aims to standardize GPU resource management across installations, enhancing system security and application compatibility. The transition of /dev/dri/renderD* from the video to the render group in SystemD has led to issues due to the lack of a fixed GID for render. This has impacted various projects and forced the community to adopt workarounds. https://github.com/systemd/systemd/commit/4e15a7343cb389e97f3eb4f49699161862d8b8b2#diff-8a70fecf0ff724cf610bf2a50eb64d8cb310079007e56d362987c4aefd5d21bb Proposed Change: Assign GID 59 to the render group or another GID that is more appropriate. Rationale: Consistency: A standardized GID ensures uniform access controls across various Linux installations. Security: Establishes clear and predictable permissions for GPU resources, reducing the need for elevated permissions. Compatibility: Supports applications that depend on GPU access, avoiding conflicts and permissions issues. Context and Documented Issues: Some examples of issues around this: https://github.com/blakeblackshear/frigate/issues/7640 https://unix.stackexchange.com/questions/747523/docker-permissions-issue-accessing-dev-dri-device https://github.com/linuxserver/docker-plex/issues/211 https://support.xilinx.com/s/question/0D52E6mfsHaSAI/permission-denied-when-running-hardware?language=en_US https://github.com/jellyfin/jellyfin/issues/9229 Impact on Ubuntu Versions: This issue affects versions such as Ubuntu 20.04 and 22.04, particularly in Docker environments where the render group is not consistently recognized. Request for Feedback: Seeking feedback and discussion from the Ubuntu community and maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/2045768/+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 2045756] Re: systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected
The following files where created when installing the system:
/run/systemd/network/10-netplan-end0.network
[Match]
Name=end0
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
[DHCP]
RouteMetric=100
UseMTU=true
/run/systemd/network/10-netplan-end1.network
[Match]
Name=end1
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
[DHCP]
RouteMetric=100
UseMTU=true
Upstream recommends adding RequiredForOnline=no
--
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/2045756
Title:
systemd-networkd-wait-online.service fails to complete if one of the
network interfaces is not physically connected
Status in netplan.io package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
My StarFive VisionFive 2 board has two network interfaces of which I
have only connected one to a switch. The systemd-networkd-wait-
online.service always fails delaying boot by 150 s. The problem does
not occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network
interface that is not physically connected.
As described in
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
the physical link state can be determined via
/sys/class/net//carrier.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Dec 6 10:57:52 2023
InstallationDate: Installed on 2023-12-04 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2045756/+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 2045577] Re: Demote isc-dhcp-server to universe
> I will proceed with removing the supported-misc-servers entry. Done. We still need to remove it from supported-maas. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2045577 Title: Demote isc-dhcp-server to universe Status in isc-dhcp package in Ubuntu: In Progress Bug description: Following up on the isc-kea promotion (LP: #2002861) as the new supported DHCP server, it is now time to demote isc-dhcp-server. All the packages that are in. While we are not ready to demote all isc-dhcp packages (there are still packages in main that reverse depend/recommend isc-dhcp-client), we are ready to demote isc-dhcp-server. $ reverse-depends isc-dhcp-server Reverse-Recommends == * fai-server Reverse-Depends === * fai-quickstart * isc-dhcp-server-ldap [amd64 arm64 armhf ppc64el s390x] Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b isc-dhcp-server Reverse-Testsuite-Triggers == * chrony * dracut As shown there are no reverse dependencies for isc-dhcp-server in main. There are Reverse-Testsuite-Triggers in main, but these should not be considered for demotion matters here. The seeds at https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/?h=noble contain 2 entries for isc-dhcp- server: $ grep -r isc-dhcp-server * supported-maas: * isc-dhcp-server supported-misc-servers: * isc-dhcp-server I will proceed with removing the supported-misc-servers entry. Once this is removed from supported-maas, the package will no longer be seeded (we should then get a component mismatch) and can be safely demoted to universe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2045577/+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 2045756] Re: systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected
** Also affects: netplan.io (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/2045756
Title:
systemd-networkd-wait-online.service fails to complete if one of the
network interfaces is not physically connected
Status in netplan.io package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
My StarFive VisionFive 2 board has two network interfaces of which I
have only connected one to a switch. The systemd-networkd-wait-
online.service always fails delaying boot by 150 s. The problem does
not occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network
interface that is not physically connected.
As described in
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
the physical link state can be determined via
/sys/class/net//carrier.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Dec 6 10:57:52 2023
InstallationDate: Installed on 2023-12-04 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2045756/+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 2045753] Re: Ubuntu stuck on the boot screen
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2045753
Title:
Ubuntu stuck on the boot screen
Status in xorg package in Ubuntu:
New
Bug description:
I'm using nomodeset option as a workaround, but I'd prefer a permanent
solution.
I have no idea what I'm doing, so if I'm not specific enough, just ask.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
Uname: Linux 6.5.0-060500-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 6 11:42:55 2023
DistUpgraded: 2023-10-18 10:12:58,820 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
bbswitch/0.8, 6.5.0-060500-generic, x86_64: installed
bbswitch/0.8, 6.5.0-14-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-060500-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620]
[103c:8537]
InstallationDate: Installed on 2020-05-20 (1295 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-060500-generic
root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7
nomodeset
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-10-18 (49 days ago)
dmi.bios.date: 04/27/2020
dmi.bios.release: 11.1
dmi.bios.vendor: HP
dmi.bios.version: R71 Ver. 01.11.01
dmi.board.name: 8537
dmi.board.vendor: HP
dmi.board.version: KBC Version 51.2A.00
dmi.chassis.asset.tag: 5CD0097RK4
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 81.42
dmi.modalias:
dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:br11.1:efr81.42:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:sku5PQ09EA#AKD:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 440 G6
dmi.product.sku: 5PQ09EA#AKD
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2045753/+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 2045756] Re: systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected
Upstream issue: https://github.com/systemd/systemd/issues/30345
** Bug watch added: github.com/systemd/systemd/issues #30345
https://github.com/systemd/systemd/issues/30345
--
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/2045756
Title:
systemd-networkd-wait-online.service fails to complete if one of the
network interfaces is not physically connected
Status in systemd package in Ubuntu:
New
Bug description:
My StarFive VisionFive 2 board has two network interfaces of which I
have only connected one to a switch. The systemd-networkd-wait-
online.service always fails delaying boot by 150 s. The problem does
not occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network
interface that is not physically connected.
As described in
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
the physical link state can be determined via
/sys/class/net//carrier.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Dec 6 10:57:52 2023
InstallationDate: Installed on 2023-12-04 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2045756/+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 2045756] [NEW] systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected
Public bug reported:
My StarFive VisionFive 2 board has two network interfaces of which I
have only connected one to a switch. The systemd-networkd-wait-
online.service always fails delaying boot by 150 s. The problem does not
occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network
interface that is not physically connected.
As described in
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net the
physical link state can be determined via
/sys/class/net//carrier.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Dec 6 10:57:52 2023
InstallationDate: Installed on 2023-12-04 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 (20231204)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0
Controller
-[0001:00]---00.0-[01]00.0 KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4:
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug noble riscv64
** Summary changed:
- systemd-networkd-wait-online.service fails to complete
+ systemd-networkd-wait-online.service fails to complete if one of the network
interfaces is not physically connected
--
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/2045756
Title:
systemd-networkd-wait-online.service fails to complete if one of the
network interfaces is not physically connected
Status in systemd package in Ubuntu:
New
Bug description:
My StarFive VisionFive 2 board has two network interfaces of which I
have only connected one to a switch. The systemd-networkd-wait-
online.service always fails delaying boot by 150 s. The problem does
not occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network
interface that is not physically connected.
As described in
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
the physical link state can be determined via
/sys/class/net//carrier.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Dec 6 10:57:52 2023
InstallationDate: Installed on 2023-12-04 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
Lspci-vt:
-[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB
3.0 Controller
-[0001:00]---00.0-[01]00.0 KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this
[Touch-packages] [Bug 2045754] [NEW] Graphics card driver crash
Public bug reported:
I was just browsing the web when the bottom half of the display became black,
the cursor froze, and everything started flickering.
I think eventually KDE crashed and some terminal messages were shown.
I Ctrl+alt+f3 to a terminal and shut down from there.
The terminal was glitchy with random artifacts but visible.
After reboot everything is working again for now.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Dec 6 12:03:24 2023
DistUpgraded: 2023-11-06 09:55:34,023 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation DG2 [Arc A770] [8086:1020]
InstallationDate: Installed on 2022-10-30 (402 days ago)
InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet
cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1
root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-06 (30 days ago)
dmi.bios.date: 05/18/2023
dmi.bios.release: 16.18
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1618
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X670E-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1618:bd05/18/2023:br16.18:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug freeze kubuntu mantic ubuntu wayland-session
** Attachment added: "dmesg log of the crash"
https://bugs.launchpad.net/bugs/2045754/+attachment/5726688/+files/dmesg-gpu-txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2045754
Title:
Graphics card driver crash
Status in xorg package in Ubuntu:
New
Bug description:
I was just browsing the web when the bottom half of the display became black,
the cursor froze, and everything started flickering.
I think eventually KDE crashed and some terminal messages were shown.
I Ctrl+alt+f3 to a terminal and shut down from there.
The terminal was glitchy with random artifacts but visible.
After reboot everything is working again for now.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Dec 6 12:03:24 2023
DistUpgraded: 2023-11-06 09:55:34,023 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation DG2 [Arc A770] [8086:1020]
InstallationDate: Installed on 2022-10-30 (402 days ago)
[Touch-packages] [Bug 2045753] [NEW] Ubuntu stuck on the boot screen
Public bug reported:
I'm using nomodeset option as a workaround, but I'd prefer a permanent
solution.
I have no idea what I'm doing, so if I'm not specific enough, just ask.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
Uname: Linux 6.5.0-060500-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 6 11:42:55 2023
DistUpgraded: 2023-10-18 10:12:58,820 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
bbswitch/0.8, 6.5.0-060500-generic, x86_64: installed
bbswitch/0.8, 6.5.0-14-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-060500-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620]
[103c:8537]
InstallationDate: Installed on 2020-05-20 (1295 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-060500-generic
root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7
nomodeset
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-10-18 (49 days ago)
dmi.bios.date: 04/27/2020
dmi.bios.release: 11.1
dmi.bios.vendor: HP
dmi.bios.version: R71 Ver. 01.11.01
dmi.board.name: 8537
dmi.board.vendor: HP
dmi.board.version: KBC Version 51.2A.00
dmi.chassis.asset.tag: 5CD0097RK4
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 81.42
dmi.modalias:
dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:br11.1:efr81.42:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:sku5PQ09EA#AKD:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 440 G6
dmi.product.sku: 5PQ09EA#AKD
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2045753
Title:
Ubuntu stuck on the boot screen
Status in xorg package in Ubuntu:
New
Bug description:
I'm using nomodeset option as a workaround, but I'd prefer a permanent
solution.
I have no idea what I'm doing, so if I'm not specific enough, just ask.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
Uname: Linux 6.5.0-060500-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 6 11:42:55 2023
DistUpgraded: 2023-10-18 10:12:58,820 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
bbswitch/0.8, 6.5.0-060500-generic, x86_64: installed
bbswitch/0.8, 6.5.0-14-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-060500-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620]
[103c:8537]
InstallationDate: Installed on 2020-05-20 (1295 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-060500-generic
root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7
nomodeset
RebootRequiredPkgs:
[Touch-packages] [Bug 1775994] Re: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
not a binutils issue, please reinstall, as the error message says ** Changed in: binutils (Ubuntu) Status: New => Invalid -- 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/1775994 Title: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in binutils package in Ubuntu: Invalid Bug description: as I opened the laptop, I got this bug error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libbinutils:amd64 2.30-20ubuntu2~18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: binutils:amd64: Install binutils-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 9 02:55:07 2018 Dependencies: binutils-common 2.30-20ubuntu2~18.04 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 zlib1g 1:1.2.11.dfsg-0ubuntu2 DuplicateSignature: package:libbinutils:amd64:2.30-20ubuntu2~18.04 Processing triggers for man-db (2.8.3-2) ... dpkg: error processing package libbinutils:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-31 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: binutils Title: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1775994/+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 1918462] Re: package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur
this is not a binutils issue, please reinstall as the error message suggests ** Changed in: binutils (Ubuntu) Status: New => Invalid -- 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/1918462 Title: package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in binutils package in Ubuntu: Invalid Bug description: It gives error since 2 weeks in every turning on of computer ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libbinutils:amd64 2.34-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 10 08:19:53 2021 DuplicateSignature: package:libbinutils:amd64:2.34-6ubuntu1.1 Setting up linux-libc-dev:amd64 (5.4.0-66.74) ... dpkg: error processing package libbinutils:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-09-28 (162 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: binutils Title: package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1918462/+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 1977958] Re: binutils: addr2line: getting error "DWARF error: section .debug_str is larger than its filesize" when building Android 8.1 on Ubuntu 20.04
closing as won't fix for 20.04 LTS ** Changed in: binutils (Ubuntu) Status: New => Won't Fix -- 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/1977958 Title: binutils: addr2line: getting error "DWARF error: section .debug_str is larger than its filesize" when building Android 8.1 on Ubuntu 20.04 Status in binutils package in Ubuntu: Won't Fix Bug description: Getting the error "DWARF error: section .debug_str is larger than its filesize" when building an Android app. This is traced back to a security fix introduced in version 2.34-6ubuntu1.3 of binutils. Reverting to 2.34-6ubuntu1 resolves the issue temporarily, but the fix is to allow for .debug_str sizes up to 10x larger than the file size (because of compression). It looks like this fix was made already for Ubuntu 22.04 (binutils 2.38), but has not been backported to 20.04. More detail on the issue and fix is available here: https://sourceware.org/bugzilla/show_bug.cgi?id=28834 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1977958/+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 2045743] Re: Ubuntu Pro attached machine displays ESM support until 31/12/99
*** This bug is a duplicate of bug 1979098 *** https://bugs.launchpad.net/bugs/1979098 Thanks Olivier, that was pointed out as a problem to fix in the design document at the time we landed the feature and already reported as bug #1979098 the date comes from the pro client, quoting what Renan wrote there > This is expected if you are using a free UA subscription. Those should not > expire at all, and year just implies that. > > `ua status --format=json` is returning `expires` as the expiry date for the > contract, and I think the > problem here is that while the contract does not expire, there are the LTS + > ESM support dates, which > should be taken into consideration on the UI. ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1979098 detached ua key and and attached back, now on extensive security maintenance until 31/12/ -- 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/2045743 Title: Ubuntu Pro attached machine displays ESM support until 31/12/99 Status in software-properties package in Ubuntu: New Bug description: The Software and Update app incorrectly shows ESM support continuing until 31/12/99 when the machine is Pro attached. The date for basic support displays correctly when Pro is not enabled. Worth noting that this page does not refresh when a Pro token is detached and needs a relaunch to display the correct support status. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2045743/+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 1824249] Re: package binutils-multiarch (not installed) [modified: usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-li
please remove the package, and re-install it ** Changed in: binutils (Ubuntu) Status: New => Invalid -- 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/1824249 Title: package binutils-multiarch (not installed) [modified: usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings usr/bin/x86_64-linux-gnu-strip] failed to install/upgrade: new binutils-multiarch package pre-installation script subprocess returned error exit status 2 Status in binutils package in Ubuntu: Invalid Bug description: non si riesce ad installare multiarch e binutils ProblemType: Package DistroRelease: Ubuntu 18.10 Package: binutils-multiarch (not installed) [modified: usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings usr/bin/x86_64-linux-gnu-strip] ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Wed Apr 10 20:39:45 2019 ErrorMessage: new binutils-multiarch package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2019-04-09 (1 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: binutils Title: package binutils-multiarch (not installed) [modified: usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings usr/bin/x86_64-linux-gnu-strip] failed to install/upgrade: new binutils-multiarch package pre-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1824249/+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 2025564] Re: package binutils-common 2.40-2ubuntu4.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
this is not a binutils issue. try to re-donwload your updates ** Changed in: binutils (Ubuntu) Status: New => Invalid -- 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/2025564 Title: package binutils-common 2.40-2ubuntu4.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in binutils package in Ubuntu: Invalid Bug description: Appeared on apt update. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: binutils-common 2.40-2ubuntu4.1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Jul 2 12:15:47 2023 Dependencies: DpkgHistoryLog: Start-Date: 2023-07-02 12:15:46 Commandline: /usr/bin/unattended-upgrade Upgrade: libctf-nobfd0:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), libbinutils:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), binutils-x86-64-linux-gnu:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), libctf0:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), binutils-common:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), libgprofng0:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1), binutils:amd64 (2.40-2ubuntu4, 2.40-2ubuntu4.1) DuplicateSignature: package:binutils-common:2.40-2ubuntu4.1 Unpacking binutils (2.40-2ubuntu4.1) over (2.40-2ubuntu4) ... dpkg-deb: error: failed to read archive '/tmp/apt-dpkg-install-sp1YtE/5-binutils_2.40-2ubuntu4.1_amd64.deb': No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-sp1YtE/5-binutils_2.40-2ubuntu4.1_amd64.deb (--unpack): dpkg-deb --fsys-tarfile subprocess returned error exit status 2 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2021-12-21 (557 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211220) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: binutils Title: package binutils-common 2.40-2ubuntu4.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: Upgraded to lunar on 2023-04-20 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2025564/+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 2029525] Re: binutils-i686-linux-gnu not provided for riscv64
we currently don't build cross compilers on riscv64, because it slows down the toolchain updates. That might change, if we have native hardware for our buildds. ** Changed in: binutils (Ubuntu) Status: New => Confirmed -- 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/2029525 Title: binutils-i686-linux-gnu not provided for riscv64 Status in binutils package in Ubuntu: Confirmed Bug description: Currently i686 binutils package is provided for the following arches: amd64 arm64 i386 ppc64el It is required for cross-compilation, but it is currently not provided for riscv64, so on that platform I can't cross-compile. Please consider providing binutils-i686-linux-gnu for riscv64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2029525/+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 2039149] Re: readelf riscv unknown
please provide a test case ** Changed in: binutils (Ubuntu) Status: New => Incomplete -- 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/2039149 Title: readelf riscv unknown Status in binutils package in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu 22.04.3 LTS Release: 22.04 2) binutils: Installed: 2.38-4ubuntu2.3 Candidate: 2.38-4ubuntu2.3 Version table: *** 2.38-4ubuntu2.3 500 500 http://be.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.38-3ubuntu1 500 500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) I'm hand assembling an ELF file and the readelf utility in the binutils package doesn't recognize riscv which is the e_machine 243. LoongArch or 258 and x86 or 3 are recognized, for example. But not riscv. 4) Readelf states that 243 is an unknown e_machine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: binutils 2.38-4ubuntu2.3 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Oct 12 10:14:30 2023 InstallationDate: Installed on 2023-07-12 (91 days ago) InstallationMedia: Xubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: binutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2039149/+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 1878617] Re: Apple pages file type should be added to MIME types
Fantastic! I can confirm that this is fixed on Ubuntu 23.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types Status in shared-mime-info: Fix Released Status in mime-support package in Ubuntu: Invalid Status in shared-mime-info package in Ubuntu: Fix Released Bug description: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+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 2045743] [NEW] Ubuntu Pro attached machine displays ESM support until 31/12/99
Public bug reported: The Software and Update app incorrectly shows ESM support continuing until 31/12/99 when the machine is Pro attached. The date for basic support displays correctly when Pro is not enabled. Worth noting that this page does not refresh when a Pro token is detached and needs a relaunch to display the correct support status. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2023-12-06 08-48-52.png" https://bugs.launchpad.net/bugs/2045743/+attachment/5726651/+files/Screenshot%20from%202023-12-06%2008-48-52.png -- 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/2045743 Title: Ubuntu Pro attached machine displays ESM support until 31/12/99 Status in software-properties package in Ubuntu: New Bug description: The Software and Update app incorrectly shows ESM support continuing until 31/12/99 when the machine is Pro attached. The date for basic support displays correctly when Pro is not enabled. Worth noting that this page does not refresh when a Pro token is detached and needs a relaunch to display the correct support status. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2045743/+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
