[Desktop-packages] [Bug 597825]
Pushed by ffxbld-merge: https://hg.mozilla.org/releases/mozilla-beta/rev/8561bba0d491 [fenix] For https://github.com/mozilla-mobile/fenix/issues/25894 - Add firefox suggest header for lib suggestions -- 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/597825 Title: Menu accelerators in Firefox don't follow the GNOME policy. Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: firefox The current GNOME default is that menu accelerators are hidden, and shown when you press the ALT key. Firefox doesn't observe this policy and have their menu accelerators displayed all the time. Also, pressing ALT alone in GNOME and Firefox doesn't invoke any menu command. This inconsistent behavior is a usability issue and also makes Ubuntu desktop look unprofessional. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 Date: Wed Jun 23 21:37:05 2010 EcryptfsInUse: Yes FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A ProcEnviron: PATH=(custom, user) LANG=pl_PL.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/597825/+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 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg
I also tried removing the Mesa Vulkan driver and set `export LIBVA_DRIVER_NAME=i965`. That gets rid of the warning message but I still get a hang with Vivaldi and nextcloud-desktop still does not work. -- 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/2061257 Title: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg Status in wayland package in Ubuntu: Confirmed Bug description: Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g. - The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg. - The Slack app works correct in Xorg not in Wayland. - The Firefox snap works fine in both. I assume that these are related? Esp. that latter suggests to me that there is some library problem? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 19:58:00 2024 DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-11-11 (885 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 2.24 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 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: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2061257/+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 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg
Thanks. Sounds similar. My nautilus and gnome-control center do work strangely enough. But the more clues the better. -- 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/2061257 Title: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg Status in wayland package in Ubuntu: Confirmed Bug description: Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g. - The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg. - The Slack app works correct in Xorg not in Wayland. - The Firefox snap works fine in both. I assume that these are related? Esp. that latter suggests to me that there is some library problem? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 19:58:00 2024 DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-11-11 (885 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 2.24 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 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: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2061257/+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 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg
** Package changed: xorg (Ubuntu) => wayland ** Project changed: wayland => wayland (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/2061257 Title: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg Status in wayland package in Ubuntu: New Bug description: Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g. - The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg. - The Slack app works correct in Xorg not in Wayland. - The Firefox snap works fine in both. I assume that these are related? Esp. that latter suggests to me that there is some library problem? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 19:58:00 2024 DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-11-11 (885 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 2.24 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 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: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2061257/+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 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg
I tried the same upgrade and test on an old Sandy Bridge laptop. Everything works as expected there. So a Haswell issue perhaps? -- 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/2061257 Title: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg Status in xorg package in Ubuntu: New Bug description: Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g. - The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg. - The Slack app works correct in Xorg not in Wayland. - The Firefox snap works fine in both. I assume that these are related? Esp. that latter suggests to me that there is some library problem? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 19:58:00 2024 DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-11-11 (885 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 2.24 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 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: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061257/+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 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg
I tried the same test on an old Sandy Bridge laptop. Everything works as expected there. So a Haswell issue? -- 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/2061257 Title: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg Status in xorg package in Ubuntu: New Bug description: Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g. - The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg. - The Slack app works correct in Xorg not in Wayland. - The Firefox snap works fine in both. I assume that these are related? Esp. that latter suggests to me that there is some library problem? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 19:58:00 2024 DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-11-11 (885 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 2.24 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 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: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061257/+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 2061257] Re: With 24.04: Many graphical app failures under Wayland; no issues with Xorg
** Summary changed: - Many app failures under Wayland; no issues with Xorg + With 24.04: Many graphical app failures under Wayland; no issues with Xorg ** Summary changed: - With 24.04: Many graphical app failures under Wayland; no issues with Xorg + After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg -- 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/2061257 Title: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg Status in xorg package in Ubuntu: New Bug description: Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g. - The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg. - The Slack app works correct in Xorg not in Wayland. - The Firefox snap works fine in both. I assume that these are related? Esp. that latter suggests to me that there is some library problem? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 19:58:00 2024 DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-11-11 (885 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 2.24 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 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: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061257/+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 2061257] Re: Many app failures under Wayland; no issues with Xorg
I should also mention: this was an upgrade from 23.10 to 24.04 and all of the apps worked correctly in 23.10. -- 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/2061257 Title: Many app failures under Wayland; no issues with Xorg Status in xorg package in Ubuntu: New Bug description: Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g. - The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg. - The Slack app works correct in Xorg not in Wayland. - The Firefox snap works fine in both. I assume that these are related? Esp. that latter suggests to me that there is some library problem? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 19:58:00 2024 DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-11-11 (885 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 2.24 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 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: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061257/+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 2061257] [NEW] Many app failures under Wayland; no issues with Xorg
Public bug reported: Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g. - The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg. - The Slack app works correct in Xorg not in Wayland. - The Firefox snap works fine in both. I assume that these are related? Esp. that latter suggests to me that there is some library problem? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 19:58:00 2024 DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-11-11 (885 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 2.24 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 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: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble 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/2061257 Title: Many app failures under Wayland; no issues with Xorg Status in xorg package in Ubuntu: New Bug description: Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g. - The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg. - The Slack app works correct in Xorg not in Wayland. - The Firefox snap works fine in both. I assume that these are related? Esp. that latter suggests to me that there is some library problem? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 19:58:00 2024 DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA
[Desktop-packages] [Bug 2053235] [NEW] Upgrade libwayland on ubuntu 22.04.3 LTS
Public bug reported: We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see the following Weston-13.0 dependencies are not met for the same. libwayland*: required version >= 1.22.0 So we request to upgrade these packages on Ubuntu 22.04.3 LTS. The release of Ubuntu we are using: - Ubuntu 22.04.3 LTS Current version of the libwayland* packages: - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] What we expect to happen: - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS. ** 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/2053235 Title: Upgrade libwayland on ubuntu 22.04.3 LTS Status in wayland package in Ubuntu: New Bug description: We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see the following Weston-13.0 dependencies are not met for the same. libwayland*: required version >= 1.22.0 So we request to upgrade these packages on Ubuntu 22.04.3 LTS. The release of Ubuntu we are using: - Ubuntu 22.04.3 LTS Current version of the libwayland* packages: - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] What we expect to happen: - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2053235/+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 271216]
Pushed by dholb...@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/110a46d27bc3 Add reftests for this bug (which was fixed by the fragmentation fallback codepath). r=TYLin -- 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/271216 Title: Firefox prints one page only of long doc in a frame Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-firefox Firefox 3.01 printing: I have two frames, one containing a document that should take many pages to print. Firefox only prints one page, losing the rest. Typical site: http://www.cict.bhtafe.edu.au/subjects/ict321/bug.html It also prints one page for multi-frame documents from web access to M/S Exchange such as http://www.cict.bhtafe.edu.au/subjects/bug/MicrosoftOutlookWebAccess.html Another problem site is http://septemberfestival.com.au/index.php?option=com_content=view=4=4 which prints three pages but still loses a lot of content Package is Ubuntu 8.10 alpha5, but problem has occurred in many other distros and earlier versions of firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/271216/+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 1878617] Re: Apple pages file type should be added to MIME types
Fantastic! I can confirm that this is fixed on Ubuntu 23.10. -- 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/1878617 Title: Apple pages file type should be added to MIME types Status in shared-mime-info: Fix Released Status in mime-support package in Ubuntu: Invalid Status in shared-mime-info package in Ubuntu: Fix Released Bug description: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Hi, should gnome-shell-extension-ubuntu-dock 87ubuntu2 have already migrated from mantic-proposed? I'm assuming this process is automatic. Thanks. -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Thanks Pablo, I must've done something wrong. Installed it now and issue solved for me on mantic. -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
how can I install gnome-shell-extension-ubuntu-dock (87ubuntu2) for mantic? I don't see it in proposed. -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2039367] [NEW] Incorrect alignment of text on file deletion popups in Nautilus
Public bug reported: In Nautilus, the alignment of the text in the file deletion popups (when clearing Trash and permanently deleting an item) is wrong. As shown in the screen-capture, the title and subtitle text is wrongly aligned left instead of centered, causing the padding between the subtitle and title to be wrong, as the text in both cases inadvertently takes up two lines. On versions of Nautilus prior to Mantic (23.10), this bug was not present and the text appearance was correct. Please fix this appearance bug by changing the text alignment of both title and subtitle to center, such that the fills one line, like how it was prior to Mantic. The bug is demonstrated in the screen-capture. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 00:42:16 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'true' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 python3-nautilus 4.0-1build1 ** Affects: nautilus Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "Screen capture of Nautilus demonstrating the bug." https://bugs.launchpad.net/bugs/2039367/+attachment/5709527/+files/Screencast%20from%202023-10-15%2000-49-43.webm ** Also affects: nautilus Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2039367 Title: Incorrect alignment of text on file deletion popups in Nautilus Status in Nautilus: New Status in nautilus package in Ubuntu: New Bug description: In Nautilus, the alignment of the text in the file deletion popups (when clearing Trash and permanently deleting an item) is wrong. As shown in the screen-capture, the title and subtitle text is wrongly aligned left instead of centered, causing the padding between the subtitle and title to be wrong, as the text in both cases inadvertently takes up two lines. On versions of Nautilus prior to Mantic (23.10), this bug was not present and the text appearance was correct. Please fix this appearance bug by changing the text alignment of both title and subtitle to center, such that the fills one line, like how it was prior to Mantic. The bug is demonstrated in the screen-capture. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 00:42:16 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'true' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2039367/+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 2037655] [NEW] dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs
Public bug reported: On the latest 23.10 Mantic beta using firefox 118.0 spams the log with message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Description changed: - On the latest Mantic beta using firefox spams the log with message: + On the latest 23.10 Mantic beta using firefox 118.0 spams the log with + message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" -- 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/2037655 Title: dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs Status in firefox package in Ubuntu: New Bug description: On the latest 23.10 Mantic beta using firefox 118.0 spams the log with message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037655/+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 2037345] Re: error saving a new vpn
Same here, and to add even though the VPN was apparently not created, after rebooting or restarting NetworkManager the VPN is now there and now I'm not able to delete it without it coming back on next reboot. I've also tried deleting it using Advanced Network Configuration but it does not stick. -- 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/2037345 Title: error saving a new vpn Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I tried adding a new openvpn. I filled in all the information, but after I click the save button, it returns me to the network settings list, but that vpn is not present. Release: 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037345/+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 2037256] Re: 23.10 maximize window shortcut missing on fresh install
*** This bug is a duplicate of bug 2034998 *** https://bugs.launchpad.net/bugs/2034998 ** Tags added: mantic -- 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/2037256 Title: 23.10 maximize window shortcut missing on fresh install Status in gnome-shell package in Ubuntu: New Bug description: Sorry not sure what package to file this bug. On a fresh 23.10 Beta install the usual default shortcut for maximizing the current window (Meta + Up) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037256/+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 2037256] [NEW] 23.10 maximize window shortcut missing on fresh install
Public bug reported: Sorry not sure what package to file this bug. On a fresh 23.10 Beta install the usual default shortcut for maximizing the current window (Meta + Up) is disabled by default. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: 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/2037256 Title: 23.10 maximize window shortcut missing on fresh install Status in gnome-shell package in Ubuntu: New Bug description: Sorry not sure what package to file this bug. On a fresh 23.10 Beta install the usual default shortcut for maximizing the current window (Meta + Up) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037256/+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 2037115] [NEW] Focus is not given when a new window is launched from overview
Public bug reported: Ubuntu 23.04 Lunar Mutter 44.3 upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 >From the upstream bug: "When opening a new app window from the overview, the window focus is not properly given to the new window and the user input still go to the old focused window. Both windows appear to be in focus, however, the old window has the proper focus." This may cause data loss or security issues due to input still going to another application if the user is not aware. This appears to be fixed in the latest mutter release 44.5, any chance we can get this in Lunar? Thanks. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Description changed: + Ubuntu 23.04 Lunar + Mutter 44.3 + upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 From the upstream bug: "When opening a new app window from the overview, the window focus is not properly given to the new window and the user input still go to the old focused window. Both windows appear to be in focus, however, the old window has the proper focus." This may cause data loss or security issues due to input still going to another application if the user is not aware. This appears to be fixed in the latest mutter release 44.5, any chance we can get this in Lunar? Thanks. -- 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/2037115 Title: Focus is not given when a new window is launched from overview Status in mutter package in Ubuntu: New Bug description: Ubuntu 23.04 Lunar Mutter 44.3 upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 From the upstream bug: "When opening a new app window from the overview, the window focus is not properly given to the new window and the user input still go to the old focused window. Both windows appear to be in focus, however, the old window has the proper focus." This may cause data loss or security issues due to input still going to another application if the user is not aware. This appears to be fixed in the latest mutter release 44.5, any chance we can get this in Lunar? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2037115/+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 2017907] Re: cups-browsed high CPU usage
*** This bug is a duplicate of bug 2018504 *** https://bugs.launchpad.net/bugs/2018504 I have again experienced this after the update that was intended to address this. Just today I found cups-browsed using 100% CPU. This is on 23.04 Lunar with 2.0~rc1-0ubuntu1.1 cups-browsed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/2017907 Title: cups-browsed high CPU usage Status in cups-filters package in Ubuntu: Confirmed Bug description: Hi, Using Lunar wifi connected to an enterprise network. cups-browsed uses a lot of CPU %, I need to kill it to save my battery. 2.0rc1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2017907/+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 2022997] [NEW] Nautilus does not update view properly when deleting or moving files unless refreshed
Public bug reported: This issue happens in Nautilus 44.0, both on Wayland and X11, and has also been noted in upstream Gnome as well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2945 When deleting files, only the file being deleted should be shown as deleted, and when moving files/folders, the file/folder should appear as-is in the destination directory. However, this is not the case here. When deleting, the file/folder gets deleted correctly in the filesystem, but Nautilus does not update the view properly. The file being deleted still remains, instead showing another file to be deleted and when undoing delete operation via [Ctrl-Z], it shows a duplicate of the deleted file/folder. This issue persists until you refresh the view [F5], when the view shows up correctly. Also, when moving files/folders to another directory, the file/folder initially shows up as a blank 'text' file named '', until you refresh the view, when it shows up correctly. It is worth noting that this issue has apparently been fixed in Fedora and Arch for a while (see gitlab bug report linked above). Please implement the same fixes here in Ubuntu as well. System details: OS: Ubuntu Version: 23.04 GNOME Version: 44.0 Kernel: Linux 6.2.0-20-generic Package details: nautilus: Installed: 1:44.0-1ubuntu2 Candidate: 1:44.0-1ubuntu2 Version table: *** 1:44.0-1ubuntu2 500 500 http://ae.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 6 08:45:58 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 549)' InstallationDate: Installed on 2023-06-03 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 ** Affects: nautilus Importance: Unknown Status: Unknown ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Footage showing how Nautilus does not update the view correctly when deleting or moving files" https://bugs.launchpad.net/bugs/2022997/+attachment/5678086/+files/Screencast%20from%202023-06-06%2008-48-19.webm ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2945 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2945 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2945 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2022997 Title: Nautilus does not update view properly when deleting or moving files unless refreshed Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: This issue happens in Nautilus 44.0, both on Wayland and X11, and has also been noted in upstream Gnome as well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2945 When deleting files, only the file being deleted should be shown as deleted, and when moving files/folders, the file/folder should appear as-is in the destination directory. However, this is not the case here. When deleting, the file/folder gets deleted correctly in the filesystem, but Nautilus does not update the view properly. The file being deleted still remains, instead showing another file to be deleted and when undoing delete operation via [Ctrl-Z], it shows a duplicate of the deleted file/folder. This issue persists until you refresh the view [F5], when the view shows up correctly. Also, when moving files/folders to another directory, the file/folder initially shows up as a blank 'text' file named '', until you refresh the view, when it shows up correctly. It is worth noting that this issue has apparently been fixed in Fedora and Arch for a while (see gitlab bug report linked above). Please implement the same fixes here in Ubuntu as well. System details: OS: Ubuntu Version: 23.04 GNOME Version: 44.0 Kernel: Linux 6.2.0-20-generic Package details: nautilus: Installed: 1:44.0-1ubuntu2 Candidate:
[Desktop-packages] [Bug 1987976] Re: firefox black window on wayland
that was it, appears to be fixed on my end. Thanks. -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976] Re: firefox black window on wayland
On 23.04 I still get a black window on first firefox start with the proposed mutter update. -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1771041] Re: Remove gconf from Ubuntu
ooo-thumbnailer is an abandoned project and is being removed from Debian. Project link: https://launchpad.net/ooo-thumbnailer ** Changed in: ooo-thumbnailer (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1771041 Title: Remove gconf from Ubuntu Status in desktopnova package in Ubuntu: New Status in evolution-indicator package in Ubuntu: Fix Released Status in gconf package in Ubuntu: New Status in gconf-editor package in Ubuntu: New Status in gkdebconf package in Ubuntu: New Status in gnome-mastermind package in Ubuntu: New Status in gnome-phone-manager package in Ubuntu: New Status in gnome-xcf-thumbnailer package in Ubuntu: New Status in gnomint package in Ubuntu: New Status in gtkwave package in Ubuntu: Fix Released Status in guake-indicator package in Ubuntu: New Status in gyrus package in Ubuntu: Fix Released Status in jack-mixer package in Ubuntu: Fix Released Status in jana package in Ubuntu: New Status in mssh package in Ubuntu: New Status in ogmrip package in Ubuntu: New Status in ooo-thumbnailer package in Ubuntu: Invalid Status in planner package in Ubuntu: New Status in ogmrip package in Debian: Fix Released Bug description: gconf is being removed from Debian Testing. We should remove it from Ubuntu also. eclipse is troublesome. At a minimum, we can remove everything but eclipse and gconf. libgnome is sort of a blocker so do it first LP: #1771031 And remove libqt-gconf LP: #1740538 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktopnova/+bug/1771041/+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 1888942]
Fixing the dep here should allow selection which will handle the use cases here *** This bug has been marked as a duplicate of bug 1633203 *** -- 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/1888942 Title: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Invalid Bug description: Hi, if I click in an url in firefox, the whole url ist marked, i.e. highlighted. If I now use a click on the mousewheel to paste the content of the clipboard into another software, I discover that the url wasn't copied into the clipboard - the previous content ist filled in. That's confusing to me. I would expect: If I can mark an url in Firefox with a single mouse-click, which looks like a marking with a triple click, then it should be copied also in the clipboard. That would be a consisting behavior. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 78.0.2+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 1453 F pulseaudio /dev/snd/controlC1: matthias 1453 F pulseaudio /dev/snd/pcmC1D0c: matthias 1453 F...m pulseaudio /dev/snd/pcmC1D0p: matthias 1453 F...m pulseaudio BuildID: 20200708170202 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 16:44:27 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2020-04-24 (92 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 600 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=74.0.1/20200403064753 (Out of date) Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET53W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS06G0J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90GJVAH dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS06G0J dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1888942/+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 1987631] Re: Screencast only records one second
It seems like this has stalled again and I don't understand why. Patches were posted about 1 month ago and they got some testing feedback within 2 days of availability. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstreamer: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 2002098] [NEW] Seems like my GPU isn't supported
Public bug reported: (base) walid@len:~$ lspci | grep VGA :00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01) (base) walid@len:~$ sudo lshw -C video [sudo] password for walid: *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 01 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080 resources: iomemory:600-5ff iomemory:400-3ff irq:158 memory:600200-6002ff memory:40-400fff ioport:3000(size=64) memory:c-d memory:401000-4016ff memory:402000-40 (base) walid@len:~$ lspci -nn |egrep "VGA|Display" :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a78] (rev 01) (base) walid@len:~$ sudo apt-get install xserver-xorg-video-intel Reading package lists... Done Building dependency tree... Done Reading state information... Done xserver-xorg-video-intel is already the newest version (2:2.99.917+git20210115-1). xserver-xorg-video-intel set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 6 11:30:53 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f89] MachineType: LENOVO 82FG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f5b7aa1d-e67f-4b72-8621-88ab6b130991 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2021 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: FHCN59WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ITL05 dmi.ec.firmware.release: 1.59 dmi.modalias: dmi:bvnLENOVO:bvrFHCN59WW:bd08/26/2021:br1.59:efr1.59:svnLENOVO:pn82FG:pvrIdeaPad515ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad515ITL05:skuLENOVO_MT_82FG_BU_idea_FM_IdeaPad515ITL05: dmi.product.family: IdeaPad 5 15ITL05 dmi.product.name: 82FG dmi.product.sku: LENOVO_MT_82FG_BU_idea_FM_IdeaPad 5 15ITL05 dmi.product.version: IdeaPad 5 15ITL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2002098 Title: Seems like my GPU isn't supported Status in xorg package in Ubuntu: New Bug description: (base) walid@len:~$ lspci | grep VGA :00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01) (base) walid@len:~$ sudo lshw -C video [sudo] password for walid: *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 01 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080 resources: iomemory:600-5ff iomemory:400-3ff irq:158 memory:600200-6002ff memory:40-400fff ioport:3000(size=64) memory:c-d
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
@binli - here are my testing results with patches: - gstreamer1.0_1.20.3-0ubuntu2.debdiff - gst-plugins-base1.0_1.20.1-2.debdiff - pipewire_0.3.48-1ubuntu4.debdiff Gnome Shell screen recorder: pass gst-launch-1.0 video preview: pass Gnome Shell screen recorder while gst-launch-1.0 video preview is visible: pass Cheese video preview: pass* Cheese has an asterisk* because I ran into other problems: 1) intermittently, selecting a filter can freeze the preview until a different filter is selected. 2) lp:1994928 Camera hardware tested (two different computers): 13d3:5405 IMC Networks Integrated Camera (Lenovo T14s Gen2 AMD Laptop) 046d:082d Logitech, Inc. HD Pro Webcam C920 - Details of how I built the packages and which ones I installed. Note that I only installed packages that are part of a default Ubuntu jammy installation: http://releases.ubuntu.com/jammy/ubuntu-22.04.1-desktop- amd64.manifest . $ wget https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638524/+files/gstreamer1.0_1.20.3-0ubuntu2.debdiff $ wget https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638525/+files/gst-plugins-base1.0_1.20.1-2.debdiff $ wget https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638528/+files/pipewire_0.3.48-1ubuntu4.debdiff $ pull-lp-source gstreamer1.0 1.20.3-0ubuntu1 $ pull-lp-source gst-plugins-base1.0 1.20.1-1 $ pull-lp-source pipewire 0.3.48-1ubuntu3 $ patch -p1 -d gstreamer1.0-1.20.3 < gstreamer1.0_1.20.3-0ubuntu2.debdiff $ patch -p1 -d gst-plugins-base1.0-1.20.1 < gst-plugins-base1.0_1.20.1-2.debdiff $ patch -p1 -d pipewire-0.3.48 < pipewire_0.3.48-1ubuntu4.debdiff $ sudo apt-get build-dep gstreamer1.0 gst-plugins-base1.0 pipewire $ cd gstreamer1.0 $ dpkg-buildpackage -rfakeroot -b $ cdu .. $ sudo dpkg -i gir1.2-gstreamer-1.0_1.20.3-0ubuntu2_amd64.deb gstreamer1.0-tools_1.20.3-0ubuntu2_amd64.deb libgstreamer1.0-0_1.20.3-0ubuntu2_amd64.deb libgstreamer1.0-dev_1.20.3-0ubuntu2_amd64.deb $ cd gst-plugins-base1.0-1.20.1 $ dpkg-buildpackage -rfakeroot -b $ cdu .. $ sudo dpkg -i gir1.2-gst-plugins-base-1.0_1.20.1-2_amd64.deb gstreamer1.0-alsa_1.20.1-2_amd64.deb gstreamer1.0-gl_1.20.1-2_amd64.deb gstreamer1.0-plugins-base_1.20.1-2_amd64.deb gstreamer1.0-plugins-base-apps_1.20.1-2_amd64.deb gstreamer1.0-x_1.20.1-2_amd64.deb libgstreamer-gl1.0-0_1.20.1-2_amd64.deb libgstreamer-plugins-base1.0-0_1.20.1-2_amd64.deb $ cd pipewire-0.3.48 $ dpkg-buildpackage -rfakeroot -b $ cd .. $ sudo dpkg -i gstreamer1.0-pipewire_0.3.48-1ubuntu4_amd64.deb libpipewire-0.3-0_0.3.48-1ubuntu4_amd64.deb libpipewire-0.3-common_0.3.48-1ubuntu4_all.deb libpipewire-0.3-modules_0.3.48-1ubuntu4_amd64.deb libspa-0.2-modules_0.3.48-1ubuntu4_amd64.deb pipewire_0.3.48-1ubuntu4_amd64.deb pipewire-bin_0.3.48-1ubuntu4_amd64.deb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
@binli - I'm still on pipewire from jammy-updates: $ apt-cache policy pipewire pipewire: Installed: 0.3.48-1ubuntu2 Candidate: 0.3.48-1ubuntu2 Version table: *** 0.3.48-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.3.48-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstreamer: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
@binli - I never found a need to update pipewire; the gstreamer patches (for gstreamer and gst-plugins-base) seem to be sufficient in my testing. I tested your gstreamer & gst-plugins-base packages and they work the same as the ones I built. I think you could drop "-0ubuntu1binli1" from the symbols update though: - _gst_meta_tag_memory_reference@Base 1.20.3-0ubuntu1binli1 + _gst_meta_tag_memory_reference@Base 1.20.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
@binli In comment #14 you wrote that the pipewire commit wasn't enough. Did something change? That comment was the reason I tested a gstreamer patch which seems to work well. See conversation following #14. -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: Confirmed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1873398] Re: gnome-disks won't do SMART on NVME drive
** Description changed: I'm running 20.04 beta amd64 Desktop from a USB stick of the live ISO. I opened Disks (gnome-disks) and it sees all my drives, but it won't show SMART stats on my NVME drive (Samsung SSD 970 EVO Plus 500GB). The SMART menu item is greyed out. It works fine on other drives. The NVME has SMART support; it works fine with smartctl -a /dev/nvme0n1 for example. (Though smartctl is not in this live ISO, I have apt-get installed it at another time and tried it; and it works fine in the Ubuntu 18.04 that is installed on this machine.) I've attached a screencast showing the failure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 07:32:43 2020 ExecutablePath: /usr/bin/gnome-disks LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANG=C.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANG=C.UTF-8 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1873398 Title: gnome-disks won't do SMART on NVME drive Status in GNOME Disks: New Status in gnome-disk-utility package in Ubuntu: Triaged Bug description: I'm running 20.04 beta amd64 Desktop from a USB stick of the live ISO. I opened Disks (gnome-disks) and it sees all my drives, but it won't show SMART stats on my NVME drive (Samsung SSD 970 EVO Plus 500GB). The SMART menu item is greyed out. It works fine on other drives. The NVME has SMART support; it works fine with smartctl -a /dev/nvme0n1 for example. (Though smartctl is not in this live ISO, I have apt-get installed it at another time and tried it; and it works fine in the Ubuntu 18.04 that is installed on this machine.) I've attached a screencast showing the failure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 07:32:43 2020 ExecutablePath: /usr/bin/gnome-disks LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1873398/+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 1987631] Re: Screencast only records one second
Just a single bump in hopes that a maintainer will see my above comments. It would be wonderful if we could either cherry-pick that commit or get a merge of gstreamer 1.20.4 in jammy (similar to https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1980239 but unfortunately Jeremy Bicha did not respond to my inquiry about merging 1.20.4). Screen recording in jammy is still broken but I've tested this patch on two machines with success now. So, I'm hopeful it will be picked up. -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: Confirmed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1997512] [NEW] Ubuntu logo in About page of Settings has black text in dark mode in Ubuntu 22.10
Public bug reported: In Ubuntu 22.10, in GNOME Settings, the Ubuntu logo on the About page has some appearance issues: 1. In dark mode, the image normally should have white text. This is not the case here. The Ubuntu logo, even in dark mode still has black text. 2. Also, when maximising or enlarging the window, the Ubuntu logo becomes blurry. This might be because the logo file is a bitmap or raster image. Ideally, the image should be a vector image, so that it looks clear at all sizes, or the logo should not be made to resize with the window. The above appearance bugs are shown in the screenshot. Please fix them as soon as possible. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 23 07:42:56 2022 InstallationDate: Installed on 2022-09-24 (59 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "Screenshot showing appearance bugs in Ubuntu logo" https://bugs.launchpad.net/bugs/1997512/+attachment/5632245/+files/Screenshot%20from%202022-11-17%2015-13-50.png -- 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/1997512 Title: Ubuntu logo in About page of Settings has black text in dark mode in Ubuntu 22.10 Status in gnome-control-center package in Ubuntu: New Bug description: In Ubuntu 22.10, in GNOME Settings, the Ubuntu logo on the About page has some appearance issues: 1. In dark mode, the image normally should have white text. This is not the case here. The Ubuntu logo, even in dark mode still has black text. 2. Also, when maximising or enlarging the window, the Ubuntu logo becomes blurry. This might be because the logo file is a bitmap or raster image. Ideally, the image should be a vector image, so that it looks clear at all sizes, or the logo should not be made to resize with the window. The above appearance bugs are shown in the screenshot. Please fix them as soon as possible. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 23 07:42:56 2022 InstallationDate: Installed on 2022-09-24 (59 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1997512/+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 1989602] Re: Delay in updating charge status in Ubuntu 22.04 LTS
This bug does not seem to be present in Ubuntu 22.10, on the same hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1989602 Title: Delay in updating charge status in Ubuntu 22.04 LTS Status in upower package in Ubuntu: New Bug description: I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS. When plugging in the charger, the current charge status in the top bar and Settings shows 'Not Charging' for a few minutes and then shows that the system is charging normally. When unplugging the charger the same happens; the charge status shows 'Not Charging' for a few minutes, and then shows the correct charge status. Normally, the change in power status should be instantaneous. In short, there is a delay in the OS in showing the current charge status. Upon further research, it was found that the 'upower' service is to blame; it polls every two minutes(i.e., it refreshes the charge status every two minutes); causing a delay in charge status. This is further compounded by the fact that restarting upower service, or the system as a whole makes the system to show the correct charge status. However, I did not have this problem on another system, a HP Pavilion x360 14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS. There, the power status behaves normally with no delays whatsoever. Please look into this issue and fix this bug as soon as possible. One suggestion would be to increase the polling frequency of upower from 2 mins. to something lesser, so that the charge status shows correctly. upower version: UPower client version 0.99.17 UPower daemon version 0.99.17 OS: Description: Ubuntu 22.04.1 LTS Release: 22.04 Kernel: Linux 5.15.0-47-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: upower 0.99.17-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 20:41:16 2022 InstallationDate: Installed on 2022-09-12 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1989602/+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 1997147] [NEW] App theme for legacy GTK3 apps inadvertently changes to light mode when Appearance pane in Settings is clicked/made active in Ubuntu 22.10
Public bug reported: This bug happens with dark mode enabled, whenever I open Settings with Appearance pane open, or I enter Appearance pane from other panes in Settings. Whenever I do so, the app theme for legacy GTK3 applications (those not supporting the new GTK dark mode API) inadvertently changes to light mode. To turn back dark mode on for legacy apps, I have to use the toggle in Quick Settings, or click on any of the theme circles. Normally, the dark mode theme for legacy apps should not change whenever Settings is opened with Appearance pane open, or Appearance pane is selected from other panes in Settings, just like GTK3 applications using the new dark mode API, and GTK4+libadwaita apps (which are not affected by this bug). A recording of the bug in action is attached along with this report. Ubuntu release details: Description:Ubuntu 22.10 Release:22.10 Package details: gnome-control-center: Installed: 1:43.0-1ubuntu2 Candidate: 1:43.0-1ubuntu2 Version table: *** 1:43.0-1ubuntu2 500 500 http://ae.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 19 17:32:30 2022 InstallationDate: Installed on 2022-09-24 (56 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "Screen capture showing the bug in action. It shows two apps: (Gufw (legacy GTK3), Software & Updates (GTK3 with new dark mode API support), and Settings (GTK4+libadwaita)" https://bugs.launchpad.net/bugs/1997147/+attachment/5631569/+files/Screencast%20from%202022-11-19%2017-42-54.webm -- 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/1997147 Title: App theme for legacy GTK3 apps inadvertently changes to light mode when Appearance pane in Settings is clicked/made active in Ubuntu 22.10 Status in gnome-control-center package in Ubuntu: New Bug description: This bug happens with dark mode enabled, whenever I open Settings with Appearance pane open, or I enter Appearance pane from other panes in Settings. Whenever I do so, the app theme for legacy GTK3 applications (those not supporting the new GTK dark mode API) inadvertently changes to light mode. To turn back dark mode on for legacy apps, I have to use the toggle in Quick Settings, or click on any of the theme circles. Normally, the dark mode theme for legacy apps should not change whenever Settings is opened with Appearance pane open, or Appearance pane is selected from other panes in Settings, just like GTK3 applications using the new dark mode API, and GTK4+libadwaita apps (which are not affected by this bug). A recording of the bug in action is attached along with this report. Ubuntu release details: Description: Ubuntu 22.10 Release: 22.10 Package details: gnome-control-center: Installed: 1:43.0-1ubuntu2 Candidate: 1:43.0-1ubuntu2 Version table: *** 1:43.0-1ubuntu2 500 500 http://ae.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 19 17:32:30 2022 InstallationDate: Installed on 2022-09-24 (56 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1997147/+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 1987631] Re: Screencast only records one second
I took the time to figure out how ubuntu packages are built and managed to test the patch in my previous comment (#15) on Jammy. My tests showed great results; it would be great to get additional confirmation. Sorry for the verbosity here, but this is new to me: 1. sudo apt-get source gstreamer1.0 gst-plugins-base1.0 2. sudo apt-get build-dep gstreamer1.0 gst-plugins-base1.0 3. apply patches from my previous comment (in gists) to respective source 4. add symbol '_gst_meta_tag_memory_reference@Base 1.20.1' to gstreamer1.0/debian/libgstreamer1.0-0.symbols 5. build gstreamer: dpkg-buildpackage -rfakeroot -b 6. install the built libgstreamer1.0-dev deb package so that the new symbol is available when building plugins 7. build gst-plugins-base: dpkg-buildpackage -rfakeroot -b 8. install all produced .deb packages Video attached after gstreamer update to show the effect. I subsequently reinstalled stock gstreamer and confirmed the broken video recording happened again. ** Attachment added: "Screencast from 11-15-2022 05:39:43 PM.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5630900/+files/Screencast%20from%2011-15-2022%2005%3A39%3A43%20PM.webm -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
Following up on my earlier comment (#9), is it worth trying to apply patch https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/2928 to gstreamer1.0 and gst-plugins-base1.0? I was able to confirm the patch picks cleanly and gstreamer still compiles when applied to the current jammy refs: https://git.launchpad.net/ubuntu/+source/gstreamer1.0/log/?h=ubuntu%2Fjammy and https://git.launchpad.net/ubuntu/+source/gst-plugins- base1.0/log/?h=ubuntu%2Fjammy . Original patch file: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/2928.patch Patch file broken into... gstreamer1.0: https://gist.github.com/mdmower/a758ec83b525ce8b1a59774782ec8abd gst-plugins-base1.0: https://gist.github.com/mdmower/de7245603f12c3ef413c0beba1f02628 I haven't created Ubuntu packages before and I'm wary of trying to overwrite gstreamer on my computer; sorry, I haven't gone beyond verifying it compiles. -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
I posted duplicate report https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993912 which was merged into this one. In that report's comments, I noted that this issue was fixed in jammy by applying https://gitlab.gnome.org/GNOME/gnome- shell/-/commit/d32c03488fcf6cdb0ca2e99b0ed6ade078460deb locally, but I left out a key detail... I had also upgraded pipewire from https://launchpad.net/~pipewire-debian/+archive/ubuntu/pipewire-upstream . I'm sorry for omitting that detail because it's important - from the upstream bug report https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585#note_1559914 : > I think we can close this given that the workaround that has now been > released in 43 and 42.5 is all we can do from the shell side and the required > pipewire 0.3.57 has been out for a while now as well. > The proper fix is still tracked in > https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/2928 . Jammy is still using pipewire 0.3.48. So, for Jammy, perhaps this needs to be fixed by backporting https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/2928 ? -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1995236] Re: Xsessions has_option code error with fix
And now OPTIONS has to be exported, and probably should be protected against being empty in the new file. So it becomes ${OPTIONS:-} and ${1:-} What else have I missed? -- 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/1995236 Title: Xsessions has_option code error with fix Status in xorg package in Ubuntu: New Bug description: Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug reports and failed fixes for this over several years and releases. There are a couple of problems in /etc/X11/Xsessions where it fails to handle options, causing bogus error messages and, doubtless, many errors. The first bug is that the entire options file, including comments, is read into a variable. Where the variable "OPTIONS" is assigned; Replacing "cat" with "grep" strips out comments and blank lines; $ diff Xsession Xsession.orig 65c65 < grep -v "^\s*\#\|^\s*$" "$OPTIONFILE" --- > cat "$OPTIONFILE" The second problem is that checking for a non-existent directory inside a command substitution does not work. It just appends garbage onto the output string. That is probably a bug in BASH, but I defer to your opinion there. The immediate work around is to create an empty directory so that the test does not fail. Better still, force the creation of the directory and remove the test. eg. change this; OPTIONS="$( if [ -r "$OPTIONFILE" ]; then cat "$OPTIONFILE" fi if [ -d /etc/X11/Xsession.options.d ]; then run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d '\n' cat fi )" to this; OPTIONSDIR=/etc/X11/Xsession.options.d mkdir --parents ${OPTIONSDIR} OPTIONS="$( if [ -r "$OPTIONFILE" ]; then grep -v "^\s*\#\|^\s*$" "$OPTIONFILE" fi run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d '\n' cat )" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 31 16:33:14 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2022-10-20 (11 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 fbcon=rotate:2 initrd=\initrd.img SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video
[Desktop-packages] [Bug 1995236] Re: Xsessions has_option code error with fix
Bother. There is a third problem, a scope issue of some sort. The errors in ~/.xsession.error go away if "has_options" is moved from Xsession to its own file in Xsession.d I don't see why sourceing it should make any difference, but it does. $ cat /etc/X11/Xsession.d/00 has_option () { # Ensure that a later no-foo overrides an earlier foo if [ "$(echo "$OPTIONS" | grep -Eo "^(no-)?$1\>" | tail -n 1)" == "$1" ]; then return 0 else return 1 fi } Also I changed a "=" to "==", but that should be cosmetic. -- 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/1995236 Title: Xsessions has_option code error with fix Status in xorg package in Ubuntu: New Bug description: Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug reports and failed fixes for this over several years and releases. There are a couple of problems in /etc/X11/Xsessions where it fails to handle options, causing bogus error messages and, doubtless, many errors. The first bug is that the entire options file, including comments, is read into a variable. Where the variable "OPTIONS" is assigned; Replacing "cat" with "grep" strips out comments and blank lines; $ diff Xsession Xsession.orig 65c65 < grep -v "^\s*\#\|^\s*$" "$OPTIONFILE" --- > cat "$OPTIONFILE" The second problem is that checking for a non-existent directory inside a command substitution does not work. It just appends garbage onto the output string. That is probably a bug in BASH, but I defer to your opinion there. The immediate work around is to create an empty directory so that the test does not fail. Better still, force the creation of the directory and remove the test. eg. change this; OPTIONS="$( if [ -r "$OPTIONFILE" ]; then cat "$OPTIONFILE" fi if [ -d /etc/X11/Xsession.options.d ]; then run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d '\n' cat fi )" to this; OPTIONSDIR=/etc/X11/Xsession.options.d mkdir --parents ${OPTIONSDIR} OPTIONS="$( if [ -r "$OPTIONFILE" ]; then grep -v "^\s*\#\|^\s*$" "$OPTIONFILE" fi run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d '\n' cat )" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 31 16:33:14 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2022-10-20 (11 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 fbcon=rotate:2 initrd=\initrd.img SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubu
[Desktop-packages] [Bug 1995236] [NEW] Xsessions has_option code error with fix
Public bug reported: Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug reports and failed fixes for this over several years and releases. There are a couple of problems in /etc/X11/Xsessions where it fails to handle options, causing bogus error messages and, doubtless, many errors. The first bug is that the entire options file, including comments, is read into a variable. Where the variable "OPTIONS" is assigned; Replacing "cat" with "grep" strips out comments and blank lines; $ diff Xsession Xsession.orig 65c65 < grep -v "^\s*\#\|^\s*$" "$OPTIONFILE" --- > cat "$OPTIONFILE" The second problem is that checking for a non-existent directory inside a command substitution does not work. It just appends garbage onto the output string. That is probably a bug in BASH, but I defer to your opinion there. The immediate work around is to create an empty directory so that the test does not fail. Better still, force the creation of the directory and remove the test. eg. change this; OPTIONS="$( if [ -r "$OPTIONFILE" ]; then cat "$OPTIONFILE" fi if [ -d /etc/X11/Xsession.options.d ]; then run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d '\n' cat fi )" to this; OPTIONSDIR=/etc/X11/Xsession.options.d mkdir --parents ${OPTIONSDIR} OPTIONS="$( if [ -r "$OPTIONFILE" ]; then grep -v "^\s*\#\|^\s*$" "$OPTIONFILE" fi run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d '\n' cat )" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 31 16:33:14 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2022-10-20 (11 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 fbcon=rotate:2 initrd=\initrd.img SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1995236 Title: Xsessions has_option code error with fix Status in xorg package in Ubuntu: New Bug description: Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug reports and failed fixes for this over se
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
Also have this. Decided to update drivers after failure to run steam app. autoinstall fails -- 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/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Hello, we received a drive-by complaint about the ubuntu-drivers autoinstall tool: < Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command < Fhazal> this error appear when i try to auto install recommended driver < Fhazal> https://pastebin.com/ydZVFT24 The contents of the pastebin: Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 513, in greet() File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke return __callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke return __callback(*args, **kwargs) File "/usr/bin/ubuntu-drivers", line 432, in autoinstall command_install(config) File "/usr/bin/ubuntu-drivers", line 187, in command_install UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install) File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in nvidia_desktop_pre_installation_hook with_nvidia_kms = version >= 470 UnboundLocalError: local variable 'version' referenced before assignment Skimming the version on my system it sure feels plausible: def nvidia_desktop_pre_installation_hook(to_install): '''Applies changes that need to happen before installing the NVIDIA drivers''' with_nvidia_kms = False # Enable KMS if nvidia >= 470 for package_name in to_install: if package_name.startswith('nvidia-driver-'): try: version = int(package_name.split('-')[-1]) except ValueError: pass finally: with_nvidia_kms = version >= 470 if with_nvidia_kms: set_nvidia_kms(1) If there was an exception splitting, indexing, or converting to an int, that 'version' variable may not have a value. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1993019/+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 1993912] Re: GNOME screen recorder drops vast majority of frames
It looks like the fix for this was just prepared for jammy-proposed a couple of days ago: https://git.launchpad.net/ubuntu/+source/gnome- shell/commit/js/dbusServices/screencast/screencastService.js?h=applied/ubuntu/jammy- proposed=40715f8dfa77b9edd5a8fad033718df4d4d65440 I've tested this change locally and verified it resolves the issue: 1. $ mkdir -p ~/.gnome-shell-custom-overlays/Screencast 2. $ gresource extract /usr/share/gnome-shell/org.gnome.Shell.Screencast.src.gresource /org/gnome/Shell/Screencast/js/screencastService.js > ~/.gnome-shell-custom-overlays/Screencast/screencastService.js 3. Apply changes to screencastService.js from https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488fcf6cdb0ca2e99b0ed6ade078460deb ) 4. Add the following to ~/.profile: export G_RESOURCE_OVERLAYS="/org/gnome/Shell/Screencast/js/screencastService.js=$HOME/.gnome-shell-custom-overlays/Screencast/screencastService.js" 5. Logout and login -- 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/1993912 Title: GNOME screen recorder drops vast majority of frames Status in gnome-shell package in Ubuntu: New Bug description: When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 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/gnome-shell/+bug/1993912/+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 1993912] Re: GNOME screen recorder drops vast majority of frames
I believe this is the same issue as reported here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5585 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 -- 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/1993912 Title: GNOME screen recorder drops vast majority of frames Status in gnome-shell package in Ubuntu: New Bug description: When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 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/gnome-shell/+bug/1993912/+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 1993912] Re: GNOME screen recorder drops vast majority of frames
Additional testing: - My laptop (also with AMD graphics, Lenovo T14s Gen2) running the same OS also exhibits this issue. - Switching my session from wayland to XOrg does not remedy the problem. - Installing AMD drivers from https://www.amd.com/en/support/linux-drivers does not remedy the problem. ** Description changed: - I was trying to screen record for a different bug report, but I can't - seem to screen record properly and so find myself here reporting this - bug. When I try to record a region on my screen, after about 4 seconds - the frames stop updating. In the attached video, I am toggling between - the two visible windows every half second, roughly. The only frame - updates after 0:04 occur at 0:33, 1:07, and 1:40. + When I try to record a region on my screen, after about 4 seconds the + frames stop updating. In the attached video, I am toggling between the + two visible windows every half second, roughly. The only frame updates + after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1993912 Title: GNOME screen recorder drops vast majority of frames Status in gnome-shell package in Ubuntu: New Bug description: When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 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/gnome-shell/+bug/1993912/+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 1993912] [NEW] GNOME screen recorder drops vast majority of frames
Public bug reported: I was trying to screen record for a different bug report, but I can't seem to screen record properly and so find myself here reporting this bug. When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screencast from 10-22-2022 12:09:45 PM.webm" https://bugs.launchpad.net/bugs/1993912/+attachment/5626020/+files/Screencast%20from%2010-22-2022%2012%3A09%3A45%20PM.webm -- 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/1993912 Title: GNOME screen recorder drops vast majority of frames Status in gnome-shell package in Ubuntu: New Bug description: I was trying to screen record for a different bug report, but I can't seem to screen record properly and so find myself here reporting this bug. When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 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/gnome-shell/+bug/1993912/+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 1988301] Re: Does not implement data-ciphers, only cipher which OpenVPN 2.5+ ignores, hence can fail to connect
Thank you! I'm a bit of a newb, so I found I had to restart the network manager before it took effect. sudo systemctl restart NetworkManager.service I'm referencing it here for other newbs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1988301 Title: Does not implement data-ciphers, only cipher which OpenVPN 2.5+ ignores, hence can fail to connect Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: It's no longer possible to use the cipher option in NetworkManager as it's ignored by OpenVPN; and the default list of data-ciphers is applied, making it impossible to connect to an AES-128-CBC endpoint from NetworkManager. There does not appear any way to forward the data-ciphers config, even if I hand edited the nmconnection file to add a data-ciphers line it is ignored. More insight is available to Canonical folks in https://rt.admin.canonical.com/Ticket/Display.html?id=153000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1988301/+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 1993327] [NEW] Misalignment of label alongside Icon size slider under Ubuntu Desktop page
Public bug reported: In System Settings, the label alongside the Icon size slider under Ubuntu Desktop page is misaligned with the slider, as shown in the attached screenshot. It is placed a bit too low from the position of the slider. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 19:58:27 2022 InstallationDate: Installed on 2022-09-24 (24 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "Screenshot showing the misaligned label" https://bugs.launchpad.net/bugs/1993327/+attachment/5624884/+files/Screenshot%20from%202022-10-18%2019-53-35.png -- 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/1993327 Title: Misalignment of label alongside Icon size slider under Ubuntu Desktop page Status in gnome-control-center package in Ubuntu: New Bug description: In System Settings, the label alongside the Icon size slider under Ubuntu Desktop page is misaligned with the slider, as shown in the attached screenshot. It is placed a bit too low from the position of the slider. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 19:58:27 2022 InstallationDate: Installed on 2022-09-24 (24 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993327/+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 1992267] [NEW] Incorrect alignment of labels in Wi-Fi properties popup
Public bug reported: In Ubuntu 22.10, in the Settings app, the labels in the IPv4 and IPv6 section of the Wi-Fi popup (shown in screenshot) seems to be misaligned with its corresponding entry boxes. For example, under IPv4 section, 'Netmask' and 'Gateway' are not properly aligned with the 2nd and the 3rd entry fields, and are above the same entry field. A similar case is also present under the IPv6 section as well. I do not know whether this is a bug or not, but this was not the case in earlier versions of Ubuntu, where the labels were perfectly aligned with its corresponding entry boxes. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 9 08:42:49 2022 InstallationDate: Installed on 2022-09-24 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "IPv4 section of Wi-Fi popup showing the misaligned labels" https://bugs.launchpad.net/bugs/1992267/+attachment/5622413/+files/Screenshot%20from%202022-10-09%2008-39-37.png -- 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/1992267 Title: Incorrect alignment of labels in Wi-Fi properties popup Status in gnome-control-center package in Ubuntu: New Bug description: In Ubuntu 22.10, in the Settings app, the labels in the IPv4 and IPv6 section of the Wi-Fi popup (shown in screenshot) seems to be misaligned with its corresponding entry boxes. For example, under IPv4 section, 'Netmask' and 'Gateway' are not properly aligned with the 2nd and the 3rd entry fields, and are above the same entry field. A similar case is also present under the IPv6 section as well. I do not know whether this is a bug or not, but this was not the case in earlier versions of Ubuntu, where the labels were perfectly aligned with its corresponding entry boxes. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 9 08:42:49 2022 InstallationDate: Installed on 2022-09-24 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1992267/+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 1975884] Re: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added"
I have the same problem on 2 installs out of 3. And no "Removing a network device that was not added" in /var/log/syslog. I also found that the problem does not seem to occur on Xorg, only on Wayland. And I also found that the work around is to go to a console and then back using (e.g.) ctrl-alt-F1 then ctrl-alt-F2. -- 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/1975884 Title: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added" Status in gnome-shell package in Ubuntu: Confirmed Bug description: As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1769981/comments/25 , I've been observing an issue when unlocking my computer (usually from a screen lock state, not hibernation/sleep) where after entering the first few characters of my password the screen freezes for 10-20 seconds before I can do any type of input (mouse, touch, keyboard). I've also seen it happen when having touch / gesture input switch between displaying the user name and the password field - where the screen can get stuck in the animation in an interstitial state for a number of seconds. I've largely been noticing this since upgrading from Ubuntu 21.10 to 22.04. It doesn't happen all the time, but often enough to file an issue for. So far I've tried: - Disabling the 'blur my shell' extension - still encountered the issue again eventually. - Looking for anything associated with this in /var/crash - couldn't find anything. - Looking for anything associated at errors.ubuntu.com for my id. What I may eventually try: - Seeing if this may depend on having too many browser tabs / apps open. Currently not in a position to do this. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 19:19:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (315 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/+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 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
Another surprising observation: Wayland seems to work just fine for me, it's only X11 that has the maximization shrinking bug. 'headerbar' can be true or false on Wayland with 22.04. I tried it on two different installs with the same behavior. Okay then. I guess I'll use Wayland. I liked to have the restart feature which Wayland doens't have, but I think I'd rather not have this gnome-terminal bug more than 'r'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+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 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
@peterx14 I did a few more experiments. One needs a new gnome session altogether for the 'headerbar' false change to work. I tried this a few times to confirm. Just killing all the terminals is not enough. However, when I login/out or kill gnome-session to restart the session manager, the problem is fixed. The side effect is that one loses all the nice gnome-terminal decoration (hamburger menu, find button, etc.). Oh well. Take your choice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+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 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
Hm, perhaps I misremembered the tweak. I do recall that 22.04 did not work initially. I applied the dconf menu setting and it started to work. I reset the dconf legacy menu setting just now and it still works (i.e. no shrinking after maximization). So I'm mystified . . . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+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 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
The bug disappeared for some old installs but not all. For those that still had the bug, the following seemed to fix the problem: dconf write /org/gnome/terminal/legacy/headerbar '@mb false' @peterx14 maybe that would help in your case as well? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+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 1989602] [NEW] Delay in updating charge status in Ubuntu 22.04 LTS
Public bug reported: I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS. When plugging in the charger, the current charge status in the top bar and Settings shows 'Not Charging' for a few minutes and then shows that the system is charging normally. When unplugging the charger the same happens; the charge status shows 'Not Charging' for a few minutes, and then shows the correct charge status. Normally, the change in power status should be instantaneous. In short, there is a delay in the OS in showing the current charge status. Upon further research, it was found that the 'upower' service is to blame; it polls every two minutes(i.e., it refreshes the charge status every two minutes); causing a delay in charge status. This is further compounded by the fact that restarting upower service, or the system as a whole makes the system to show the correct charge status. However, I did not have this problem on another system, a HP Pavilion x360 14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS. There, the power status behaves normally with no delays whatsoever. Please look into this issue and fix this bug as soon as possible. One suggestion would be to increase the polling frequency of upower from 2 mins. to something lesser, so that the charge status shows correctly. upower version: UPower client version 0.99.17 UPower daemon version 0.99.17 OS: Description:Ubuntu 22.04.1 LTS Release:22.04 Kernel: Linux 5.15.0-47-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: upower 0.99.17-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 20:41:16 2022 InstallationDate: Installed on 2022-09-12 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1989602 Title: Delay in updating charge status in Ubuntu 22.04 LTS Status in upower package in Ubuntu: New Bug description: I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS. When plugging in the charger, the current charge status in the top bar and Settings shows 'Not Charging' for a few minutes and then shows that the system is charging normally. When unplugging the charger the same happens; the charge status shows 'Not Charging' for a few minutes, and then shows the correct charge status. Normally, the change in power status should be instantaneous. In short, there is a delay in the OS in showing the current charge status. Upon further research, it was found that the 'upower' service is to blame; it polls every two minutes(i.e., it refreshes the charge status every two minutes); causing a delay in charge status. This is further compounded by the fact that restarting upower service, or the system as a whole makes the system to show the correct charge status. However, I did not have this problem on another system, a HP Pavilion x360 14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS. There, the power status behaves normally with no delays whatsoever. Please look into this issue and fix this bug as soon as possible. One suggestion would be to increase the polling frequency of upower from 2 mins. to something lesser, so that the charge status shows correctly. upower version: UPower client version 0.99.17 UPower daemon version 0.99.17 OS: Description: Ubuntu 22.04.1 LTS Release: 22.04 Kernel: Linux 5.15.0-47-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: upower 0.99.17-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 20:41:16 2022 InstallationDate: Installed on 2022-09-12 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1989602/+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 1875015] Re: Displaylink is extremely slow in Xorg sessions
Hi Jeremyszu, That ppa fixed my issue! Is this going to prevent other upgrades? I am not super familiar with how different ppas for same packages would work. I imagine a later version will be marked as an update and override those updates. Daniel, Unfortunately I tried installing the kubuntu wayland packages and the experience was far worse on the dock. So I switched back to x as I'm a pretty big kde fan (I saw some reports that KDE wayland was a bit half baked as of yet across the web, I'm not really in the know). I might switch to gnome to try it out as it has been some years. When I do that I'll definitely try wayland again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1510091] Re: xdg-open fails on wily with chrome
I've resolved issue by fixing the ~/.local/share/applications/google-chrome.desktop file by editing following entry: Exec=/usr/bin/google-chrome --enable-features=WebUIDarkMode --force-dark-mode %u It turned out that I've missed the %u wildcard. Now it works! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1510091 Title: xdg-open fails on wily with chrome Status in xdg-utils package in Ubuntu: Confirmed Bug description: Fresh install of Wily. Attempting to file a bug against Unity using ubuntu-bug. ubuntu-bug prompts me with the expected prompts for a Unity/Gfx bug and then says it will open a new window to complete the bug process. Normally, this would open a window to a launchpad bug in progress so I can update the bug with final details before completing the bug filing process. Instead, it opens a new browser window with NOTHING in the address bar. Since Ubuntu-Bug does NOT give me the URL in the console where it was launched, I have NO way of completing any bugs using ubuntu- bug. I attempted to file a bug twice with ubuntu-bug and failed both times as it does NOT actually open a window that opens the bug's page on launchpad: bladernr@Rogue1:~/Downloads$ ubuntu-bug unity Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. bladernr@Rogue1:~/Downloads$ Created new window in existing browser session. bladernr@Rogue1:~/Downloads$ ubuntu-bug unity Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. bladernr@Rogue1:~/Downloads$ Created new window in existing browser session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1510091/+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 1510091] Re: xdg-open fails on wily with chrome
Have updated to Kubuntu 22.04 Jammy recently and it turns out that xdg- open fails to open in Chrome both from terminal and applications that use. I haven't checked whether it works with other browsers so far. Versions: - xdg-open 1.1.3 - xdg-mime 1.1.3 - KUbuntu 22.04 LTS - KDE Plasma 5.24.4 - Google Chrome 103.0.5060.134 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1510091 Title: xdg-open fails on wily with chrome Status in xdg-utils package in Ubuntu: Confirmed Bug description: Fresh install of Wily. Attempting to file a bug against Unity using ubuntu-bug. ubuntu-bug prompts me with the expected prompts for a Unity/Gfx bug and then says it will open a new window to complete the bug process. Normally, this would open a window to a launchpad bug in progress so I can update the bug with final details before completing the bug filing process. Instead, it opens a new browser window with NOTHING in the address bar. Since Ubuntu-Bug does NOT give me the URL in the console where it was launched, I have NO way of completing any bugs using ubuntu- bug. I attempted to file a bug twice with ubuntu-bug and failed both times as it does NOT actually open a window that opens the bug's page on launchpad: bladernr@Rogue1:~/Downloads$ ubuntu-bug unity Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. bladernr@Rogue1:~/Downloads$ Created new window in existing browser session. bladernr@Rogue1:~/Downloads$ ubuntu-bug unity Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. bladernr@Rogue1:~/Downloads$ Created new window in existing browser session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1510091/+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 1875015] Re: Displaylink is extremely slow in Xorg sessions
Hi, I can confirm this for lenovo z16 laptop as well. This seems not yet fixed in jammy? Glad it seems to be being worked on? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
@paulstejskal I don't think the issue you are describing is caused by the bug described in this bug report. You might need to file a separate bug report or ask for help elsewhere. -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Status in plasma-browser-integration package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. sudo apt install gnome-shell-extension-manager To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1977655] [NEW] Nautilus Open Files and Save File... dialogs keep growing
Public bug reported: In Firefox and Chrome, each time the Open File(s) or Save File... dialog opens, it grows in size. Eventually, it fills the whole screen. See attached screen recording taken from Firefox 101.0 (Mozilla Firefox Snap for Ubuntu canonical-002 - 1.0). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 10:00:40 2022 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' InstallationDate: Installed on 2022-05-01 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-dropbox 2019.02.14-1ubuntu1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Firefox save file dialog growing" https://bugs.launchpad.net/bugs/1977655/+attachment/5594873/+files/Screencast%20from%2006-04-2022%2010%3A03%3A41%20AM.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1977655 Title: Nautilus Open Files and Save File... dialogs keep growing Status in nautilus package in Ubuntu: New Bug description: In Firefox and Chrome, each time the Open File(s) or Save File... dialog opens, it grows in size. Eventually, it fills the whole screen. See attached screen recording taken from Firefox 101.0 (Mozilla Firefox Snap for Ubuntu canonical-002 - 1.0). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 10:00:40 2022 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' InstallationDate: Installed on 2022-05-01 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-dropbox 2019.02.14-1ubuntu1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1977655/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)
*** This bug is a duplicate of bug 1956915 *** https://bugs.launchpad.net/bugs/1956915 Verified internally with Ubuntu 20.04.4 + libegl-mesa0 version "21.2.6-0ubuntu0.1~20.04.2" and confirmed the crash issue is resolved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Impish: New Bug description: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1946621/+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 1878617] Re: Apple pages file type should be added to MIME types
A fix was released upstream in shared-mime-info 2.2 (2022-03-27). Sadly, this didn't make it to Ubuntu 22.04 LTS. -- 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/1878617 Title: Apple pages file type should be added to MIME types Status in shared-mime-info: Unknown Status in mime-support package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Bug description: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+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 1973093] [NEW] xmessage loses text area as buttons are added and -g
Public bug reported: xmessage text gets obscured with option combinations using buttons and geometry specifications. Quick background: xmessage creates a new grey window with a white text box inside it. Without -buttons, the white text box usually spans the full width of the grey window that contains it, leaving no margins. Things start going wrong when you start specifying -buttons or -g (geometry), and text can end up being obscured. Problem #1: If the width of all the buttons you specify makes the grey window wider than the text, the white text box does not increase in width to match. You end up with an undesirable wide grey margin on the right side of the white text box. If you resize the window, making it less wide, the grey margin does not narrow; it moves in and covers and obscures the text, even though there is plenty of room for the text. Suggested Fix #1: The white text box must always be created the same width as the window that contains it, with no useless grey margin to the right. Narrowing the width of the window should not cause text to be obscured by a wide and useless fixed grey margin. Reproduce: xmessage -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" Problem #2: If you add a -g (geometry) option and specify just the width (not the height) for a window with buttons wider than the text box, the obscuring grey margin persists. If you add a "-g NNN" option, where NNN is the width that xmessage would have chosen itself, then you get exactly the same unpleasant behaviour as Problem #1 above. If you increase the NNN to be wider that what xmessage would have used, then both the window and the text box width are created increased by that amount, as if you had resized the window with a mouse. The useless grey margin to the right of the text box stays the same width, just as in Problem #1. If you decrease the NNN to be narrower that what xmessage would have used, then both the window and the text box width are created decreased by that amount, as if you had resized the window with a mouse. Not all buttons will show; this is expected. What is not expected is that the useless grey margin to the right of the text box stays the same width, and so it now overwrites and obscures the text, even though there is plenty of room for the text. If you resize the window back so that all the buttons show, all the text also shows and we're back to Problem #1 above. Suggested Fix #2: Same as above. Reproduce (width 541 is my xmessage chosen width for font "fixed"): xmessage -g 400 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" xmessage -g 541 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" xmessage -g 700 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" Problem #3: If you add a -g option and specify both the width *and* the height for a window with buttons wider than the text, things get much worse. If you add a "-g NNNx55" option, where NNN is the width that xmessage would have chosen itself and "55" is about the same height, you would expect to get exactly the same results as if you didn't specify any geometry at all. That's not what happens. You get a fixed-width text window about 12 characters wide, with a huge grey margin on the right. It doesn't matter what size text you specify; the white text box will be created about 12 characters wide and any text to the right of that will be masked and obscured by the wide grey margin. Changing the width of the window has all the problems of Problems #1 and #2 above. Suggested Fix #3: Same as above. Specifying a geometry that is identical to what xmessage would have chosen itself should create an identical window. Text should not be obscured. Reproduce (width 541 is my xmessage chosen width for font "fixed"): xmessage -g 541x55 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789-123 YOU DON'T SEE THIS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-utils 7.7+5build2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 11 17:12:52 2022 DistUpgraded: 2022-04-04 16:21:26,723 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-29-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-30-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. 2nd Generation Core Processor Family Integrated Graphics Controller [10cf:15f5] InstallationDate: Installed on 2020-09-08 (610 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
I have the same issue connecting to Onion Omega2 IoT devices, since they use cp210x -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+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 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
Updated and now I can't reproduce. Looks like some update made it go away. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
fwiw I've checked Ubuntu 21.10/22.04, Fedora 35/36 and Arch. This only happens in Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by
** Description changed: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to - return to the desktop, journal spits out js stacktrace and animations - become choppy. + return to the desktop, journal spits out js stacktrace. If you don't + trigger the crash then try opening and closing an app and trying again. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. -- 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. If you don't trigger the crash then try opening and closing an app and trying again. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+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 1968390] Re: JS ERROR: TypeError: this.window_container is null
** Description changed: Ubuntu 22.04 Development - - A 3 finger touchpad swipe up/down gesture with 1 application open outputs a lot of JS errors and stacks to the journal. This issue may be the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 but the output is somewhat different when you have more than 1 app open. + A 3 finger touchpad swipe up/down gesture with 1 application open + outputs a lot of JS errors and stacks to the journal. This issue may be + the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome- + shell/+bug/1968383 but the output is somewhat different when you have + more than 1 app open. This also happens with all extensions disabled, does not happen in Fedora 36. To reproduce 1. login and open terminal and watch the journal 2. perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 3. See journal + 4. If nothing happens try opening an app, closing it and try again. Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Button (0x56219f5b8060), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:566 (4ce0bb0ac40 @ 10) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:567 (4ce0bb0ac40 @ 36) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:570 (4ce0bb0ac40 @ 77) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:638 (4ce0bb0ae20 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:353 (4ce0bb0a5b0 @ 62) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:357 (4ce0bb0a5b0 @ 87) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:364 (4ce0bb0a600 @ 8) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:160 (330c4e3cc560 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a9a70 b resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #4 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #5 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Label (0x56219f5a8440), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a98b0 b resource:///org/gnome/shell/ui/environment.js:361 (330c4e3ccc90 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:163 (330c4e3cc560 @ 91) Apr 08 21:18:49 x1c
[Desktop-packages] [Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by
** Description changed: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to - return to the desktop, journal spits out js stacktrace. + return to the desktop, journal spits out js stacktrace and animations + become choppy. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. -- 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace and animations become choppy. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+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 1968390] [NEW] JS ERROR: TypeError: this.window_container is null
Public bug reported: Ubuntu 22.04 Development A 3 finger touchpad swipe up/down gesture with 1 application open outputs a lot of JS errors and stacks to the journal. This issue may be the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 but the output is somewhat different when you have more than 1 app open. This also happens with all extensions disabled, does not happen in Fedora 36. To reproduce 1. login and open terminal and watch the journal 2. perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 3. See journal Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Button (0x56219f5b8060), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:566 (4ce0bb0ac40 @ 10) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:567 (4ce0bb0ac40 @ 36) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:570 (4ce0bb0ac40 @ 77) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:638 (4ce0bb0ae20 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:353 (4ce0bb0a5b0 @ 62) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:357 (4ce0bb0a5b0 @ 87) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:364 (4ce0bb0a600 @ 8) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:160 (330c4e3cc560 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a9a70 b resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #4 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #5 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Label (0x56219f5a8440), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a98b0 b resource:///org/gnome/shell/ui/environment.js:361 (330c4e3ccc90 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:163 (330c4e3cc560 @ 91) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 7ffc4c0a9a70 b resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109) Apr 08 21:18:49 x1c gnome-shell[21675]: #4 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #5 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08
[Desktop-packages] [Bug 1968383] Re: Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the
** Description changed: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up - touch gesture to enter the application grid and then back down to return - to the desktop, journal spits out js stacktrace. + touchpad gesture to enter the application grid and then back down to + return to the desktop, journal spits out js stacktrace. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ** Summary changed: - Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. + Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. -- 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
I am seeing this in 22.04 and an easy way for me to reproduce is on a fresh login, open a terminal and watch the log, open Brave/Chrome, for some reason the first time you open the browser it has a GTK title bar which goes away on closing/reopening the app, now right clicking in the terminal window or opening the hamburger menu and bringing up the menu triggers this message in the logs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1968383] [NEW] Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by t
Public bug reported: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touch gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- 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/1968383 Title: Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touch gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+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 1956915] Re: New bugfix release 21.2.6
Hi Timo, When we can expect that to be part of 'focal-updates' ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1956915 Title: New bugfix release 21.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Impish: Fix Committed Bug description: [Impact] This is the last point-release of the 21.2.x-series, we should put it in impish so latest bugfixes would get there, and in focal for 20.04.4 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04
*** This bug is a duplicate of bug 1956915 *** https://bugs.launchpad.net/bugs/1956915 Hi Timo, >From https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915, I understood that Mesa 21.2.6 is backported to ubuntu0.1~20.04.1 and that is currently under 'focal-proposed', when we can expect that to be part of 'focal-updates' ? I tried upgrading it with "sudo add-apt-repository ppa:savoury1/display && sudo apt upgrade" for now as mentioned in https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915. But the mesa package is not upgraded in my system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1940545 Title: Update Mesa to mesa-21.1.7 on Ubuntu 20.04 Status in mesa package in Ubuntu: Confirmed Bug description: With the recent MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa, we (NVIDIA) have added ability to GBM to dynamically load the backends. So we request to upgrade mesa libs to its latest version (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1870597] Re: libinput says "your system is too slow"
I'm getting spammed by libinput messages about the system being slow. A couple of patches in libinput were merged to master about month ago that rate limits some messages that previously were not, and should at least stop the spamming of messages, if you use a wireless mouse for example the journal gets flooded if you're doing a lot of mouse movements. Please consider backporting these. https://gitlab.freedesktop.org/libinput/libinput/-/commit/a1e9150210abda0d3dd41127330cd7985d29957d https://gitlab.freedesktop.org/libinput/libinput/-/commit/64a49d18b948a5b8ac88da9207689af356a081cf -- 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/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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+git20190815-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/gnome-shell/+bug/1870597/+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 1877038]
I'd also love to see this get added — I'd love to use passwordless auth, but I'm not going to implement it if it's not supported by the main browser I use. Looks like https://github.com/mozilla/authenticator- rs/pull/157 just got approved a few days ago, so hopefully things are moving? Thanks for working on this! -- 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/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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 1741074]
This bug report is getting triaged, I'm glad. I'll add that Ubuntu 22.04 LTS is planning on removing Firefox from the APT repositories altogether and to only provide the snap version of Firefox, which is Ubuntu's default browser, so this bug is going to be experienced by a large fraction of the Ubuntu userbase at some point. -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: Confirmed Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
** Package changed: gnome-terminal (Ubuntu) => mutter (Ubuntu) -- 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/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1951878/+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 1952533] [NEW] [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while
Public bug reported: Sometimes if I run `pulseaudio -k` a few times, sound returns. Sometimes if I run `sudo alsa force-reload`, sound returns. Sometimes if I shutdown and start the laptop, sound returns. This first occurred a few months ago when I was running 20.04, and I upgraded to 21.10 in the hope it would fix the issue. It did not - sound continues to be intermittent. I use the Brave browser, not firefox. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sheehan3636 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 27 20:21:47 2021 InstallationDate: Installed on 2021-10-15 (43 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Nov 27 19:00:54 xps systemd[1436]: pulseaudio.service: Deactivated successfully. Nov 27 19:01:05 xps systemd[1436]: pulseaudio.socket: Deactivated successfully. Symptom_Type: Sound works for a while, then breaks Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd07/09/2021:br1.16:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-27T18:59:43.285943 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- 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/1952533 Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Sometimes if I run `pulseaudio -k` a few times, sound returns. Sometimes if I run `sudo alsa force-reload`, sound returns. Sometimes if I shutdown and start the laptop, sound returns. This first occurred a few months ago when I was running 20.04, and I upgraded to 21.10 in the hope it would fix the issue. It did not - sound continues to be intermittent. I use the Brave browser, not firefox. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sheehan3636 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 27 20:21:47 2021 InstallationDate: Installed on 2021-10-15 (43 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Nov 27 19:00:54 xps systemd[1436]: pulseaudio.service: Deactivated successfully. Nov 27 19:01:05 xps systemd[1436]: pulseaudio.socket: Deactivated successfully. Symptom_Type: Sound works for a while, then breaks Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd07/09/2021:br1.16:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-27T18:59:43.285943 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952533/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
* I found out how to repro. Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 If I leave any gtk apps open e.g. gnome-terminal, evince, Files open, and then open Google Chrome with the flags to enable wayland support --enable-features=UseOzonePlatform --ozone-platform=wayland Then any gtk app that was open outputs the following message to journal after any UI interaction, like switching tabs, opening context menu, etc. gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window This persists until each individual app is restarted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gnome-terminal package in Ubuntu: New Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1951878/+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 1951878] [NEW] "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
Public bug reported: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gnome-terminal package in Ubuntu: New Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1951878/+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 1951786] Re: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated
Can confirm, does not happen with dock disabled. Thanks! -- 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/1951786 Title: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: on Ubuntu 21.10 gnome-shell 40.5-1ubuntu2 Locking desktop and then unlocking it makes gnome-shell spit out a stack trace. v 22 02:00:49 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to access it. This might be caused by the> Nov 22 02:00:49 saturn gnome-shell[33781]: == Stack trace for context 0x5572c18e3130 == Nov 22 02:00:49 saturn gnome-shell[33781]: #0 7ffcbc579470 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:567 (22c5be1b1d80 @ 25) Nov 22 02:00:49 saturn gnome-shell[33781]: #1 5572c8ea2dc0 i resource:///org/gnome/shell/ui/components/autorunManager.js:159 (374b9f3380 @ 31) Nov 22 02:00:49 saturn gnome-shell[33781]: #2 7ffcbc57a1d0 b resource:///org/gnome/shell/ui/components/__init__.js:56 (374b9d7650 @ 66) Nov 22 02:00:49 saturn gnome-shell[33781]: #3 7ffcbc57a960 b resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d7790 @ 15) Nov 22 02:00:49 saturn gnome-shell[33781]: #4 7ffcbc57b030 b self-hosted:225 (374b92ab50 @ 273) Nov 22 02:00:49 saturn gnome-shell[33781]: #5 5572c8ea2d30 i resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d78d0 @ 110) ...skipping... Nov 22 02:04:21 saturn gnome-shell[33781]: #7 7ffcbc578a80 b resource:///org/gnome/shell/ui/sessionMode.js:200 (25da4d8e6d30 @ 284) Nov 22 02:04:21 saturn gnome-shell[33781]: #8 7ffcbc579630 b resource:///org/gnome/shell/ui/sessionMode.js:168 (25da4d8e6e20 @ 116) Nov 22 02:04:21 saturn gnome-shell[33781]: #9 7ffcbc579dc0 b resource:///org/gnome/shell/ui/screenShield.js:574 (25da4d8d4a60 @ 79) Nov 22 02:04:21 saturn gnome-shell[33781]: #10 7ffcbc57a550 b resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4ab0 @ 17) Nov 22 02:04:21 saturn gnome-shell[33781]: #11 7ffcbc57acd0 b resource:///org/gnome/shell/gdm/authPrompt.js:604 (25da4d8f24c0 @ 65) Nov 22 02:04:21 saturn gnome-shell[33781]: #12 7ffcbc57b460 b resource:///org/gnome/shell/ui/unlockDialog.js:871 (374b9053d0 @ 40) Nov 22 02:04:21 saturn gnome-shell[33781]: #13 7ffcbc57bbf0 b resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4b00 @ 50) Nov 22 02:04:21 saturn gnome-shell[33781]: #14 7ffcbc57c380 b resource:///org/gnome/shell/ui/screenShield.js:116 (25da4d8dc6f0 @ 13) Nov 22 02:04:21 saturn gnome-shell[33781]: #15 7ffcbc57ca50 b resource:///org/gnome/gjs/modules/core/_signals.js:114 (22c5be1b1330 @ 439) Nov 22 02:04:21 saturn gnome-shell[33781]: #16 5572c39ba218 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:152 (22c5be1a5b50 @ 39) Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to connect to any signal on it. This migh> Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn dbus-daemon[33727]: [session uid=1000 pid=33727] Activating service name='org.freedesktop.FileManager1' requested by ':1.20' (uid=1000 pid=33781 comm> Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to access it. This might be caused by the> Nov 22 02:04:21 saturn gnome-shell[33781]: g_volume_monitor_get_volumes: assertion 'G_IS_VOLUME_MONITOR (volume_monitor)' failed Nov 22 02:04:21 saturn gnome-shell[33781]: == Stack trace for context 0x5572c18e3130 == Nov 22 02:04:21 saturn gnome-shell[33781]: #0 5572c39ba218 i resource:///org/gnome/shell/ui/components/automountManager.js:66 (374b9f3e20 @ 30) Nov 22 02:04:21 saturn gnome-shell[33781]: #1 7ffcbc57d550 b self-hosted:850 (374b92a650 @ 398) Nov 22 02:04:21 saturn NetworkManager[1054]: [1637564661.8704] agent-manager: agent[70e63220a742bb64,:1.631/org.gnome.Shell.NetworkAgent/1000]: agent registered Nov 22
[Desktop-packages] [Bug 1951786] [NEW] Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated
Public bug reported: on Ubuntu 21.10 gnome-shell 40.5-1ubuntu2 Locking desktop and then unlocking it makes gnome-shell spit out a stack trace. v 22 02:00:49 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to access it. This might be caused by the> Nov 22 02:00:49 saturn gnome-shell[33781]: == Stack trace for context 0x5572c18e3130 == Nov 22 02:00:49 saturn gnome-shell[33781]: #0 7ffcbc579470 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:567 (22c5be1b1d80 @ 25) Nov 22 02:00:49 saturn gnome-shell[33781]: #1 5572c8ea2dc0 i resource:///org/gnome/shell/ui/components/autorunManager.js:159 (374b9f3380 @ 31) Nov 22 02:00:49 saturn gnome-shell[33781]: #2 7ffcbc57a1d0 b resource:///org/gnome/shell/ui/components/__init__.js:56 (374b9d7650 @ 66) Nov 22 02:00:49 saturn gnome-shell[33781]: #3 7ffcbc57a960 b resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d7790 @ 15) Nov 22 02:00:49 saturn gnome-shell[33781]: #4 7ffcbc57b030 b self-hosted:225 (374b92ab50 @ 273) Nov 22 02:00:49 saturn gnome-shell[33781]: #5 5572c8ea2d30 i resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d78d0 @ 110) ...skipping... Nov 22 02:04:21 saturn gnome-shell[33781]: #7 7ffcbc578a80 b resource:///org/gnome/shell/ui/sessionMode.js:200 (25da4d8e6d30 @ 284) Nov 22 02:04:21 saturn gnome-shell[33781]: #8 7ffcbc579630 b resource:///org/gnome/shell/ui/sessionMode.js:168 (25da4d8e6e20 @ 116) Nov 22 02:04:21 saturn gnome-shell[33781]: #9 7ffcbc579dc0 b resource:///org/gnome/shell/ui/screenShield.js:574 (25da4d8d4a60 @ 79) Nov 22 02:04:21 saturn gnome-shell[33781]: #10 7ffcbc57a550 b resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4ab0 @ 17) Nov 22 02:04:21 saturn gnome-shell[33781]: #11 7ffcbc57acd0 b resource:///org/gnome/shell/gdm/authPrompt.js:604 (25da4d8f24c0 @ 65) Nov 22 02:04:21 saturn gnome-shell[33781]: #12 7ffcbc57b460 b resource:///org/gnome/shell/ui/unlockDialog.js:871 (374b9053d0 @ 40) Nov 22 02:04:21 saturn gnome-shell[33781]: #13 7ffcbc57bbf0 b resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4b00 @ 50) Nov 22 02:04:21 saturn gnome-shell[33781]: #14 7ffcbc57c380 b resource:///org/gnome/shell/ui/screenShield.js:116 (25da4d8dc6f0 @ 13) Nov 22 02:04:21 saturn gnome-shell[33781]: #15 7ffcbc57ca50 b resource:///org/gnome/gjs/modules/core/_signals.js:114 (22c5be1b1330 @ 439) Nov 22 02:04:21 saturn gnome-shell[33781]: #16 5572c39ba218 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:152 (22c5be1a5b50 @ 39) Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to connect to any signal on it. This migh> Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn dbus-daemon[33727]: [session uid=1000 pid=33727] Activating service name='org.freedesktop.FileManager1' requested by ':1.20' (uid=1000 pid=33781 comm> Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to access it. This might be caused by the> Nov 22 02:04:21 saturn gnome-shell[33781]: g_volume_monitor_get_volumes: assertion 'G_IS_VOLUME_MONITOR (volume_monitor)' failed Nov 22 02:04:21 saturn gnome-shell[33781]: == Stack trace for context 0x5572c18e3130 == Nov 22 02:04:21 saturn gnome-shell[33781]: #0 5572c39ba218 i resource:///org/gnome/shell/ui/components/automountManager.js:66 (374b9f3e20 @ 30) Nov 22 02:04:21 saturn gnome-shell[33781]: #1 7ffcbc57d550 b self-hosted:850 (374b92a650 @ 398) Nov 22 02:04:21 saturn NetworkManager[1054]: [1637564661.8704] agent-manager: agent[70e63220a742bb64,:1.631/org.gnome.Shell.NetworkAgent/1000]: agent registered Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: 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/1951786 Title: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated Status in gnome-shell
[Desktop-packages] [Bug 1941752]
Created attachment 143424 New crash information added by DrKonqi gwenview (20.12.3) using Qt 5.15.2 - What I was doing when the application crashed: This is a little bizarre. I encountered this while rapidly scrolling through thumbnails in a directory. One particular image reliably crashes QwenView, but it isn't the image itself because QwenView opens the image just fine if I copy it to another directory. If I copy just a few of the images to another directory, QwenView also works just fine. The directory contents are available online to replicate this issue. I downloaded and replicated again just to be sure. The directory contents are available online inside this archive: https://downloads.open- tx.org/2.3/release/sdcard/opentx-t16/sdcard-480x272-2.3V0025.zip. The directory is IMAGES. The image QwenView crashes on is IMAGES/P51.jpg. To replicate, extract the archive, and start clicking through the images. I double clicked on in Dolphin to start. The crash can be reproduced every time. -- Backtrace (Reduced): #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f191f393864 in __GI_abort () at abort.c:79 [...] #12 0x7f191f00a92d in Exiv2::Xmpdatum::write(std::ostream&, Exiv2::ExifData const*) const () from /lib/x86_64-linux-gnu/libexiv2.so.27 #13 0x7f1921515250 in Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #14 0x7f19214dfa70 in Gwenview::Document::setExiv2Image(std::unique_ptr >) () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1776499] Re: Crash in libegl-mesa0 due to out of bound array access
Hi Timo, A similar crash is observed in mesa-egl and it is resolved in Mesa master branch. Please refer the bug: https://bugs.launchpad.net/mesa/+bug/1946621 Can you help backporting the fix to "Focal" series. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1776499 Title: Crash in libegl-mesa0 due to out of bound array access Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: Crash in libegl-mesa0 due to out of bound array access. Crash is fixed on Mesa master branch with change: https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d .This bug is to request to include this change in Mesa upgrades in bionic. Please let me know if this change needs to be back ported to other branch so that libegl-mesa0 upgrade in Bionic could pick this change. lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 18.0.0~rc5-1ubuntu1 Candidate: 18.0.0~rc5-1ubuntu1 Version table: *** 18.0.0~rc5-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #5466 https://gitlab.freedesktop.org/mesa/mesa/-/issues/5466 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/5466 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1946621/+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 1741074]
This bug is also being tracked at https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1741074 Ubuntu 21.10 ships the snap version of Firefox by default, (instead of the APT version), so we can expect more users to experience this bug. -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: New Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
I can confirm, and this has been irritating me for years. I suggest using 'terminator' as a work around. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+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 1947579] [NEW] GNOME Shell integration doesn't work with snap version of Firefox
Public bug reported: In Ubuntu 21.10, the default installation has been switched from the version provided by APT, to the version provided by snap. Users that upgrade from Ubuntu 21.04 to 21.10 will be migrated to the snap version of Firefox. In the snap version of Firefox, it is impossible to install extensions from https://extensions.gnome.org . This error message is displayed: > Although GNOME Shell integration extension is running, native host connector is not detected. Refer documentation for instructions about installing connector. Installing chrome-gnome-shell does not fix this issue. I'm not sure where to file this bug report exactly, but I thought I would file it here. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: chrome-gnome-shell 10.1-5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 18 12:51:26 2021 InstallationDate: Installed on 2021-10-16 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: chrome-gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chrome-gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Affects: snap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: snap (Ubuntu) Importance: Undecided Status: New -- 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/1947579 Title: GNOME Shell integration doesn't work with snap version of Firefox Status in chrome-gnome-shell package in Ubuntu: New Status in firefox package in Ubuntu: New Status in snap package in Ubuntu: New Bug description: In Ubuntu 21.10, the default installation has been switched from the version provided by APT, to the version provided by snap. Users that upgrade from Ubuntu 21.04 to 21.10 will be migrated to the snap version of Firefox. In the snap version of Firefox, it is impossible to install extensions from https://extensions.gnome.org . This error message is displayed: > Although GNOME Shell integration extension is running, native host connector is not detected. Refer documentation for instructions about installing connector. Installing chrome-gnome-shell does not fix this issue. I'm not sure where to file this bug report exactly, but I thought I would file it here. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: chrome-gnome-shell 10.1-5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 18 12:51:26 2021 InstallationDate: Installed on 2021-10-16 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: chrome-gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1947579/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)
PR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13302 is merged on Mesa master branch: https://gitlab.freedesktop.org/maniraj87/mesa/-/commit/796c9ab3fd6b897ae3b3c069568182178c7661d4 Please include this change in Mesa upgrades in "Focal" series. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) Status in mesa package in Ubuntu: New Bug description: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1946621/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)
Root caused the issue with Mesa-EGL, created a PR for the same: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13302 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) Status in mesa package in Ubuntu: New Bug description: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1946621/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)
The crash happens only when calling eglReleaseThread() from destructor of the process. Please find the attached simple app which can be used to repro the issue. With valgrind, I see there is some invalid memory access during the eglReleaseThread() call. Find the logs below: ==5059== Invalid read of size 8 ==5059==at 0x70480EC: eglReleaseThread (eglapi.c:1706) ==5059==by 0x48825B7: eglReleaseThread (in /usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0) ==5059==by 0x1089FB: deinit (in /home/ubuntu/egl_sample/egl_sample) ==5059==by 0x400EBFF: _dl_fini (dl-fini.c:138) ==5059==by 0x48DC84B: __run_exit_handlers (exit.c:108) ==5059==by 0x48DC9DB: exit (exit.c:139) ==5059==by 0x48C7093: (below main) (libc-start.c:342) ==5059== Address 0x4c6f8c8 is 8 bytes inside a block of size 48 free'd ==5059==at 0x484AF20: free (in /usr/lib/aarch64-linux-gnu/valgrind/vgpreload_memcheck-arm64-linux.so) ==5059==by 0x7051FE3: _eglDestroyThreadInfo (eglcurrent.c:134) ==5059==by 0x7051FE3: _eglFiniTSD (eglcurrent.c:76) ==5059==by 0x70539CF: _eglAtExit (eglglobals.c:112) ==5059==by 0x48DC84B: __run_exit_handlers (exit.c:108) ==5059==by 0x48DC9DB: exit (exit.c:139) ==5059==by 0x48C7093: (below main) (libc-start.c:342) So eglReleaseThread() in this case, tries to access the _EGLThreadInfo memory already freed by _eglFiniTSD() ? But it is expected that a new instance of _EGLThreadInfo has to be created when eglReleaseThread() is called from the app in this case. ** Attachment added: "egl_sample.tar" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1946621/+attachment/5531907/+files/egl_sample.tar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) Status in mesa package in Ubuntu: New Bug description: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1946621/+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 1946621] [NEW] Crash in libegl-mesa0 (eglReleaseThread)
Public bug reported: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) Status in mesa package in Ubuntu: New Bug description: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1946621/+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 687689]
Closing this bug as it works for me (Xubuntu 20.04) and we've not seen any reports of this problem for many years. -- 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/687689 Title: Audacity ruins bluetooth Status in Audacity: Invalid Status in audacity package in Ubuntu: Incomplete Status in portaudio package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: Binary package hint: audacity Apparently Audacity is not smart enough to know that it's running under a Gnome environment. Everything in terms of audio devices is managed quite well with pulseaudio, bluetooth-applet, and other Gnome desktop infrastructure. It tries to hard and breaks it. It tries to hack into my bluetooth in a vain attempt to find a headset or something like that and it ruins my bluetooth support in the desktop. I am no longer able to send files or use bluetooth in anyway. First thing it does when you launch it is that it does nothing. It'll just hang. You click on the icon in the menu and you won't get any feedback. Even if you run it from the command line it will give no feedback and display no errors. It just hangs. Then you kill it and restart it a couple times and it launches successfully. Sorta. Besides the globalmenu bug reported in another report it displays this error on my terminal: $ audacity bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started Expression 'stream->capture.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 3653 Here is the errors reported by dmesg: [ 807.086761] EXT4-fs (dm-0): re-mounted. Opts: commit=0 [ 812.790151] usb 6-1: USB disconnect, address 2 [ 812.790881] btusb_intr_complete: hci0 urb 88010e8e1600 failed to resubmit (19) [ 812.790905] btusb_bulk_complete: hci0 urb 88010e8e1c00 failed to resubmit (19) [ 812.791892] btusb_bulk_complete: hci0 urb 8801185a93c0 failed to resubmit (19) [ 812.792064] btusb_send_frame: hci0 urb 8800c0872e40 submission failed [ 813.322598] usb 6-1: new full speed USB device using uhci_hcd and address 3 [ 900.790130] usb 6-1: USB disconnect, address 3 [ 900.790753] btusb_intr_complete: hci0 urb 8800cba0d6c0 failed to resubmit (19) [ 900.790784] btusb_bulk_complete: hci0 urb 8800c0805d80 failed to resubmit (19) [ 900.791836] btusb_bulk_complete: hci0 urb 8800c0805180 failed to resubmit (19) [ 900.792039] btusb_send_frame: hci0 urb 8800c08ddf00 submission failed [ 900.807505] bluetooth-apple[2004]: segfault at a ip 7f65d520c9ee sp 7fffba728880 error 4 in libdbusmenu-glib.so.1.0.17[7f65d5208000+1] [ 901.320309] usb 6-1: new full speed USB device using uhci_hcd and address 4 [ 1308.540165] usb 6-1: USB disconnect, address 4 [ 1308.541015] btusb_intr_complete: hci0 urb 8800c0b18840 failed to resubmit (19) [ 1308.541045] btusb_bulk_complete: hci0 urb 8800c099eb40 failed to resubmit (19) [ 1308.542097] btusb_bulk_complete: hci0 urb 8800c0b180c0 failed to resubmit (19) [ 1308.542300] btusb_send_frame: hci0 urb 88010f313540 submission failed At that point my bluetooth support is broken and thus Audacity will successfully open. After hitting ctrl-f to work around the globalmenu bug (even though I am not using global menu) I can then edit files and such. Save them. Everything works. Of course I can no longer connect to the internet through my phone, send files, upload ringtones, use my bluetooth headset, etc. To work around you can remove the USB bluetooth adapter if you use a external one, plug it back in, and launch bluetooth-applet from the command line and it should be working again. It's not the end of the world, but Audacity should be configured to work properly in the default environment. I suggest eliminating Alsa and bluetooth support and have it not try to fight proper daemons handle it as they do a much better job. At least with PA and Bluetooth. I don't know how well Jack supports bluetooth audio devices, but Audacity really should not be allowed to do this sort of thing. I understand that it seems like a nice feature to be able to use a headset outside of Gnome, but it seems to be fundamentally incompatible with having a bluetooth adapter that is able to work with any other device. For people that may run into this problem in the future through Google or whatever here is two work arounds I suggest: 1. Remove or otherwise disable
[Desktop-packages] [Bug 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04
Will that be updated only on impish (21.10) ? Actually we need the update on focal (20.04). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1940545 Title: Update Mesa to mesa-21.1.7 on Ubuntu 20.04 Status in mesa package in Ubuntu: New Bug description: With the recent MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa, we (NVIDIA) have added ability to GBM to dynamically load the backends. So we request to upgrade mesa libs to its latest version (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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