[Touch-packages] [Bug 2049247] Re: Broken IPv4 support on IPv6-preferring networks (v255)
** Changed in: systemd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2049247
Title:
Broken IPv4 support on IPv6-preferring networks (v255)
Status in systemd:
New
Status in systemd package in Ubuntu:
New
Bug description:
I noticed a bug in systemd version 255 which is currently available in
noble-proposed (255.2-3ubuntu1).
I have already reported to upstream at
https://github.com/systemd/systemd/issues/30891 but there's no fix
available yet as of today.
I'm still reporting the bug here anyways because this bug can, under
some conditions, result in the loss of IPv4 network connectivity in a
completely standard Ubuntu 24.04 installation just by updating to
systemd 255. I'm hoping that that's okay even though it's a bug caused
by upstream not by Ubuntu; just because it could have a bad impact if
this version ends up in 24.04 as it is.
---
In systemd version 255, a feature has been added to "support" the
IPv6-only DHCP option 108 defined in RFC8925. I'm putting "support" in
quotation marks because one functionality that this RFC marks as a
requirement is not implemented in systemd yet.
To summarize: Option 108 can be sent by a DHCPv4 client to signal to
the DHCPv4 server: "Hey, if (and only if) your network has proper IPv6
support and a working NAT64 gateway, I don't really need my own IPv4
address, I can handle it using 464XLAT and NAT64". The point of that
option is to be able to run a Dual Stack network, where only clients
that really need IPv4 (older Linux, Windows, etc.) will receive an
IPv4 from DHCP, and clients that don't need IPv4 (Android, MacOS,
Linux with systemd >=255, etc.) won't receive one from DHCP and
instead set up a 464XLAT for outgoing IPv4 connectivity.
This new code in systemd is enabled by default (the option
"IPv6OnlyMode" defaults to "yes"). However, systemd does not actually
have code to set up a 464XLAT yet (which violates the RFC).
This means that systemd signals to the DHCPv4 server "Hey, I don't
need IPv4, I'll just use 464XLAT and NAT64" but then it doesn't
actually do that. Updating systemd on an Ubuntu 24.04 installation
(where systemd-networkd is used) will result in the loss of the DHCP-
assigned IPv4 address, breaking network connectivity for all IPv4-only
applications.
---
Information on how to reproduce this issue can be found in detail in
the github bug report linked above, but to summarize:
1. Have a Dual Stack network that announces a NAT64 through RAs or through
DNS (or, ideally, both)
2. Configure your DHCPv4 server to hand out option 108 ("v6-only-preferred")
3. Connect an Ubuntu machine with systemd < 255.
4. Notice that IPv4 connectivity is working fine.
5. Update to systemd = 255.
6. Notice that there's no IPv4 connectivity anymore and IPv4-only apps break.
---
The proper fix for this issue to make systemd conform to the RFC would
be to implement a 464XLAT. However that's not an easy task and most
certainly not something that would end up as a hotfix / patch release.
A good workaround for this bug would be, in my opinion, to change the
default value for the "IPv6OnlyMode" to "no" when compiling systemd.
That way, the RFC-violating code doesn't run by default, and if a user
does set up a 464XLAT on their machine in some other way (outside of
systemd) they can just change their config to include
"IPv6OnlyMode=yes" and it'll be working as intended.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 255.2-3ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Jan 13 07:05:42 2024
InstallationDate: Installed on 2024-01-12 (0 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release amd64
(20231011)
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device,
Driver=usbhid, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic
root=UUID=b5e6aabf-881a-4589-85ae-688f41df0be7 ro
SourcePackage: systemd
UpgradeStatus: Upgraded to noble on 2024-01-12 (0 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.moda
[Touch-packages] [Bug 2037595] [gpgme1.0/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.
** Tags added: removal-candidate
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
Fix Committed
Status in gpgme1.0 source package in Jammy:
Fix Committed
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```
[Where problems could occur]
`_gpgme_io_select` is pretty central to gpgme, so if something is
wrong the package will be pretty broken. On the other hand, that also
means any glaring problems are likely to be caught by the package's
test suite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+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 2049240] Re: ghostwriter no longer runs on ubuntu noble
** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: ghostwriter (Ubuntu) Status: New => Confirmed ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- 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/2049240 Title: ghostwriter no longer runs on ubuntu noble Status in apparmor package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Confirmed Bug description: Ubuntu noble (desktop is LXQt; so Lubuntu if technical) I've used ghostwriter on this box before, so expect it to run without issue... alas it no longer is guiverc@d7050-next:~$ ghostwriter Command "pandoc" is not available. Command "multimarkdown" is not available. Command "cmark" is not available. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed [1103820:1103820:0112/100524.977724:FATAL:credentials.cc(125)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped) I've also on another Ubuntu noble box `sudo apt install ghostwriter` & get a similar failure on attempt to run. Of note: I also tried the snap version of ghostwriter (hoping to use in the meantime) and it's also failing; I've not tried the snap before so this may not be different. I've not reboot in a week (probably equal on my other box too) guiverc@d7050-next:/de2900/lubuntu/testcases_2023/ubuntu-manual-tests/testcases/image$ uptime 10:04:55 up 7 days, 23:23, 1 user, load average: 4.90, 2.05, 1.69 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ghostwriter 23.08.4+ds-0ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: LXQt Date: Sat Jan 13 10:01:32 2024 InstallationDate: Installed on 2023-08-29 (137 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ghostwriter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2049240/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: ghostwriter (Ubuntu) Importance: Undecided Status: New ** Changed in: ghostwriter (Ubuntu) Status: New => Confirmed -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Confirmed Status in angelfish package in Ubuntu: Confirmed Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Confirmed Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Confirmed Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Confirmed Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in konqueror package in Ubuntu: Confirmed Status in kontact package in Ubuntu: Confirmed Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2049240] Re: ghostwriter no longer runs on ubuntu noble
*** This bug is a duplicate of bug 2046844 *** https://bugs.launchpad.net/bugs/2046844 I have now tested with the attached profile and confirmed that ghostwriter works after the policy update. ** Attachment added: "usr.bin.ghostwriter" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2049240/+attachment/5738992/+files/usr.bin.ghostwriter ** This bug has been marked a duplicate of bug 2046844 AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP -- 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/2049240 Title: ghostwriter no longer runs on ubuntu noble Status in apparmor package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Confirmed Bug description: Ubuntu noble (desktop is LXQt; so Lubuntu if technical) I've used ghostwriter on this box before, so expect it to run without issue... alas it no longer is guiverc@d7050-next:~$ ghostwriter Command "pandoc" is not available. Command "multimarkdown" is not available. Command "cmark" is not available. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed [1103820:1103820:0112/100524.977724:FATAL:credentials.cc(125)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped) I've also on another Ubuntu noble box `sudo apt install ghostwriter` & get a similar failure on attempt to run. Of note: I also tried the snap version of ghostwriter (hoping to use in the meantime) and it's also failing; I've not tried the snap before so this may not be different. I've not reboot in a week (probably equal on my other box too) guiverc@d7050-next:/de2900/lubuntu/testcases_2023/ubuntu-manual-tests/testcases/image$ uptime 10:04:55 up 7 days, 23:23, 1 user, load average: 4.90, 2.05, 1.69 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ghostwriter 23.08.4+ds-0ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: LXQt Date: Sat Jan 13 10:01:32 2024 InstallationDate: Installed on 2023-08-29 (137 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ghostwriter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2049240/+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 2045621] Re: Improve power consumption on Framework systems
Successfully tested here as reported by the previous user (see #16). Tested on jammy: 0. Checked before patch: - cat /sys/devices/pci:00/:00:08.3/:c3:00.3/usb5/5-1/manufacturer Framework - cat /sys/devices/pci\:00/\:00\:08.3/\:c3\:00.3/usb5/5-1/power/control on 1. Enabled jammy-proposed 2. Installed systemd-hwe-hwdb (version 249.11.5) 3. File /usr/lib/udev/hwdb.d/90-ubuntu-autosuspend.hwdb is created 4. Check power status (HDMI card): $ cat /sys/devices/pci:00/:00:08.3/:c3:00.3/usb5/5-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.3/:c3:00.3/usb5/5-1/power/control auto -- 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/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Won't Fix Status in systemd-hwe source package in Jammy: Fix Committed Status in systemd source package in Lunar: Won't Fix Status in systemd-hwe source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Status in systemd-hwe source package in Mantic: Fix Committed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2049262] [NEW] Cannot successfully mount the directory through nfs4 on Ubuntu 20.04
Public bug reported: we want to mount with nfs 4.1 on Ubuntu 20.04, but when we run the command: mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt it will only try version 4, the following is the log: root@ubuntutest:~# mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt mount.nfs: timeout set for Thu Dec 28 12:31:23 2023 mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported The only way to make it work is to specify ver=4.1: root@ubuntutest:~# mount -o vers=4.1 -vvv x.x.x.x:/sam_test /mnt mount.nfs: timeout set for Thu Dec 28 12:31:33 2023 mount.nfs: trying text-based options 'vers=4.1,addr=x.x.x.x,clientaddr=x.x.x.x' Now we use nfs-common version 1:1.3.4-2.5ubuntu3.5. I think it is a bug of nfs-common package. Normally, as a comparison, in Redhat, if we set vers=4, it will try the latest nfs4 version 4.2, if it failed , it will try the older version until it works. [root@zhf1smg002 ~]# mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt mount.nfs: timeout set for Thu Dec 28 04:37:38 2023 mount.nfs: trying text-based options 'rsize=32768,wsize=32768,vers=4.2,addr=x.x.x.x,clientaddr=x.x.x.x' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'rsize=32768,wsize=32768,vers=4,minorversion=1,addr=x.x.x.x,clientaddr=x.x.x.x' affects Ubuntu 20.04 nfs4 mount affects nfs-common ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Package changed: pulseaudio (Ubuntu) => nfs-utils (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/2049262 Title: Cannot successfully mount the directory through nfs4 on Ubuntu 20.04 Status in nfs-utils package in Ubuntu: New Bug description: we want to mount with nfs 4.1 on Ubuntu 20.04, but when we run the command: mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt it will only try version 4, the following is the log: root@ubuntutest:~# mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt mount.nfs: timeout set for Thu Dec 28 12:31:23 2023 mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported The only way to make it work is to specify ver=4.1: root@ubuntutest:~# mount -o vers=4.1 -vvv x.x.x.x:/sam_test /mnt mount.nfs: timeout set for Thu Dec 28 12:31:33 2023 mount.nfs: trying text-based options 'vers=4.1,addr=x.x.x.x,clientaddr=x.x.x.x' Now we use nfs-common version 1:1.3.4-2.5ubuntu3.5. I think it is a bug of nfs-common package. Normally, as a comparison, in Redhat, if we set vers=4, it will try the latest nfs4 version 4.2, if it failed , it will try the older version until it works. [root@zhf1smg002 ~]# mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt mount.nfs: timeout set for Thu Dec 28 04:37:38 2023 mount.nfs: trying text-based options 'rsize=32768,wsize=32768,vers=4.2,addr=x.x.x.x,clientaddr=x.x.x.x' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'rsize=32768,wsize=32768,vers=4,minorversion=1,addr=x.x.x.x,clientaddr=x.x.x.x' affects Ubuntu 20.04 nfs4 mount affects nfs-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2049262/+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 2047656] Re: [SRU] Players terminate after stopping and restarting
** Changed in: fluidsynth (Ubuntu Mantic) Status: Fix Committed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/2047656 Title: [SRU] Players terminate after stopping and restarting Status in fluidsynth package in Ubuntu: Fix Released Status in fluidsynth source package in Mantic: New Status in fluidsynth source package in Noble: Fix Released Bug description: [ Impact ] Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop of playback of a midi song, causing issues for a multitude of players including EasyABC. This will cause said player to be unable to playback again and perhaps even crash. See https://github.com/FluidSynth/fluidsynth/issues/1272, fix in https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055. This is the included patch with the upload of 2.3.3-2.1ubuntu-0.23.10.1 [ Test Case ] * To reproduce the bug: # download sample midi file from wikiepdia: wget https://upload.wikimedia.org/wikipedia/commons/5/55/MIDI_sample.mid # play it with fluidsynth fluidsynth MIDI_sample.mid # at this point, you will actually be at a prompt. Wait for the song to play for a few seconds, then issue a stop command at that prompt: player_stop # And this is where the bug happens. Issue a continuation: player_cont And this is where things break: > player_cont > fluidsynth: error: The maximum playback duration has been reached. Terminating player! * With the fixed package, the audio resumes playback. [ What could go wrong ] This is actually a fix for a regression that was found in version 2.3.3 of fluidsynth and fixed for 2.3.4, which can be found in noble. I think the only thing that can go wrong here is that this patch is not the actual fix and we need to find more solutions within. I have tested this in my PPA and it *seems* to fix it, but it would be nice if the original reporter could verify once this lands in proposed. [ Other information ] Included below is the original report, in which case the reporter deduces that the problem is the binary being spat-out is the 2.3.2 version from the 2.3.3 sources. This is not the case, as it appears to be confusion due to the -2.1 Debian revision number. I assure, this is definitely the 2.3.3, and the bug, per the github link in the Impact section, is pertinent to this version. --- The latest package of fluidsynth should include the sources from version 2.3.3 but the binary includes only version 2.3.2 This version has a bug (see https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to problems in EasyABC. Please include the latest version 2.3.3 from upstream in the ubuntu package. -- Description: Ubuntu 23.10 Release: 23.10 Codename: mantic $ apt-cache policy libfluidsynth3 libfluidsynth3: Installiert: 2.3.3-2.1 Installationskandidat: 2.3.3-2.1 Versionstabelle: *** 2.3.3-2.1 500 500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+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 2047656] Re: [SRU] Players terminate after stopping and restarting
Hi Michael, Per the instructions, don't change the status to "New", but keep as "Fix Committed". You simply needed to change the tags to "verification-done- mantic" and "verification-done", which I have done for you. Just for future reference. Thanks! ** Changed in: fluidsynth (Ubuntu Mantic) Status: New => Fix Committed ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/2047656 Title: [SRU] Players terminate after stopping and restarting Status in fluidsynth package in Ubuntu: Fix Released Status in fluidsynth source package in Mantic: Fix Committed Status in fluidsynth source package in Noble: Fix Released Bug description: [ Impact ] Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop of playback of a midi song, causing issues for a multitude of players including EasyABC. This will cause said player to be unable to playback again and perhaps even crash. See https://github.com/FluidSynth/fluidsynth/issues/1272, fix in https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055. This is the included patch with the upload of 2.3.3-2.1ubuntu-0.23.10.1 [ Test Case ] * To reproduce the bug: # download sample midi file from wikiepdia: wget https://upload.wikimedia.org/wikipedia/commons/5/55/MIDI_sample.mid # play it with fluidsynth fluidsynth MIDI_sample.mid # at this point, you will actually be at a prompt. Wait for the song to play for a few seconds, then issue a stop command at that prompt: player_stop # And this is where the bug happens. Issue a continuation: player_cont And this is where things break: > player_cont > fluidsynth: error: The maximum playback duration has been reached. Terminating player! * With the fixed package, the audio resumes playback. [ What could go wrong ] This is actually a fix for a regression that was found in version 2.3.3 of fluidsynth and fixed for 2.3.4, which can be found in noble. I think the only thing that can go wrong here is that this patch is not the actual fix and we need to find more solutions within. I have tested this in my PPA and it *seems* to fix it, but it would be nice if the original reporter could verify once this lands in proposed. [ Other information ] Included below is the original report, in which case the reporter deduces that the problem is the binary being spat-out is the 2.3.2 version from the 2.3.3 sources. This is not the case, as it appears to be confusion due to the -2.1 Debian revision number. I assure, this is definitely the 2.3.3, and the bug, per the github link in the Impact section, is pertinent to this version. --- The latest package of fluidsynth should include the sources from version 2.3.3 but the binary includes only version 2.3.2 This version has a bug (see https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to problems in EasyABC. Please include the latest version 2.3.3 from upstream in the ubuntu package. -- Description: Ubuntu 23.10 Release: 23.10 Codename: mantic $ apt-cache policy libfluidsynth3 libfluidsynth3: Installiert: 2.3.3-2.1 Installationskandidat: 2.3.3-2.1 Versionstabelle: *** 2.3.3-2.1 500 500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+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 1978400] Re: GNOME Network Displays does not work with error Authorization supplicant timed out
** Changed in: hostap Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1978400 Title: GNOME Network Displays does not work with error Authorization supplicant timed out Status in hostap: Fix Released Status in wpa package in Ubuntu: Triaged Bug description: I have a problem with connecting to a Miracast device via GNOME Network Displays package (https://gitlab.gnome.org/GNOME/gnome-network-displays) on Ubuntu. It sees the device normally (I see the device name in "Available Video Sinks" list), but when I'm trying to connect, after some time I've got the connection failed with the error: ``` p2p-dev-wlp0s20f3: Authorization supplicant timed out ``` Other systems (Android, Windows, MacOS) connects to it successfully. In the https://gitlab.gnome.org/GNOME/gnome-network-displays it's described that wpa_supplicant requires the patch: https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benja...@sipsolutions.net/ Maybe just adding this one-line patch could resolve this issue? Or it is already applied? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jun 12 09:56:19 2022 InstallationDate: Installed on 2022-04-14 (58 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: wpa UpgradeStatus: Upgraded to jammy on 2022-04-14 (58 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/hostap/+bug/1978400/+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 2049192] Re: Audio problem on zoom + kubuntu 23.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/2049192 Title: Audio problem on zoom + kubuntu 23.10 Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am using kubuntu 23.10, and have sound issues with zoom. I have a Jabra Speak 510 running thorugh USB. When I first connect to a meeting, I hear nothing (but apparently my mic does work, so others can hear me). If I open audio settings, hit "Test" and then switch the profile from Analog Stereo Output + Mono Input to Digital Stereo Output + Mono Input (or vice versa, it's the action of changing the profile that seems important), then the sound works. At points during a zoom call (seems to be related to other windows/apps opening), the sound dies and I have to switch profile again. I never had this issue with kubuntu 22.04 LTS. I have not noticed similar problems applications which only output audio, eg vlc or clementine. STEPS TO REPRODUCE 1. Join a zoom meeting OBSERVED RESULT No sound output until switching audio profile EXPECTED RESULT Sound should work without having to switch profile SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0.0 Qt Version: 5.15.10 Kernel 6.5.0-14 Zoom 5.16.10 (668). ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jan 12 09:40:10 2024 InstallationDate: Installed on 2023-11-10 (63 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= 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: 09/06/2021 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.18 dmi.board.name: 0T2HR0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.18:bd09/06/2021:br1.1:svnDellInc.:pnXPS8930:pvr1.1.18:rvnDellInc.:rn0T2HR0:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2049192/+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 1946475] Re: USB support in intram broken for raspberry 4 after udpate
[Expired for initramfs-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Expired -- 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/1946475 Title: USB support in intram broken for raspberry 4 after udpate Status in initramfs-tools package in Ubuntu: Expired Bug description: Hi, I have a Raspberry PI 4 running Ubuntu 18.04. Recently I apt-get upgrade'd it which resulted in new kernel and ramdisk. My initramdisk now does not recognize USB devices. I can see the modules are there (usb-storage uas), and I can load them, but no devices come up, in particular USB storage. I have looked at the recent commits to this package, and I wonder if the following commit may have had something to do, as it is recent and deals with device firmware and resuming devices.. https://git.launchpad.net/ubuntu/+source/initramfs- tools/commit/?id=3faf13b2b7217c05a20d649b10920f828b3c83c3 I really don't understand what is the process until USB devices are instantiated as /dev/disk/... so I am a bit lost in finding out exactly what is not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1946475/+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 1941649] Re: switch to zstd by default breaks booting focal LTS kernel
[Expired for initramfs-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Expired -- 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/1941649 Title: switch to zstd by default breaks booting focal LTS kernel Status in initramfs-tools package in Ubuntu: Expired Bug description: While trying to track down a behavior difference between focal and impish, I installed focal's kernel in an impish userspace and attempted to boot it. The boot failed, unable to find root. While GRUB reported that it had loaded the initramfs, no initramfs messages were emitted during boot. I tracked this down to initramfs-tools having switched to use zstd compression by default. zstd decompression does not appear to be supported by the LTS 5.4 kernel - it appears to have been added upstream in v5.9. I imagine this is likely to cause problems with partial-upgrade scenarios. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1941649/+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 1904048] Re: ı have amd64 cpu but . updater want installed intel microcode firmware
[Expired for initramfs-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Expired -- 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/1904048 Title: ı have amd64 cpu but . updater want installed intel microcode firmware Status in initramfs-tools package in Ubuntu: Expired Bug description: software updater wants install some and ı want see whats new intel-microcode changelog: installed: 3.20200609.0ubuntu0.18.04.1 new: 3.20201110.0ubuntu0.18.04.2 when ı see 5 minutes a go , ı said Aao!!? when ,? and yes, my laptop is very slow , why , maybe this ? Ubuntu 18.04.5 LTS AMD® C-60 apu with radeon(tm) hd graphics × 2 3,5 GiB Ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1904048/+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
