[Touch-packages] [Bug 2063000] Re: Running ubuntu-bug outputs errors
Ubuntu-desktop 24.04 development branch @ 21/04/2024 Im also having these warnings, but apport can still proceed with the bug filing, it just leaves these cloud warnings indeed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2063000 Title: Running ubuntu-bug outputs errors Status in apport package in Ubuntu: Confirmed Bug description: ubuntu-bug reports errors accessing cloud.cfg.d files: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg, insufficient permissions . ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 ApportLog: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 20 23:59:59 2024 InstallationDate: Installed on 2024-04-20 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta amd64 (20240420) PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063000/+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 2063000] Re: Running ubuntu-bug outputs errors
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2063000 Title: Running ubuntu-bug outputs errors Status in apport package in Ubuntu: Confirmed Bug description: ubuntu-bug reports errors accessing cloud.cfg.d files: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg, insufficient permissions . ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 ApportLog: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 20 23:59:59 2024 InstallationDate: Installed on 2024-04-20 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta amd64 (20240420) PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063000/+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 2063012] [NEW] package libglib2.0-0:armhf 2.72.4-0ubuntu2.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: Error while apt full-upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libglib2.0-0:armhf 2.72.4-0ubuntu2.2 Uname: Linux 4.9.140-l4t aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Sun Apr 21 11:23:54 2024 ErrorMessage: dependency problems - leaving triggers unprocessed PackageArchitecture: armhf Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: glib2.0 Title: package libglib2.0-0:armhf 2.72.4-0ubuntu2.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063012 Title: package libglib2.0-0:armhf 2.72.4-0ubuntu2.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: Error while apt full-upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libglib2.0-0:armhf 2.72.4-0ubuntu2.2 Uname: Linux 4.9.140-l4t aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Sun Apr 21 11:23:54 2024 ErrorMessage: dependency problems - leaving triggers unprocessed PackageArchitecture: armhf Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: glib2.0 Title: package libglib2.0-0:armhf 2.72.4-0ubuntu2.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063012/+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 2063005] Re: Onscreen keyboard is disabled by default
Sorry, I missed the "X11 session" part. Bug confirmed. ** No longer affects: gsettings-desktop-schemas (Ubuntu) ** Summary changed: - Onscreen keyboard is disabled by default + Some shell elements don't respond to touchscreen in Xorg sessions ** Changed in: gnome-shell (Ubuntu) Importance: Low => Medium ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+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 2063005] Re: Onscreen keyboard is disabled by default
Looks like it's been disabled for at least 6 years: https://gitlab.gnome.org/GNOME/gsettings-desktop- schemas/-/blob/master/schemas/org.gnome.desktop.a11y.applications.gschema.xml.in?ref_type=heads so whether or not it gets toggled automatically is probably up to gnome- shell. ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: New => Won't Fix ** Changed in: gnome-shell (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Onscreen keyboard is disabled by default Status in gnome-shell package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+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 2063005] Re: touchscreen input critical regressions in GNOME 45 to 46
Partially confirmed. It looks like the onscreen keyboard is always disabled by default. You have to enable it in: Settings > Accessibility > Typing > Screen Keyboard = ON After I did that, all the features mentioned here started working. ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Summary changed: - touchscreen input critical regressions in GNOME 45 to 46 + Onscreen keyboard is disabled by default ** Tags added: osk ** Also affects: gsettings-desktop-schemas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Onscreen keyboard is disabled by default Status in gnome-shell package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Per https://irclogs.ubuntu.com/2024/04/20/%23ubuntu-release.html#t18:58
the required kernel is -31, which is currently in proposed
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2063003] Re: package manager could not make changes to the installed system
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/2063003 ** Tags added: iso-testing -- 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/2063003 Title: package manager could not make changes to the installed system Status in apt package in Ubuntu: New Bug description: This is the cause of Ubuntu Unity failing to install. Test case requires system to be offline. The full error message is: The package manager could not make changes to the installed system. The command apt-get --purge -q -y remove ^live-* calamares-settings-ubuntu-unity calamares zram-config cifs-utils returned error code 100. There are no logs in /var/log/installer or /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2063003/+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 2063006] [NEW] e4defrag led to kernel reporting split-lock and 2 corrupted RAID arrays
Public bug reported: I was curious how e4defrag works and how it could optimize a speed and loudness of 48TB mdraid array with four 16TB drives in RAID5 and tried the defrag on the whole mountpoint. After a couple of minutes the mountpoint became inaccessible and I found two of the drives marked as faulty even when S.M.A.R.T. is healthy. The dmesg log showed many messages related to "split-lock", unfortunately I don't remeber the exact wording. The whole computer became unstable and I decided to reboot. The boot failed as well, as it also damaged data on a second RAID1 array with system that I didn't touch with the e4defrag at all. So, one array kicked out 2 drives and one array ended up with a filesystem corruption and fsck fixing many issues. I could reassemble the RAID with "assume-clean" and it seems to be ok now, but the whole incident makes me believe there could be something unhealthy in the kernel's ioctl or deeper that needs attention. The kernel version is 5.15.0-102-generic #112-Ubuntu SMP The e2fsprogs version is 1.46.5-2ubuntu1.1 ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Description changed: I was curious how e4defrag works and how it could optimize a speed and loudness of 48TB mdraid array with four 16TB drives in RAID5 and tried the defrag on the whole mountpoint. After a couple of minutes the mountpoint became inaccessible and I found two of the drives marked as - faulty even when S.M.A.R.T. is healthy. The dmesg log shown many + faulty even when S.M.A.R.T. is healthy. The dmesg log showed many messages related to "split-lock", unfortunately I don't remeber the exact wording. The whole computer became unstable and I decided to reboot. The boot failed as well, as it also damaged data on a second RAID1 array with system that I didn't touch with the e4defrag at all. So, one array kicked out 2 drives and one array ended up with a filesystem corruption and fsck fixing many issues. I could reassemble the RAID with "assume-clean" and it seems to be ok now, but the whole incident makes me believe there could be something unhealthy in the kernel's ioctl or deeper that needs attention. The kernel version is 5.15.0-102-generic #112-Ubuntu SMP The e2fsprogs version is 1.46.5-2ubuntu1.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2063006 Title: e4defrag led to kernel reporting split-lock and 2 corrupted RAID arrays Status in e2fsprogs package in Ubuntu: New Bug description: I was curious how e4defrag works and how it could optimize a speed and loudness of 48TB mdraid array with four 16TB drives in RAID5 and tried the defrag on the whole mountpoint. After a couple of minutes the mountpoint became inaccessible and I found two of the drives marked as faulty even when S.M.A.R.T. is healthy. The dmesg log showed many messages related to "split-lock", unfortunately I don't remeber the exact wording. The whole computer became unstable and I decided to reboot. The boot failed as well, as it also damaged data on a second RAID1 array with system that I didn't touch with the e4defrag at all. So, one array kicked out 2 drives and one array ended up with a filesystem corruption and fsck fixing many issues. I could reassemble the RAID with "assume-clean" and it seems to be ok now, but the whole incident makes me believe there could be something unhealthy in the kernel's ioctl or deeper that needs attention. The kernel version is 5.15.0-102-generic #112-Ubuntu SMP The e2fsprogs version is 1.46.5-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2063006/+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 2063003] Re: package manager could not make changes to the installed system
Error does not prevent the installed system from booting, but it still contains the installer and related items. -- 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/2063003 Title: package manager could not make changes to the installed system Status in apt package in Ubuntu: New Bug description: This is the cause of Ubuntu Unity failing to install. Test case requires system to be offline. The full error message is: The package manager could not make changes to the installed system. The command apt-get --purge -q -y remove ^live-* calamares-settings-ubuntu-unity calamares zram-config cifs-utils returned error code 100. There are no logs in /var/log/installer or /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2063003/+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 2063003] [NEW] package manager could not make changes to the installed system
Public bug reported: This is the cause of Ubuntu Unity failing to install. Test case requires system to be offline. The full error message is: The package manager could not make changes to the installed system. The command apt-get --purge -q -y remove ^live-* calamares-settings-ubuntu-unity calamares zram-config cifs-utils returned error code 100. There are no logs in /var/log/installer or /var/crash ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2063003 Title: package manager could not make changes to the installed system Status in apt package in Ubuntu: New Bug description: This is the cause of Ubuntu Unity failing to install. Test case requires system to be offline. The full error message is: The package manager could not make changes to the installed system. The command apt-get --purge -q -y remove ^live-* calamares-settings-ubuntu-unity calamares zram-config cifs-utils returned error code 100. There are no logs in /var/log/installer or /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2063003/+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 2063000] [NEW] Running ubuntu-bug outputs errors
Public bug reported: ubuntu-bug reports errors accessing cloud.cfg.d files: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg, insufficient permissions . ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 ApportLog: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 20 23:59:59 2024 InstallationDate: Installed on 2024-04-20 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta amd64 (20240420) PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2063000 Title: Running ubuntu-bug outputs errors Status in apport package in Ubuntu: New Bug description: ubuntu-bug reports errors accessing cloud.cfg.d files: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg, insufficient permissions . ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 ApportLog: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 20 23:59:59 2024 InstallationDate: Installed on 2024-04-20 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta amd64 (20240420) PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063000/+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 2057943] Re: Can't disable or modify snap package apparmor rules
I will note that current snap behavior is by design. Not saying that
they couldn't make this easier but the snap side is functioning the way
it was desiged.
--
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/2057943
Title:
Can't disable or modify snap package apparmor rules
Status in apparmor package in Ubuntu:
New
Status in snapd package in Ubuntu:
New
Bug description:
On Ubuntu 20.04 (and probably 22.04 and greater), it is impossible to
disable snap chromium apparmor rules:
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure
Can't find chromium.hook.configure in the system path list. If the name of
the application
is correct, please run 'which snap.chromium.hook.configure' as a user with
correct PATH
environment set up in order to find the fully-qualified path and
use the full path as parameter.
root@{HOSTNAME}:~# aa-complain snap.chromium.chromedriver -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.chromium -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global
not found
It seems like no one has an answer on how these overly restricted
rules can be disabled:
https://askubuntu.com/questions/1267980/how-to-disable-apparmor-for-chromium-snap-ubuntu-20-04
https://ubuntuforums.org/showthread.php?t=2410550
https://ubuntuforums.org/showthread.php?t=2449022
https://answers.launchpad.net/ubuntu/+source/apparmor/+question/701036
So I just got rid of apparmor which doesn't seem like the solution I
was after, but it works great now:
sudo systemctl stop apparmor
sudo systemctl disable apparmor
Please give us a way to modify (and keep the rules permanently
modified even after snap updates) snap apparmor rules.
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057943/+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 2061995] Re: ULTS 22, 24: FontConfig broken by including ".conf" file
** Summary changed: - ULLTS 22,24: FontConfig broken by including ".conf" file + ULTS 22,24: FontConfig broken by including ".conf" file -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2061995 Title: ULTS 22,24: FontConfig broken by including ".conf" file Status in Ubuntu: New Status in fontconfig package in Ubuntu: New Bug description: This happens to me on both ULTS 22 and ULKTS 24 on FotnConfig in somewhat different ways: * In ULTS 24 if there is a file '/etc/fonts/local.conf' then all fonts are rendered as if the font were not hinted or 'hinting' were 'false'. This is not noticeable if antialiasing is on, and most users default to antialiasing. * In ULTS 22 if there is a file '$XDG_CONFIG_HOME/fontconfig/fonts.conf' then some fonts are no longer found, or get rendered with rectangular shapes. I guess not many users customize their font settings. A telling example from ULTS 22: $ cat /etc/fonts/conf.d/10-antialias.conf false $ cp -p /etc/fonts/conf.d/10-antialias.conf $XDG_CONFIG_HOME/fontconfig/fonts.conf $ fc-list 'dejavu sans mono' family $ rm $XDG_CONFIG_HOME/fontconfig/fonts.conf $ fc-list 'dejavu sans mono' family DejaVu Sans Mono This happens also with a skeleton '$XDG_CONFIG_HOME/fontconfig/fonts.conf' (or '/etc/fonts/local.conf') too: $ cat > $XDG_CONFIG_HOME/fontconfig/fonts.conf $ fc-list 'dejavu sans mono' family $ rm $XDG_CONFIG_HOME/fontconfig/fonts.conf $ fc-list 'dejavu sans mono' family DejaVu Sans Mono None of these anomalies happen under ULST 20. My impression: symptoms vary and are weird, so probably it is something like a buffer overflow when reading the ".conf" files or the use of not-initialized memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061995/+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 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12
** Changed in: cython (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2049369 Title: autopkg tests ignored for migration of python3-defaults adding 3.12 Status in cython package in Ubuntu: New Status in cython-legacy package in Ubuntu: New Status in ipykernel package in Ubuntu: New Status in ironic-python-agent package in Ubuntu: New Status in jupyter-client package in Ubuntu: New Status in numpy package in Ubuntu: New Status in python-memory-profiler package in Ubuntu: New Status in python-oslo.versionedobjects package in Ubuntu: Fix Released Status in python-urllib3 package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in rich package in Ubuntu: New Status in sphinx-autoapi package in Ubuntu: New Status in vcr.py package in Ubuntu: New Status in cython package in Debian: Fix Released Status in cython-legacy package in Debian: Fix Released Status in ipykernel package in Debian: Fix Released Status in jupyter-client package in Debian: Confirmed Status in numpy package in Debian: Fix Released Status in python-memory-profiler package in Debian: New Status in python-urllib3 package in Debian: Fix Released Status in rich package in Debian: Fix Released Status in sphinx-autoapi package in Debian: Fix Released Status in vcr.py package in Debian: Fix Released Bug description: autopkg tests ignored for migration of python3-defaults adding 3.12: These are the autopkg tests for packages, which we'll ignore for the initial migration of python3-defaults adding 3.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056758] Re: ubuntu-bug doesn't let me file bugs for Snap thunderbird
> Do you have the thunderbird deb also installed? Do you get prompted to report against the snap or deb? if by the deb you mean the transitional package, then i have it uninstalled, marked as "residual-config". I don't get prompted to file against the deb. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2056758 Title: ubuntu-bug doesn't let me file bugs for Snap thunderbird Status in apport package in Ubuntu: Triaged Status in thunderbird package in Ubuntu: Incomplete Bug description: I'm trying to report a bug in the new Snap for Thunderbird. When I run "ubuntu-bug thunderbird", it: * Collects information correctly after I input the sudo password * Opens a page like https://bugs.launchpad.net/distros/+filebug/a9564134-dfa6-11ee-85a7-c7116d9f638e?, which does not seem to be valid. This is not the case for Firefox, which works fine with ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:483410:2024-03-11 14:47:26.874792575 +0400:2024-03-11 14:47:27.874792575 +0400:/var/crash/_opt_Citrix_ICAClient_util_storebrowse.1000.crash 640:0:124:29135:2024-03-10 17:02:30.124656623 +0400:2024-03-10 17:02:30.124656623 +0400:/var/crash/_usr_share_apport_apport.0.crash CurrentDesktop: KDE Date: Mon Mar 11 16:54:18 2024 InstallationDate: Installed on 2022-08-29 (560 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to noble on 2024-02-23 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2056758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062982] [NEW] [USB-Audio - SB Live! 24-bit External, playback] volume slider and mute button have no effect
Public bug reported: When the external sound card (SB Live! 24 bit) is used, the volume slider and the mute button have no effect. The volume is low. I tried two SB Live! 24 bit cards (at home and at work). The behaviour is the same. On Lubuntu 20.04, there was no problem. The embedded sound card operates normally and reacts on the volume slider. Ubuntu 22.04.4 LTS pulseaudio 1:15.99.1+dfsg1-1ubuntu2.2 pavucontrol 5.0-2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.8.7-2-liquorix-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 20 21:33:26 2024 InstallationDate: Installed on 2024-04-03 (16 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: SoundBlaster Live! 24-bit External SB0490 - SB Live! 24-bit External Symptom_PulseAudioLog: кві 20 19:57:33 Lattitude dbus-daemon[590]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.33' (uid=1001 pid=845 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - SB Live! 24-bit External, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2023 dmi.bios.release: 1.32 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.32.2 dmi.board.name: 015DR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: NTB71181 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.32.2:bd09/22/2023:br1.32:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn015DR5:rvrA00:cvnDellInc.:ct10:cvr:sku07A7: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2062982 Title: [USB-Audio - SB Live! 24-bit External, playback] volume slider and mute button have no effect Status in alsa-driver package in Ubuntu: New Bug description: When the external sound card (SB Live! 24 bit) is used, the volume slider and the mute button have no effect. The volume is low. I tried two SB Live! 24 bit cards (at home and at work). The behaviour is the same. On Lubuntu 20.04, there was no problem. The embedded sound card operates normally and reacts on the volume slider. Ubuntu 22.04.4 LTS pulseaudio 1:15.99.1+dfsg1-1ubuntu2.2 pavucontrol 5.0-2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.8.7-2-liquorix-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 20 21:33:26 2024 InstallationDate: Installed on 2024-04-03 (16 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: SoundBlaster Live! 24-bit External SB0490 - SB Live! 24-bit External Symptom_PulseAudioLog: кві 20 19:57:33 Lattitude dbus-daemon[590]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.33' (uid=1001 pid=845 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - SB Live! 24-bit External, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2023 dmi.bios.release: 1.32 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.32.2 dmi.board.name: 015DR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: NTB71181 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.32.2:bd09/22/2023:br1.32:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn015DR5:rvrA00:cvnDellInc.:ct10:cvr:sku07A7: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2062982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure
** Description changed: + this is running with LC_ALL=C + + the following are output in terminal when configuring dictionaries- + common + Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine ::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): - installed dictionaries-common package post-installation script subprocess returned error exit status 2 + installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: - dictionaries-common + dictionaries-common + + this worked without issues when I last built images of ubuntu-noble in + late February 2024 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure Status in aspell package in Ubuntu: New Status in dictionaries-common package in Ubuntu: New Bug description: this is running with LC_ALL=C the following are output in terminal when configuring dictionaries- common Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine ::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dictionaries-common this worked without issues when I last built images of ubuntu-noble in late February 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062979] [NEW] unable to create ubuntu-noble image due to dictionaries-common config failure
Public bug reported: Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine ::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dictionaries-common ** Affects: aspell (Ubuntu) Importance: Undecided Status: New ** Affects: dictionaries-common (Ubuntu) Importance: Undecided Status: New ** Also affects: aspell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure Status in aspell package in Ubuntu: New Status in dictionaries-common package in Ubuntu: New Bug description: Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine ::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dictionaries-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
Unfortunately, my sound finally did fail again... But the symptoms seem different. Audacious just hangs for a while before ultimately giving up (and it stops hanging and stops trying to play). But this is a new type of failure so perhaps this patch did make a bit of a difference? https://bugzilla.kernel.org/show_bug.cgi?id=208555#c863 But this happened immediately after resuming from suspend. My laptop went to sleep with mute enabled, I started playing sound after resuming, noticed I was muted, and resumed... And sound was no longer working. Could bec7760a6c5fa59593dac264fa0c628e46815986 be the issue? This did not fixed my count: amixer -c 0 cset numid=3,name='Speaker Force Firmware Load' 1 (-c 1 is incorrect for my laptop.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062501] Re: Dhcpcd prioritizes (unconnnected) LAN adapter over WLAN, causing a 5 min boot delay
Thanks. Then I mark this bug as Invalid for initramfs-tools. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2062501 Title: Dhcpcd prioritizes (unconnnected) LAN adapter over WLAN, causing a 5 min boot delay Status in aoetools package in Ubuntu: New Status in initramfs-tools package in Ubuntu: Invalid Bug description: After upgrading to Ubuntu 24.04, dhcpcd spends over five minutes trying to obtain a DHCP lease for an unconnected LAN adapter during startup. Only after this process times out, the boot process resumes. Consequently, startup works flawlessly, if the laptop is connected to the LAN, but takes five additional minutes, if that's not the case. Please find below the console output (obtained by pressing "ESC" during bootup) Setting ip link enp0s... up Setting ip link enx0... up dhcpcd-10.0.6 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot Sleeping 30 seconds before retrying getting a DHCP lease dhcpcd-10.0.6 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot Sleeping 60 seconds before retrying getting a DHCP lease ... dhcpcd-10.0.6 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot Sleeping 120 seconds before retrying getting a DHCP lease After multiples tries to obtain a DHCP lease (which take approximately five minutes) the standard boot process resumes. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: initramfs-tools 0.142ubuntu25 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.1-0ubuntu1 Architecture: amd64 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-firmware-535-535.113.01_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/xserver-xorg-video-nvidia-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-compute-utils-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-source-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-driver-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-utils-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-common-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.113.01-0ubuntu3_i386.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 07:40:31 2024 InstallationDate: Installed on 2023-12-03 (138 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to noble on 2024-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aoetools/+bug/2062501/+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 2062501] Re: Dhcpcd prioritizes (unconnnected) LAN adapter over WLAN, causing a 5 min boot delay
Thank you for helping debug this issue. I concur with your assessment. - this should be handled by aoetools (probably similar to the way nfs versus nfsroot is handled). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2062501 Title: Dhcpcd prioritizes (unconnnected) LAN adapter over WLAN, causing a 5 min boot delay Status in aoetools package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Bug description: After upgrading to Ubuntu 24.04, dhcpcd spends over five minutes trying to obtain a DHCP lease for an unconnected LAN adapter during startup. Only after this process times out, the boot process resumes. Consequently, startup works flawlessly, if the laptop is connected to the LAN, but takes five additional minutes, if that's not the case. Please find below the console output (obtained by pressing "ESC" during bootup) Setting ip link enp0s... up Setting ip link enx0... up dhcpcd-10.0.6 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot Sleeping 30 seconds before retrying getting a DHCP lease dhcpcd-10.0.6 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot Sleeping 60 seconds before retrying getting a DHCP lease ... dhcpcd-10.0.6 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot Sleeping 120 seconds before retrying getting a DHCP lease After multiples tries to obtain a DHCP lease (which take approximately five minutes) the standard boot process resumes. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: initramfs-tools 0.142ubuntu25 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.1-0ubuntu1 Architecture: amd64 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-firmware-535-535.113.01_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/xserver-xorg-video-nvidia-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-compute-utils-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-source-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-driver-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-utils-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-common-535_535.113.01-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.113.01-0ubuntu3_i386.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 07:40:31 2024 InstallationDate: Installed on 2023-12-03 (138 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to noble on 2024-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aoetools/+bug/2062501/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Oh the new kernel wasn't built with the new zfs-dkms =/
II: dkms-build downloading zfs (zfs-dkms_2.2.2-0ubuntu7_all.deb)
II: fetching
https://launchpad.net/ubuntu/+archive/primary/+files/zfs-dkms_2.2.2-0ubuntu7_all.deb
II: fixing
https://launchpadlibrarian.net/718392332/zfs-dkms_2.2.2-0ubuntu7_all.deb
II: following
http://launchpadlibrarian.net/718392332/zfs-dkms_2.2.2-0ubuntu7_all.deb
II: dkms-build-configure dkms-build-configure--zfs found, executing
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2061337] Re: systemd-localed crashed with SIGABRT in __waitid()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2061337 Title: systemd-localed crashed with SIGABRT in __waitid() Status in systemd package in Ubuntu: Confirmed Bug description: send report is displaed on install ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.496 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) Date: Mon Apr 15 09:23:26 2024 ExecutablePath: /usr/lib/systemd/systemd-localed LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) Lspci: Lspci-vt: Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcCmdline: /usr/lib/systemd/systemd-localed ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SignalName: SIGABRT SourcePackage: systemd StacktraceTop: __waitid (idtype=P_PID, id=3636, infop=0x7ffeb9206940, options=4) at ../sysdeps/unix/sysv/linux/waitid.c:29 wait_for_terminate () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-255.so wait_for_terminate_and_check () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-255.so safe_fork_full () from /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-255.so ?? () SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Title: systemd-localed crashed with SIGABRT in __waitid() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 1040-4220-4322-0021-6896-6557-30 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2061337/+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 2062542] Re: systemd-resolved stub gives SERVFAIL for DNSSEC negative response
This is on mantic, systemd-resolved 253.5-1ubuntu6.1 ** Tags added: mantic ** Description changed: - This issue surface when researching the issue that Postfix on my system + This issue surfaced when researching the issue that Postfix on my system (with DANE enabled) deferred mail deliveries with 100s of this warning in the log: - Warning: DANE TLSA lookup problem: Host or domain name not found. + Warning: DANE TLSA lookup problem: Host or domain name not found. Name service error for name=_25._tcp.cluster5.us.messagelabs.com type=TLSA: Host not found, try again The DNS resolver on my machine was pointing at the systemd-resolved stub: - $ cat /etc/resolv.conf | grep nameserver - nameserver 127.0.0.53 + $ cat /etc/resolv.conf | grep nameserver + nameserver 127.0.0.53 - $ resolvectl status - Global - Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported - resolv.conf mode: stub + $ resolvectl status + Global + Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported + resolv.conf mode: stub Note DNSSEC is enabled (else Postfix couldn't be doing DANE). Now if I query the TLSA record for the messagelab server, I get a SERVFAIL from the stub resolver: - $ delv +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA - ;; resolution failed: SERVFAIL + $ delv +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA + ;; resolution failed: SERVFAIL Whereas if I query my upstream DNS or Google DNS, I get a DNSSEC validated (negative) response: - $ delv @8.8.8.8 +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA - ;; resolution failed: ncache nxrrset - ; negative response, fully validated - ; _25._tcp.cluster5.us.messagelabs.com. 299 IN \-TLSA ;-$NXRRSET - ; _25._tcp.cluster5.us.messagelabs.com. RRSIG NSEC ... - ; _25._tcp.cluster5.us.messagelabs.com. NSEC \000._25._tcp.cluster5.us.messagelabs.com. A PTR HINFO MX TXT RP SRV NAPTR SSHFP RRSIG NSEC SVCB HTTPS SPF IXFR AXFR CAA - ; messagelabs.com. SOA ns-1714.awsdns-22.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 - ; messagelabs.com. RRSIG SOA ... + $ delv @8.8.8.8 +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA + ;; resolution failed: ncache nxrrset + ; negative response, fully validated + ; _25._tcp.cluster5.us.messagelabs.com. 299 IN \-TLSA ;-$NXRRSET + ; _25._tcp.cluster5.us.messagelabs.com. RRSIG NSEC ... + ; _25._tcp.cluster5.us.messagelabs.com. NSEC \000._25._tcp.cluster5.us.messagelabs.com. A PTR HINFO MX TXT RP SRV NAPTR SSHFP RRSIG NSEC SVCB HTTPS SPF IXFR AXFR CAA + ; messagelabs.com. SOA ns-1714.awsdns-22.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 + ; messagelabs.com. RRSIG SOA ... I assume Postfix (with smtp_tls_security_level = dane i.e. "Opportunistic DANE") deals with the negative response by downgrading to "encrypt", whereas the SERVFAIL response makes it refuse to connect altogether. My workaround was to switch from the systemd-resolved stub resolver to the upstream servers. In /etc/systemd/resolved.conf set: - DNS=... your upstream servers if not already given through DHCP ... - DNSStubListener=no + DNS=... your upstream servers if not already given through DHCP ... + DNSStubListener=no Then restart the service and restart Postfix if it is chrooted (so the new /etc/resolv.conf gets copied into the chroot): - systemctl restart systemd-resolved - systemctl restart postfix + systemctl restart systemd-resolved + systemctl restart postfix I am not sure if this could be considered a Postfix bug as well (it could consider a SERVFAIL on a TLSA record the same as a negative), but surely it seems to me the systemd-resolved stub resolver should not return the SERVFAIL here. For more background on this bug report, please see https://serverfault.com/a/1158198/299950 -- 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/2062542 Title: systemd-resolved stub gives SERVFAIL for DNSSEC negative response Status in systemd package in Ubuntu: Incomplete Bug description: This issue surfaced when researching the issue that Postfix on my system (with DANE enabled) deferred mail deliveries with 100s of this warning in the log: Warning: DANE TLSA lookup problem: Host or domain name not found. Name service error for name=_25._tcp.cluster5.us.messagelabs.com type=TLSA: Host not found, try again The DNS resolver on my machine was pointing at the systemd-resolved stub: $ cat /etc/resolv.conf | grep nameserver nameserver 127.0.0.53 $ resolvectl status Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported resolv.conf mode: stub
[Touch-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
I just updated and rebooted but I'm also still seeing the same problem:
Failed to backup /etc/group: Operation not supported. It's reproducible
with "apt install tomcat10".
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2057927] Re: lxd vga console throws "Operation not permitted" error
Please can you confirm if still an issue on lxd 5.21/stable as this is the current supported version. Thanks -- 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/2057927 Title: lxd vga console throws "Operation not permitted" error Status in apparmor package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Confirmed Bug description: Since I upgraded to Noble the lxd vga console doesn't work anymore. I am using the lxd latest/stable snap (5.20-f3dd836). When trying to attach a vga console to an lxd vm I get: unshare: write failed /proc/self/uid_map: Operation not permitted It seems to be related to apparmor, I can see a matching DENIAL message in dmesg: [ 4735.233989] audit: type=1400 audit(1710419600.517:300): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=13157 comm="unshare" capability=21 capname="sys_admin" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
This might be user error, but I seem to still be running into issues
with docker and this.
I'm on the latest kernel and zfs versions:
zfs --version:
zfs-2.2.2-0ubuntu9
zfs-kmod-2.2.2-0ubuntu7
uname -r:
6.8.0-28-generic
[00:41:58 ERROR]: Encountered an unexpected exception
org.spongepowered.configurate.ConfigurateException: []: java.io.IOException:
Operation not supported
at
org.spongepowered.configurate.loader.AbstractConfigurationLoader.save(AbstractConfigurationLoader.java:205)
~[configurate-core-4.2.0-SNAPSHOT.jar:?]
at
io.papermc.paper.configuration.Configurations.trySaveFileNode(Configurations.java:111)
~[paper-1.20.4.jar:git-Paper-488]
at
io.papermc.paper.configuration.Configurations.initializeGlobalConfiguration(Configurations.java:136)
~[paper-1.20.4.jar:git-Paper-488]
at
io.papermc.paper.configuration.Configurations.initializeGlobalConfiguration(Configurations.java:106)
~[paper-1.20.4.jar:git-Paper-488]
at
io.papermc.paper.configuration.PaperConfigurations.initializeGlobalConfiguration(PaperConfigurations.java:198)
~[paper-1.20.4.jar:git-Paper-488]
at
net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:209)
~[paper-1.20.4.jar:git-Paper-488]
at
net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1131)
~[paper-1.20.4.jar:git-Paper-488]
at
net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:319)
~[paper-1.20.4.jar:git-Paper-488]
at java.lang.Thread.run(Thread.java:1583) ~[?:?]
Caused by: java.io.IOException: Operation not supported
at sun.nio.fs.LinuxNativeDispatcher.directCopy0(Native Method) ~[?:?]
at sun.nio.fs.LinuxFileSystem.directCopy(LinuxFileSystem.java:159)
~[?:?]
at sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:682) ~[?:?]
at sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060) ~[?:?]
at
sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300) ~[?:?]
at java.nio.file.Files.copy(Files.java:1304) ~[?:?]
at
org.spongepowered.configurate.loader.AtomicFiles.atomicBufferedWriter(AtomicFiles.java:85)
~[configurate-core-4.2.0-SNAPSHOT.jar:?]
at
org.spongepowered.configurate.loader.AtomicFiles.lambda$atomicWriterFactory$0(AtomicFiles.java:58)
~[configurate-core-4.2.0-SNAPSHOT.jar:?]
at
org.spongepowered.configurate.loader.AbstractConfigurationLoader.save(AbstractConfigurationLoader.java:188)
~[configurate-core-4.2.0-SNAPSHOT.jar:?]
... 8 more
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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
