[Touch-packages] [Bug 1942703] Re: Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around
Works by 2.3ubuntu0.3 but there is no such update for 18.04. ** Description changed: If user has linux-generic-hwe-18.04 installed, versioned linux-headers packages depend on versioned linux-hwe-5.4-headers packages that will not get removed. Consequently in time there will be hundreds of thousands of unused files under /usr/src. For example I have about 45 totalling 1.4 GB. The number of inodes may be bigger issue, because file systems have some limitations. I noted the issue when using my linux-purge tool. It is supposed to be able to remove kernels, even if the file system runs out of inodes. + + Workaround: + + Install linux-purge from https://launchpad.net/linux-purge and run + + sudo linux-purge ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.14 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic i686 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: i386 Date: Sun Sep 5 14:38:49 2021 InstallationDate: Installed on 2016-09-05 (1826 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to bionic on 2019-04-06 (882 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-03-26T11:42:30.041160 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1942703 Title: Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: New Bug description: If user has linux-generic-hwe-18.04 installed, versioned linux-headers packages depend on versioned linux-hwe-5.4-headers packages that will not get removed. Consequently in time there will be hundreds of thousands of unused files under /usr/src. For example I have about 45 totalling 1.4 GB. The number of inodes may be bigger issue, because file systems have some limitations. I noted the issue when using my linux-purge tool. It is supposed to be able to remove kernels, even if the file system runs out of inodes. Workaround: Install linux-purge from https://launchpad.net/linux-purge and run sudo linux-purge ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.14 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic i686 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: i386 Date: Sun Sep 5 14:38:49 2021 InstallationDate: Installed on 2016-09-05 (1826 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to bionic on 2019-04-06 (882 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-03-26T11:42:30.041160 To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1942703/+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 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
** No longer affects: zsys (Ubuntu) ** No longer affects: systemd (Ubuntu) ** No longer affects: snapd (Ubuntu) -- 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/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in ubiquity source package in Jammy: Fix Released Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+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 2018538] Re: All PDFs when printed come out mirror image
This behavior also occurs on 23.04 with an HP CP2025. Prior to upgrade printing was great. After upgrade if nothing is touched all pages are mirrored. If the print option is set to mirrored the described behavior in the original report occurs. -- 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/2018538 Title: All PDFs when printed come out mirror image Status in cups package in Ubuntu: Confirmed Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 2018538] Re: All PDFs when printed come out mirror image
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/2018538 Title: All PDFs when printed come out mirror image Status in cups package in Ubuntu: Confirmed Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 2018552] Re: Hundreds of duplicate icons exist in humanity-icon-theme package.
Symlinks created in related branch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2018552 Title: Hundreds of duplicate icons exist in humanity-icon-theme package. Status in Humanity: New Status in humanity-icon-theme package in Ubuntu: New Bug description: Using find for duplicates shows 443 duplicate or related to duplicate files. To manage notifications about this bug go to: https://bugs.launchpad.net/humanity/+bug/2018552/+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 2018552] [NEW] Hundreds of duplicate icons exist in humanity-icon-theme package.
Public bug reported: Using find for duplicates shows 443 duplicate or related to duplicate files. ** Affects: humanity Importance: Undecided Status: New ** Affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: bionic bitesize focal humanity icons jammy kinetic lunar mantic ubuntu ** Also affects: humanity Importance: Undecided Status: New ** Branch linked: lp:~ubuntu-art-pkg/humanity/release ** Branch linked: lp:~wontfix/humanity/devel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2018552 Title: Hundreds of duplicate icons exist in humanity-icon-theme package. Status in Humanity: New Status in humanity-icon-theme package in Ubuntu: New Bug description: Using find for duplicates shows 443 duplicate or related to duplicate files. To manage notifications about this bug go to: https://bugs.launchpad.net/humanity/+bug/2018552/+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 2012805] Re: Motorola logos exist in Humanity icon theme.
** Tags added: bitesize mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2012805 Title: Motorola logos exist in Humanity icon theme. Status in Humanity: New Status in humanity-icon-theme package in Ubuntu: New Bug description: See summary. Possible fix is attached below. Branding occurs on most but not all sizes. I am not an artist. Occurs- /usr/share/icons/Humanity/devices/22/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/24/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/32/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/48/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/64/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/128/phone-motorola-droid.svg Doesn't occur- /usr/share/icons/Humanity/devices/16/phone-motorola-droid.svg To manage notifications about this bug go to: https://bugs.launchpad.net/humanity/+bug/2012805/+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 1325949] Re: Add note to Debconf template about unintuitive inverted Etc/GMT offsets
** Changed in: tzdata (Debian) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1325949 Title: Add note to Debconf template about unintuitive inverted Etc/GMT offsets Status in tzdata package in Ubuntu: Fix Committed Status in tzdata package in Debian: Fix Committed Bug description: Looks like GMT[+-} timezones have signs swapped. My local timezone is Europe/Tallinn When timezone is set to "Europe/Tallinn", everything is ok: # dpkg-reconfigure tzdata -> Europe/Tallinn # date Tue Jun 3 14:34:21 EEST 2014 # date +%z +0300 # date -u Tue Jun 3 11:34:59 UTC 2014 I need to set timezone to GMT+2, to avoid dailight savings time. When I set timezone to "GMT+2", things fall apart. Timezone is shown GMT+2/GMT-2. Clock is set to GMT-2. # dpkg-reconfigure tzdata -> Etc/GMT+2 # date Tue Jun 3 09:36:21 GMT+2 2014 # date +%z -0200 # date -u Tue Jun 3 11:37:43 UTC 2014 When I set timezone to "GMT-2", then it's turned around. Timezone is shown GMT-2/GMT+2. Clock is set to GMT+2. #dpkg-reconfigure tzdata -> Etc/GMT-2 # date Tue Jun 3 13:39:35 GMT-2 2014 # date +%z +0200 # date -u Tue Jun 3 11:39:56 UTC 2014 # lsb_release -rd Description:Ubuntu 12.04.4 LTS Release:12.04 # apt-cache policy tzdata tzdata: Installed: 2014c-0ubuntu0.12.04 Candidate: 2014c-0ubuntu0.12.04 Version table: *** 2014c-0ubuntu0.12.04 0 500 http://ee.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 2012e-0ubuntu0.12.04.1 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 2012b-1 0 500 http://ee.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages # apt-get update # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1325949/+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 2018457] Re: [SRU] Enable support for Bobcat Cloud Archive
This bug was fixed in the package software-properties - 0.99.36 --- software-properties (0.99.36) mantic; urgency=medium * cloudarchive: Enable support for the Bobcat Ubuntu Cloud Archive on 22.04 (LP: #2018457). -- Corey Bryant Thu, 04 May 2023 10:12:11 +0200 ** Changed in: software-properties (Ubuntu Mantic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2018457 Title: [SRU] Enable support for Bobcat Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Triaged Status in software-properties source package in Mantic: Fix Released Bug description: Please add support for: cloud-archive:bobcat cloud-archive:bobcat-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the antelope cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:bobcat sudo add-apt-repository cloud-archive:bobcat-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2018457/+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 2016597] Re: Tests create ~/.ssh/authorized_keys group writable due to wrong umask
This bug was fixed in the package tinyssh - 20230101-1ubuntu1 --- tinyssh (20230101-1ubuntu1) devel; urgency=medium * d/tests: Create ~/.ssh/authorized_keys with proper umask (LP: #2016597) * d/tests: Avoid flaky failures on slow testbeds -- Lukas Märdian Mon, 17 Apr 2023 15:09:53 +0200 ** Changed in: tinyssh (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2016597 Title: Tests create ~/.ssh/authorized_keys group writable due to wrong umask Status in systemd package in Ubuntu: Invalid Status in tinyssh package in Ubuntu: Fix Released Bug description: Traditionally, the default umask as been 0022, which is still the case on Debian and for the root user on Ubuntu. But for non-root users PAM sets a user's session umask to 0002 by default (/etc/pam.d/common-session*), as defined in "/etc/login.defs" via USERGROUPS_ENAB. tinyssh's sshd will reject connections if ~/.ssh/authorized_key is writable by group/other. The test case (re-)creates ~/.ssh/authorized_keys by echoing some strings/keys into it, which creates a new file on the default umask, breaking the test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2016597/+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 2018538] Re: All PDFs when printed come out mirror image
** Description changed: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page - become mirror image as well. (I'm printing double sided/long edge print, - so the other side of the page becomes mirror image when I do this). + become mirror image as instead. (I'm printing double sided/long edge + print, so one side is normal and the other side becomes mirror image + when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) -- 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/2018538 Title: All PDFs when printed come out mirror image Status in cups package in Ubuntu: New Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 2018538] Re: All PDFs when printed come out mirror image
** Package changed: ubiquity (Ubuntu) => cups (Ubuntu) ** Tags removed: ubiquity-22.10.10 -- 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/2018538 Title: All PDFs when printed come out mirror image Status in cups package in Ubuntu: New Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as well. (I'm printing double sided/long edge print, so the other side of the page becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 2018536] Re: Crash switching audio output while playing audio in Audacity
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/2018536 Title: Crash switching audio output while playing audio in Audacity Status in alsa-driver package in Ubuntu: New Bug description: Following the steps below, i get a crash and KDE Plasma doesn't show any audio output device on my system. I have to reboot the PC to make it work again. I can reproduce 100% of the times in Kubuntu (installed and also using the Live ISO). I can't reproduce it on Ubuntu standard, so it seems to affect Kubuntu only I have a PC that is connected to the HDMI screen and to the earphones via audio jack. So I have 2 outputs: HDMI + Earphones. 1) Put the audio output to HDMI 2) Play an mp3 file for few seconds to check everything works 3) Open an audio file in Audacity 4) Play the audio file in Audacity 5) While playing, change the audio output to earphones. I attach the output of journalctl if it can be useful Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-20-generic (64-bit) Graphics Platform: X11 Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 7.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Intel(R) Client Systems Product Name: NUC12WSHi5 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: enrico 2214 F wireplumber /dev/snd/seq:enrico 2212 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu May 4 20:02:44 2023 InstallationDate: Installed on 2023-04-23 (11 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2022 dmi.bios.release: 5.26 dmi.bios.vendor: Intel Corp. dmi.bios.version: WSADL357.0086.2022.1103.1433 dmi.board.name: NUC12WSBi5 dmi.board.vendor: Intel Corporation dmi.board.version: M46425-303 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrWSADL357.0086.2022.1103.1433:bd11/03/2022:br5.26:svnIntel(R)ClientSystems:pnNUC12WSHi5:pvrM46655-303:rvnIntelCorporation:rnNUC12WSBi5:rvrM46425-303:cvnIntelCorporation:ct35:cvr2.0:skuNUC12WSHi5000: dmi.product.family: WS dmi.product.name: NUC12WSHi5 dmi.product.sku: NUC12WSHi5000 dmi.product.version: M46655-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2018536/+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 2018537] [NEW] Xorg freeze
Public bug reported: Linux laptop2 5.19.0-41-generic #42~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 18 17:40:00 UTC 2 x86_64 x86_64 x86_64 GNU/Linux There is a constant issue with the video acceleration in amdgpu. In conjunction with firefox and drm protected video I could trigger a display freeze very reliably. Disney+ start page would trigger this, screen would go blank shortly, returning with partial mouse response of applications. Just some days ago the new kernel upgrade was applied. With this, the graphics driver even crashes when playing unprotected videos like on youtube. This applies to wayland and xorg mode. Crash log: [43929.632425] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_dec timeout, signaled seq=40254, emitted seq=40256 [43929.632814] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process RDD Process pid 17220 thread firefox:cs0 pid 31188 [43929.633160] amdgpu :03:00.0: amdgpu: GPU reset begin! [43930.143971] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [43930.346077] [drm] Register(0) [mmUVD_RBC_RB_RPTR] failed to reach value 0x0120 != 0x00a0 [43930.542345] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [43930.551906] [drm] free PSP TMR buffer [43930.580095] CPU: 0 PID: 51067 Comm: kworker/u32:2 Not tainted 5.19.0-41-generic #42~22.04.1-Ubuntu [43930.580103] Hardware name: LENOVO 82KT/LNVNB161216, BIOS GLCN41WW 09/13/2021 [43930.580106] Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched] [43930.580121] Call Trace: [43930.580124] [43930.580128] show_stack+0x52/0x69 [43930.580135] dump_stack_lvl+0x49/0x6d [43930.580143] dump_stack+0x10/0x18 [43930.580149] amdgpu_do_asic_reset+0x2b/0x441 [amdgpu] [43930.580186] amdgpu_device_gpu_recover_imp.cold+0x4f6/0x805 [amdgpu] [43930.580186] amdgpu_job_timedout+0x15e/0x190 [amdgpu] [43930.580186] ? finish_task_switch.isra.0+0x84/0x290 [43930.580186] drm_sched_job_timedout+0x6d/0x120 [gpu_sched] [43930.580186] process_one_work+0x21f/0x400 [43930.580186] worker_thread+0x50/0x3f0 [43930.580186] ? rescuer_thread+0x3a0/0x3a0 [43930.580186] kthread+0xee/0x120 [43930.580186] ? kthread_complete_and_exit+0x20/0x20 [43930.580186] ret_from_fork+0x22/0x30 [43930.580186] [43930.581703] amdgpu :03:00.0: amdgpu: MODE2 reset [43930.582168] amdgpu :03:00.0: amdgpu: GPU reset succeeded, trying to resume [43930.582364] [drm] PCIE GART of 1024M enabled. [43930.582366] [drm] PTB located at 0x00F40090 [43930.582382] [drm] PSP is resuming... [43930.602253] [drm] reserve 0x40 from 0xf41fb0 for PSP TMR [43930.921623] amdgpu :03:00.0: amdgpu: RAS: optional ras ta ucode is not available [43930.933021] amdgpu :03:00.0: amdgpu: RAP: optional rap ta ucode is not available [43930.933027] amdgpu :03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [43930.933033] amdgpu :03:00.0: amdgpu: SMU is resuming... [43930.933772] amdgpu :03:00.0: amdgpu: SMU is resumed successfully! [43930.934335] [drm] DMUB hardware initialized: version=0x0101001F [43931.267844] [drm] kiq ring mec 2 pipe 1 q 0 [43931.270626] [drm] VCN decode and encode initialized successfully(under DPG Mode). [43931.270689] [drm] JPEG decode initialized successfully. [43931.270695] amdgpu :03:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 [43931.270701] amdgpu :03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [43931.270704] amdgpu :03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [43931.270707] amdgpu :03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [43931.270710] amdgpu :03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [43931.270712] amdgpu :03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [43931.270714] amdgpu :03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [43931.270717] amdgpu :03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [43931.270719] amdgpu :03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [43931.270722] amdgpu :03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [43931.270725] amdgpu :03:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 [43931.270728] amdgpu :03:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 [43931.270730] amdgpu :03:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 [43931.270733] amdgpu :03:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 [43931.270735] amdgpu :03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 [43931.274645] amdgpu :03:00.0: amdgpu: recover vram bo from shadow start [43931.274648] amdgpu :03:00.0: amdgpu: recover vram bo from shadow done [43931.274654] [drm] Skip scheduling IBs! [43931.274670] amdgpu :03:00.0: amdgpu: GPU reset(2) succeeded! [43931.293293] [drm] Skip scheduling IBs! [43931.293997] [drm] Skip scheduling IBs! [43931.294319]
[Touch-packages] [Bug 2017819] Re: Many broken symlinks and a few empty directories.
** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2017819 Title: Many broken symlinks and a few empty directories. Status in Humanity: New Status in humanity-icon-theme package in Ubuntu: New Bug description: Broken symlinks- ./Humanity/apps/24/catfish.svg ./Humanity/apps/24/x-system-software-sources.svg ./Humanity/apps/24/panel-searchtool.svg ./Humanity/apps/24/pk-package-sources.svg ./Humanity/apps/24/xfce4-appfinder.svg ./Humanity/apps/24/gpk-repo.svg ./Humanity/apps/24/edit-urpm-sources.svg ./Humanity/apps/24/gnome-searchtool.svg ./Humanity/apps/48/catfish.svg ./Humanity/apps/48/x-system-software-sources.svg ./Humanity/apps/48/panel-searchtool.svg ./Humanity/apps/48/pk-package-sources.svg ./Humanity/apps/48/xfce4-appfinder.svg ./Humanity/apps/48/gpk-repo.svg ./Humanity/apps/48/edit-urpm-sources.svg ./Humanity/apps/48/gnome-searchtool.svg ./Humanity/status/48/aptdaemon-update-cache.svg ./Humanity/stock/24/stock_zoom-page.svg ./Humanity/stock/22/stock_zoom-page.svg ./Humanity/stock/48/stock_zoom-page.svg Empty directories- ./Humanity-Dark/places/32 ./Humanity-Dark/actions/24 ./Humanity-Dark/actions/22 To manage notifications about this bug go to: https://bugs.launchpad.net/humanity/+bug/2017819/+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 2018530] Re: Updating error, apt and apt-utils on Kubuntu 22.04 kernel version 5.19.0-41
** Description changed: Doing regular update fails apt and apt-utils packages: ¿Desea continuar? [S/n] s (Leyendo la base de datos ... 759723 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../archives/apt_2.4.9_amd64.deb ... Desempaquetando apt (2.4.9) sobre (2.4.8) ... dpkg: error al procesar el archivo /var/cache/apt/archives/apt_2.4.9_amd64.deb (--unpack): intentando sobreescribir `/etc/apt/trusted.gpg.d', que está también en el paquete ubuntu-oem-keyring 2021.03.26 dpkg-deb: error: el subproceso copiado fue terminado por la señal (Tubería rota) Se encontraron errores al procesar: /var/cache/apt/archives/apt_2.4.9_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) + + __ + + Operating System: Kubuntu 22.04 + KDE Plasma Version: 5.24.7 + KDE Frameworks Version: 5.92.0 + Qt Version: 5.15.3 + Kernel Version: 5.19.0-41-generic (64-bit) + Graphics Platform: X11 + Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz + Memory: 31.0 GiB of RAM + Graphics Processor: Mesa Intel® UHD Graphics 620 -- 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/2018530 Title: Updating error, apt and apt-utils on Kubuntu 22.04 kernel version 5.19.0-41 Status in apt package in Ubuntu: New Bug description: Doing regular update fails apt and apt-utils packages: ¿Desea continuar? [S/n] s (Leyendo la base de datos ... 759723 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../archives/apt_2.4.9_amd64.deb ... Desempaquetando apt (2.4.9) sobre (2.4.8) ... dpkg: error al procesar el archivo /var/cache/apt/archives/apt_2.4.9_amd64.deb (--unpack): intentando sobreescribir `/etc/apt/trusted.gpg.d', que está también en el paquete ubuntu-oem-keyring 2021.03.26 dpkg-deb: error: el subproceso copiado fue terminado por la señal (Tubería rota) Se encontraron errores al procesar: /var/cache/apt/archives/apt_2.4.9_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) __ Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.19.0-41-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2018530/+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 2018530] Re: Updating error, apt and apt-utils on Kubuntu 22.04 kernel version 5.19.0-41
** Description changed: Doing regular update fails apt and apt-utils packages: ¿Desea continuar? [S/n] s (Leyendo la base de datos ... 759723 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../archives/apt_2.4.9_amd64.deb ... Desempaquetando apt (2.4.9) sobre (2.4.8) ... dpkg: error al procesar el archivo /var/cache/apt/archives/apt_2.4.9_amd64.deb (--unpack): - intentando sobreescribir `/etc/apt/trusted.gpg.d', que está también en el paquete ubuntu-oem-keyring 2021.03.26 + intentando sobreescribir `/etc/apt/trusted.gpg.d', que está también en el paquete ubuntu-oem-keyring 2021.03.26 dpkg-deb: error: el subproceso copiado fue terminado por la señal (Tubería rota) Se encontraron errores al procesar: - /var/cache/apt/archives/apt_2.4.9_amd64.deb + /var/cache/apt/archives/apt_2.4.9_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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/2018530 Title: Updating error, apt and apt-utils on Kubuntu 22.04 kernel version 5.19.0-41 Status in apt package in Ubuntu: New Bug description: Doing regular update fails apt and apt-utils packages: ¿Desea continuar? [S/n] s (Leyendo la base de datos ... 759723 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../archives/apt_2.4.9_amd64.deb ... Desempaquetando apt (2.4.9) sobre (2.4.8) ... dpkg: error al procesar el archivo /var/cache/apt/archives/apt_2.4.9_amd64.deb (--unpack): intentando sobreescribir `/etc/apt/trusted.gpg.d', que está también en el paquete ubuntu-oem-keyring 2021.03.26 dpkg-deb: error: el subproceso copiado fue terminado por la señal (Tubería rota) Se encontraron errores al procesar: /var/cache/apt/archives/apt_2.4.9_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) __ Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.19.0-41-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2018530/+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 2018530] [NEW] Updating error, apt and apt-utils on Kubuntu 22.04 kernel version 5.19.0-41
Public bug reported: Doing regular update fails apt and apt-utils packages: ¿Desea continuar? [S/n] s (Leyendo la base de datos ... 759723 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../archives/apt_2.4.9_amd64.deb ... Desempaquetando apt (2.4.9) sobre (2.4.8) ... dpkg: error al procesar el archivo /var/cache/apt/archives/apt_2.4.9_amd64.deb (--unpack): intentando sobreescribir `/etc/apt/trusted.gpg.d', que está también en el paquete ubuntu-oem-keyring 2021.03.26 dpkg-deb: error: el subproceso copiado fue terminado por la señal (Tubería rota) Se encontraron errores al procesar: /var/cache/apt/archives/apt_2.4.9_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Package changed: pulseaudio (Ubuntu) => apt (Ubuntu) -- 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/2018530 Title: Updating error, apt and apt-utils on Kubuntu 22.04 kernel version 5.19.0-41 Status in apt package in Ubuntu: New Bug description: Doing regular update fails apt and apt-utils packages: ¿Desea continuar? [S/n] s (Leyendo la base de datos ... 759723 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../archives/apt_2.4.9_amd64.deb ... Desempaquetando apt (2.4.9) sobre (2.4.8) ... dpkg: error al procesar el archivo /var/cache/apt/archives/apt_2.4.9_amd64.deb (--unpack): intentando sobreescribir `/etc/apt/trusted.gpg.d', que está también en el paquete ubuntu-oem-keyring 2021.03.26 dpkg-deb: error: el subproceso copiado fue terminado por la señal (Tubería rota) Se encontraron errores al procesar: /var/cache/apt/archives/apt_2.4.9_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2018530/+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 2018525] Re: Xorg freeze
Hello Sebastien. This most frequently happens (if not all the time) when writing in editors (for example VSCode or Evolution), but does not happen each time and I am not sure it is related. It seems to be random... I can work during hours without any problem and then it happens. Today, just before it happens, I noticed that while wrinting an e-mail in evolution letters were displaying long time after typing. That did it also in website for a comment. That's really all I noticed... but I hope this will help. -- 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/2018525 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: Screen freezes, then goes to black during a few seconds then returns to working state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem 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..07.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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 4 17:21:47 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-41-generic, x86_64: installed nvidia/525.105.17, 6.1.0-1008-oem, x86_64: installed ExtraDebuggingInterest: No GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GA104M [GeForce RTX 3070 Mobile / Max-Q] [1558:50f4] InstallationDate: Installed on 2023-01-27 (96 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Notebook NH5xVR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1008-oem root=UUID=c6e942e5-1878-4e2a-8d85-81abebd32761 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2021 dmi.bios.release: 7.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5xVR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.3 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.07.06:bd02/18/2021:br7.6:efr7.3:svnNotebook:pnNH5xVR:pvrNotApplicable:rvnNotebook:rnNH5xVR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5xVR dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.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.4-2ubuntu1.7~22.04.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-2ubuntu1 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/2018525/+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 2018526] [NEW] Mesa Clover built with opaque pointers against LLVM built without opaque pointers
Public bug reported: This can be verified with any OpenCL application that actually tries to compute something (clinfo may not be enough). A very simple application to reproduce the bug is cl-mem: ``` git clone https://github.com/nerdralph/cl-mem.git cd cl-mem make ./cl-mem OpenCL build failed (-11). Build log follows: fatal error: cannot open file '/usr/lib/clc/hawaii-amdgcn-mesa-mesa3d.bc': Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 15.0.7') ``` I may provide help to fix it, without guarantee. The migration of LLVM to opaque pointers was not painless, some versions of Mesa may build and run against some versions of LLVM 15 given that build option or that patch is used, some not. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mesa-opencl-icd 22.2.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Thu May 4 17:38:07 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: Default string Default string ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2022 dmi.bios.release: 5.23 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: WRX80PRO-F1 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80PRO-F1:bd08/04/2022:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.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: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2018526 Title: Mesa Clover built with opaque pointers against LLVM built without opaque pointers Status in mesa package in Ubuntu: New Bug description: This can be verified with any OpenCL application that actually tries to compute something (clinfo may not be enough). A very simple application to reproduce the bug is cl-mem: ``` git clone https://github.com/nerdralph/cl-mem.git cd cl-mem make ./cl-mem OpenCL build failed (-11). Build log follows: fatal error: cannot open file '/usr/lib/clc/hawaii-amdgcn-mesa-mesa3d.bc': Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 15.0.7') ``` I may provide help to fix it, without guarantee. The migration of LLVM to opaque pointers was not painless, some versions of Mesa may build and run against some versions of LLVM 15 given that build option or that patch is used, some not. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mesa-opencl-icd 22.2.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None
[Touch-packages] [Bug 2018525] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2018525 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: Screen freezes, then goes to black during a few seconds then returns to working state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem 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..07.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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 4 17:21:47 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-41-generic, x86_64: installed nvidia/525.105.17, 6.1.0-1008-oem, x86_64: installed ExtraDebuggingInterest: No GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GA104M [GeForce RTX 3070 Mobile / Max-Q] [1558:50f4] InstallationDate: Installed on 2023-01-27 (96 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Notebook NH5xVR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1008-oem root=UUID=c6e942e5-1878-4e2a-8d85-81abebd32761 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2021 dmi.bios.release: 7.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5xVR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.3 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.07.06:bd02/18/2021:br7.6:efr7.3:svnNotebook:pnNH5xVR:pvrNotApplicable:rvnNotebook:rnNH5xVR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5xVR dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.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.4-2ubuntu1.7~22.04.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-2ubuntu1 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/2018525/+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 2018525] [NEW] Xorg freeze
Public bug reported: Screen freezes, then goes to black during a few seconds then returns to working state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem 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..07.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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 4 17:21:47 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-41-generic, x86_64: installed nvidia/525.105.17, 6.1.0-1008-oem, x86_64: installed ExtraDebuggingInterest: No GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GA104M [GeForce RTX 3070 Mobile / Max-Q] [1558:50f4] InstallationDate: Installed on 2023-01-27 (96 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Notebook NH5xVR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1008-oem root=UUID=c6e942e5-1878-4e2a-8d85-81abebd32761 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2021 dmi.bios.release: 7.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5xVR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.3 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.07.06:bd02/18/2021:br7.6:efr7.3:svnNotebook:pnNH5xVR:pvrNotApplicable:rvnNotebook:rnNH5xVR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5xVR dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.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.4-2ubuntu1.7~22.04.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-2ubuntu1 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: Incomplete ** Tags: amd64 apport-bug freeze jammy 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/2018525 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: Screen freezes, then goes to black during a few seconds then returns to working state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem 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..07.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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
[Touch-packages] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Bionic) Assignee: (unassigned) => Andrei Gherzan (agherzan) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Status in lxc source package in Bionic: New Bug description: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 2017984] Re: Browser "Save as" dialog is not in dark mode
*** This bug is a duplicate of bug 2013126 *** https://bugs.launchpad.net/bugs/2013126 ** This bug has been marked a duplicate of bug 2013126 file chooser dialog doesn't respect system theme -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017984 Title: Browser "Save as" dialog is not in dark mode Status in gtk+3.0 package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20X4S1GH08 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrR1JET60W(1.60):bd11/22/2022:br1.60:efr1.48:svnLENOVO:pn20X4S1GH08:pvrThinkPadL15Gen2:rvnLENOVO:rn20X4S1GH08:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20X4_BU_Think_FM_ThinkPadL15Gen2: dmi.product.family: ThinkPad L15 Gen 2 dmi.product.name: 20X4S1GH08 dmi.product.sku: LENOVO_MT_20X4_BU_Think_FM_ThinkPad L15 Gen 2 dmi.product.version: ThinkPad L15 Gen 2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 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/gtk+3.0/+bug/2017984/+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 2018444] Re: [ASUS X555LAB] Kernel 6.2 touchpad won´t drag and drop (but 5.19 works)
** Summary changed: - Kernel 6.2 touchpad won´t drag and drop + [ASUS X555LAB] Kernel 6.2 touchpad won´t drag and drop (but 5.19 works) ** Package changed: xorg (Ubuntu) => linux (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/2018444 Title: [ASUS X555LAB] Kernel 6.2 touchpad won´t drag and drop (but 5.19 works) Status in linux package in Ubuntu: New Bug description: After upgrading to lunar lobster, I can´t drag and drop with my touchpad - it jumps around uncontrollably. If I reboot to the last version 5.19, it works ok. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Wed May 3 23:33:53 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2020-07-11 (1026 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera 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/11p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: ASUSTeK COMPUTER INC. X555LAB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=70b396bb-907c-46c9-a9da-18fecdb5f2d0 ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.603 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.603:bd04/16/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X555LAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 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/2018444/+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 1325949] Re: Add note to Debconf template about unintuitive inverted Etc/GMT offsets
** Changed in: tzdata (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1325949 Title: Add note to Debconf template about unintuitive inverted Etc/GMT offsets Status in tzdata package in Ubuntu: Fix Committed Status in tzdata package in Debian: New Bug description: Looks like GMT[+-} timezones have signs swapped. My local timezone is Europe/Tallinn When timezone is set to "Europe/Tallinn", everything is ok: # dpkg-reconfigure tzdata -> Europe/Tallinn # date Tue Jun 3 14:34:21 EEST 2014 # date +%z +0300 # date -u Tue Jun 3 11:34:59 UTC 2014 I need to set timezone to GMT+2, to avoid dailight savings time. When I set timezone to "GMT+2", things fall apart. Timezone is shown GMT+2/GMT-2. Clock is set to GMT-2. # dpkg-reconfigure tzdata -> Etc/GMT+2 # date Tue Jun 3 09:36:21 GMT+2 2014 # date +%z -0200 # date -u Tue Jun 3 11:37:43 UTC 2014 When I set timezone to "GMT-2", then it's turned around. Timezone is shown GMT-2/GMT+2. Clock is set to GMT+2. #dpkg-reconfigure tzdata -> Etc/GMT-2 # date Tue Jun 3 13:39:35 GMT-2 2014 # date +%z +0200 # date -u Tue Jun 3 11:39:56 UTC 2014 # lsb_release -rd Description:Ubuntu 12.04.4 LTS Release:12.04 # apt-cache policy tzdata tzdata: Installed: 2014c-0ubuntu0.12.04 Candidate: 2014c-0ubuntu0.12.04 Version table: *** 2014c-0ubuntu0.12.04 0 500 http://ee.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 2012e-0ubuntu0.12.04.1 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 2012b-1 0 500 http://ee.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages # apt-get update # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1325949/+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 2011432] Re: Display port audio recognized in live mode but not after installation
When I upgraded to 23.04 the HDMI Audio option appeared and is now working OK. Thanks. -- 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/2011432 Title: Display port audio recognized in live mode but not after installation Status in pulseaudio package in Ubuntu: New Bug description: After a powercut, my Display port sound device was not recognized. I tried troubleshooting but nothing worked. I then ran a 'live USB' of Ubuntu 22.04, Ubuntu 22.10, Xubuntu 22.04 and during live mode, all OSes recognized the Display port sound and sound worked. But after installing it, it was no long available. Pulseaudio is showing in the bug report as, before sending the report, on a vanilla install of Ubuntu 22.10, I ran through one more troubleshooting guide that installed Pulseaudio. The issue was not solved, and I am sure it is not due to pulse audio. Please let me know if you would like me to test anything. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pulseaudio 1:16.1+dfsg1-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: james 1415 F wireplumber /dev/snd/controlC1: james 1415 F wireplumber /dev/snd/seq:james 1412 F pipewire CasperMD5CheckMismatches: ./pool/restricted/l/linux-restricted-modules/linux-objects-nvidia-510-5.19.0-21-generic_5.19.0-21.21+1_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 20:19:48 2023 InstallationDate: Installed on 2023-03-12 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/24/2022 dmi.bios.release: 18.0 dmi.bios.vendor: HP dmi.bios.version: Q15 Ver. 02.18.00 dmi.board.name: 8463 dmi.board.vendor: HP dmi.board.version: KBC Version 07.D1.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.209 dmi.modalias: dmi:bvnHP:bvrQ15Ver.02.18.00:bd03/24/2022:br18.0:efr7.209:svnHP:pnHPEliteDesk705G4SFF:pvrDBXEnabled:rvnHP:rn8463:rvrKBCVersion07.D1.00:cvnHP:ct3:cvr:sku4HJ12AV: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 705 G4 SFF dmi.product.sku: 4HJ12AV dmi.product.version: DBXEnabled dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2011432/+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 2016404] Re: NetworkManager Applet popups continue despite asking not to
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/2016404 Title: NetworkManager Applet popups continue despite asking not to Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 23.04, I keep receiving popup notifications from "NetworkManager Applet" telling me that I am connected to a wifi network or disconnected from a wifi network. I repeatedly click on "Don't show this again", but they keep on being shown. My desktop environment is Unity. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager 1.42.4-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Apr 16 10:33:10 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2020-07-14 (1005 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.141 dev wlp0s20f3 proto dhcp src 192.168.86.33 metric 600 10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.86.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.86.33 metric 600 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: network-manager UpgradeStatus: Upgraded to lunar on 2023-03-31 (15 days ago) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [modified] mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-08-05T00:08:37.126151 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.42.4 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2016404/+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 2017770] Re: "Enter code on ubuntu.com/pro/attach" is not clickable URL like everything else
** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2017770 Title: "Enter code on ubuntu.com/pro/attach" is not clickable URL like everything else Status in software-properties package in Ubuntu: Confirmed Bug description: Enter code on ubuntu.com/pro/attach is not a clickable url. however ubuntu.com/pro and "register new account" are. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2017770/+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 1325949] Re: Add note to Debconf template about unintuitive inverted Etc/GMT offsets
Result from the upstream discussion: We will update debconf question with an explanation: https://mm.icann.org/pipermail/tz/2023-May/032942.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1325949 Title: Add note to Debconf template about unintuitive inverted Etc/GMT offsets Status in tzdata package in Ubuntu: Confirmed Status in tzdata package in Debian: New Bug description: Looks like GMT[+-} timezones have signs swapped. My local timezone is Europe/Tallinn When timezone is set to "Europe/Tallinn", everything is ok: # dpkg-reconfigure tzdata -> Europe/Tallinn # date Tue Jun 3 14:34:21 EEST 2014 # date +%z +0300 # date -u Tue Jun 3 11:34:59 UTC 2014 I need to set timezone to GMT+2, to avoid dailight savings time. When I set timezone to "GMT+2", things fall apart. Timezone is shown GMT+2/GMT-2. Clock is set to GMT-2. # dpkg-reconfigure tzdata -> Etc/GMT+2 # date Tue Jun 3 09:36:21 GMT+2 2014 # date +%z -0200 # date -u Tue Jun 3 11:37:43 UTC 2014 When I set timezone to "GMT-2", then it's turned around. Timezone is shown GMT-2/GMT+2. Clock is set to GMT+2. #dpkg-reconfigure tzdata -> Etc/GMT-2 # date Tue Jun 3 13:39:35 GMT-2 2014 # date +%z +0200 # date -u Tue Jun 3 11:39:56 UTC 2014 # lsb_release -rd Description:Ubuntu 12.04.4 LTS Release:12.04 # apt-cache policy tzdata tzdata: Installed: 2014c-0ubuntu0.12.04 Candidate: 2014c-0ubuntu0.12.04 Version table: *** 2014c-0ubuntu0.12.04 0 500 http://ee.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 2012e-0ubuntu0.12.04.1 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 2012b-1 0 500 http://ee.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages # apt-get update # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1325949/+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 2018457] Re: [SRU] Enable support for Bobcat Cloud Archive
** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Jammy) Status: New => Triaged ** Changed in: software-properties (Ubuntu Mantic) Status: New => Triaged ** Changed in: software-properties (Ubuntu Mantic) Importance: Undecided => High ** Changed in: software-properties (Ubuntu Jammy) Importance: Undecided => High -- 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/2018457 Title: [SRU] Enable support for Bobcat Cloud Archive Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Jammy: Triaged Status in software-properties source package in Mantic: Triaged Bug description: Please add support for: cloud-archive:bobcat cloud-archive:bobcat-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the antelope cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:bobcat sudo add-apt-repository cloud-archive:bobcat-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2018457/+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 2018439] Re: Apparmor crashes GPU acceleration
Hi Daniel. Thanks for the report! Could you try the following commands and let me know if they fix the issue? sudo sh -c "echo 'include ' >> /etc/apparmor.d/local/usr.bin.firefox" sudo apparmor_parser -r /etc/apparmor.d/usr.bin.firefox -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2018439 Title: Apparmor crashes GPU acceleration Status in apparmor package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: Apparmor crashes GPU acceleration Firefox GPU acceleration started crashing after updating from Ubuntu 22.10 to 23.04. $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 $ apt-cache policy firefox firefox: Installed: 113.0+build1-0ubuntu0.23.04.1~mt1 Candidate: 113.0+build1-0ubuntu0.23.04.1~mt1 Version table: 1:1snap1-0ubuntu3 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages *** 113.0+build1-0ubuntu0.23.04.1~mt1 999 500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy libglx-mesa0 libglx-mesa0: Installed: 23.0.3~kisak1~k Candidate: 23.0.3~kisak1~k Version table: *** 23.0.3~kisak1~k 500 500 https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 23.0.2-1ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages $ apt-cache policy apparmor apparmor: Installed: 3.0.8-1ubuntu2 Candidate: 3.0.8-1ubuntu2 Version table: *** 3.0.8-1ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status # Expected behavior Firefox should not crash in WebGL aquarium and continue to work properly like on 22.10. It should successfully use my GPU to make scrolling smooths and save battery when watching videos. # Actual behavior 1. Startup takes a second or two longer than usual 2. Typing in the address bar is slow 3. Scrolling takes 400% CPU usage 4. Scrolling stutters 5. VAAPI on https://www.w3schools.com/html/html5_video.asp is no longer used as shown in intel_gpu_top 6. Fans start spinning and battery goes down fast 7. glxtest failures had to be manually deleted in about:config 8. Only a few fish in WebGL aquarium (https://webglsamples.org/aquarium/aquarium.html) load before Firefox force-closes with the message: "Mozilla Crash Reporter Firefox had a problem and crashed. Unfortunately, the crash reporter is unable to submit a crash report. Details: The application did not leave a crash dump file. Close" 9. The following lines are relevant in dmesg after clearing it: [22157.695580] kauditd_printk_skb: 6 callbacks suppressed [22157.695582] audit: type=1400 audit(1683153440.994:2583): apparmor="DENIED" operation="capable" class="cap" profile="firefox" pid=15898 comm="firefox" capability=21 capname="sys_admin" [22157.739641] audit: type=1400 audit(1683153441.038:2584): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739647] audit: type=1400 audit(1683153441.038:2585): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739719] audit: type=1400 audit(1683153441.038:2586): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739729] audit: type=1400 audit(1683153441.038:2587): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.769407] audit: type=1400 audit(1683153441.070:2588): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/15898/oom_score_adj" pid=15898 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [22157.773042] audit: type=1400 audit(1683153441.074:2589): apparmor="DENIED" operation="file_mmap" class="file" profile="firefox//lsb_release" name="/usr/bin/dash" pid=15934 comm="lsb_release" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.974718] audit: type=1400 audit(1683153441.274:2590): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/15898/cgroup" pid=15898 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000
[Touch-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Same issue here, samsung galaxy book pro2, ALC298 -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 1926014] Re: simple-scan is trying to start disabled avahi-daemon.service
The report is now 2 years old, so I'm not sore if anyone will still read or follow this, but I don't think it's related to policykit, not even related to simple-scan. I got the same message recently, and it's probably related to the hpaio backend of sane (included in hplib). There's a bugreport on this here: https://bugs.launchpad.net/hplip/+bug/1996438 As a workaround, when no HP scanner is used, you can disable this e.g. by editing `/etc/sane.d/dll.d/hplib` and commenting out the only included library there: # dll.conf snippet for hplip # #hpaio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1926014 Title: simple-scan is trying to start disabled avahi-daemon.service Status in policykit-1 package in Ubuntu: New Bug description: Hi, I have a fresh installation of Ubuntu desktop 21.04. I stop and disable avahi-daemon.service + avahi-daemon.socket (I don't use these services on my desktop) Then I start "simple-scan" program. After that I see a pop-up window for admin password! It's wrong, no such thing should be there. In previouse release (20.10) it was OK. Thanks. Antonin ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: policykit-1 0.105-30 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 15:17:52 2021 InstallationDate: Installed on 2021-04-22 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1926014/+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 2013543] Re: systemctl daemon-reexec forgets running services and starts everything new
Nike - Unfortunately, I don't have the resources to put a new image in our environment. But I've updated systemd (and all related) libraries to `252.5-2ubuntu3` and it's still "broken": `systemctl daemon-reexec` forgets all the old processes and restarts everything. -- 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/2013543 Title: systemctl daemon-reexec forgets running services and starts everything new Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Jammy: Incomplete Bug description: # Our problem # During a regular update of our container environment, `systemd` (and the related packages libpam-systemd, libsystemd0, libudev1, systemd- sysv and udev) were updated from `249.11-0ubuntu3.6` to `249.11-0ubuntu3.7`. We're talking only about Ubuntu 22.04. Our Ubuntu 20.04 is working fine with `systemctl daemon-reexec`. In my opinion, the update was not the problem because we've tried downgrading and tried these versions: (current) `249.11-0ubuntu3.7`, `249.11-0ubuntu3.6`, `249.11-0ubuntu3.4` and `249.11-0ubuntu3.3`. The symptoms were the same. # Symptoms # The `/var/lib/dpkg/info/systemd.postinst` executes a `systemctl daemon-reexec` and that ended in a disaster. It seems that `systemd` is forgetting all it started children and tries to start nearly every configured service again. Naturally, the old services are still running, and the ports can't be opened twice and `systemd` won't give up. Here are some(!) of the logfiles: Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Starting Create Volatile Files and Directories... Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found left-over process 130 (systemd-udevd) in control group while starting unit. Ignoring. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found left-over process 31475 (systemd-udevd) in control group while starting unit. Ignoring. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found left-over process 31476 (systemd-udevd) in control group while starting unit. Ignoring. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. And... Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Reached target System Initialization. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily apt download activities. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily apt upgrade and clean activities. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily dpkg database backup timer. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Periodic ext4 Online Metadata Check for All Filesystems. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Condition check resulted in Discard unused blocks once a week being skipped. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily rotation of log files. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily man-db regeneration. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Message of the Day. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Clean PHP session files every 30 mins. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Update the plocate database daily. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily Cleanup of Temporary Directories. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Reached target Basic System. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: System is tainted: cgroupsv1 Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Reached target Timer Units. And... Mar 31 12:51:39 FQDN_REDACTED systemd[1]: atd.service: Found left-over process 206 (atd) in control group while starting unit. Ignoring. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Starting Deferred execution scheduler... Mar 31 12:51:39 FQDN_REDACTED systemd[1]: cron.service: Found left-over process 164 (cron) in control group while starting unit. Ignoring. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Regular background program processing daemon. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: dbus.service: Found left-over process 177 (dbus-daemon) in control group while starting unit. Ignoring. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean termination of
[Touch-packages] [Bug 2018457] [NEW] [SRU] Enable support for Bobcat Cloud Archive
Public bug reported: Please add support for: cloud-archive:bobcat cloud-archive:bobcat-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the antelope cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:bobcat sudo add-apt-repository cloud-archive:bobcat-proposed [Regression potential] Limited - just a data item addition ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- 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/2018457 Title: [SRU] Enable support for Bobcat Cloud Archive Status in software-properties package in Ubuntu: New Bug description: Please add support for: cloud-archive:bobcat cloud-archive:bobcat-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the antelope cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:bobcat sudo add-apt-repository cloud-archive:bobcat-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2018457/+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 972077] Re: apt repository disk format has race conditions
That's a hashicorp problem if they serve repositories without by-hash or atomically updated dists/ directory, this bug here is solved. -- 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/972077 Title: apt repository disk format has race conditions Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+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 972077] Re: apt repository disk format has race conditions
I'm also affected by this (a Hashicorp repo): ``` Get:14 https://apt.releases.hashicorp.com jammy/main i386 Packages [31,3 kB] Err:14 https://apt.releases.hashicorp.com jammy/main i386 Packages File has unexpected size (31295 != 31290). Mirror sync in progress? [IP: 18.173.5.94 443] Hashes of expected file: - Filesize:31290 [weak] - SHA256:a1aba716abdbf9f2e3bc13d25734ff9fcc58a399698795ebc98f7cec76146d2e - SHA1:20e1b9792e678e5223d1387e4e5effaf5a4ca24f [weak] - MD5Sum:647502cff7f79ac8a4641b6519696b30 [weak] Release file created at: Wed, 03 May 2023 21:28:51 + ``` and in the summary: ``` Reading package lists... Done E: Failed to fetch https://apt.releases.hashicorp.com/dists/jammy/main/binary-i386/Packages.bz2 File has unexpected size (31295 != 31290). Mirror sync in progress? [IP: 18.173.5.94 443] Hashes of expected file: - Filesize:31290 [weak] - SHA256:a1aba716abdbf9f2e3bc13d25734ff9fcc58a399698795ebc98f7cec76146d2e - SHA1:20e1b9792e678e5223d1387e4e5effaf5a4ca24f [weak] - MD5Sum:647502cff7f79ac8a4641b6519696b30 [weak] Release file created at: Wed, 03 May 2023 21:28:51 + E: Some index files failed to download. They have been ignored, or old ones used instead. ``` -- 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/972077 Title: apt repository disk format has race conditions Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+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 2018352] Re: Scaling wrong on external display when setting 100% scaling
** Summary changed: - Resolution wrong on external display when setting 100% scaling + Scaling wrong on external display when setting 100% scaling ** Description changed: - Resolution on external display is wrong when setting 100% scaling on it. It becomes too big, bigger than when set to 125% + Scaling on external display is wrong when setting 100% scaling on it. It becomes too big, bigger than when set to 125% This happens with Xorg on Ubuntu 23.04 with NVIDIA GPU set as only GPU in the system ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 - GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 + GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 3 08:27:32 2023 DistUpgraded: 2023-04-20 10:00:59,509 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] + NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] InstallationDate: Installed on 2023-02-09 (82 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82N6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=2a43fd27-b65c-4d7a-bc19-b001521b0771 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-20 (12 days ago) dmi.bios.date: 03/07/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN60WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.60 dmi.modalias: dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 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 -- 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/2018352 Title: Scaling wrong on external display when setting 100% scaling Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Scaling on external display is wrong when setting 100% scaling on it. It becomes too big, bigger than when set to 125% This happens with Xorg on Ubuntu 23.04 with NVIDIA GPU set as only GPU in the system ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia
[Touch-packages] [Bug 1942703] Re: Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around
** Changed in: unattended-upgrades Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1942703 Title: Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: New Bug description: If user has linux-generic-hwe-18.04 installed, versioned linux-headers packages depend on versioned linux-hwe-5.4-headers packages that will not get removed. Consequently in time there will be hundreds of thousands of unused files under /usr/src. For example I have about 45 totalling 1.4 GB. The number of inodes may be bigger issue, because file systems have some limitations. I noted the issue when using my linux-purge tool. It is supposed to be able to remove kernels, even if the file system runs out of inodes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.14 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic i686 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: i386 Date: Sun Sep 5 14:38:49 2021 InstallationDate: Installed on 2016-09-05 (1826 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to bionic on 2019-04-06 (882 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-03-26T11:42:30.041160 To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1942703/+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 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
** Changed in: openssl (Ubuntu Bionic)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983100
Title:
dotnet build intermittently crashes with segfault on Ubuntu 18.04
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Bionic:
In Progress
Bug description:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that
does not have support for the OPENSSL_NO_ATEXIT functionality from
1.1.1b (openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background
threads are still running when exit() is called, which can cause
SIGSEGV if a background thread interacts with OpenSSL after/while it
has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with
the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only
has no effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published
into the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
[Test Plan]
The described behavior can be reproduced by passing the
OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
terminate with a SEGFAULT. More concretely, a minimal reproducer is:
#include
#include
#include
#ifndef OPENSSL_INIT_NO_ATEXIT
#define OPENSSL_INIT_NO_ATEXIT 0x0008L
#endif
static void print_error_string()
{
printf("print_error_string:\n");
printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0));
}
int main(int argc, char* argv[])
{
// register this handler first, so it runs last.
atexit(print_error_string);
OPENSSL_init_ssl(
OPENSSL_INIT_ADD_ALL_CIPHERS |
OPENSSL_INIT_ADD_ALL_DIGESTS |
OPENSSL_INIT_LOAD_CONFIG |
OPENSSL_INIT_NO_ATEXIT |
OPENSSL_INIT_LOAD_CRYPTO_STRINGS |
OPENSSL_INIT_LOAD_SSL_STRINGS,
NULL);
print_error_string();
return 0;
}
Building
$ sudo apt install libssl-dev
$ gcc test.c -lssl -lcrypto
$ ./a.out
print_error_string:
ERR_reason_error_string(0) => (null)
print_error_string:
Segmentation fault (core dumped)
[Other Info]
All of these patches are included in upstream release 1.1.1b
- lp1983100-0001-Fix-shlibloadtest-to-properly-execute-the-dso_ref-te.patch
Fixes the shlibloadtest that was updated as part of #0005
- lp1983100-0002-Implement-OPENSSL_INIT_NO_ATEXIT.patch
Patch adds the OPENSSL_INIT_NO_ATEXIT option
- lp1983100-0003-Don-t-link-shlibloadtest-against-libcrypto.patch
Additional fixes for shlibloadtest
- lp1983100-0004-Fix-rpath-related-Linux-test_shlibload-failure.patch
Additional fixes for shlibloadtest
- lp1983100-0005-Test-atexit-handlers.patch
Adds test for OPENSSL_INIT_NO_ATEXIT option and updates the shlibloadtest
- lp1983100-0006-Introduce-a-no-pinshared-option.patch
This patch includes tests to ensure that if OPENSSL_INIT_NO_ATEXIT is not
defined then the atexit() handler is run
- lp1983100-0007-Support-_onexit-in-preference-to-atexit-on-Windows.patch
This patch ensures that atexit() is only called when on non-Windows systems
as Windows uses _onexit() during library unloading
All seven patches are required to ensure the correct logic and
operation of the OPENSSL_INIT_NO_ATEXIT option.
[Where problems could occur]
The patches adds an option to the OPENSSL_init_crypto() function to
disable the default behavior of calling of a cleanup function on
application exit. The patch also includes a few bug fixes around
various initializations that were supposed to happen once when running
threaded but were not.
These changes have the potential for regressions and it is conceivable
that they lead to incorrect behavior. However, I have also backported
and included all new testing functions in the hope that the changed
behavior will get appropriate testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100/+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
