[Desktop-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
Upstream seems replaced the comment#7 by https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/596 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965215] Re: [81FD, Realtek ALC236, Black Mic, Right] The external microphone is not detected
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1965215 Title: [81FD, Realtek ALC236, Black Mic, Right] The external microphone is not detected Status in alsa-driver package in Ubuntu: New Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 When inserted in the 3.5mm phone jack, the external microphone is not detected, and thus the audio input doesn't auto-switch from the internal microphone to the external microphone. The problem probably is related to the kernel version, as kernels 5.11.0-34, 5.11.0-36,5.11.0-37 and 5.11.0-38 works as expected, but kernels 5.4.0-104, 5.11.0-40, 5.11.0-41, 5.11.0-43, 5.11.0-44, 5.11.0-46, 5.13.0-30 and 5.13.0-35 don't. A similar problem happens for Debian 11. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thales 1485 F pulseaudio /dev/snd/pcmC0D0p: thales 1485 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 00:07:20 2022 InstallationDate: Installed on 2022-03-09 (7 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_Type: No auto-switch between inputs Title: [81FD, Realtek ALC236, Black Mic, Right] No autoswitch UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2021 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: 8RCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.ec.firmware.release: 1.58 dmi.modalias: dmi:bvnLENOVO:bvr8RCN58WW:bd05/19/2021:br1.58:efr1.58:svnLENOVO:pn81FD:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81FD_BU_idea_FM_ideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81FD dmi.product.sku: LENOVO_MT_81FD_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password Status in xorg package in Ubuntu: New Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1965219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1965215] [NEW] [81FD, Realtek ALC236, Black Mic, Right] The external microphone is not detected
You have been subscribed to a public bug: Description:Ubuntu 20.04.4 LTS Release:20.04 When inserted in the 3.5mm phone jack, the external microphone is not detected, and thus the audio input doesn't auto-switch from the internal microphone to the external microphone. The problem probably is related to the kernel version, as kernels 5.11.0-34, 5.11.0-36,5.11.0-37 and 5.11.0-38 works as expected, but kernels 5.4.0-104, 5.11.0-40, 5.11.0-41, 5.11.0-43, 5.11.0-44, 5.11.0-46, 5.13.0-30 and 5.13.0-35 don't. A similar problem happens for Debian 11. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thales 1485 F pulseaudio /dev/snd/pcmC0D0p: thales 1485 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 00:07:20 2022 InstallationDate: Installed on 2022-03-09 (7 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_Type: No auto-switch between inputs Title: [81FD, Realtek ALC236, Black Mic, Right] No autoswitch UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2021 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: 8RCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.ec.firmware.release: 1.58 dmi.modalias: dmi:bvnLENOVO:bvr8RCN58WW:bd05/19/2021:br1.58:efr1.58:svnLENOVO:pn81FD:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81FD_BU_idea_FM_ideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81FD dmi.product.sku: LENOVO_MT_81FD_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- [81FD, Realtek ALC236, Black Mic, Right] The external microphone is not detected https://bugs.launchpad.net/bugs/1965215 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965219] [NEW] gnome lock screen does not permit reentering password
You have been subscribed to a public bug: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- gnome lock screen does not permit reentering password https://bugs.launchpad.net/bugs/1965219 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964532] Re: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected
This occurs every time I reboot my system - Ubuntu Mate 22.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1964532 Title: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected Status in udisks2 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding udisks2. This problem was most recently seen with package version 2.9.4-1, the problem page at https://errors.ubuntu.com/problem/ee70e42ef96a41e0ae118869c75b7cc675ae974c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1964532/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965214] Re: keep getting asked to set a Primary Password?
Sigh. Please close ticket. After hitting Send I went and looked at Preferences again and NOW I see there's a Security section where you can turn off the Primary Password feature. Sorry for wasting your time. :-/ Jason ** Changed in: remmina (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1965214 Title: keep getting asked to set a Primary Password? Status in remmina package in Ubuntu: Invalid Bug description: Under Ubuntu-22.04beta I am continually getting prompted to set what I assume is a master password for remmina cred changes. The issue is that I have it configured to save to gnome-keyring. And if I bring up that gnome-keyring I can see the remmina creds I've saved in there - so all is good on that front. ie the gnome-keyring and whatever this "primary password" thing is are doing the same thing and only one should win - the latter should be disabled. There doesn't seem to be any way to disable it - I am just hitting cancel and it keeps popping up later. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: remmina 1.4.24+dfsg-2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 16:06:00 2022 InstallationDate: Installed on 2022-03-13 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1965214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965214] [NEW] keep getting asked to set a Primary Password?
Public bug reported: Under Ubuntu-22.04beta I am continually getting prompted to set what I assume is a master password for remmina cred changes. The issue is that I have it configured to save to gnome-keyring. And if I bring up that gnome-keyring I can see the remmina creds I've saved in there - so all is good on that front. ie the gnome-keyring and whatever this "primary password" thing is are doing the same thing and only one should win - the latter should be disabled. There doesn't seem to be any way to disable it - I am just hitting cancel and it keeps popping up later. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: remmina 1.4.24+dfsg-2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 16:06:00 2022 InstallationDate: Installed on 2022-03-13 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: remmina (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1965214 Title: keep getting asked to set a Primary Password? Status in remmina package in Ubuntu: Invalid Bug description: Under Ubuntu-22.04beta I am continually getting prompted to set what I assume is a master password for remmina cred changes. The issue is that I have it configured to save to gnome-keyring. And if I bring up that gnome-keyring I can see the remmina creds I've saved in there - so all is good on that front. ie the gnome-keyring and whatever this "primary password" thing is are doing the same thing and only one should win - the latter should be disabled. There doesn't seem to be any way to disable it - I am just hitting cancel and it keeps popping up later. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: remmina 1.4.24+dfsg-2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 16:06:00 2022 InstallationDate: Installed on 2022-03-13 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1965214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962624] Re: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected
*** This bug is a duplicate of bug 1955758 *** https://bugs.launchpad.net/bugs/1955758 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: udisks2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1962624 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in udisks2 package in Ubuntu: Confirmed Bug description: automatically created data, did not look into it. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.chromium.rules Date: Thu Feb 24 23:58:25 2022 ExecutablePath: /usr/libexec/udisks2/udisksd InstallationDate: Installed on 2018-12-10 (1177 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MEDION DEFENDER P10 ProcCmdline: /usr/libexec/udisks2/udisksd ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/mapper/newroot Signal: 6 SourcePackage: udisks2 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7febbba0db8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7febbba105d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7febbba46c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7febbba46c80 , p=0x5627404144c0, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 08/29/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RME1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH77Dx dmi.board.vendor: MEDION dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd08/29/2020:br7.5:efr7.1:svnMEDION:pnDEFENDERP10:pvrNotApplicable:rvnMEDION:rnNH77Dx:rvrNotApplicable:cvnMEDION:ct10:cvrN/A:skuML-21000930028862: dmi.product.family: Erazer dmi.product.name: DEFENDER P10 dmi.product.sku: ML-210009 30028862 dmi.product.version: Not Applicable dmi.sys.vendor: MEDION separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1962624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965208] [NEW] Ubuntu dock is visible too early during the login animation in Xorg sessions
Public bug reported: Ubuntu dock is visible too early during the login animation in Xorg sessions. It appears immediately, disappears, then appears again. This also explains why the login animation is so stuttery in Xorg compared to Wayland. ** Affects: gnome-shell (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: New ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: New ** Tags: jammy performance visual-quality ** Tags added: jammy ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Description changed: Ubuntu dock is visible too early during the login animation in Xorg sessions. - It appears immediately, disappears, then animates in again. + It appears immediately, disappears, then appears again. This also explains why the login animation is so stuttery in Xorg compared to Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965208 Title: Ubuntu dock is visible too early during the login animation in Xorg sessions Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu dock is visible too early during the login animation in Xorg sessions. It appears immediately, disappears, then appears again. This also explains why the login animation is so stuttery in Xorg compared to Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964532] Re: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: udisks2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1964532 Title: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected Status in udisks2 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding udisks2. This problem was most recently seen with package version 2.9.4-1, the problem page at https://errors.ubuntu.com/problem/ee70e42ef96a41e0ae118869c75b7cc675ae974c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1964532/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965210] [NEW] Grey (gray) panel menus don't contrast with the grey login screen
Public bug reported: Grey (gray) panel menus don't contrast with the grey login screen. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: jammy visual-quality ** Tags added: jammy visual-quality -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1965210 Title: Grey (gray) panel menus don't contrast with the grey login screen Status in yaru-theme package in Ubuntu: New Bug description: Grey (gray) panel menus don't contrast with the grey login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1965210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965113] Re: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions
Failing again. It only fails in Xorg sessions after I've launched it in a Wayland session and then logged out. 1. Log into a Wayland session and launch Firefox. 2. Log into a Xorg session and Firefox can't start. 'snap connections firefox' shows as connected?; x11firefox:x11:x11 Rebooting fixes the problem. I can launch Firefox again. ** Summary changed: - Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions + Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions if a Wayland session has been used -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1965113 Title: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions if a Wayland session has been used Status in firefox package in Ubuntu: New Bug description: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions. $ /snap/bin/firefox Error: cannot open display: :0 $ echo $DISPLAY :0 And other X11 apps still work just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1965113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965207] [NEW] The spinner animation in the panel has hiccups and jumps periodically
Public bug reported: The spinner animation in the panel (when an app is launching) has hiccups and jumps periodically. You'll need to launch a big/slow app to see the issue though. Seems to happen with Firefox for me. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1965207 Title: The spinner animation in the panel has hiccups and jumps periodically Status in yaru-theme package in Ubuntu: New Bug description: The spinner animation in the panel (when an app is launching) has hiccups and jumps periodically. You'll need to launch a big/slow app to see the issue though. Seems to happen with Firefox for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1965207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965113] Re: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions
And today it just works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1965113 Title: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions Status in firefox package in Ubuntu: New Bug description: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions. $ /snap/bin/firefox Error: cannot open display: :0 $ echo $DISPLAY :0 And other X11 apps still work just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1965113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965116] Re: Desktop lockup with because Wayland compositor not fast enough
Thanks for the bug report. Next time a freeze happens please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt lspci -k > lspci.txt 4. Attach the resulting text files here. 5. Run: apport-collect 1965116 6. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 7. If step 6 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. ** Summary changed: - Desktop lockup with because Wayland compositor not fast enough + Desktop lockup ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1965116 Title: Desktop lockup Status in gnome-shell package in Ubuntu: Incomplete Bug description: I use Ubuntu 21.10 with Wayland and nvidia drivers. Sometimes, when working, the desktop freezes. Over ssh, I can see in the system logs many of those messages: > gnome-shell[5615]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! dmesg doesn't show any problems. Xwayland has a very high CPU usage. Killing Xwayland didn't help. When I then restart gdm, logging in either works again, or at least gdm allows a graceful reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965123] Re: Active launchers area pixels missing
I can't seem to reproduce the issue yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965123 Title: Active launchers area pixels missing Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 22.04 development branch @ 16/03/2022 after yesterdays updates to gnome 42 beta the docks area around the active launcher is missing 4 pixels in the corners when hovering mouse over them switching to another active launchers can be reproduced non-active area around launchers does not suffer this bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 12:55:20 2022 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965085] Re: Login screen sometimes unresponsive to mouse clicks (after waking from sleep)
Maybe related to bug 1964545 somehow? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965085 Title: Login screen sometimes unresponsive to mouse clicks (after waking from sleep) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: The login screen is sometimes unresponsive to mouse clicks (after waking from sleep). I can generally get it working again either by hitting Tab, or by switching VTs. Seems to happen with either Wayland or Xorg greeters. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 16 14:07:16 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-05 (130 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964279] Re: the output PDF is abnormal
>Please add the --verbose flag to scanimage, and attach the output. The outputs is as below scanimage --mode color --format=pdf --batch-count=1 --verbose Scanning 1 page, incrementing by 1, numbering from 1 Scanning page 1 scanimage: scanning image of size 424x774 pixels at 24 bits/pixel scanimage: acquiring RGB frame scanimage: min/max graylevel value = 33/255 scanimage: read 984528 bytes in total Scanned page 1. (scanner status = 5) Batch terminated, 1 page scanned >Is this issue only with PDF? If you use --format=jpeg instead, are you able to open the image? If I use --format=jpeg instead, I am able to open the image. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1964279 Title: the output PDF is abnormal Status in sane-backends package in Ubuntu: New Bug description: When batch-count is set to 1, the output PDF cannot be opened with the PDF tool. The command line is as follows scanimage --mode color --format=pdf --batch-count=1 When mode is set to gray or lineart, the output PDF is abnormal. (there were three images in one sheet of PDF) The command line is as follows scanimage --mode gray --format=pdf --batch scanimage --mode lineart --format=pdf --batch ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: sane-utils 1.1.1-3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 17:43:59 2022 InstallationDate: Installed on 2022-03-03 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1964279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.6.1 --- ubuntu-drivers-common (1:0.9.6.1) jammy; urgency=medium * UbuntuDrivers/detect.py: - Handle Production branches (PB) (LP: #1964747). - Always prefer PB and LTSB, and pick the highest of the two whenever possible. * tests/test_ubuntu_drivers.py: - Add test_system_driver_packages_chroot_support_branch_pb and test_system_driver_packages_chroot_support_branch_pb_1, to keep track of our policy on PB and LTSB releases. -- Alberto Milone Wed, 16 Mar 2022 15:59:19 +0100 ** Changed in: ubuntu-drivers-common (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Impish: In Progress Bug description: [Impact] * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. [Test Plan] * ubuntu-drivers debug ``` ... === matching driver packages === nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] ... nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB ... ``` * As you can see, "(auto-install)" is point to 470 because of it owns LTSB tag. [Fix] * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. [Where problems could occur] * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. --- + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965190] Re: software centre search is non-obvious
I just notice the search icon to the top left of the title bar. No, No and No. The search should be front and centre not in the title bar. FYI my actually close icon is on the right-hand side. I can't remember if this is standard gnome or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1965190 Title: software centre search is non-obvious Status in gnome-software package in Ubuntu: New Bug description: Every time I go to install software from the software centre I find the interface less than intuitive. I'm expecting the home page to have a search button. Instead, it has a spotify banner, a set of editors' picks and a list of categories. This is all great and all but I know the name of the software, I just want to search for it. Please add a large obvious search bar between the spotify ad and the list of editors' picks. lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1965190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965190] [NEW] software centre search is non-obvious
Public bug reported: Every time I go to install software from the software centre I find the interface less than intuitive. I'm expecting the home page to have a search button. Instead, it has a spotify banner, a set of editors' picks and a list of categories. This is all great and all but I know the name of the software, I just want to search for it. Please add a large obvious search bar between the spotify ad and the list of editors' picks. lsb_release -rd Description:Ubuntu 21.10 Release:21.10 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1965190 Title: software centre search is non-obvious Status in gnome-software package in Ubuntu: New Bug description: Every time I go to install software from the software centre I find the interface less than intuitive. I'm expecting the home page to have a search button. Instead, it has a spotify banner, a set of editors' picks and a list of categories. This is all great and all but I know the name of the software, I just want to search for it. Please add a large obvious search bar between the spotify ad and the list of editors' picks. lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1965190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965168] Re: jammy community competition wallpapers
** Changed in: ubuntu-wallpapers (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1965168 Title: jammy community competition wallpapers Status in ubuntu-wallpapers package in Ubuntu: Triaged Bug description: We have the winning images, in full size and both under CC by SA 4.0 The author of the first image is Elena Stravoravdi The author of the remaining images, both light and dark mode, is by hiking93 If it is possible, we would like to include both the light and dark mode of the jellyfish image. If there is not enough room, please only include the light jellyfish image. Let me know if there are any other concerns or questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965138] Re: Desktop application should check for service available information before listing it
The following PR should hopefully fix this: https://github.com/canonical/ubuntu-advantage-desktop-daemon/pull/14 ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: New => In Progress ** Package changed: software-properties (Ubuntu) => ubuntu-advantage- desktop-daemon (Ubuntu) ** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-advantage-desktop-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1965138 Title: Desktop application should check for service available information before listing it Status in ubuntu-advantage-desktop-daemon package in Ubuntu: In Progress Bug description: Currently, it seems that software-properties is incorrectly assuming that both ESM and Livepatch services can be enabled in a Jammy machine. Those services are not yet available in Jammy and we are attaching an image showing that the Desktop message is that we had an error enabling then and that the user should try again. It seems that software-proporties source `/var/lib/ubuntu- advantage/status.json` and assumes the services is available if it appears on the services list and the `entitled` field has the `yes` value. However, it is perfectly possible for a service to be entitled to an user, but not available in the user's machine. We are now suggesting that software-properties also looks at the `available` field in the services json output to make that assumption, this will probably solve the issue we are seeing on Jammy. Another approach would be using the output of `ua status --format json` directly. However, this command will make a request to the contract's server if the user is unattached and maybe it is not wise to use it in that context. However, the output of that command only show services that are available, so we would not need to apply that extra available filter to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/1965138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965189] [NEW] Add session migration for GNOME 42 dark theme
Public bug reported: Test Case - 1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance and choose Dark 2. Upgrade to Ubuntu 22.04 LTS 3. Your apps should still be dark Linked Issue That test case is broken by the libhandy update. See LP: #1964841 We are updating gnome-control-center to set the correct gsettings value (below) when choosing a dark theme. Implementation -- We need to set gsettings org.gnome.desktop.interface color-scheme 'prefer-dark' for users using a theme name ending in "-dark" That gsettings schema is provided by gsettings-desktop-schemas. I don't think we should do this in ubuntu-settings because there are people using GTK desktops that don't have ubuntu-settings installed. I suggest we use dh-migrations/session-migration to do this from gnome- settings-daemon. Let me know now if there is a better place for this. ** Affects: gnome-settings-daemon (Ubuntu) Importance: High Assignee: Jeremy Bicha (jbicha) Status: In Progress ** Affects: gnome-settings-daemon (Ubuntu Jammy) Importance: High Assignee: Jeremy Bicha (jbicha) Status: In Progress ** Tags: jammy ** Also affects: gnome-settings-daemon (Ubuntu Jammy) Importance: High Assignee: Jeremy Bicha (jbicha) Status: In Progress ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1965189 Title: Add session migration for GNOME 42 dark theme Status in gnome-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Jammy: In Progress Bug description: Test Case - 1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance and choose Dark 2. Upgrade to Ubuntu 22.04 LTS 3. Your apps should still be dark Linked Issue That test case is broken by the libhandy update. See LP: #1964841 We are updating gnome-control-center to set the correct gsettings value (below) when choosing a dark theme. Implementation -- We need to set gsettings org.gnome.desktop.interface color-scheme 'prefer-dark' for users using a theme name ending in "-dark" That gsettings schema is provided by gsettings-desktop-schemas. I don't think we should do this in ubuntu-settings because there are people using GTK desktops that don't have ubuntu-settings installed. I suggest we use dh-migrations/session-migration to do this from gnome-settings-daemon. Let me know now if there is a better place for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1965189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965188] [NEW] Policies not being picked up anymore
Public bug reported: Description: Ubuntu 20.04.4 LTS Release: 20.04 chromium 99.0.4844.51 1926 latest/stable canonical✓ I think with Chrome 99 manged policies in a json file are broken, they no longer seem to be picked up (used to work for me which a script I wrote). When one follows Chrome's documentation to use policies, it does not work: https://www.chromium.org/administrators/linux-quick-start/ If snap mutates various path's and changes various things, I hope this layer of obfuscation is documented somewhere? I could not find it. Similar to this issue but none of the paths in this issue work for me anymore: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244 I have tried many combos of dirs/permissions from stackoverflow and bug reports but they don't seem to work. I don't know what snap is doing to Chromium behind the scenes, and perhaps it seems undocumented? Apologies if it is documentented (but can't find it). ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1965188 Title: Policies not being picked up anymore Status in chromium-browser package in Ubuntu: New Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 chromium 99.0.4844.51 1926 latest/stable canonical✓ I think with Chrome 99 manged policies in a json file are broken, they no longer seem to be picked up (used to work for me which a script I wrote). When one follows Chrome's documentation to use policies, it does not work: https://www.chromium.org/administrators/linux-quick- start/ If snap mutates various path's and changes various things, I hope this layer of obfuscation is documented somewhere? I could not find it. Similar to this issue but none of the paths in this issue work for me anymore: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244 I have tried many combos of dirs/permissions from stackoverflow and bug reports but they don't seem to work. I don't know what snap is doing to Chromium behind the scenes, and perhaps it seems undocumented? Apologies if it is documentented (but can't find it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1965188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895383] Re: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shared-mime-info (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1895383 Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1 Status in shared-mime-info package in Ubuntu: Confirmed Bug description: Failure occurred on update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: shared-mime-info 1.15-1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: bcompare:amd64: Install r-cran-mass:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 12 19:29:30 2020 DuplicateSignature: package:shared-mime-info:1.15-1 Processing triggers for shared-mime-info (1.15-1) ... Failed to rename /usr/share/mime/inode/socket.xml.new as /usr/share/mime/inode/socket.xml: No such file or directory dpkg: error processing package shared-mime-info (--configure): installed shared-mime-info package post-installation script subprocess returned error exit status 1 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-07 (127 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1895383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965186] [NEW] Snap changes the specified user data on it own accord
Public bug reported: Description:Ubuntu 20.04.4 LTS Release:20.04 chromium 99.0.4844.51 1926 latest/stable canonical✓ - When starting chromium-browser, I specify the --user-data- dir=/path/to/special/location, but the snap installation (took me awhile to figure out was not apt, but sneaky snap), takes the liberty of adding '--user-data-dir=/home/guest/snap/chromium/common/chromium' directly after my flag. Well there is a good reason I set the user-data-dir, because its on a terminal with OverlayFS (a read only file system), and there is a separate partion for read/write that I point it to, so it maintains the data between reboots. Please don't override peoples required preferences. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1965186 Title: Snap changes the specified user data on it own accord Status in chromium-browser package in Ubuntu: New Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 chromium 99.0.4844.51 1926 latest/stable canonical✓ - When starting chromium-browser, I specify the --user-data- dir=/path/to/special/location, but the snap installation (took me awhile to figure out was not apt, but sneaky snap), takes the liberty of adding '--user-data-dir=/home/guest/snap/chromium/common/chromium' directly after my flag. Well there is a good reason I set the user-data-dir, because its on a terminal with OverlayFS (a read only file system), and there is a separate partion for read/write that I point it to, so it maintains the data between reboots. Please don't override peoples required preferences. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1965186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965067] Re: [42beta] gnome-disks does not respect gtk theme
Hi Sebastien, Thankyou for your suggestion about libhandy-1. I had 1.5.91-2 installed. I downgraded to 1.5.91-1 and my issue vanished, nautilus, gnome-disks and calendar are back to dark theme now. On 1.5.91-2, toggling back and forth between light and dark did not do anything. Tagging regression-proposed. ** No longer affects: gnome-disk-utility (Ubuntu) ** Also affects: libhandy-1 (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-disk-utility (Ubuntu Jammy) ** Changed in: libhandy-1 (Ubuntu Jammy) Importance: Undecided => High ** Tags added: regression-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1965067 Title: [42beta] (some) GNOME applications use light theme when dark is set in gnome-control-center Status in libhandy-1 package in Ubuntu: New Status in libhandy-1 source package in Jammy: New Bug description: gnome-disks does not apply the Yaru theme, when all other GNOME applications respect the default theme. See attached screenshot. gnome-disks 42~rc-1ubuntu1 gnome-shell 42~beta-1ubuntu2 yaru-theme-gtk 22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhandy-1/+bug/1965067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965180] [NEW] apt-add-repository requires --login for private repos, breaking automated workflows
Public bug reported:
On Focal, in an automated environment (such as a launchpad builder), a
used can do the following workflow:
curl
"https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu focal main"
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64 Packages
[3288 B]
Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main Translation-en
[1892 B]
However, on Jammy, I get the following:
curl "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu jammy main"
Repository: 'deb https://private-ppa.launchpad.net/$REPO/ubuntu jammy main'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 105, in
lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line
592, in __call__
response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
429, in _request
raise error
lazr.restfulclient.errors.NotFound: HTTP Error 404: Not Found
Response headers:
---
-content-encoding: gzip
content-length: 91
content-type: text/plain;charset=utf-8
date: Wed, 16 Mar 2022 19:54:16 GMT
server: gunicorn/19.8.1
status: 404
vary: Accept-Encoding
x-powered-by: Zope (www.zope.org), Python (www.python.org)
x-request-id: ec4bd7ff-f333-4543-ba91-3b7b063fab0e
x-vcs-revision: 81acd06336f3c4be8f28a2213f7a64912593402d
---
Response body:
---
b"Object: ,
name: '$REPO'"
---
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 352, in main
self.prompt_user_shortcut(shortcut)
File "/usr/bin/apt-add-repository", line 140, in prompt_user_shortcut
if shortcut.description:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 117, in
description
return self.lpppa.description
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 109, in
lpppa
raise ShortcutException(msg)
softwareproperties.shortcuthandler.ShortcutException: ERROR: ppa
'$REPO/proposed' not found (use --login if private)
Impish similarly breaks. Digging through changelogs, I see various
entries in Impish forward, starting with version 0.99.0 where a refactor
was done.
using `--login` is not possible in an automated setup (such as a
builder) as it starts an OAuth dance, which requires human interaction.
this will break existing automation utilizing apt-add-repository for
users when migrating to Jammy
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1965180
Title:
apt-add-repository requires --login for private repos, breaking
automated workflows
Status in software-properties package in Ubuntu:
New
Bug description:
On Focal, in an automated environment (such as a launchpad builder), a
used can do the following workflow:
curl
"https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu focal main"
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64
Packages [3288 B]
Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main
Translation-en [1892 B]
However, on Jammy, I get the following:
curl "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
[Desktop-packages] [Bug 1965175] Re: gjs-console assert failure: free(): invalid pointer
*** This bug is a duplicate of bug 1946165 *** https://bugs.launchpad.net/bugs/1946165 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1946165, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1965175/+attachment/5569750/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1965175/+attachment/5569752/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1965175/+attachment/5569756/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1965175/+attachment/5569757/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1965175/+attachment/5569758/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1965175/+attachment/5569759/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1965175/+attachment/5569760/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1946165 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1965175 Title: gjs-console assert failure: free(): invalid pointer Status in gjs package in Ubuntu: New Bug description: dash to panel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gjs 1.71.90-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AssertionMessage: free(): invalid pointer CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 22:19:54 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2022-01-27 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220127) ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Extensions Signal: 6 SourcePackage: gjs StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ff1e5179b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7ff1e5177764 "free(): invalid pointer") at ./malloc/malloc.c:5664 _int_free (av=, p=, have_lock=0) at ./malloc/malloc.c:4439 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 Title: gjs-console assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1965175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965168] Re: jammy community competition wallpapers
** Changed in: ubuntu-wallpapers (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-wallpapers (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1965168 Title: jammy community competition wallpapers Status in ubuntu-wallpapers package in Ubuntu: Triaged Bug description: We have the winning images, in full size and both under CC by SA 4.0 The author of the first image is Elena Stravoravdi The author of the remaining images, both light and dark mode, is by hiking93 If it is possible, we would like to include both the light and dark mode of the jellyfish image. If there is not enough room, please only include the light jellyfish image. Let me know if there are any other concerns or questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965168] Re: jammy community competition wallpapers
After talking to Ken, we would like to propose one more to include in the ISO, space allowing. This is also by Elena Stravoravdi ** Attachment added: "Optical Fibers in Dark.jpg" https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+attachment/5569739/+files/Optical%20Fibers%20in%20Dark.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1965168 Title: jammy community competition wallpapers Status in ubuntu-wallpapers package in Ubuntu: Triaged Bug description: We have the winning images, in full size and both under CC by SA 4.0 The author of the first image is Elena Stravoravdi The author of the remaining images, both light and dark mode, is by hiking93 If it is possible, we would like to include both the light and dark mode of the jellyfish image. If there is not enough room, please only include the light jellyfish image. Let me know if there are any other concerns or questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965168] Re: jammy community competition wallpapers
** Summary changed: - community competition wallpapers + jammy community competition wallpapers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1965168 Title: jammy community competition wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: We have the winning images, in full size and both under CC by SA 4.0 The author of the first image is Elena Stravoravdi The author of the remaining images, both light and dark mode, is by hiking93 If it is possible, we would like to include both the light and dark mode of the jellyfish image. If there is not enough room, please only include the light jellyfish image. Let me know if there are any other concerns or questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965168] Re: community competition wallpapers
Image 2 - Light Abstract Jellyfish by Hiking93 ** Attachment added: "jj_light.jpg" https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+attachment/5569735/+files/jj_light.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1965168 Title: jammy community competition wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: We have the winning images, in full size and both under CC by SA 4.0 The author of the first image is Elena Stravoravdi The author of the remaining images, both light and dark mode, is by hiking93 If it is possible, we would like to include both the light and dark mode of the jellyfish image. If there is not enough room, please only include the light jellyfish image. Let me know if there are any other concerns or questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965168] Re: community competition wallpapers
Image 1 by Elena Stravoravdi ** Attachment added: "Blue flower!!!.jpg" https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+attachment/5569734/+files/Blue%20flower%21%21%21.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1965168 Title: jammy community competition wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: We have the winning images, in full size and both under CC by SA 4.0 The author of the first image is Elena Stravoravdi The author of the remaining images, both light and dark mode, is by hiking93 If it is possible, we would like to include both the light and dark mode of the jellyfish image. If there is not enough room, please only include the light jellyfish image. Let me know if there are any other concerns or questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965168] Re: community competition wallpapers
Optional Image 3 - Abstract Jellyfish Dark by hiking93 ** Attachment added: "jj_dark.jpg" https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+attachment/5569736/+files/jj_dark.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1965168 Title: jammy community competition wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: We have the winning images, in full size and both under CC by SA 4.0 The author of the first image is Elena Stravoravdi The author of the remaining images, both light and dark mode, is by hiking93 If it is possible, we would like to include both the light and dark mode of the jellyfish image. If there is not enough room, please only include the light jellyfish image. Let me know if there are any other concerns or questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965168] [NEW] jammy community competition wallpapers
Public bug reported: We have the winning images, in full size and both under CC by SA 4.0 The author of the first image is Elena Stravoravdi The author of the remaining images, both light and dark mode, is by hiking93 If it is possible, we would like to include both the light and dark mode of the jellyfish image. If there is not enough room, please only include the light jellyfish image. Let me know if there are any other concerns or questions. ** Affects: ubuntu-wallpapers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1965168 Title: jammy community competition wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: We have the winning images, in full size and both under CC by SA 4.0 The author of the first image is Elena Stravoravdi The author of the remaining images, both light and dark mode, is by hiking93 If it is possible, we would like to include both the light and dark mode of the jellyfish image. If there is not enough room, please only include the light jellyfish image. Let me know if there are any other concerns or questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965085] Re: Login screen sometimes unresponsive to mouse clicks (after waking from sleep)
I can confirm this as twice I've had difficulties logging in after waking from sleep and once after a 40 minute period of the screen being locked while I was away from the PC. This is using Wayland. I have a dual monitor set-up and see a mouse pointer on both screens. Each time I have had to switch to a vt, switch back to vt1 and then log- in. The effects of pressing tab or escape have been quite random. On one occasion I could see my desktop but could not actually use it and on another I could see Ubuntu Dock on top of the lock screen but could not log in. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965085 Title: Login screen sometimes unresponsive to mouse clicks (after waking from sleep) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: The login screen is sometimes unresponsive to mouse clicks (after waking from sleep). I can generally get it working again either by hitting Tab, or by switching VTs. Seems to happen with either Wayland or Xorg greeters. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 16 14:07:16 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-05 (130 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
I have uploaded cups 2.4.1op1-1ubuntu3 with the updated patch now, and
also updated the upstream pull request:
https://github.com/OpenPrinting/cups/pull/353
Please test as soon as the update arrives.
** Changed in: cups (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
Fix Committed
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 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.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Hi Daniel, I tried it on my DELL XPS 9510 which is I+N platform but I didn't meet this issue on Jammy daily build (with dist-upgrade). Did you change anything? e.g. upgrade gnome-shell or mutter to 42 beta? ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in OEM Priority Project: New Status in mutter package in Ubuntu: In Progress Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-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 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964732] Re: [FFe] Include Desktop Icons Appearance Settings
** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Triaged ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1964732 Title: [FFe] Include Desktop Icons Appearance Settings Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Bug description: In Jammy the default desktop extension is providing lots settings in a poorly integrated way, accessible from right-click: https://i.imgur.com/boMhCrH.png We got a community contribution (https://gitlab.gnome.org/Community/Ubuntu/gnome-conyol- center/-/merge_requests/9) to move the most relevant (for ubuntu) settings into the ubuntu "appearance" panel in gnome-control-center so that we can explicitly only support a restricted number of options that we care about, while all the rest can be tuned when using the ding options manually or tools such as d-conf editor. The appearance options will include these new widgets: https://i.imgur.com/Cup75om.png (wording to be improved before UIF) This is the code involved: - https://salsa.debian.org/gnome-team/gnome-control-center/-/commit/3f7c10501b1ac28311dd9edb64e64bfbbcd67204 Plus we need to change DING code to call `gnome-settings-daemon ubuntu` on desktop context menu. Not sure this is fully a FFe request, given that from the global desktop point of view we want actually support less features. --- It would be nice to be able to upload the update before UIF, so that we don't require further exception steps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
** Description changed: + [Impact] + + * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). + * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. + * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. + + [Test Plan] + + * ubuntu-drivers debug + ``` + ... + === matching driver packages === + nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] + ... + nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB + ... + ``` + * As you can see, "(auto-install)" is point to 470 because of it owns LTSB tag. + + [Fix] + * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. + + [Where problems could occur] + * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. + * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. + + --- + + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Impish: In Progress Bug description: [Impact] * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. [Test Plan] * ubuntu-drivers debug ``` ... === matching driver packages === nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] ... nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB ... ``` * As you can see, "(auto-install)" is point to 470 because of it owns LTSB tag. [Fix] * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. [Where problems could occur] * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. --- + nvidia-graphics-drivers-510
[Desktop-packages] [Bug 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
Thanks for all the info, it is as I expected, your cupsd.conf has
"Browsing No" because you do not use printer sharing. Then the DNS-SD
host name is not set in the daemon's internal variable DNSSDHostName and
this variable I compared with the host name of the URI of the potential
new queue to see whether I have to change it to "localhost" for the case
that the printer is a local service (IPP-over-USB, Printer Application,
...). This caused the crash. Now I have added a fallback to the internal
variable ServerName if DNSSDHostName is NULL.
I could reproduce the bug by doing the command
cupsctl --no-share-printers
(I had printer sharing on for my OpenPrinting work) and re-trying to
access an IPP printer through GTK's print dialog which caused the crash
then for me.
I have the fix now ready and with it the crash goes away.
I will update the Pull Request on CUPS upstream
(https://github.com/OpenPrinting/cups/pull/353) and also the patch on
the Ubuntu package.
Thanks for the bug report.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
In Progress
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 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.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964930] Re: Failed to start flatpak document portal service.
** Changed in: libxml2 Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1964930 Title: Failed to start flatpak document portal service. Status in libxml2: New Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: Bug desciption: when launching the Calendar app (flatpak version) my system freezes for 2/3 sec, then re-become responsive, then the calendar app launcher like 10 sec after. All my flatpak apps boot a lot slower than usual. This bug happened with the recent update to libxml2 (one or two days ago ?). This is not the first time it happened. See: https://github.com/flatpak/xdg-desktop-portal-gtk/issues/107#issuecomment-454653039 I don't know where to report this, if this is relates to ubuntu or to the flatpak project. Thanks for looking into this ! Description: Ubuntu 21.10 Release: 21.10 libxml2: Installed: 2.9.12+dfsg-4ubuntu0.1 Candidate: 2.9.12+dfsg-4ubuntu0.1 Version table: *** 2.9.12+dfsg-4ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 2.9.12+dfsg-4 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages flatpak: Installed: 1.10.2-3ubuntu0.1 Candidate: 1.10.2-3ubuntu0.1 Version table: *** 1.10.2-3ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/universe amd64 Packages 100 /var/lib/dpkg/status 1.10.2-3 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages systemd: Installed: 248.3-1ubuntu8.2 Candidate: 248.3-1ubuntu8.2 Version table: *** 248.3-1ubuntu8.2 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 248.3-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages journalctl -e: mars 15 11:25:09 mathieu-ThinkPad systemd[3226]: app-gnome-gufw-20889.scope: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad systemd[1]: systemd-timedated.service: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad dbus-daemon[6461]: [session uid=1000 pid=6461] Activating via systemd: service name='org.freedesktop.port> mars 15 11:25:13 mathieu-ThinkPad systemd[3226]: Starting flatpak document portal service... mars 15 11:25:14 mathieu-ThinkPad xdg-document-portal[21187]: error: Failed to load db from '/home/mathieu/.local/share/flatpak/db/document> mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Main process exited, code=exited, status=2/INVALIDARGUMENT mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Failed with result 'exit-code'. mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: Failed to start flatpak document portal service. sudo dmesg: [ 2380.432314] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.445853] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.449934] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2513.367108] gnome-calendar[9096]: segfault at 40016 ip 7f8e926037a0 sp 7ffe96506ca8 error 4 in libgobject-2.0.so.0.7000.4[7f8e925db000+31000] [ 2513.367127] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48 81 fe fc 03 00 00 76 28 48 83 e6 fc 31 c0 48 85 ff 74 33 47 16 04 74 05 48 85 f6 75 2d 31 c0 c3 66 90 48 83 e7 fc 48 81 [ 2739.248107] [UFW BLOCK] IN=wlp3s0 OUT= MAC=a8:6d:aa:ef:af:b5:be:0d:fd:89:d3:3b:08:00 SRC=142.250.200.129 DST=192.168.43.18 LEN=40 TOS=0x00 PREC=0x00 TTL=116 ID=0 DF PROTO=TCP SPT=443 DPT=56418 WINDOW=0 RES=0x00 RST URGP=0 [ 4484.828195] gnome-calendar[20663]: segfault at 40016 ip 7f4c418207a0 sp 7ffc815aff58 error 4 in libgobject-2.0.so.0.7000.4[7f4c417f8000+31000] [ 4484.828209] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48 81 fe fc 03 00 00 76 28 48 83 e6 fc 31 c0 48 85 ff 74 33 47 16 04 74 05 48 85 f6 75 2d 31 c0 c3 66 90 48 83 e7 fc 48 81 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8.2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 11:28:05 2022 MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine:
[Desktop-packages] [Bug 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
** Changed in: cups (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
In Progress
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 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.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Tested impish version
```
ubuntu-drivers-common:
Installed: 1:0.9.2.4~0.21.10.1
```
and the log shows
```
...
Takes 660ms to wait for nvidia udev rules completed.
```
thus, the result is PASS.
** Tags removed: verification-needed verification-needed-impish
** Tags added: verification-done verification-done-impish
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver probe
Status in OEM Priority Project:
Confirmed
Status in gdm3 package in Ubuntu:
Incomplete
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Incomplete
Status in ubuntu-drivers-common source package in Focal:
Fix Committed
Status in gdm3 source package in Impish:
Incomplete
Status in ubuntu-drivers-common source package in Impish:
Fix Committed
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Tested focal version
```
ubuntu-drivers-common:
Installed: 1:0.9.0~0.20.04.6
```
and the log shows
```
...
Takes 640ms to wait for nvidia udev rules completed.
```
thus, the result is PASS.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver probe
Status in OEM Priority Project:
Confirmed
Status in gdm3 package in Ubuntu:
Incomplete
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Incomplete
Status in ubuntu-drivers-common source package in Focal:
Fix Committed
Status in gdm3 source package in Impish:
Incomplete
Status in ubuntu-drivers-common source package in Impish:
Fix Committed
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
debian bug:
[Desktop-packages] [Bug 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
doko@xe1:~$ driverless
ipp://HP%20LaserJet%20500%20colorMFP%20M570dw%20(6C84AD)._ipp._tcp.local/
doko@xe1:~$ driverless --std-ipp-uris
ipp://NPI6C84AD.local:631/ipp/printer
doko@xe1:~$ lpstat -v
lpstat: No destinations added.
$ ps aux | grep cups-browsed
root 94786 0.0 0.0 172744 11908 ?Ssl 11:00 0:00
/usr/sbin/cups-browsed
doko 110175 0.0 0.0 9560 2428 pts/4S+ 17:21 0:00 grep
--color=auto cups-browsed
Trying to print a png image with eog
** Attachment added: "error_log"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+attachment/5569701/+files/error_log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
New
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 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.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
$ cupsctl
_debug_logging=1
_remote_admin=0
_remote_any=0
_share_printers=0
_user_cancel_any=0
BrowseLocalProtocols=dnssd
DefaultAuthType=Basic
ErrorPolicy=retry-job
IdleExitTimeout=60
JobPrivateAccess=default
JobPrivateValues=default
MaxLogSize=0
PageLogFormat=
SubscriptionPrivateAccess=default
SubscriptionPrivateValues=default
WebInterface=Yes
** Attachment added: "cupsd.conf"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+attachment/5569712/+files/cupsd.conf
** Changed in: cups (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
New
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 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.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed Status in OEM Priority Project: Fix Released Status in gdm3 package in Ubuntu: Fix Released Bug description: [Impact] * In Ubuntu 22.04, gdm should use Wayland by default even if proprietary nVidia driver is in use. * gdm upstream prefers Wayland if nvidia version newer than (or equal) to 510. It same as Ubuntu's strategy[1]. [Test Plan] Steps: 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Where problems could occur] * If nVidia GPU doesn't support Wayland then it will be a problem but it doesn't means this patch leads a regression, instead, the problem should always there as it is if the user switches to Wayland mode no matter default mode. * This ticket switches the default mode to Wayland. If there is a problem then user will encounter it after the installation which has bad experience. * However, it's not regression because Jammy is a new LTS version and we decide to switch to Wayland. If a problem occurs, then we fix it. --- [Steps to reproduce] 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Expect result] gdm using wayland (at least with nvidia-510) [Actual result] gdm using xorg 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy gdm3 gdm3: Installed: 41.3-1ubuntu2 Candidate: 41.3-1ubuntu2 Version table: *** 41.3-1ubuntu2 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Reference: [1] Ubuntu Jammy should use Wayland as default with nVidia https://docs.google.com/document/d/1wK4vGUXaDG2Nd7e3XGI9kDpNzReka_VOHO7sgRqce5s/edit?disco=VxVMzfA To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962214] Re: The documentation around NM's 10-globally-managed-devices.conf is inadequate
*** This bug is a duplicate of bug 1951653 *** https://bugs.launchpad.net/bugs/1951653 ** This bug has been marked a duplicate of bug 1951653 can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1962214 Title: The documentation around NM's 10-globally-managed-devices.conf is inadequate Status in netplan: New Status in network-manager package in Ubuntu: New Bug description: So, we're UBports, porting Ubuntu Touch stack to Ubuntu 20.04. While debugging why NM won't manage the phone's USB network interface, I stumbled upon /usr/lib/NetworkManager/conf.d/10-globally-managed- devices.conf. This file prevents NM from managing ethernet connection, which confuses me since this file also exists on my laptop, yet NM happily manages its ethernet port. This file exists at part of NetworkManager package in Ubuntu without any documentation. And the reason given in the commit that add it [1] does not mention any specific reason why it's added. Only when looking in the log on my laptop do I see that something places the file with the same name in /run/NetworkManager/conf.d/, and requires greping in /usr/lib to find out that the thing is Netplan's generator binary. Now, that file in /run is empty, which requires another round of searching to find out that Netplan places this file when it's configured to use NM as a renderer. With that in mind, I discovered that /etc/netplan/01-network-manager-all.yaml exists on my laptop but not the phone. Now, because 'dpkg -S' returns empty result, I need to search again what places this file, with no avail. Luckily, I happen to have a clone of livecd-rootfs on my laptop, which leads me to this commit [2] which finally reveals the reason why this is done: to prevent systems which installs NM after-the-fact to have NM conflicts with e.g. systemd-networkd. All of these knowledge should not require this much searching plus grepping through _binary_ file. If either my laptop was not running Ubuntu or I didn't have livecd-rootfs cloned, it would be much harder to figure this out. They should be more properly documented, probably both in the /usr/lib/ and /run/ files. Thus, this issue is filled against both Netplan and NetworkManager packages. [1] https://git.launchpad.net/network-manager/commit?id=1ab4db73c1f0db30f3af1845a9c41e3c3952dea1 [2] https://git.launchpad.net/livecd-rootfs/commit/?id=d9ce44d73a0a6d91156bb94e03063d541b0f7579 P.S. Arguably, this behavior might be even wrong. According to https://netplan.io: > Obviously, without configuration, netplan will not do anything. This is not really the expected "not do anything". IMO the NM's behavior should be left at the default, unless e.g. the networkd renderer is used, in which case Netplan will disable NetworkManager to not manage interfaces configured by Netplan. However the reason above of preventing conflict with networkd is a valid one, and my proposal doesn't help with that particular case. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1962214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965156] Re: light theme background color window
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1965156 Title: light theme background color window Status in gnome-control-center package in Ubuntu: New Bug description: Using settings->appearance there are two options: light theme and dark theme 1) release of Ubuntu: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2) The version of the package gnome-control-center: Installed: 1:41.4-1ubuntu3.1 Candidate: 1:41.4-1ubuntu3.1 Version table: *** 1:41.4-1ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen light theme has two windows: one light in front and one dark behind, having the same color as observed in dark theme 4) What happened instead the window in the background of the light theme should be dimmed slightly instead of being completely dark as found in the dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951653 Title: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged' Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Confirmed Bug description: I have tried to tell netplan to let my ethernet device be managed by NetworkManager, so that I can then configure a pppoe connection on top of this device. This fails with: # nmcli c up netplan-wan Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged). # I don't know why it mentions 'lo' in that message, but the wan interface is unmanaged (as are all devices on the system, but this one is supposed to be managed): # nmcli d status | grep wan wan ethernet unmanaged -- # After much searching, I've figured out that this comes from /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf: keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma Even though I've told netplan to use the NM renderer for this device, the configuration emitted by netplan is insufficient to override this. Using the workaround from https://askubuntu.com/questions/71159/network-manager-says-device-not- managed (sudo touch /etc/NetworkManager/conf.d/10-globally-managed- devices.conf) doesn't work, but if I set NetworkManager as the toplevel renderer in /etc/netplan, /run/NetworkManager/conf.d/10-globally-managed-devices.conf is emitted, which evidently DOES work. But I only have one device that I want rendered by NM, so I shouldn't have to declare NM at the top level of the yaml with a lot of duplication in order to get this result. I would argue that the 10-globally-managed-devices.conf should not be there at all. But if it is going to be, then netplan needs to consistently override it whenever there is any use of the NetworkManager backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1951653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964976] Re: gnome-remote-desktop is not listening on port 5900, no sign of why
We were also tracking this already in https://warthogs.atlassian.net/browse/DT-264 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1964976 Title: gnome-remote-desktop is not listening on port 5900, no sign of why Status in gnome-remote-desktop package in Ubuntu: New Bug description: With all current packages from jammy, gnome-remote-desktop is not listening on port 5900. Lsof doesn't show it listening on that port, attempting to connect to that port yields connection refused), with no indication of why. There are no errors matching the pattern "gnome- remote-desktop" in /var/log/syslog, "journalctl --user --unit gnome- remote-desktop" doesn't show any errors, "systemctl status --user gnome-remote-desktop" shows that it is running, my settings show that screen sharing is enabled, this used to work, and I haven't changed anything since it did. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-remote-desktop 42~rc-1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 10:49:08 2022 InstallationDate: Installed on 2019-01-02 (1167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-remote-desktop UpgradeStatus: Upgraded to jammy on 2022-02-20 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1964976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965003] Re: Orange running dots on launchers are out of centre on bottom dock
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Medium ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Tags added: fixed-upstream ** Changed in: yaru-theme (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965003 Title: Orange running dots on launchers are out of centre on bottom dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in yaru-theme package in Ubuntu: Fix Committed Bug description: Ubuntu 22.04 development branch @ 15/03/2022 After todays updates with gnome-shell 42 beta the dock at bottom has the orange 'running' dots out of centre to the left under the launchers dock placed left and right they seem centered correctly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 20:25:18 2022 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965156] Re: light theme background color window
We basically get that graphic from gnome-control-center 42. Please report this bug to GNOME and let us know the bug number. https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues ** Tags added: jammy upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1965156 Title: light theme background color window Status in gnome-control-center package in Ubuntu: New Bug description: Using settings->appearance there are two options: light theme and dark theme 1) release of Ubuntu: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2) The version of the package gnome-control-center: Installed: 1:41.4-1ubuntu3.1 Candidate: 1:41.4-1ubuntu3.1 Version table: *** 1:41.4-1ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen light theme has two windows: one light in front and one dark behind, having the same color as observed in dark theme 4) What happened instead the window in the background of the light theme should be dimmed slightly instead of being completely dark as found in the dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961854] Re: Thunderbid saves accepted calendar events in different identity
https://bugzilla.mozilla.org/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1961854 Title: Thunderbid saves accepted calendar events in different identity Status in thunderbird package in Ubuntu: New Bug description: When user have configured e.g: 1. One self hosted e-mail 2. One GMail account 3. One Microsoft Office360 account with calendar When he will accept calendar event in 1 or 2 and the only available calendar (from Thunderbird perspective) is 3, clicking the bluebar over e-mail to add calendar entry will save it in wrong identity(the 3). As identities are also boundaries for control -this should be considered privacy threat. E.g one can have private and business e-mail accounts in one Thunderbird where business ones could be inspected manually of automatically . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1961854/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell
** Changed in: gnome-shell (Ubuntu Jammy) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964545 Title: 42beta: moving mouse as screen is fading to screensaver prevents input to shell Status in gnome-shell package in Ubuntu: New Status in gnome-shell source package in Jammy: New Bug description: [Impact] If you move the mouse as the system fades into black for the screensaver, the screensaver will be prevented as normal, but the user will not be able to interact with the shell. Mouse clicks are ignored, and most key presses are ignored too. Workaround is to press super to enter shell overview, then super again to close, and mouse clicks will begin working again. gnome-shell 42~beta-1ubuntu2 from -proposed. [Testcase] 1) Leave your system idle, until the screen starts fading to black 2) As the screen is fading to black, move the mouse to prevent screensaver. 3) Attempt to click any window or type something To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965067] Re: [42beta] gnome-disks does not respect gtk theme
Also please tag bugs rls-jj-incoming instead of nominating them for the serie directly so they are reviewed by the team and can get properly assigned as part of the process -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1965067 Title: [42beta] gnome-disks does not respect gtk theme Status in gnome-disk-utility package in Ubuntu: Incomplete Status in gnome-disk-utility source package in Jammy: Incomplete Bug description: gnome-disks does not apply the Yaru theme, when all other GNOME applications respect the default theme. See attached screenshot. gnome-disks 42~rc-1ubuntu1 gnome-shell 42~beta-1ubuntu2 yaru-theme-gtk 22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1965067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965003] Re: Orange running dots on launchers are out of centre on bottom dock
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965003 Title: Orange running dots on launchers are out of centre on bottom dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in yaru-theme package in Ubuntu: Fix Committed Bug description: Ubuntu 22.04 development branch @ 15/03/2022 After todays updates with gnome-shell 42 beta the dock at bottom has the orange 'running' dots out of centre to the left under the launchers dock placed left and right they seem centered correctly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 20:25:18 2022 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965067] Re: [42beta] gnome-disks does not respect gtk theme
Thank you for the bug report. Is that specific to using the dark mode? Which version of libhandy-1 do you have installed? There are changes in https://launchpad.net/ubuntu/+source/libhandy-1/1.5.91-2 that could create issue, setting the theme to light and back to dark might help fixing the configuration if that's the issue ** Changed in: gnome-disk-utility (Ubuntu Jammy) Importance: Undecided => High ** Changed in: gnome-disk-utility (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1965067 Title: [42beta] gnome-disks does not respect gtk theme Status in gnome-disk-utility package in Ubuntu: Incomplete Status in gnome-disk-utility source package in Jammy: Incomplete Bug description: gnome-disks does not apply the Yaru theme, when all other GNOME applications respect the default theme. See attached screenshot. gnome-disks 42~rc-1ubuntu1 gnome-shell 42~beta-1ubuntu2 yaru-theme-gtk 22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1965067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964976] Re: gnome-remote-desktop is not listening on port 5900, no sign of why
** Changed in: gnome-remote-desktop (Ubuntu) Importance: Undecided => High ** Changed in: gnome-remote-desktop (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1964976 Title: gnome-remote-desktop is not listening on port 5900, no sign of why Status in gnome-remote-desktop package in Ubuntu: New Bug description: With all current packages from jammy, gnome-remote-desktop is not listening on port 5900. Lsof doesn't show it listening on that port, attempting to connect to that port yields connection refused), with no indication of why. There are no errors matching the pattern "gnome- remote-desktop" in /var/log/syslog, "journalctl --user --unit gnome- remote-desktop" doesn't show any errors, "systemctl status --user gnome-remote-desktop" shows that it is running, my settings show that screen sharing is enabled, this used to work, and I haven't changed anything since it did. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-remote-desktop 42~rc-1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 10:49:08 2022 InstallationDate: Installed on 2019-01-02 (1167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-remote-desktop UpgradeStatus: Upgraded to jammy on 2022-02-20 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1964976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965156] [NEW] light theme background color window
Public bug reported: Using settings->appearance there are two options: light theme and dark theme 1) release of Ubuntu: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) The version of the package gnome-control-center: Installed: 1:41.4-1ubuntu3.1 Candidate: 1:41.4-1ubuntu3.1 Version table: *** 1:41.4-1ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen light theme has two windows: one light in front and one dark behind, having the same color as observed in dark theme 4) What happened instead the window in the background of the light theme should be dimmed slightly instead of being completely dark as found in the dark theme ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1965156 Title: light theme background color window Status in gnome-control-center package in Ubuntu: New Bug description: Using settings->appearance there are two options: light theme and dark theme 1) release of Ubuntu: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2) The version of the package gnome-control-center: Installed: 1:41.4-1ubuntu3.1 Candidate: 1:41.4-1ubuntu3.1 Version table: *** 1:41.4-1ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen light theme has two windows: one light in front and one dark behind, having the same color as observed in dark theme 4) What happened instead the window in the background of the light theme should be dimmed slightly instead of being completely dark as found in the dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
thanks, the journal has some error, did you edit the .service to add the -d to the execstart as request? wpa doesn't seem to be in debug mode on that log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in network-manager package in Ubuntu: Incomplete Bug description: WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964930] Re: Failed to start flatpak document portal service.
Thanks for reporting it upstream! ** Package changed: libxml2 (Ubuntu) => xdg-desktop-portal (Ubuntu) ** Changed in: xdg-desktop-portal (Ubuntu) Importance: Undecided => High ** Changed in: xdg-desktop-portal (Ubuntu) Status: New => Triaged ** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #728 https://github.com/flatpak/xdg-desktop-portal/issues/728 ** Changed in: libxml2 Status: Fix Released => Unknown ** Changed in: libxml2 Remote watch: github.com/flatpak/xdg-desktop-portal-gtk/issues #107 => github.com/flatpak/xdg-desktop-portal/issues #728 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1964930 Title: Failed to start flatpak document portal service. Status in libxml2: Unknown Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: Bug desciption: when launching the Calendar app (flatpak version) my system freezes for 2/3 sec, then re-become responsive, then the calendar app launcher like 10 sec after. All my flatpak apps boot a lot slower than usual. This bug happened with the recent update to libxml2 (one or two days ago ?). This is not the first time it happened. See: https://github.com/flatpak/xdg-desktop-portal-gtk/issues/107#issuecomment-454653039 I don't know where to report this, if this is relates to ubuntu or to the flatpak project. Thanks for looking into this ! Description: Ubuntu 21.10 Release: 21.10 libxml2: Installed: 2.9.12+dfsg-4ubuntu0.1 Candidate: 2.9.12+dfsg-4ubuntu0.1 Version table: *** 2.9.12+dfsg-4ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 2.9.12+dfsg-4 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages flatpak: Installed: 1.10.2-3ubuntu0.1 Candidate: 1.10.2-3ubuntu0.1 Version table: *** 1.10.2-3ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/universe amd64 Packages 100 /var/lib/dpkg/status 1.10.2-3 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages systemd: Installed: 248.3-1ubuntu8.2 Candidate: 248.3-1ubuntu8.2 Version table: *** 248.3-1ubuntu8.2 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 248.3-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages journalctl -e: mars 15 11:25:09 mathieu-ThinkPad systemd[3226]: app-gnome-gufw-20889.scope: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad systemd[1]: systemd-timedated.service: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad dbus-daemon[6461]: [session uid=1000 pid=6461] Activating via systemd: service name='org.freedesktop.port> mars 15 11:25:13 mathieu-ThinkPad systemd[3226]: Starting flatpak document portal service... mars 15 11:25:14 mathieu-ThinkPad xdg-document-portal[21187]: error: Failed to load db from '/home/mathieu/.local/share/flatpak/db/document> mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Main process exited, code=exited, status=2/INVALIDARGUMENT mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Failed with result 'exit-code'. mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: Failed to start flatpak document portal service. sudo dmesg: [ 2380.432314] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.445853] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.449934] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2513.367108] gnome-calendar[9096]: segfault at 40016 ip 7f8e926037a0 sp 7ffe96506ca8 error 4 in libgobject-2.0.so.0.7000.4[7f8e925db000+31000] [ 2513.367127] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48 81 fe fc 03 00 00 76 28 48 83 e6 fc 31 c0 48 85 ff 74 33 47 16 04 74 05 48 85 f6 75 2d 31 c0 c3 66 90 48 83 e7 fc 48 81 [ 2739.248107] [UFW BLOCK] IN=wlp3s0 OUT= MAC=a8:6d:aa:ef:af:b5:be:0d:fd:89:d3:3b:08:00 SRC=142.250.200.129 DST=192.168.43.18 LEN=40 TOS=0x00 PREC=0x00 TTL=116 ID=0 DF PROTO=TCP SPT=443 DPT=56418 WINDOW=0 RES=0x00 RST URGP=0 [ 4484.828195] gnome-calendar[20663]: segfault at 40016 ip 7f4c418207a0 sp 7ffc815aff58 error 4 in libgobject-2.0.so.0.7000.4[7f4c417f8000+31000] [ 4484.828209] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48
[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
** Also affects: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Importance: Undecided => Critical ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Impish: In Progress Bug description: + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965113] Re: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions
Could you share the output of $ snap connections firefox it's working fine here but could it be that somehow the x11 interface isn't connected for you? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1965113 Title: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions Status in firefox package in Ubuntu: New Bug description: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions. $ /snap/bin/firefox Error: cannot open display: :0 $ echo $DISPLAY :0 And other X11 apps still work just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1965113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965123] Re: Active launchers area pixels missing
this was happening on yaru dark, switched to yaru as a test now it does not happen anymore on neither -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965123 Title: Active launchers area pixels missing Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 22.04 development branch @ 16/03/2022 after yesterdays updates to gnome 42 beta the docks area around the active launcher is missing 4 pixels in the corners when hovering mouse over them switching to another active launchers can be reproduced non-active area around launchers does not suffer this bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 12:55:20 2022 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963241] Re: [FFe] evince 42
This bug was fixed in the package evince - 42~rc-1 --- evince (42~rc-1) experimental; urgency=medium * New upstream release (LP: #1963241) -- Jeremy Bicha Tue, 08 Mar 2022 08:08:25 -0500 ** Changed in: evince (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1963241 Title: [FFe] evince 42 Status in evince package in Ubuntu: Fix Released Bug description: Why Needed -- The Ubuntu Desktop had a goal of including as much of GNOME 42 as possible in Ubuntu 22.04 LTS. (One major exception was where apps had switched to GTK4). The evince document viewer (PDFs and more) did not have earlier releases in the 42 cycle and its Beta wasn't released until March 3, a week after Feature Freeze. The Ubuntu Desktop Team commits to packaging the final evince 42 stable release and working to fix any regressions introduced in the update. We do have the ability to use a "really" version number in case we decide we need to go back to the 41 version. What Changed https://gitlab.gnome.org/GNOME/evince/-/blob/42.beta/NEWS https://gitlab.gnome.org/GNOME/evince/-/compare/41.3...42.beta For this release I have reverted 2 commits that required a new version of libarchive since that wasn't included in 22.04 LTS yet. Build Test -- Builds successfully Install Test $ sudo apt install ./../build-area/*ev*.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'evince' instead of './../build-area/evince_42~beta-1_amd64.deb' Note, selecting 'evince-common' instead of './../build-area/evince-common_42~beta-1_all.deb' Note, selecting 'gir1.2-evince-3.0' instead of './../build-area/gir1.2-evince-3.0_42~beta-1_amd64.deb' Note, selecting 'libevdocument3-4' instead of './../build-area/libevdocument3-4_42~beta-1_amd64.deb' Note, selecting 'libevview3-3' instead of './../build-area/libevview3-3_42~beta-1_amd64.deb' The following packages were automatically installed and are no longer required: libabsl20200923 libicu67 libpoppler115 Use 'sudo apt autoremove' to remove them. Suggested packages: unrar The following packages will be upgraded: evince evince-common gir1.2-evince-3.0 libevdocument3-4 libevview3-3 5 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Need to get 0 B/821 kB of archives. After this operation, 803 kB disk space will be freed. Get:1 /home/jeremy/devel/pkg-gnome/build-area/evince-common_42~beta-1_all.deb evince-common all 42~beta-1 [132 kB] Get:2 /home/jeremy/devel/pkg-gnome/build-area/evince_42~beta-1_amd64.deb evince amd64 42~beta-1 [306 kB] Get:3 /home/jeremy/devel/pkg-gnome/build-area/libevdocument3-4_42~beta-1_amd64.deb libevdocument3-4 amd64 42~beta-1 [204 kB] Get:4 /home/jeremy/devel/pkg-gnome/build-area/libevview3-3_42~beta-1_amd64.deb libevview3-3 amd64 42~beta-1 [148 kB] Get:5 /home/jeremy/devel/pkg-gnome/build-area/gir1.2-evince-3.0_42~beta-1_amd64.deb gir1.2-evince-3.0 amd64 42~beta-1 [31.1 kB] (Reading database ... 207369 files and directories currently installed.) Preparing to unpack .../evince-common_42~beta-1_all.deb ... Unpacking evince-common (42~beta-1) over (41.3-3) ... Preparing to unpack .../evince_42~beta-1_amd64.deb ... Unpacking evince (42~beta-1) over (41.3-3) ... Preparing to unpack .../libevdocument3-4_42~beta-1_amd64.deb ... Unpacking libevdocument3-4:amd64 (42~beta-1) over (41.3-3) ... Preparing to unpack .../libevview3-3_42~beta-1_amd64.deb ... Unpacking libevview3-3:amd64 (42~beta-1) over (41.3-3) ... Preparing to unpack .../gir1.2-evince-3.0_42~beta-1_amd64.deb ... Unpacking gir1.2-evince-3.0:amd64 (42~beta-1) over (41.3-3) ... Setting up evince-common (42~beta-1) ... Setting up libevdocument3-4:amd64 (42~beta-1) ... Setting up libevview3-3:amd64 (42~beta-1) ... Setting up evince (42~beta-1) ... Setting up gir1.2-evince-3.0:amd64 (42~beta-1) ... Processing triggers for desktop-file-utils (0.26-1ubuntu2) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for gnome-menus (3.36.0-1ubuntu2) ... Processing triggers for libglib2.0-0:amd64 (2.71.2-1) ... Processing triggers for libc-bin (2.35-0ubuntu1) ... Processing triggers for man-db (2.10.1-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... N: Download is performed unsandboxed as root as file '/home/jeremy/devel/pkg-gnome/build-area/evince-common_42~beta-1_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) $ evince (runs ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1963241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1963241] Re: [FFe] evince 42
The new libarchive should increase increase the compatibility with zip and RAR files. Certainly not an essential boost in functionality but on the other hand certainly welcome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1963241 Title: [FFe] evince 42 Status in evince package in Ubuntu: Fix Released Bug description: Why Needed -- The Ubuntu Desktop had a goal of including as much of GNOME 42 as possible in Ubuntu 22.04 LTS. (One major exception was where apps had switched to GTK4). The evince document viewer (PDFs and more) did not have earlier releases in the 42 cycle and its Beta wasn't released until March 3, a week after Feature Freeze. The Ubuntu Desktop Team commits to packaging the final evince 42 stable release and working to fix any regressions introduced in the update. We do have the ability to use a "really" version number in case we decide we need to go back to the 41 version. What Changed https://gitlab.gnome.org/GNOME/evince/-/blob/42.beta/NEWS https://gitlab.gnome.org/GNOME/evince/-/compare/41.3...42.beta For this release I have reverted 2 commits that required a new version of libarchive since that wasn't included in 22.04 LTS yet. Build Test -- Builds successfully Install Test $ sudo apt install ./../build-area/*ev*.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'evince' instead of './../build-area/evince_42~beta-1_amd64.deb' Note, selecting 'evince-common' instead of './../build-area/evince-common_42~beta-1_all.deb' Note, selecting 'gir1.2-evince-3.0' instead of './../build-area/gir1.2-evince-3.0_42~beta-1_amd64.deb' Note, selecting 'libevdocument3-4' instead of './../build-area/libevdocument3-4_42~beta-1_amd64.deb' Note, selecting 'libevview3-3' instead of './../build-area/libevview3-3_42~beta-1_amd64.deb' The following packages were automatically installed and are no longer required: libabsl20200923 libicu67 libpoppler115 Use 'sudo apt autoremove' to remove them. Suggested packages: unrar The following packages will be upgraded: evince evince-common gir1.2-evince-3.0 libevdocument3-4 libevview3-3 5 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Need to get 0 B/821 kB of archives. After this operation, 803 kB disk space will be freed. Get:1 /home/jeremy/devel/pkg-gnome/build-area/evince-common_42~beta-1_all.deb evince-common all 42~beta-1 [132 kB] Get:2 /home/jeremy/devel/pkg-gnome/build-area/evince_42~beta-1_amd64.deb evince amd64 42~beta-1 [306 kB] Get:3 /home/jeremy/devel/pkg-gnome/build-area/libevdocument3-4_42~beta-1_amd64.deb libevdocument3-4 amd64 42~beta-1 [204 kB] Get:4 /home/jeremy/devel/pkg-gnome/build-area/libevview3-3_42~beta-1_amd64.deb libevview3-3 amd64 42~beta-1 [148 kB] Get:5 /home/jeremy/devel/pkg-gnome/build-area/gir1.2-evince-3.0_42~beta-1_amd64.deb gir1.2-evince-3.0 amd64 42~beta-1 [31.1 kB] (Reading database ... 207369 files and directories currently installed.) Preparing to unpack .../evince-common_42~beta-1_all.deb ... Unpacking evince-common (42~beta-1) over (41.3-3) ... Preparing to unpack .../evince_42~beta-1_amd64.deb ... Unpacking evince (42~beta-1) over (41.3-3) ... Preparing to unpack .../libevdocument3-4_42~beta-1_amd64.deb ... Unpacking libevdocument3-4:amd64 (42~beta-1) over (41.3-3) ... Preparing to unpack .../libevview3-3_42~beta-1_amd64.deb ... Unpacking libevview3-3:amd64 (42~beta-1) over (41.3-3) ... Preparing to unpack .../gir1.2-evince-3.0_42~beta-1_amd64.deb ... Unpacking gir1.2-evince-3.0:amd64 (42~beta-1) over (41.3-3) ... Setting up evince-common (42~beta-1) ... Setting up libevdocument3-4:amd64 (42~beta-1) ... Setting up libevview3-3:amd64 (42~beta-1) ... Setting up evince (42~beta-1) ... Setting up gir1.2-evince-3.0:amd64 (42~beta-1) ... Processing triggers for desktop-file-utils (0.26-1ubuntu2) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for gnome-menus (3.36.0-1ubuntu2) ... Processing triggers for libglib2.0-0:amd64 (2.71.2-1) ... Processing triggers for libc-bin (2.35-0ubuntu1) ... Processing triggers for man-db (2.10.1-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... N: Download is performed unsandboxed as root as file '/home/jeremy/devel/pkg-gnome/build-area/evince-common_42~beta-1_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) $ evince (runs ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1963241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** No longer affects: nvidia-graphics-drivers-510 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
This bug was fixed in the package gdm3 - 41.3-1ubuntu3 --- gdm3 (41.3-1ubuntu3) jammy; urgency=medium [ Jeremy Szu ] * d/p/ubuntu/gdm.rules-Prefer-Wayland-with-NVIDIA-510.patch - default to Wayland for nvidia 510 drivers (LP: #1962523) -- Sebastien Bacher Tue, 15 Mar 2022 13:20:58 +0100 ** Changed in: gdm3 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: Fix Released Bug description: [Impact] * In Ubuntu 22.04, gdm should use Wayland by default even if proprietary nVidia driver is in use. * gdm upstream prefers Wayland if nvidia version newer than (or equal) to 510. It same as Ubuntu's strategy[1]. [Test Plan] Steps: 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Where problems could occur] * If nVidia GPU doesn't support Wayland then it will be a problem but it doesn't means this patch leads a regression, instead, the problem should always there as it is if the user switches to Wayland mode no matter default mode. * This ticket switches the default mode to Wayland. If there is a problem then user will encounter it after the installation which has bad experience. * However, it's not regression because Jammy is a new LTS version and we decide to switch to Wayland. If a problem occurs, then we fix it. --- [Steps to reproduce] 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Expect result] gdm using wayland (at least with nvidia-510) [Actual result] gdm using xorg 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy gdm3 gdm3: Installed: 41.3-1ubuntu2 Candidate: 41.3-1ubuntu2 Version table: *** 41.3-1ubuntu2 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Reference: [1] Ubuntu Jammy should use Wayland as default with nVidia https://docs.google.com/document/d/1wK4vGUXaDG2Nd7e3XGI9kDpNzReka_VOHO7sgRqce5s/edit?disco=VxVMzfA To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965138] [NEW] Desktop application should check for service available information before listing it
Public bug reported: Currently, it seems that software-properties is incorrectly assuming that both ESM and Livepatch services can be enabled in a Jammy machine. Those services are not yet available in Jammy and we are attaching an image showing that the Desktop message is that we had an error enabling then and that the user should try again. It seems that software-proporties source `/var/lib/ubuntu- advantage/status.json` and assumes the services is available if it appears on the services list and the `entitled` field has the `yes` value. However, it is perfectly possible for a service to be entitled to an user, but not available in the user's machine. We are now suggesting that software-properties also looks at the `available` field in the services json output to make that assumption, this will probably solve the issue we are seeing on Jammy. Another approach would be using the output of `ua status --format json` directly. However, this command will make a request to the contract's server if the user is unattached and maybe it is not wise to use it in that context. However, the output of that command only show services that are available, so we would not need to apply that extra available filter to it. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "jammy-desktop-error.png" https://bugs.launchpad.net/bugs/1965138/+attachment/5569662/+files/jammy-desktop-error.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965138 Title: Desktop application should check for service available information before listing it Status in software-properties package in Ubuntu: New Bug description: Currently, it seems that software-properties is incorrectly assuming that both ESM and Livepatch services can be enabled in a Jammy machine. Those services are not yet available in Jammy and we are attaching an image showing that the Desktop message is that we had an error enabling then and that the user should try again. It seems that software-proporties source `/var/lib/ubuntu- advantage/status.json` and assumes the services is available if it appears on the services list and the `entitled` field has the `yes` value. However, it is perfectly possible for a service to be entitled to an user, but not available in the user's machine. We are now suggesting that software-properties also looks at the `available` field in the services json output to make that assumption, this will probably solve the issue we are seeing on Jammy. Another approach would be using the output of `ua status --format json` directly. However, this command will make a request to the contract's server if the user is unattached and maybe it is not wise to use it in that context. However, the output of that command only show services that are available, so we would not need to apply that extra available filter to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965136] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate()
*** This bug is a duplicate of bug 1959937 *** https://bugs.launchpad.net/bugs/1959937 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1959937, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1965136/+attachment/5569639/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1965136/+attachment/5569641/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1965136/+attachment/5569645/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1965136/+attachment/5569646/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1965136/+attachment/5569647/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1965136/+attachment/5569649/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1965136/+attachment/5569650/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1959937 gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965136 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() Status in gnome-shell package in Ubuntu: New Bug description: gnome crashes on logon ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Mar 16 14:41:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2022-03-15 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SegvAnalysis: Segfault happened at: 0x7ff628286470 :cmpl $0x4,0x24(%rbx) PC (0x7ff628286470) ok source "$0x4" ok destination "0x24(%rbx)" (0xffb4) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_context_terminate () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965137] [NEW] package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit statu
Public bug reported: ideas of askubuntu.com/questions/1365631/nvidia-340-driver-on- ubuntu-20-04 helped to solve the issue ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166 Uname: Linux 5.4.0-104-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 16 03:49:14 2022 ErrorMessage: installed nvidia-340 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2016-03-16 (2190 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1965137 Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: ideas of askubuntu.com/questions/1365631/nvidia-340-driver-on- ubuntu-20-04 helped to solve the issue ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166 Uname: Linux 5.4.0-104-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 16 03:49:14 2022 ErrorMessage: installed nvidia-340 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2016-03-16 (2190 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1965137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965123] Re: Active launchers area pixels missing
when placing the dock left and right of the screen the active area is not disformed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965123 Title: Active launchers area pixels missing Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 22.04 development branch @ 16/03/2022 after yesterdays updates to gnome 42 beta the docks area around the active launcher is missing 4 pixels in the corners when hovering mouse over them switching to another active launchers can be reproduced non-active area around launchers does not suffer this bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 12:55:20 2022 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
Can you also attach your /etc/cups/cupsd.conf file?
And please also post the output of the command
cupsctl
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
Incomplete
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 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.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965123] [NEW] Active launchers area pixels missing
Public bug reported: Ubuntu 22.04 development branch @ 16/03/2022 after yesterdays updates to gnome 42 beta the docks area around the active launcher is missing 4 pixels in the corners when hovering mouse over them switching to another active launchers can be reproduced non-active area around launchers does not suffer this bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 12:55:20 2022 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "missing pixels" https://bugs.launchpad.net/bugs/1965123/+attachment/5569615/+files/Screenshot%20from%202022-03-16%2012-54-45.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965123 Title: Active launchers area pixels missing Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 22.04 development branch @ 16/03/2022 after yesterdays updates to gnome 42 beta the docks area around the active launcher is missing 4 pixels in the corners when hovering mouse over them switching to another active launchers can be reproduced non-active area around launchers does not suffer this bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 12:55:20 2022 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958019]
(In reply to Darin Miller from comment #563) > *Ubuntu version: > > 1) install kernel build tools: > (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): > > * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev dkms > libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git > > 2) clone the kernel from github and checkout to v5.17 branch (Rather large, > multiple GB's): > > * git clone https://github.com/torvalds/linux.git > * cd linux > * git checkout v5.17-rc4 > > 3) get the patch and install it: > > get the patch form this site and save to "linux" directory: (top right > corner "series" button) and use the following "git am ..." line to apply the > patch: > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > sbind...@opensource.cirrus.com/ > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > 4) load current kernel config and change configuration then run the > following scripts/config commands: > > * make olddefconfig > * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI > * ./scripts/config --disable CONFIG_DEBUG_INFO > * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" > * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" > > 6) build the kernel > > * make -j 16 > > 7) install the kernel > > * sudo make module_install > * sudo make install Hi guys, This is my first time compiling a kernel (Legion 7 16ACHg6/Ubuntu 20.04). I followed these steps (checked out the v5.17-rc8 branch on git) but at the end I am getting this error at the last step, just before running sudo make install: arch/x86/Makefile:154: CONFIG_X86_X32 enabled but no binutils support sh ./arch/x86/boot/install.sh 5.17.0-rc8+ \ arch/x86/boot/bzImage System.map "/boot" *** Missing file: arch/x86/boot/bzImage *** You need to run "make" before "make install". make: *** [arch/x86/Makefile:278: install] Error 1 Any help would be appreciated -- You received this bug notification because you are a member of Desktop 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
[Desktop-packages] [Bug 1964880] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
I have created a merge proposal for this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964880 Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: Opened up "Software & Updates" and clicked the "Additional Drivers Tab", for the tab to crash. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 19:02:39 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-01-02 (72 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1964880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964880] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
** Merge proposal linked: https://code.launchpad.net/~albertomilone/ubuntu/+source/software-properties/+git/software-properties/+merge/416950 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964880 Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: Opened up "Software & Updates" and clicked the "Additional Drivers Tab", for the tab to crash. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 19:02:39 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-01-02 (72 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1964880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962093] Re: network-manager can't connect to pppoe since version 1.35.90
No,I can't. I has no account on the gitlab. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: New Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8774] device (enp4s1): state change: config -> failed
[Desktop-packages] [Bug 1964132] Re: [FFe] webkit2gtk additionally built with libsoup3 support
Yes, I have tested that I can install the 4.1 packages along with the 4.0 packages. The webkit2gtk version numbers follow the older GNOME style. Odd numbers like 2.35 are unstable releases. Even numbers are stable releases. And the release cycle approximately follows GNOME too. 2.36.0 will be released in a few days. (2.35.3 is a Beta; 2.35.90 is more or less a Release Candidate.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1964132 Title: [FFe] webkit2gtk additionally built with libsoup3 support Status in webkit2gtk package in Ubuntu: Triaged Bug description: Request --- 1. Add the new libsoup3-using packages in webkit2gtk 2. Build Epiphany with the new webkit2gtk 4.1 API built with libsoup3 Why Needed -- Our webkit2gtk packaging is built with libsoup2 (webkitgtk's 4.0 API). Debian's packaging recently added additional packages built with libsoup3 (webkitgtk's 4.1 API); these should not affect the existing libsoup2 packages. The libsoup2 > libsoup3 transition is a big one and will not happen for 22.04 LTS; I am hoping we can finish it for main by 23.04 but I haven't looked into it yet. It's expected that GNOME 43 will try to switch to libsoup3. Having webkit2gtk with libsoup3 support in 22.04 LTS will make it easier for newer versions of the GNOME Web Browser (epiphany) to run on this release. It also will make it easier to create snaps of GNOME 43 apps using a core22 base. My instinct is that we want libsoup3 and the new webkit+libsoup3 packages to stay in universe for 22.04 LTS and then Main Inclusion can be recommended for 22.10. It is not intended for any traditional (.deb) packages in 22.04 LTS itself to use these new packages except epiphany. I already uploaded the webkit2gtk merge/sync with this change. If this FFe is rejected, I can undo the addition. What Changed See above Build Test -- https://launchpad.net/ubuntu/+source/webkit2gtk/2.35.90-1ubuntu1 Install Test Not done yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1964132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965116] [NEW] Desktop lockup with because Wayland compositor not fast enough
Public bug reported: I use Ubuntu 21.10 with Wayland and nvidia drivers. Sometimes, when working, the desktop freezes. Over ssh, I can see in the system logs many of those messages: > gnome-shell[5615]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! dmesg doesn't show any problems. Xwayland has a very high CPU usage. Killing Xwayland didn't help. When I then restart gdm, logging in either works again, or at least gdm allows a graceful reboot. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1965116 Title: Desktop lockup with because Wayland compositor not fast enough Status in wayland package in Ubuntu: New Bug description: I use Ubuntu 21.10 with Wayland and nvidia drivers. Sometimes, when working, the desktop freezes. Over ssh, I can see in the system logs many of those messages: > gnome-shell[5615]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! dmesg doesn't show any problems. Xwayland has a very high CPU usage. Killing Xwayland didn't help. When I then restart gdm, logging in either works again, or at least gdm allows a graceful reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1965116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
Could you run the following commands:
driverless
driverless --std-ipp-uris
lpstat -v
and post the output here.
On which print queue are you printing?
Are you running cups-browsed?
Then switch CUPS into debug mode:
cupsctl --debug-logging
Print a job as you did when the crash happened. When it fails again,
take the /var/log/cups/error_log file and attach it to this bug report.
DO NOT compress or package it.
Could you also tell me how you printed the job? Which application? GTK
print dialog? Any other print dialog?
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
Incomplete
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 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.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
New
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 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.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956537] Re: Firefox 95.0.2 64-bit Ubuntu gets error from command line launch
** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956537 Title: Firefox 95.0.2 64-bit Ubuntu gets error from command line launch Status in firefox package in Ubuntu: Incomplete Bug description: Steps to reproduce: firefox --private-window https://www.google.com Firefox 95.0.2 64-bit Ubuntu 21.10 using Unity 7.5 Actual results: ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored. Gtk-Message: 10:06:43.897: Failed to load module "xapp-gtk3-module" Gtk-Message: 10:06:44.073: Failed to load module "canberra-gtk-module" Gtk-Message: 10:06:44.579: Failed to load module "canberra-gtk-module" Expected results: These errors shouldn't be generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
** Attachment added: "syslog(success)" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+attachment/5569560/+files/syslog.7z -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions
The same Firefox snap doesn't start at all in Xorg sessions. Seems Firefox lost the ability to connect to X11 display :0 when all other X11 apps still can. --> bug 1965113 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions Status in firefox package in Ubuntu: Confirmed Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965113] Re: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions
The tarball of the same release works just fine: https://download- installer.cdn.mozilla.net/pub/firefox/releases/98.0.1/linux-x86_64/en- US/firefox-98.0.1.tar.bz2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1965113 Title: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions Status in firefox package in Ubuntu: New Bug description: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions. $ /snap/bin/firefox Error: cannot open display: :0 $ echo $DISPLAY :0 And other X11 apps still work just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1965113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965113] [NEW] Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions
Public bug reported: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions. $ /snap/bin/firefox Error: cannot open display: :0 $ echo $DISPLAY :0 And other X11 apps still work just fine. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: jammy snap x11 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1965113 Title: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions Status in firefox package in Ubuntu: New Bug description: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions. $ /snap/bin/firefox Error: cannot open display: :0 $ echo $DISPLAY :0 And other X11 apps still work just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1965113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
** Attachment added: "syslog(Failed)" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+attachment/5569534/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964930] Re: Failed to start flatpak document portal service.
I found the culprit, being a 0 byte "documents" file in the flatpak database. I filed an issue in the flatpak github. https://github.com/flatpak/xdg-desktop- portal/issues/369#issuecomment-1068915444 I still don't know if this relates to libxml2, and if it is worth being investigated how that 0 byte file was created. Thanks for reading. ** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #369 https://github.com/flatpak/xdg-desktop-portal/issues/369 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1964930 Title: Failed to start flatpak document portal service. Status in libxml2: Fix Released Status in libxml2 package in Ubuntu: New Bug description: Bug desciption: when launching the Calendar app (flatpak version) my system freezes for 2/3 sec, then re-become responsive, then the calendar app launcher like 10 sec after. All my flatpak apps boot a lot slower than usual. This bug happened with the recent update to libxml2 (one or two days ago ?). This is not the first time it happened. See: https://github.com/flatpak/xdg-desktop-portal-gtk/issues/107#issuecomment-454653039 I don't know where to report this, if this is relates to ubuntu or to the flatpak project. Thanks for looking into this ! Description: Ubuntu 21.10 Release: 21.10 libxml2: Installed: 2.9.12+dfsg-4ubuntu0.1 Candidate: 2.9.12+dfsg-4ubuntu0.1 Version table: *** 2.9.12+dfsg-4ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 2.9.12+dfsg-4 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages flatpak: Installed: 1.10.2-3ubuntu0.1 Candidate: 1.10.2-3ubuntu0.1 Version table: *** 1.10.2-3ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/universe amd64 Packages 100 /var/lib/dpkg/status 1.10.2-3 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages systemd: Installed: 248.3-1ubuntu8.2 Candidate: 248.3-1ubuntu8.2 Version table: *** 248.3-1ubuntu8.2 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 248.3-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages journalctl -e: mars 15 11:25:09 mathieu-ThinkPad systemd[3226]: app-gnome-gufw-20889.scope: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad systemd[1]: systemd-timedated.service: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad dbus-daemon[6461]: [session uid=1000 pid=6461] Activating via systemd: service name='org.freedesktop.port> mars 15 11:25:13 mathieu-ThinkPad systemd[3226]: Starting flatpak document portal service... mars 15 11:25:14 mathieu-ThinkPad xdg-document-portal[21187]: error: Failed to load db from '/home/mathieu/.local/share/flatpak/db/document> mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Main process exited, code=exited, status=2/INVALIDARGUMENT mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Failed with result 'exit-code'. mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: Failed to start flatpak document portal service. sudo dmesg: [ 2380.432314] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.445853] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.449934] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2513.367108] gnome-calendar[9096]: segfault at 40016 ip 7f8e926037a0 sp 7ffe96506ca8 error 4 in libgobject-2.0.so.0.7000.4[7f8e925db000+31000] [ 2513.367127] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48 81 fe fc 03 00 00 76 28 48 83 e6 fc 31 c0 48 85 ff 74 33 47 16 04 74 05 48 85 f6 75 2d 31 c0 c3 66 90 48 83 e7 fc 48 81 [ 2739.248107] [UFW BLOCK] IN=wlp3s0 OUT= MAC=a8:6d:aa:ef:af:b5:be:0d:fd:89:d3:3b:08:00 SRC=142.250.200.129 DST=192.168.43.18 LEN=40 TOS=0x00 PREC=0x00 TTL=116 ID=0 DF PROTO=TCP SPT=443 DPT=56418 WINDOW=0 RES=0x00 RST URGP=0 [ 4484.828195] gnome-calendar[20663]: segfault at 40016 ip 7f4c418207a0 sp 7ffc815aff58 error 4 in libgobject-2.0.so.0.7000.4[7f4c417f8000+31000] [ 4484.828209] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48 81 fe fc 03 00 00 76 28 48 83 e6 fc 31 c0 48 85 ff 74 33 47 16 04 74 05 48 85 f6 75 2d 31 c0 c3 66 90 48 83 e7 fc 48 81 ProblemType:
[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions
Is it perhaps related to the fix for bug 1959596? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions Status in firefox package in Ubuntu: Confirmed Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965105] [NEW] application crashes since update
Public bug reported: Since a few days ago the program LibreOffice Writer is broken. 1) Does not launch, or launches after several clicks a long (> 2 min) dely. 2) When open, the program often freezes and needs to be killed. My system: Operating System: Kubuntu 21.10 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-35-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Using Hebrew. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice-writer 1:7.2.5-0ubuntu0.21.10.3 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 16 11:19:12 2022 InstallationDate: Installed on 2021-06-15 (273 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: libreoffice UpgradeStatus: Upgraded to impish on 2022-01-12 (62 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1965105 Title: application crashes since update Status in libreoffice package in Ubuntu: New Bug description: Since a few days ago the program LibreOffice Writer is broken. 1) Does not launch, or launches after several clicks a long (> 2 min) dely. 2) When open, the program often freezes and needs to be killed. My system: Operating System: Kubuntu 21.10 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-35-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Using Hebrew. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice-writer 1:7.2.5-0ubuntu0.21.10.3 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 16 11:19:12 2022 InstallationDate: Installed on 2021-06-15 (273 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: libreoffice UpgradeStatus: Upgraded to impish on 2022-01-12 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1965105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964132] Re: [FFe] webkit2gtk additionally built with libsoup3 support
Oh, one thing before moving this to release: did you check that the new packages install correctly (and co-install with 4.0 API ones)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1964132 Title: [FFe] webkit2gtk additionally built with libsoup3 support Status in webkit2gtk package in Ubuntu: Triaged Bug description: Request --- 1. Add the new libsoup3-using packages in webkit2gtk 2. Build Epiphany with the new webkit2gtk 4.1 API built with libsoup3 Why Needed -- Our webkit2gtk packaging is built with libsoup2 (webkitgtk's 4.0 API). Debian's packaging recently added additional packages built with libsoup3 (webkitgtk's 4.1 API); these should not affect the existing libsoup2 packages. The libsoup2 > libsoup3 transition is a big one and will not happen for 22.04 LTS; I am hoping we can finish it for main by 23.04 but I haven't looked into it yet. It's expected that GNOME 43 will try to switch to libsoup3. Having webkit2gtk with libsoup3 support in 22.04 LTS will make it easier for newer versions of the GNOME Web Browser (epiphany) to run on this release. It also will make it easier to create snaps of GNOME 43 apps using a core22 base. My instinct is that we want libsoup3 and the new webkit+libsoup3 packages to stay in universe for 22.04 LTS and then Main Inclusion can be recommended for 22.10. It is not intended for any traditional (.deb) packages in 22.04 LTS itself to use these new packages except epiphany. I already uploaded the webkit2gtk merge/sync with this change. If this FFe is rejected, I can undo the addition. What Changed See above Build Test -- https://launchpad.net/ubuntu/+source/webkit2gtk/2.35.90-1ubuntu1 Install Test Not done yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1964132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions
Weird. No bug in Weston with the same firefox 98.0.1-2 snap that fails in GNOME. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions Status in firefox package in Ubuntu: Confirmed Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964132] Re: [FFe] webkit2gtk additionally built with libsoup3 support
I think this is fine. If we made sure that the webkit2gtk-4.0 packages still use the old libsoup2, I'm all fine with this going to the release pocket. For other release team members: I was also curious what changes does the new webkit2gtk version bring, especially that it felt like a big jump (.3 to .90 ?!). Apparently though .90 is simply the next version after .3, and the news entry is: += WebKitGTK 2.35.90 = What's new in WebKitGTK 2.35.90? - Fix scrolling with the mouse wheel on sites using overscroll-behavior. - Suspend web processes after some time in the process cache. - Fix renderning of horizontal scrollbars with themes enabling steppers. - Ensure EGL displays are terminated before web process exits. - Deinitialize gstreamer before web process exits. - Make fonts under XDG_DATA_DIRS available in web process sanbox. - Canonicalize paths passed to bubblewrap launcher. - Fix several crashes and rendering issues. - Translation updates: Hebrew. ** Changed in: webkit2gtk (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1964132 Title: [FFe] webkit2gtk additionally built with libsoup3 support Status in webkit2gtk package in Ubuntu: Triaged Bug description: Request --- 1. Add the new libsoup3-using packages in webkit2gtk 2. Build Epiphany with the new webkit2gtk 4.1 API built with libsoup3 Why Needed -- Our webkit2gtk packaging is built with libsoup2 (webkitgtk's 4.0 API). Debian's packaging recently added additional packages built with libsoup3 (webkitgtk's 4.1 API); these should not affect the existing libsoup2 packages. The libsoup2 > libsoup3 transition is a big one and will not happen for 22.04 LTS; I am hoping we can finish it for main by 23.04 but I haven't looked into it yet. It's expected that GNOME 43 will try to switch to libsoup3. Having webkit2gtk with libsoup3 support in 22.04 LTS will make it easier for newer versions of the GNOME Web Browser (epiphany) to run on this release. It also will make it easier to create snaps of GNOME 43 apps using a core22 base. My instinct is that we want libsoup3 and the new webkit+libsoup3 packages to stay in universe for 22.04 LTS and then Main Inclusion can be recommended for 22.10. It is not intended for any traditional (.deb) packages in 22.04 LTS itself to use these new packages except epiphany. I already uploaded the webkit2gtk merge/sync with this change. If this FFe is rejected, I can undo the addition. What Changed See above Build Test -- https://launchpad.net/ubuntu/+source/webkit2gtk/2.35.90-1ubuntu1 Install Test Not done yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1964132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions
Possibly related: https://bugzilla.mozilla.org/show_bug.cgi?id=1739339 https://bugzilla.mozilla.org/show_bug.cgi?id=1700591 ** Summary changed: - Cannot rearrange Firefox 98 browser tabs in Wayland sessions + Cannot rearrange Firefox (snap) browser tabs in Wayland sessions ** Bug watch added: Mozilla Bugzilla #1739339 https://bugzilla.mozilla.org/show_bug.cgi?id=1739339 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions Status in firefox package in Ubuntu: Confirmed Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
