[Desktop-packages] [Bug 2015543] Re: Update to the upstream 1.12.1 bugfix version
It looks like (for Jammy, at least) there is an in-archive consumer of libwpebackend-fdo-1.0-1 - cog. We need at least a minimal smoke test for SRU verification, and that should suffice. I don't have a Jammy system handy, and cog isn't in the archives post-Jammy - could someone please cook up a minimal test case using cog? ** Also affects: wpebackend-fdo (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: wpebackend-fdo (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpebackend-fdo in Ubuntu. https://bugs.launchpad.net/bugs/2015543 Title: Update to the upstream 1.12.1 bugfix version Status in wpebackend-fdo package in Ubuntu: Fix Released Status in wpebackend-fdo source package in Jammy: Incomplete Bug description: * Impact The update fixes memory handling issues which could potential have security implication. It was requested by the MIR team on https://bugs.launchpad.net/ubuntu/+source/wpebackend- fdo/+bug/1973033/comments/11 as we need to promote the package for incoming webkitgtk security updates Fedora issues an update on similar concern https://bodhi.fedoraproject.org/updates/FEDORA-2022-f98ab9f311 * Testcase Unfortunately it's not easy to test wpebackend-fdo since the project has no tests nor demo utility. The backend is used mostly by webkitgtk but the current archive version is built without that option. It is a requirement for newer webkitgtk series though and such for incoming security update (since newer webkitgtk series are rolled out as security updates) * Regression potential The changes are small fixes for memory management issues but if those were wrong then it could lead to rendering issues or crashes in webkitgtk clients once webkitgtk is build with libwpe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpebackend-fdo/+bug/2015543/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
** Description changed: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): - MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 + MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: - MUTTER_DEBUG_FORCE_KMS_MODE=simple + MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. + + [ Upstream bugs ] + + https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 + https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 + https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) -- 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/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2016411] Re: Man page says that mutter is a GTK2 project.
** Summary changed: - Man page says that project is a GTK2 project. + Man page says that mutter is a GTK2 project. -- 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/2016411 Title: Man page says that mutter is a GTK2 project. Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: I don't know for a fact that Ubuntu isn't running mutter using GTK2, but I suspect that it's probably a documentation bug, since Ubuntu tries to use later versions of GTK in their projects. Also, GTK2 apparently hasn't been the default version of GTK used in mutter since 2010, going by this commit in their repository: https://gitlab.gnome.org/GNOME/mutter/-/commit/069092eb9dae48a0aaa208728ad58d997d444221 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016411/+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 2016933] Re: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU
** Changed in: nvidia-graphics-drivers-530 (Ubuntu) Status: Incomplete => New ** Also affects: xwayland (Ubuntu) Importance: Undecided Status: New -- 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/2016933 Title: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU Status in nvidia-graphics-drivers-530 package in Ubuntu: New Status in xwayland package in Ubuntu: New Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. Every reboot or shutdown, the nvidia daemon doesn't terminate properly: Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: State 'stop-sigterm' timed out. Killing. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Killing process 1832 (nvidia-persiste) with signal SIGKILL. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Main process exited, code=killed, status=9/KILL Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'. Apr 19 01:00:31 ZB systemd[1]: Stopped NVIDIA Persistence Daemon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2016933/+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 1968610] Re: Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia
As a workaround/fix try logging into Xorg and then opening this in Chromium: chrome://flags/#ozone-platform-hint Change it to 'Wayland'. Now log out and log into Wayland again. Does Chromium work now? -- 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/1968610 Title: Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia Status in chromium-browser package in Ubuntu: Confirmed Bug description: When launching Chromium as a snap on Ubuntu 22.04, it will not open properly and will open the browser with only the titlebar and a transparent window. I am using an Nvidia Graphics card with the 510.60.02 Nvidia proprietary drivers. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Chromium Version: 100.0.4896.75 2022-04-07 When running "snap run chromium" in the terminal, the following output happens. Attached screenshot of result. nyaa@nyaa-desktop:~$ snap run chromium Gtk-Message: 13:42:20.777: Failed to load module "canberra-gtk-module" Gtk-Message: 13:42:20.778: Failed to load module "canberra-gtk-module" MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open nvidia-drm: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/nvidia-drm_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load driver: nvidia-drm MESA-LOADER: failed to open kms_swrast: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load swrast driver [9358:9478:0411/134223.111306:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration. Edit: I have recently tested this more, and I've isolated it to Wayland and the snap version of Chromium. On X, the chromium snap runs correctly. When I run Chromium as a binary from the Chromium website, the issue doesn't occur on Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968610/+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 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)
In my case it's not only on Chrome, resizing and moving any application can reproduce this issue in Ubuntu 23.04 GFX Card: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] GFX driver: nvidia-driver-525 gnome-shell: 44.0-2ubuntu3 Kernel: 6.2.0-19-generic -- 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/2007742 Title: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11) Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: These messages repeat: [ 105.711276] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bba91da500] is on because it needs an allocation. [ 105.711772] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bbac95c330] is on because it needs an allocation. [ 105.711903] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bbae726860] is on because it needs an allocation. --- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 Uname: Linux 6.1.11-060111-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 21:54:39 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-22 (179 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2023-02-08 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2007742/+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 2016870] Re: Wayland - Brave browser doesn't launch & blinking windows
Thanks for the bug report. Please try opening a Terminal window, launch brave from there and tell us what messages are printed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: nvidia nvidia-wayland wayland wayland-session -- 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/2016870 Title: [nvidia] Wayland - Brave browser doesn't launch & blinking windows Status in Ubuntu: Incomplete Bug description: Some bugs make Ubuntu 22.04.2 LTS impracticable under Wayland : - blinking windows - Brave Browser seems to launch (launched in system monitor processes) but app window never opens. As english is not my native language, a video will better describe the blinking windows bug : https://mega.nz/file/6LBUkQZJ#oKVqnbMsgJALDwgIn4hJhqsvpBqvEHWrBgJPnO_pMTY (This bug report has been generated with Apport App, but not under Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 14:02:58 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 6.1.0-1008-oem, x86_64: installed GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GA104M [GeForce RTX 3070 Mobile / Max-Q] [1558:50f4] InstallationDate: Installed on 2023-01-27 (80 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Notebook NH5xVR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1008-oem root=UUID=c6e942e5-1878-4e2a-8d85-81abebd32761 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2021 dmi.bios.release: 7.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5xVR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.3 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.07.06:bd02/18/2021:br7.6:efr7.3:svnNotebook:pnNH5xVR:pvrNotApplicable:rvnNotebook:rnNH5xVR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5xVR dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2016870/+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 2016933] Re: Nvidia proprietary driver can't run apps
> Package: nvidia-driver-530 (not installed) suggests the driver is not installed properly. Please try reinstalling it: sudo apt install --reinstall nvidia-driver-530 nvidia-dkms-530 and reboot. If the problem continues after that then please run: lspci -k > lspci.txt journalctl -b0 > journal.txt dpkg -l > packages.txt and attach the resulting text files here. ** No longer affects: wayland (Ubuntu) ** Tags added: wayland wayland-session ** Summary changed: - Nvidia proprietary driver can't run apps + X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU ** Changed in: nvidia-graphics-drivers-530 (Ubuntu) Status: New => Incomplete ** Tags added: nvidia nvidia-wayland -- 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/2016933 Title: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU Status in nvidia-graphics-drivers-530 package in Ubuntu: Incomplete Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. Every reboot or shutdown, the nvidia daemon doesn't terminate properly: Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: State 'stop-sigterm' timed out. Killing. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Killing process 1832 (nvidia-persiste) with signal SIGKILL. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Main process exited, code=killed, status=9/KILL Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'. Apr 19 01:00:31 ZB systemd[1]: Stopped NVIDIA Persistence Daemon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2016933/+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 2016933] [NEW] Nvidia proprietary driver can't run apps
Public bug reported: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. Every reboot or shutdown, the nvidia daemon doesn't terminate properly: Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: State 'stop-sigterm' timed out. Killing. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Killing process 1832 (nvidia-persiste) with signal SIGKILL. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Main process exited, code=killed, status=9/KILL Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'. Apr 19 01:00:31 ZB systemd[1]: Stopped NVIDIA Persistence Daemon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-530 (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ** Also 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/2016933 Title: Nvidia proprietary driver can't run apps Status in nvidia-graphics-drivers-530 package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. Every reboot or shutdown, the nvidia daemon doesn't terminate properly: Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: State 'stop-sigterm' timed out. Killing. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Killing process 1832 (nvidia-persiste) with signal SIGKILL. Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Main process exited, code=killed, status=9/KILL Apr 19 01:00:31 ZB systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'. Apr 19 01:00:31 ZB systemd[1]: Stopped NVIDIA Persistence Daemon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2016933/+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
I'm not sure, but I think the issue was present in kinetic. Hence not a regression (probably). I agree. Only this issue would not motivate a respin, and mentioning it in the release note sounds reasonable. -- 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: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug 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 1999578] Re: Bursts of high CPU usage after triggering overview
Fixed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2823 ** Changed in: gnome-shell (Ubuntu) Status: Opinion => Fix Committed ** Tags added: fixed-in-mutter-44.1 fixed-upstream ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- 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/1999578 Title: Bursts of high CPU usage after triggering overview Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: As requested in the upstream bug report https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby file the downstream issue: I am experiencing high cpu usage of gnome-shell in situations where I would not expect it, leading to my fans running more often and wasting my battery on my Dell XPS 13 9310 2-in1. The problem can be seen in action here: https://www.youtube.com/watch?v=Y9o7a7BGPE4 See also the upstream report for syscap recordings of such situations. I think there might be a correlation with firefox being opened on another workspace (but no video or any other playback happening). At least everytime I notice that my an comes on for no reason and I fire up top to see gnome shell consuming too much cpu, when I kill all my firefox windows gnome shell cpu usage goes down as well, but that could be pure coincidence. At least I can safely rule out the triple buffering downstream ubuntu mutter patch, since I recompiled mutter without the patch and it does not really change the problem much. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1999578/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_obje
** Changed in: indicator-messages (Ubuntu) Status: Confirmed => Invalid ** Changed in: accountsservice (Ubuntu) Assignee: Sebastien Bacher (seb128) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in indicator-messages package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+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 1989477] Re: Switching to dark mode in settings does not change shell theme.
Confirmed the bug is fixed in 23.04. Also I do still have the smooth theme switch animation. ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Released -- 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/1989477 Title: Switching to dark mode in settings does not change shell theme. Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: Changing the "Style" in the "Appearance" section of "Settings" (gnome- control-center), does not update the shell theme. When I select dark mode from settings, Libadwaita apps respond to the changes, but the shell theme and GTK3 applications do not. This has been observed on both Wayland and X11. Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10 Package Version: 1:43~rc-1ubuntu2 What I Expected: Changing the style in settings will affect all the apps that support changing light/dark mode. The shell theme will also respond to the change. What happened instead: Only libadwaita apps are affected by changing the style in Settings. GTK3 apps and the shell theme do not change. When changing to dark mode via the quick settings menu, all the apps change their color scheme appropriately. However, there is not a smooth transition when switching the style from quick settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989477/+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
Gunnar, thanks for reporting on this bug. A quick question: since the original issue got reported in 2022 before kinetic release, what was the status for this in 22.10? Was this also broken there? It's important for us to know if this is a regression or not. Also, with a visible workaround (re-running firefox), my recommendation would be to release note it, and maybe only include it in case we will need to do a full respin of all desktop RC images for 23.04. -- 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: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug 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 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
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-gnome-shell-44.1 fixed-upstream -- 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. [windowPreview.js:566] Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Fix Committed 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/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
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-gnome-shell-44.1 fixed-upstream -- 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/1968390 Title: JS ERROR: TypeError: this.window_container is null Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Fix Committed Bug description: 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 4. If nothing happens try opening an app, closing it and try again. Apr 08 21:18:49 x1c gnome-shell[21675]: JS ERROR: TypeError: this.window_container is null hideOverlay@resource:///org/gnome/shell/ui/windowPreview.js:373:9 vfunc_leave_event/this._idleHideOverlayId<@resource:///org/gnome/shell/ui/windowPreview.js:571:26 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968390/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_obje
** Changed in: accountsservice (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+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
Marco Trevisan submitted an upstream mutter merge request with a fix of this issue. I have applied it to the Ubuntu package through a PPA, installed the resulting binaries, and accomplished some tests: * I can no longer reproduce the issue with a black window when opening Firefox in wayland, not even after having run "killall Xwayland". * This sequence: killall Xwayland; sleep 3; GDK_BACKEND=x11 gedit results in a normal gedit window as far as I can tell. * I also entered an x11 session, and also there I can open Firefox without issues. So I uploaded mutter to the lunar unapproved queue for consideration by the release team. ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed -- 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: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug 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 2016914] Re: gsd-smartcard: segfault on startup
Sure! I've gone ahead and updated the description with a better description of the problem. I have the crashdump files as well, if those can be uploaded somewhere. ** Description changed: A smartcard reader attached to the computer on startup, containing a non-standard smartcard (in this case an NXP AV3 SAM card) causes gsd- smartcard to segfault and restart 200 times after login. + + + System Info: + This is Ubuntu 22.04.2 LTS at Kernel 5.19.0-38-generic + The Smart Card reader is an Identiv uTrust 4711 F with both SAM and Contactless slots + The system is an HP ZBook Firefly 14 G7 + + Detailed issue: + When the smartcard reader is plugged into the system, and an NXP SAM AV3 card is inserted into the physical smartcard slot, upon login several (5) Ubuntu Error report windows will open asking to report a crash. The reader lights will flicker for about 5 minutes until they finally stop. No other issues are seen with the system during this time. + + Upon looking at /var/log/syslog, the errors listed in the attachment are + visible as it appears gsd-smartcard is in a loop of restarting and + crashing following an error. + + /var/crash contains two files from the crash loop, + _usr_libexec_gsd_smartcard.1000.crash and + _usr_libexec_gsd_smartcard_127.crash + + Eventually the crashes seem to stop and the light stops flickering, but + a logout and log back in will restart the issue again, as will rebooting + the machine. Re-plugging the device while logged in does not seem to + cause it to start the crash loop again. + + To complete the standard questions: + 1. I logged into my computer and saw error messages + 2. I expected the smart card to be ignored if there was a card inserted that was unexpected or incompatible with the gnome settings daemon + 3. I encountered several crash reporter messages upon logging in, which seem to have come from the gsd-smartcard program -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2016914 Title: gsd-smartcard: segfault on startup Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: A smartcard reader attached to the computer on startup, containing a non-standard smartcard (in this case an NXP AV3 SAM card) causes gsd- smartcard to segfault and restart 200 times after login. System Info: This is Ubuntu 22.04.2 LTS at Kernel 5.19.0-38-generic The Smart Card reader is an Identiv uTrust 4711 F with both SAM and Contactless slots The system is an HP ZBook Firefly 14 G7 Detailed issue: When the smartcard reader is plugged into the system, and an NXP SAM AV3 card is inserted into the physical smartcard slot, upon login several (5) Ubuntu Error report windows will open asking to report a crash. The reader lights will flicker for about 5 minutes until they finally stop. No other issues are seen with the system during this time. Upon looking at /var/log/syslog, the errors listed in the attachment are visible as it appears gsd-smartcard is in a loop of restarting and crashing following an error. /var/crash contains two files from the crash loop, _usr_libexec_gsd_smartcard.1000.crash and _usr_libexec_gsd_smartcard_127.crash Eventually the crashes seem to stop and the light stops flickering, but a logout and log back in will restart the issue again, as will rebooting the machine. Re-plugging the device while logged in does not seem to cause it to start the crash loop again. To complete the standard questions: 1. I logged into my computer and saw error messages 2. I expected the smart card to be ignored if there was a card inserted that was unexpected or incompatible with the gnome settings daemon 3. I encountered several crash reporter messages upon logging in, which seem to have come from the gsd-smartcard program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2016914/+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 2004552] Re: Sound doesn't work on ASUS X670E-E motherboard.
Just following up, this also affects the 23.04 release when I tested the 04-17-23 daily image for lunar, which is to my understanding going to be the release build for Thursday. This has been resolved for a little over 5 months now upstream, could it please be picked into the Ubuntu package? https://github.com/alsa-project/alsa-ucm- conf/commit/88f232dffd54e1b9222ea76c7885445efebaa74d -- 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/2004552 Title: Sound doesn't work on ASUS X670E-E motherboard. Status in alsa-driver package in Ubuntu: New Bug description: None of the outputs work for my digital optical output on my ASUS ROG STRIX X670E-E GAMING WIFI motherboard since updating the ALC4080/ALC4082 firmware. The issue is resolved in the upstream package of alsa-ucm-conf (https://github.com/alsa-project/alsa-ucm-conf). When I applied the newer configs sound started working again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 2 06:08:15 2023 InstallationDate: Installed on 2023-01-08 (24 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2004552/+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 1959747]
I am having the same issue with ~25% CPU usage when hovering over the messages list and from what I can observer this is somehow related to the HiDPI monitor I am using (27' LG, 4k)? OS: Fedora 37 TB: 102.9.1 Nvidia 3060Ti + X11 (Also tested this with an AMD RX 580 and X11 and Wayland - same issue) Ryzen 5 3400G (4 cores/8 threads) 16G Memory Also recorded a profile: https://share.firefox.dev/3MNOpmA I have another Fedora 37 system at work (i7-8700 w/ onboard graphics) and a 1440p monitor and here I have no issues at all. I hope this can be fixed in the not so far future - TB is really laggy at this point for me :-/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1959747 Title: [upstream] Very high CPU and slow responsiveness in Thunderbird 91-102 Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Very high CPU and slow responsiveness in Thunderbird 91.5.0 and later. Just moving the mouse cursor over a message list results in 365% CPU for me. I had to set this in the config editor to fix it: gfx.webrender.force-disabled = TRUE Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1959747/+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
** Summary changed: - firefox black window + firefox black window on wayland ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- 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: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug 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 2016918] Re: Firefox snap opens a black window on wayland
*** This bug is a duplicate of bug 1987976 *** https://bugs.launchpad.net/bugs/1987976 Let's use the original bug report instead. ** This bug has been marked a duplicate of bug 1987976 firefox black window -- 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/2016918 Title: Firefox snap opens a black window on wayland Status in Mutter: New Status in firefox package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Status in xwayland package in Ubuntu: New Bug description: This may actually be a duplicate of bug #1987976, but I was advised to file a new bug to get attention to this issue for the 23.04 release and consider a possible workaround. https://irclogs.ubuntu.com/2023/04/18/%23ubuntu-desktop.html#t17:42 In short: On a fresh 23.04 install, the first time in each wayland session I try to launch Firefox via the icon in the dock, it just opens a black window. I can close Firefox, and try again, and then it opens as expected. I'd better mention that I have a NVIDIA card, but the issue is present both with the NVIDIA and the Nouveau driver. While it might be some kind of race condition (not everyone is affected), in my case it happens every time. I have a proposed workaround: use the xrefresh command. That could for instance be done with this file: $ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop [Desktop Entry] Name=Launch Xwayland on startup of wayland session Comment=This allows to start the Firefox snap from the dock without a black window Type=Application Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi' TryExec=xrefresh OnlyShowIn=GNOME; NoDisplay=true That idea isn't new. We have shipped a similar file (for a similar reason) with ibus-mozc for a few cycles: https://salsa.debian.org/debian/mozc/-/commit/4e48b655 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016918/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a v2 debdiff for Focal, after Denison correctly pointed out that I was missing a patch. ** Description changed: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 - Focal requires three additional patches to solve the issue, namely: + Focal requires four additional patches to solve the issue, namely: commit 8065985c8d818414a36fe151862afdf42c5eda8a Author: Laurent Bigonville Date: Sat, 4 Apr 2020 19:18:00 +0200 Subject: Move the Install section to the systemd .service file instead - of the udev one + of the udev one Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/8065985c8d818414a36fe151862afdf42c5eda8a commit 74ae33ce01b8d314d6e33746915f75f270b0e21d Author: Sam Thursfield Date: Tue, 3 Nov 2020 12:50:02 +0100 Subject: miners: Opt out of systemd / XDG autostart integration Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/74ae33ce01b8d314d6e33746915f75f270b0e21d commit 3a75f93865e8eb002a377a341a72b1a4b22a8040 Author: Sam Thursfield Date: Tue, 27 Oct 2020 22:05:07 +0100 Subject: miners: Tie systemd startup to gnome-session.service Link:
[Desktop-packages] [Bug 2016914] Re: gsd-smartcard: segfault on startup
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2016914 Title: gsd-smartcard: segfault on startup Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: A smartcard reader attached to the computer on startup, containing a non-standard smartcard (in this case an NXP AV3 SAM card) causes gsd- smartcard to segfault and restart 200 times after login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2016914/+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 1951586] Re: Need option to specify wifi regulatory domain
>Circled back with the latest server image using rpi-imager to set the wifi credentials, wifi country does not get populated Imager does not fill in the 'regulatory-domain' field in network-config because the last time we tried that the existing Ubuntu editions in the Imager repository did not support the field yet, and reacted badly to it. As in error'ing out instead of just ignoring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 2016918] Re: Firefox snap opens a black window on wayland
I applied a mutter patch written by Marco Trevisan and uploaded to a PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/mutter With the binaries from that PPA build I can no longer reproduce the black window issue described in this bug. Not even after having run: killall Xwayland So I pushed the patch to the repo. https://salsa.debian.org/gnome-team/mutter/-/commit/a400e60d ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- 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/2016918 Title: Firefox snap opens a black window on wayland Status in Mutter: New Status in firefox package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Status in xwayland package in Ubuntu: New Bug description: This may actually be a duplicate of bug #1987976, but I was advised to file a new bug to get attention to this issue for the 23.04 release and consider a possible workaround. https://irclogs.ubuntu.com/2023/04/18/%23ubuntu-desktop.html#t17:42 In short: On a fresh 23.04 install, the first time in each wayland session I try to launch Firefox via the icon in the dock, it just opens a black window. I can close Firefox, and try again, and then it opens as expected. I'd better mention that I have a NVIDIA card, but the issue is present both with the NVIDIA and the Nouveau driver. While it might be some kind of race condition (not everyone is affected), in my case it happens every time. I have a proposed workaround: use the xrefresh command. That could for instance be done with this file: $ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop [Desktop Entry] Name=Launch Xwayland on startup of wayland session Comment=This allows to start the Firefox snap from the dock without a black window Type=Application Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi' TryExec=xrefresh OnlyShowIn=GNOME; NoDisplay=true That idea isn't new. We have shipped a similar file (for a similar reason) with ibus-mozc for a few cycles: https://salsa.debian.org/debian/mozc/-/commit/4e48b655 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016918/+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 2016918] Re: Firefox snap opens a black window on wayland
** Changed in: mutter Status: Unknown => 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/2016918 Title: Firefox snap opens a black window on wayland Status in Mutter: New Status in firefox package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xwayland package in Ubuntu: New Bug description: This may actually be a duplicate of bug #1987976, but I was advised to file a new bug to get attention to this issue for the 23.04 release and consider a possible workaround. https://irclogs.ubuntu.com/2023/04/18/%23ubuntu-desktop.html#t17:42 In short: On a fresh 23.04 install, the first time in each wayland session I try to launch Firefox via the icon in the dock, it just opens a black window. I can close Firefox, and try again, and then it opens as expected. I'd better mention that I have a NVIDIA card, but the issue is present both with the NVIDIA and the Nouveau driver. While it might be some kind of race condition (not everyone is affected), in my case it happens every time. I have a proposed workaround: use the xrefresh command. That could for instance be done with this file: $ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop [Desktop Entry] Name=Launch Xwayland on startup of wayland session Comment=This allows to start the Firefox snap from the dock without a black window Type=Application Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi' TryExec=xrefresh OnlyShowIn=GNOME; NoDisplay=true That idea isn't new. We have shipped a similar file (for a similar reason) with ibus-mozc for a few cycles: https://salsa.debian.org/debian/mozc/-/commit/4e48b655 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016918/+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 2016925] [NEW] Firefox window is visually corrupted after upgrading to Ubuntu 23.04
Public bug reported: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 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: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/2016925/+attachment/5665069/+files/Captura%20desde%202023-04-18%2018-04-09.png -- 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/2016925 Title: Firefox window is visually corrupted after upgrading to Ubuntu 23.04 Status in firefox package in Ubuntu: New Bug description: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 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: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+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 2016428] Re: nautilus crashes when entering a query into the search box
Update: It seems to be fixed by a tracker3 reset --filesystem. I'll see how it goes... -- 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/2016428 Title: nautilus crashes when entering a query into the search box Status in nautilus package in Ubuntu: New Bug description: As soon as I start typing in its search box, nautilus freezes for a second and then goes on to crash. When that happens, the terminal reports a "Bus Error". This happens systematically when the directory contains many files. It also appears to be restricted to X11. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Apr 16 21:39:52 2023 InstallationDate: Installed on 2022-10-29 (169 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (4 days ago) usr_lib_nautilus: eiciel0.10.0-1 file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016428/+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 2016921] Re: Translations are missing in Lunar
** Changed in: tepl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tepl in Ubuntu. https://bugs.launchpad.net/bugs/2016921 Title: Translations are missing in Lunar Status in tepl package in Ubuntu: Invalid Bug description: * Impact The tepl translations are missing from the Lunar langpacks because the new template wasn't properly set up on launchpad https://translations.launchpad.net/ubuntu/lunar/+source/tepl * Test case Using a !english locale with translations available in tepl upstream (french for example), edit a file in gedit, change it from outside gedit. The editor view displays a banner telling you that the file changed and asking you if you want to reload. The banner and actions should be translated * What could go wrong The change is basically telling pkgbinarymangler to let the translations be included in the deb, if the package builds it shouldn't have an impact other than including the translations. If a translation was buggy it could potentially create issues on the software or confusion for the user but that isn't likely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tepl/+bug/2016921/+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 2016923] [NEW] Translations are missing in Lunar
Public bug reported: * Impact The tepl translations are missing from the Lunar langpacks because the new template wasn't properly set up on launchpad https://translations.launchpad.net/ubuntu/lunar/+source/tepl * Test case Using a !english locale with translations available in tepl upstream (french for example), edit a file in gedit, change it from outside gedit. The editor view displays a banner telling you that the file changed and asking you if you want to reload. The banner and actions should be translated * What could go wrong The change is basically telling pkgbinarymangler to let the translations be included in the deb, if the package builds it shouldn't have an impact other than including the translations. If a translation was buggy it could potentially create issues on the software or confusion for the user but that isn't likely. ** Affects: tepl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tepl in Ubuntu. https://bugs.launchpad.net/bugs/2016923 Title: Translations are missing in Lunar Status in tepl package in Ubuntu: New Bug description: * Impact The tepl translations are missing from the Lunar langpacks because the new template wasn't properly set up on launchpad https://translations.launchpad.net/ubuntu/lunar/+source/tepl * Test case Using a !english locale with translations available in tepl upstream (french for example), edit a file in gedit, change it from outside gedit. The editor view displays a banner telling you that the file changed and asking you if you want to reload. The banner and actions should be translated * What could go wrong The change is basically telling pkgbinarymangler to let the translations be included in the deb, if the package builds it shouldn't have an impact other than including the translations. If a translation was buggy it could potentially create issues on the software or confusion for the user but that isn't likely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tepl/+bug/2016923/+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 2016918] Re: Firefox snap opens a black window on wayland
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2472 https://gitlab.gnome.org/GNOME/mutter/-/issues/2472 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2472 Importance: Unknown Status: Unknown ** Also affects: xwayland (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/2016918 Title: Firefox snap opens a black window on wayland Status in Mutter: Unknown Status in firefox package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xwayland package in Ubuntu: New Bug description: This may actually be a duplicate of bug #1987976, but I was advised to file a new bug to get attention to this issue for the 23.04 release and consider a possible workaround. https://irclogs.ubuntu.com/2023/04/18/%23ubuntu-desktop.html#t17:42 In short: On a fresh 23.04 install, the first time in each wayland session I try to launch Firefox via the icon in the dock, it just opens a black window. I can close Firefox, and try again, and then it opens as expected. I'd better mention that I have a NVIDIA card, but the issue is present both with the NVIDIA and the Nouveau driver. While it might be some kind of race condition (not everyone is affected), in my case it happens every time. I have a proposed workaround: use the xrefresh command. That could for instance be done with this file: $ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop [Desktop Entry] Name=Launch Xwayland on startup of wayland session Comment=This allows to start the Firefox snap from the dock without a black window Type=Application Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi' TryExec=xrefresh OnlyShowIn=GNOME; NoDisplay=true That idea isn't new. We have shipped a similar file (for a similar reason) with ibus-mozc for a few cycles: https://salsa.debian.org/debian/mozc/-/commit/4e48b655 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016918/+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 2016921] [NEW] Translations are missing in Lunar
Public bug reported: * Impact The tepl translations are missing from the Lunar langpacks because the new template wasn't properly set up on launchpad https://translations.launchpad.net/ubuntu/lunar/+source/tepl * Test case Using a !english locale with translations available in tepl upstream (french for example), edit a file in gedit, change it from outside gedit. The editor view displays a banner telling you that the file changed and asking you if you want to reload. The banner and actions should be translated * What could go wrong The change is basically telling pkgbinarymangler to let the translations be included in the deb, if the package builds it shouldn't have an impact other than including the translations. If a translation was buggy it could potentially create issues on the software or confusion for the user but that isn't likely. ** Affects: tepl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tepl in Ubuntu. https://bugs.launchpad.net/bugs/2016921 Title: Translations are missing in Lunar Status in tepl package in Ubuntu: New Bug description: * Impact The tepl translations are missing from the Lunar langpacks because the new template wasn't properly set up on launchpad https://translations.launchpad.net/ubuntu/lunar/+source/tepl * Test case Using a !english locale with translations available in tepl upstream (french for example), edit a file in gedit, change it from outside gedit. The editor view displays a banner telling you that the file changed and asking you if you want to reload. The banner and actions should be translated * What could go wrong The change is basically telling pkgbinarymangler to let the translations be included in the deb, if the package builds it shouldn't have an impact other than including the translations. If a translation was buggy it could potentially create issues on the software or confusion for the user but that isn't likely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tepl/+bug/2016921/+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 1995092] Re: Wrong ubuntu logo in About section in darkmode
Thanks for the report, it was a packaging bug, a fix is commited now in https://salsa.debian.org/gnome-team/gnome-control- center/-/commit/0357698d ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Committed -- 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/1995092 Title: Wrong ubuntu logo in About section in darkmode Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: Bug only on Ubuntu 22.10 and Ubuntu 23.04 The ubuntu logo used when darkmode is selected on the "About" page of Settings is not the right one. There is two ubuntu logo stored in /usr/share/pixmaps/: -ubuntu-logo-text.png -ubuntu-logo-text-dark.png It seams that for some reasons the "ubuntu-logo-text-dark.png" is not used at it should be in darkmode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1995092/+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 2016918] [NEW] Firefox snap opens a black window on wayland
Public bug reported: This may actually be a duplicate of bug #1987976, but I was advised to file a new bug to get attention to this issue for the 23.04 release and consider a possible workaround. https://irclogs.ubuntu.com/2023/04/18/%23ubuntu-desktop.html#t17:42 In short: On a fresh 23.04 install, the first time in each wayland session I try to launch Firefox via the icon in the dock, it just opens a black window. I can close Firefox, and try again, and then it opens as expected. I'd better mention that I have a NVIDIA card, but the issue is present both with the NVIDIA and the Nouveau driver. While it might be some kind of race condition (not everyone is affected), in my case it happens every time. I have a proposed workaround: use the xrefresh command. That could for instance be done with this file: $ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop [Desktop Entry] Name=Launch Xwayland on startup of wayland session Comment=This allows to start the Firefox snap from the dock without a black window Type=Application Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi' TryExec=xrefresh OnlyShowIn=GNOME; NoDisplay=true That idea isn't new. We have shipped a similar file (for a similar reason) with ibus-mozc for a few cycles: https://salsa.debian.org/debian/mozc/-/commit/4e48b655 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: High Status: New ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/2016918 Title: Firefox snap opens a black window on wayland Status in firefox package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: This may actually be a duplicate of bug #1987976, but I was advised to file a new bug to get attention to this issue for the 23.04 release and consider a possible workaround. https://irclogs.ubuntu.com/2023/04/18/%23ubuntu-desktop.html#t17:42 In short: On a fresh 23.04 install, the first time in each wayland session I try to launch Firefox via the icon in the dock, it just opens a black window. I can close Firefox, and try again, and then it opens as expected. I'd better mention that I have a NVIDIA card, but the issue is present both with the NVIDIA and the Nouveau driver. While it might be some kind of race condition (not everyone is affected), in my case it happens every time. I have a proposed workaround: use the xrefresh command. That could for instance be done with this file: $ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop [Desktop Entry] Name=Launch Xwayland on startup of wayland session Comment=This allows to start the Firefox snap from the dock without a black window Type=Application Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi' TryExec=xrefresh OnlyShowIn=GNOME; NoDisplay=true That idea isn't new. We have shipped a similar file (for a similar reason) with ibus-mozc for a few cycles: https://salsa.debian.org/debian/mozc/-/commit/4e48b655 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016918/+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 2016914] Re: gsd-smartcard: segfault on startup
Have attempted to use apport to attach the crash dump but have so far been unsuccessful. It doesn't seem to upload anything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2016914 Title: gsd-smartcard: segfault on startup Status in gnome-settings-daemon package in Ubuntu: New Bug description: A smartcard reader attached to the computer on startup, containing a non-standard smartcard (in this case an NXP AV3 SAM card) causes gsd- smartcard to segfault and restart 200 times after login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2016914/+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
Simple way to reproduce is: killall XWayland # may kill other apps! start firefox Now, it happens in all the installation where something doesn't bring X11 on startup and firefox is the first app launched. -- 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 Status in Mozilla Firefox: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug 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 2016914] [NEW] gsd-smartcard: segfault on startup
Public bug reported: A smartcard reader attached to the computer on startup, containing a non-standard smartcard (in this case an NXP AV3 SAM card) causes gsd- smartcard to segfault and restart 200 times after login. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Syslog snipped from crash loop" https://bugs.launchpad.net/bugs/2016914/+attachment/5665043/+files/gsd-smartcard_crash_syslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2016914 Title: gsd-smartcard: segfault on startup Status in gnome-settings-daemon package in Ubuntu: New Bug description: A smartcard reader attached to the computer on startup, containing a non-standard smartcard (in this case an NXP AV3 SAM card) causes gsd- smartcard to segfault and restart 200 times after login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2016914/+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 2013128] Re: [feature request] Upgrade libglx-mesa0
Sorry about that, I thought linking the bugfix to the question would show the question post more prominently. I'll keep that in mind for next time. Is there a way to see when this fix will make its way to the 22.04 repositories? I'm just curious how to follow along with the progress of the bugfix being applied. Is this something that's done on a schedule, or is it just when the package maintainer has time? I don't mean to rush, I'm just curious! Thanks. -- 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/2013128 Title: [feature request] Upgrade libglx-mesa0 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Bug description: I have a bug that occurs in Ubuntu 22.04's most up to date libmesa related packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in =22.0.1-1ubuntu2. It has since been solved in mesa's repo and pulled into debian's repo. I do not know the proper way to request an updated version be made for Ubuntu. I've manually installed many different versions of libmesa to test on my own that it was working in an older version, is broken in this update, and was fixed again in 22.3.4 and 22.3.5. The one-line fix is implemented here in libmesa's repo: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782/pipelines -- Feature Request: Upgrade mesa libraries to apply upstream bugfix to a bug introduced in 22.2.5-0ubuntu0.1~22.04.1. I was directed to report this bug via my question at answers.launchpad.net/ubuntu: https://answers.launchpad.net/ubuntu/+question/705988 Please let me know if you need further information. Thanks! > lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 > apt-cache policy libglx-mesa0 libglx-mesa0: Installed: 22.2.5-0ubuntu0.1~22.04.1 Candidate: 22.2.5-0ubuntu0.1~22.04.1 Version table: *** 22.2.5-0ubuntu0.1~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 22.0.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: i3 Date: Tue Mar 28 15:30:59 2023 InstallationDate: Installed on 2022-04-28 (334 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 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2013128/+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 1908931] Re: Kubuntu 20.04 System Settings Online Accounts - unable to add Google account
The same happens on Kubuntu 22.04.2, but I've found a workaround: after the MFA step the empty window is shown, right-clicking into it and choosing the "Reload" permission page is shown and the process could continue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1908931 Title: Kubuntu 20.04 System Settings Online Accounts - unable to add Google account Status in systemsettings package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: New Bug description: Let's try with fresh install: Kubuntu 20.04.1 with default installer options + all packages updated, upgraded, systemsettings package version 4:5.18.4.1-0ubuntu1: - Go to System Settings -> Online Accounts - Click + Add new Account - Choose Google - Window "Web authentication with google" pops up - Enter the email, click Next - Enter the password, click Next - Enter 2FA code from the authenticator, click Next Expected result: - Google account is added, or some sort of confirmation/error Actual result: - Window title with title "Web authentication with google", buttons (menu, min, max, close), and borders are OK - Window content is empty (white canvas) - Nothing happens - Google account is not added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1908931/+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 1951586] Re: Need option to specify wifi regulatory domain
Circled back with the latest server image using rpi-imager to set the wifi credentials, wifi country does not get populated in network-config but adding that line in works fine. https://bugs.launchpad.net/ubuntu/+source/rpi-imager/+bug/2016911 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 1930769] Re: When enabled, Firefox AppArmor profile prevents U2F devices from working
I was also affected by this bug (on Ubuntu 22.04.2 LTS with the latest Firefox 112.0.1 from ppa:mozillateam). I don't want to use the snap version of Firefox. After digging around in AppArmor audit mode and inspecting the logs I noticed that torbrowser (also based on Firefox) has a set of rule in its profile that seem to resolve the issue: /etc/apparmor.d/usr.bin.firefox ``` # u2f (tested with Yubikey 4) /sys/class/ r, /sys/bus/ r, /sys/class/hidraw/ r, /run/udev/data/c24{7,9}:* r, /dev/hidraw* rw, # Yubikey NEO also needs this: /sys/devices/**/hidraw/hidraw*/uevent r, ``` (I am not sure to what extend other tokens need different rules.) -- 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/1930769 Title: When enabled, Firefox AppArmor profile prevents U2F devices from working Status in firefox package in Ubuntu: Confirmed Bug description: Summary: If you enable the apparmor profile that comes in Ubuntu's Firefox package, it prevents USB U2F tokens from being used. To reproduce: 1. Obtain a USB FIDO/U2F token - such as a Yubikey; and a clean install of Ubuntu 20.04 with Firefox installed, but the AppArmor profile for firefox disabled (As is the default). 2. Confirm the correct function of your U2F token - such as at https://demo.yubico.com/webauthn-technical 3. Enable the AppArmor profile with the following command, then restart firefox. sudo aa-enforce /etc/apparmor.d/usr.bin.firefox 4. Repeat your test of your U2F token. You will find Firefox is unable to access your U2F token. Any accounts you need U2F to log into are now inaccessible. 5. Disabling the apparmor profile and restarting firefox will make U2F work again. To work around: Edit /etc/apparmor.d/usr.bin.firefox and replace these lines: # Doesn't seem to be required, but noisy. Maybe allow 'r' for 'b*' if needed. # Possibly move to an abstraction if anything else needs it. deny /run/udev/data/** r, Instead allowing access to udev data, and to hidraw devices: /run/udev/data/** r, /dev/hidraw[0-9] rw, I haven't checked the security implications of this change; some might feel it grants overly broad access. Chromium, which in 20.04 is delivered as a snap, includes udev rules (70-snap.chromium.rules) which I suspect grant access in a device-id-whitelisted way. This is me resubmitting #1930768 this time with all the info attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 88.0.1+build1-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtandy 1757 F pulseaudio /dev/snd/controlC1: mtandy 1757 F pulseaudio BuildID: 20210504152106 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 23:34:55 2021 ForcedLayersAccel: False IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} InstallationDate: Installed on 2021-05-31 (3 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: default via 192.168.0.1 dev enp3s0 proto dhcp metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.2 metric 100 MostRecentCrashID: bp-4122b123-9c74-4baf-b817-c8a771171216 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=88.0.1/20210504152106 (In use) RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2202 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/11/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-K:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.apparmor.d.usr.bin.firefox: 2021-06-03T23:25:44.143815 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firef
[Desktop-packages] [Bug 2016906] [NEW] Inactive zombie ghost icons left behind on desktop when copying files
Public bug reported: When copying files between directory windows, occasionally zombie ghost icons are left on the desktop. These are like holes in the screen with an icon that appears on top of everything in its covered location, is not selectable and is not moveable. Ubuntu 22.10 Release:22.10 gjs: Installed: 1.74.0-1 Candidate: 1.74.0-1 Version table: *** 1.74.0-1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gjs 1.74.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 11:24:52 2023 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2023-02-21 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ** Attachment added: "Example Zombie Ghost Icons On Desktop" https://bugs.launchpad.net/bugs/2016906/+attachment/5665032/+files/Screenshot%20from%202023-04-08%2007-54-06.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2016906 Title: Inactive zombie ghost icons left behind on desktop when copying files Status in gjs package in Ubuntu: New Bug description: When copying files between directory windows, occasionally zombie ghost icons are left on the desktop. These are like holes in the screen with an icon that appears on top of everything in its covered location, is not selectable and is not moveable. Ubuntu 22.10 Release: 22.10 gjs: Installed: 1.74.0-1 Candidate: 1.74.0-1 Version table: *** 1.74.0-1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gjs 1.74.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 11:24:52 2023 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2023-02-21 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2016906/+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 2016870] Re: Wayland - Brave browser doesn't launch & blinking windows
** Description changed: Some bugs make Ubuntu 22.04.2 LTS impracticable under Wayland : - blinking windows - - Brave Browser seems to launch (launched in system monitor processes but app window never opens). + - Brave Browser seems to launch (launched in system monitor processes) but app window never opens. As english is not my native language, a video will better describe the blinking windows bug : https://mega.nz/file/6LBUkQZJ#oKVqnbMsgJALDwgIn4hJhqsvpBqvEHWrBgJPnO_pMTY (This bug report has been generated with Apport App, but not under Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 14:02:58 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 6.1.0-1008-oem, x86_64: installed GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GA104M [GeForce RTX 3070 Mobile / Max-Q] [1558:50f4] InstallationDate: Installed on 2023-01-27 (80 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Notebook NH5xVR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1008-oem root=UUID=c6e942e5-1878-4e2a-8d85-81abebd32761 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2021 dmi.bios.release: 7.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5xVR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.3 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.07.06:bd02/18/2021:br7.6:efr7.3:svnNotebook:pnNH5xVR:pvrNotApplicable:rvnNotebook:rnNH5xVR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5xVR dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 -- 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/2016870 Title: Wayland - Brave browser doesn't launch & blinking windows Status in xorg package in Ubuntu: New Bug description: Some bugs make Ubuntu 22.04.2 LTS impracticable under Wayland : - blinking windows - Brave Browser seems to launch (launched in system monitor processes) but app window never opens. As english is not my native language, a video will better describe the blinking windows bug : https://mega.nz/file/6LBUkQZJ#oKVqnbMsgJALDwgIn4hJhqsvpBqvEHWrBgJPnO_pMTY (This bug report has been generated with Apport App, but not under Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error
[Desktop-packages] [Bug 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
Same, ubuntu 23.04, Epson ET-8500 printer, old certificate was from November, deleted it then I was able to print (and a new certificate appeared). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+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 1951586] Re: Need option to specify wifi regulatory domain
I tried the preinstalled desktop image of Ubuntu 23.04 (Lunar Lobster) Beta last night. It has the same problem, as expected, but it was a bit tricky to fix it directly on the disk image. There are two files called 'cmdline.txt', one in each of the disk's two partitions: 1. system-boot/cmdline.txt <-- Modify this one. 2. writable/boot/firmware/cmdline.txt <-- NOT this one. The file is found as '/boot/firmware/cmdline.txt' when running, so I added the command-line argument to the second file. That's the wrong one, though. The partition labeled 'system-boot' is mounted as '/boot/firmware', hiding the directory with the same name on the second partition with the label 'writeable': $ mount | grep boot /dev/mmcblk0p1 on /boot/firmware type vfat (rw,relatime,fmask=0022,dmask=0022, codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro) The correct file to modify on the disk image is the first one, directly in the 'system-boot' partition. By the way, you might wonder why I don't just change the access point's channels, but those high-end 5-GHz channels are the only ones that work well here. The 2.4-GHz channels are saturated by more than 150 access points nearby, and the same with the low-end 5-GHz channels. The high- end channels in Canada from 149 to 161 are far less occupied, fully available (not just for "indoors"), and don't have any Dynamic Frequency Selection (DFS) or Transmit Power Control (TPC) restrictions. John -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 2016870] [NEW] Wayland - Brave browser doesn't launch & blinking windows
Public bug reported: Some bugs make Ubuntu 22.04.2 LTS impracticable under Wayland : - blinking windows - Brave Browser seems to launch (launched in system monitor processes but app window never opens). As english is not my native language, a video will better describe the blinking windows bug : https://mega.nz/file/6LBUkQZJ#oKVqnbMsgJALDwgIn4hJhqsvpBqvEHWrBgJPnO_pMTY (This bug report has been generated with Apport App, but not under Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 14:02:58 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 6.1.0-1008-oem, x86_64: installed GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GA104M [GeForce RTX 3070 Mobile / Max-Q] [1558:50f4] InstallationDate: Installed on 2023-01-27 (80 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Notebook NH5xVR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1008-oem root=UUID=c6e942e5-1878-4e2a-8d85-81abebd32761 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2021 dmi.bios.release: 7.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5xVR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.3 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.07.06:bd02/18/2021:br7.6:efr7.3:svnNotebook:pnNH5xVR:pvrNotApplicable:rvnNotebook:rnNH5xVR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5xVR dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Description changed: Some bugs make Ubuntu 22.04.2 LTS impracticable under Wayland : - blinking windows - Brave Browser seems to launch (launched in system monitor processes but app window never opens). As english is not my native language, a video will better describe the blinking windows bug : https://mega.nz/file/6LBUkQZJ#oKVqnbMsgJALDwgIn4hJhqsvpBqvEHWrBgJPnO_pMTY + + (This bug report has been generated with Apport App, but not under + Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 - GCC version: gcc ve
[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
** Changed in: gnome-shell Status: Unknown => 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/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. [windowPreview.js:566] Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress 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/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 2016855] Re: padlock icon is missing sometimes
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/2016855 Title: padlock icon is missing sometimes Status in nautilus package in Ubuntu: New Bug description: The directory icon modifier which is the padlock is missing from a child directory after a recursive "read-only" chmod on a parent directory. This bug has been around for years. Full description at... https://askubuntu.com/questions/1462795/padlock-on-directory-icons-may-be-missing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 05:38:36 2023 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1080, 749)' b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'never'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2022-08-27 (233 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016855/+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 1989477] Re: Switching to dark mode in settings does not change shell theme.
I'm running 23.04 daily build and I can confirm the issue is gone here. Though the smooth theme switch animation that Gnome has is also gone, but I assume that is because the method of changing theme is changed to fix the aforementioned problem? -- 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/1989477 Title: Switching to dark mode in settings does not change shell theme. Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: Changing the "Style" in the "Appearance" section of "Settings" (gnome- control-center), does not update the shell theme. When I select dark mode from settings, Libadwaita apps respond to the changes, but the shell theme and GTK3 applications do not. This has been observed on both Wayland and X11. Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10 Package Version: 1:43~rc-1ubuntu2 What I Expected: Changing the style in settings will affect all the apps that support changing light/dark mode. The shell theme will also respond to the change. What happened instead: Only libadwaita apps are affected by changing the style in Settings. GTK3 apps and the shell theme do not change. When changing to dark mode via the quick settings menu, all the apps change their color scheme appropriately. However, there is not a smooth transition when switching the style from quick settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989477/+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 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures
Surprisingly still not fixed in Firefox 111 on lunar. We all just failed to notice because forcing it to use native Wayland is a workaround. ** Tags added: jammy lunar -- 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/1697122 Title: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu version: Kubuntu 17.04 Firefox version: 53.0.3+build1-0ubuntu0.17.04.2 In Firefox, two-finger scroll gestures on a touchpad are interpreted as scroll wheel rotations, and the content scrolls three lines at a time. This is inappropriate behavior for touchpad scrolling; it should scroll pixel-by-pixel. Firefox already has the ability to do this, you just need to turn it on by running the program with MOZ_USE_XINPUT2=1 in the environment: for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to /etc/environment or something like that. Turning on this behavior yields a large usability improvement for laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently added to the packaging such that it's always present when Firefox runs. This is what Fedora does, and it results in a much improved experience for the laptop user. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1697122/+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 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
Upstream project will include the fix for 44.1. ** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Jammy: Fix Released Status in gnome-settings-daemon source package in Kinetic: Fix Released Bug description: [ Impact ] * Sometimes on devices with WWAN card, whenever user presses the wireless function key (Fn+F8) or turn on the airplane mode radio button in Settings, the airplane mode will not be enabled, and the airplane mode icon is not shown in the status bar. * There is a unmerged upstream merge request that delivers the fix: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/merge_requests/310 It works perfectly well on several Lenovo laptops with WWAN cards. The root causes is that the value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should listen to "g-properties-changed" instead of "g-signal" now. [ Test Plan ] 1. Find a machine which has WWAN card. 2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not use rfkill to unblock the WWAN, and reboot. 3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio button in Settings. 4. The airplane mode should be enabled, but actually not. [ Where problems could occur ] * When user is using a very low version network-manager (< 1.20) that still broadcasting DBUS "PropertiesChanged" events on "g-signal" instead of the concurrent "g-properties-changed", the airplane mode will sometimes not be able to enable. [1]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853 [2]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f [ Other Info ] 1. About Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Kernel: 6.1.0-1007-oem 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and manager->wwan_enabled is set to the correct value. 4. Actual: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the initial value of manager->wwan_enabled is true, it will never be able to switch to airplane mode. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_obje
Reported upstream with a valgrind log on https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/114 ** Changed in: accountsservice (Ubuntu) Status: Confirmed => In Progress ** Bug watch added: gitlab.freedesktop.org/accountsservice/accountsservice/-/issues #114 https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/114 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+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 2016855] [NEW] padlock icon is missing sometimes
Public bug reported: The directory icon modifier which is the padlock is missing from a child directory after a recursive "read-only" chmod on a parent directory. This bug has been around for years. Full description at... https://askubuntu.com/questions/1462795/padlock-on-directory-icons-may-be-missing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 05:38:36 2023 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1080, 749)' b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'never'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2022-08-27 (233 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/2016855 Title: padlock icon is missing sometimes Status in nautilus package in Ubuntu: New Bug description: The directory icon modifier which is the padlock is missing from a child directory after a recursive "read-only" chmod on a parent directory. This bug has been around for years. Full description at... https://askubuntu.com/questions/1462795/padlock-on-directory-icons-may-be-missing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 05:38:36 2023 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1080, 749)' b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'never'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2022-08-27 (233 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016855/+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 1999578] Re: Bursts of high CPU usage after triggering overview
** Changed in: gnome-shell Status: New => Fix Released -- 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/1999578 Title: Bursts of high CPU usage after triggering overview Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Opinion Bug description: As requested in the upstream bug report https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby file the downstream issue: I am experiencing high cpu usage of gnome-shell in situations where I would not expect it, leading to my fans running more often and wasting my battery on my Dell XPS 13 9310 2-in1. The problem can be seen in action here: https://www.youtube.com/watch?v=Y9o7a7BGPE4 See also the upstream report for syscap recordings of such situations. I think there might be a correlation with firefox being opened on another workspace (but no video or any other playback happening). At least everytime I notice that my an comes on for no reason and I fire up top to see gnome shell consuming too much cpu, when I kill all my firefox windows gnome shell cpu usage goes down as well, but that could be pure coincidence. At least I can safely rule out the triple buffering downstream ubuntu mutter patch, since I recompiled mutter without the patch and it does not really change the problem much. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1999578/+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 2016312] Re: indicator-messages-service crashed with SIGSEGV in free_fetch_user_request() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from
*** This bug is a duplicate of bug 2015962 *** https://bugs.launchpad.net/bugs/2015962 ** Summary changed: - /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service:11:free_fetch_user_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit + indicator-messages-service crashed with SIGSEGV in free_fetch_user_request() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2016312 Title: indicator-messages-service crashed with SIGSEGV in free_fetch_user_request() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() Status in accountsservice package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/0e715044718e39117f0d6382a7dc032e629ee88e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2016312/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Still here in 22.04 LTS; the workaround I use is the last one suggested in https://askubuntu.com/a/1428798/16395 (WARNING; that will allow evince to launch *any* snap in your system. But otherwise, evince is severely limited...) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Confirmed Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_obje
I just rebooted for a second time today and reproduced the crash again with libaccountsservice0 22.08.8-1ubuntu7 Program terminated with signal SIGSEGV, Segmentation fault. #0 g_type_check_instance (type_instance=0x55b49b114970) at ../../../gobject/gtype.c:4272 #1 0x7f94d743a568 in g_signal_handlers_disconnect_matched ( instance=instance@entry=0x55b49b114970, mask=mask@entry=(G_SIGNAL_MATCH_FUNC | G_SIGNAL_MATCH_DATA), signal_id=signal_id@entry=0, detail=detail@entry=0, closure=closure@entry=0x0, func=func@entry=0x7f94d72a9d70 , data=0x55b49b1151b0) at ../../../gobject/gsignal.c:3067 #2 0x7f94d72a39a8 in act_user_manager_finalize (object=0x55b49b1151b0) at ../src/libaccountsservice/act-user-manager.c:2639 #3 0x7f94d7430e4c in g_object_unref (_object=0x55b49b1151b0) at ../../../gobject/gobject.c:3938 #4 0x55b499c9b950 in im_accounts_service_dispose (object=0x55b49b114020) at ./src/im-accounts-service.c:84 #5 0x7f94d7430da0 in g_object_unref (_object=0x55b49b114020) at ../../../gobject/gobject.c:3891 #6 0x55b499c9ac04 in im_application_list_dispose (object=0x55b49b110e10) at ./src/im-application-list.c:566 #7 0x7f94d7430da0 in g_object_unref (_object=0x55b49b110e10) at ../../../gobject/gobject.c:3891 #8 0x55b499c9a41e in main (argc=, argv=0x7fff96920ea8) at ./src/messages-service.c:289 ** Changed in: accountsservice (Ubuntu) Status: Incomplete => Confirmed ** Changed in: indicator-messages (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+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
This fixes the issue for me: $ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop [Desktop Entry] Name=Launch Xwayland on startup of wayland session Comment=This allows to start the Firefox snap from the dock without a black window Type=Application Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi' TryExec=xrefresh OnlyShowIn=GNOME; NoDisplay=true How about letting some package install that, or maybe make use of the xrefresh command in some other way. -- 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 Status in Mozilla Firefox: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug 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