[Touch-packages] [Bug 2054908] Re: gnupg is pulling in gpg-wks-server which pulls in postfix
gpg-wks-server is not a new dependency so upgrading will of course pull in a newer version until you remove it. The images will be fixed eventually when they get rebuilt from scratch. For upgrades, we can quirk this to avoid upgrading it only for it to become auto removable later. ** Changed in: gnupg2 (Ubuntu) Status: New => Invalid ** Changed in: apt (Ubuntu) Status: New => Invalid ** Changed in: munin (Ubuntu) Status: Triaged => Invalid ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Also affects: auto-package-testing Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2054908 Title: gnupg is pulling in gpg-wks-server which pulls in postfix Status in Auto Package Testing: New Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Invalid Status in munin package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Example 1 I did a sudo apt dist-upgrade today on my developer machine running Ubuntu Desktop 24.04 LTS and it surprisingly pulled in postfix. I did not built this into a full reproducible test case because I found another test case… Example 2 munin's autopkgtests are now failing because postfix and gpg-wks-server is now unexpectedly being installed. https://autopkgtest.ubuntu.com/packages/munin/noble/amd64 Other Info gnupg2's changelog indicates that there was an attempt to avoid this misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is **nothing** in Ubuntu that Depends or Recommends gpg-wks-server. Notably, gnupg has Suggests: gpg-wks-server (<< 2.4.4-2ubuntu7.1~), gpg-wks-server (>= 2.4.4-2ubuntu7) I don't recall ever seeing strict versioned Suggests before so it's my wild guess that apt does not strict handle versioned Suggests in the expected way. As a workaround, try dropping the versions from gnupg's Suggests. But the true fix may be in apt. I added a munin bug task as a pointer in case anyone wonder's about the autopkgtest regression but I don't believe munin needs any changes. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2054908/+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 2052925] Re: lpoptions -d as root
I will test this once I'm back from PTO on 1Mar. -- 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/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Status in cups source package in Jammy: Fix Committed Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://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.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2052925/+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 2054908] [NEW] gnupg is pulling in gpg-wks-server which pulls in postfix
Public bug reported: Example 1 I did a sudo apt dist-upgrade today on my developer machine running Ubuntu Desktop 24.04 LTS and it surprisingly pulled in postfix. I did not built this into a full reproducible test case because I found another test case… Example 2 munin's autopkgtests are now failing because postfix and gpg-wks-server is now unexpectedly being installed. https://autopkgtest.ubuntu.com/packages/munin/noble/amd64 Other Info gnupg2's changelog indicates that there was an attempt to avoid this misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is **nothing** in Ubuntu that Depends or Recommends gpg-wks-server. Notably, gnupg has Suggests: gpg-wks-server (<< 2.4.4-2ubuntu7.1~), gpg-wks-server (>= 2.4.4-2ubuntu7) I don't recall ever seeing strict versioned Suggests before so it's my wild guess that apt does not strict handle versioned Suggests in the expected way. As a workaround, try dropping the versions from gnupg's Suggests. But the true fix may be in apt. I added a munin bug task as a pointer in case anyone wonder's about the autopkgtest regression but I don't believe munin needs any changes. ** Affects: apt (Ubuntu) Importance: High Status: New ** Affects: gnupg2 (Ubuntu) Importance: High Status: New ** Affects: munin (Ubuntu) Importance: Undecided Status: Triaged ** Tags: noble update-excuse ** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Changed in: apt (Ubuntu) Importance: Undecided => High ** Also affects: munin (Ubuntu) Importance: Undecided Status: New ** Changed in: munin (Ubuntu) Status: New => Triaged ** Tags added: update-excuse ** Description changed: Example 1 I did a sudo apt dist-upgrade today on my developer machine running Ubuntu Desktop 24.04 LTS and it surprisingly pulled in postfix. I did not built this into a full reproducible test case because I found another test case… Example 2 munin's autopkgtests are now failing because postfix and gpg-wks-server is now unexpectedly being installed. https://autopkgtest.ubuntu.com/packages/munin/noble/amd64 Other Info gnupg2's changelog indicates that there was an attempt to avoid this misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is **nothing** in Ubuntu that Depends or Recommends gpg-wks-server. Notably, gnupg has Suggests: gpg-wks-server (<< 2.4.4-2ubuntu7.1~), gpg-wks-server (>= 2.4.4-2ubuntu7) I don't recall ever seeing versioned Suggests before so it's my wild - guess that maybe apt does not handle versioned Suggests in the expected - way. + guess that apt does not handle versioned Suggests in the expected way. - As a workaround, try dropping the versions from the Suggests. + As a workaround, try dropping the versions from gnupg's Suggests. - But the ultimate fix may be in apt. + But the true fix may be in apt. + + I added a munin bug task as a pointer in case anyone wonder's about the + autopkgtest regression but I don't believe munin needs any changes. ** Description changed: Example 1 I did a sudo apt dist-upgrade today on my developer machine running Ubuntu Desktop 24.04 LTS and it surprisingly pulled in postfix. I did not built this into a full reproducible test case because I found another test case… Example 2 munin's autopkgtests are now failing because postfix and gpg-wks-server is now unexpectedly being installed. https://autopkgtest.ubuntu.com/packages/munin/noble/amd64 Other Info gnupg2's changelog indicates that there was an attempt to avoid this misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is **nothing** in Ubuntu that Depends or Recommends gpg-wks-server. Notably, gnupg has Suggests: gpg-wks-server (<< 2.4.4-2ubuntu7.1~), gpg-wks-server (>= 2.4.4-2ubuntu7) - I don't recall ever seeing versioned Suggests before so it's my wild - guess that apt does not handle versioned Suggests in the expected way. + I don't recall ever seeing strict versioned Suggests before so it's my + wild guess that apt does not strict handle versioned Suggests in the + expected way. As a workaround, try dropping the versions from gnupg's Suggests. But the true fix may be in apt. I added a munin bug task as a pointer in case anyone wonder's about the autopkgtest regression but I don't believe munin needs any changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2054908 Title: gnupg is pulling in gpg-wks-server which pulls in postfix Status in apt package in Ubuntu: New Status in gnupg2 package in Ubuntu: New Status in munin package in Ubuntu: Triaged Bug description: Example 1 I did a sudo apt dist-upgrade today on my developer machine runni
[Touch-packages] [Bug 2054902] [NEW] apport test error: /bin/bash not found
Public bug reported:
This looks like fallout from the completion of usrmerge.
https://autopkgtest.ubuntu.com/packages/apport
=== FAILURES ===
367s ___ T.test_get_file_package
367s
367s self =
367s
367s def test_get_file_package(self):
367s """get_file_package() on installed files."""
367s > self.assertEqual(impl.get_file_package("/bin/bash"), "bash")
367s E AssertionError: None != 'bash'
367s
367s tests/integration/test_packaging_apt_dpkg.py:158: AssertionError
367s ___ T.test_get_files
___
367s
367s self =
367s
367s def test_get_files(self):
367s """get_files()."""
367s self.assertRaises(ValueError, impl.get_files, "nonexisting")
367s > self.assertIn("/bin/bash", impl.get_files("bash"))
367s E AssertionError: '/bin/bash' not found in ['/.', '/etc',
'/etc/bash.bashrc', '/etc/skel', '/etc/skel/.bash_logout', '/etc/skel/.bashrc',
'/etc/skel/.profile', '/usr', '/usr/bin', '/usr/bin/bash', '/usr/bin/bashbug',
** Affects: apport (Ubuntu)
Importance: High
Status: New
** Tags: noble update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2054902
Title:
apport test error: /bin/bash not found
Status in apport package in Ubuntu:
New
Bug description:
This looks like fallout from the completion of usrmerge.
https://autopkgtest.ubuntu.com/packages/apport
=== FAILURES
===
367s ___ T.test_get_file_package
367s
367s self =
367s
367s def test_get_file_package(self):
367s """get_file_package() on installed files."""
367s > self.assertEqual(impl.get_file_package("/bin/bash"), "bash")
367s E AssertionError: None != 'bash'
367s
367s tests/integration/test_packaging_apt_dpkg.py:158: AssertionError
367s ___ T.test_get_files
___
367s
367s self =
367s
367s def test_get_files(self):
367s """get_files()."""
367s self.assertRaises(ValueError, impl.get_files, "nonexisting")
367s > self.assertIn("/bin/bash", impl.get_files("bash"))
367s E AssertionError: '/bin/bash' not found in ['/.', '/etc',
'/etc/bash.bashrc', '/etc/skel', '/etc/skel/.bash_logout', '/etc/skel/.bashrc',
'/etc/skel/.profile', '/usr', '/usr/bin', '/usr/bin/bash', '/usr/bin/bashbug',
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2054902/+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 2054901] [NEW] Systemd fails to install on Noble arm64
Public bug reported: Hello! When trying to bootstrap a new arm64 rootfs using the upcoming Noble release the systemd post-installation script will fail. Please see the file debootstrap.log attached for package install logs. To reproduce: $ sudo debootstrap --no-merged-usr --arch arm64 noble rootfs http://ports.ubuntu.com/ubuntu-ports Description:Ubuntu 20.04.6 LTS Release:20.04 systemd: Installed: (none) Candidate: 255.2-3ubuntu2 Version table: 255.2-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages ** Affects: debootstrap (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Debootstrap build log" https://bugs.launchpad.net/bugs/2054901/+attachment/5749050/+files/debootstrap.log ** Also affects: debootstrap (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/2054901 Title: Systemd fails to install on Noble arm64 Status in debootstrap package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Hello! When trying to bootstrap a new arm64 rootfs using the upcoming Noble release the systemd post-installation script will fail. Please see the file debootstrap.log attached for package install logs. To reproduce: $ sudo debootstrap --no-merged-usr --arch arm64 noble rootfs http://ports.ubuntu.com/ubuntu-ports Description: Ubuntu 20.04.6 LTS Release: 20.04 systemd: Installed: (none) Candidate: 255.2-3ubuntu2 Version table: 255.2-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/2054901/+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 2022879] Re: No sound from Woofer speaker of Asus Zephyrus G14 2023
Here's the link for kernel update instructions and the Mainline tool: https://9to5linux.com/you-can-now-install-linux-kernel-6-7-on-ubuntu-heres-how -- 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/2022879 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022879/+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 2022879] Re: No sound from Woofer speaker of Asus Zephyrus G14 2023
I had this problem, and updating to Kernel 6.7.5 fixed it for me. I used the "Mainline kernel tool" to install the latest Kernel manually, it was easy and quick. AMD Ryzen 9 7940HS w/ Radeon 780M Graphics × 8 NVIDIA Corporation AD106M [GeForce RTX 4070 Max-Q / Mobile] Ubuntu 23.10 Mantic Minotaur (x86-64) Cinnamon version 5.8.4 Kernel 6.7.5-060705-generic Much Love to all! Thanks :) -- 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/2022879 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022879/+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 2054882] [NEW] Xorg freeze
Public bug reported:
Nothing more. Just freezes all the time.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 09:37:57 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-24 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic
root=UUID=3ea98830-6da6-49cf-b34a-00412e832e62 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
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 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/2054882
Title:
Xorg freeze
Status in xorg package in Ubuntu:
New
Bug description:
Nothing more. Just freezes all the time.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 09:37:57 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Seems to happen randomly
[Touch-packages] [Bug 1982336] Re: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16)
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1982336 Title: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16) Status in Ubuntu on IBM z Systems: Fix Released Status in gdb package in Ubuntu: Fix Released Bug description: GDB Support for new IBM Z Hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982336/+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 2054771] Re: Kernel panic boot error with kernel 6.5.0.21
Could restore a working Kernel 6.5.0.21 with $ sudo apt update $ sudo apt upgrade However, the system starts up directly without asking for the user login, which is really weird. There is also a security warning when updating: $ sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease Hit:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu mantic-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu mantic-security InRelease Ign:5 http://linux.dropbox.com/ubuntu mantic InRelease Hit:6 http://linux.dropbox.com/ubuntu mantic Release Get:7 http://linux.dropbox.com/ubuntu mantic Release.gpg [488 B] Ign:7 http://linux.dropbox.com/ubuntu mantic Release.gpg Hit:8 https://dl.google.com/linux/chrome/deb stable InRelease Reading package lists... Done W: GPG error: http://linux.dropbox.com/ubuntu mantic Release: The following signatures were invalid: BADSIG FC918B335044912E Dropbox Automatic Signing Key E: The repository 'http://linux.dropbox.com/ubuntu mantic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://dl.google.com/linux/chrome/deb stable InRelease' doesn't support architecture 'i386' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2054771 Title: Kernel panic boot error with kernel 6.5.0.21 Status in network-manager package in Ubuntu: New Bug description: Booting on kernel 6.5.0.21-generic returns error: 'Unable to mount root fs on unknown-block(0.0)' The system starts up correctly with the previous kernel 6.7.0.17-generic Trying fixing 6.5.0.21-generic does not work: $ update-initramfs -u -k 6.5.0.21-generic update-initramfs: Generating /boot/initrd.img-6.5.0.21-generic touch: cannot touch '/boot/initrd.img-6.5.0.21-generic.new': Permission denied W: Kernel configuration /boot/config-6.5.0.21-generic is missing, cannot check for zstd compression support (CONFIG_RD_ZSTD) W: missing /lib/modules/6.5.0.21-generic W: Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/6.5.0.21-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory cat: /var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic/modules.builtin: No such file or directory W: Can't find modules.builtin.modinfo (for locating built-in drivers' firmware, supported in Linux >=5.2) /dev/mapper/control: open failed: Permission denied Failure to communicate with kernel device-mapper driver. Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown version). Command failed. /dev/mapper/control: open failed: Permission denied Failure to communicate with kernel device-mapper driver. Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown version). Command failed. /dev/mapper/control: open failed: Permission denied Failure to communicate with kernel device-mapper driver. Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown version). Command failed. /dev/mapper/control: open failed: Permission denied Failure to communicate with kernel device-mapper driver. Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown version). Command failed. I: The initramfs will attempt to resume from /dev/dm-2 I: (UUID=ae16e50c-6748-4c2f-877f-b084acd65a51) I: Set the RESUME variable to override this. cp: cannot access '/etc/lvm/backup': Permission denied depmod: WARNING: could not open modules.order at /var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or directory depmod: WARNING: could not open modules.builtin at /var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or directory depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or directory /usr/sbin/mkinitramfs: 539: cannot create /boot/initrd.img-6.5.0.21-generic.new: Permission denied update-initramfs: failed for /boot/initrd.img-6.5.0.21-generic with 2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2054771/+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 2054771] Re: Kernel panic boot error with kernel 6.5.0.21
After a reboot this is the output from update: $ sudo apt update Reading package lists... Done E: Could not get lock /var/lib/apt/lists/lock. It is held by process 3911 (packagekitd) N: Be aware that removing the lock file is not a solution and may break your system. E: Unable to lock directory /var/lib/apt/lists/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2054771 Title: Kernel panic boot error with kernel 6.5.0.21 Status in network-manager package in Ubuntu: New Bug description: Booting on kernel 6.5.0.21-generic returns error: 'Unable to mount root fs on unknown-block(0.0)' The system starts up correctly with the previous kernel 6.7.0.17-generic Trying fixing 6.5.0.21-generic does not work: $ update-initramfs -u -k 6.5.0.21-generic update-initramfs: Generating /boot/initrd.img-6.5.0.21-generic touch: cannot touch '/boot/initrd.img-6.5.0.21-generic.new': Permission denied W: Kernel configuration /boot/config-6.5.0.21-generic is missing, cannot check for zstd compression support (CONFIG_RD_ZSTD) W: missing /lib/modules/6.5.0.21-generic W: Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/6.5.0.21-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory cat: /var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic/modules.builtin: No such file or directory W: Can't find modules.builtin.modinfo (for locating built-in drivers' firmware, supported in Linux >=5.2) /dev/mapper/control: open failed: Permission denied Failure to communicate with kernel device-mapper driver. Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown version). Command failed. /dev/mapper/control: open failed: Permission denied Failure to communicate with kernel device-mapper driver. Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown version). Command failed. /dev/mapper/control: open failed: Permission denied Failure to communicate with kernel device-mapper driver. Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown version). Command failed. /dev/mapper/control: open failed: Permission denied Failure to communicate with kernel device-mapper driver. Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown version). Command failed. I: The initramfs will attempt to resume from /dev/dm-2 I: (UUID=ae16e50c-6748-4c2f-877f-b084acd65a51) I: Set the RESUME variable to override this. cp: cannot access '/etc/lvm/backup': Permission denied depmod: WARNING: could not open modules.order at /var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or directory depmod: WARNING: could not open modules.builtin at /var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or directory depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or directory /usr/sbin/mkinitramfs: 539: cannot create /boot/initrd.img-6.5.0.21-generic.new: Permission denied update-initramfs: failed for /boot/initrd.img-6.5.0.21-generic with 2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2054771/+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 1888391] Re: /etc/dhcp/dhclient-enter-hooks.d/resolved should not run in non-root network namespaces
You' re right. It's provided by isc-dhcp-client. Can' t recall how I
ended up with reporting this against systemd 4 years ago.
** Package changed: systemd (Ubuntu) => isc-dhcp (Ubuntu)
** Changed in: isc-dhcp (Ubuntu)
Status: Invalid => New
--
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/1888391
Title:
/etc/dhcp/dhclient-enter-hooks.d/resolved should not run in non-root
network namespaces
Status in isc-dhcp package in Ubuntu:
New
Bug description:
Running dhclient in a (non-root) network namespace on a system with
systemd enabled fails because the hook installed by the systemd
package updates the DNS configuration of the core/root namespace,
instead of simply the /etc/resolv.conf file of that particular network
namespace.
("ip netns add " nicely links /etc/resolv.conf in that namespace
to /etc/netns//resolv.conf if it exists.)
The following patch ensures that this script no longer misbehaves for
this scenario:
--- /etc/dhcp/dhclient-enter-hooks.d/resolved.bak 2020-07-21
14:05:23.390989468 +0200
+++ /etc/dhcp/dhclient-enter-hooks.d/resolved 2020-07-21 14:03:18.566046842
+0200
@@ -14,7 +14,7 @@
# (D) = master script downs interface
# (-) = master script does nothing with this
-if [ -x /lib/systemd/systemd-resolved ] ; then
+if [ -x /lib/systemd/systemd-resolved ] && [ -z "$(ip netns identify)" ] ;
then
# For safety, first undefine the nasty default make_resolv_conf()
make_resolv_conf() { : ; }
case "$reason" in
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1888391/+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 2054873] Re: Connection to xwayland lost / Xwayland terminated, exiting since it was mandatory
** Attachment added: "journalctl-6.8.0-rc4-realtime-rt4 full with Connection to Xwayland lost" https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2054873/+attachment/5748932/+files/journalctl-6.8.0-rc4-realtime-rt4.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2054873 Title: Connection to xwayland lost / Xwayland terminated, exiting since it was mandatory Status in wayland package in Ubuntu: New Bug description: Hi Kernel Team, I notice this today when using Ubuntu 24.04 Noble. Xwayland session crashed while I was using the laptop. My kernel is: 6.8.0-rc4-realtime-rt4 I notice this: (../src/core/meta- context.c:533):meta_context_terminate: runtime check failed: (g_main_loop_is_running (priv->main_loop)) # journalctl -b --no-pager --no-hostname | grep "gnome-shell\[3017\]" Feb 24 13:21:13 gnome-shell[3017]: Running GNOME Shell (using mutter 45.3) as a Wayland display server Feb 24 13:21:13 gnome-shell[3017]: Made thread 'KMS thread' realtime scheduled Feb 24 13:21:14 gnome-shell[3017]: Device '/dev/dri/card1' prefers shadow buffer Feb 24 13:21:14 gnome-shell[3017]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting. Feb 24 13:21:14 gnome-shell[3017]: Created gbm renderer for '/dev/dri/card1' Feb 24 13:21:14 gnome-shell[3017]: Boot VGA GPU /dev/dri/card1 selected as primary Feb 24 13:21:14 gnome-shell[3017]: Obtained a high priority EGL context Feb 24 13:21:14 gnome-shell[3017]: Obtained a high priority EGL context Feb 24 13:21:14 gnome-shell[3017]: Using public X11 display :1024, (using :1025 for managed services) Feb 24 13:21:14 gnome-shell[3017]: Using Wayland display name 'wayland-0' Feb 24 13:21:15 gnome-shell[3017]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. Feb 24 13:21:15 gnome-shell[3017]: Will monitor session c1 Feb 24 13:21:15 gnome-shell[3017]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded Feb 24 13:21:15 gnome-shell[3017]: Extension tiling-assist...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com. /usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com will not be loaded Feb 24 13:21:15 gnome-shell[3017]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded Feb 24 13:21:15 gnome-shell[3017]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded Feb 24 13:21:15 gnome-shell[3017]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Feb 24 13:21:15 gnome-shell[3017]: Failed to open sliced image: The resource at “/org/gnome/shell/theme/process-working-dark.svg” does not exist Feb 24 13:21:16 gnome-shell[3017]: Failed to open sliced image: The resource at “/org/gnome/shell/theme/process-working-dark.svg” does not exist Feb 24 13:21:16 gnome-shell[3017]: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available Feb 24 13:21:16 gnome-shell[3017]: Registering session with GDM Feb 24 13:21:18 gnome-shell[3017]: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available Feb 24 13:21:25 gnome-shell[3017]: Connection to xwayland lost Feb 24 13:21:25 gnome-shell[3017]: Xwayland terminated, exiting since it was mandatory Feb 24 13:21:25 gnome-shell[3017]: (../src/core/meta-context.c:533):meta_context_terminate: runtime check failed: (g_main_loop_is_running (priv->main_loop)) Feb 24 13:21:25 gnome-shell[3017]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly Feb 24 13:21:25 gnome-shell[3017]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2054873/+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 2054873] [NEW] Connection to xwayland lost / Xwayland terminated, exiting since it was mandatory
Public bug reported: Hi Kernel Team, I notice this today when using Ubuntu 24.04 Noble. Xwayland session crashed while I was using the laptop. My kernel is: 6.8.0-rc4-realtime-rt4 I notice this: (../src/core/meta-context.c:533):meta_context_terminate: runtime check failed: (g_main_loop_is_running (priv->main_loop)) # journalctl -b --no-pager --no-hostname | grep "gnome-shell\[3017\]" Feb 24 13:21:13 gnome-shell[3017]: Running GNOME Shell (using mutter 45.3) as a Wayland display server Feb 24 13:21:13 gnome-shell[3017]: Made thread 'KMS thread' realtime scheduled Feb 24 13:21:14 gnome-shell[3017]: Device '/dev/dri/card1' prefers shadow buffer Feb 24 13:21:14 gnome-shell[3017]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting. Feb 24 13:21:14 gnome-shell[3017]: Created gbm renderer for '/dev/dri/card1' Feb 24 13:21:14 gnome-shell[3017]: Boot VGA GPU /dev/dri/card1 selected as primary Feb 24 13:21:14 gnome-shell[3017]: Obtained a high priority EGL context Feb 24 13:21:14 gnome-shell[3017]: Obtained a high priority EGL context Feb 24 13:21:14 gnome-shell[3017]: Using public X11 display :1024, (using :1025 for managed services) Feb 24 13:21:14 gnome-shell[3017]: Using Wayland display name 'wayland-0' Feb 24 13:21:15 gnome-shell[3017]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. Feb 24 13:21:15 gnome-shell[3017]: Will monitor session c1 Feb 24 13:21:15 gnome-shell[3017]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded Feb 24 13:21:15 gnome-shell[3017]: Extension tiling-assist...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com. /usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com will not be loaded Feb 24 13:21:15 gnome-shell[3017]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded Feb 24 13:21:15 gnome-shell[3017]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded Feb 24 13:21:15 gnome-shell[3017]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Feb 24 13:21:15 gnome-shell[3017]: Failed to open sliced image: The resource at “/org/gnome/shell/theme/process-working-dark.svg” does not exist Feb 24 13:21:16 gnome-shell[3017]: Failed to open sliced image: The resource at “/org/gnome/shell/theme/process-working-dark.svg” does not exist Feb 24 13:21:16 gnome-shell[3017]: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available Feb 24 13:21:16 gnome-shell[3017]: Registering session with GDM Feb 24 13:21:18 gnome-shell[3017]: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available Feb 24 13:21:25 gnome-shell[3017]: Connection to xwayland lost Feb 24 13:21:25 gnome-shell[3017]: Xwayland terminated, exiting since it was mandatory Feb 24 13:21:25 gnome-shell[3017]: (../src/core/meta-context.c:533):meta_context_terminate: runtime check failed: (g_main_loop_is_running (priv->main_loop)) Feb 24 13:21:25 gnome-shell[3017]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly Feb 24 13:21:25 gnome-shell[3017]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception ** Affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2054873 Title: Connection to xwayland lost / Xwayland terminated, exiting since it was mandatory Status in wayland package in Ubuntu: New Bug description: Hi Kernel Team, I notice this today when using Ubuntu 24.04 Noble. Xwayland session crashed while I was using the laptop. My kernel is: 6.8.0-rc4-realtime-rt4 I notice this: (../src/core/meta- context.c:533):meta_context_terminate: runtime check failed: (g_main_loop_is_running (priv->main_loop)) # journalctl -b --no-pager --no-hostname | grep "gnome-shell\[3017\]" Feb 24 13:21:13 gnome-shell[3017]: Running GNOME Shell (using mutter 45.3) as a Wayland display server Feb 24 13:21:13 gnome-shell[3017]: Made thread 'KMS thread' realtime scheduled Feb 24 13:21:14 gnome-shell[3017]: Device '/dev/dri/card1' prefers shadow buffer Feb 24 13:21:14 gnome-shell[3017]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting. Feb 24 13:21:14 gnome-shell[3017]: Created gbm renderer for '/dev/dri/card1' Feb 24 13:21:14 gnome-shell[3017]: Boot VGA GPU /dev/dri/card1 selected a
[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start
The same happens if trying to open repositories under synaptic package
manager, which allows the same configurations to take place.
--
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/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Triaged
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2053228] Re: software-properties-gtk does not start
I have the same issue for software-properties-gtk. Software-properties-
qt does start, but doesn't show any software sources as enabled.
If I had to guess, I'd blame the fact that upgrading to 24.04 seems to
have moved default repos from /etc/apt/sources.list to
/etc/apt/sources.list.d/ubuntu.sources and changed the format to a more
explicit one. Attached here is my /etc/apt/sources.list.d/ubuntu.sources
** Attachment added: "ubuntu.sources"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+attachment/5748930/+files/ubuntu.sources
--
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/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Triaged
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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
