[Touch-packages] [Bug 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
I was able to get something working on my win 11 i9-13900H discrete RTX2000 laptop. I used: mks.enable3d = "TRUE" mks.enableDX12Renderer = "TRUE" mks.enableDX11Renderer = "FALSE" mks.dx12.vendorID = "0x17AA" and I also had to do: settings->system->dislay->graphics entries for both vmware.exe and vmware-vmx.exe (its in a subdirectory) Both entries specify that vmware must run only on RTX2000 and not the cpu GPU. Still seeing MESA: error: ZINK: failed to choose pdev glx: failed to create drisw screen but that might be known? I dont think linux will be stable until you back off mesa to not have that error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Confirmed Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
Also tried virtualbox this morning on a different win 11 machine with an nvidia laptop gpu and same thing. No 3D acceleration is not stable on vmware (crashes after a while) With 3D acceleration black screens really fast on vmware and virtualbox (which uses the vmware driver by default) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
Microsoft Windows [Version 10.0.22631.3447] Processor AMD Ryzen 7 3700X 8-Core Processor, 3600 Mhz, 8 Core(s), 16 Logical Processor(s) System ModelX570 AORUS PRO WIFI RTX 2070 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
vmware 17.5 win 11 not fixed with todays iso. mesa is 24.0.5. Can see gui without enable 3d acceleration, but black screen and have to task manager kill with 3d acceleration. rtx 2070 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2049988] Re: Latest kernel kills wifi.
I think Connman is the culprit? ** Package changed: network-manager (Ubuntu) => connman -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2049988 Title: Latest kernel kills wifi. Status in Connection Manager: New Bug description: New kernel 6.0.5-14 boot up system does not recognize built in wifi adapter. When I drop to last kernel install wifi works fine. HP Pavillion With intel core I7 chip. Output of lshow --C network: *-network description: Wireless interface product: MT7921 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: b4:8c:9d:28:0e:cb width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=mt7921e driverversion=6.2.0-39-generic firmware=01-20220209150915 ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 memory:601210-60121f memory:601220-6012203fff memory:6012204000-6012204fff --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick2379 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-15 (432 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Pavilion Laptop 15-eg2xxx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/08/2023 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 89F7 dmi.board.vendor: HP dmi.board.version: 14.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.27 dmi.modalias: dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg2xxx dmi.product.sku: 6W540UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/connman/+bug/2049988/+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 2049988] Re: Latest kernel kills wifi.
Any news on this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2049988 Title: Latest kernel kills wifi. Status in network-manager package in Ubuntu: New Bug description: New kernel 6.0.5-14 boot up system does not recognize built in wifi adapter. When I drop to last kernel install wifi works fine. HP Pavillion With intel core I7 chip. Output of lshow --C network: *-network description: Wireless interface product: MT7921 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: b4:8c:9d:28:0e:cb width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=mt7921e driverversion=6.2.0-39-generic firmware=01-20220209150915 ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 memory:601210-60121f memory:601220-6012203fff memory:6012204000-6012204fff --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick2379 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-15 (432 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Pavilion Laptop 15-eg2xxx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/08/2023 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 89F7 dmi.board.vendor: HP dmi.board.version: 14.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.27 dmi.modalias: dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg2xxx dmi.product.sku: 6W540UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+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 2058003] Re: Keine Freigabe
Nein die DAtei ist nicht im Papierkorb. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2058003 Title: Keine Freigabe Status in tzdata package in Ubuntu: Incomplete Bug description: Wenn ich eine grosse Datei in Thunar oder Nautilus lösche wird es auf die Partition nicht um den Anteil gelöscht. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058003/+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 2058829] [NEW] Extreme low audio when using headphones
Public bug reported: The laptop audio works fine, but when I plug a headphone it seems that there is no audio. If I turn on overamplification it is possible to hear some low volume sound. So, the audio is actually there, it is just extremely low. I tried multiple things that I found only but none seems to work. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.8.1-060801-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 15:21:27 2024 InstallationDate: Installed on 2024-01-20 (64 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: LENOVO 83AW PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to noble on 2024-03-10 (13 days ago) dmi.bios.date: 09/01/2023 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: MLCN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Slim Pro 7 14APH8 dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrMLCN23WW:bd09/01/2023:br1.23:efr1.23:svnLENOVO:pn83AW:pvrLenovoSlimPro714APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoSlimPro714APH8:skuLENOVO_MT_83AW_BU_idea_FM_SlimPro714APH8: dmi.product.family: Slim Pro 7 14APH8 dmi.product.name: 83AW dmi.product.sku: LENOVO_MT_83AW_BU_idea_FM_Slim Pro 7 14APH8 dmi.product.version: Lenovo Slim Pro 7 14APH8 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2058829 Title: Extreme low audio when using headphones Status in alsa-driver package in Ubuntu: New Bug description: The laptop audio works fine, but when I plug a headphone it seems that there is no audio. If I turn on overamplification it is possible to hear some low volume sound. So, the audio is actually there, it is just extremely low. I tried multiple things that I found only but none seems to work. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.8.1-060801-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 15:21:27 2024 InstallationDate: Installed on 2024-01-20 (64 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: LENOVO 83AW PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to noble on 2024-03-10 (13 days ago) dmi.bios.date: 09/01/2023 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: MLCN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Slim Pro 7 14APH8 dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrMLCN23WW:bd09/01/2023:br1.23:efr1.23:svnLENOVO:pn83AW:pvrLenovoSlimPro714APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoSlimPro714APH8:skuLENOVO_MT_83AW_BU_idea_FM_SlimPro714APH8: dmi.product.family: Slim Pro 7 14APH8 dmi.product.name: 83AW dmi.product.sku: LENOVO_MT_83AW_BU_idea_FM_Slim Pro 7 14APH8 dmi.product.version: Lenovo Slim Pro 7 14APH8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2058829/+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 2058003] [NEW] Keine Freigabe
Public bug reported: Wenn ich eine grosse Datei in Thunar oder Nautilus lösche wird es auf die Partition nicht um den Anteil gelöscht. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2058003 Title: Keine Freigabe Status in tzdata package in Ubuntu: New Bug description: Wenn ich eine grosse Datei in Thunar oder Nautilus lösche wird es auf die Partition nicht um den Anteil gelöscht. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058003/+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 2054609] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2054609/+attachment/5749433/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-02-25 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 Tags: wayland-session jammy third-party-packages Uname: Linux 5.15.0-97-fips x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+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 2054609] Re: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1
apport information ** Tags added: apport-collected third-party-packages wayland-session ** Description changed: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.3 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2024-02-25 (0 days ago) + InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) + NtpStatus: ntpq: read: Connection refused + Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 + PackageArchitecture: amd64 + ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 + Tags: wayland-session jammy third-party-packages + Uname: Linux 5.15.0-97-fips x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: ".etc.apparmor.d.usr.sbin.ntpd.txt" https://bugs.launchpad.net/bugs/2054609/+attachment/5749430/+files/.etc.apparmor.d.usr.sbin.ntpd.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-02-25 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 Tags: wayland-session jammy third-party-packages Uname: Linux 5.15.0-97-fips x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 2054609] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/2054609/+attachment/5749432/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-02-25 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 Tags: wayland-session jammy third-party-packages Uname: Linux 5.15.0-97-fips x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+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 2054609] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2054609/+attachment/5749431/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-02-25 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 Tags: wayland-session jammy third-party-packages Uname: Linux 5.15.0-97-fips x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+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 2054861] [NEW] suspend-target and systemd-suspend.service hang on resume and blocks shutdown/reboot
Public bug reported:
This happens only after I connect my Toshiba FireTV via HDMI. I don't need to
be using the TV. If I have connected TV just once it is enough to trigger this
bug. Laptop goes to sleep just fine but when it wakes up from sleep I see 5
services when I execute
$ systemctl list-jobs
JOB UNIT TYPE STATE
7348 nvidia-resume.servicestart waiting
7236 suspend.target start waiting
7346 grub-common.service start waiting
7237 systemd-suspend.service start running
7241 grub-initrd-fallback.service start waiting
In this state, I have to cancel suspend-target which in turn cancels
7346 grub-common.service start waiting
7237 systemd-suspend.service start running
7241 grub-initrd-fallback.service start waiting
Then, I have to cancel cancelling systemd-suspend.service which cancels
7348 nvidia-resume.servicestart waiting
I use the laptop without issues but then if I need to shut it down or
reboot, system gets stuck after logging out of X. I end up doing a
REISUB.
This only happens if I connect to TV via HDMI.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6.1
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Fri Feb 23 19:32:08 2024
InstallationDate: Installed on 2023-11-04 (112 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash
amd_pstate=passive vt.handoff=7
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4:
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: Upgraded to mantic on 2023-12-10 (75 days ago)
dmi.bios.date: 12/28/2023
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN41WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.41
dmi.modalias:
dmi:bvnLENOVO:bvrM3CN41WW:bd12/28/2023:br1.41:efr1.41:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
dmi.product.family: Legion Slim 5 16APH8
dmi.product.name: 82Y9
dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
dmi.product.version: Legion Slim 5 16APH8
dmi.sys.vendor: LENOVO
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2054861
Title:
suspend-target and systemd-suspend.service hang on resume and blocks
shutdown/reboot
Status in systemd package in Ubuntu:
New
Bug description:
This happens only after I connect my Toshiba FireTV via HDMI. I don't need to
be using the TV. If I have connected TV just once it is enough to trigger this
bug. Laptop goes to sleep just fine but when it wakes up from sleep I see 5
services when I execute
$ systemctl list-jobs
JOB UNIT TYPE STATE
7348 nvidia-resume.servicestart waiting
7236 suspend.target start waiting
7346 grub-common.service start waiting
7237 systemd-suspend.service start running
7241 grub-initrd-fallback.service start waiting
In this state, I have to cancel suspend-target which in turn cancels
7346 grub-common.service start waiting
7237 systemd-suspend.service start running
7241 grub-initrd-fallback.service start waiting
Then, I have to cancel cancelling systemd-suspend.service which cancels
7348 nvidia-resume.servicestart waiting
I use the laptop without issues but then if I need to shut it down or
reboot, system gets stuck after logging out of X. I end up doing a
REISUB.
This only happens if I connect to TV via HDMI.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6.1
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Fri Feb 23 19:32:08 2024
InstallationDate:
[Touch-packages] [Bug 2054609] [NEW] package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1
Public bug reported: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: fips-updates jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+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 2049988] Re: Latest kernel kills wifi.
Any news on this bug? Latest patches did not affect it -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2049988 Title: Latest kernel kills wifi. Status in network-manager package in Ubuntu: New Bug description: New kernel 6.0.5-14 boot up system does not recognize built in wifi adapter. When I drop to last kernel install wifi works fine. HP Pavillion With intel core I7 chip. Output of lshow --C network: *-network description: Wireless interface product: MT7921 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: b4:8c:9d:28:0e:cb width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=mt7921e driverversion=6.2.0-39-generic firmware=01-20220209150915 ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 memory:601210-60121f memory:601220-6012203fff memory:6012204000-6012204fff --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick2379 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-15 (432 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Pavilion Laptop 15-eg2xxx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/08/2023 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 89F7 dmi.board.vendor: HP dmi.board.version: 14.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.27 dmi.modalias: dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg2xxx dmi.product.sku: 6W540UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+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 2049988] Re: Latest kernel kills wifi.
Has anyone figured out a patch for this? there was an update today, which I applied. Did not change anything with new kernel, but now old version boots to airplane mode. I can get the wifi going on older kernel still. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2049988 Title: Latest kernel kills wifi. Status in network-manager package in Ubuntu: New Bug description: New kernel 6.0.5-14 boot up system does not recognize built in wifi adapter. When I drop to last kernel install wifi works fine. HP Pavillion With intel core I7 chip. Output of lshow --C network: *-network description: Wireless interface product: MT7921 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: b4:8c:9d:28:0e:cb width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=mt7921e driverversion=6.2.0-39-generic firmware=01-20220209150915 ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 memory:601210-60121f memory:601220-6012203fff memory:6012204000-6012204fff --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick2379 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-15 (432 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Pavilion Laptop 15-eg2xxx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/08/2023 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 89F7 dmi.board.vendor: HP dmi.board.version: 14.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.27 dmi.modalias: dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg2xxx dmi.product.sku: 6W540UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+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 2049988] Re: Latest kernel kills wifi.
Thank you for the reply. I had to apply the command twice. It gave me an error the first time. Report was sent ( I think) On 1/21/24 03:16, Chris Guiver wrote: > apport-collect 2049988 ** Package changed: linux (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2049988 Title: Latest kernel kills wifi. Status in network-manager package in Ubuntu: New Bug description: New kernel 6.0.5-14 boot up system does not recognize built in wifi adapter. When I drop to last kernel install wifi works fine. HP Pavillion With intel core I7 chip. Output of lshow --C network: *-network description: Wireless interface product: MT7921 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: b4:8c:9d:28:0e:cb width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=mt7921e driverversion=6.2.0-39-generic firmware=01-20220209150915 ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 memory:601210-60121f memory:601220-6012203fff memory:6012204000-6012204fff --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick2379 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-15 (432 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Pavilion Laptop 15-eg2xxx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/08/2023 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 89F7 dmi.board.vendor: HP dmi.board.version: 14.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.27 dmi.modalias: dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg2xxx dmi.product.sku: 6W540UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+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 2042587] Re: jammy's version breaks existing dhcp scripts with relay
Hello, and thank you, seems to fix the issue. I updated my jammy's to dsnmasq version 2.86-1.1ubuntu0.5, and tested with the same setup as I reported the original bug. Can confirm that the DHCP hook script now works exatly like it used to in focal, getting the correct IP address as an argument. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Fix Committed Bug description: [ Impact ] When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. This was fixed in 2.87, therefore making only jammy carry an affected package. [ Test Plan ] To easily test this on a single machine, a test script is being provided to setup networking and dnsmasq configuration. # Launch a jammy VM lxc launch ubuntu-daily:jammy j-dnsmasq-2042587 --vm # open a root shell in that VM. All subsequent commands must be executed as root in that VM lxc shell j-dnsmasq-2042587 # download test script wget https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5738174/+files/setup- and-server.sh # make it executable chmod +x setup-and-server.sh # install dnsmasq. Ignore the postinst error (because systemd-resolved is also running and there is a port conflict) apt update && apt install dnsmasq -y # run the setup script. It will configure things and start dnsmasq ready to be tested ./setup-and-server.sh # in another root session inside the vm (so run "lxc shell j-dnsmasq-2042587" in another terminal), run the proposed commands from the setup script (and press ctrl-c after the result is shown): No DHCP relay: ip netns exec client dhclient -d -v p2 The setup script should log an IP that is not a relay. For example: dnsmasq-dhcp: DHCPDISCOVER(p1) aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPOFFER(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587 ### IP = 192.168.47.150 ### With DHCP relay set to 192.168.47.9, IP should NOT be that address: ip netns exec client dhclient -d -v p2 -g 192.168.47.9 With the affected dnsmasq package, we will see an error: dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587 ### IP = 192.168.47.9 TEST FAILED ### The error is that the obtained IP is that of the dhcp relay (provided via the -g option). With the fixed dnsmasq package, "TEST FAILED" must not appear, and the IP should not be that of the provided dhcp relay. [ Where problems could occur ] If the fix is incorrect, it would mean the dhcp-script would get an incorrect IP again, or perhaps we could have crashes in dnsmasq when dealing with buffers and pointers if the dhcp-script option is in use. This fix was committed upstream a few months after the bug was introduced, so it took a while to be noticed. [ Other Info ] Not at this time. [ Original description ] When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 2047743] Re: Sound glitches while moving window and talking on discord
I think the bug is probably related to KDE itself, but I dont know how should I report that -- 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/2047743 Title: Sound glitches while moving window and talking on discord Status in pulseaudio package in Ubuntu: New Bug description: while being on discord call, moving any window causes the sound to be fragmented, choppy, unusable. That probably happens if system is after sleep cycle. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 Uname: Linux 6.6.1-060601-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Dec 31 04:36:50 2023 InstallationDate: Installed on 2023-07-07 (177 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-04 (56 days ago) dmi.bios.date: 07/28/2023 dmi.bios.release: 12.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1220 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790M-PLUS D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1220:bd07/28/2023:br12.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790M-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2047743/+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 2047743] [NEW] Sound glitches while moving window and talking on discord
Public bug reported: while being on discord call, moving any window causes the sound to be fragmented, choppy, unusable. That probably happens if system is after sleep cycle. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 Uname: Linux 6.6.1-060601-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Dec 31 04:36:50 2023 InstallationDate: Installed on 2023-07-07 (177 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-04 (56 days ago) dmi.bios.date: 07/28/2023 dmi.bios.release: 12.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1220 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790M-PLUS D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1220:bd07/28/2023:br12.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790M-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2047743 Title: Sound glitches while moving window and talking on discord Status in pulseaudio package in Ubuntu: New Bug description: while being on discord call, moving any window causes the sound to be fragmented, choppy, unusable. That probably happens if system is after sleep cycle. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 Uname: Linux 6.6.1-060601-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Dec 31 04:36:50 2023 InstallationDate: Installed on 2023-07-07 (177 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-04 (56 days ago) dmi.bios.date: 07/28/2023 dmi.bios.release: 12.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1220 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790M-PLUS D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1220:bd07/28/2023:br12.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790M-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2047743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
(In reply to Gergo K from comment #794) > (In reply to m from comment #792) > > I'm on 6.6.4 on a Lenovo Yoga S940-14IIL > > > > cat /sys/class/sound/hwC1D0/subsystem_id 0x17aa3819 > > > > Same subsystem_id as for Lenovo 13s Gen2 ITL > > (https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_realtek. > > c#L10193) > > > > Sound works, but it is high-pitched since the base is missing. > > The C940 also has alc298 and tas2770. > Please try this: > sudo nano /etc/modprobe.d/alsa-base.conf > > add this line: > options snd-hda-intel model=17aa:3818 > > save: > ctrl+o ctrl+x > > sudo reboot The file didn't exist and therefore was empty. I added the line and saved the file. There was no change after rebooting. I still get sound, but the same as before, only high-pitched with no base. Does there need to be something additional in the file or some other configuration? Is there some configuration to enable the speakers that give the base? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
I'm on 6.6.4 on a Lenovo Yoga S940-14IIL cat /sys/class/sound/hwC1D0/subsystem_id 0x17aa3819 Same subsystem_id as for Lenovo 13s Gen2 ITL (https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_realtek.c#L10193) Sound works, but it is high-pitched since the base is missing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046224] [NEW] Resolutions lower than max results in corrupted screen
Public bug reported:
Upgrading from 23.04 to 23.10 resulted in corrupt screen when switching
to lower resolutions. Only maximum resolution works.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-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: MATE
Date: Tue Dec 12 01:21:01 2023
DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2) (prog-if
00 [VGA controller])
Subsystem: Lenovo Phoenix [17aa:3c92]
InstallationDate: Installed on 2023-11-04 (38 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
dmi.bios.date: 06/16/2023
dmi.bios.release: 1.34
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.34
dmi.modalias:
dmi:bvnLENOVO:bvrM3CN34WW:bd06/16/2023:br1.34:efr1.34:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
dmi.product.family: Legion Slim 5 16APH8
dmi.product.name: 82Y9
dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
dmi.product.version: Legion Slim 5 16APH8
dmi.sys.vendor: LENOVO
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.1
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 corruption mantic ubuntu
** Attachment added: "corrupt-screen.jpg"
https://bugs.launchpad.net/bugs/2046224/+attachment/5728569/+files/corrupt-screen.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2046224
Title:
Resolutions lower than max results in corrupted screen
Status in xorg package in Ubuntu:
New
Bug description:
Upgrading from 23.04 to 23.10 resulted in corrupt screen when
switching to lower resolutions. Only maximum resolution works.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-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: MATE
Date: Tue Dec 12 01:21:01 2023
DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Phoenix [17aa:3c92]
InstallationDate: Installed on 2023-11-04 (38 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
dmi.bios.date: 06/16/2023
dmi.bios.release: 1.34
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.34
dmi.modalias:
[Touch-packages] [Bug 2045907] [NEW] GtkFileChooserDialog hangs on large folder with 300000 files
Public bug reported: when I paste filename into the location bar (Ctrl+L) the file chooser hangs. The file happens to be in a folder with 30 other files and GtkFileChooserDialog tries to offer a filename typing suggestion dropdown which is slow and eventually crashes. When I then kill chrome or firefox then wayland session gets logouted. Ubuntu version is 23.10 ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2045907 Title: GtkFileChooserDialog hangs on large folder with 30 files Status in gtk+3.0 package in Ubuntu: New Bug description: when I paste filename into the location bar (Ctrl+L) the file chooser hangs. The file happens to be in a folder with 30 other files and GtkFileChooserDialog tries to offer a filename typing suggestion dropdown which is slow and eventually crashes. When I then kill chrome or firefox then wayland session gets logouted. Ubuntu version is 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2045907/+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 2042587] Re: jammy's version breaks existing dhcp scripts with relay
..also, apologies for all the typos I managed to place there. Step 7 was meant to say "repeat steps 4 and 5" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: Incomplete Bug description: When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+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 2042587] Re: jammy's version breaks existing dhcp scripts with relay
I'm so sorry this is so complex, but I couldn't figure out any simpler way to reproduce as they components involved do network configuration. Anyway, please find attached a docker compose file and related dnsmasq configurations (mapped automatically in that compose file) that helps in the reproduction by setting up two different dhcp servers based on dnsmasq (focal and jammy) and a machine that can be used to request a dhcp address. To reproduce the bug: 1) first install everything needed by running docker-compose up -d 2) wait until everything has been installed, check for example that the output of has something from all 3 containers and is not getting any more lines docker-compose logs --follow 3) stop jammy version of the server with docker-compose stop jammy-server 4) get inside client machine to run dhclient. Run it first without fake relay address, then with one (to trigger the DHCP relay behaviour in dnsmasq) docker-compose exec client bash dhclient -d -v (ctrl-c after a while) dhclient -d -v -g 192.168.0.10 (ctrl-c after a while) 5) observe server's log dnsmasq-script-sample-focal-server-1 | dnsmasq-dhcp: DHCPREQUEST(eth0) 192.168.0.3 02:42:c0:a8:00:04 dnsmasq-script-sample-focal-server-1 | dnsmasq-dhcp: DHCPACK(eth0) 192.168.0.3 02:42:c0:a8:00:04 5a49beb3cd53 dnsmasq-script-sample-focal-server-1 | hello from dhcp hook script, IP argument is 192.168.0.3 dnsmasq-script-sample-focal-server-1 | dnsmasq-dhcp: DHCPREQUEST(eth0) 192.168.0.3 02:42:c0:a8:00:04 dnsmasq-script-sample-focal-server-1 | dnsmasq-dhcp: DHCPACK(eth0) 192.168.0.3 02:42:c0:a8:00:04 5a49beb3cd53 dnsmasq-script-sample-focal-server-1 | hello from dhcp hook script, IP argument is 192.168.0.3 6) now stop focal version of server and start jammy: docker-compose stop focal-server docker-compose start jammy-server 7) repeat steps 5 and 6, this time the output has the wroing ip in the 2nd hook script invocation dnsmasq-script-sample-jammy-server-1 | dnsmasq-dhcp: DHCPREQUEST(eth0) 192.168.0.1 02:42:c0:a8:00:04 dnsmasq-script-sample-jammy-server-1 | dnsmasq-dhcp: DHCPACK(eth0) 192.168.0.1 02:42:c0:a8:00:04 5a49beb3cd53 dnsmasq-script-sample-jammy-server-1 | hello from dhcp hook script, IP argument is 192.168.0.1 dnsmasq-script-sample-jammy-server-1 | dnsmasq-dhcp: DHCPREQUEST(eth0) 192.168.0.1 02:42:c0:a8:00:04 dnsmasq-script-sample-jammy-server-1 | dnsmasq-dhcp: DHCPACK(eth0) 192.168.0.1 02:42:c0:a8:00:04 5a49beb3cd53 dnsmasq-script-sample-jammy-server-1 | hello from dhcp hook script, IP argument is 192.168.0.10 ** Attachment added: "archive containing docker-compose.yml and needed configuration files" https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5716459/+files/sample.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: Incomplete Bug description: When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+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 2042729] [NEW] Xorg freeze
Public bug reported:
Computer unresponsive after closing laptop screen and reopening. GDM
screen does not appear to login, just see contents of the X session
before i closed the lid. mouse moves and hardware buttons (mute, caps
lock etc) are responsive with LEDs. Have to hard reboot to login and use
computer
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
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: Sat Nov 4 15:33:14 2023
DistUpgraded: 2023-11-02 15:19:38,871 DEBUG 'libkf5itemviews5' scheduled for
remove but not safe to remove, skipping
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00
[VGA controller])
Subsystem: Lenovo CoffeeLake-H GT2 [UHD Graphics 630] [17aa:229f]
NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
InstallationDate: Installed on 2023-05-24 (164 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=UUID=45e4e3f8-045a-4651-bd83-6087eca44175 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-02 (2 days ago)
dmi.bios.date: 09/19/2023
dmi.bios.release: 1.48
dmi.bios.vendor: LENOVO
dmi.bios.version: N2OET61W (1.48 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QV00BRUK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.22
dmi.modalias:
dmi:bvnLENOVO:bvrN2OET61W(1.48):bd09/19/2023:br1.48:efr1.22:svnLENOVO:pn20QV00BRUK:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00BRUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
dmi.product.family: ThinkPad X1 Extreme 2nd
dmi.product.name: 20QV00BRUK
dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
dmi.product.version: ThinkPad X1 Extreme 2nd
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
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 freeze mantic 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/2042729
Title:
Xorg freeze
Status in xorg package in Ubuntu:
New
Bug description:
Computer unresponsive after closing laptop screen and reopening. GDM
screen does not appear to login, just see contents of the X session
before i closed the lid. mouse moves and hardware buttons (mute, caps
lock etc) are responsive with LEDs. Have to hard reboot to login and
use computer
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
[Touch-packages] [Bug 2042587] [NEW] jammy's version breaks existing dhcp scripts with relay
Public bug reported: When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp-script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: New Bug description: When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+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 228077] Re: libgtk2 immodules has cedilla disabled in en locales
*** This bug is a duplicate of bug 518056 *** https://bugs.launchpad.net/bugs/518056 I was on 18.04 and that was not an issue for me. Using US intl. alt. keyboard I could always get ç (cedilha). Now that I've upgrade to 23.04, this problem came back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/228077 Title: libgtk2 immodules has cedilla disabled in en locales Status in gnome-control-center: Confirmed Status in GTK+: Invalid Status in gnome-control-center package in Ubuntu: Triaged Status in gtk+2.0 package in Ubuntu: Invalid Status in gnome-control-center package in Fedora: Won't Fix Bug description: Binary package hint: libgtk2.0-0 philsf@philsf-laptop:~$ lsb_release -rd Description: Ubuntu 8.04 Release: 8.04 philsf@philsf-laptop:~$ apt-cache policy libgtk2.0-0 libgtk2.0-0: Installed: 2.12.9-3ubuntu3 One can't use dead keys to input a c+cedilla in en_US (probably other en_* locales). I had this on Gutsy. Now in Hardy, I thought I should report, since it's annoying, and the fix is documented. Steps to reproduce: - enable deadkeys - Open gnome-terminal (or firefox) and enter ' + c What you should get: ç What you do get: ć Fix (got from http://ubuntuforums.org/showthread.php?p=3652628 ): Edit /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules, and include ":en" in the cedilla line 6c6 < "cedilla" "Cedilla" "gtk20" "/usr/share/locale" "az:ca:co:fr:gv:oc:pt:sq:tr:wa" --- > "cedilla" "Cedilla" "gtk20" "/usr/share/locale" "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/228077/+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 1641230] Re: package linux-image-4.4.0-43-generic 4.4.0-43.63 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 due to /usr/s
I shut down the VM and used a live ISO to take a look at the filesystem. You were correct - there is an /etc/ld.so.preload which points to /lib/libgcwrap.so. There is also a /usr/lib/libgcwrap.so copy. These files were marked as immutable and were not visible from the booted system. I took a look at the cron configurations and found the root user had an entry for "perfcc". Looking this up, perfcc/perfctl is a crypto-miner malware. Thanks for all your help in troubleshooting this. I hope it clarifies for someone what may be afoot if they find libgcwrap present on their system; there was nothing available on the popular search engines about it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1641230 Title: package linux-image-4.4.0-43-generic 4.4.0-43.63 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 due to /usr/share/initramfs-tools/hooks/fsck failed with return 1 Status in e2fsprogs package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Do you want to continue? [Y/n] y (Reading database ... 254369 files and directories currently installed.) Removing linux-image-extra-4.4.0-43-generic (4.4.0-43.63) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-43-generic /boot/vmlinuz-4.4.0-43-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-43-generic /boot/vmlinuz-4.4.0-43-generic Error! Your kernel headers for kernel 4.4.0-43-generic cannot be found. Please install the linux-headers-4.4.0-43-generic package, or use the --kernelsourcedir option to tell DKMS where it's located run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-43-generic /boot/vmlinuz-4.4.0-43-generic update-initramfs: Generating /boot/initrd.img-4.4.0-43-generic E: /usr/share/initramfs-tools/hooks/fsck failed with return 1. update-initramfs: failed for /boot/initrd.img-4.4.0-43-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-4.4.0-43-generic (--remove): subprocess installed post-removal script returned error exit status 1 Removing linux-image-extra-4.4.0-47-generic (4.4.0-47.68) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-47-generic /boot/vmlinuz-4.4.0-47-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-47-generic /boot/vmlinuz-4.4.0-47-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-47-generic /boot/vmlinuz-4.4.0-47-generic update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic E: /usr/share/initramfs-tools/hooks/fsck failed with return 1. update-initramfs: failed for /boot/initrd.img-4.4.0-47-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-4.4.0-47-generic (--remove): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-extra-4.4.0-43-generic linux-image-extra-4.4.0-47-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-43-generic 4.4.0-43.63 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pezhman1535 F pulseaudio Date: Fri Nov 11 21:03:09 2016 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=e8c76af0-04d5-4831-a401-a0911630111c InstallationDate: Installed on 2016-08-27 (76 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. S300CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=72d332d4-9180-442f-a032-8c1b612566ec ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.4.0-43-generic 4.4.0-43.63 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S300CA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S300CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10
[Touch-packages] [Bug 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio]
I realize that the conflict is probably intended and my issue is that vanilla-gnome-desktop relies on pulseaudio still. I'll create a separate bug, sorry. -- 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/2017196 Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire- alsa conflicts with pulseaudio] Status in pipewire package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required software appeared to have downloaded. Committing Changes operated to about 84% at which point the system crashed. It was necessary to re- initiate the upgrade procedure. This time, the upgrade proceeded to about 95% when an error notification appeared on the screen. Further upgrades were not attempted. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: pipewire-alsa (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 21 04:46:04 2023 ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64 InstallationDate: Installed on 2020-02-04 (1171 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: pipewire Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2017196/+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 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio]
I seem to hit the same dep issues on a freshly installed 23.04 system when trying to install vanilla-gnome-desktop. The following packages have unmet dependencies: pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be installed pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. -- 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/2017196 Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire- alsa conflicts with pulseaudio] Status in pipewire package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required software appeared to have downloaded. Committing Changes operated to about 84% at which point the system crashed. It was necessary to re- initiate the upgrade procedure. This time, the upgrade proceeded to about 95% when an error notification appeared on the screen. Further upgrades were not attempted. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: pipewire-alsa (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 21 04:46:04 2023 ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64 InstallationDate: Installed on 2020-02-04 (1171 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: pipewire Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2017196/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
what does that mean for me?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in cairo package in Ubuntu:
Triaged
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
will gtk4 come with 23.04?
Should I wait or just bite the bullet and reinstall (what a pain) as it
worked flawlessly on 22.04?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
would it be bad to enable developer updates / proposed kinetic updates?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
Very odd, I'm only using a scale of 1.25
** Attachment added: "125-scale.jpg"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004533/+attachment/5645548/+files/125-scale.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
I can also confirm that the problem persists after a fresh boot, turning
off 2 screens, and only using the main screen at 100% scale.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in gtk+3.0 package in Ubuntu:
Incomplete
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
attached
** Attachment added: "xrandr.txt"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004533/+attachment/5645339/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in gtk+3.0 package in Ubuntu:
Incomplete
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
Hi Daniel,
It worked flawlessly for about a year, and only started doing this
(immediately) after the update to 22.10. I used fractional scaling for
the past year as well with no issues.
I have already tried changing the resolution back to just plain 100% 4k
and it's the exact same with all kinds of instabilities and missing
icons.
Any other ideas?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in gtk+3.0 package in Ubuntu:
Incomplete
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004533/+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 2003569] [NEW] all kinds of graphic issues, cannot scale desktop properly, icons vanish but reappear temporarily when hovering over missing icon then text vanishes again.
Public bug reported: all kinds of graphic issues, cannot scale desktop properly, icons vanish but reappear temporarily when hovering over missing icon then text vanishes again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0b.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 20 12:17:19 2023 DistUpgraded: 2023-01-05 13:54:18,926 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:859b] InstallationDate: Installed on 2021-01-17 (733 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=c3541a51-e46f-4010-8668-6d2918b42e5e ro nvidia-drm.modeset=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-05 (14 days ago) dmi.bios.date: 04/26/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4201 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VIII DARK HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4201:bd04/26/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIDARKHERO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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 corruption kinetic possible-manual-nvidia-install 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/2003569 Title: all kinds of graphic issues, cannot scale desktop properly, icons vanish but reappear temporarily when hovering over missing icon then text vanishes again. Status in xorg package in Ubuntu: New Bug description: all kinds of graphic issues, cannot scale desktop properly, icons vanish but reappear temporarily when hovering over missing icon then text vanishes again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0b.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13]
[Touch-packages] [Bug 1998950] Re: GPU hang on Alder Lake laptop
I don't see this happening anymore as of the release of linux- image-5.19.0-28-generic. Neither the -28 nor the -29 kernel seem to cause this to happen anymore, so I suspect this can probably be closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 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/linux/+bug/1998950/+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 1998950] Re: GPU hang on Alder Lake laptop
Since there appears to be upstream patches in kernel 6.0 and Mesa 22.3.1 which fix this, perhaps it would be possible to backport those to the versions in Ubuntu 22.10? If not, would it at least be possible to upload such packages to Lunar so that there's an option which doesn't involve reinstalling the machine to go back to 22.04? Right now my machine is freezing multiple times per day and it would be really valuable to get those backports applied. I'm pretty sure this affects all Alder Lake-P GPUs on Kinetic, since the upstream bug report mentions multiple different hardware variants. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 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/linux/+bug/1998950/+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 1680087] Re: package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is different from other instances o
i strongly believe that this issue has been fixed with newer versions of libogg, as found from Ubuntu/focal onwards. i'm therefore closing this issue. if you still experience this problem, please ping me. ** Changed in: libogg (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libogg in Ubuntu. https://bugs.launchpad.net/bugs/1680087 Title: package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is different from other instances of package libogg0:i386 Status in libogg package in Ubuntu: Fix Released Bug description: Since I updated ubuntu 14.04 to 16.04, I can not use "apt-get install' Vous pouvez lancer « apt-get -f install » pour corriger ces problèmes : Les paquets suivants contiennent des dépendances non satisfaites : aptitude : Dépend: libcwidget3v5 mais ne sera pas installé gstreamer1.0-plugins-base:i386 : Dépend: libogg0:i386 (>= 1.0rc3) mais ne sera pas installé libflac8:i386 : Dépend: libogg0:i386 (>= 1.0rc3) mais ne sera pas installé libtheora0:i386 : Dépend: libogg0:i386 (>= 1.1.0) mais ne sera pas installé libvorbis0a:i386 : Dépend: libogg0:i386 (>= 1.1.0) mais ne sera pas installé E: Dépendances non satisfaites. Essayez « apt-get -f install » sans paquet When I follow the instruction 'apt-get -f install' : dpkg: erreur de traitement de l'archive /var/cache/apt/archives/libogg0_1.3.2-1_i386.deb (--unpack) : tentative de remplacement de « /usr/share/doc/libogg0/changelog.Debian.gz », qui est différent d'autres instances du paquet libogg0:i386 Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/libogg0_1.3.2-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libogg0 1.3.2-1 ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Apr 4 04:03:24 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu7 DuplicateSignature: package:libogg0:1.3.2-1 Unpacking libogg0:i386 (1.3.2-1) ... dpkg: error processing archive /var/cache/apt/archives/libogg0_1.3.2-1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is different from other instances of package libogg0:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is different from other instances of package libogg0:i386 InstallationDate: Installed on 2014-11-03 (884 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libogg Title: package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is different from other instances of package libogg0:i386 UpgradeStatus: Upgraded to xenial on 2017-04-03 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libogg/+bug/1680087/+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 1998950] [NEW] GPU hang on Alder Lake laptop
Public bug reported: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 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 freeze kinetic 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/1998950 Title: GPU hang on Alder Lake laptop Status in xorg package in Ubuntu: New Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature:
[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files
Thanks, uninstalling libcanberra-gtk-3-0 helped with this. (I'd only
installed it way back in the distant past to stop those stupid warnings
on the command line!)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1993869] Re: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04
You can close this. I did an upgrade from ubuntu 18.04 since I initially upgraded to 22.04 from this version, and openssh-server's sockets didn't break the install. If the error happened it's either related to the Ubuntu 18.04 install/image that was provided by my host or some freak corruption. If I had touched anything related to systemd's openssh-server but forgot about it, it would have been the service and a .d folder in /etc/systemd/system -> https://i.imgur.com/eTRBEmc.png I joined the dist-upgrade folder with the two ssh.service.d and ssh.socket.d folder and override files that were created during the upgrade. ** Attachment added: "dist-upgrade.zip" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+attachment/5627085/+files/dist-upgrade.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993869 Title: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04 Status in openssh package in Ubuntu: Incomplete Bug description: This is a bug report to separate the second issue that was reported in this bug report: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478 There's an issue after upgrading to 22.10 from 22.04 that prevents opensshd from listening to anything other than :::2. I already commented in the bug report I linked, so I'll just copy/paste and add some details. I guess. The issue is that after upgrading, sshd doesn't use the Listen port or ListenAddress config from the sshd_config file or any custom config file that was in the sshd_config.d drop in folder anymore. Other drop in settings from sshd.config.d seem to be applied normally, the issue seem to be only for IP binding and custom ports. If I change Accept=no by Accept=yes in ssh.socket and reloads the socket unit, I can start sshd on a different port and I can also bind the IP to something else than :: There's an issue still, an instance of sshd is still listening to :::22 that is not started by SSHD but by init. root@ubuntulocal:~# netstat -antp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd tcp 0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin tcp 0 272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts tcp6 0 0 :::22 :::* LISTEN 1/init If I reboot after changing this no to yes in ssh.socket does not survive a reboot and fails to load sshd with a "Failed to queue service startup job" error. Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Invalid argument Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 'resources'. I had to mask/stop the sshd.socket unit and create a custom sshd service in /etc/systemd/system to be able start sshd on a custom port and IP. chris@ubuntulocal:~$ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: active (running) since Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Until: Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 18899) Memory: 4.0K CPU: 418us CGroup: /system.slice/ssh.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+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 1993869] Re: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04
The machine that returned an openssh-server error and left me with a partially installed openssh-server package (dpkg IF flag) at the end of the upgrade process didn't have anything in ssh.socket.d, nor it had a ssh.socket.d folder in /etc/systemd/system/. The local machine I tested the upgrade on before trying on my live server had a file, override.conf, if I remember correctly, in /etc/systemd/system/ssh.socket.d. >I have done a jammy->kinetic upgrade using the Machine-1 sshd config that >you provided, and I do NOT see the errors that were shown in your apt term >log. Everything related to systemd was from the 22.04 install. The first and only time I ever touched anything related to openssh-server systemd service and socket units was two days ago after the 22.10 upgrade process returned that openssh-server error. I'll try to do a 22.04 -> 22.10 upgrade on my local machine later today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993869 Title: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04 Status in openssh package in Ubuntu: Incomplete Bug description: This is a bug report to separate the second issue that was reported in this bug report: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478 There's an issue after upgrading to 22.10 from 22.04 that prevents opensshd from listening to anything other than :::2. I already commented in the bug report I linked, so I'll just copy/paste and add some details. I guess. The issue is that after upgrading, sshd doesn't use the Listen port or ListenAddress config from the sshd_config file or any custom config file that was in the sshd_config.d drop in folder anymore. Other drop in settings from sshd.config.d seem to be applied normally, the issue seem to be only for IP binding and custom ports. If I change Accept=no by Accept=yes in ssh.socket and reloads the socket unit, I can start sshd on a different port and I can also bind the IP to something else than :: There's an issue still, an instance of sshd is still listening to :::22 that is not started by SSHD but by init. root@ubuntulocal:~# netstat -antp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd tcp 0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin tcp 0 272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts tcp6 0 0 :::22 :::* LISTEN 1/init If I reboot after changing this no to yes in ssh.socket does not survive a reboot and fails to load sshd with a "Failed to queue service startup job" error. Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Invalid argument Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 'resources'. I had to mask/stop the sshd.socket unit and create a custom sshd service in /etc/systemd/system to be able start sshd on a custom port and IP. chris@ubuntulocal:~$ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: active (running) since Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Until: Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 18899) Memory: 4.0K CPU: 418us CGroup: /system.slice/ssh.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+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 1993869] Re: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04
"My local machine is the one that refuses to boot" -> refused to start openssh-server at boot. I believe it happened because I didn't know ssh.service was disabled when I restarted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993869 Title: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04 Status in openssh package in Ubuntu: Incomplete Bug description: This is a bug report to separate the second issue that was reported in this bug report: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478 There's an issue after upgrading to 22.10 from 22.04 that prevents opensshd from listening to anything other than :::2. I already commented in the bug report I linked, so I'll just copy/paste and add some details. I guess. The issue is that after upgrading, sshd doesn't use the Listen port or ListenAddress config from the sshd_config file or any custom config file that was in the sshd_config.d drop in folder anymore. Other drop in settings from sshd.config.d seem to be applied normally, the issue seem to be only for IP binding and custom ports. If I change Accept=no by Accept=yes in ssh.socket and reloads the socket unit, I can start sshd on a different port and I can also bind the IP to something else than :: There's an issue still, an instance of sshd is still listening to :::22 that is not started by SSHD but by init. root@ubuntulocal:~# netstat -antp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd tcp 0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin tcp 0 272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts tcp6 0 0 :::22 :::* LISTEN 1/init If I reboot after changing this no to yes in ssh.socket does not survive a reboot and fails to load sshd with a "Failed to queue service startup job" error. Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Invalid argument Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 'resources'. I had to mask/stop the sshd.socket unit and create a custom sshd service in /etc/systemd/system to be able start sshd on a custom port and IP. chris@ubuntulocal:~$ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: active (running) since Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Until: Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 18899) Memory: 4.0K CPU: 418us CGroup: /system.slice/ssh.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+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 1993869] Re: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04
The whatever caused this "> Failed to restart ssh.socket: Unit ssh.socket has a bad unit file setting." is related to the 22.04 install. The openSSH-server on machine-1 only has customs ports in the sshd_config and the rest of the config in the sshd_config.d drop in folder. Everything related to systemd was never touched. I joined the sshd config from machine 1. My local machine is the one that refuses to boot after I change accept=no to yes in ssh.socket, systemctl daemon-reload and reboot. I tried to change no to yes to reflect 22.04 settings as I missed the news and I didn't Ubuntu uses socket to save some 9MB of memory(...) when openssh-server isn't used. I didn't try on my live server but I'm pretty sure if I tried the result would be the same. ** Attachment added: "sshd_config-machine1.zip" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+attachment/5626572/+files/sshd_config-machine1.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993869 Title: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04 Status in openssh package in Ubuntu: Incomplete Bug description: This is a bug report to separate the second issue that was reported in this bug report: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478 There's an issue after upgrading to 22.10 from 22.04 that prevents opensshd from listening to anything other than :::2. I already commented in the bug report I linked, so I'll just copy/paste and add some details. I guess. The issue is that after upgrading, sshd doesn't use the Listen port or ListenAddress config from the sshd_config file or any custom config file that was in the sshd_config.d drop in folder anymore. Other drop in settings from sshd.config.d seem to be applied normally, the issue seem to be only for IP binding and custom ports. If I change Accept=no by Accept=yes in ssh.socket and reloads the socket unit, I can start sshd on a different port and I can also bind the IP to something else than :: There's an issue still, an instance of sshd is still listening to :::22 that is not started by SSHD but by init. root@ubuntulocal:~# netstat -antp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd tcp 0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin tcp 0 272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts tcp6 0 0 :::22 :::* LISTEN 1/init If I reboot after changing this no to yes in ssh.socket does not survive a reboot and fails to load sshd with a "Failed to queue service startup job" error. Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Invalid argument Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 'resources'. I had to mask/stop the sshd.socket unit and create a custom sshd service in /etc/systemd/system to be able start sshd on a custom port and IP. chris@ubuntulocal:~$ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: active (running) since Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Until: Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 18899) Memory: 4.0K CPU: 418us CGroup: /system.slice/ssh.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+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 1993869] Re: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04
[Unit] After=ssh.socket Requires=ssh.socket ** Attachment added: "00-socket.conf" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+attachment/5626566/+files/00-socket.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993869 Title: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04 Status in openssh package in Ubuntu: Incomplete Bug description: This is a bug report to separate the second issue that was reported in this bug report: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478 There's an issue after upgrading to 22.10 from 22.04 that prevents opensshd from listening to anything other than :::2. I already commented in the bug report I linked, so I'll just copy/paste and add some details. I guess. The issue is that after upgrading, sshd doesn't use the Listen port or ListenAddress config from the sshd_config file or any custom config file that was in the sshd_config.d drop in folder anymore. Other drop in settings from sshd.config.d seem to be applied normally, the issue seem to be only for IP binding and custom ports. If I change Accept=no by Accept=yes in ssh.socket and reloads the socket unit, I can start sshd on a different port and I can also bind the IP to something else than :: There's an issue still, an instance of sshd is still listening to :::22 that is not started by SSHD but by init. root@ubuntulocal:~# netstat -antp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd tcp 0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin tcp 0 272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts tcp6 0 0 :::22 :::* LISTEN 1/init If I reboot after changing this no to yes in ssh.socket does not survive a reboot and fails to load sshd with a "Failed to queue service startup job" error. Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Invalid argument Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 'resources'. I had to mask/stop the sshd.socket unit and create a custom sshd service in /etc/systemd/system to be able start sshd on a custom port and IP. chris@ubuntulocal:~$ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: active (running) since Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Until: Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 18899) Memory: 4.0K CPU: 418us CGroup: /system.slice/ssh.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+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 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
I deleted my account, so I had to create a new one. I used Linux headless, I'll move away to a Systemd Linux distro that doesn't pull shenanigans or tries to reinvent the wheel every update. Whomever pushed this script didn't test it with anything else than the default all commented ListenAddress and Port in the config. On my install it failed to convert a custom Listenaddress and Port formatted exactly as in the default sshd_config file: Port 622 ListenAddress 0.0.0.0 The machine that didn't return an openssh-server error post-upgrade had and almost untouched sshd_config with ListenAddress and Port commented to use opensshd-server default ListenAddress/Port. I know how to set ports with sockets. I didn't see the new # comment in the sshd_config at first I just didn't get why the third party systemd socket was taking precedence over the config from the original application package. The machine that didn't fail installing openssh-server post-upgrade had a /etc/systemd/system/ssh.socket.d/override.conf set. Sorry if I hijacked your bug report a bit. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Bug description: update failed... ProblemType: Package DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi mac_hid ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 19 08:41:28 2022 ErrorMessage: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2019-08-13 (1162 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: openssh Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+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 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
Port Specifies the port number that sshd(8) listens on. The default is 22. Multiple options of this type are permitted. See also ListenAddress. Note: On Ubuntu, the openssh-server package is configured to use systemd socket-based activation by default. Therefore if you are using systemd with the default configuration, Port options will not be honored. Address configuration must be handled in /etc/systemd/system/ssh.socket.d instead. # Port and ListenAddress options are not used when sshd is socket-activated, # which is now the default in Ubuntu. See sshd_config(5) and # /usr/share/doc/openssh-server/README.Debian.gz for details. -- For me, the post upgrade error didn't happen on the machine that had the default openssh-server port 22, but on the machine that had a custom port and bind address. I had to purge and reinstall openssh-server to fix the broken, partially installed, package post-upgrade. I only noticed the new message in the sshd_config configuration file after purging/reinstalling openssh-server second time on one of my machine. I was multitasking during the upgrade process, if there was a message about the new port configuration being a systemd socket, I missed it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Bug description: update failed... ProblemType: Package DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi mac_hid ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 19 08:41:28 2022 ErrorMessage: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2019-08-13 (1162 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: openssh Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+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 1993869] Re: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04
I suppose this wont get fixed any time soon. Apparently, UX config prime over manual configuration now, for a configuration file that's mostly used by server admin. Time to learn yum I suppose. source: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991592 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993869 Title: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04 Status in openssh package in Ubuntu: New Bug description: This is a bug report to separate the second issue that was reported in this bug report: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478 There's an issue after upgrading to 22.10 from 22.04 that prevents opensshd from listening to anything other than :::2. I already commented in the bug report I linked, so I'll just copy/paste and add some details. I guess. The issue is that after upgrading, sshd doesn't use the Listen port or ListenAddress config from the sshd_config file or any custom config file that was in the sshd_config.d drop in folder anymore. Other drop in settings from sshd.config.d seem to be applied normally, the issue seem to be only for IP binding and custom ports. If I change Accept=no by Accept=yes in ssh.socket and reloads the socket unit, I can start sshd on a different port and I can also bind the IP to something else than :: There's an issue still, an instance of sshd is still listening to :::22 that is not started by SSHD but by init. root@ubuntulocal:~# netstat -antp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd tcp 0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin tcp 0 272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts tcp6 0 0 :::22 :::* LISTEN 1/init If I reboot after changing this no to yes in ssh.socket does not survive a reboot and fails to load sshd with a "Failed to queue service startup job" error. Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Invalid argument Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 'resources'. I had to mask/stop the sshd.socket unit and create a custom sshd service in /etc/systemd/system to be able start sshd on a custom port and IP. chris@ubuntulocal:~$ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: active (running) since Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Until: Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 18899) Memory: 4.0K CPU: 418us CGroup: /system.slice/ssh.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993869/+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 1993869] [NEW] openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04
Public bug reported: This is a bug report to separate the second issue that was reported in this bug report: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478 There's an issue after upgrading to 22.10 from 22.04 that prevents opensshd from listening to anything other than :::2. I already commented in the bug report I linked, so I'll just copy/paste and add some details. I guess. The issue is that after upgrading, sshd doesn't use the Listen port or ListenAddress config from the sshd_config file or any custom config file that was in the sshd_config.d drop in folder anymore. Other drop in settings from sshd.config.d seem to be applied normally, the issue seem to be only for IP binding and custom ports. If I change Accept=no by Accept=yes in ssh.socket and reloads the socket unit, I can start sshd on a different port and I can also bind the IP to something else than :: There's an issue still, an instance of sshd is still listening to :::22 that is not started by SSHD but by init. root@ubuntulocal:~# netstat -antp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd tcp 0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin tcp 0 272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts tcp6 0 0 :::22 :::* LISTEN 1/init If I reboot after changing this no to yes in ssh.socket does not survive a reboot and fails to load sshd with a "Failed to queue service startup job" error. Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Invalid argument Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 'resources'. I had to mask/stop the sshd.socket unit and create a custom sshd service in /etc/systemd/system to be able start sshd on a custom port and IP. chris@ubuntulocal:~$ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: active (running) since Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Until: Fri 2022-10-21 23:08:09 UTC; 1min 24s ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 18899) Memory: 4.0K CPU: 418us CGroup: /system.slice/ssh.socket ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: openssh-server ** Attachment added: "upgrade log + sshd_config" https://bugs.launchpad.net/bugs/1993869/+attachment/5625858/+files/do-release%20log-M1-M2%20.zip ** Tags added: openssh-server -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993869 Title: openssh-server cannot listen or bind to anything other than :::2 after upgrading to 22.10 from 22.04 Status in openssh package in Ubuntu: New Bug description: This is a bug report to separate the second issue that was reported in this bug report: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478 There's an issue after upgrading to 22.10 from 22.04 that prevents opensshd from listening to anything other than :::2. I already commented in the bug report I linked, so I'll just copy/paste and add some details. I guess. The issue is that after upgrading, sshd doesn't use the Listen port or ListenAddress config from the sshd_config file or any custom config file that was in the sshd_config.d drop in folder anymore. Other drop in settings from sshd.config.d seem to be applied normally, the issue seem to be only for IP binding and custom ports. If I change Accept=no by Accept=yes in ssh.socket and reloads the socket unit, I can start sshd on a different port and I can also bind the IP to something else than :: There's an issue still, an instance of sshd is still listening to :::22 that is not started by SSHD but by init. root@ubuntulocal:~# netstat -antp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd tcp 0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin tcp 0 272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts tcp6 0 0 :::22 :::* LISTEN 1/init If I reboot after changing this no to yes in ssh.socket does not survive a reboot and fails to load sshd with a "Failed to queue service startup job" error. Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Invalid argument Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 'resources'. I had to mask/stop the sshd.socket unit and create a custom sshd service in /etc/systemd/system
[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
It is exactly the same issue msaxl reported, the Opensshd returns an error 1 at the ends of the upgrade process, and after the upgrade it is impossible to bind/listen opensshd on anything else than :::22. The first issue which is that opensshd reported an error 1 at the end of the upgrade process, happened on one machine. I'll open a ticket for the bind/port issue as msaxl isn't really clear with what he said regarding the behavior of Opensshd post-upgrade, and I understood only because I had the exact same issue. The second that is about the sshd.socket, or whatever it is, unit that doesn't allow opensshd to listen or bind to anything other than :::22. In short it is impossible to bind or listen to a custom port with Opensshd after upgrading 22.04 to 22.10 on both of my machines. The machine that returned an error 1 and the other that didn't. Same as msaxl That second issue that msaxl reported happens to me on both of my machine, including the machine that did not report an opensshd error 1 at the end of the upgrade process. I joined the log from the machine that had the opensshd error 1 2022-10-21 14:59:29,800 ERROR got an error from dpkg for pkg: 'openssh-server': 'installed openssh-server package post-installation script subprocess returned error exit status 1' 2022-10-21 14:59:29,801 DEBUG running apport_pkgfailure() openssh-server: installed openssh-server package post-installation script subprocess returned error exit status 1 2022-10-21 15:00:17,041 ERROR Exception during pm.DoInstall() ** Attachment added: "Machine-1_dist-upgrade.zip" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+attachment/5625850/+files/Machine-1_dist-upgrade.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Bug description: update failed... ProblemType: Package DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi mac_hid ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 19 08:41:28 2022 ErrorMessage: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2019-08-13 (1162 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: openssh Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+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 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
Some additional info: drop in settings from sshd.config.d seem to be applied normally, the issue seem to be only for IP binding and custom ports. If I change Accept=no by Accept=yes in ssh.socket and reloads the socket unit, I can start sshd on a different port and I can also bind the IP to something else than :: There's an issue still, an instance of sshd is still listening to :::22 that is not started by SSHD but by init. root@ubuntulocal:~# netstat -antp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 0.0.0.0:21 0.0.0.0:* LISTEN 568/vsftpd tcp0 0 0.0.0.0:622 0.0.0.0:* LISTEN 571/sshd: /usr/sbin tcp0272 192.168.1.225:622 192.168.1.220:2473 ESTABLISHED 1027/sshd: root@pts tcp6 0 0 :::22 :::*LISTEN 1/init If I reboot after changing this no to yes in ssh.socket does not survive a reboot and fails to load sshd with a "Failed to queue service startup job" error. Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Invalid argument Oct 21 15:41:56 ubuntulocal systemd[1]: ssh.socket: Failed with result 'resources'. I had to mask/stop the sshd.socket unit and create a custom sshd service in /etc/systemd/system to be able start sshd on a custom port and IP. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Bug description: update failed... ProblemType: Package DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi mac_hid ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 19 08:41:28 2022 ErrorMessage: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2019-08-13 (1162 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: openssh Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+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 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
Hellow, same issue here. SSHD failed during the do-release-upgrade process on one of my machines, and now it refuses to change the port to anything else than 22 on both of my machines. If I start the sshd daemon using systemd service -> systemctl start ssh.service ssh does change the port if I load the config using the -f command after manually launching the binary. /usr/sbin/sshd -f /path/to/my/config.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Bug description: update failed... ProblemType: Package DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi mac_hid ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 19 08:41:28 2022 ErrorMessage: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2019-08-13 (1162 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: openssh Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+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 1991492] Re: Upgrade to version 1.1.0
libsndfile-1.1.0 is now (2022-09-06) packaged in Debian and will automatically be imported into Ubuntu with the next DebianImport. Unfortunately we missed the freeze deadline for 22.10/kinetic, which means that the first Ubuntu version with the new library version will be 23.04 ** Changed in: libsndfile (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1991492 Title: Upgrade to version 1.1.0 Status in libsndfile package in Ubuntu: Fix Committed Bug description: Version 1.1.0 (released in March 2022) brings MP3 encoding/decoding support. It would be great if the version here could be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1991492/+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 1992025] [NEW] When sudo does not require a password, it alters stty as though it is reading a password
Public bug reported: Summary: Executing a sudo (that does not require a password) in a /bin/bash script leaves the terminal as though it is reading a password (-echo, -icrnl, -ixon, -opost, -isig, -icanon, -iexten) To recreate the problem: (See attached log) In a fresh install of 22.04.1 (desktop, minimal, do not load updates, no update done beyond iso data, running under Virtualbox on a Mac), I set up a new user that can run "sudo sleep" without a password. In a Terminal, I demonstrate this, running "stty -a" before and after the "sudo sleep". Then I create a bash script with those same commands. When that script is run, the stty after the "sudo sleep" shows that the state of the terminal has been altered (-echo, etc.) The log starts immediately after the reboot after installing 22.04.1. I decline to do the update when it is offered. (The bug appears even if I do the update on 22.04.1, but I decline the update to make sure this is repeatable.) Basically, the steps are Create user "testuser" Add a file to /etc/sudoers.d that gives testuser sudo privs, with no password required for sleep. (nor for "grep", but I dropped the use of grep in the demo) su - testuser Interactively, in the terminal, I show that "sudo sleep 30 &" does not mess with the terminal settings. I create a /bin/bash script that includes the same commands (stty -a; sudo sleep 10 &; sleep 3; stty -a) I execute the script, which alters the terminal settings.(Quite visible on the Terminal; not as easily visible in the log file.) I expect the second "stty -a" to be the same as the first. I originally saw the bug in 20.04.5 (repeatable but on someone else's computer) for "sudo tcpdump" but wasn't able to reproduce it in a fresh install. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: sudo 1.9.9-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 6 10:40:03 2022 InstallationDate: Installed on 2022-10-06 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: Error: command ['pkexec', '/usr/sbin/visudo', '-c'] failed with exit code 1: /etc/sudoers.d/testuser: bad permissions, should be mode 0440 /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Log of demoing the bug in a fresh install of Ub22.04.1" https://bugs.launchpad.net/bugs/1992025/+attachment/5621792/+files/sudobug.log -- 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/1992025 Title: When sudo does not require a password, it alters stty as though it is reading a password Status in sudo package in Ubuntu: New Bug description: Summary: Executing a sudo (that does not require a password) in a /bin/bash script leaves the terminal as though it is reading a password (-echo, -icrnl, -ixon, -opost, -isig, -icanon, -iexten) To recreate the problem: (See attached log) In a fresh install of 22.04.1 (desktop, minimal, do not load updates, no update done beyond iso data, running under Virtualbox on a Mac), I set up a new user that can run "sudo sleep" without a password. In a Terminal, I demonstrate this, running "stty -a" before and after the "sudo sleep". Then I create a bash script with those same commands. When that script is run, the stty after the "sudo sleep" shows that the state of the terminal has been altered (-echo, etc.) The log starts immediately after the reboot after installing 22.04.1. I decline to do the update when it is offered. (The bug appears even if I do the update on 22.04.1, but I decline the update to make sure this is repeatable.) Basically, the steps are Create user "testuser" Add a file to /etc/sudoers.d that gives testuser sudo privs, with no password required for sleep. (nor for "grep", but I dropped the use of grep in the demo) su - testuser Interactively, in the terminal, I show that "sudo sleep 30 &" does not mess with the terminal settings. I create a /bin/bash script that includes the same commands (stty -a; sudo sleep 10 &; sleep 3; stty -a) I execute the script, which alters the terminal settings.(Quite visible on the Terminal; not as easily visible in
[Touch-packages] [Bug 1989826] [NEW] cannot start lightdm gui
Public bug reported: i installed lightdm but cannot start it manually using ubuntu 22.04.1 LTS release 22.04 codename: jammy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 Date: Fri Sep 16 01:27:20 2022 InstallationDate: Installed on 2022-08-28 (18 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1989826 Title: cannot start lightdm gui Status in lightdm package in Ubuntu: New Bug description: i installed lightdm but cannot start it manually using ubuntu 22.04.1 LTS release 22.04 codename: jammy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 Date: Fri Sep 16 01:27:20 2022 InstallationDate: Installed on 2022-08-28 (18 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1989826/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04
*** This bug is a duplicate of bug 1842320 *** https://bugs.launchpad.net/bugs/1842320 I guess the problem hasn't been fixed in ubuntu-22.04.1. I'm having the same exact issue when trying to install ubuntu-22.04.1 from USB on a computer with large memory (32GB of RAM). -- 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/1970402 Title: Initrd out of memory error after upgrade to 22.04 Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Jammy: Confirmed Bug description: After upgrading to 22.04 system is unbootable because of "out of memory" error when loading initial ramdisk. I was able to fix it by editing cat /etc/initramfs-tools/initramfs.conf and changing configuration to: MODULES=dep COMPRESS=xz RUNSIZE=15% Not sure which one helped, but I can test it if needed. System information: Description:Ubuntu 22.04 LTS Release:22.04 initramfs-tools: Installed: 0.140ubuntu13 Candidate: 0.140ubuntu13 Version table: *** 0.140ubuntu13 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1863080] Re: Unable to use dead keys in Java apps
```bash lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy muksihs@omen-desktop:~$ set | grep -E 'XMODIFIERS|GTK_IM_MODULE|QT_IM_MODULE';setxkbmap -query GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus rules: evdev model: pc105 layout: us variant:altgr-intl options:compose:lwin,compose:rwin,grp_led:scroll,mod_led:compose muksihs@omen-desktop:~$ cat .xsessionrc #!/bin/bash export CLUTTER_IM_MODULE=ibus export GTK_IM_MODULE=ibus export QT_IM_MODULE=ibus export XMODIFIERS=@im=ibus muksihs@omen-desktop:~$ ``` I'm using ibus with a local m17n layout. Layout file: https://github.com/CherokeeLanguage/m17n.d/blob/main/chr- phonetic.mim My issue with ibus and intellij/pycharm is that the cursor is positioned before the last character typed instead of after on short sequences where a longer sequence exists. The cursor appears to get moved back one character in the matching case. I'm not sure the issue I'm having is exactly the same as this issue as I'm not using dead keys. See https://youtrack.jetbrains.com/issue/PY-55374/ibus-input-issue-where- cursor-position-ends-being-before-the-character-inserted -- 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/1863080 Title: Unable to use dead keys in Java apps Status in ibus: Fix Released Status in ibus package in Ubuntu: Confirmed Bug description: This is same bug as #540751, as it happens again in Ubuntu 19.10 with Java 11. Way of reproduce it: - Fresh Ubuntu 19.10 install. - Install default-jre. - Download (for example) lastest NetBeans version. - Edit a file in NetBeans, you can't insert characters like 'á'. The workaround is the same, define XMODIFIERS='' before launching the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1863080/+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 1982057] [NEW] gdebi-gtk is not installing .deb package if "Open With Gdebi" is used on right-click
Public bug reported: In Xfce on 22.04 Xubuntu, when trying to install .deb package with "Open With Gdebi packge Installer" right-click option while in Thunar file manager, Gdebi-gtk just silently dies, without installing package. If gdebi-gtk is started from CLI, and then .deb file is opened via File>Open , then .deb package is able to be installed. Gdebi=gtk should be able to install package with open with method and should not die. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdebi 0.9.5.7+nmu6 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Jul 19 07:08:58 2022 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: Upgraded to jammy on 2022-04-29 (80 days ago) ** Affects: gdebi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1982057 Title: gdebi-gtk is not installing .deb package if "Open With Gdebi" is used on right-click Status in gdebi package in Ubuntu: New Bug description: In Xfce on 22.04 Xubuntu, when trying to install .deb package with "Open With Gdebi packge Installer" right-click option while in Thunar file manager, Gdebi-gtk just silently dies, without installing package. If gdebi-gtk is started from CLI, and then .deb file is opened via File>Open , then .deb package is able to be installed. Gdebi=gtk should be able to install package with open with method and should not die. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdebi 0.9.5.7+nmu6 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Jul 19 07:08:58 2022 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: Upgraded to jammy on 2022-04-29 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1982057/+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 1975865] Re: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz
This seems to be fixed, now. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1975865 Title: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz Status in apt package in Ubuntu: Confirmed Bug description: When adding the debug repos, I am getting: E: Failed to fetch http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: 91.189.91.49 80] Hashes of expected file: - Filesize:795487 [weak] - SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81 - SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6 - SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak] - MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak] Release file created at: Thu, 26 May 2022 08:04:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. When I manually go to the repositories... many (all?) of the hashes listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not match the files (e.g. http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz ) Note: I filed this against `apt` because `ubuntu-bug` forced me to specify a package and I didn't know any other way to file the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.14 Uname: Linux 5.16.18-1rodete2-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Thu May 26 18:36:21 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865/+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 1975865] Re: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz
Yep, this affects all versions. FWIW, the ddebs repository seems to break like this every 1-2 years and after reporting it, it's usually cleaned up in a week or two. On Mon, May 30, 2022 at 2:31 AM Juan Navarro <1975...@bugs.launchpad.net> wrote: > I just filed a similar bug affecting Ubuntu 20.04 Focal: > https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1976233 > > There seems to be a problem with a recent update of the ddebs > repositories. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1975865 > > Title: > Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic- > updates/main/binary-amd64/Packages.gz > > Status in apt package in Ubuntu: > New > > Bug description: > When adding the debug repos, I am getting: > > E: Failed to fetch > http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz > File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: > 91.189.91.49 80] > Hashes of expected file: > - Filesize:795487 [weak] > - > SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81 > - > SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6 > - SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak] > - MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak] > Release file created at: Thu, 26 May 2022 08:04:16 + > E: Some index files failed to download. They have been ignored, or old > ones used instead. > > When I manually go to the repositories... many (all?) of the hashes > listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not > match the files (e.g. http://ddebs.ubuntu.com/dists/bionic- > updates/main/binary-amd64/Packages.gz ) > > Note: I filed this against `apt` because `ubuntu-bug` forced me to > specify a package and I didn't know any other way to file the bug. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: apt 1.6.14 > Uname: Linux 5.16.18-1rodete2-amd64 x86_64 > ApportVersion: 2.20.9-0ubuntu7.28 > Architecture: amd64 > Date: Thu May 26 18:36:21 2022 > ProcEnviron: >TERM=xterm >PATH=(custom, no user) > SourcePackage: apt > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1975865 Title: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz Status in apt package in Ubuntu: New Bug description: When adding the debug repos, I am getting: E: Failed to fetch http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: 91.189.91.49 80] Hashes of expected file: - Filesize:795487 [weak] - SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81 - SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6 - SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak] - MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak] Release file created at: Thu, 26 May 2022 08:04:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. When I manually go to the repositories... many (all?) of the hashes listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not match the files (e.g. http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz ) Note: I filed this against `apt` because `ubuntu-bug` forced me to specify a package and I didn't know any other way to file the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.14 Uname: Linux 5.16.18-1rodete2-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Thu May 26 18:36:21 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865/+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 1975865] [NEW] Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz
Public bug reported: When adding the debug repos, I am getting: E: Failed to fetch http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: 91.189.91.49 80] Hashes of expected file: - Filesize:795487 [weak] - SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81 - SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6 - SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak] - MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak] Release file created at: Thu, 26 May 2022 08:04:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. When I manually go to the repositories... many (all?) of the hashes listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not match the files (e.g. http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz ) Note: I filed this against `apt` because `ubuntu-bug` forced me to specify a package and I didn't know any other way to file the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.14 Uname: Linux 5.16.18-1rodete2-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Thu May 26 18:36:21 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1975865 Title: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz Status in apt package in Ubuntu: New Bug description: When adding the debug repos, I am getting: E: Failed to fetch http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: 91.189.91.49 80] Hashes of expected file: - Filesize:795487 [weak] - SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81 - SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6 - SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak] - MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak] Release file created at: Thu, 26 May 2022 08:04:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. When I manually go to the repositories... many (all?) of the hashes listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not match the files (e.g. http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz ) Note: I filed this against `apt` because `ubuntu-bug` forced me to specify a package and I didn't know any other way to file the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.14 Uname: Linux 5.16.18-1rodete2-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Thu May 26 18:36:21 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865/+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 1968912] [NEW] vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install
Public bug reported: Ubuntu 22.04 When running vim.tiny it says: $ vim.tiny E1187: Failed to source defaults.vim Press ENTER or type command to continue This is due to the defaults.vim file not being available. If you just run it as vi $ vi this message does not appear as vim.tiny runs in compatibility mode. I found mention of this issue in: https://github.com/grml/grml-etc-core/issues/99 The defaults.vim file is provided by the package vim-runtime. I'm unsure what the issue is, if something needs to be in /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg claims vimrc is in vim-common, but no file is installed for me from that package, or if vim-runtime needs to be a required package for vim-tiny $ dpkg -S /etc/vim/vimrc vim-common: /etc/vim/vimrc $ ls -al /etc/vim/vimrc ls: cannot access '/etc/vim/vimrc': No such file or directory I discovered this because my .selected-editor was vim.tiny after running crontab -e $ crontab -e Select an editor. To change later, run 'select-editor'. 1. /bin/nano< easiest 2. /usr/bin/vim.tiny 3. /bin/ed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: vim-tiny 2:8.2.3995-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30 Uname: Linux 5.15.0-1005-raspi aarch64 ApportVersion: 2.20.11-0ubuntu81 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Apr 13 11:56:35 2022 ImageMediaBuild: 20201022 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image jammy raspi-image ** Description changed: Ubuntu 22.04 When running vim.tiny it says: $ vim.tiny E1187: Failed to source defaults.vim Press ENTER or type command to continue This is due to the defaults.vim file not being available. If you just run it as vi $ vi - this message does not appear. - - I discovered this because my .selected-editor was vim.tiny after running - crontab -e - - $ crontab -e - - Select an editor. To change later, run 'select-editor'. - 1. /bin/nano< easiest - 2. /usr/bin/vim.tiny - 3. /bin/ed + this message does not appear as vim.tiny runs in compatibility mode. I found mention of this issue in: + https://github.com/grml/grml-etc-core/issues/99 The defaults.vim file is provided by the package vim-runtime. I'm unsure what the issue is, if something needs to be in /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg claims vimrc is in vim-common, but no file is installed for me from that package, or if vim-runtime needs to be a required package for vim-tiny $ dpkg -S /etc/vim/vimrc vim-common: /etc/vim/vimrc $ ls -al /etc/vim/vimrc ls: cannot access '/etc/vim/vimrc': No such file or directory + I discovered this because my .selected-editor was vim.tiny after running + crontab -e + + $ crontab -e + + Select an editor. To change later, run 'select-editor'. + 1. /bin/nano< easiest + 2. /usr/bin/vim.tiny + 3. /bin/ed + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: vim-tiny 2:8.2.3995-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30 Uname: Linux 5.15.0-1005-raspi aarch64 ApportVersion: 2.20.11-0ubuntu81 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Apr 13 11:56:35 2022 ImageMediaBuild: 20201022 ProcEnviron: - TERM=screen - PATH=(custom, no user) - LANG=en_CA.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + LANG=en_CA.UTF-8 + SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1968912 Title: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install Status in vim package in Ubuntu: New Bug description: Ubuntu 22.04 When running vim.tiny it says: $ vim.tiny E1187: Failed to source defaults.vim Press ENTER or type command to continue This is due to the defaults.vim file not being available. If you just run it as vi $ vi this message does not appear as vim.tiny runs in compatibility mode. I found mention of this issue in: https://github.com/grml/grml-etc-core/issues/99 The defaults.vim file is provided by the package vim-runtime. I'm unsure what the issue is, if something needs to be in /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg claims vimrc is in vim-common, but no file is installed for me from that package, or if vim-runtime needs to be a required package for vim-tiny $ dpkg -S /etc/vim/vimrc vim-common: /etc/vim/vimrc $ ls -al /etc/vim/vimrc ls: cannot access '/etc/vim/vimrc': No such file or
[Touch-packages] [Bug 1961848] [NEW] gst-play-1.0 crashes when attempting to play a mp4 file
Public bug reported: I am attempting to play a mp4 file using gstreamer's gst-play-1.0. What I see is that a window is opened and a segmentation fault is reported (window closes). I am running Jammy: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 On an Intel Coffelake core-i7 / integrated (Gen 9) graphics. The machine is updated as of Feb 22, 2022. Package version is: $ apt-cache policy gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-base-apps: Installed: 1.20.0-2 Candidate: 1.20.0-2 Version table: *** 1.20.0-2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status bms20@lichking:/tmp$ Crash log attached. Any advice on how to fix welcome! ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_bin_gst-play-1.0.1000.crash.gz" https://bugs.launchpad.net/bugs/1961848/+attachment/5562828/+files/_usr_bin_gst-play-1.0.1000.crash.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1961848 Title: gst-play-1.0 crashes when attempting to play a mp4 file Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: I am attempting to play a mp4 file using gstreamer's gst-play-1.0. What I see is that a window is opened and a segmentation fault is reported (window closes). I am running Jammy: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 On an Intel Coffelake core-i7 / integrated (Gen 9) graphics. The machine is updated as of Feb 22, 2022. Package version is: $ apt-cache policy gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-base-apps: Installed: 1.20.0-2 Candidate: 1.20.0-2 Version table: *** 1.20.0-2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status bms20@lichking:/tmp$ Crash log attached. Any advice on how to fix welcome! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1961848/+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 1948511] [NEW] Very low volume output: Realtek ALC1222 in Omen 30L desktop
Public bug reported: Volume at 100% + Speaker knob at 100% and I get barely audio than can be barely heard. Alsa Info link: http://alsa- project.org/db/?f=5bf0f297f3700c75db822f78d563962f563f355c ``` lspci 00:00.0 Host bridge: Intel Corporation Device 9b33 (rev 05) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05) 00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller 00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller 00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM 00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi 00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0) 00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0685 00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS 00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH SPI Controller 01:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GA102 High Definition Audio Controller (rev a1) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16) 03:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN750 / PC SN730 NVMe SSD ``` ``` sudo dmesg | grep snd [6.624036] snd_hda_intel :00:1f.3: enabling device (0100 -> 0102) [6.624372] snd_hda_intel :01:00.1: enabling device (0100 -> 0102) [6.624423] snd_hda_intel :01:00.1: Disabling MSI [6.624426] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [6.776175] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC1220: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line [6.776179] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [6.776181] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x14/0x0/0x0/0x0/0x0) [6.776182] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [6.776183] snd_hda_codec_realtek hdaudioC0D0:inputs: [6.776184] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 [6.776186] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 [6.776187] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a [6.776188] snd_hda_codec_realtek hdaudioC0D0: Line=0x15 ``` ``` cat /proc/asound/car*/co* | grep Codec Codec: Realtek ALC1220 Codec: Nvidia GPU 9a HDMI/DP ``` ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: 30l alc1222 omen realtek -- 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/1948511 Title: Very low volume output: Realtek ALC1222 in Omen 30L desktop Status in alsa-driver package in Ubuntu: New Bug description: Volume at 100% + Speaker knob at 100% and I get barely audio than can be barely heard. Alsa Info link: http://alsa- project.org/db/?f=5bf0f297f3700c75db822f78d563962f563f355c ``` lspci 00:00.0 Host bridge: Intel Corporation Device 9b33 (rev 05) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05) 00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller 00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller 00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM 00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi 00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0) 00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0685 00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS 00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH SPI Controller 01:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GA102 High Definition Audio Controller (rev a1) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16) 03:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN750 / PC SN730 NVMe SSD ``` ``` sudo dmesg | grep snd [6.624036] snd_hda_intel :00:1f.3: enabling device (0100 -> 0102) [6.624372] snd_hda_intel
[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr
When I do right-click on .deb package and open it with Gdebi-gtk, and try to install a package on 21.10 (also used to happen od 21.04) program closes. I have downloaded 0.9.5.7+nmu6 and I think I have built it with dpkg- buildpackage - us -uc and still happens the same. 0.9.5.7+nmu6 works of gdebi-gtk is called from Terminal and .deb opened via File>Open , but it does not when on right-click and install in Thunar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Invalid Status in gdebi package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Confirmed Status in gdebi source package in Impish: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to:
[Touch-packages] [Bug 1493921] Re: X server fails to set correct mode on resume from sleep (NVIDIA: Setting a mode on head 0 failed: An invalid mode was requested)
Steve, please open a new report. Thanks! -- 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/1493921 Title: X server fails to set correct mode on resume from sleep (NVIDIA: Setting a mode on head 0 failed: An invalid mode was requested) Status in xorg package in Ubuntu: Won't Fix Bug description: Using a really picky Dell P2415Q monitor through DP->mDP (displayport -> mini displayport) cable, nvidia binary driver version 352.30-0ubuntu1. This is not a laptop, so the Intel integrated VGA is disabled. (No other cards in sysfs.) Really nasty bug, as every time all the running applications detect that the X server went away and exit, logind terminates the session culling everyone, and so on. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.30 Tue Jul 21 18:53:45 PDT 2015 GCC version: gcc version 5.2.1 20150825 (Ubuntu 5.2.1-15ubuntu5) ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Wed Sep 9 17:56:53 2015 DistUpgraded: 2014-08-06 01:18:55,244 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3614] MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fba348ec-fc7c-4c7f-b78b-026be76c4568 ro crashkernel=384M-:128M crashkernel=384M-:128M SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2014-08-05 (399 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F18 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF18:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Sep 9 15:10:08 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech G100s Optical Gaming Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1493921/+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 1934552] [NEW] Graphical glitches on Radeon RX 6700 XT
Public bug reported: Ubuntu 21.04, mesa 21.0.1-2 amd64 Upstream MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9568 Graphical glitches can be seen occasionally on screen with the RX 6700 XT graphics card. This is fixed upstream with the above merged MR, so please backport it... ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1934552 Title: Graphical glitches on Radeon RX 6700 XT Status in mesa package in Ubuntu: New Bug description: Ubuntu 21.04, mesa 21.0.1-2 amd64 Upstream MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9568 Graphical glitches can be seen occasionally on screen with the RX 6700 XT graphics card. This is fixed upstream with the above merged MR, so please backport it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934552/+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 1886728] Re: OpenVPN OTP replaces the ordinary password
This is still an issue in Ubuntu 21.04 (development, as of March 30, 2021) It looks like people have been complaining about this for years, and while some people have tried to fix it, those fixes never made it in. Surely it must be of some type of urgency to support 2FA one-time passwords in the primary network management solution in Ubuntu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1886728 Title: OpenVPN OTP replaces the ordinary password Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Triaged Bug description: When OpenVPN has One-time password (OTP) enabled, and the user connects, a dialog asks the user to enter the One-time password (OTP) and press ok. This action replaces the ordinary "long term" password with the OTP. This causes annoyance as the next login will fail because the password is wrong and the user has to enter both the password and the OTP the next time they log in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-keyring 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 8 01:07:18 2020 InstallationDate: Installed on 2020-03-23 (106 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to focal on 2020-05-11 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1886728/+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 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
** Description changed: From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN - I don't know if it comes from Ubunut or upstream. + I don't know if it comes from Ubuntu or upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1917148 Title: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2 Status in procps package in Ubuntu: New Bug description: From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+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 1917148] [NEW] ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
Public bug reported: >From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubunut or upstream. ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1917148 Title: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2 Status in procps package in Ubuntu: New Bug description: From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubunut or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+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 1906741] Re: Firefox sometimes causes garbled audio
For me many videos have garbled audio, today it's https://octopus.com/, some others, e.g. a cloud guru, tedx weren't working before, but are now. Perhaps it's not related to the video format. Ubuntu 20.04 and FF 84.0.2 -- 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/1906741 Title: Firefox sometimes causes garbled audio Status in firefox package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Opening certain applications/websites at the same time as Firefox causes the audio to become garbled. The audio sounds distorted with an echo. Certain actions are guaranteed to cause this, but it can also happening when only running instances of Firefox. I've been able to consistently cause this by launching Zoom from a link within Firefox. This does not occur when using Chrome. The only way to fix the issue is to shut down all audio-related programs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rdevans 55475 F pulseaudio /dev/snd/controlC0: rdevans 55475 F pulseaudio /dev/snd/controlC3: rdevans 55475 F pulseaudio /dev/snd/controlC1: rdevans 55475 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:55:36 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-20 (1140 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.0.0.1 dev enp7s0 proto dhcp metric 100 10.0.0.0/24 dev enp7s0 proto kernel scope link src 10.0.0.7 metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-11-12 (21 days ago) dmi.bios.date: 02/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: H67M dmi.board.vendor: ASRock 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.:bvrP1.40:bd02/18/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1906741/+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 1912668] [NEW] [Q1U dynamic microphone - AT2020 USB, recording] fails after a while
Public bug reported: Opening sound control panel, or Audacity, ATH2020-USB microphone will show signal for a few seconds, then cut off (the meter stays stuck in last updated position). Same behavior using other apps that use the microphone. Changed USB port, still the same result. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: surefoot 1972 F pulseaudio /dev/snd/controlC2: surefoot 1972 F pulseaudio /dev/snd/controlC1: surefoot 1972 F pulseaudio /dev/snd/pcmC1D0c: surefoot 1972 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 18:00:16 2021 InstallationDate: Installed on 2020-10-31 (81 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: CMI8788 [Oxygen HD Audio] (Virtuoso 100 (Xonar Essence STX II)) - Xonar STX II Symptom_PulseAudioLog: janv. 21 14:34:39 STH10 dbus-daemon[1083]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3902 dmi.board.asset.tag: Default string dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3902:bd03/21/2018:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1912668 Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Opening sound control panel, or Audacity, ATH2020-USB microphone will show signal for a few seconds, then cut off (the meter stays stuck in last updated position). Same behavior using other apps that use the microphone. Changed USB port, still the same result. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: surefoot 1972 F pulseaudio /dev/snd/controlC2: surefoot 1972 F pulseaudio /dev/snd/controlC1: surefoot 1972 F pulseaudio /dev/snd/pcmC1D0c: surefoot 1972 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 18:00:16 2021 InstallationDate: Installed on 2020-10-31 (81 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: CMI8788 [Oxygen HD Audio] (Virtuoso 100 (Xonar Essence STX II)) - Xonar STX II Symptom_PulseAudioLog: janv. 21 14:34:39 STH10 dbus-daemon[1083]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3902 dmi.board.asset.tag: Default string dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.c
[Touch-packages] [Bug 1899103] Re: libpam-cap causes PAM applications to crash
I have this problem too. When I try to connect to it for the second time, it gives this error on the client-side: Got HTTP response: HTTP/1.1 401 Authentication failed Server 'example.com' requested Basic authentication which is disabled by default Failed to obtain WebVPN cookie And then the ocserv goes down on the server. If I add --http-auth=Basic option to openconnect, then it won't ask for password from me and gives the following error: Got HTTP response: HTTP/1.1 401 Authentication failed Content-Length: 0 HTTP body length: (0) No more authentication methods to try Failed to obtain WebVPN cookie -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1899103 Title: libpam-cap causes PAM applications to crash Status in libcap2 package in Ubuntu: Confirmed Bug description: Install ocserv and setup for PAM authentication. On second connection, ocserv crashes due to a double free in PAM. Repro steps: 1. Create Dockerfile that installs ocserv + libpam-cap ``` FROM ubuntu:20.04 RUN apt update && apt install -y ocserv libpam-cap && apt autoremove && apt clean COPY server-cert.pem /etc/ssl/ocserv_test.cert COPY server-key.pem /etc/ssl/ocserv_test.key COPY ca-cert.pem /etc/ssl/certs/ssl-cert-snakeoil.pem COPY ocserv.conf /etc/ocserv/ocserv.conf RUN useradd test RUN echo "test\ntest" | passwd test ENV MALLOC_CHECK_=3 CMD ocserv -f -d 1 ``` 2. Build container: ``` sudo docker build -t ocserv:20.04 . ``` 3. Launch container: ``` docker run -p 443:443/tcp -p 443:443/udp -it --rm --device /dev/net/tun --cap-add net_admin ocserv:20.04 ``` 4. From another console, connect / disconnect: ``` while true; do echo test | openconnect https://localhost -u test --passwd-on-stdin --servercert pin-sha256:qBLVTyoXiFdn+0pW+eSGqnVCEnMbLigVf5vAl1ZewW4= --background && sleep 2 && pkill openconnect && sleep 2;done ``` 5. ocserv crashes: free(): invalid pointer ocserv[8]: main: main-sec-mod-cmd.c:106: command socket for sec-mod closed ocserv[8]: main: main.c:1179: error in command from sec-mod ocserv[8]: main: termination request received; waiting for children to die For more details see: https://gitlab.com/openconnect/ocserv/-/issues/361 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1899103/+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 1902760] [NEW] Please merge linker bugfix into Ubuntu 20.04 LTS
Public bug reported: Binutils bug https://sourceware.org/bugzilla/show_bug.cgi?id=26262 fixes a problem that Intel Fortran is running into when using the -ipo option to request link time optimization. Please merge the fix into Ubuntu 20.04 LTS ** Affects: binutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1902760 Title: Please merge linker bugfix into Ubuntu 20.04 LTS Status in binutils package in Ubuntu: New Bug description: Binutils bug https://sourceware.org/bugzilla/show_bug.cgi?id=26262 fixes a problem that Intel Fortran is running into when using the -ipo option to request link time optimization. Please merge the fix into Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1902760/+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 1888746] [NEW] graphics performance very poor
Public bug reported: Your system is providing 3D via software rendering rather than hardware rendering. This is a compatibility mode which should display 3D graphics properly but the performance may be very poor. If the problem you're reporting is related to graphics performance, your real question may be why X didn't use hardware acceleration for your system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jul 24 03:20:06 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201601261029~ubuntu14.04.1, 3.13.0-170-generic, x86_64: installed oem-audio-hda-daily, 0.201601261029~ubuntu14.04.1, 3.13.0-53-generic, x86_64: installed synaptic-i2c-hid-3.13.0-32-backport, 1.6.4, 3.13.0-170-generic, x86_64: installed virtualbox, 4.3.40, 3.13.0-170-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06ac] InstallationDate: Installed on 2020-07-22 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=c19be7d4-6630-4858-92a4-1ecda27d8cfc ro locale=en_US quiet splash radeon.modeset=0 nouveau.modeset=0 i915.disable_power_well=0 video.use_native_backlight=1 radeon.modeset=0 nouveau.modeset=0 i915.disable_power_well=0 video.use_native_backlight=1 vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.product.name: Inspiron 15-3552 version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Jul 24 00:58:07 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.11 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1888746 Title: graphics performance very poor Status in xorg package in Ubuntu: New Bug description: Your system is providing 3D via software rendering rather than hardware rendering. This is a compatibility mode which should display 3D graphics properly but the performance may be very poor. If the problem you're reporting is related to graphics performance, your real question may be why X didn't use hardware acceleration for your system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jul 24 03:20:06 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201601261029~ubuntu14.04.1, 3.13.0-170-generic, x86_64: installed oem-audio-hda-daily, 0.201601261029~ubuntu14.04.1, 3.13.0-53-generic, x86_64: installed
[Touch-packages] [Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity
Never mind - Somehow my local package simply looked newer from a versioning perspective. I found the right version and as far as I can tell the problems are gone in this version. I have not seen any of the dbus messages and roaming works better (less erratic) here. Thanks a lot for getting this fix in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1879087 Title: dbus errors, frequent roaming and unstable connectivity Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Released Bug description: * Impact extra roaming events are been generated * Test case check the output of `journalctl -lu wpa_supplicant`, it shouldn't have those warnings dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 the roaming events should not be too frequent * Regression potential check that wifi connection keep working correctly -- When using this version of wpa_supplicant with my company WPA2-Enterprise wireless setup, I'm experiencing far too frequent roaming events (even when not moving around) accompanied by hiccups in connectivity. I also see these messages in the wpa_supplicant log: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Having done a little research, at least the dbus errors seem to be fixed by this commit upstream: https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756 So I built a version of wpa_supplicant including this particular patch and installed on my machine. Apart from solving the dbus errors completely, it seems to have had a positive impact on the frequent roaming and unstable connectivity as well (I've run for a day with no burst of roaming events at all, where they used to happen every few minutes most of the time.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 16 16:47:27 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+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 1879087] Re: dbus errors, frequent roaming and unstable connectivity
I've been looking for the package but cannot seem to find it for testing. Please help me find it and I will test it immediately. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1879087 Title: dbus errors, frequent roaming and unstable connectivity Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Released Bug description: * Impact extra roaming events are been generated * Test case check the output of `journalctl -lu wpa_supplicant`, it shouldn't have those warnings dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 the roaming events should not be too frequent * Regression potential check that wifi connection keep working correctly -- When using this version of wpa_supplicant with my company WPA2-Enterprise wireless setup, I'm experiencing far too frequent roaming events (even when not moving around) accompanied by hiccups in connectivity. I also see these messages in the wpa_supplicant log: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Having done a little research, at least the dbus errors seem to be fixed by this commit upstream: https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756 So I built a version of wpa_supplicant including this particular patch and installed on my machine. Apart from solving the dbus errors completely, it seems to have had a positive impact on the frequent roaming and unstable connectivity as well (I've run for a day with no burst of roaming events at all, where they used to happen every few minutes most of the time.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 16 16:47:27 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+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 1881314] Re: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04
Great! Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1881314 Title: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04 Status in openssl package in Ubuntu: Fix Released Bug description: After a recent update: $ apt-get install libssl1.1-dbgsym The following packages have unmet dependencies: libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.5) but 1.1.1-1ubuntu2.1~18.04.6 is to be installed E: Unable to correct problems, you have held broken packages. The following debug repositories are enabled: $ cat /etc/apt/sources.list.d/ddebs.list deb http://ddebs.ubuntu.com bionic main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse When manually inspecting the apt repository for `bionic-updates`[1], the timestamp is 5/19/2020 (prior to the libssl update on ~5/27), and the only libssl1.1-dbgsym entry is: Package: libssl1.1-dbgsym Package-Type: ddeb Architecture: amd64 Version: 1.1.1-1ubuntu2.1~18.04.5 Meanwhile, I'm unable to find any policy information online about how frequently the ddebs repositories get updated. [1] http://ddebs.ubuntu.com/dists/bionic-updates/main/binary- amd64/Packages.gz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libssl1.1 1.1.1-1ubuntu2.1~18.04.6 Uname: Linux 5.5.17-1rodete4-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Fri May 29 08:47:51 2020 ProcEnviron: LD_LIBRARY_PATH= TERM=xterm PATH=(custom, user) SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1881314/+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 1881314] [NEW] libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04
Public bug reported: After a recent update: $ apt-get install libssl1.1-dbgsym The following packages have unmet dependencies: libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.5) but 1.1.1-1ubuntu2.1~18.04.6 is to be installed E: Unable to correct problems, you have held broken packages. The following debug repositories are enabled: $ cat /etc/apt/sources.list.d/ddebs.list deb http://ddebs.ubuntu.com bionic main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse When manually inspecting the apt repository for `bionic-updates`[1], the timestamp is 5/19/2020 (prior to the libssl update on ~5/27), and the only libssl1.1-dbgsym entry is: Package: libssl1.1-dbgsym Package-Type: ddeb Architecture: amd64 Version: 1.1.1-1ubuntu2.1~18.04.5 Meanwhile, I'm unable to find any policy information online about how frequently the ddebs repositories get updated. [1] http://ddebs.ubuntu.com/dists/bionic-updates/main/binary- amd64/Packages.gz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libssl1.1 1.1.1-1ubuntu2.1~18.04.6 Uname: Linux 5.5.17-1rodete4-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Fri May 29 08:47:51 2020 ProcEnviron: LD_LIBRARY_PATH= TERM=xterm PATH=(custom, user) SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1881314 Title: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04 Status in openssl package in Ubuntu: New Bug description: After a recent update: $ apt-get install libssl1.1-dbgsym The following packages have unmet dependencies: libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.5) but 1.1.1-1ubuntu2.1~18.04.6 is to be installed E: Unable to correct problems, you have held broken packages. The following debug repositories are enabled: $ cat /etc/apt/sources.list.d/ddebs.list deb http://ddebs.ubuntu.com bionic main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse When manually inspecting the apt repository for `bionic-updates`[1], the timestamp is 5/19/2020 (prior to the libssl update on ~5/27), and the only libssl1.1-dbgsym entry is: Package: libssl1.1-dbgsym Package-Type: ddeb Architecture: amd64 Version: 1.1.1-1ubuntu2.1~18.04.5 Meanwhile, I'm unable to find any policy information online about how frequently the ddebs repositories get updated. [1] http://ddebs.ubuntu.com/dists/bionic-updates/main/binary- amd64/Packages.gz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libssl1.1 1.1.1-1ubuntu2.1~18.04.6 Uname: Linux 5.5.17-1rodete4-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Fri May 29 08:47:51 2020 ProcEnviron: LD_LIBRARY_PATH= TERM=xterm PATH=(custom, user) SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1881314/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
(I'm not using Ubuntu for my desktop but I'have had the same problem. I'm running Pulseaudio 13 built with enable_bluez5_native_headset and Bluez 5.54) Solved it by adding headset=native forthe module module-bluetooth-discover in default.pa : load-module module-bluetooth-discover headset=native in ~/.pulse/default.pa (or /etc/pulse/default.pa) then restarting pulseaudio with pulseaudio -k Since Pulseaudio 11.0 has ofono support, "headset=auto" option enabled by default, pactl list shows that both profiles with available: yes Generally when using VoIP application automatically switch bluetooth profile to HSP works , but when not or when switch back to A2DP need to be done annually (for me, Blueman does the job with a few clicks). Sound with HSP profile isn't very good and HFP doesn't seems to work as I haven't setup phonesimp (ref https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Bluetooth/ ) -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1879087] Re: dbus errors, frequent roaming and unstable connectivity
Thank you for taking care of this so swiftly. I don't believe I have much to add to the test-case. From testing locally I can see that the warnings disappear from the log and the connection _seems_ more stable. I underscore _seems_ because I have not been able to figure out which other parts of the system are actually using these particular dbus messages, if any. If nobody is actually using these, the perceived improvement could be placebo. I will keep testing though, because I've generally been struggling with a stable wifi connection on 20.04. Thanks again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1879087 Title: dbus errors, frequent roaming and unstable connectivity Status in wpa package in Ubuntu: Fix Committed Bug description: * Impact extra roaming events are been generated * Test case check the wpa_supplicant log, it should have warnings dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 the roaming events should not be too frequent * Regression potential check that wifi connection keep working correctly -- When using this version of wpa_supplicant with my company WPA2-Enterprise wireless setup, I'm experiencing far too frequent roaming events (even when not moving around) accompanied by hiccups in connectivity. I also see these messages in the wpa_supplicant log: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Having done a little research, at least the dbus errors seem to be fixed by this commit upstream: https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756 So I built a version of wpa_supplicant including this particular patch and installed on my machine. Apart from solving the dbus errors completely, it seems to have had a positive impact on the frequent roaming and unstable connectivity as well (I've run for a day with no burst of roaming events at all, where they used to happen every few minutes most of the time.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 16 16:47:27 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+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 1553669] Re: Annoying "call from" message when connecting Bose devices
I've had this issue since 16.04. How is it that we've gone through 3 LTS releases without a fix? What is the technical challenge with getting a Bluetooth LE headset paired for use as a headset? What is going on? -- 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/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+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 1879087] [NEW] dbus errors, frequent roaming and unstable connectivity
Public bug reported: When using this version of wpa_supplicant with my company WPA2-Enterprise wireless setup, I'm experiencing far too frequent roaming events (even when not moving around) accompanied by hiccups in connectivity. I also see these messages in the wpa_supplicant log: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Having done a little research, at least the dbus errors seem to be fixed by this commit upstream: https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756 So I built a version of wpa_supplicant including this particular patch and installed on my machine. Apart from solving the dbus errors completely, it seems to have had a positive impact on the frequent roaming and unstable connectivity as well (I've run for a day with no burst of roaming events at all, where they used to happen every few minutes most of the time.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 16 16:47:27 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1879087 Title: dbus errors, frequent roaming and unstable connectivity Status in wpa package in Ubuntu: New Bug description: When using this version of wpa_supplicant with my company WPA2-Enterprise wireless setup, I'm experiencing far too frequent roaming events (even when not moving around) accompanied by hiccups in connectivity. I also see these messages in the wpa_supplicant log: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Having done a little research, at least the dbus errors seem to be fixed by this commit upstream: https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756 So I built a version of wpa_supplicant including this particular patch and installed on my machine. Apart from solving the dbus errors completely, it seems to have had a positive impact on the frequent roaming and unstable connectivity as well (I've run for a day with no burst of roaming events at all, where they used to happen every few minutes most of the time.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 16 16:47:27 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+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 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
Still an issue in the latest Ubuntu 20.04 release. User winds up having to click the toggle over and over again while it stubbornly snaps back. Replicated on Many different machines with different hardware. Is there anyone who can not replicate this bug? ** Changed in: bluez (Ubuntu) Status: Expired => Confirmed -- 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/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Confirmed Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+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 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed
Just to clear out what the intended behavior should be: Automatically switch to HSP/HFP when an application is requesting to record the microphone. When it stops, revert back to A2DP. This is how this works in other operating systems so this is what we should aim for also in here. A2DP with a microphone is wishful thinking and should not be pursued after. -- 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/508522 Title: Add automatic switching to HSP/HFP from A2DP when a mic is needed Status in PulseAudio: New Status in chromium-browser package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed
Can you please describe how can I enable automatic switching? Using Bose QC35 and fresh Ubuntu 20.04. I need to manually set the profile when calling with MS Teasm, Google Meet, Zoom etc. This works in Windows and MacOS perfectly so it is supported by the device. -- 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/508522 Title: Add automatic switching to HSP/HFP from A2DP when a mic is needed Status in PulseAudio: New Status in chromium-browser package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1875407] [NEW] package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Received this error when doing do-release-upgrade from ubuntu 18.04.4 to 20.4 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 27 09:59:42 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-01-12 (1567 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-04-27 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1875407 Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Received this error when doing do-release-upgrade from ubuntu 18.04.4 to 20.4 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 27 09:59:42 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-01-12 (1567 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-04-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1875407/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
I still get this issue even on focal, or atleast the fix is the same. I have a USB headset and upon reboot it always switches to the USB headset regardless if HDMI was selected last. It's a desktop so things don't get unplugged. -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1863158] [NEW] UTF-8 Encoding errors with Security patch in 2.9.4+dfsg1-6.1ubuntu1.3
Public bug reported: I'm using libxml2 via perl-bindings in XML::LibXML. After upgrading to 2.9.4+dfsg1-6.1ubuntu1.3 my perl-scripts threw many UTF-8 encoding errors, e.g. "Malformed UTF-8 character: \xb0 (unexpected continuation byte 0xb0, with no preceding start byte." Re-installing libxml2.so.2.9.4 from 2.9.4+dfsg1-6.1ubuntu1.2 and linking libxml2.so.2 to this file without changing anything else lead to error- free execution of the perl-scripts: All Unicode characters are ok. At present, I'm not able to reduce the error situation in such a way that a simple perl script can be given which reproduces this error - I'm working on this. I'm also not able to provide an error description using libxml2 directly, without perl. So, please be patient with me and this stumbling bug-report. My system is: Description:Ubuntu 18.04.4 LTS Release:18.04 ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1863158 Title: UTF-8 Encoding errors with Security patch in 2.9.4+dfsg1-6.1ubuntu1.3 Status in libxml2 package in Ubuntu: New Bug description: I'm using libxml2 via perl-bindings in XML::LibXML. After upgrading to 2.9.4+dfsg1-6.1ubuntu1.3 my perl-scripts threw many UTF-8 encoding errors, e.g. "Malformed UTF-8 character: \xb0 (unexpected continuation byte 0xb0, with no preceding start byte." Re-installing libxml2.so.2.9.4 from 2.9.4+dfsg1-6.1ubuntu1.2 and linking libxml2.so.2 to this file without changing anything else lead to error-free execution of the perl-scripts: All Unicode characters are ok. At present, I'm not able to reduce the error situation in such a way that a simple perl script can be given which reproduces this error - I'm working on this. I'm also not able to provide an error description using libxml2 directly, without perl. So, please be patient with me and this stumbling bug-report. My system is: Description:Ubuntu 18.04.4 LTS Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1863158/+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 1813266] Re: udhcpd: not dying on SIGTERM
Anyway to raise the priority on this?, almost two years since the bug was fixed in busybox but ubuntu has not picked the patch. I had to update the service stop script to do a pkill -9 udhcpd but that is not ideal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1813266 Title: udhcpd: not dying on SIGTERM Status in busybox package in Ubuntu: Confirmed Bug description: udhcpd in bionic does not stop on SIGTERM due to an upstream change. This was corrected by the following patch: https://git.busybox.net/busybox/commit/?id=3293bc146985c56790033409facc0ad64a471084 Please apply and backport/SRU this change to bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1813266/+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 1850806] [NEW] Ubuntu Software Centre (gnome-software) search function semi-broken
Public bug reported: Ubuntu version: Description:Ubuntu 19.10 Release:19.10 Package version: ubuntu-software: Installed: 3.30.6-2ubuntu10 Candidate: 3.30.6-2ubuntu10 Version table: *** 3.30.6-2ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status Expected behaviour: Typing in a search query returns results What happened instead: Half the time, Ubuntu Software returns "no results" Work-around(ish): Delete a letter or two out of the search query ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1850806 Title: Ubuntu Software Centre (gnome-software) search function semi-broken Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: Description: Ubuntu 19.10 Release: 19.10 Package version: ubuntu-software: Installed: 3.30.6-2ubuntu10 Candidate: 3.30.6-2ubuntu10 Version table: *** 3.30.6-2ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status Expected behaviour: Typing in a search query returns results What happened instead: Half the time, Ubuntu Software returns "no results" Work-around(ish): Delete a letter or two out of the search query To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850806/+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 1850805] [NEW] PulseAudio resets output device to RX 580 HDMI every reboot
Public bug reported: Ubuntu version: Description:Ubuntu 19.10 Release:19.10 PulseAudio version: pulseaudio: Installed: 1:13.0-1ubuntu1 Candidate: 1:13.0-1ubuntu1 Version table: *** 1:13.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Expected behavior: Selected output device does not change after reboot What happened instead: When Ubuntu reboots, Pulse returns the output to RX 580's HDMI/DisplayPort device ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1850805 Title: PulseAudio resets output device to RX 580 HDMI every reboot Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: Description: Ubuntu 19.10 Release: 19.10 PulseAudio version: pulseaudio: Installed: 1:13.0-1ubuntu1 Candidate: 1:13.0-1ubuntu1 Version table: *** 1:13.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Expected behavior: Selected output device does not change after reboot What happened instead: When Ubuntu reboots, Pulse returns the output to RX 580's HDMI/DisplayPort device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850805/+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 1773087] Re: Remove python3-apport as dependency of xserver-xorg
sordna, regarding your specific problem, please file a bug against apport via a terminal: ubuntu-bug apport In this new report, please copy/paste the reproduction steps, and result as per terminal command. -- 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/1773087 Title: Remove python3-apport as dependency of xserver-xorg Status in xorg package in Ubuntu: Invalid Bug description: Distro: Bionic Binary Package: xserver-xorg Version: 1:7.7+19ubuntu7 Hello! The package xserver-xorg depends on python3-apport. I don't want to use apport on my systems. Can the dependency be removed? Also, it doesn't work anyway. That's how I noticed that the package is installed: root@00debac04ddf:~# foo Traceback (most recent call last): File "/usr/bin/foo", line 3, in raise Exception Exception Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 145, in apport_excepthook os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f: FileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_bin_foo.0.crash' Original exception was: Traceback (most recent call last): File "/usr/bin/foo", line 3, in raise Exception Exception Thanks Jörn Heissler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773087/+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 1275042] Re: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC
** No longer affects: mesa (Ubuntu) ** Project changed: mesa => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: Unknown => New ** Changed in: mesa (Ubuntu) Remote watch: freedesktop.org Bugzilla #72877 => None ** Changed in: mesa (Ubuntu) Status: New => Triaged ** Description changed: - Hi all, + Upstream report: + https://gitlab.freedesktop.org/mesa/mesa/issues/477 I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this translating code but IBM pSeries machines without graphics cards need this code. This code translates the colors in a wrong way for Radeon graphics cards. I removed this code and after compiling Mesa again, the colors are displayed correctly. I released some unofficial Mesa versions with this patch. Downloads: http://www.supertuxkart-amiga.de/amiga/mesalib- unofficial.html Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU "Xena" 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM XFX Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian --- ApportVersion: 2.20-0ubuntu3 Architecture: powerpc CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Barts XT [Radeon HD 6870] [1682:3107] Package: libgl1-mesa-dri 11.1.2-1ubuntu1 PackageArchitecture: powerpc ProcKernelCmdLine: root=/dev/sdb1 quiet ro splash ProcModules: kvm_pr 91899 0 - Live 0x Tags: xenial ubuntu Uname: Linux 4.5.0-rc6_A-EON_AmigaONE_X1000_Nemo ppc64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1275042 Title: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC Status in mesa package in Ubuntu: Triaged Bug description: Upstream report: https://gitlab.freedesktop.org/mesa/mesa/issues/477 I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this
