[Touch-packages] [Bug 2049247] [NEW] Broken IPv4 support on IPv6-preferring networks (v255)
Public bug reported:
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.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
** Affects: systemd
Importance: Unknown
Status: Unknown
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble package-from-proposed
** Bug watch added:
[Touch-packages] [Bug 2047656] Re: [SRU] Players terminate after stopping and restarting
I've tested the proposed package and it works as expected. Thanks for the fix -- 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 2049244] [NEW] linuxx64.efi.stub missing on Ubuntu 23.10 installation
Public bug reported: I installed Ubuntu 23.10 server and converted it to UKI boot, but in the process of doing so I discovered that /usr/lib/systemd/boot/efi/linuxx64.efi.stub is for some reason missing on this installation even though it was supposed to come with systemd. I checked two Ubuntu 22.04 installations (desktop and server) and the file is present on both. For now I copied the file from one of those systems for my purposes as a workaround, but I believe it is a bug that the file is missing in the first place and should be fixed. ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/2049244 Title: linuxx64.efi.stub missing on Ubuntu 23.10 installation Status in systemd package in Ubuntu: New Bug description: I installed Ubuntu 23.10 server and converted it to UKI boot, but in the process of doing so I discovered that /usr/lib/systemd/boot/efi/linuxx64.efi.stub is for some reason missing on this installation even though it was supposed to come with systemd. I checked two Ubuntu 22.04 installations (desktop and server) and the file is present on both. For now I copied the file from one of those systems for my purposes as a workaround, but I believe it is a bug that the file is missing in the first place and should be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049244/+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 1592544] Re: ubuntu is using gallium graphics instead of intel graphics
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1592544 Title: ubuntu is using gallium graphics instead of intel graphics Status in xorg package in Ubuntu: Expired Bug description: xorg file empty, I tried to uninstall the gallium drivers but it didn't work ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.27 Thu Jun 9 18:53:27 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jun 14 21:50:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed nvidia-367, 367.27, 4.4.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05fe] Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fe] InstallationDate: Installed on 2016-04-25 (50 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. XPS 15 9530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=f565161c-e76f-4b59-b989-60ea2a0b51a6 ro nomodeset nomodeset nouveau.modeset=0 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Jun 14 21:48:10 2016 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1592544/+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 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Expired Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 2049234] Re: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later
** Summary changed: - tunnel interface creation fails on jammy 5.15.0-81 or later + non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later -- 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/2049234 Title: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later Status in systemd package in Ubuntu: New Bug description: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 https://bugs.launchpad.net/bugs/2029401 This causes creation of ip6tnl tunnel interface to fail through systemd-networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049234/+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 2049238] [NEW] Video does not output to second monitor
Public bug reported: I have a 2-display setup (laptop screen with second monitor). When I am booted into Linux kernel 6.5.0-14-generic, my laptop screen works fine, however my second monitor doesn't get any video input at all. This problem does not occur on previous Linux kernel versions. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Fri Jan 12 17:32:15 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 6.2.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Lenovo Wani [Radeon R5/R6/R7 Graphics] [17aa:39ff] InstallationDate: Installed on 2023-10-03 (101 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: LENOVO 80XS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15ABR dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr5QCN24WW:bd07/29/2019:br1.24:efr1.24:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:skuLENOVO_MT_80XS_BU_idea_FM_ideapad320-15ABR: dmi.product.family: ideapad 320-15ABR dmi.product.name: 80XS dmi.product.sku: LENOVO_MT_80XS_BU_idea_FM_ideapad 320-15ABR dmi.product.version: Lenovo ideapad 320-15ABR dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2049238 Title: Video does not output to second monitor Status in xorg package in Ubuntu: New Bug description: I have a 2-display setup (laptop screen with second monitor). When I am booted into Linux kernel 6.5.0-14-generic, my laptop screen works fine, however my second monitor doesn't get any video input at all. This problem does not occur on previous Linux kernel versions. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Fri Jan 12 17:32:15 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 6.2.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Lenovo Wani [Radeon R5/R6/R7 Graphics] [17aa:39ff] InstallationDate: Installed on 2023-10-03 (101 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: LENOVO 80XS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag
[Touch-packages] [Bug 2047450] Re: tail emits no output for sysfs files when using large page kernels
** Changed in: coreutils (Ubuntu Mantic) Status: Confirmed => In Progress ** Changed in: coreutils (Ubuntu Lunar) Status: Confirmed => In Progress ** Changed in: coreutils (Ubuntu Jammy) Status: Confirmed => In Progress -- 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/2047450 Title: tail emits no output for sysfs files when using large page kernels Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: In Progress Status in coreutils source package in Lunar: In Progress Status in coreutils source package in Mantic: In Progress Status in coreutils source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional -64k flavors). When booted on 64K kernels, tail emits no output when tailing a sysfs file. The difference in behavior can be a source for bugs in scripts that use tail, and general user confusion. [Test Plan] The upstream fix includes a test case that tails the /sys/kernel/profiling file, if it exists. That case would fail with an unfixed coreutils package as shown below: = When booted on a 4K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling 0 = When booted on a 64K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling ubuntu@gunyolk:~$ Since the upstream test cases are executed at build time, the existing tests and this new test will be used to regression test behavior. This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We should also do a manual verification on arm64 w/ the 64K kernel since that case is not covered by our builders. [Where Problems Could Occur] The biggest risk for a regression I see is due to the side-effect of the fix now allocating a dynamic buffer instead of the stack. An error in logic there could cause a crash or a memory leak in scenarios undetected during testing. I used valgrind when developing the fix to derisk the memory leak scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+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 2049234] Re: tunnel interface creation fails on jammy 5.15.0-81 or later
** Description changed: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 + https://bugs.launchpad.net/bugs/2029401 This causes creation of ip6tnl tunnel interface to fail through systemd- networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` -- 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/2049234 Title: tunnel interface creation fails on jammy 5.15.0-81 or later Status in systemd package in Ubuntu: New Bug description: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 https://bugs.launchpad.net/bugs/2029401 This causes creation of ip6tnl tunnel interface to fail through systemd-networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049234/+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 2049234] Re: tunnel interface creation fails on jammy 5.15.0-81 or later
** Description changed: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 This causes creation of ip6tnl tunnel interface to fail through systemd- networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument - I believe this is a regression. + I believe this is a regression; We encountered this linux- + image-5.15.0-91-generic installed via unattended-upgrade. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` ** Description changed: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 This causes creation of ip6tnl tunnel interface to fail through systemd- networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- - image-5.15.0-91-generic installed via unattended-upgrade. + image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL + during creating tunnel interfaces let AcceptIPv6RA function not to + start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` -- 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/2049234 Title: tunnel interface creation fails on jammy 5.15.0-81 or later Status in systemd package in Ubuntu: New Bug description: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 This causes creation of ip6tnl tunnel interface to fail through systemd-networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049234/+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 2049234] [NEW] tunnel interface creation fails on jammy 5.15.0-81 or later
Public bug reported: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 This causes creation of ip6tnl tunnel interface to fail through systemd- networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 - This causes creation of ip6tnl tunnel interface through systemd- + This causes creation of ip6tnl tunnel interface to fail through systemd- networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` - ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` ** Description changed: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 This causes creation of ip6tnl tunnel interface to fail through systemd- networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb + + (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` -- 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/2049234 Title: tunnel interface creation fails on jammy 5.15.0-81 or later Status in systemd package in Ubuntu: New Bug description: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 This causes creation of ip6tnl tunnel interface to fail through systemd-networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due
[Touch-packages] [Bug 2048092] Re: [low-priority SRU] Fix CVE-2022-0563 in source
@ahasenack - thanks for asking these questions. I do know of a user rebuilding jammy's util-linux. The build recipe I've seen installs these binaries. I don't know the risk that they might become setuid. This CVE I noticed as being fixed in a later version of util-linux, but not in jammy. I then looked it up in our CVE tracker and saw why we had chosen not to patch it. To verify that the code inside is not used, I used inotifywait during the build to watch for processes opening these .c files. Each file is opened exactly twice - both times during the dh-autoreconf phase, where it collects a checksum before and after using md5sum. Neither file is opened again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2048092 Title: [low-priority SRU] Fix CVE-2022-0563 in source Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Lunar: Fix Released Status in util-linux source package in Mantic: Fix Released Status in util-linux source package in Noble: Fix Released Bug description: [Impact] We did not fix this CVE in Ubuntu because we do not build the impacted binaries (we use --disable-chfn-chsh). However, some users are known to build their own binaries from this Ubuntu source and therefore could be impacted. [Test Plan] Since there is no impact to Ubuntu binaries, there is no functional change to verify. Regression testing using the existing build-time tests and autopkgtests should suffice. We should also verify that util-linux source builds fine w/ chfn and chsh enabled after applying this patch - otherwise it is really helping no one. [Where problems could occur] The upstream patch is clearly restricted to the chfn chsh binaries, which are not compiled by Ubuntu, so I don't see a risk there. I do see a risk that this is used as a precedent to fix other no-impact-to-Ubuntu security issues in other source - say, just to silence 3rd party security scanners. I do not intend to set such a precedent here, and suggest we consider them only on a case-by-case basis. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2048092/+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 2046495] Re: test-execute fails in LXD with failure in exec-privatenetwork-yes-privatemounts-yes.service
I think this test will just need to remain skipped. Since systemd gets -EPERM when trying to mount the private sysfs, it just takes some fallback code and re-uses the existing sysfs, which means that dummy- test-exec will still be accessible through sysfs. I can't currently think of a good way to generalize a patch for upstream, so we will probably just keep this in Ubuntu only. -- 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/2046495 Title: test-execute fails in LXD with failure in exec-privatenetwork-yes- privatemounts-yes.service Status in systemd package in Ubuntu: New Bug description: This is in v255. This log snippet is taken from a local autopkgtest build: exec-privatenetwork-yes-privatemounts-yes.service: Will spawn child (service_enter_start): /bin/sh exec-privatenetwork-yes-privatemounts-yes.service: Failed to set 'trusted.invocation_id' xattr on control group /system.slice/test-execute-48e27182b3724b7.scope/99d288e6f11f869e/system.slice/exec-privatenetwork-yes-privatemounts-yes.service, ignoring: Operation not permitted exec-privatenetwork-yes-privatemounts-yes.service: Failed to remove 'trusted.delegate' xattr flag on control group /system.slice/test-execute-48e27182b3724b7.scope/99d288e6f11f869e/system.slice/exec-privatenetwork-yes-privatemounts-yes.service, ignoring: Operation not permitted exec-privatenetwork-yes-privatemounts-yes.service: Failed to remove 'trusted.survive_final_kill_signal' xattr flag on control group /system.slice/test-execute-48e27182b3724b7.scope/99d288e6f11f869e/system.slice/exec-privatenetwork-yes-privatemounts-yes.service, ignoring: Operation not permitted exec-privatenetwork-yes-privatemounts-yes.service: Passing 0 fds to service exec-privatenetwork-yes-privatemounts-yes.service: About to execute: /bin/sh -x -c "! ip link show dummy-test-exec" Serializing sd-executor-state to memfd. exec-privatenetwork-yes-privatemounts-yes.service: Forked /bin/sh as 5092 Closing set fd 21 (socket:[116840]) Closing set fd 19 (socket:[113527]) Closing set fd 20 (socket:[116839]) exec-privatenetwork-yes-privatemounts-yes.service: Changed dead -> start Received SIGCHLD from PID 5092 (sh). Child 5092 (sh) died (code=exited, status=0/SUCCESS) exec-privatenetwork-yes-privatemounts-yes.service: Child 5092 belongs to exec-privatenetwork-yes-privatemounts-yes.service. exec-privatenetwork-yes-privatemounts-yes.service: Main process exited, code=exited, status=0/SUCCESS (success) exec-privatenetwork-yes-privatemounts-yes.service: Running next main command for state start. exec-privatenetwork-yes-privatemounts-yes.service: Will spawn child (service_run_next_main): /bin/sh exec-privatenetwork-yes-privatemounts-yes.service: Passing 0 fds to service exec-privatenetwork-yes-privatemounts-yes.service: About to execute: /bin/sh -x -c "test ! -e /proc/sys/net/ipv4/conf/dummy-test-exec" Serializing sd-executor-state to memfd. exec-privatenetwork-yes-privatemounts-yes.service: Forked /bin/sh as 5094 Closing set fd 21 (socket:[116840]) Closing set fd 19 (socket:[113527]) Closing set fd 20 (socket:[116839]) Received SIGCHLD from PID 5094 (sh). Child 5094 (sh) died (code=exited, status=0/SUCCESS) exec-privatenetwork-yes-privatemounts-yes.service: Child 5094 belongs to exec-privatenetwork-yes-privatemounts-yes.service. exec-privatenetwork-yes-privatemounts-yes.service: Main process exited, code=exited, status=0/SUCCESS (success) exec-privatenetwork-yes-privatemounts-yes.service: Running next main command for state start. exec-privatenetwork-yes-privatemounts-yes.service: Will spawn child (service_run_next_main): /bin/sh exec-privatenetwork-yes-privatemounts-yes.service: Passing 0 fds to service exec-privatenetwork-yes-privatemounts-yes.service: About to execute: /bin/sh -x -c "test ! -e /sys/class/net/dummy-test-exec" Serializing sd-executor-state to memfd. exec-privatenetwork-yes-privatemounts-yes.service: Forked /bin/sh as 5095 Closing set fd 21 (socket:[116840]) Closing set fd 19 (socket:[113527]) Closing set fd 20 (socket:[116839]) exec-privatenetwork-yes-privatemounts-yes.service: Control group is empty. Received SIGCHLD from PID 5095 (sh). Child 5095 (sh) died (code=exited, status=1/FAILURE) exec-privatenetwork-yes-privatemounts-yes.service: Child 5095 belongs to exec-privatenetwork-yes-privatemounts-yes.service. exec-privatenetwork-yes-privatemounts-yes.service: Main process exited, code=exited, status=1/FAILURE exec-privatenetwork-yes-privatemounts-yes.service: Failed with result 'exit-code'. exec-privatenetwork-yes-privatemounts-yes.service: Service will not restart (restart setting) exec-privatenetwork-yes-privatemounts-yes.service: Changed start -> failed exec-privatenetwork-yes-privatemounts-yes.service: Unit entered failed state.
[Touch-packages] [Bug 2049218] [NEW] [USB-Audio - Avantree DG60P, recording] Duplex is missing
Public bug reported: Under pavucontrol, I get four options (see below) : Mono Input, Analog Stereo Output, Digital Stereo (IEC958) Output, or Off. All options work fine (beside caveats below) but I am missing the Duplex mode. Recording works on Ardour if I set 8kHz sample rate. Other software (Mixxx) refuse to open the input probably because the sample rate (44.1kHz or 48kHz generally) apply to output and input, presumably. Any side answer on this point would be nice too, but my main concern is activating Duplex mode. This report is close, but different, to bug 2048897 with a different adapter (has same missing Duplex mode, but Loop110 works worse : no usable sound). $ pactl list Card #13 Name: alsa_card.usb-Qualcomm_Avantree_DG60P_A4DC15BFFAA7DE239586-02 Driver: module-alsa-card.c Owner Module: 37 Properties: alsa.card = "2" alsa.card_name = "Avantree DG60P" alsa.long_card_name = "Qualcomm Avantree DG60P at usb-:00:14.0-13.1.1, full speed" alsa.driver_name = "snd_usb_audio" device.bus_path = "pci-:00:14.0-usb-0:13.1.1:1.2" sysfs.path = "/devices/pci:00/:00:14.0/usb1/1-13/1-13.1/1-13.1.1/1-13.1.1:1.2/sound/card2" udev.id = "usb-Qualcomm_Avantree_DG60P_A4DC15BFFAA7DE239586-02" device.bus = "usb" device.vendor.id = "0a12" device.vendor.name = "Cambridge Silicon Radio, Ltd" device.product.id = "4007" device.product.name = "Avantree DG60P" device.serial = "Qualcomm_Avantree_DG60P_A4DC15BFFAA7DE239586" device.string = "2" device.description = "Avantree DG60P" module-udev-detect.discovered = "1" device.icon_name = "audio-card-usb" Profiles: input:mono-fallback: Mono Input (sinks: 0, sources: 1, priority: 1, available: yes) output:analog-stereo: Analog Stereo Output (sinks: 1, sources: 0, priority: 6500, available: yes) output:iec958-stereo: Digital Stereo (IEC958) Output (sinks: 1, sources: 0, priority: 5500, available: yes) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) Active Profile: output:analog-stereo Ports: analog-input-headset-mic: Headset Microphone (type: Headset, priority: 8800, latency offset: 0 usec, availability unknown) Properties: device.icon_name = "audio-input-microphone" Part of profile(s): input:mono-fallback analog-output: Analog Output (type: Analog, priority: 9900, latency offset: 0 usec, availability unknown) Part of profile(s): output:analog-stereo iec958-stereo-output: Digital Output (S/PDIF) (type: SPDIF, priority: 0, latency offset: 0 usec, availability unknown) Part of profile(s): output:iec958-stereo $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy $ apt-cache policy alsa-base alsa-base: Installed: 1.0.25+dfsg-0ubuntu7 Candidate: 1.0.25+dfsg-0ubuntu7 Version table: *** 1.0.25+dfsg-0ubuntu7 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status System is up to date (apt update ; apt upgrade) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-91.101-lowlatency 5.15.131 Uname: Linux 5.15.0-91-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcel 4814 F pulseaudio /dev/snd/controlC0: marcel 4814 F pulseaudio /dev/snd/controlC1: marcel 4814 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jan 12 17:23:15 2024 InstallationDate: Installed on 2023-02-13 (333 days ago) InstallationMedia: Ubuntu-Studio 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:DG60P successful Symptom_Card: Avantree DG60P - Avantree DG60P Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:DG60P failed Symptom_Type: None of the above Title: [USB-Audio - Avantree DG60P, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX582LR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX582LR dmi.board.vendor: ASUSTeK COMPUTER
[Touch-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
Sorry, forgot to add that the device appears in the Sound settings correctly and the integrated microphone is working too. There's just no sound coming out of the speaker. -- 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/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 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: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+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
Re: [Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi Christian,
Thank you, yes I don't disagree with anything you said. There can be no
"one size fits all" and customizing performance tuning will always be
important but I will argue
1. There can be a "one size fits most" at least for desktop client
environments ("general optimization")
2. It may be surprising what "general optimization" entails given the
general lack of consideration to the psychological experience of the user.
Apple discovered this as a historical accident a few decades ago. I am no
fan of them, though, because they don't allow that customization. My wife
is dyslexic and uses a Mac for work that does not allow her to install and
use OpenDyslexic fonts in the OS because Apple has already "determined what
is best."
To ground the 2nd point above, I would give a hypothetical: trading 25ms of
latency/jitter for a 10% gain in throughput might seem like a no-brainer
from a benchmarking perspective. But when user psychology is factored in as
well as allowing for adequate default performance for the widest use cases
available, the tradeoff quickly becomes unacceptable. The "relatively
large" 10% throughput has very little relevance outside of benchmarking
whereas the 25ms of latency/jitter can make or break entire workflows and
usage scenarios from a user perspective covering a broad set of scenarios.
The only danger there is that people will compare "out of the box benchmark
performance" and say "this system is slower than that system!"
But I agree, now it's time for more discussion and input (including data)
from others. I'm glad that this discussion is occurring! I don't think I
have anything more to offer at this point.
ethan
On Thu, Jan 11, 2024 at 11:20 PM Christian Ehrhardt <
1833...@bugs.launchpad.net> wrote:
> Hi Etanay,
>
> I realize I maybe wrote too much :-/
> So I start with a TL;DR:
> AFAICS you are right in all you say, but I think there can not be "one
> right answer" anyway. Hence I'm trying to leave all parties their freedom
> of defining what is important to them and try to learn from them what
> impact irqbalance has to that.
>
>
> > Yes I was not arguing strictly against irqbalance, just trying
> > to ascertain some discussion parameters as well as parameters for data
> > collection.
>
> Yeah, I see that and didn't intend to rebut your statements either.
> Just push them a bit into potential context and POV of others.
>
>
> > I have not yet seen a coherent philosophy on what it means to "optimize
> > performance" with default settings that serve the greatest capacity of
> > server or desktop scenarios.
>
> That is true, but the reason for that is that you can only optimize for
> something like a workload or particular HW.
>
> The defaults are usually trying to be not too crappy for any possible
> thing that might happen on e.g. Ubuntu which is quite a scope.
>
> > In my humble opinion, data collection is useless without this
> > framework of understanding what it is we are trying to achieve
> > and why in terms of system performance. To me this is the deeper
> > unresolved issue, perhaps.
>
> I can see your point and would not even argue against. But this is
> (this is opinion and a bit of experience, not scientific proven
> truth) only the problem if we'd try to solve the singular global
> and always valid "is irqbalance good or bad" question.
>
> Thinking about it I think I'm even of the same opinion than you,
> but instead of standardizing excatly what we are trying to achieve
> (which to me feels like selecting a workload or HW as optimization
> target) I was trying to reach out to as many groups as possible
> so we can see what HW/workloads are important to them and how
> irqbalance might help or interfere with that.
>
> A bit like the old case where some clouds brought it up that it is
> conflicting in virtio-net on their substrate and to be disabled
> by default there (see Debian and also some Ubuntu cloud images).
>
> I have personally no hope in reaching a general "this is good / bad"
> without considering it per workload or HW environment.
>
> Hence my hope is that if we manage to get this variety of preferences
> of different parties and only then the impact of irqbalance to that
> we can make compartmentalized decisions.
> For example as some suggested, making it no more the default in
> Desktop, but keeping it in other cases.
>
> And this is just me trying to be helpful and drive this from being
> a dormant case to something useful, I do not pretend to have the
> masterplan or the solution yet :-)
>
>
> > I fear that systems are currently optimized by default for throughput.
> For
> > users, responsiveness (which can include but is not limited to
> throughput)
> > and latency may be more important psychologically
>
> Can I just say yes here, you go into lengths explaining (thanks) but I
> already agreed here :-)
>
> Yet - as true as that is - it is true for a set of workloads and hardware,
> but not for all that Ubuntu can be (as I outlined above neither
[Touch-packages] [Bug 2049210] Re: After install Rasp Pi 4 - system fails to send report info to metrics server
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/2049210 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2049210 Title: After install Rasp Pi 4 - system fails to send report info to metrics server Status in xorg package in Ubuntu: New Bug description: Testing Rasp Pi Ubuntu Noble daily iso dated 12-01-2024 After install system fails to send report info to metrics server, (client:timeout exceeded while awaiting headers. Will also attach screenshot of error received. Not sure if this is correct package for the bug report - ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu6 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 14:26:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:D1:2B:AD vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.117-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2049210/+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 2049210] Re: After install Rasp Pi 4 - system fails to send report info to metrics server
** Summary changed: - After install system fails to send report info to metrics server + After install Rasp Pi 4 - system fails to send report info to metrics server -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2049210 Title: After install Rasp Pi 4 - system fails to send report info to metrics server Status in xorg package in Ubuntu: New Bug description: Testing Rasp Pi Ubuntu Noble daily iso dated 12-01-2024 After install system fails to send report info to metrics server, (client:timeout exceeded while awaiting headers. Will also attach screenshot of error received. Not sure if this is correct package for the bug report - ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu6 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 14:26:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:D1:2B:AD vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.117-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2049210/+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 2049210] Re: After install system fails to send report info to metrics server
Attached is screenshot of error ** Attachment added: "20240112_140420[1].jpg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2049210/+attachment/5738774/+files/20240112_140420%5B1%5D.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2049210 Title: After install Rasp Pi 4 - system fails to send report info to metrics server Status in xorg package in Ubuntu: New Bug description: Testing Rasp Pi Ubuntu Noble daily iso dated 12-01-2024 After install system fails to send report info to metrics server, (client:timeout exceeded while awaiting headers. Will also attach screenshot of error received. Not sure if this is correct package for the bug report - ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu6 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 14:26:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:D1:2B:AD vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.117-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2049210/+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 2049210] [NEW] After install Rasp Pi 4 - system fails to send report info to metrics server
Public bug reported: Testing Rasp Pi Ubuntu Noble daily iso dated 12-01-2024 After install system fails to send report info to metrics server, (client:timeout exceeded while awaiting headers. Will also attach screenshot of error received. Not sure if this is correct package for the bug report - ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu6 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 14:26:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:D1:2B:AD vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.117-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 noble reproducible ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2049210 Title: After install Rasp Pi 4 - system fails to send report info to metrics server Status in xorg package in Ubuntu: New Bug description: Testing Rasp Pi Ubuntu Noble daily iso dated 12-01-2024 After install system fails to send report info to metrics server, (client:timeout exceeded while awaiting headers. Will also attach screenshot of error received. Not sure if this is correct package for the bug report - ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu6 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 14:26:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:D1:2B:AD vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.117-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to:
[Touch-packages] [Bug 1731628] Re: Cannot add caldav calendar
This bug was fixed in the package gnome-online-accounts - 3.49.0-1 --- gnome-online-accounts (3.49.0-1) unstable; urgency=medium * New upstream release - Drop Last.fm provider - Add WebDav support, allowing adding CalDav integration for the GNOME Calendar app without using Evolution (Closes: #866794) (LP: #1731628) - Authentication for Google & Microsoft now uses the web browser instead of a webkitgtk-powered popup window (LP: #1826311, LP: #1827764) * debian/gnome-online-accounts.docs: README -> README.md * debian/gnome-online-accounts.install: Install new OAuth2 handler * debian/libgoa-backend-1.0-1.symbols: Update * Add patch to keep using gcr3 for now * Drop unused Build-Depends: webkit2gtk * Drop references to kfreebsd and use arch:any (Closes: #1058677) * Stop using debian/control.in and dh_gnome_clean -- Jeremy Bícha Wed, 10 Jan 2024 12:37:10 -0500 ** Changed in: gnome-online-accounts (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1731628 Title: Cannot add caldav calendar Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: Hi, I try to add a caldav calendar calendars -> Add -> From Web -> https://posteo.de:8443/calendars/max.mustermann/default/ and I hit enter but the "add" button in the right upper corner remains grayed out. Kind regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.26.2-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 11 14:47:03 2017 InstallationDate: Installed on 2017-11-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1731628/+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 1826311] Re: Cannot Login to Google with Advanced Protection Enabled
This bug was fixed in the package gnome-online-accounts - 3.49.0-1 --- gnome-online-accounts (3.49.0-1) unstable; urgency=medium * New upstream release - Drop Last.fm provider - Add WebDav support, allowing adding CalDav integration for the GNOME Calendar app without using Evolution (Closes: #866794) (LP: #1731628) - Authentication for Google & Microsoft now uses the web browser instead of a webkitgtk-powered popup window (LP: #1826311, LP: #1827764) * debian/gnome-online-accounts.docs: README -> README.md * debian/gnome-online-accounts.install: Install new OAuth2 handler * debian/libgoa-backend-1.0-1.symbols: Update * Add patch to keep using gcr3 for now * Drop unused Build-Depends: webkit2gtk * Drop references to kfreebsd and use arch:any (Closes: #1058677) * Stop using debian/control.in and dh_gnome_clean -- Jeremy Bícha Wed, 10 Jan 2024 12:37:10 -0500 ** Changed in: gnome-online-accounts (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1826311 Title: Cannot Login to Google with Advanced Protection Enabled Status in gnome-online-accounts: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: Description: Ubuntu 19.04 Release: 19.04 gnome-online-accounts: Installed: 3.32.0-1ubuntu1 Candidate: 3.32.0-1ubuntu1 Version table: *** 3.32.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 1) Open Online accounts and select google (From settings or during OS setup) 2) enter username and password. What I expect: I get the prompt to plug-in my 2 factor hardware key What actually happens: I get a prompt saying, "You can only use your Security keys with Google Chrome" Not sure if this is actually fixable, I know desktop firefox has hidden settings to allow u2f, but not sure if that extends to the embedded browsers (if gnome-online-accounts even uses an embedded firefox for its browser) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 00:16:27 2019 InstallationDate: Installed on 2019-04-25 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1826311/+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 1827764] Re: GOA cannot add a Gmail account of a minor (young child who needs consent)
This bug was fixed in the package gnome-online-accounts - 3.49.0-1 --- gnome-online-accounts (3.49.0-1) unstable; urgency=medium * New upstream release - Drop Last.fm provider - Add WebDav support, allowing adding CalDav integration for the GNOME Calendar app without using Evolution (Closes: #866794) (LP: #1731628) - Authentication for Google & Microsoft now uses the web browser instead of a webkitgtk-powered popup window (LP: #1826311, LP: #1827764) * debian/gnome-online-accounts.docs: README -> README.md * debian/gnome-online-accounts.install: Install new OAuth2 handler * debian/libgoa-backend-1.0-1.symbols: Update * Add patch to keep using gcr3 for now * Drop unused Build-Depends: webkit2gtk * Drop references to kfreebsd and use arch:any (Closes: #1058677) * Stop using debian/control.in and dh_gnome_clean -- Jeremy Bícha Wed, 10 Jan 2024 12:37:10 -0500 ** Changed in: gnome-online-accounts (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1827764 Title: GOA cannot add a Gmail account of a minor (young child who needs consent) Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: Hello I am user of ubuntu 18.04 with gnome version 3.28.2 and it seems that I have found a bug when a GMAIL account is added. I have a problem setting up my child's GMAIL account (minor). The normal thing in any web browser is that when entering the GMAIL website, enter the data of them and then have to enter mine to consent to their access. In the GNOME directly blocks access when entering from ONLINE ACCOUNTS. Is there a solution for you to access? Thanks and best regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.31 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 5 07:43:54 2019 InstallationDate: Installed on 2019-04-07 (27 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1827764/+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 2028935] Re: Merge rsyslog 8.2306.0-2
I have added some waiting time in tests to hopefully overcome autopkgtest issues: https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/458517 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2028935 Title: Merge rsyslog 8.2306.0-2 Status in rsyslog package in Ubuntu: Fix Released Bug description: Debian has upgraded rsyslog to 8.2306.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2028935/+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] [NEW] Audio problem on zoom + kubuntu 23.10
Public bug reported: 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. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- 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: New 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
[Touch-packages] [Bug 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
Hey there, thanks for the bug report. @Simon, First I'm lowering the severity because I don't think it's breaking systems in a way that justify the important you set > As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files I don't think that's true, it's iterating over XDG_CONFIG_DIRS and stops to the first match which should be etc/xdg/xdg-$desktopsession I've just tried under a wmaker session (makes it easier to confirm the behaviour of gtk because in modern desktops the theme default can be overwritten from xsettings or portal) when I copied the file to /etc/xdg/xdg-wmaker/gtk-3.0/settings.ini and edited the theme to Adwaita and confirmed restarting gtk3-demo it was using Adwaita instead of Yaru I would also advice to not do what you did in lxqt-session, if I understand the change correctly you are creating a local user configuration which isn't likely to stick around without the user knowing about it and which isn't desktop specific so will create problems for the users if they log into another desktop environment later on... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration Status in gtk+3.0 package in Ubuntu: Confirmed Status in lxqt-session package in Ubuntu: Fix Released Bug description: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg- divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+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 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
** Changed in: gtk+3.0 (Ubuntu) Importance: Critical => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration Status in gtk+3.0 package in Ubuntu: Confirmed Status in lxqt-session package in Ubuntu: Fix Released Bug description: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg- divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+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
