[Touch-packages] [Bug 2051625] Re: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1
Looks like systemd failed and started timing out for multiple things before this happened. So there's nothing bluez can do about that. ** Changed in: bluez (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2051625 Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous- processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in bluez package in Ubuntu: Invalid Bug description: i don't know why ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 29 19:22:29 2024 ErrorMessage: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2024-01-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. N56VZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=141cf8eb-0e88-4525-ba98-20cbc63c70ae ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: bluez Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.212:bd08/28/2012:br4.6:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N56VZ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: DC:85:DE:08:4E:27 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING RX bytes:1402 acl:0 sco:0 events:102 errors:0 TX bytes:6363 acl:0 sco:0 commands:102 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2051625/+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 2051617] Re: Raspberry Pi mouse buttons left and right unresponsive
Please check to see if the kernel is getting the button events:
sudo apt install evtest
sudo evtest
** Package changed: xorg (Ubuntu) => linux-raspi (Ubuntu)
** Changed in: linux-raspi (Ubuntu)
Status: New => Incomplete
** Package changed: linux-raspi (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Raspberry Pi mouse buttons left and right unresponsive
+ Raspberry Pi mouse buttons left and right unresponsive (on a PC)
--
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/2051617
Title:
Raspberry Pi mouse buttons left and right unresponsive (on a PC)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Using the event tracker tool
(
xmodmap -pp > ~/xmodmap-pp
xev | grep -i button
), buttons 4 and 5 are responsive, optical works (the cursor moves across the
screen).
Left and right click buttons are unresponsive. Mouse connected via
USB.
MOUSE INFO:
Raspberry Pi Mouse
CAN ICES-3 (B)/NMB-3(B)
Model No.: RPI-MOUSE
This issue has been extant every since I have tried to use this mouse.
Currently using Ubuntu Mantic Minotaur (23.10)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 29 21:24:11 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:09ed]
InstallationDate: Installed on 2023-12-16 (45 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid,
1.5M
|__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=aa49e6e1-853a-4b59-81d9-ea0fcd3ca2cf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2021
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 00V66M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.10.1:bd08/05/2021:br1.10:svnDellInc.:pnLatitude3510:pvr:rvnDellInc.:rn00V66M:rvrA00:cvnDellInc.:ct10:cvr:sku09ED:
dmi.product.family: Latitude
dmi.product.name: Latitude 3510
dmi.product.sku: 09ED
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051617/+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 2051548] Re: Problem in Booting and nomodeset
> Display resolution stuck at 800x600 after using nomodeset in grub. > But my Dell monitor has 1600x900 resolution. This is correct behaviour. "nomodeset" means to disable the graphics driver and to disable high resolution support. ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu) ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Invalid -- 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/2051548 Title: Problem in Booting and nomodeset Status in linux-hwe-6.5 package in Ubuntu: Invalid Bug description: Display resolution stuck at 800x600 after using nomodeset in grub. But my Dell monitor has 1600x900 resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 19:27:23 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:2111] InstallationDate: Installed on 2024-01-26 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=ba3dc7d3-3688-4f19-947e-a1d3aedb15f3 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2020 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61 dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/11/2020:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. 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.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051548/+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 2051625] [NEW] package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1
Public bug reported: i don't know why ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 29 19:22:29 2024 ErrorMessage: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2024-01-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. N56VZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=141cf8eb-0e88-4525-ba98-20cbc63c70ae ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: bluez Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.212:bd08/28/2012:br4.6:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N56VZ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0: Type: Primary Bus: USB BD Address: DC:85:DE:08:4E:27 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING RX bytes:1402 acl:0 sco:0 events:102 errors:0 TX bytes:6363 acl:0 sco:0 commands:102 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2051625 Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous- processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in bluez package in Ubuntu: New Bug description: i don't know why ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 29 19:22:29 2024 ErrorMessage: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2024-01-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. N56VZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=141cf8eb-0e88-4525-ba98-20cbc63c70ae ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: bluez Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.212:bd08/28/2012:br4.6:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N56VZ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB
[Touch-packages] [Bug 2045245] Re: ubuntu22.04 ibus Chinese pinying input not response
[Expired for ibus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ibus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2045245 Title: ubuntu22.04 ibus Chinese pinying input not response Status in ibus package in Ubuntu: Expired Bug description: I have used 22.04 many times, and I encountered this problem every time. During the first period of installing the system, everything was fine, but once I used the system for more than a few months, the ibus started to stop responding and I could not enter. There is no response when pressing any keys on the keyboard. The only solution is to manually click the input method icon in the upper right corner, switch to English, and then enter `ibus restart`. But this problem of input method not responding is too frequent and occurs every few minutes. I can't stand this torture anymore, and I now use a third-party input method. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2045245/+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 2051617] Re: Raspberry Pi mouse buttons left and right unresponsive
** Package changed: ubuntu => xorg (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/2051617
Title:
Raspberry Pi mouse buttons left and right unresponsive
Status in xorg package in Ubuntu:
New
Bug description:
Using the event tracker tool
(
xmodmap -pp > ~/xmodmap-pp
xev | grep -i button
), buttons 4 and 5 are responsive, optical works (the cursor moves across the
screen).
Left and right click buttons are unresponsive. Mouse connected via
USB.
MOUSE INFO:
Raspberry Pi Mouse
CAN ICES-3 (B)/NMB-3(B)
Model No.: RPI-MOUSE
This issue has been extant every since I have tried to use this mouse.
Currently using Ubuntu Mantic Minotaur (23.10)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 29 21:24:11 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:09ed]
InstallationDate: Installed on 2023-12-16 (45 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid,
1.5M
|__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=aa49e6e1-853a-4b59-81d9-ea0fcd3ca2cf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2021
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 00V66M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.10.1:bd08/05/2021:br1.10:svnDellInc.:pnLatitude3510:pvr:rvnDellInc.:rn00V66M:rvrA00:cvnDellInc.:ct10:cvr:sku09ED:
dmi.product.family: Latitude
dmi.product.name: Latitude 3510
dmi.product.sku: 09ED
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2051617/+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 2051617] [NEW] Raspberry Pi mouse buttons left and right unresponsive
You have been subscribed to a public bug:
Using the event tracker tool
(
xmodmap -pp > ~/xmodmap-pp
xev | grep -i button
), buttons 4 and 5 are responsive, optical works (the cursor moves across the
screen).
Left and right click buttons are unresponsive. Mouse connected via USB.
MOUSE INFO:
Raspberry Pi Mouse
CAN ICES-3 (B)/NMB-3(B)
Model No.: RPI-MOUSE
This issue has been extant every since I have tried to use this mouse.
Currently using Ubuntu Mantic Minotaur (23.10)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 29 21:24:11 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if
00 [VGA controller])
Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:09ed]
InstallationDate: Installed on 2023-12-16 (45 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=aa49e6e1-853a-4b59-81d9-ea0fcd3ca2cf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2021
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 00V66M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.10.1:bd08/05/2021:br1.10:svnDellInc.:pnLatitude3510:pvr:rvnDellInc.:rn00V66M:rvrA00:cvnDellInc.:ct10:cvr:sku09ED:
dmi.product.family: Latitude
dmi.product.name: Latitude 3510
dmi.product.sku: 09ED
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu wayland-session
--
Raspberry Pi mouse buttons left and right unresponsive
https://bugs.launchpad.net/bugs/2051617
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to xorg in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051454] Re: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel
This bug was fixed in the package pipewire - 1.0.1-1ubuntu3 --- pipewire (1.0.1-1ubuntu3) noble; urgency=medium * Fix broken audio when using a kernel without "fine grained unix mediation" patch (LP: #2051504, LP: #2051454) -- Sergio Costas Rodriguez Mon, 29 Jan 2024 19:03:45 +0200 ** Changed in: pipewire (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2051454 Title: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel Status in apparmor package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Fix Released Status in wireplumber package in Ubuntu: Confirmed Bug description: Ubuntu 24.04 noble I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work. relating service status: gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:418 error:25 (Input/output error) pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:426 error:25 (Input/output error) pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the AppArmor info. wireplumber[61568]: si-standard-link: in/out items are not valid anymore wireplumber[61568]: 2 of 2 PipeWire links failed to activate It's worked on kernel linux-image-6.5.0-14-generic. I built the same version 1.0.1 from the https://gitlab.freedesktop.org/pipewire source code, The sound card can be detected normally and shown in the gnome setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051454/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Description Updated. I'll work on getting the patch for Jammy approved
and then I will create the patch for Focal. I expect (and would love)
feedback on wording for the new print statements I made.
** Description changed:
- Compiling a Python extension using Python2 (Python 2.7.18) is making use
- of wrong compiler flags, hence dropping required optimizations when
- required. This is happening only when python2 is installed from Ubuntu's
- repositories. By default, Python's distutils module uses compiler and
- linker flags used to compile Python itself to be used to compile
- extensions.
+ [ Impact ]
- Steps to reproduce:
- 1) On Ubuntu 20.04, install python2 using apt package manager.
- 2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
+ When compiling Python extensions using Python2, CFLAGS optimization
+ flags are dropped.
- Python 2.7.18 (default, Jul 1 2022, 12:27:04)
- [GCC 9.4.0] on linux2
- Type "help", "copyright", "credits" or "license" for more information.
- >>> import sysconfig
- >>> sysconfig.get_config_var('CFLAGS')
- '-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
+ This behavior has been caused by our update in this patch
+
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
+ which differs from upstream.
- 3) Build a test extension module using python2 and verify the compilation
flags.
- python2 setup.py build_ext --inplace
+ The fix modifies the portion of code in Lib/distutils/sysconfig.py which
+ gets the cflags from the environments, and includes the dropped OPT flag
+ from get_config_vars().
- Output from below command is not matching with our expected above CFLAGS.
- aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
+ [ Test Plan ]
+
+ There will be 2 separate tests for this bug:
+ * Ensuring no-change rebuilds are not changed
+ * Ensuring local builds are not changed unless environment variable is set
+
+ Test 1) No-change rebuilds
+
+ To test that no-change rebuilds are not changed, the package python-
+ stdlib-extensions will be built against the new python2.7, and confirm
+ the compiler flags are not altered. This will be a manual test and
+ visual inspection of the build logs.
+
+ Test 2) Functional test
+
+ 1. Create test container
+ $ lxc launch ubuntu:jammy jammy-2002043
+ $ lxc shell ubuntu:jammy jammy-2002043
+
+ 2. Install required packages
+ # apt update -y && apt install -y python2 python-pip
+
+ 3. Create test files
+ # mkdir testprog
+ # cd testprog
+ # cat >setup.py
[Touch-packages] [Bug 2043579] Re: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2
** Also affects: cryptsetup (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: cryptsetup (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: initramfs-tools (Ubuntu Noble) Importance: Undecided Status: Triaged ** Also affects: auto-package-testing Importance: Undecided Status: New ** No longer affects: cryptsetup (Ubuntu Mantic) ** No longer affects: cryptsetup (Ubuntu Noble) ** No longer affects: initramfs-tools (Ubuntu Mantic) ** No longer affects: initramfs-tools (Ubuntu Noble) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2043579 Title: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 Status in Auto Package Testing: New Status in cryptsetup package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Triaged Bug description: The autopkgtest of initramfs-tools fails on armhf on noble: ``` qemu-ata-onlySKIP Test lists explicitly supported architectures, but the current architecture armhf isn't listed. unit-tests PASS qemu-klibc FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-busybox FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-virtio-only FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-separate-usrFAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-panic-shell FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net-dnsmasq FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 ``` The /usr/sbin/mkinitramfs call in build_initramfs() has following output: ``` cryptsetup: ERROR: Couldn't resolve device /dev/sda2 cryptsetup: WARNING: Couldn't determine root device copying from directory /tmp/autopkgtest.g0n4ix/autopkgtest_tmp/initramfs-test.qV8LgntBoK/rootdir ``` The two cryptsetup log lines are printed by /usr/share/initramfs- tools/hooks/cryptroot (which comes from cryptsetup-initramfs) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2043579/+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 2051222] Re: apport-gtk crashed with SIGSEGV in g_type_create_instance()
*** This bug is a duplicate of bug 2051221 *** https://bugs.launchpad.net/bugs/2051221 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2051221, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2051222/+attachment/5742178/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2051222/+attachment/5742181/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2051222/+attachment/5742185/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2051222/+attachment/5742186/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2051222/+attachment/5742187/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2051222/+attachment/5742188/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2051222/+attachment/5742189/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 2051221 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2051222 Title: apport-gtk crashed with SIGSEGV in g_type_create_instance() Status in apport package in Ubuntu: New Bug description: GNOME desktop crash on HDMI disconnect please see: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2050865 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: apport-gtk 2.20.11-0ubuntu82.5 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 10:14:00 2024 ExecutablePath: /usr/share/apport/apport-gtk ExecutableTimestamp: 1681427306 InstallationDate: Installed on 2022-05-01 (633 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcCwd: /home/hristo Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A SegvAnalysis: Segfault happened at: 0x7f47e018ccf4:mov0x18(%rax),%rax PC (0x7f47e018ccf4) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with SIGSEGV in g_type_create_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo mtime.conffile..etc.apport.crashdb.conf: 2022-05-17T00:40:19.420743 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2051222/+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 2051594] Re: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
The log output shows that you have pam_tally or pam_tally2 in your pam configuration. The preinst fails in order to save you from upgrading and breaking your system, leaving you with a configuration referencing an obsolete pam module. The message says: you are using pam_tally or pam_tally2 in your configuration The pam_tally and pam_tally2 modules have been removed from PAM. You are using one of these modules in your PAM configuration in /etc/pam.d. You must remove the uses of these modules before PAM can be upgraded; including these modules in your PAM configuration after the upgrade will stop users from being able to log into the system. Consider the pam_faillock module as a replacement for pam_tally. The fact that this message was shown to you via the pam preinst script also indicates that you were not using ubuntu-release-upgrader, the recommended way to upgrade between Ubuntu releases. On servers, please upgrading using 'sudo do-release-upgrade'. On desktops, please use 'update-manager'. ** Changed in: pam (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2051594 Title: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Status in pam package in Ubuntu: Invalid Bug description: failed during upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4.7 ProcVersionSignature: Ubuntu 5.4.0-170.188-generic 5.4.257 Uname: Linux 5.4.0-170-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 29 13:45:41 2024 ErrorMessage: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2017-09-02 (2340 days ago) InstallationMedia: Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.0.10 SourcePackage: pam Title: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2024-01-29 (0 days ago) modified.conffile..etc.security.limits.conf: [modified] mtime.conffile..etc.security.limits.conf: 2017-09-01T17:53:53.083396 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2051594/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Thanks Nafees! I'll go ahead and prepare the SRU and move forward with
it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
Invalid
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
In Progress
Status in python2.7 source package in Jammy:
In Progress
Status in python2.7 source package in Kinetic:
Invalid
Status in python2.7 source package in Lunar:
Invalid
Status in python2.7 source package in Mantic:
Invalid
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Thanks Mitchell for looking into this. The proposed workaround looks
good to me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
Invalid
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
In Progress
Status in python2.7 source package in Jammy:
In Progress
Status in python2.7 source package in Kinetic:
Invalid
Status in python2.7 source package in Lunar:
Invalid
Status in python2.7 source package in Mantic:
Invalid
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2051594] [NEW] package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
Public bug reported: failed during upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4.7 ProcVersionSignature: Ubuntu 5.4.0-170.188-generic 5.4.257 Uname: Linux 5.4.0-170-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 29 13:45:41 2024 ErrorMessage: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2017-09-02 (2340 days ago) InstallationMedia: Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.0.10 SourcePackage: pam Title: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2024-01-29 (0 days ago) modified.conffile..etc.security.limits.conf: [modified] mtime.conffile..etc.security.limits.conf: 2017-09-01T17:53:53.083396 ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2051594 Title: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Status in pam package in Ubuntu: New Bug description: failed during upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4.7 ProcVersionSignature: Ubuntu 5.4.0-170.188-generic 5.4.257 Uname: Linux 5.4.0-170-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 29 13:45:41 2024 ErrorMessage: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2017-09-02 (2340 days ago) InstallationMedia: Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.0.10 SourcePackage: pam Title: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2024-01-29 (0 days ago) modified.conffile..etc.security.limits.conf: [modified] mtime.conffile..etc.security.limits.conf: 2017-09-01T17:53:53.083396 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2051594/+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 2051594] Re: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2051594 Title: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Status in pam package in Ubuntu: New Bug description: failed during upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4.7 ProcVersionSignature: Ubuntu 5.4.0-170.188-generic 5.4.257 Uname: Linux 5.4.0-170-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 29 13:45:41 2024 ErrorMessage: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2017-09-02 (2340 days ago) InstallationMedia: Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.0.10 SourcePackage: pam Title: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2024-01-29 (0 days ago) modified.conffile..etc.security.limits.conf: [modified] mtime.conffile..etc.security.limits.conf: 2017-09-01T17:53:53.083396 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2051594/+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 2051454] Re: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel
Lovely stuff, thank you! Confirming pipewire 1.0.1-1ubuntu3 is now available in noble-proposed and works a charm. A quick "systemctl --user restart pipewire*.service" or reboot has audio working again on mainline and upstream kernels. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2051454 Title: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel Status in apparmor package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: In Progress Status in wireplumber package in Ubuntu: Confirmed Bug description: Ubuntu 24.04 noble I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work. relating service status: gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:418 error:25 (Input/output error) pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:426 error:25 (Input/output error) pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the AppArmor info. wireplumber[61568]: si-standard-link: in/out items are not valid anymore wireplumber[61568]: 2 of 2 PipeWire links failed to activate It's worked on kernel linux-image-6.5.0-14-generic. I built the same version 1.0.1 from the https://gitlab.freedesktop.org/pipewire source code, The sound card can be detected normally and shown in the gnome setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051454/+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 2051454] Re: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel
** Changed in: pipewire (Ubuntu) Importance: Undecided => High ** Changed in: pipewire (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2051454 Title: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel Status in apparmor package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: In Progress Status in wireplumber package in Ubuntu: Confirmed Bug description: Ubuntu 24.04 noble I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work. relating service status: gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:418 error:25 (Input/output error) pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:426 error:25 (Input/output error) pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the AppArmor info. wireplumber[61568]: si-standard-link: in/out items are not valid anymore wireplumber[61568]: 2 of 2 PipeWire links failed to activate It's worked on kernel linux-image-6.5.0-14-generic. I built the same version 1.0.1 from the https://gitlab.freedesktop.org/pipewire source code, The sound card can be detected normally and shown in the gnome setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051454/+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 2043579] Re: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2
** Changed in: initramfs-tools (Ubuntu) Status: New => Triaged ** Changed in: cryptsetup (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2043579 Title: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 Status in cryptsetup package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Triaged Bug description: The autopkgtest of initramfs-tools fails on armhf on noble: ``` qemu-ata-onlySKIP Test lists explicitly supported architectures, but the current architecture armhf isn't listed. unit-tests PASS qemu-klibc FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-busybox FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-virtio-only FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-separate-usrFAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-panic-shell FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net-dnsmasq FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 ``` The /usr/sbin/mkinitramfs call in build_initramfs() has following output: ``` cryptsetup: ERROR: Couldn't resolve device /dev/sda2 cryptsetup: WARNING: Couldn't determine root device copying from directory /tmp/autopkgtest.g0n4ix/autopkgtest_tmp/initramfs-test.qV8LgntBoK/rootdir ``` The two cryptsetup log lines are printed by /usr/share/initramfs- tools/hooks/cryptroot (which comes from cryptsetup-initramfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2043579/+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 2043579] Re: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2
Comparing the artifacts between a failed and successful log, the relevant difference appears to be that cryptsetup-initramfs is only installed in the failed log. These errors also appear during the setup phase when package installation causes the initramfs for the host to be updated: 3870s Processing triggers for initramfs-tools (0.142ubuntu15.1) ... 3870s Processing triggers for linux-image-6.5.0-15-generic (6.5.0-15.15) ... 3870s /etc/kernel/postinst.d/initramfs-tools: 3870s update-initramfs: Generating /boot/initrd.img-6.5.0-15-generic 3874s cryptsetup: ERROR: Couldn't resolve device /dev/sda2 3874s cryptsetup: WARNING: Couldn't determine root device So this seems like a host configuration issue. Is there a LP project for those for which we could add a task? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2043579 Title: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 Status in cryptsetup package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Triaged Bug description: The autopkgtest of initramfs-tools fails on armhf on noble: ``` qemu-ata-onlySKIP Test lists explicitly supported architectures, but the current architecture armhf isn't listed. unit-tests PASS qemu-klibc FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-busybox FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-virtio-only FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-separate-usrFAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-panic-shell FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net-dnsmasq FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 ``` The /usr/sbin/mkinitramfs call in build_initramfs() has following output: ``` cryptsetup: ERROR: Couldn't resolve device /dev/sda2 cryptsetup: WARNING: Couldn't determine root device copying from directory /tmp/autopkgtest.g0n4ix/autopkgtest_tmp/initramfs-test.qV8LgntBoK/rootdir ``` The two cryptsetup log lines are printed by /usr/share/initramfs- tools/hooks/cryptroot (which comes from cryptsetup-initramfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2043579/+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 2051371] Re: Backspace in gnome-terminal often deletes cluster
> It's never the terminal emulator (whether GNOME Terminal or any other terminal app) that decides what to print on a backspace keypress. The only thing it does is that it tells over the tty line that the backspace key has been pressed. Makes sense. However, the user thinks of gnome-terminal because that's what he runs... > If your input method cannot generate the symbols you need, and you need to press backspace as a workaround to get that, moreover, you need to rely on one particular behavior of backspace, then I'd argue that it's all the fault of your input method, it should be able to produce straight away whatever you wish to end up with. Unfortunately that's not always possible. Please take a look at the wiki page under [1]. With complex writing systems there's more than one way to write a word which look 'correct' on the screen, but the order of the code points is different [2]. Not very good if you search for that word. Therefore Keyman allows to define keyboards that can auto-correct words so that you end up with the same order of the code points regardless which way you type [3]. And that requires to replace some codepoints typed previously. > Maybe the bug you _really_ wanted to report is that gnome-terminal doesn't use the "surrounding text" feature of input methods? That would be nice to have but until then it would be good to have backspace working properly. But as you wrote in an earlier comment that has nothing to do with gnome-terminal... [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion [2] https://www.sil.org/resources/archives/91817 [3] https://help.keyman.com/keyboard/khmer_angkor/1.0.7/KAK_Documentation_EN.pdf ** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/2051371 Title: Backspace in gnome-terminal often deletes cluster Status in bash package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left with ខ (U+1781). Instead it should only delete the last codepoint, U+17d2. If I have ខែ (U+1781 U+17c2) a backspace deletes only U+17c2, similarly if I have ខ្ (U+1781 U+17d2) where the backspace deletes U+17d2. Further investigations show that backspace often deletes the entire cluster, i.e. diacritic(s) plus the base character, for example with x̣́ (U+0078 U+0301 U+0323) where a backspace deletes all three codepoints. gnome-terminal should only delete the last codepoint [1]. A real live example where this behavior is problematic is when using ibus-keyman with the Khmer Angkor keyboard [2]. When typing xEjmr the expected output is ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman does some reordering while typing to put the codepoints in a standardized order. Because gnome-terminal lacks support for surrounding text, the codepoints have to be deleted by emitting several backspace keypresses. Because of the deletion of the cluster the result in gnome-terminal is ្មែរ (U+17d2 U+1798 U+17c2 U+179a). [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion [2] https://github.com/keymanapp/keyman/issues/10481 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 [modified: usr/libexec/gnome-terminal-server] 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 12:21:42 2024 InstallationDate: Installed on 2022-04-12 (653 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2051371/+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 1674137] Re: ifdown unknown interface net-tools is broken
i am using 21.1 18 was a long time ago On 1/29/24 11:01 AM, Ken Sharp wrote: > Are you still seeing this issue? > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1674137 Title: ifdown unknown interface net-tools is broken Status in Linux Mint: New Status in net-tools package in Ubuntu: New Bug description: System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 5.3.1) Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena Network: Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller driver: alx port: d000 bus-ID: 03:00.0 IF: enp3s0 state: up speed: 1000 Mbps duplex: full Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: ath9k bus-ID: 04:00.0 IF: wlp4s0 state: up After mint 18.1 upgrade had various issues. After quite a few updates I started having issues with ifdown command. I use a script with qemu to setup a bridge (br0) with tap0 and the default wired connection enp3s0. The script began giving off unknown interface errors. Testing showed that the ifdown command changed behavior after the updates and now does this. The behavior is not limited to scripting. I changed the code from using ifdown to ifconfig enp3s0 down. This fails also within the script but with no error. It, however, works from a terminal just fine. I switched to using the ip command i.e. ip link set enp3s0 down. Same result, the interface does not go down, but no error. After the script is run and windows 7 boots in qemu I have to open a terminal and run the commands manually: >ifconfig enp3s0 down >ifconfig enp3s0 0.0.0.0 promisc up Then all is well. These commands will not run from within a script. The script is run as such: >sudo ./up.sh tap0 It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge. The fact that ifdown no longer recognizes any interfaces seems to point to a change in net-tools that has broken something. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1674137/+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 2051454] Re: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel
Ok, people from the apparmor mailing list explained that ENOPROTOOPT error is returned when the kernel doesn't have "fine grained unix mediation", and that it still hasn't been merged upstream, so it's a patch that has to be manually merged. I prepared a patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2051454 Title: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel Status in apparmor package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in wireplumber package in Ubuntu: Confirmed Bug description: Ubuntu 24.04 noble I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work. relating service status: gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:418 error:25 (Input/output error) pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:426 error:25 (Input/output error) pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the AppArmor info. wireplumber[61568]: si-standard-link: in/out items are not valid anymore wireplumber[61568]: 2 of 2 PipeWire links failed to activate It's worked on kernel linux-image-6.5.0-14-generic. I built the same version 1.0.1 from the https://gitlab.freedesktop.org/pipewire source code, The sound card can be detected normally and shown in the gnome setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051454/+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 2051573] [NEW] [HDA-Intel - HD-Audio Generic, playback] No sound at all
Public bug reported: Internal speakers - no sound Headphones (jack) no sound HDMI sound works while connected to external monitor, there are some minor quality issues Ubuntu 22.04 kernel 6.5.0-15-generic on Huawei Matebook 14D ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 17:39:17 2024 InstallationDate: Installed on 2023-07-13 (200 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: acp - acp Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2023 dmi.bios.release: 1.8 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.08 dmi.board.asset.tag: N/A dmi.board.name: KLVL-WXXW-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnHUAWEI:bvr1.08:bd01/11/2023:br1.8:efr1.8:svnHUAWEI:pnKLVL-WXXW:pvrM1010:rvnHUAWEI:rnKLVL-WXXW-PCB:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook 14 dmi.product.name: KLVL-WXXW dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2051573 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Internal speakers - no sound Headphones (jack) no sound HDMI sound works while connected to external monitor, there are some minor quality issues Ubuntu 22.04 kernel 6.5.0-15-generic on Huawei Matebook 14D ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 17:39:17 2024 InstallationDate: Installed on 2023-07-13 (200 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: acp - acp Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2023 dmi.bios.release: 1.8 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.08 dmi.board.asset.tag: N/A dmi.board.name: KLVL-WXXW-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnHUAWEI:bvr1.08:bd01/11/2023:br1.8:efr1.8:svnHUAWEI:pnKLVL-WXXW:pvrM1010:rvnHUAWEI:rnKLVL-WXXW-PCB:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook 14 dmi.product.name: KLVL-WXXW dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051573/+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 2051572] Re: Always preseed core and snapd snap in server seed
** Merge proposal linked: https://code.launchpad.net/~philroche/ubuntu-seeds/+git/ubuntu/+merge/459599 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snaps snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snaps snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2051576] [NEW] Please merge 1.9.15p5-3 into noble
Public bug reported: tracking bug ** Affects: sudo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2051576 Title: Please merge 1.9.15p5-3 into noble Status in sudo package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2051576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051570] [NEW] [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: Since the last three weeks' updates, I have encountered several challenges with the audio functionality on my system. Primarily, upon starting my laptop, the audio often fails to work, displaying "Dummy Output." To resolve this, I find myself needing to restart the laptop two or three times before the audio becomes functional. Even when the audio is working, I've noticed a recurring issue where, after playing video or audio for approximately 2-3 minutes, the sound starts crackling and buzzing. The intensity of these distortions gradually increases, resembling the static interference on a radio station with a weak signal. This issue persists even when using 3.5mm headphones, requiring the use of a USB headset or Bluetooth headphones to enjoy distortion-free audio. Furthermore, I have observed that, regardless of the Ubuntu version (ranging from 22.04 to 22.04.3), I face difficulties changing the microphone output settings when an external audio peripheral, such as a USB headset, 3.5mm headphones, or Bluetooth headphones, is connected. The OS appears to exclusively utilize the microphone from the connected peripheral, making it impossible to switch to the laptop's built-in microphone. For your reference, here are the specifications of my laptop and the Ubuntu version I am currently using: Laptop: Dell Vostro 3400 CPU: 11th Gen Intel i5-1135G7 GPU: Intel TigerLake-LP GT2 Iris Xe Memory: 2490MiB / 19720MiB Resolution: 1920x1080 OS: Ubuntu 22.04.3 LTS x86_64 Kernel: 6.5.0-14-generic DE: GNOME 42.9 Shell: bash 5.1.16 Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42 UPDATE 29-01-2024 After the latest Linux kernel update to "6.5.0-15-generic." Following the update, I observed a significant reduction in crackling sound (approximately 80%) after disabling C-states from the BIOS. However, this improvement came at the cost of higher CPU temperatures, with the fan constantly running. Conversely, with C-states enabled, the crackling sound occurs only when the fan starts working. Additionally, I am still encountering the "Dummy Output" audio issue consistently on a fresh start, necessitating a reboot to resolve. I want to emphasize that I receive updates from the Tunisia Ubuntu server. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galxy-a10 1437 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 17:50:44 2024 InstallationDate: Installed on 2024-01-16 (13 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: جانفي 29 17:49:49 galxya10-VR whoopsie-upload-all[712]: INFO:root:/var/crash/_usr_bin_pulseaudio.1000.crash already marked for upload, skipping Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2023 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.1 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23: dmi.product.family: Vostro dmi.product.name: Vostro 3400 dmi.product.sku: 0A23 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-01-28T08:52:28.427855 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2051570 Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Since the last three weeks' updates, I have encountered several challenges with the audio functionality on my system. Primarily, upon starting my laptop, the audio often fails to work, displaying "Dummy Output." To resolve this, I find myself needing to restart the laptop two or three times before the audio becomes functional. Even when the audio is working, I've noticed a recurring issue where, after playing video or
[Touch-packages] [Bug 2051572] [NEW] Always preseed core and snapd snap in server seed
Public bug reported: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snaps snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real0m29.107s user0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real0m15.034s user0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re-introduce core22 and snaps snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Assignee: Philip Roche (philroche) Status: New ** Affects: ubuntu-meta (Ubuntu Noble) Importance: Undecided Assignee: Philip Roche (philroche) Status: New ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Philip Roche (philroche) ** Also affects: ubuntu-meta (Ubuntu Noble) Importance: Undecided Assignee: Philip Roche (philroche) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snaps snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snaps snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
I updated my livecd-rootfs PPA test package that runs this section of code in a loop to use this pattern, and it survived until the autopkgtest timeout - 304 iterations: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf- loop/noble/amd64/l/livecd-rootfs/20240128_061640_5c909@/log.gz ...when it previously was failing reliably within a few iterations. They `udevadm lock` fix is now in unstable, so the next sync should pull it in. However, I don't know that we really need any features of `udevadm lock` beyond the actual flock'ing of the device. We could presumably do that with `flock` for older releases. Or we could consider SRU'ing back the udevadm lock command to jammy as a low priority SRU. The way it was introduced looks very non-invasive: https://github.com/systemd/systemd/commit/8b12a516e9304f720e07eeec5d25c5b7f7104bc9 But I haven't gone through the bug fixes since to ensure it remained that way. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 1093649] Re: Supporting device assignment in /etc/ethers
This isn't something Ubuntu should be working on. Please file a request upstream with the original maintainer. ** Changed in: net-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1093649 Title: Supporting device assignment in /etc/ethers Status in net-tools package in Ubuntu: Invalid Bug description: I'm using Ubuntu 13.04 dev with net-tools 1.60-24.2ubuntu1 (arp 1.88). The -s option from arp allows to load address informations from a file. But if I want to set a static arp entry for 2 different devices (for example eth0 and wlan0) I have to use 2 different files if I don't want to have all entries assigned to both devices. In this case it would be usefull if the format of the file had an optional extra column. This columns stores the assigned device which is only read if the -i option is not given. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1093649/+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 1674137] Re: ifdown unknown interface net-tools is broken
Are you still seeing this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1674137 Title: ifdown unknown interface net-tools is broken Status in Linux Mint: New Status in net-tools package in Ubuntu: New Bug description: System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 5.3.1) Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena Network: Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller driver: alx port: d000 bus-ID: 03:00.0 IF: enp3s0 state: up speed: 1000 Mbps duplex: full Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: ath9k bus-ID: 04:00.0 IF: wlp4s0 state: up After mint 18.1 upgrade had various issues. After quite a few updates I started having issues with ifdown command. I use a script with qemu to setup a bridge (br0) with tap0 and the default wired connection enp3s0. The script began giving off unknown interface errors. Testing showed that the ifdown command changed behavior after the updates and now does this. The behavior is not limited to scripting. I changed the code from using ifdown to ifconfig enp3s0 down. This fails also within the script but with no error. It, however, works from a terminal just fine. I switched to using the ip command i.e. ip link set enp3s0 down. Same result, the interface does not go down, but no error. After the script is run and windows 7 boots in qemu I have to open a terminal and run the commands manually: >ifconfig enp3s0 down >ifconfig enp3s0 0.0.0.0 promisc up Then all is well. These commands will not run from within a script. The script is run as such: >sudo ./up.sh tap0 It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge. The fact that ifdown no longer recognizes any interfaces seems to point to a change in net-tools that has broken something. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1674137/+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 1763534] Re: ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters.
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1763534 Title: ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters. Status in net-tools package in Ubuntu: Confirmed Status in net-tools source package in Bionic: Confirmed Bug description: When executing ifconfig, it outputs the whole 10 characters of the interface name. However, when using ifconfig -s (or ifconfig -a -s) it doesn't include all the name of the interface (or 10+ characters). Instead, it outputs only 8 characters of the interface. ubuntu@dradis:~$ ifconfig -a enP2p1s0f0: flags=4163 mtu 1500 inet 10.245.71.108 netmask 255.255.248.0 broadcast 10.245.71.255 inet6 fe80::ae1f:6bff:fe09:c052 prefixlen 64 scopeid 0x20 ether ac:1f:6b:09:c0:52 txqueuelen 1000 (Ethernet) RX packets 154570 bytes 229998298 (229.9 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 61080 bytes 6131460 (6.1 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enP2p1s0f1: flags=4098 mtu 1500 ether ac:1f:6b:09:c0:53 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ubuntu@dradis:~$ ifconfig -a -s Iface MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg enP2p1s0 1500 154607 0 0 0 61101 0 0 0 BMRU enP2p1s0 15000 0 0 0 0 0 0 0 BM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1763534/+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 1096873] Re: netstat -i option malformed
No information provided whatsoever. ** Changed in: net-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1096873 Title: netstat -i option malformed Status in net-tools package in Ubuntu: Invalid Bug description: $ netstat -V net-tools 1.60 netstat 1.42 (2001-04-15) Fred Baumgarten, Alan Cox, Bernd Eckenfels, Phil Blundell, Tuan Hoang and others +NEW_ADDRT +RTF_IRTT +RTF_REJECT +FW_MASQUERADE -I18N AF: (inet) +UNIX +INET +INET6 +IPX +AX25 +NETROM +X25 +ATALK -ECONET -ROSE HW: +ETHER +ARC +SLIP +PPP +TUNNEL +TR +AX25 +NETROM +X25 +FR -ROSE -ASH -SIT -FDDI -HIPPI -HDLC/LAPB $ Kernel Interface table Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg eth0 1500 0 1816781 0 0 0 217707 0 0 0 BMRU eth1 1500 0 293560 0 21 0 394001 0 0 0 BMRU eth2 1500 0 0 0 0 0 0 0 0 0 BMU lo16436 0 257620 0 0 0 257620 0 0 0 LRU port1 1500 0 0 0 0 0 0 0 0 0 BMU port1 1500 0 0 0 0 0 0 0 0 0 BMU port2 1500 0 0 0 0 0 0 0 0 0 BMU port2 1500 0 0 0 0 0 0 0 0 0 BMU Although ports are named as port1-2, ... and port2-1,... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1096873/+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 878333] Re: ifconfig not showing virtual ip addresses
Is this still an issue after a decade? ** Changed in: net-tools (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/878333 Title: ifconfig not showing virtual ip addresses Status in net-tools package in Ubuntu: Incomplete Bug description: After upgrading to 11.10 my virtual ip addresses do not show up in an ifconfig (-a). Furthermore the eth0:1 address seems to be used for eth0 itself, and the DHCP assigned address (10.8.100.81) is seen as secondary address for eth0? ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: net-tools 1.60-23ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Wed Oct 19 18:30:37 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: net-tools UpgradeStatus: Upgraded to oneiric on 2011-10-14 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/878333/+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 921280] Re: ifconfig does not display sub-interfaces (aka: eth0:1 )
** Changed in: net-tools (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/921280 Title: ifconfig does not display sub-interfaces (aka: eth0:1 ) Status in net-tools package in Ubuntu: Fix Released Bug description: I have noticed a possible regression in ifconfig. When executing # ifconfig , only parent network interfaces are output. ifconfig is failing to display child/sub interfaces (aka. secondary interfaces.) Also, running "# ifconfig -a" doesn't display the child/sub- interfaces. Although the secondary IP is bound to the parent interface, and functional. The child/sub-interface IP addresses *can* be properly seen on eth0 when using iproute, by running "# ip addr", as expected. The /etc/network/interfaces file specifies two eth0 interfaces and addresses. Example: (lo entry omitted) auto eth0 iface eth0 inet static address 10.10.10.10 netmask 255.255.255.0 broadcast 10.10.10.255 gateway 10.10.10.1 auto eth0:2 iface eth0:2 inet static address 10.10.10.11 netmask 255.255.255.0 - I have observed this on two separate Oneiric-servers, v11.10. ::Critical Details:: Ubuntu Server: Oneiric v11.10 Package net-tools version: 1.60-23ubuntu3 Package ifupdown version: 0.7~alpha5.1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/921280/+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 1415159] Re: netstat giving negative octet values
1.60-26 landed in Xenial. Fixed. ** Changed in: net-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1415159 Title: netstat giving negative octet values Status in net-tools package in Ubuntu: Fix Released Bug description: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.04.4 LTS Release:10.04 Codename: lucid I keep getting the following from netstat -us: IcmpMsg: InType3: 103 InType8: 12 OutType0: 12 OutType3: 268 OutType11: 6 Udp: 999114787 packets received 1524847 packets to unknown port received. 5882127 packet receive errors 1003746107 packets sent UdpLite: IpExt: InMcastPkts: 143997 OutMcastPkts: 3885 InBcastPkts: 99976 OutBcastPkts: 2455 InOctets: -1042835510 OutOctets: -62785229 InMcastOctets: 15435060 OutMcastOctets: 135125 InBcastOctets: 13591924 OutBcastOctets: 326303 The bug has been fixed in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561161 I have tried updating net-tools package to utopic (14.10) but I get the following errors: npacking replacement libnih-dbus1 ... dpkg-deb: file `/var/cache/apt/archives/libnih-dbus1_1.0.3-4ubuntu26_amd64.deb' contains ununderstood data member data.tar.xz , giving up dpkg: error processing /var/cache/apt/archives/libnih-dbus1_1.0.3-4ubuntu26_amd64.deb (--unpack): – To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1415159/+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 2051454] Re: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel
I'm the author of the patch. The man page says nothing about ENOPROTOOPT, that's why I didn't managed that error. Clearly it is incomplete. Does anybody know where to send a patch for that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2051454 Title: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel Status in apparmor package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in wireplumber package in Ubuntu: Confirmed Bug description: Ubuntu 24.04 noble I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work. relating service status: gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:418 error:25 (Input/output error) pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:426 error:25 (Input/output error) pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the AppArmor info. wireplumber[61568]: si-standard-link: in/out items are not valid anymore wireplumber[61568]: 2 of 2 PipeWire links failed to activate It's worked on kernel linux-image-6.5.0-14-generic. I built the same version 1.0.1 from the https://gitlab.freedesktop.org/pipewire source code, The sound card can be detected normally and shown in the gnome setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051454/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Nafees, while exploring adding this change, a priority is to not cause
any regressions in packages already built in the archives. This is
unfortunately a non-trivial change so I'm proposing making this an opt-
in change, but make an informative message whenever someone compiles
wheels, so they can be made aware of it. This will make it so there's
minimal chances of regression, and spreads the word of this change.
How does this solution sound? I have the change staged in
https://code.launchpad.net/~mitchdz/ubuntu/+source/python2.7/+git/python2.7/+merge/458533
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
Invalid
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
In Progress
Status in python2.7 source package in Jammy:
In Progress
Status in python2.7 source package in Kinetic:
Invalid
Status in python2.7 source package in Lunar:
Invalid
Status in python2.7 source package in Mantic:
Invalid
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."
hey, i removed the "quiet" and did a bit of alternate outputs. the action is 'start' for my failing 'xrdp'. Job for xrdp.service failed because the control process exited with error code. See "systemctl status xrdp.service" and "journalctl -xeu xrdp.service" for details. Could not execute systemctl: - start at /usr/bin/deb-systemd-invoke line 143. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2003756 Title: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142." Status in init-system-helpers package in Ubuntu: Triaged Status in krb5 package in Ubuntu: Triaged Bug description: I have a fresh install of Ubuntu Server 22.04.01 LTS. After installing the server and running all updates, I run the following command: apt -y install slapd ldap-utils schema2ldif sasl2-bin libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc This will be installing krb5-kdc 1.19.2-2. This is in preparation for setting up an OpenLDAP server, a Kerberos server with an LDAP backend, and saslauthd for pass-through authentication. krb5-kdc was auto-selected when running the steps in the guide here in my development environment: https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend When installing that, I get the following in the output: Setting up krb5-kdc (1.19.2-2) ... Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service → /lib/systemd/system/krb5-kdc.service. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I do get the prompts for the realm, kdc, and admin server hostnames, and they are reflected in /etc/krb5.conf. If I then run the following: dpkg-reconfigure krb5-kdc I am prompted for whether I want the package to create the Kerberos KDC configuration automatically, and when I say yes, it then repeats the following error: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I cannot find any further debug in the syslog or anything to indicate what the root cause is; the list of packages here are all installed together on a separate development server where I experimented with the configuration I will be deploying here in production so I don't think it's incompatible packages in the install list, but I am open to feedback on that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2051346] Re: No longer preseed LXD snap to allow for LXD 5.20 release
This has been released in Noble version 1.529 ** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Released ** Also affects: ubuntu-meta (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Changed in: ubuntu-meta (Ubuntu Noble) Assignee: (unassigned) => Philip Roche (philroche) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051346 Title: No longer preseed LXD snap to allow for LXD 5.20 release Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Noble: Fix Released Bug description: With LXD 5.20 there is a license change to AGPL and it has been decided to no longer seed the snap in Ubuntu 24.04 and later and instead seed the lxd-installer package instead. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346/+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 2051548] [NEW] Problem in Booting and nomodeset
Public bug reported: Display resolution stuck at 800x600 after using nomodeset in grub. But my Dell monitor has 1600x900 resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 19:27:23 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:2111] InstallationDate: Installed on 2024-01-26 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=ba3dc7d3-3688-4f19-947e-a1d3aedb15f3 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2020 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61 dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/11/2020:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. 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.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 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/2051548 Title: Problem in Booting and nomodeset Status in xorg package in Ubuntu: New Bug description: Display resolution stuck at 800x600 after using nomodeset in grub. But my Dell monitor has 1600x900 resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 19:27:23 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:2111] InstallationDate: Installed on 2024-01-26 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=ba3dc7d3-3688-4f19-947e-a1d3aedb15f3 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2020 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61 dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M.
[Touch-packages] [Bug 535054] Re: Shouldn't use SIGILL to detect NEON
It looks this code changed a lot since 2010. Is this still an issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to x264 in Ubuntu. https://bugs.launchpad.net/bugs/535054 Title: Shouldn't use SIGILL to detect NEON Status in x264 package in Ubuntu: Triaged Bug description: Binary package hint: x264 Hey x264 currently uses SIGILL to test for support of NEON (and other features, on non-armel arch too); according to Dave Martin we need to disable the the "fast NEON MRC" test as """ this performance counter based test may not be safe across all platforms, and won't reliably give the right answer even where it doesn't SIGILL— it also requires a patched kernel; so we probably don't want it enabled in Ubuntu (unless we can use some other decision route like identifying the CPU from the contents of /proc/cpuinfo. I haven't attempted this for now.) """ see bug #388388 and bug #524859 (comments 6 and 7); patches: http://launchpadlibrarian.net/39623773/x264-enable-neon-runtime-detection.diff http://launchpadlibrarian.net/39623809/x264-rules.diff Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x264/+bug/535054/+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 2049117] Re: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep
** Description changed: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep From testing sound came but not from google chrome ---=== Update ===--- False alarm. Sound i was able to put back on, turn out i dont remember i turned off sound on Chrome in task menu of Kubuntu. Icon shows sound playing and when clicking sound speaker icon in taskbar of chrome then it shows very thin line that sound is turned mute off. === Suggestion === Since i dont remember i turned it off or dont see big difference or red icon that sound is off then i dont know its off. NEED different icon (size, more contrast, red color, round red X sign) so i can see warning that sound is off. image attached how hard it is to see any difference from speaker icon when turned off + === Suggestion 2 === + I just accidentally again clicked on it because it appears on all open windows. Can it not be only one one window of chrome where it playing? + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kng2239 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jan 12 01:20:49 2024 InstallationDate: Installed on 2024-01-05 (6 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kng2239 F pulseaudio /dev/snd/pcmC0D0p: kng2239 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2023 dmi.bios.release: 15.0 dmi.bios.vendor: HP dmi.bios.version: T70 Ver. 01.15.00 dmi.board.name: 87E0 dmi.board.vendor: HP dmi.board.version: KBC Version 33.24.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 51.36 dmi.modalias: dmi:bvnHP:bvrT70Ver.01.15.00:bd10/06/2023:br15.0:efr51.36:svnHP:pnHPProBook440G8NotebookPC:pvrSBKPF:rvnHP:rn87E0:rvrKBCVersion33.24.00:cvnHP:ct10:cvr:sku27J72EA#B1R: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 440 G8 Notebook PC dmi.product.sku: 27J72EA#B1R dmi.product.version: SBKPF dmi.sys.vendor: HP -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2049117 Title: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep Status in alsa-driver package in Ubuntu: Invalid Status in plasma-workspace package in Ubuntu: New Bug description: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep From testing sound came but not from google chrome ---=== Update ===--- False alarm. Sound i was able to put back on, turn out i dont remember i turned off sound on Chrome in task menu of Kubuntu. Icon shows sound playing and when clicking sound speaker icon in taskbar of chrome then it shows very thin line that sound is turned mute off. === Suggestion === Since i dont remember i turned it off or dont see big difference or red icon that sound is off then i dont know its off. NEED different icon (size, more contrast, red color, round red X sign) so i can see warning that sound is off. image attached how hard it is to see any difference from speaker icon when turned off === Suggestion 2 === I just accidentally again clicked on it because it appears on all open windows. Can it not be only one one window of chrome where it playing? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kng2239 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jan 12 01:20:49 2024 InstallationDate: Installed on 2024-01-05 (6 days ago) InstallationMedia: Kubuntu 22.04.3
[Touch-packages] [Bug 2051541] [NEW] unattended-upgrades ftbfs with Python 3.12 as default
Public bug reported: [...] Running ./test_pep484.py with python3 s -- Ran 0 tests in 0.000s NO TESTS RAN (skipped=1) make[2]: *** [Makefile:9: check] Error 5 make[2]: Leaving directory '/<>/test' make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2 5 is a new exit value when all tests are skipped. ** Affects: unattended-upgrades (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-nn-incoming ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2051541 Title: unattended-upgrades ftbfs with Python 3.12 as default Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: [...] Running ./test_pep484.py with python3 s -- Ran 0 tests in 0.000s NO TESTS RAN (skipped=1) make[2]: *** [Makefile:9: check] Error 5 make[2]: Leaving directory '/<>/test' make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2 5 is a new exit value when all tests are skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2051541/+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 2051540] [NEW] ufw ftbfs with Python 3.12 as default
Public bug reported:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in
test_ufwcommand_parse
self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
==
ERROR: test_ufwcommand_rule_get_command
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
Test UFWCommand(Route)Rule.get_command()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in
test_ufwcommand_rule_get_command
self.assertEquals(len(errors), 0,
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
--
Ran 24 tests in 7.584s
FAILED (errors=9)
test_skeleton
test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
Test example dummy test ... ok
--
Ran 1 test in 0.000s
OK
** Affects: ufw (Ubuntu)
Importance: High
Status: Confirmed
** Tags: ftbfs rls-nn-incoming
** Changed in: ufw (Ubuntu)
Status: New => Confirmed
** Changed in: ufw (Ubuntu)
Importance: Undecided => High
** Tags added: ftbfs rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status in ufw package in Ubuntu:
Confirmed
Bug description:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in
test_ufwcommand_parse
self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
==
ERROR: test_ufwcommand_rule_get_command
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
Test UFWCommand(Route)Rule.get_command()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in
test_ufwcommand_rule_get_command
self.assertEquals(len(errors), 0,
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
--
Ran 24 tests in 7.584s
FAILED (errors=9)
test_skeleton
test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
Test example dummy test ... ok
--
Ran 1 test in 0.000s
OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/2051540/+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 2051118] Re: DEP8 error on armhf
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/libseccomp/+git/libseccomp/+merge/459586 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2051118 Title: DEP8 error on armhf Status in libseccomp package in Ubuntu: In Progress Bug description: Version 2.5.4-2 introduced this change in d/t/control: libseccomp (2.5.4-2) unstable; urgency=medium * Fix watch file. (Closes: #1050659) * Dynamically skip autopkgtests when the test runner already applies seccomp restrictions. - Drop isolation-machine restriction. -Restrictions: isolation-machine, allow-stderr +Restrictions: skippable, allow-stderr This made the test run in Ubuntu again on armhf, where we use a lxd container (it wasn't running previously). This change is relying on this check in d/t/common: if ! grep -q -E '^Seccomp:[[:blank:]]+0$' /proc/self/status; then echo "Skipping autpkgptest as the test environment already applies a seccomp filter" exit 77 fi In Debian, where they also use containers, the testsuite-live-python3 test is skipped correctly, but in Ubuntu, it is run and fails[1] with timeout limit: 541s live 541s ./regression: line 253: cd: /tmp/autopkgtest.X55y55/autopkgtest_tmp/tests/../src/python/build/lib.*: No such file or directory 10468s autopkgtest [01:49:37]: kill with SIGTERM did not work sending SIGKILL 1. https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/libs/libseccomp/20231225_015646_12139@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/2051118/+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 2049628] Re: Persistent Audio Issues on Dell Vostro 3400 Running Ubuntu 22.04.3 LTS
UPDATE 29-01-2024 After the latest Linux kernel update to "6.5.0-15-generic." Following the update, I observed a significant reduction in crackling sound (approximately 80%) after disabling C-states from the BIOS. However, this improvement came at the cost of higher CPU temperatures, with the fan constantly running. Conversely, with C-states enabled, the crackling sound occurs only when the fan starts working. Additionally, I am still encountering the "Dummy Output" audio issue consistently on a fresh start, necessitating a reboot to resolve. -- 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/2049628 Title: Persistent Audio Issues on Dell Vostro 3400 Running Ubuntu 22.04.3 LTS Status in pulseaudio package in Ubuntu: New Bug description: Since the last three weeks' updates, I have encountered several challenges with the audio functionality on my system. Primarily, upon starting my laptop, the audio often fails to work, displaying "Dummy Output." To resolve this, I find myself needing to restart the laptop two or three times before the audio becomes functional. Even when the audio is working, I've noticed a recurring issue where, after playing video or audio for approximately 2-3 minutes, the sound starts crackling and buzzing. The intensity of these distortions gradually increases, resembling the static interference on a radio station with a weak signal. This issue persists even when using 3.5mm headphones, requiring the use of a USB headset or Bluetooth headphones to enjoy distortion-free audio. Furthermore, I have observed that, regardless of the Ubuntu version (ranging from 22.04 to 22.04.3), I face difficulties changing the microphone output settings when an external audio peripheral, such as a USB headset, 3.5mm headphones, or Bluetooth headphones, is connected. The OS appears to exclusively utilize the microphone from the connected peripheral, making it impossible to switch to the laptop's built-in microphone. For your reference, here are the specifications of my laptop and the Ubuntu version I am currently using: Laptop: Dell Vostro 3400 CPU: 11th Gen Intel i5-1135G7 GPU: Intel TigerLake-LP GT2 Iris Xe Memory: 2490MiB / 19720MiB Resolution: 1920x1080 OS: Ubuntu 22.04.3 LTS x86_64 Kernel: 6.5.0-14-generic DE: GNOME 42.9 Shell: bash 5.1.16 Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42 I want to emphasize that I receive updates from the Tunisia Ubuntu server. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galxy-a10 1404 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 14:56:16 2024 InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2023 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.1 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23: dmi.product.family: Vostro dmi.product.name: Vostro 3400 dmi.product.sku: 0A23 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2049628/+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 2051506] Re: apparmor blocks libnss-resolve socket
I forgot to add, the apparmor log contains this as the error f.ex when using
`ping`:
`apparmor="ALLOWED" operation="connect" info="Failed name lookup - disconnected
path" error=-13 profile="ping" name="run/systemd/resolve/io.systemd.Resolve"
pid=2450 comm="ping" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=102`
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2051506
Title:
apparmor blocks libnss-resolve socket
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
Usage of `libnss-resolve` socket is blocked by apparmor.
Evidence:
- Install `libnss-resolve`
- Set /etc/nsswitch.conf to have `hosts: files resolve`
- Try resolving anything, it fails
`strace` of affected process reveals:
`connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/resolve/io.systemd.Resolve"}, 42) = -1 EACCES
(Permission denied)`
Run `aa-disable` on affected profile and `strace` it again, it works:
`connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/resolve/io.systemd.Resolve"}, 42) = 0`
Note that using `aa-complain` DOES NOT work.
p.s. has this ever worked?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051506/+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 2051512] [NEW] apport ftbfs with Python 3.12 as the default
Public bug reported: debian/rules override_dh_auto_test make[1]: Entering directory '/<>' tests/run-linters --errors-only Skipping mypy tests, mypy is not installed Running pylint... * Module apport-retrace bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment (used-before-assignment) make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 ** Affects: apport (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-nn-incoming ** Changed in: apport (Ubuntu) Status: New => Confirmed ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2051512 Title: apport ftbfs with Python 3.12 as the default Status in apport package in Ubuntu: Confirmed Bug description: debian/rules override_dh_auto_test make[1]: Entering directory '/<>' tests/run-linters --errors-only Skipping mypy tests, mypy is not installed Running pylint... * Module apport-retrace bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment (used-before-assignment) make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2051512/+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 2051506] Re: apparmor blocks libnss-resolve socket
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2051506
Title:
apparmor blocks libnss-resolve socket
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
Usage of `libnss-resolve` socket is blocked by apparmor.
Evidence:
- Install `libnss-resolve`
- Set /etc/nsswitch.conf to have `hosts: files resolve`
- Try resolving anything, it fails
`strace` of affected process reveals:
`connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/resolve/io.systemd.Resolve"}, 42) = -1 EACCES
(Permission denied)`
Run `aa-disable` on affected profile and `strace` it again, it works:
`connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/resolve/io.systemd.Resolve"}, 42) = 0`
Note that using `aa-complain` DOES NOT work.
p.s. has this ever worked?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051506/+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 2051506] [NEW] apparmor blocks libnss-resolve socket
Public bug reported:
Usage of `libnss-resolve` socket is blocked by apparmor.
Evidence:
- Install `libnss-resolve`
- Set /etc/nsswitch.conf to have `hosts: files resolve`
- Try resolving anything, it fails
`strace` of affected process reveals:
`connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/resolve/io.systemd.Resolve"}, 42) = -1 EACCES
(Permission denied)`
Run `aa-disable` on affected profile and `strace` it again, it works:
`connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/resolve/io.systemd.Resolve"}, 42) = 0`
Note that using `aa-complain` DOES NOT work.
p.s. has this ever worked?
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: apparmor libnss-resolve systemd-resolved
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2051506
Title:
apparmor blocks libnss-resolve socket
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
Usage of `libnss-resolve` socket is blocked by apparmor.
Evidence:
- Install `libnss-resolve`
- Set /etc/nsswitch.conf to have `hosts: files resolve`
- Try resolving anything, it fails
`strace` of affected process reveals:
`connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/resolve/io.systemd.Resolve"}, 42) = -1 EACCES
(Permission denied)`
Run `aa-disable` on affected profile and `strace` it again, it works:
`connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/resolve/io.systemd.Resolve"}, 42) = 0`
Note that using `aa-complain` DOES NOT work.
p.s. has this ever worked?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051506/+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 420963] Re: file command reports incorrect mime type for mkv files
Fixed in Trusty+ ** Changed in: file (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/420963 Title: file command reports incorrect mime type for mkv files Status in file package in Ubuntu: Fix Released Bug description: Binary package hint: file libmagic1-4.26-2ubuntu4 running "file -i" on an mkv file (matroska video) results in "application/octet-stream" for the mime type. While not technically inaccurate, the generally accepted type for this filetype at the moment is "video/x-matroska" which can be evidenced by looking in /etc/mime.types, where it's already defined this way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/420963/+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 348139] Re: netstat --numeric-ports also shows hosts only in numeric format
Fix landed in Bionic but Trusty and Xenial didn't get it. I can't check the ESM apps without jumping through hoops. ** Tags removed: jaunty natty needs-upstream-report precise ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/348139 Title: netstat --numeric-ports also shows hosts only in numeric format Status in net-tools package in Ubuntu: Won't Fix Status in net-tools package in Debian: New Bug description: Binary package hint: net-tools Output from 'lsb_release -rd' Description:Ubuntu jaunty (development branch) Release:9.04 According to the man page of netstat, netstat --numeric-ports "shows numerical port numbers but does not affect the resolution of host or user names". In reality, this option also leads to a ip-address display of hosts (which is wrong, unwanted and different from previous versions). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/348139/+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
