[Touch-packages] [Bug 2058715] [NEW] ubuntu.sources can become broken via GUI
Public bug reported: With the latest proposed versions of software-properties-gtk, software- properties-common, and python3-software-properties (0.99.44), it is possible to break the default ubuntu.sources list. How to replicate 1. Open software-properties-gtk 2. Uncheck all of the repository suites (main, universe, multiverse, etc.) 3. Cat the /etc/apt/sources.list.d/ubuntu.sources file. It should be mostly empty. 4. Re-check all of the repository suites again. 5. Cat the /etc/apt/sources.list.d/ubuntu.sources file again. It will still be mostly empty with no repository configuration present. The ubuntu.sources file remains in a broken state even though software-properties-gtk shows the suites as checked. We can workaround this issue by using the 'Revert' button in software- properties-gtk. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-gtk 0.99.44 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 09:05:37 2024 InstallationDate: Installed on 2024-03-13 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240313) PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble package-from-proposed wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2058715 Title: ubuntu.sources can become broken via GUI Status in software-properties package in Ubuntu: New Bug description: With the latest proposed versions of software-properties-gtk, software-properties-common, and python3-software-properties (0.99.44), it is possible to break the default ubuntu.sources list. How to replicate 1. Open software-properties-gtk 2. Uncheck all of the repository suites (main, universe, multiverse, etc.) 3. Cat the /etc/apt/sources.list.d/ubuntu.sources file. It should be mostly empty. 4. Re-check all of the repository suites again. 5. Cat the /etc/apt/sources.list.d/ubuntu.sources file again. It will still be mostly empty with no repository configuration present. The ubuntu.sources file remains in a broken state even though software-properties-gtk shows the suites as checked. We can workaround this issue by using the 'Revert' button in software- properties-gtk. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-gtk 0.99.44 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 09:05:37 2024 InstallationDate: Installed on 2024-03-13 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240313) PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start
Can confirm that the version in noble-proposed fixes this issue.
Although I noticed another bug, possibly related to deb822 sources in
general rather than this specific change: #2058715
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
https://salsa.debian.org/ubuntu-dev- team/plymouth/-/commit/bd9d0119fdbeb3b30c8d3caafdb8a31b23c188c4 does not reflect the removal of the complete drm section. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2058720] [NEW] 'Other Software' section displays verbose ubuntu.sources comment
Public bug reported: With software-properties-gtk (0.99.44), the 'Other Software' section displays the full multi-line comment from the new ubuntu.sources file. This creates an unpleasant looking entry in the list. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2024-03-22 10-38-59.png" https://bugs.launchpad.net/bugs/2058720/+attachment/5758293/+files/Screenshot%20from%202024-03-22%2010-38-59.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2058720 Title: 'Other Software' section displays verbose ubuntu.sources comment Status in software-properties package in Ubuntu: New Bug description: With software-properties-gtk (0.99.44), the 'Other Software' section displays the full multi-line comment from the new ubuntu.sources file. This creates an unpleasant looking entry in the list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058720/+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 2058733] [NEW] polkitd does not create default config files on noble
Public bug reported: With a fresh install of the daily Ubuntu 24.04, polkitd does not create the default config files under /etc/polkit-1/localauthority.conf.d/ This folder should contain some default config files which specify which users can perform GUI admin authorization. In fact, even if I create a config file under that directory, the settings are not respected at all ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 11:17:16 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/usr/local/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2058733 Title: polkitd does not create default config files on noble Status in policykit-1 package in Ubuntu: New Bug description: With a fresh install of the daily Ubuntu 24.04, polkitd does not create the default config files under /etc/polkit-1/localauthority.conf.d/ This folder should contain some default config files which specify which users can perform GUI admin authorization. In fact, even if I create a config file under that directory, the settings are not respected at all ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 11:17:16 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/usr/local/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2058733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start
Also for me the version in noble-proposed fixes this issue.
I'm unable to find your bug #2058715
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058715] Re: ubuntu.sources can become broken via GUI
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2058715 Title: ubuntu.sources can become broken via GUI Status in software-properties package in Ubuntu: Confirmed Bug description: With the latest proposed versions of software-properties-gtk, software-properties-common, and python3-software-properties (0.99.44), it is possible to break the default ubuntu.sources list. How to replicate 1. Open software-properties-gtk 2. Uncheck all of the repository suites (main, universe, multiverse, etc.) 3. Cat the /etc/apt/sources.list.d/ubuntu.sources file. It should be mostly empty. 4. Re-check all of the repository suites again. 5. Cat the /etc/apt/sources.list.d/ubuntu.sources file again. It will still be mostly empty with no repository configuration present. The ubuntu.sources file remains in a broken state even though software-properties-gtk shows the suites as checked. We can workaround this issue by using the 'Revert' button in software- properties-gtk. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-gtk 0.99.44 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 09:05:37 2024 InstallationDate: Installed on 2024-03-13 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240313) PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start
I confirm this.
BUT:
with this ubuntu.sources:
Types: deb
URIs: http://archive.ubuntu.com/ubuntu
Suites: noble noble-updates noble-backports
Components: main universe restricted multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
Types: deb
URIs: http://security.ubuntu.com/ubuntu
Suites: noble-security
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
I get a line in 'Other softwares' tab in software-properties-gtk,
containing noble noble-updates noble-backports suites. Is that ok?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
Autopkgtests are now clear in update_excuses and pending-sru. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: Fix Committed Status in coreutils package in Fedora: Fix Released Bug description: [Impact] Issuing a 'ls -l' or a 'stat' on an autofs share when you have set --ghost in the auto.master file, or browse_mode=yes in autofs.conf will lead to the shares being mounted, when they didn't previously. Disks / shares may not be present and the mounts may fail, leading to errors in your output. This is a behaviour change in autofs 8.32, which occurred in the transition to using statx() instead of stat()/lstat() in previous releases. There doesn't seem to be any workarounds, apart from not running a 'ls -l' in your autofs share directory. [Testcase] Start two Jammy VMs. One will be a NFS server, the other, the client. NFS server: Server VM: $ sudo hostnamectl set-hostname jammy-nfs-server $ sudo apt update && sudo apt upgrade -y $ sudo apt install nfs-kernel-server $ sudo mkdir /export $ sudo mkdir /export/users $ sudo vi /etc/exports # add the following lines: /export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync) /export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync) $ sudo systemctl restart nfs-server.service AutoFS Client: $ sudo apt update $ sudo apt install autofs $ sudo vim /etc/autofs.conf browse_mode = yes $ sudo mkdir /mnt2 $ sudo vim /etc/auto.master /mnt2 /etc/auto.indirect $ sudo vim /etc/auto.indirect export 192.168.122.18:/export export-missing 192.168.122.18:/export-missing $ sudo reboot $ cd /mnt2 $ ls -l ls: cannot access 'export-missing': No such file or directory total 4 drwxr-xr-x 3 root root 4096 Feb 12 21:48 export d? ? ?? ?? export-missing $ mount -l | grep /mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=634,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=21561) 192.168.122.18:/export on /mnt2/export type nfs (rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.122.18,mountvers=3,mountport=35786,mountproto=udp,local_lock=none,addr=192.168.122.18) We see the mount for export occurred, and export-missing was attempted, but it was either bogus or the disk was not present, leading to a "No such file or directory" error. There are test packages available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf378489-test If you install them, this is what should occur: $ ls -l total 0 drwxr-xr-x 2 root root 0 Feb 12 22:01 export drwxr-xr-x 2 root root 0 Feb 12 22:01 export-missing $ mount -l | grep /mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=636,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18346) No mounts happen, and no errors either. [Where problems could occur] We are changing the behaviour of core utilities, ls and stat, such that they no longer attempt to mount autofs shares when --ghost option is present or browse_mode is enabled. This is the intended behaviour in the first place, and has been this way for at least a decade prior, and was changed to return to this behaviour shortly after the release of coreutils that introduced statx() that caused automounts to occur. It is unlikely any system administrators are relying on the behaviour found in jammy in any scripts or day to day operations that would be adversely affected by the change. The worst case scenario is that a user doing an 'ls -l' on an unmounted disk finds the mount doesn't automatically occur, and they have to attach the disk and issue the mount themselves. If a regression were to occur, it would be limited to the ls and stat commands, specifically when listing directories linked to autofs mountpoints. [Other info] The automount behaviour change was introduced upstream in version 8.32, with the introduction of the statx() call. This means only Jammy is affected. It was quickly reverted back to how it was originally in version 9.1, which is already available in Mantic and onward. The commits that solve the issue are: commit 85c975df2c25bd799370b04bb294e568e001102f From: Rohan Sable Date: Mon, 7 Mar 2022 14:14:13 + Subject: ls: avoid triggering automounts Link: https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2 commit 92cb8427c537f37edd43c5cef1909585201372ab From: Pádraig Brady Date: Mon, 7 Mar 2022 23:29:20 + Subject: stat: only automount wit
[Touch-packages] [Bug 2058743] [NEW] systemd local DNS tests failing with timeout
Public bug reported: Investigations done in 22.04/Jammy but may be affecting other series, too. The dnsmasq package recently was updated from 2.86-1.1ubuntu0.5 to 2.90-0ubuntu0.22.04.1. This seems to have brought back the same issue reported in bug #1957086. Sounds like both have interaction issues. To reproduce: $ pull-lp-source systemd jammy # Install test deps $ sudo apt install systemd udev libpam-systemd libnss-systemd acl locales evemu-tools python3 pkg-config cryptsetup-bin systemd-sysv policykit-1 dnsmasq-base $ cd systemd-249.11/test/ $ sudo ./networkd-test.py == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 252.167s ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2058743 Title: systemd local DNS tests failing with timeout Status in dnsmasq package in Ubuntu: New Bug description: Investigations done in 22.04/Jammy but may be affecting other series, too. The dnsmasq package recently was updated from 2.86-1.1ubuntu0.5 to 2.90-0ubuntu0.22.04.1. This seems to have brought back the same issue reported in bug #1957086. Sounds like both have interaction issues. To reproduce: $ pull-lp-source systemd jammy # Install test deps $ sudo apt install systemd udev libpam-systemd libnss-systemd acl locales evemu-tools python3 pkg-config cryptsetup-bin systemd-sysv policykit-1 dnsmasq-base $ cd systemd-249.11/test/ $ sudo ./networkd-test.py == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 252.167s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+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 2058743] Re: systemd local DNS tests failing with timeout
The same issue was present with the old dnsmasq package...for example: https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/s/systemd/20240224_133847_88f29@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2058743 Title: systemd local DNS tests failing with timeout Status in dnsmasq package in Ubuntu: New Bug description: Investigations done in 22.04/Jammy but may be affecting other series, too. The dnsmasq package recently was updated from 2.86-1.1ubuntu0.5 to 2.90-0ubuntu0.22.04.1. This seems to have brought back the same issue reported in bug #1957086. Sounds like both have interaction issues. To reproduce: $ pull-lp-source systemd jammy # Install test deps $ sudo apt install systemd udev libpam-systemd libnss-systemd acl locales evemu-tools python3 pkg-config cryptsetup-bin systemd-sysv policykit-1 dnsmasq-base $ cd systemd-249.11/test/ $ sudo ./networkd-test.py == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 252.167s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+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 2058743] Re: systemd local DNS tests failing with timeout
Sounds like some interaction issue between the system, systemd, and dnsmasq somehow. As this fails on and off since a very long time. When I test with the older dnsmasq and getting a success the time spent on the test seems overly long. Like there is something not quite right even then. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2058743 Title: systemd local DNS tests failing with timeout Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Investigations done in 22.04/Jammy but may be affecting other series, too. The dnsmasq package recently was updated from 2.86-1.1ubuntu0.5 to 2.90-0ubuntu0.22.04.1. This seems to have brought back the same issue reported in bug #1957086. Sounds like both have interaction issues. To reproduce: $ pull-lp-source systemd jammy # Install test deps $ sudo apt install systemd udev libpam-systemd libnss-systemd acl locales evemu-tools python3 pkg-config cryptsetup-bin systemd-sysv policykit-1 dnsmasq-base $ cd systemd-249.11/test/ $ sudo ./networkd-test.py == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 252.167s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+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 2058743] Re: systemd local DNS tests failing with timeout
It appears most of the systemd autopkgtest failures are because of this flaky test: https://autopkgtest.ubuntu.com/packages/systemd/jammy/amd64 The effort required to manually retrigger systemd autopkgtests because of that flaky test is substantial. We should disable that particular test unless someone manages to fix it properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2058743 Title: systemd local DNS tests failing with timeout Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Investigations done in 22.04/Jammy but may be affecting other series, too. The dnsmasq package recently was updated from 2.86-1.1ubuntu0.5 to 2.90-0ubuntu0.22.04.1. This seems to have brought back the same issue reported in bug #1957086. Sounds like both have interaction issues. To reproduce: $ pull-lp-source systemd jammy # Install test deps $ sudo apt install systemd udev libpam-systemd libnss-systemd acl locales evemu-tools python3 pkg-config cryptsetup-bin systemd-sysv policykit-1 dnsmasq-base $ cd systemd-249.11/test/ $ sudo ./networkd-test.py == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 252.167s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+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 1286021] Re: 2.1 surround support (userspace)
I have a problem with 2.1 sound on Realtek High Definition Audio (2.1): 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1286021 Title: 2.1 surround support (userspace) Status in alsa-lib package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Trusty: Confirmed Status in pulseaudio source package in Trusty: Confirmed Bug description: 2.1 surround should work as seamlessly as other surround options, such as 4.0, 5.1 and 7.1 work today. Alsa-lib and pulseaudio patches for 14.04 can be tested here: https://launchpad.net/~diwic/+archive/surround21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1286021/+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 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.
Thanks Tim! With more people having a seemingly similar issue I re-
opened it as New and subscribed ubuntu-server to take a look at this
again.
** Changed in: dnsmasq (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2055776
Title:
After updating ubuntu, the network to which the subnet address is
assigned does not become active in KVM.
Status in dnsmasq package in Ubuntu:
New
Bug description:
phenomenon:
After updating ubuntu, the network to which the subnet address is assigned
does not become active in KVM.
Cause:
This is because the following dnsmasq update operation performed by apt's
automatic update causes an error. It worked properly with dnsmasq 2.80, but
does not work properly with 2.90.
$ cat /var/log/apt/history.log
(snip)
Start-Date: 2024-02-27 06:17:31
Commandline: /usr/bin/unattended-upgrade
Upgrade: dnsmasq-base:amd64 (2.80-1.1ubuntu1.7, 2.90-0ubuntu0.20.04.1)
End-Date: 2024-02-27 06:17:44
(snip)
$
Cause details:
As a premise, bind-dynamic is set in the dnsmasq config file for KVM. Below
is an example.
$ cat default.conf
##WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
##OVERWRITTEN AND LOST. Changes to this configuration should be made using:
##virsh net-edit default
## or other application using the libvirt API.
##
## dnsmasq conf file created by libvirt
strict-order
user=libvirt-dnsmasq
pid-file=/run/libvirt/network/default.pid
except-interface=lo
bind-dynamic
interface=virbr0
dhcp-range=192.168.122.2,192.168.122.254,255.255.255.0
dhcp-no-override
dhcp-authoritative
dhcp-lease-max=253
dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
$
When starting the network with KVM (virsh net-start), dnsmasq started from
KVM executes the make_sock function twice as shown below.
$ cat network.c
(snip)
1087 static struct listener *create_listeners(union mysockaddr *addr, int
do_
1087 tftp, int dienow)
1088 {
1089 struct listener *l = NULL;
1090 int fd = -1, tcpfd = -1, tftpfd = -1;
1091
1092 (void)do_tftp;
1093
1094 if (daemon->port != 0)
1095 {
1096 fd = make_sock(addr, SOCK_DGRAM, dienow);
1097 tcpfd = make_sock(addr, SOCK_STREAM, dienow);
1098 }
(snip)
The following code causes an issue with the update made in dnsmasq
2.90.
$ cat network.c
(snip)
895 static int make_sock(union mysockaddr *addr, int type, int dienow)
896 {
(snip)
934 if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
935 {
936 if (dienow)
937 die(s, daemon->addrbuff, EC_BADNET);
938 else
939 my_syslog(LOG_WARNING, s, daemon->addrbuff,
strerror(errno))939 ;
940 }
(snip)
function "make_sock" in network.c:1096 binds the socket to 192.168.122.1/24,
and then make_sock in network.c:1097 tries to bind to the same address.
However, in network.c:934, when errno==98 occurs, network.c:937 is executed, so
dnsmasq does not cause a startup error. As a result, virsh net-start fails.
As a temporary workaround, it will work if you try not to die.
$ diff -u network_c_back network.c
--- network_c_back 2024-02-29 15:36:05.156467935 +
+++ network.c 2024-02-29 15:36:38.733324350 +
@@ -934,7 +934,8 @@
if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
{
if (dienow)
- die(s, daemon->addrbuff, EC_BADNET);
+ my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
+ //die(s, daemon->addrbuff, EC_BADNET);
else
my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
}
$
If bind-dynamic is set, it should be modified so that it works even if
errno==98.
For reference, in the case of dnsmasq 2.80, the code is as follows, so
no error occurs.
network.c
699 static int make_sock(union mysockaddr *addr, int type, int dienow)
700 {
701 int family = addr->sa.sa_family;
702 int fd, rc, opt = 1;
(snip)
715 err:
716 errsave = errno;
717 port = prettyprint_addr(addr, daemon->addrbuff);
718 if (!option_bool(OPT_NOWILD) && !option_bool(OPT_CLEVERBIND))
719 sprintf(daemon->addrbuff, "port %d", port);
720 s = _("failed to create listening socket for %s: %s");
721
722 if (fd != -1)
723 close (fd);
724
725 errno = errsave;
726
727 if (dienow)
728 {
729 /* failure to bind addresses given by --listen-address at
this
[Touch-packages] [Bug 2056802] Re: crypttab does not honor `x-initrd.attach` option
ack, thanks I will mark as invalid. systemd brings its own crypttab implementation. We try to cover the differences between the systemd and our implementation in this manpage, https://manpages.ubuntu.com/manpages/noble/en/man5/crypttab.5.html#on%20different%20crypttab%20formats ** Changed in: systemd (Ubuntu Focal) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu Jammy) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu Mantic) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu Noble) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu Noble) Assignee: Heather Lemon (hypothetical-lemon) => (unassigned) -- 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/2056802 Title: crypttab does not honor `x-initrd.attach` option Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Focal: Invalid Status in systemd source package in Jammy: Invalid Status in systemd source package in Mantic: Invalid Status in systemd source package in Noble: Invalid Bug description: From systemd version 245+ an option was added x-initrd.attach - Setup this encrypted block device in the initrd, similarly to systemd.mount(5) units marked with x-initrd.mount. Although it's not necessary to mark the mount entry for the root file system with x-initrd.mount, x-initrd.attach is still recommended with the encrypted block device containing the root file system as otherwise systemd will attempt to detach the device during the regular system shutdown while it's still in use. With this option the device will still be detached but later after the root file system is unmounted. All other encrypted block devices that contain file systems mounted in the initrd should use this option. Added in version 245. [0] - release: noble systemd version: 253.5-1ubuntu6 Install noble to a vm with virt-manager and encrypt the lvm during subiquity install. After successful install, Modify /etc/crypttab to include the parameter in the 4th column example: sda6_crypt UUID=099aae4a-b11b-49a6-a6c4-62939eddf7a0 none luks,x-initrd.attach update-initramfs -u -k all During boot or shutdown the logs show cryptsetup: WARNING: dm_crypt-0: ignoring unknown option x-initrd.attach There are two separate problems 1. crypttab doesn't recognize x-initrd.attach option in /etc/crypttab file. cryptsetup: WARNING: dm_crypt-0: ignoring unknown option x-initrd.attach 2. this error happens on shutdown/restart [systemd-cryptsetup]: Device dm-crypt-0 is still in use. [systemd-cryptsetup]: Failed to deactivate: Device or resource busy. The vm does eventually shutdown after throwing the above warnings. [0] https://www.freedesktop.org/software/systemd/man/latest/crypttab.html#x-initrd.attach These patches look like they could fix the issue, The last one might not be needed. git format-patch -1 8ce02b87cece09797c1030c778db4180e1e2ce2e https://github.com/systemd/systemd/commit/8ce02b87cece09797c1030c778db4180e1e2ce2e git format-patch -1 1dc85eff1d0dff18aaeaae530c91bf53f34b726e https://github.com/systemd/systemd/commit/1dc85eff1d0dff18aaeaae530c91bf53f34b726e git format-patch -1 bf1484c70a24cf04c145a9509c8124ffd7fb0879 https://github.com/systemd/systemd/commit/bf1484c70a24cf04c145a9509c8124ffd7fb0879 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056802/+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 2058767] [NEW] proposed-migration for auto-multiple-choice 1.6.0-3build3
You have been subscribed to a public bug: auto-multiple-choice 1.6.0-3build3 is stuck in -proposed due to regressing armhf autopkgtest. ** Affects: mesa (Ubuntu) Importance: Undecided Assignee: Steve Langasek (vorlon) Status: Fix Released ** Tags: block-proposed update-excuse -- proposed-migration for auto-multiple-choice 1.6.0-3build3 https://bugs.launchpad.net/bugs/2058767 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 2058767] Re: proposed-migration for auto-multiple-choice 1.6.0-3build3
mesa bootstrap had not been unwound all the way. Fixed mesa is building now. ** Package changed: auto-multiple-choice (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2058767 Title: proposed-migration for auto-multiple-choice 1.6.0-3build3 Status in mesa package in Ubuntu: Fix Released Bug description: auto-multiple-choice 1.6.0-3build3 is stuck in -proposed due to regressing armhf autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2058767/+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 2058769] [NEW] proposed-migration for click 0.5.2-2
Public bug reported: click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf, and possibly on all archs. armhf binary will be removed from the release pocket. ** Affects: click (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Description changed: - click 0.5.2-2 is stuck in -proposed. + click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf, + and possibly on all archs. + + armhf binary will be removed from the release pocket. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/2058769 Title: proposed-migration for click 0.5.2-2 Status in click package in Ubuntu: New Bug description: click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf, and possibly on all archs. armhf binary will be removed from the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/2058769/+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 2058775] [NEW] coreutils: printf formatting bug for nb_NO and nn_NO locales
Public bug reported: I just discovered a printf bug for at least the nb_NO and nn_NO locales when printing numbers with thousands separator. To reproduce: #!/bin/bash for l in de_DE en_US nb_NO ; do echo "LC_NUMERIC=$l.UTF-8" for n in 1 100 1000 1 10 100 1000 ; do LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n done done The expected output of "%'10d" is a right-formatted number string with 10 characters. The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8 and LC_NUMERIC=en_US.UTF-8: LC_NUMERIC=de_DE.UTF-8 < 1> < 100> < 1.000> <10.000> < 100.000> < 1.000.000> <10.000.000> LC_NUMERIC=en_US.UTF-8 < 1> < 100> < 1,000> <10,000> < 100,000> < 1,000,000> <10,000,000> However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the formatting is wrong: LC_NUMERIC=nb_NO.UTF-8 < 1> < 100> < 1 000> < 10 000> < 100 000> <1 000 000> <10 000 000> LC_NUMERIC=nn_NO.UTF-8 < 1> < 100> < 1 000> < 10 000> < 100 000> <1 000 000> <10 000 000> I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04) as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: coreutils 8.32-4.1ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Mar 22 21:33:13 2024 InstallationDate: Installed on 2022-11-29 (479 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: I just discovered a printf bug for at least the nb_NO and nn_NO locales when printing numbers with thousands separator. To reproduce: #!/bin/bash for l in de_DE en_US nb_NO ; do -echo "LC_NUMERIC=$l.UTF-8" -for n in 1 100 1000 1 10 100 1000 ; do - LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n -done + echo "LC_NUMERIC=$l.UTF-8" + for n in 1 100 1000 1 10 100 1000 ; do + LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n + done done The expected output of "%'10d" is a right-formatted number string with 10 characters. The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8 and LC_NUMERIC=en_US.UTF-8: LC_NUMERIC=de_DE.UTF-8 < 1> < 100> < 1.000> <10.000> < 100.000> < 1.000.000> <10.000.000> LC_NUMERIC=en_US.UTF-8 < 1> < 100> < 1,000> <10,000> < 100,000> < 1,000,000> <10,000,000> However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the formatting is wrong: LC_NUMERIC=nb_NO.UTF-8 < 1> < 100> < 1 000> < 10 000> < 100 000> <1 000 000> <10 000 000> LC_NUMERIC=nn_NO.UTF-8 < 1> < 100> < 1 000> < 10 000> < 100 000> <1 000 000> <10 000 000> I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04) as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: coreutils 8.32-4.1ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Mar 22 21:33:13 2024 InstallationDate: Installed on 2022-11-29 (479 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2058775 Title: coreutils: printf formatting bug for nb_NO and nn_NO locales Status in coreutils package in Ubuntu: New Bug description: I just discovered a printf bug for at least the nb_NO and nn_NO locales when printing numbers with thousands separator. To reproduce: #!/bin/bash for l in de_DE en_US nb_NO ; do echo "LC_NUMERIC=$l.UTF-8" for n in 1 100 1000 1 10 100 1000 ; do LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n done done The expected output of "%'10d" is a right-formatted number string with 10 characters. The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8 and LC_NUMERIC=en_US.UTF-8: LC_NUMERIC=de_DE.UTF-8 < 1> < 100> < 1.000> <10.000> < 100.000> < 1.000.000> <10.000.000> LC_NUMERIC=en_US.UTF-8 < 1> < 100> < 1,000>
[Touch-packages] [Bug 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales
Launchpad suppresses the spaces, it seems. I attached a screenshot of the terminal output to display the formatting issue. ** Attachment added: "Screenshot of the test script output" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2058775/+attachment/5758462/+files/Screenshot_20240322_213947.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2058775 Title: coreutils: printf formatting bug for nb_NO and nn_NO locales Status in coreutils package in Ubuntu: New Bug description: I just discovered a printf bug for at least the nb_NO and nn_NO locales when printing numbers with thousands separator. To reproduce: #!/bin/bash for l in de_DE en_US nb_NO ; do echo "LC_NUMERIC=$l.UTF-8" for n in 1 100 1000 1 10 100 1000 ; do LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n done done The expected output of "%'10d" is a right-formatted number string with 10 characters. The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8 and LC_NUMERIC=en_US.UTF-8: LC_NUMERIC=de_DE.UTF-8 < 1> < 100> < 1.000> <10.000> < 100.000> < 1.000.000> <10.000.000> LC_NUMERIC=en_US.UTF-8 < 1> < 100> < 1,000> <10,000> < 100,000> < 1,000,000> <10,000,000> However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the formatting is wrong: LC_NUMERIC=nb_NO.UTF-8 < 1> < 100> < 1 000> < 10 000> < 100 000> <1 000 000> <10 000 000> LC_NUMERIC=nn_NO.UTF-8 < 1> < 100> < 1 000> < 10 000> < 100 000> <1 000 000> <10 000 000> I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04) as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: coreutils 8.32-4.1ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Mar 22 21:33:13 2024 InstallationDate: Installed on 2022-11-29 (479 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2058775/+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 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales
In a hexdump, printf seems to add a 3 characters for the thousands separator: #!/bin/sh for l in de_DE en_US nb_NO nn_NO ; do echo "LC_NUMERIC=$l.UTF-8" for n in 1 100 1000 1 10 100 1000 ; do LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'8d>" $n | hexdump -C done done Output: LC_NUMERIC=nb_NO.UTF-8 3c 20 20 20 20 20 20 20 31 3e|< 1>| 000a 3c 20 20 20 20 20 31 30 30 3e|< 100>| 000a 3c 20 31 e2 80 af 30 30 30 3e|< 1...000>| 000a 3c 31 30 e2 80 af 30 30 30 3e|<10...000>| 000a 3c 31 30 30 e2 80 af 30 30 30 3e |<100...000>| 000b 3c 31 e2 80 af 30 30 30 e2 80 af 30 30 30 3e |<1...000...000>| 000f 3c 31 30 e2 80 af 30 30 30 e2 80 af 30 30 30 3e |<10...000...000>| 0010 LC_NUMERIC=nn_NO.UTF-8 3c 20 20 20 20 20 20 20 31 3e|< 1>| 000a 3c 20 20 20 20 20 31 30 30 3e|< 100>| 000a 3c 20 31 e2 80 af 30 30 30 3e|< 1...000>| 000a 3c 31 30 e2 80 af 30 30 30 3e|<10...000>| 000a 3c 31 30 30 e2 80 af 30 30 30 3e |<100...000>| 000b 3c 31 e2 80 af 30 30 30 e2 80 af 30 30 30 3e |<1...000...000>| 000f 3c 31 30 e2 80 af 30 30 30 e2 80 af 30 30 30 3e |<10...000...000>| 0010 However, both in Konsole as well as in XTerm, the issue occurs. So, the bytes "0xe2 0x80 0xaf" inserted by printf for the thousands separator seem to be incorrect? "0xe2 0x80 0xaf" is UTF-8 NARROW NO-BREAK SPACE -> https://www.fileformat.info/info/ .unicode/char/202f/index.htm . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2058775 Title: coreutils: printf formatting bug for nb_NO and nn_NO locales Status in coreutils package in Ubuntu: New Bug description: I just discovered a printf bug for at least the nb_NO and nn_NO locales when printing numbers with thousands separator. To reproduce: #!/bin/bash for l in de_DE en_US nb_NO ; do echo "LC_NUMERIC=$l.UTF-8" for n in 1 100 1000 1 10 100 1000 ; do LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n done done The expected output of "%'10d" is a right-formatted number string with 10 characters. The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8 and LC_NUMERIC=en_US.UTF-8: LC_NUMERIC=de_DE.UTF-8 < 1> < 100> < 1.000> <10.000> < 100.000> < 1.000.000> <10.000.000> LC_NUMERIC=en_US.UTF-8 < 1> < 100> < 1,000> <10,000> < 100,000> < 1,000,000> <10,000,000> However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the formatting is wrong: LC_NUMERIC=nb_NO.UTF-8 < 1> < 100> < 1 000> < 10 000> < 100 000> <1 000 000> <10 000 000> LC_NUMERIC=nn_NO.UTF-8 < 1> < 100> < 1 000> < 10 000> < 100 000> <1 000 000> <10 000 000> I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04) as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: coreutils 8.32-4.1ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Mar 22 21:33:13 2024 InstallationDate: Installed on 2022-11-29 (479 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2058775/+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 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales
Loading the test script output as text file in LibreOffice also shows the same issue (screenshot attached). So, it is not a bug of Konsole or XTerm. Probably, the 3-byte UTF-8 thousands separator character of the locale is not useful. May be it should be a simple space, or a normal UTF-8 non-breakable space (0xc2 0xa0, HTML " ")? ** Attachment added: "Screenshot of the test script output loaded in LibreOffice" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2058775/+attachment/5758464/+files/Screenshot_20240322_222052.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2058775 Title: coreutils: printf formatting bug for nb_NO and nn_NO locales Status in coreutils package in Ubuntu: New Bug description: I just discovered a printf bug for at least the nb_NO and nn_NO locales when printing numbers with thousands separator. To reproduce: #!/bin/bash for l in de_DE en_US nb_NO ; do echo "LC_NUMERIC=$l.UTF-8" for n in 1 100 1000 1 10 100 1000 ; do LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n done done The expected output of "%'10d" is a right-formatted number string with 10 characters. The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8 and LC_NUMERIC=en_US.UTF-8: LC_NUMERIC=de_DE.UTF-8 < 1> < 100> < 1.000> <10.000> < 100.000> < 1.000.000> <10.000.000> LC_NUMERIC=en_US.UTF-8 < 1> < 100> < 1,000> <10,000> < 100,000> < 1,000,000> <10,000,000> However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the formatting is wrong: LC_NUMERIC=nb_NO.UTF-8 < 1> < 100> < 1 000> < 10 000> < 100 000> <1 000 000> <10 000 000> LC_NUMERIC=nn_NO.UTF-8 < 1> < 100> < 1 000> < 10 000> < 100 000> <1 000 000> <10 000 000> I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04) as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: coreutils 8.32-4.1ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Mar 22 21:33:13 2024 InstallationDate: Installed on 2022-11-29 (479 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2058775/+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 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
Hi aminesaka, About the #4, if you want to use the mic of bluetooth headset, please set output Configuration to HSP/HFP instead of A2DP. -- 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/2051570 Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Since the last three weeks' updates, I have encountered several challenges with the audio functionality on my system. Primarily, upon starting my laptop, the audio often fails to work, displaying "Dummy Output." To resolve this, I find myself needing to restart the laptop two or three times before the audio becomes functional. Even when the audio is working, I've noticed a recurring issue where, after playing video or audio for approximately 2-3 minutes, the sound starts crackling and buzzing. The intensity of these distortions gradually increases, resembling the static interference on a radio station with a weak signal. This issue persists even when using 3.5mm headphones, requiring the use of a USB headset or Bluetooth headphones to enjoy distortion-free audio. Furthermore, I have observed that, regardless of the Ubuntu version (ranging from 22.04 to 22.04.3), I face difficulties changing the microphone output settings when an external audio peripheral, such as a USB headset, 3.5mm headphones, or Bluetooth headphones, is connected. The OS appears to exclusively utilize the microphone from the connected peripheral, making it impossible to switch to the laptop's built-in microphone. For your reference, here are the specifications of my laptop and the Ubuntu version I am currently using: Laptop: Dell Vostro 3400 CPU: 11th Gen Intel i5-1135G7 GPU: Intel TigerLake-LP GT2 Iris Xe Memory: 2490MiB / 19720MiB Resolution: 1920x1080 OS: Ubuntu 22.04.3 LTS x86_64 Kernel: 6.5.0-14-generic DE: GNOME 42.9 Shell: bash 5.1.16 Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42 **UPDATE 12/02/2024 Noticed that every time my laptop fan starts spinning the crackling sound appears, after fan stops the crackling sound disappear. **UPDATE 19/03/2024 I did a software update to the linux kernel 6.5.0-26, now i get a dummy output in sound even if i restart the system many times, and if i use my Bluetooth headphone i can't use the mic, neither the mic of the laptop or of the headphone (there is no option is the settings to choose from) it's all blank. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galxy-a10 1437 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 17:50:44 2024 InstallationDate: Installed on 2024-01-16 (13 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: جانفي 29 17:49:49 galxya10-VR whoopsie-upload-all[712]: INFO:root:/var/crash/_usr_bin_pulseaudio.1000.crash already marked for upload, skipping Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2023 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.1 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23: dmi.product.family: Vostro dmi.product.name: Vostro 3400 dmi.product.sku: 0A23 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-01-28T08:52:28.427855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570/+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 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
Please upload a complete dmesg with the kernel you updated on 19/03/2024 (dummy output). And could you also test the latest upstream mainline kernel or ubuntu 24.04 (just put the iso to usb flash drive, boot from it and try ubuntu 24.04, no need to install). https://kernel.ubuntu.com/mainline/v6.8/ And also, it looks like a hardware issue to me. -- 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/2051570 Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Since the last three weeks' updates, I have encountered several challenges with the audio functionality on my system. Primarily, upon starting my laptop, the audio often fails to work, displaying "Dummy Output." To resolve this, I find myself needing to restart the laptop two or three times before the audio becomes functional. Even when the audio is working, I've noticed a recurring issue where, after playing video or audio for approximately 2-3 minutes, the sound starts crackling and buzzing. The intensity of these distortions gradually increases, resembling the static interference on a radio station with a weak signal. This issue persists even when using 3.5mm headphones, requiring the use of a USB headset or Bluetooth headphones to enjoy distortion-free audio. Furthermore, I have observed that, regardless of the Ubuntu version (ranging from 22.04 to 22.04.3), I face difficulties changing the microphone output settings when an external audio peripheral, such as a USB headset, 3.5mm headphones, or Bluetooth headphones, is connected. The OS appears to exclusively utilize the microphone from the connected peripheral, making it impossible to switch to the laptop's built-in microphone. For your reference, here are the specifications of my laptop and the Ubuntu version I am currently using: Laptop: Dell Vostro 3400 CPU: 11th Gen Intel i5-1135G7 GPU: Intel TigerLake-LP GT2 Iris Xe Memory: 2490MiB / 19720MiB Resolution: 1920x1080 OS: Ubuntu 22.04.3 LTS x86_64 Kernel: 6.5.0-14-generic DE: GNOME 42.9 Shell: bash 5.1.16 Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42 **UPDATE 12/02/2024 Noticed that every time my laptop fan starts spinning the crackling sound appears, after fan stops the crackling sound disappear. **UPDATE 19/03/2024 I did a software update to the linux kernel 6.5.0-26, now i get a dummy output in sound even if i restart the system many times, and if i use my Bluetooth headphone i can't use the mic, neither the mic of the laptop or of the headphone (there is no option is the settings to choose from) it's all blank. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galxy-a10 1437 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 17:50:44 2024 InstallationDate: Installed on 2024-01-16 (13 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: جانفي 29 17:49:49 galxya10-VR whoopsie-upload-all[712]: INFO:root:/var/crash/_usr_bin_pulseaudio.1000.crash already marked for upload, skipping Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2023 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.1 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23: dmi.product.family: Vostro dmi.product.name: Vostro 3400 dmi.product.sku: 0A23 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-01-28T08:52:28.427855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Uns
[Touch-packages] [Bug 2047719] Re: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: new slapd package pre-installation script subprocess returned error exit status 1
[Expired for openldap (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openldap (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2047719 Title: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: new slapd package pre-installation script subprocess returned error exit status 1 Status in openldap package in Ubuntu: Expired Bug description: Happened while upgrading ubuntu distro ProblemType: Package DistroRelease: Ubuntu 22.04 Package: slapd 2.4.49+dfsg-2ubuntu1.9 ProcVersionSignature: Ubuntu 5.15.0-1053.61~20.04.1-azure 5.15.131 Uname: Linux 5.15.0-1053-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Dec 29 23:55:31 2023 ErrorMessage: new slapd package pre-installation script subprocess returned error exit status 1 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1053-azure root=UUID=b9df59e6-c806-4851-befa-12402bca5828 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 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.2 apt 2.4.11 SourcePackage: openldap Title: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: new slapd package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-12-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2047719/+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
