[Desktop-packages] [Bug 2016193] Re: systemd refuses to start a secondary Xorg session [org.gnome.Shell@x11.service: Skipped due to 'exec-condition']
*** This bug is a duplicate of bug 2006059 *** https://bugs.launchpad.net/bugs/2006059 Moved to bug 2006059. ** This bug has been marked a duplicate of bug 2006059 gdm requires a second login to start xorg session instead of wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2016193 Title: systemd refuses to start a secondary Xorg session [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'] Status in gdm3 package in Ubuntu: New Status in gnome-session package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Split out from https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2015386/comments/9 . I'm using the nvidia 525-server drivers. When I create a new user, then attempt to "switch to" that user from another user's GNOME session, the new session immediately aborts and returns me to the original user's session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2016193/+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 2016193] Re: "switch to" a new user immediately aborts, returns to previous user's session
*** This bug is a duplicate of bug 2006059 *** https://bugs.launchpad.net/bugs/2006059 ** Attachment added: "syslog.gz" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2016193/+attachment/5663886/+files/syslog.gz ** Summary changed: - "switch to" a new user immediately aborts, returns to previous user's session + systemd refuses to start a secondary Xorg session [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'] ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2016193 Title: systemd refuses to start a secondary Xorg session [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'] Status in gdm3 package in Ubuntu: New Status in gnome-session package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Split out from https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2015386/comments/9 . I'm using the nvidia 525-server drivers. When I create a new user, then attempt to "switch to" that user from another user's GNOME session, the new session immediately aborts and returns me to the original user's session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2016193/+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 2015386] Re: Multi-NVIDIA-GPU system crashes starting Wayland session
** Summary changed: - gnome-shell crashes after "switching to" a new user from an existing login + Multi-NVIDIA-GPU system crashes starting Wayland session ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2015386 Title: Multi-NVIDIA-GPU system crashes starting Wayland session Status in mutter package in Ubuntu: New Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: 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.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.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.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA 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.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015386/+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 2012991] Re: Insensitive items in system tray menus not visible
This bug was fixed in the package yaru-theme - 23.04.4-0ubuntu1 --- yaru-theme (23.04.4-0ubuntu1) lunar; urgency=medium [ Paul Kepinski ] * GS: fix light theme invisible text (LP: #2012991) -- Marco Trevisan (Treviño) Thu, 13 Apr 2023 22:17:56 +0200 ** Changed in: yaru-theme (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012991 Title: Insensitive items in system tray menus not visible Status in gnome-shell-extension-appindicator package in Ubuntu: Won't Fix Status in yaru-theme package in Ubuntu: Fix Released Bug description: If you use the multipass system tray menu the text on the items that are insensitive aren't visible. It appears they have the same colour as the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012991/+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 2012287] Re: gjs-console crashed with signal 6 in g_assertion_message("assertion failed: (!priv->is_realized)") from g_assertion_message_expr() from gsk_renderer_dispose() from
This bug was fixed in the package gnome-characters - 44.0-2
---
gnome-characters (44.0-2) experimental; urgency=medium
* debian/patches: Do not crash when rendering invisible characters
(LP: #2012287)
* debian/control: Add build-dependencies on xvfb and gjs for testing
-- Marco Trevisan (Treviño) Fri, 14 Apr 2023
05:04:46 +0200
** Changed in: gnome-characters (Ubuntu Lunar)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-characters in Ubuntu.
https://bugs.launchpad.net/bugs/2012287
Title:
gjs-console crashed with signal 6 in g_assertion_message("assertion
failed: (!priv->is_realized)") from g_assertion_message_expr() from
gsk_renderer_dispose() from gsk_renderer_dispose() from
g_object_unref()
Status in GNOME Characters:
New
Status in gjs package in Ubuntu:
Won't Fix
Status in gnome-characters package in Ubuntu:
Fix Released
Status in gnome-characters source package in Lunar:
Fix Released
Bug description:
Test Case
-
1. From Ubuntu 22.10, install Lunar's glib 2.76.1
2. Log out
3. Log back in
4. Open the GNOME Shell Activities Overview and type the word smile
5. Close the Activities Overview
What Happens
In my case, if I repeat 4 and 5 several times, I will eventually get an
apport crash popup dialog reporting that the GNOME Shell search provider for
GNOME Characters has crashed.
Tracking In
---
https://errors.ubuntu.com/problem/031c8ecfc5e8a51d75d6a028554e9c5354792705
Other Info
--
This isn't a gjs bug, but I'm leaving the gjs task open since I think apport
looks for it.
ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: gjs 1.75.90-1
Uname: Linux 6.1.0-16-generic x86_64
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 20 23:04:59 2023
ExecutablePath: /usr/bin/gjs-console
ExecutableTimestamp: 1678210639
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters
--gapplication-service
ProcCwd: /home/solomax
Signal: 6
SourcePackage: gjs
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-characters/+bug/2012287/+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 2016193] Re: "switch to" a new user immediately aborts, returns to previous user's session
This looks exactly like I would expect: 1. Xorg fails to start in the same way as bug 2015386: Apr 13 23:35:23 nvidia-dgx-station-c25989 systemd[3916]: Condition check resulted in GNOME Shell on X11 being skipped. 2. Wayland fails to start because the server driver doesn't support it: Apr 13 23:35:23 nvidia-dgx-station-c25989 gnome-shell[4072]: Failed to setup: No GPUs found So this is useful information. It shows: 1. There is a common issue between bug 2015386 and bug 2016193 where systemd can't start Xorg. It's not even trying so this seems like a systemd/environment issue. 2. The crashes in bug 2016193 are Wayland-specific (using NVIDIA desktop drivers). I suspect the customer isn't affected by that. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags added: nvidia ** Tags added: multigpu ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2016193 Title: "switch to" a new user immediately aborts, returns to previous user's session Status in gdm3 package in Ubuntu: New Status in gnome-session package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Split out from https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2015386/comments/9 . I'm using the nvidia 525-server drivers. When I create a new user, then attempt to "switch to" that user from another user's GNOME session, the new session immediately aborts and returns me to the original user's session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2016193/+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 2016045] Re: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument]
Interesting, thanks! This looks like the first example of Xorg getting stuck on the same Intel kernel issues as we see with Wayland. Could you try adding a kernel parameter 'drm.debug=0xff' and reproduce it again? That should tell us exactly what the "Invalid argument" is. Possibly indirectly related: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040 (see this for a workaround) https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2933#note_1706156 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2016045 Title: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument] Status in xorg-server package in Ubuntu: New Bug description: 1/3 times I tab in / out of a app/game, that is running using the nvidia dedicated gpu, the screen freezes forcing me to restart my laptop. The cursor is still "usable" and reboot using SysRq REISUB is possible. This is not tied only to steam games, other apps/games like minecraft also cause this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.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 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 13 00:58:23 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84c1] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1] InstallationDate: Installed on 2023-02-06 (65 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=bd5e3449-4d4f-4ebd-afef-1e4da7b9ec69 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84C1 dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku7EF01EA#AB7: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs2xxx dmi.product.sku: 7EF01EA#AB7 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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.3-2ubuntu2.9 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.
[Desktop-packages] [Bug 2016045] Re: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument]
** Summary changed: - Screen sometimes freezes when tabbing in-out of apps running using dedicated gpu. + Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument] ** Package changed: ubuntu => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2016045 Title: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument] Status in xorg-server package in Ubuntu: New Bug description: 1/3 times I tab in / out of a app/game, that is running using the nvidia dedicated gpu, the screen freezes forcing me to restart my laptop. The cursor is still "usable" and reboot using SysRq REISUB is possible. This is not tied only to steam games, other apps/games like minecraft also cause this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.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 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 13 00:58:23 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84c1] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1] InstallationDate: Installed on 2023-02-06 (65 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=bd5e3449-4d4f-4ebd-afef-1e4da7b9ec69 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84C1 dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku7EF01EA#AB7: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs2xxx dmi.product.sku: 7EF01EA#AB7 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2016045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 2016217] Re: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer()
** Summary changed: - /usr/bin/gnome-shell:11:clutter_actor_remove_effect:st_scroll_view_dispose:g_object_unref:GjsAutoPointer:GjsAutoPointer + gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer() -- 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/2016217 Title: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/677a794c2788cd0244c8fc6d7d34780a85127bc9 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/gnome-shell/+bug/2016217/+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 2016217] [NEW] gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/677a794c2788cd0244c8fc6d7d34780a85127bc9 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- 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/2016217 Title: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/677a794c2788cd0244c8fc6d7d34780a85127bc9 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/gnome-shell/+bug/2016217/+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 2016218] Re: /usr/bin/gnome-shell:11:g_type_check_instance_is_a:clutter_actor_remove_effect:st_scroll_view_dispose:g_object_unref:GjsAutoPointer
*** This bug is a duplicate of bug 2016217 *** https://bugs.launchpad.net/bugs/2016217 ** This bug has been marked a duplicate of bug 2016217 /usr/bin/gnome-shell:11:clutter_actor_remove_effect:st_scroll_view_dispose:g_object_unref:GjsAutoPointer:GjsAutoPointer -- 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/2016218 Title: /usr/bin/gnome- shell:11:g_type_check_instance_is_a:clutter_actor_remove_effect:st_scroll_view_dispose:g_object_unref:GjsAutoPointer Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/2f53716bb3ca1e3811b8531860cbf8801dd12505 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/gnome-shell/+bug/2016218/+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 2016218] [NEW] /usr/bin/gnome-shell:11:g_type_check_instance_is_a:clutter_actor_remove_effect:st_scroll_view_dispose:g_object_unref:GjsAutoPointer
*** This bug is a duplicate of bug 2016217 *** https://bugs.launchpad.net/bugs/2016217 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/2f53716bb3ca1e3811b8531860cbf8801dd12505 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- 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/2016218 Title: /usr/bin/gnome- shell:11:g_type_check_instance_is_a:clutter_actor_remove_effect:st_scroll_view_dispose:g_object_unref:GjsAutoPointer Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/2f53716bb3ca1e3811b8531860cbf8801dd12505 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/gnome-shell/+bug/2016218/+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 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)
Same for this fix in 41.0: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1935 Still not enough. -- 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/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears. It seems to myself there is an issue between Wayland and spice-vdagent. Regards, Michel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 09:52:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-01-28 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 __GI_abort () at abort.c:79 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+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 2016045] [NEW] Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument]
You have been subscribed to a public bug: 1/3 times I tab in / out of a app/game, that is running using the nvidia dedicated gpu, the screen freezes forcing me to restart my laptop. The cursor is still "usable" and reboot using SysRq REISUB is possible. This is not tied only to steam games, other apps/games like minecraft also cause this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.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 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 13 00:58:23 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84c1] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1] InstallationDate: Installed on 2023-02-06 (65 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=bd5e3449-4d4f-4ebd-afef-1e4da7b9ec69 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84C1 dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku7EF01EA#AB7: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs2xxx dmi.product.sku: 7EF01EA#AB7 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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.3-2ubuntu2.9 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-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument] https://bugs.launchpad.net/bugs/2016045 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)
The fix for this one was in 3.37.3 so that clearly wasn't enough: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2957 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1349 -- 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/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears. It seems to myself there is an issue between Wayland and spice-vdagent. Regards, Michel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 09:52:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-01-28 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 __GI_abort () at abort.c:79 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+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 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)
In later releases this has become bug 2016214. ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2957 Importance: Unknown Status: Unknown ** No longer affects: gnome-shell -- 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/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears. It seems to myself there is an issue between Wayland and spice-vdagent. Regards, Michel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 09:52:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-01-28 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 __GI_abort () at abort.c:79 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+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 2016214] Re: gnome-shell crashed with signal 6: "assertion failed: (guessed_scale >= 0.5)" in clutter_actor_get_real_resource_scale()
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2016214 Title: gnome-shell crashed with signal 6: "assertion failed: (guessed_scale >= 0.5)" in clutter_actor_get_real_resource_scale() Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/add7be4181ddaecd22eff586b55741552553e36d 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/gnome-shell/+bug/2016214/+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 2016214] Re: gnome-shell crashed with signal 6: "assertion failed: (guessed_scale >= 0.5)" in clutter_actor_get_real_resource_scale()
See also bug 1959507 ** Summary changed: - /usr/bin/gnome-shell:6:g_assertion_message:g_assertion_message_expr:clutter_actor_get_real_resource_scale:clutter_actor_get_real_resource_scale:clutter_actor_get_real_resource_scale + gnome-shell crashed with signal 6: "assertion failed: (guessed_scale >= 0.5)" in clutter_actor_get_real_resource_scale() -- 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/2016214 Title: gnome-shell crashed with signal 6: "assertion failed: (guessed_scale >= 0.5)" in clutter_actor_get_real_resource_scale() Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/add7be4181ddaecd22eff586b55741552553e36d 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/gnome-shell/+bug/2016214/+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 2016214] [NEW] gnome-shell crashed with signal 6: "assertion failed: (guessed_scale >= 0.5)" in clutter_actor_get_real_resource_scale()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/add7be4181ddaecd22eff586b55741552553e36d 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jammy lunar -- 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/2016214 Title: gnome-shell crashed with signal 6: "assertion failed: (guessed_scale >= 0.5)" in clutter_actor_get_real_resource_scale() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/add7be4181ddaecd22eff586b55741552553e36d 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/gnome-shell/+bug/2016214/+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 1991709] Re: gnome-shell memory leak
John, please: 1. Remove all those extensions from your system. 2. If you still experience leaks after that then please open a new bug. ** Summary changed: - gnome-shell memory leak + gnome-shell memory leak (when Ubuntu AppIndicators is enabled) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1991709 Title: gnome-shell memory leak (when Ubuntu AppIndicators is enabled) Status in GNOME Shell: New Status in Ubuntu AppIndicators: New Status in GNOME Software: New Status in Open Weather Map: New Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gjs source package in Jammy: Confirmed Status in gnome-shell source package in Jammy: Confirmed Status in gnome-shell-extension-appindicator source package in Jammy: Confirmed Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1991709/+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 2015928] Re: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1
This bug was fixed in the package gst-plugins-base1.0 - 1.22.1-1ubuntu1 --- gst-plugins-base1.0 (1.22.1-1ubuntu1) lunar; urgency=medium * Cherry-pick proposed patch to fix build test failure seen with glib 2.76 (LP: #2015928) -- Jeremy Bicha Tue, 11 Apr 2023 20:07:07 -0400 ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015928 Title: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1 Status in gst-plugins-base: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Bug description: gst-plugins-base1.0 fails to build on Ubuntu 23.04 because of a build test failure. This appears to have been triggered by the removal of the slice allocator in glib 2.76. I have reported the issue upstream to gstreamer now. https://launchpad.net/ubuntu/+source/gst-plugins-base1.0/1.22.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-base/+bug/2015928/+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 2015129] Re: gstreamer 1.22.1 bugfix release
This bug was fixed in the package gst-plugins-base1.0 - 1.22.1-1ubuntu1 --- gst-plugins-base1.0 (1.22.1-1ubuntu1) lunar; urgency=medium * Cherry-pick proposed patch to fix build test failure seen with glib 2.76 (LP: #2015928) -- Jeremy Bicha Tue, 11 Apr 2023 20:07:07 -0400 ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015129 Title: gstreamer 1.22.1 bugfix release Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Committed Status in gstreamer1.0 package in Ubuntu: Fix Released Bug description: Impact -- This is a stable bugfix release See https://gstreamer.freedesktop.org/releases/1.22/#1.22.1 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2015129/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
Attached ** Attachment added: "_usr_bin_gnome-shell.1001.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+attachment/5663851/+files/_usr_bin_gnome-shell.1001.crash -- 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/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: 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.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.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.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA 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.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+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 1965323] Re: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL
Thanks for the bug report. The version of gnome-shell you have is not supported, it is a prerelease from January 2022. Please: 1. Try the official release: https://ubuntu.com/download/desktop 2. If the bug still occurs after upgrading then please also report it upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965323 Title: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL Status in gnome-shell package in Ubuntu: Incomplete Bug description: Using Wayland, ubuntu-gnome, nvidia-510, RTL locale (hebrew). When sliding the cursor along the top (horizontal) edge of the screen to the hotspot at the top right corner of the screen (where the activities menu is found in an rtl environment), gnome-shell does not go into overview mode (and back). When sliding the cursor to the very same hotspot along the right (vertical) edge of the screen, gnome-shell works properly and goes to overview mode (and back). This problem exists only in wayland gnome sessions. It does not occur in x11 gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Mar 17 17:21:49 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-01-31 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=he_IL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965323/+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 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m
Another crash file generated with waking from suspend ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+attachment/5663843/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2014986 Title: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+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 1906792] Re: Chromium tabs freeze with two windows on Wayland (Xwayland)
If you experience the issue on Manjaro then please subscribe to https://gitlab.gnome.org/GNOME/mutter/-/issues/1563 instead... Although there is also this menu bug at the moment which is a little bit similar: https://bugs.chromium.org/p/chromium/issues/detail?id=1427954 -- 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/1906792 Title: Chromium tabs freeze with two windows on Wayland (Xwayland) Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Original description: When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. --- Updates: As for #1916458 this behaviour may happen also on the same workspace and with Google Chrome ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1906792/+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 995406] Re: User not added to group sambashare: "You do not have permission to create a usershare."
This is happening in lunar beta 23.04,. I install nautilus-share. Turned on sharing in Gnome preference (both options) When attempting to share a folder: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error Permission denied You do not have permission to create a usershare. Ask your administrator to grant you permissions to create a share. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/995406 Title: User not added to group sambashare: "You do not have permission to create a usershare." Status in nautilus-share package in Ubuntu: Confirmed Bug description: I tried to share a folder and was prompted to install samba, which I accepted. I did not install pam-smbpass as I don't need it. I was prompted to log out and in again, which I did. Now I get this when creating a share: --- 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error Permission denied You do not have permission to create a usershare. Ask your administrator to grant you permissions to create a share. --- It looks like the user was not added to the group sambashare at all (which script is supposed to do this? Where is the log file?). Manually running # sudo usermod -a -G sambashare jakob fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus-share 0.7.3-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sun May 6 11:37:08 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) SourcePackage: nautilus-share UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/995406/+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 2012287] Re: gjs-console crashed with signal 6 in g_assertion_message("assertion failed: (!priv->is_realized)") from g_assertion_message_expr() from gsk_renderer_dispose() from
** Changed in: gjs (Ubuntu Lunar)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** No longer affects: gjs (Ubuntu Lunar)
** Changed in: gjs (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-characters in Ubuntu.
https://bugs.launchpad.net/bugs/2012287
Title:
gjs-console crashed with signal 6 in g_assertion_message("assertion
failed: (!priv->is_realized)") from g_assertion_message_expr() from
gsk_renderer_dispose() from gsk_renderer_dispose() from
g_object_unref()
Status in GNOME Characters:
New
Status in gjs package in Ubuntu:
Won't Fix
Status in gnome-characters package in Ubuntu:
In Progress
Status in gnome-characters source package in Lunar:
In Progress
Bug description:
Test Case
-
1. From Ubuntu 22.10, install Lunar's glib 2.76.1
2. Log out
3. Log back in
4. Open the GNOME Shell Activities Overview and type the word smile
5. Close the Activities Overview
What Happens
In my case, if I repeat 4 and 5 several times, I will eventually get an
apport crash popup dialog reporting that the GNOME Shell search provider for
GNOME Characters has crashed.
Tracking In
---
https://errors.ubuntu.com/problem/031c8ecfc5e8a51d75d6a028554e9c5354792705
Other Info
--
This isn't a gjs bug, but I'm leaving the gjs task open since I think apport
looks for it.
ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: gjs 1.75.90-1
Uname: Linux 6.1.0-16-generic x86_64
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 20 23:04:59 2023
ExecutablePath: /usr/bin/gjs-console
ExecutableTimestamp: 1678210639
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters
--gapplication-service
ProcCwd: /home/solomax
Signal: 6
SourcePackage: gjs
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-characters/+bug/2012287/+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 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m
Another crash file from gnome-shell running as gdm ** Attachment added: "_usr_bin_gnome-shell.120.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+attachment/5663835/+files/_usr_bin_gnome-shell.120.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2014986 Title: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+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 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m
Another crash file from what appears to be from the gdm instance of gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2014986 Title: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+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 2016182] Re: terminal opened started from nautilus does not get focus
Unable to reproduce on a freshly installed machine. Try removing your
~/.config/nautilus folder, or another associated configuration. You
likely have a corrupted or otherwise misconfigured configuration.
Chances are you really need to seek support and this is not really a
bug.
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
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/2016182
Title:
terminal opened started from nautilus does not get focus
Status in nautilus package in Ubuntu:
Incomplete
Bug description:
Terminals launched from the nautilus context menu ("Open in Terminal") do not
automatically receive focus.If one starts typing, the input goes to nautilus
instead of the terminal and the terminal needs to be selected manually to get
focus.
Steps:
1. right-click in nautilus
2. select "Open in Terminal"
3. A terminal pops up but the prompt is inactive
I gave up on 22.10 because it had the same issue. I thought the issue
would be solved by now but clearly it still exists. Maybe the
behaviour is intended but that feels go against basic UX...
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.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Apr 13 21:34:46 2023
InstallationDate: Installed on 2022-10-29 (166 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: nautilus
UpgradeStatus: Upgraded to lunar on 2023-04-12 (1 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/2016182/+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 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.19.0-1023.24)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.19.0-1023.24) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.19/5.19.0-1023.24~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19 (5.19.0-1023.24~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.15.0-1036.43)
All autopkgtests for the newly accepted linux-restricted-modules-azure (5.15.0-1036.43) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.19.0-1023.24)
All autopkgtests for the newly accepted linux-restricted-modules-azure (5.19.0-1023.24) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1034.38)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.15.0-1034.38) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) nvidia-graphics-drivers-525/525.89.02-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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
This bug was fixed in the package accountsservice - 22.08.8-1ubuntu7 --- accountsservice (22.08.8-1ubuntu7) lunar; urgency=medium * debian/patches/gitlab_manager_requests.patch: - Disconnect from manager signals when freeing a request and resolve indicator-messages crashing on logout, thanks Marco! (lp: #2015962) -- Sebastien Bacher Thu, 13 Apr 2023 23:59:56 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- 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: New Status in accountsservice package in Ubuntu: Fix Released 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 2012974] Re: gnome-shell crashed with SIGSEGV at ...90ffb
I think the limiting factor is bug 2015857 at the moment. -- 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/2012974 Title: gnome-shell crashed with SIGSEGV at ...90ffb Status in gnome-shell package in Ubuntu: Invalid Bug description: Running preview of 23.04, I click Firefox, the screen is black, and it hangs around. Eventually it pops up the bug report dialog, and then, oddly, launches Firefox to let me tell you about it! ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 20:18:21 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-03-27 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230324) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f747b290ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffe3242f220 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012974/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)
**free --giga --human**: ``` totalusedfree shared buff/cache available Mem:7.6G4.0G374M351M3.3G3.0G Swap:23G117M 23G ``` **gnome-extensions list --enabled**: ``` unbl...@sun.wxg@gmail.com unlockdialogbackgro...@sun.wxg@gmail.com prevent-double-empty-win...@silliewous.nl user-th...@gnome-shell-extensions.gcampax.github.com workspace-indica...@gnome-shell-extensions.gcampax.github.com fq@megh caffe...@patapon.info no-overview@fthx arcm...@arcmenu.com noannoya...@daase.net quick-lang-swi...@ankostis.gmail.com primary_input_on_lockscr...@sagidayan.com lockk...@vaina.lt notification-posit...@drugo.dev favourites-in-appg...@harshadgavali.gitlab.org notification-banner-reloa...@marcinjakubowski.github.com date-menu-format...@marcinjakubowski.github.com auto-move-wind...@gnome-shell-extensions.gcampax.github.com recentit...@bananenfisch.net openweather-extens...@jenslody.de remove-alt-tab-de...@daase.net NotificationCounter@coolllsk workspace-switcher-mana...@g-dh.github.com screenshot-window-si...@gnome-shell-extensions.gcampax.github.com native-window-placem...@gnome-shell-extensions.gcampax.github.com notification-time...@chlumskyvaclav.gmail.com ubuntu-d...@ubuntu.com ubuntu-appindicat...@ubuntu.com d...@rastersoft.com ``` **ps auxw | grep gnome**: ``` USER PR NIVIRTRESSHR%CPU %MEM TIME+ COMMAND johnm 5474 0.0 0.0 242108 7204 ?SLl 03:15 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login johnm 5478 0.0 0.0 163440 6112 tty2 Ssl+ 03:15 0:00 /usr/libexec/gdm-wayland-session env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --session=ubuntu johnm 5485 0.0 0.1 224196 15580 tty2 Sl+ 03:15 0:00 /usr/libexec/gnome-session-binary --session=ubuntu johnm 5546 0.0 0.0 92960 5104 ?Ssl 03:15 0:00 /usr/libexec/gnome-session-ctl --monitor johnm 5569 0.0 0.2 521284 17692 ?Ssl 03:15 0:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu johnm 5774 11.2 4.5 5446336 359844 ? Ssl 03:15 3:01 /usr/bin/gnome-shell johnm 5807 0.0 0.2 1059236 20344 ? Sl 03:15 0:00 /usr/libexec/gnome-shell-calendar-server johnm 5948 0.0 0.3 2670180 27068 ? Sl 03:15 0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Notifications johnm 5950 0.0 0.0 162676 7332 ?Sl 03:15 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session johnm 6014 0.5 2.6 868404 210992 ? Sl 03:15 0:08 /usr/bin/gnome-software --gapplication-service johnm 6216 0.0 0.3 2670180 26836 ? Sl 03:15 0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver johnm 6283 0.0 0.4 67 33288 ?Ssl 03:16 0:00 /usr/libexec/xdg-desktop-portal-gnome johnm 6286 0.1 1.0 3020104 78652 ? Sl 03:16 0:02 gjs /usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js -E -P /usr/share/gnome-shell/extensions/d...@rastersoft.com -M 0 -D 1280:0:1366:768:1:27:56:0:0:0 -D 0:0:1280:1024:1:0:56:0:0:1 johnm 7274 0.0 0.2 37388 19824 ?S03:17 0:00 /usr/bin/python3 /usr/bin/gnome-terminal --wait johnm 7277 0.0 0.3 384004 27960 ?Sl 03:17 0:00 /usr/bin/gnome-terminal.real --wait johnm 7287 0.8 0.7 902128 59084 ?Ssl 03:17 0:13 /usr/libexec/gnome-terminal-server johnm 8027 0.0 0.0 3644 1100 ?S03:23 0:00 bwrap --args 38 gnome-extensions-app johnm 8164 0.0 0.0 3768 1472 ?S03:23 0:00 bwrap --args 38 gnome-extensions-app johnm 8165 0.0 0.0 7704 3224 ?S03:23 0:00 /bin/sh /app/bin/gnome-extensions-app johnm 8166 0.4 1.8 3867112 141276 ? Sl 03:23 0:05 /usr/bin/gjs /app/share/gnome-extensions-app/org.gnome.Extensions johnm 8311 0.0 0.6 2912668 53152 ? Sl 03:23 0:01 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Extensions johnm 9499 0.0 0.4 207508 35856 ?Sl 03:25 0:00 /usr/bin/python3 /usr/bin/chrome-gnome-shell /usr/lib/mozilla/native-messaging-hosts/org.gnome.chrome_gnome_shell.json chrome-gnome-sh...@gnome.org ``` **ps auxw | grep gjs**: ``` USER PR NIVIRTRESSHR%CPU %MEM TIME+ COMMAND johnm 5948 0.0 0.3 2670180 27068 ? Sl 03:15 0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Notifications johnm 6216 0.0 0.3 2670180 26836 ? Sl 03:15 0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver johnm 6286 0.1 1.0 3020104 78652 ? Sl 03:16 0:02 gjs /usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js -E -P /usr/share/gnome-shell/extensions/d...@rastersoft.com -M 0 -D 1280:0:1366:768:1:27:56:0:0:0 -D 0:0:1280:1024:1:0:56:0:0:1 johnm 8166 0.4 1.8 3867112 141276 ? Sl 03:23 0:05 /
[Desktop-packages] [Bug 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
Seems there is no stack trace in https://errors.ubuntu.com/oops/7a01bd23-da4e-11ed-ba6b-fa163ef35206 Can you find the original /var/crash/ file ? -- 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/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: 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.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.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.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA 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.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)
** Also affects: gnome-software Importance: Undecided Status: New ** Also affects: openweathermap Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1991709 Title: gnome-shell memory leak (when Ubuntu AppIndicators is enabled) Status in GNOME Shell: New Status in Ubuntu AppIndicators: New Status in GNOME Software: New Status in Open Weather Map: New Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gjs source package in Jammy: Confirmed Status in gnome-shell source package in Jammy: Confirmed Status in gnome-shell-extension-appindicator source package in Jammy: Confirmed Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1991709/+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 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m
I added MUTTER_SYNC=1 to my environment and got the attached crash file ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+attachment/5663801/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2014986 Title: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)
** Also affects: gnome-shell-extension-appindicator Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1991709 Title: gnome-shell memory leak (when Ubuntu AppIndicators is enabled) Status in GNOME Shell: New Status in Ubuntu AppIndicators: New Status in GNOME Software: New Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gjs source package in Jammy: Confirmed Status in gnome-shell source package in Jammy: Confirmed Status in gnome-shell-extension-appindicator source package in Jammy: Confirmed Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1991709/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-appindicator (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1991709 Title: gnome-shell memory leak (when Ubuntu AppIndicators is enabled) Status in GNOME Shell: New Status in Ubuntu AppIndicators: New Status in GNOME Software: New Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gjs source package in Jammy: Confirmed Status in gnome-shell source package in Jammy: Confirmed Status in gnome-shell-extension-appindicator source package in Jammy: Confirmed Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1991709/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1991709 Title: gnome-shell memory leak (when Ubuntu AppIndicators is enabled) Status in GNOME Shell: New Status in Ubuntu AppIndicators: New Status in GNOME Software: New Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gjs source package in Jammy: Confirmed Status in gnome-shell source package in Jammy: Confirmed Status in gnome-shell-extension-appindicator source package in Jammy: Confirmed Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1991709/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gjs (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1991709 Title: gnome-shell memory leak (when Ubuntu AppIndicators is enabled) Status in GNOME Shell: New Status in Ubuntu AppIndicators: New Status in GNOME Software: New Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gjs source package in Jammy: Confirmed Status in gnome-shell source package in Jammy: Confirmed Status in gnome-shell-extension-appindicator source package in Jammy: Confirmed Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1991709/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
I reset all the relevant packages back to the versions used when I originally filed this bug (luckily I stashed an sosreport), and I was able to reproduce. https://errors.ubuntu.com/user/b18128bc669a4a4d1f371a58f4f5d719833ab52c5ab794dbbc9d9e55b45d12516efcc5085f9d93e4d219bc6948f530cdaa31ddf8e34b7e9242e050c269d729c3 Let me know if that is what you needed. This is using the UDA (non-server) drivers, but the user for originally reported the bug to me appears to have been using the -server drivers as you surmised. I tried switching to the 525-server driver and I still experienced an issue with switch user, but the symptoms are different. Instead of entering a new login for a few seconds followed by a gnome- shell crash, this seemed to immediately kick me out of the switched-to session with no gnome-shell crash. Since this is likely a different issue, I reported it as bug 2016193 to keep the threads separate. -- 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/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: 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.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.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.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA 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.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-p
[Desktop-packages] [Bug 2016193] [NEW] "switch to" a new user immediately aborts, returns to previous user's session
Public bug reported: Split out from https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2015386/comments/9 . I'm using the nvidia 525-server drivers. When I create a new user, then attempt to "switch to" that user from another user's GNOME session, the new session immediately aborts and returns me to the original user's session. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sosreport-nvidia-dgx-station-c25989-2023-04-13-lncndqw.tar.xz" https://bugs.launchpad.net/bugs/2016193/+attachment/5663793/+files/sosreport-nvidia-dgx-station-c25989-2023-04-13-lncndqw.tar.xz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2016193 Title: "switch to" a new user immediately aborts, returns to previous user's session Status in gdm3 package in Ubuntu: New Bug description: Split out from https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2015386/comments/9 . I'm using the nvidia 525-server drivers. When I create a new user, then attempt to "switch to" that user from another user's GNOME session, the new session immediately aborts and returns me to the original user's session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2016193/+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 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-input-libinput (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2014986 Title: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+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 2016191] Re: gnome-shell crashed with signal 5 in _XEventsQueued()
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2014986, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2016191/+attachment/5663770/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2016191/+attachment/5663772/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2016191/+attachment/5663775/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2016191/+attachment/5663776/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2016191/+attachment/5663777/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2016191/+attachment/5663779/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2016191/+attachment/5663780/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 2014986 gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2016191 Title: gnome-shell crashed with signal 5 in _XEventsQueued() Status in gnome-shell package in Ubuntu: New Bug description: I'm seeing this crash on each login after a fresh install of 23.04. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 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.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Apr 13 19:06:05 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-04-10 (3 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu3 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2016191/+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 2016191] [NEW] gnome-shell crashed with signal 5 in _XEventsQueued()
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 Public bug reported: I'm seeing this crash on each login after a fresh install of 23.04. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 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.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Apr 13 19:06:05 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-04-10 (3 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu3 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash lunar ** Information type changed from Private to Public Security ** Information type changed from Public Security to Public -- 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/2016191 Title: gnome-shell crashed with signal 5 in _XEventsQueued() Status in gnome-shell package in Ubuntu: New Bug description: I'm seeing this crash on each login after a fresh install of 23.04. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 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.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Apr 13 19:06:05 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-04-10 (3 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu3 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2016191/+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 1906792] Re: Chromium tabs freeze with two windows on Wayland (Xwayland)
So this issue was reported in 2020 and is still an issue in 2023... Using KDE on manjaro linux. -- 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/1906792 Title: Chromium tabs freeze with two windows on Wayland (Xwayland) Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Original description: When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. --- Updates: As for #1916458 this behaviour may happen also on the same workspace and with Google Chrome ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1906792/+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 2015948] Re: GNOME Character shows no emoji
Fixed by gjs (1.76.0-3) experimental; urgency=medium * debian/patches: Drop patch causing GNOME Characters not to show emojis (LP: #2015948) gjs (1.76.0-2) experimental; urgency=medium [ Daniel van Vugt ] * Add context-Clear-all-vectors-of-JS-Heap-on-dispose.patch (LP: #1974293) [ Marco Trevisan (Treviño) ] * debian/patches: Do not leak GVariants and other handled objects (LP: #1991709, #2012978) -- Marco Trevisan (Treviño) Wed, 12 Apr 2023 05:40:15 +0200 ** Changed in: gnome-characters (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2015948 Title: GNOME Character shows no emoji Status in gnome-characters package in Ubuntu: Fix Released Bug description: Emoji list is empty after gjs update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/2015948/+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 ** Changed in: indicator-messages (Ubuntu) Status: Confirmed => Invalid -- 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: New 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 1951586] Re: Need option to specify wifi regulatory domain
netplan added support for configuring the regulatory domain in kinetic and it works pretty nicely (it's one of the things I test before release). However, that's relying on cloud-init to inject the netplan configuration and that's only on the server images -- it's not a solution for the preinstalled desktop images. Having said that ... it might be if cloud-init gets included in the preinstalled desktop images, but that's not happening in lunar as it caused other issues. Still, even if it did that's still a rather command-line / text-configuration-file interface that's nowhere near as "good" as having it integrated into the first time GUI setup (as RaspiOS does). -- 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 1569857] Re: Show installation and uninstallation history
** Changed in: gnome-software Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1569857 Title: Show installation and uninstallation history Status in GNOME Software: Fix Released Status in Ubuntu GNOME: Confirmed Status in gnome-software package in Ubuntu: Triaged Bug description: I much prefer GNOME Software to the Ubuntu Software Center, however I believe that there is one thing lacking in GS which is present in USC, the installation and uninstallation history. That is, the history of all packaged which have been installed and uninstalled, I believe that this is a very important feature for any software center like application to have and GS users would benefit from it. Upstream: https://gitlab.gnome.org/GNOME/gnome-software/issues/51 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1569857/+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
Looking in the root directory of the first partition of the 23.04 beta image contains 'network-config' think this is a user setting file, forgot to set this while testing but I was using wired, as the file contains: # This file contains a netplan-compatible configuration which cloud-init will # apply on first-boot (note: it will *not* update the config after the first # boot). Please refer to the cloud-init documentation and the netplan reference # for full details: # # https://netplan.io/reference # https://cloudinit.readthedocs.io/en/latest/topics/network-config.html # https://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v2.html # # Please note that the YAML format employed by this file is sensitive to # differences in whitespace; if you are editing this file in an editor (like # Notepad) which uses literal tabs, take care to only use spaces for # indentation. See the following link for more details: # # https://en.wikipedia.org/wiki/YAML # Some additional examples are commented out below network: version: 2 ethernets: eth0: dhcp4: true optional: true # wifis: #wlan0: # dhcp4: true # optional: true # access-points: #myhomewifi: # password: "S3kr1t" #myworkwifi: # password: "correct battery horse staple" #workssid: # auth: #key-management: eap #method: peap #identity: "m...@example.com" #password: "passw0rd" #ca-certificate: /etc/my_ca.pem # regulatory-domain: GB I'll use wifi for the next install and see how that goes. -- 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 1993668] Re: mSBC codec not available only CVSD one
** Changed in: pipewire Status: Fix Released => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1993668 Title: mSBC codec not available only CVSD one Status in Linux: Confirmed Status in PipeWire: New Status in linux package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Bug description: I am using Ubuntu 22.10 and my headset Pixel Buds Pro works correctly but only the low-quality CVSD codec is available and not the mSBC one for the Handsfree profile. I know the Pixel Buds Pro headset are compatible with mSBC because on another machine also running Ubuntu 22.10, this headset correctly works with the mSBC codec (and the audio quality is much better for both input and output audio). My motherboard is an Aorus x670 with AMD Zen 4 CPU. The bluetooth controller seems to be: ``` Bus 005 Device 003: ID 0e8d:0616 MediaTek Inc. Wireless_Device ``` Let me know if you need more informations. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-27 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) NonfreeKernelModules: nvidia_modeset nvidia Package: pipewire 0.3.58-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1993668/+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 2016172] Re: Missing figures
This bug was fixed in the package gnome-user-docs - 44.0-1ubuntu2 --- gnome-user-docs (44.0-1ubuntu2) lunar; urgency=medium * Add missing figures (LP: #2016172) -- Gunnar Hjalmarsson Thu, 13 Apr 2023 20:02:12 +0200 ** Changed in: gnome-user-docs (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/2016172 Title: Missing figures Status in gnome-user-docs package in Ubuntu: Fix Released Bug description: This is terribly late, I know. When trying to build the Ubuntu Desktop Guide for the web, I noticed that three figures were missing. I have uploaded a fix to the unapproved queue and reported it upstream. It would not be the end of the world if we shipped the package without those figures, but it would be nice to get them in. :) In any case I will include the patch in the web version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/2016172/+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 2012991] Re: Insensitive items in system tray menus not visible
** Changed in: yaru-theme (Ubuntu) Status: New => Fix Committed ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Medium ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012991 Title: Insensitive items in system tray menus not visible Status in gnome-shell-extension-appindicator package in Ubuntu: Won't Fix Status in yaru-theme package in Ubuntu: Fix Committed Bug description: If you use the multipass system tray menu the text on the items that are insensitive aren't visible. It appears they have the same colour as the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012991/+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 2016183] [NEW] Ubuntu 22.10 nautilus serch sits and spins
Public bug reported: ubuntu 22.10, Nautilus search not working, when opening a directory the files and folders display instantaneously as expected, as normal I start typing the name of the file/folder I am interested in. If I type in only one letter the search seems to work instantly, but if I type in the second letter of the search string the search just sits and spins. I have experimented with it and if I leave it for some time (multiples of minutes) it will eventually find what I have searched for. I notice several complaints online for this exact problem and it seems that nobody has a solution for it. I have a couple of screen recordings to show the problem. Ubuntu 22.10 About files -> 'Files, The Gnome Project - 43.0' (nautilus) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screen recording of the problem." https://bugs.launchpad.net/bugs/2016183/+attachment/5663731/+files/Screencast%20from%202023-04-13%2023-09-41.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2016183 Title: Ubuntu 22.10 nautilus serch sits and spins Status in nautilus package in Ubuntu: New Bug description: ubuntu 22.10, Nautilus search not working, when opening a directory the files and folders display instantaneously as expected, as normal I start typing the name of the file/folder I am interested in. If I type in only one letter the search seems to work instantly, but if I type in the second letter of the search string the search just sits and spins. I have experimented with it and if I leave it for some time (multiples of minutes) it will eventually find what I have searched for. I notice several complaints online for this exact problem and it seems that nobody has a solution for it. I have a couple of screen recordings to show the problem. Ubuntu 22.10 About files -> 'Files, The Gnome Project - 43.0' (nautilus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016183/+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 2000743] Re: kinetic: UI unresponsive while disk op dialog showing.
One more video showing how the dialog dominates the UI. In the video I open a terminal and put a sleep (so I can setup the UI dialog) in front of executing google-chrome as a simple example. At the end of the video, the UI is still locked up but you can see the copy dialog not behind the new window but the rest of the file browser is. ** Attachment added: "PXL_20230413_195725415.TS.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2000743/+attachment/5663730/+files/PXL_20230413_195725415.TS.mp4 -- 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/2000743 Title: kinetic: UI unresponsive while disk op dialog showing. Status in gnome-shell package in Ubuntu: New Bug description: This bug is easily reproducible on my system, a new installation of kinetic. 1) Using a large file (my case is > 8gb), via the UI, drag and drop to copy. 2) When the "pie chart" UI indicator starts filling up, click the pie chart UI item to show the speed of the transfer. 3) Notice, once the pie chart is expanded to show the progress details, it is not possible to click on any window to switch applications. One either needs to wait for the transfer to complete or dismiss the file transfer progress UI. While writing this bug, I thought it would be useful to take a screenshot using the default method and even that locks up the UI and must be dismissed before the UI becomes responsive again. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-12-06 (127 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 43.1-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: kinetic Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2000743/+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 2016182] [NEW] terminal opened started from nautilus does not get focus
Public bug reported:
Terminals launched from the nautilus context menu ("Open in Terminal") do not
automatically receive focus.If one starts typing, the input goes to nautilus
instead of the terminal and the terminal needs to be selected manually to get
focus.
Steps:
1. right-click in nautilus
2. select "Open in Terminal"
3. A terminal pops up but the prompt is inactive
I gave up on 22.10 because it had the same issue. I thought the issue
would be solved by now but clearly it still exists. Maybe the behaviour
is intended but that feels go against basic UX...
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.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Apr 13 21:34:46 2023
InstallationDate: Installed on 2022-10-29 (166 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: nautilus
UpgradeStatus: Upgraded to lunar on 2023-04-12 (1 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
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lunar
--
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/2016182
Title:
terminal opened started from nautilus does not get focus
Status in nautilus package in Ubuntu:
New
Bug description:
Terminals launched from the nautilus context menu ("Open in Terminal") do not
automatically receive focus.If one starts typing, the input goes to nautilus
instead of the terminal and the terminal needs to be selected manually to get
focus.
Steps:
1. right-click in nautilus
2. select "Open in Terminal"
3. A terminal pops up but the prompt is inactive
I gave up on 22.10 because it had the same issue. I thought the issue
would be solved by now but clearly it still exists. Maybe the
behaviour is intended but that feels go against basic UX...
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.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Apr 13 21:34:46 2023
InstallationDate: Installed on 2022-10-29 (166 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: nautilus
UpgradeStatus: Upgraded to lunar on 2023-04-12 (1 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/2016182/+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 2016082] Re: CUPS doesnt add my HP LasterJet MFP N280nw anymore
** Changed in: cups (Ubuntu) Status: New => Invalid -- 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/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: Invalid Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 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.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+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 2015943] Re: gstreamer 1.22.2 bugfix release
This bug was fixed in the package gstreamer1.0 - 1.22.2-1 --- gstreamer1.0 (1.22.2-1) experimental; urgency=medium * Team upload * New upstream bugfix release (LP: #2015943) -- Jeremy Bicha Wed, 12 Apr 2023 11:47:38 -0400 ** Changed in: gstreamer1.0 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015943 Title: gstreamer 1.22.2 bugfix release Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Triaged Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Bug description: https://gstreamer.freedesktop.org/releases/1.22/#1.22.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/2015943/+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
Given there doesn't seem much interest in fixing this from the network manager angle (and there's even a question as to whether that's the right place to fix this), I'm going to take a leaf out of the RaspiOS book, and see if I can persuade someone that the installer is the right place to fix this (or more specifically, the new installer, subiquity). That's not going to do anything for lunar which won't be using subiquity on the raspi images, so I'll hold off on adding the project to the "affected" list until lunar's out, but it should be something I can try and push for in the m-animal cycle. @jgneff many thanks for the additional report -- it's extremely useful to have stuff like this I can point to and say "look! It's actually a problem!" -- 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 2000743] Re: kinetic: UI unresponsive while lengthy disk op dialog showing.
** Summary changed: - kinetic: UI unresponsive while lengthy disk operations complete. + kinetic: UI unresponsive while lengthy disk op dialog showing. ** Summary changed: - kinetic: UI unresponsive while lengthy disk op dialog showing. + kinetic: UI unresponsive while disk op dialog showing. -- 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/2000743 Title: kinetic: UI unresponsive while disk op dialog showing. Status in gnome-shell package in Ubuntu: New Bug description: This bug is easily reproducible on my system, a new installation of kinetic. 1) Using a large file (my case is > 8gb), via the UI, drag and drop to copy. 2) When the "pie chart" UI indicator starts filling up, click the pie chart UI item to show the speed of the transfer. 3) Notice, once the pie chart is expanded to show the progress details, it is not possible to click on any window to switch applications. One either needs to wait for the transfer to complete or dismiss the file transfer progress UI. While writing this bug, I thought it would be useful to take a screenshot using the default method and even that locks up the UI and must be dismissed before the UI becomes responsive again. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-12-06 (127 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 43.1-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: kinetic Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2000743/+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 2012638] Re: tracker-extract-3 crashed with SIGSEGV in decorator_item_cache_remove()
This bug was fixed in the package tracker-miners - 3.4.3-1ubuntu3 --- tracker-miners (3.4.3-1ubuntu3) lunar; urgency=medium * Add tracker-extract-Add-missing-break-to-remove-a-single.patch to fix SIGSEGV in decorator_item_cache_remove (LP: #2012638) -- Daniel van Vugt Thu, 13 Apr 2023 17:34:18 +0800 ** Changed in: tracker-miners (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/2012638 Title: tracker-extract-3 crashed with SIGSEGV in decorator_item_cache_remove() Status in Tracker: New Status in tracker-miners package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/76c7a9b949987c296ebfd60bf2328fc949156e32 laptop freeze when trying change desktop background ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: tracker-extract 3.4.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 23 15:49:56 2023 ExecutablePath: /usr/libexec/tracker-extract-3 InstallationDate: Installed on 2023-03-23 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230323) ProcCmdline: /usr/libexec/tracker-extract-3 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f611a08e5b8:mov(%r15),%rbx PC (0x7f611a08e5b8) ok source "(%r15)" (0x2c0010b18b376185) not located in a known VMA region (needed readable region)! destination "%rbx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: tracker-miners StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/tracker-miners-3.0/libtracker-miner-3.0.so ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8 g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: tracker-extract-3 crashed with SIGSEGV in ffi_call() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/2012638/+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 2016172] [NEW] Missing figures
Public bug reported: This is terribly late, I know. When trying to build the Ubuntu Desktop Guide for the web, I noticed that three figures were missing. I have uploaded a fix to the unapproved queue and reported it upstream. It would not be the end of the world if we shipped the package without those figures, but it would be nice to get them in. :) In any case I will include the patch in the web version. ** Affects: gnome-user-docs (Ubuntu) Importance: Undecided Assignee: Gunnar Hjalmarsson (gunnarhj) Status: In Progress ** Description changed: This is terribly late, I know. When trying to build the Ubuntu Desktop Guide for the web, I noticed that three figures were missing. I have uploaded a fix to the unapproved - queue. + queue and reported it upstream. It would not be the end of the world if we shipped the package without those figures, but it would be nice to get them in. :) In any case I will include the patch in the web version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/2016172 Title: Missing figures Status in gnome-user-docs package in Ubuntu: In Progress Bug description: This is terribly late, I know. When trying to build the Ubuntu Desktop Guide for the web, I noticed that three figures were missing. I have uploaded a fix to the unapproved queue and reported it upstream. It would not be the end of the world if we shipped the package without those figures, but it would be nice to get them in. :) In any case I will include the patch in the web version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/2016172/+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 2000743] Re: kinetic: UI unresponsive while lengthy disk operations complete.
There wasn't any activity noticeable in top and no updates from the journalctl command. I've attached a video demonstrating it is really just about the dialog displayed. Even dismissing, switching programs to show the UI is responsive, then showing the PI chart dialog again (before it times out and disappears) recreates the UI problem. ** Attachment added: "PXL_20230413_170853766.TS.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2000743/+attachment/5663674/+files/PXL_20230413_170853766.TS.mp4 -- 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/2000743 Title: kinetic: UI unresponsive while lengthy disk operations complete. Status in gnome-shell package in Ubuntu: New Bug description: This bug is easily reproducible on my system, a new installation of kinetic. 1) Using a large file (my case is > 8gb), via the UI, drag and drop to copy. 2) When the "pie chart" UI indicator starts filling up, click the pie chart UI item to show the speed of the transfer. 3) Notice, once the pie chart is expanded to show the progress details, it is not possible to click on any window to switch applications. One either needs to wait for the transfer to complete or dismiss the file transfer progress UI. While writing this bug, I thought it would be useful to take a screenshot using the default method and even that locks up the UI and must be dismissed before the UI becomes responsive again. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-12-06 (127 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 43.1-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: kinetic Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2000743/+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 1983794] Re: Evolution not deleting autosave files
Jaap, what's needed is a verification for kinetic. Please see the test
plan in the bug description at the very top, and try out the package
from proposed as outlined in comment #24.
And we also need a kinetic verification on
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200 which
is being fixed in the same upload.
Since jammy comes before kinetic, and both are affected, we need the
verification to be complete for both, to avoid jammy users upgrading to
kinetic and experiencing the bug again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
Confirmed
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions
--
Mailing list: https://launchpad.net/~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 1965323] Re: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen
Still exists on current Ubuntu Lunar. ** Summary changed: - Wayland: overview hotspot is not recognised if cursor slides to it along top of screen + Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL -- 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/1965323 Title: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL Status in gnome-shell package in Ubuntu: New Bug description: Using Wayland, ubuntu-gnome, nvidia-510, RTL locale (hebrew). When sliding the cursor along the top (horizontal) edge of the screen to the hotspot at the top right corner of the screen (where the activities menu is found in an rtl environment), gnome-shell does not go into overview mode (and back). When sliding the cursor to the very same hotspot along the right (vertical) edge of the screen, gnome-shell works properly and goes to overview mode (and back). This problem exists only in wayland gnome sessions. It does not occur in x11 gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Mar 17 17:21:49 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-01-31 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=he_IL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965323/+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 2016169] Re: ayatana-indicator-messages-service crashed with SIGSEGV in g_type_check_instance()
*** This bug is a duplicate of bug 2015848 *** https://bugs.launchpad.net/bugs/2015848 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2015848, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2016169/+attachment/5663662/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2016169/+attachment/5663664/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2016169/+attachment/5663668/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2016169/+attachment/5663669/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2016169/+attachment/5663670/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2016169/+attachment/5663671/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2016169/+attachment/5663672/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 2015848 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2016169 Title: ayatana-indicator-messages-service crashed with SIGSEGV in g_type_check_instance() Status in ayatana-indicator-messages package in Ubuntu: New Bug description: ayatana-indicator-messages-service crashed with SIGSEGV in g_type_check_instance() ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ayatana-indicator-messages 22.9.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Thu Apr 13 23:15:22 2023 ExecutablePath: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service InstallationDate: Installed on 2023-04-13 (0 days ago) InstallationMedia: Ubuntu-MATE 23.04 "Lunar Lobster" - Daily amd64 (20230413) ProcCmdline: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service SegvAnalysis: Segfault happened at: 0x7fbd37a25d4d : mov (%rax),%rdx PC (0x7fbd37a25d4d) ok source "(%rax)" (0x55ca0d2bb0b6) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ayatana-indicator-messages StacktraceTop: g_type_check_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_handlers_disconnect_matched () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: ayatana-indicator-messages-service crashed with SIGSEGV in g_type_check_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2016169/+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 2016000] Re: Settings > Online Accounts > Add Google Account > foreverloading password prompt
The issue was resolved by using XORG instead of Wayland with NVIDIA. Seems that NVIDIA hates it if you want a secure desktop environment, even though you're already using their proprietary drivers. Filthy NVIDIA. ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- 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/2016000 Title: Settings > Online Accounts > Add Google Account > foreverloading password prompt Status in gnome-control-center package in Ubuntu: Invalid Bug description: when trying to add a google account in Settings > Online Accounts, it is forever stuck on loading. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 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.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Wed Apr 12 21:26:57 2023 InstallationDate: Installed on 2023-04-12 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230412) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2016000/+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
> is that having a visible impact for users? like was your computer not able to connect to some access point? Yes. I just hit this problem on my new Raspberry Pi 400 with Ubuntu. The Raspberry Pi OS dated February 21, 2023, based on Debian 11 (bullseye), sets my Wi-Fi region code to Canada during installation, and everything works fine. I then tried the Ubuntu 22.10 (Kinetic Kudu) 64-bit desktop image and could no longer find my 5-GHz Wi-Fi access point. It turns out that my 5-GHz Wi-Fi is on channel 149, which is available in Canada but not available when the country code is unset. Channel 149 is not permitted in Japan, Turkey, and South Africa. [1] Adding "cfg80211.ieee80211_regdom=CA" to the end of the following file solved the problem: $ cat /boot/firmware/cmdline.txt zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash cfg80211.ieee80211_regdom=CA It took me forever to find this bug report! The notes here are very helpful. I agree that it would be great to have the country code set automatically when the region is set at installation, and then again in the settings of the Wi-Fi configuration panels. That's certainly the first place I checked while trying to fix it. [1]: https://en.wikipedia.org/wiki/List_of_WLAN_channels -- 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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
I am dropping block-proposed-kinetic because Kinetic already has the increased crash rate. ** Tags removed: block-proposed-kinetic -- 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/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Fix Released Status in mozjs102 package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Status in mozjs102 source package in Jammy: Fix Committed Status in mozjs102 source package in Kinetic: Fix Committed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 2013236] Re: Failed to install bcmwl wireless driver during the install
@Alberto - oh yeah, updating the initramfs prevented it from being loaded without the command line arguments. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
I manually installed the 74ubuntu2 release on my Ubuntu 22.04.2 LTS system, and this release does not appear to fix the issue. I can also confirm that Merci's description of the requirements to trigger the bug also affect me in the same way. However, doing some additional checking, I can expand this to: - Scaling greater than or equal to 200% (fractional or non-fractional) - Dock set to auto-hide - Dock position is "left" - All other dock options have no impact A scale of 175% does not activate the bug, only 200 and greater. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Confirmed Bug description: The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/dash-to-dock/+bug/1979096/+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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
Given comment #12, I'm adding a block-proposed tag to this bug. Is this something we could use to improve the test plan of this package by any chance? Since it seems to have introduced crashes on kinetic. ** Tags added: block-proposed-jammy ** Tags added: block-proposed-kinetic -- 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/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Fix Released Status in mozjs102 package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Status in mozjs102 source package in Jammy: Fix Committed Status in mozjs102 source package in Kinetic: Fix Committed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 1927149] Re: Irrelevant translatable strings
During a discussion here: https://salsa.debian.org/gnome-team/gnome-software/-/commit/6e0534db the idea was born to address this issue in a more generic way via dh- translations. So I submitted a pkgbinarymangler merge proposal (see link above). ** Also affects: pkgbinarymangler (Ubuntu) Importance: Undecided Status: New ** Changed in: pkgbinarymangler (Ubuntu) Status: New => In Progress ** Changed in: pkgbinarymangler (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Merge proposal linked: https://code.launchpad.net/~gunnarhj/+git/pkgbinarymangler/+merge/440954 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1927149 Title: Irrelevant translatable strings Status in AppStream: Unknown Status in GNOME Software: Fix Released Status in snap-store-desktop: New Status in gnome-software package in Ubuntu: Fix Released Status in pkgbinarymangler package in Ubuntu: In Progress Bug description: When building gnome-software on Ubuntu, dh_translations generates a translation template (.pot file) to be imported to Rosetta. That template includes 700+ log messages from data/appdata/org.gnome.Software.appdata.xml.in. The messages are not shown to users, and it makes no sense to have those strings translated. It's worth mentioning that the strings are excluded in upstream's translation template. The issue was first reported at the ubuntu-translators mailing list: https://lists.ubuntu.com/archives/ubuntu-translators/2021-May/007757.html I stripped the redundant strings from the template and uploaded it to hirsute manually as a temporary measure. The reason why this happens seems to be that the appstream package is included in Build-Depends. appstream installs the file /usr/share/gettext/its/metainfo.its with rules which make all the log entries be extracted. But the gettext package installs /usr/share/gettext-0.21/its/metainfo.its with more sensible rules which do not make the log entries be extracted. If the former is not present, xgettext falls back to the latter. So a solution to this issue is to drop appstream from Build-Depends. gnome-software seems to build fine without that package (tested in PPA). To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1927149/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Christian, it should only be using msbc when the headset's microphone is in use, otherwise it should automatically fall back to A2DP. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 2016082] Re: CUPS doesnt add my HP LasterJet MFP N280nw anymore
I found the issue. But I have no idea why. RustDesk blocks somehow the mdns communication. That is also the reason why printing was so slow. But with the last update of cups-browsed printing was not possible anymore at all. https://github.com/rustdesk/rustdesk/issues/3129 Seems it was fixed from rustdesk. This call can be closed. Sorry! ** Bug watch added: github.com/rustdesk/rustdesk/issues #3129 https://github.com/rustdesk/rustdesk/issues/3129 -- 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/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: New Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 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.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+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 1844453] Re: [upstream] Access to the Google remote account does not work
** Changed in: df-libreoffice
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1844453
Title:
[upstream] Access to the Google remote account does not work
Status in LibreOffice:
Confirmed
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+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 1844453]
Cloph, you were assigned by Heiko since 2021. I've reset that to the
default, as prrvchr said they were interested in working on it in
comment 95.
prrvchr, are you still interested in submitting patches? If so, please
go ahead and assign yourself.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1844453
Title:
[upstream] Access to the Google remote account does not work
Status in LibreOffice:
Confirmed
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+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 2015997] Re: gnome-shell crashed with SIGSEGV in wl_resource_get_client() from meta_wayland_keyboard_get_focus_client() from owner_changed_cb()
Yesterday I had zero problems with FF revision 2487 (firefox 111.0.1-2), but today I got a bunch of updated mesa packages for 23.04, so, decided to check if they helped, upgraded FF snap once again to rev.2559 and this time system worked for a couple of hours before total GUI crash on some youtube video. My journal before crash in attachment ** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015997/+attachment/5663594/+files/journal.log -- 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/2015997 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_client() from meta_wayland_keyboard_get_focus_client() from owner_changed_cb() Status in gnome-shell package in Ubuntu: New Bug description: Hi. I just got two crashes in a row trying to watch this video: https://t.me/TeamShcherbakova/9113 Snapped Firefox just got updated to 112.0-2 rev.2559, so maybe it's Firefox's fault. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 Uname: Linux 6.2.0-20-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 12 13:32:42 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/delirium Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015997/+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 2016082] Re: CUPS doesnt add my HP LasterJet MFP N280nw anymore
It seems that cups hangs at the ippfind command now. ** Attachment added: "Screenshot_20230413_135030.png" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+attachment/5663592/+files/Screenshot_20230413_135030.png -- 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/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: New Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 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.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+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 2016082] Re: CUPS doesnt add my HP LasterJet MFP N280nw anymore
Source : https://bugs.launchpad.net/ubuntu/+source/android- androresolvd/+bug/1803663/comments/2 -- 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/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: New Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 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.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Thank you for your response Konrad. I followed the docs for replacing pulseaudio with pipewire which worked well. Now the bluetooth app offers more codecs to use. I figured out "mSBC" offers the best quality. Compared to A2DP it still sucks and sounds horrible. You dont want to accept this if you bought a bluetooth headset for 250 EUR with brilliant audio capabilities. So I ended up to use a separate mic from my webcam. Hope this will be fixed soon. Thank you so far. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 2003192]
here the interfaces with better formatting ``` $ snap interfaces thunderbird ## SNAP CONFIGURATION Slot Plug gnome-3-38-2004:gnome-3-38-2004 thunderbird gtk-common-themes:gtk-3-themes thunderbird gtk-common-themes:icon-themes thunderbird gtk-common-themes:sound-themes thunderbird :audio-playback thunderbird :browser-support thunderbird:browser-sandbox :cups-controlthunderbird :desktop thunderbird :desktop-legacy thunderbird :gsettings thunderbird :homethunderbird :network thunderbird :opengl thunderbird :system-filesthunderbird:etc-thunderbird-policies :wayland thunderbird thunderbird:dbus-daemon - -thunderbird:avahi-observe -thunderbird:camera -thunderbird:gpg-keys -thunderbird:network-control -thunderbird:removable-media -thunderbird:u2f-devices -thunderbird:x11 ``` -- 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/2003192 Title: thunderbird snap does not work without x11 interface connected Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: New Bug description: When I disconnect the thunderbird from the x11 interface thunderbird crashes saying it can not find the wayland socket. If I add a link to the wayland socket inside the container thunderbird works fine. That is on kubuntu 22.04 in a plasma/wayland session, MOZ_ENABLE_WAYLAND=1 is set on the host and in the container as well. This also probably means that the thunderbird snap actually never uses native wayland and falls back to xwayland (because the wayland socket can not be found). This unintended use of xwayland could be construed as a security issue, but someone who mistrusts snaps using x11 (like me) will remove the permission which leads to failure instead of a security issue. $ snap run thunderbird ## BROKEN ... [GFX1-]: glxtest: libpci missing [GFX1-]: glxtest: Could not connect to wayland socket [GFX1-]: No GPUs detected via PCI (thunderbird:103861): Gtk-WARNING **: 12:37:14.162: cannot open display: :1 ExceptionHandler::GenerateDump cloned child 103976 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... $ snap run --shell thunderbird ## FIXING IT To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. user@user-mycomputer:/$ ln -s /run/user/1000/wayland-0 $XDG_RUNTIME_DIR/ ; exit $ snap run thunderbird ## NOW IT WORKS $ lsb_release -rd ## UBUNTU VERSION Description:Ubuntu 22.04.1 LTS Release:22.04 $ snap interfaces thunderbird ## SNAP CONFIGURATION Slot Plug gnome-3-38-2004:gnome-3-38-2004 thunderbird gtk-common-themes:gtk-3-themes thunderbird gtk-common-themes:icon-themesthunderbird gtk-common-themes:sound-themes thunderbird :audio-playback thunderbird :browser-support thunderbird:browser-sandbox :cups-controlthunderbird :desktop thunderbird :desktop-legacy thunderbird :gsettings thunderbird :homethunderbird :network thunderbird :opengl thunderbird :system-filesthunderbird:etc-thunderbird-policies :wayland thunderbird thunderbird:dbus-daemon - -thunderbird:avahi-observe -thunderbird:camera -thunderbird:gpg-keys -thunderbird:network-control -thunderbird:removable-media -thunderbird:u2f-devices -thunderbird:x11 $ snap info thunderbird ## THUNDERBIRD SNAP VERSION ... installed: 102.7.0-1(288) 106MB - $ snap --version ## SNAPD etc VERSION snap2.58 snapd 2.58 series 16 ubuntu 22.04 kernel 5.15.0-57-generic To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/2003192/+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/ListH
[Desktop-packages] [Bug 2016082] Re: CUPS doesnt add my HP LasterJet MFP N280nw anymore
subscription file gets huge and ippfind runs permanent. -- 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/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: New Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 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.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+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 2016082] [NEW] CUPS doesnt add my HP LasterJet MFP N280nw anymore
Public bug reported: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 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.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- 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/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: New Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 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.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@Christian, @Konrad, Ubuntu 22.04 has this fixed. It was fixed in PulseAudio 15, run `pulseaudio --version` to see the version you are running. But HSP sound is still much worse than A2DP sound e.g. if you listen to music. HSP is still mono and limited to a bandwidth of 8 kHz. The scope of this bug was only to support WBS in the Linux stack, so improve HSP sound from even more terrible 4 kHz bandwidth to what it is now. The current limitations are with the Bluetooth specification and the limited data rates that bluetooth offers, so PipeWire is not going to help with that. If you want better two-way sound your options currently are using a wire, or using a proprietary wireless transmission (search for gaming headsets) or Bluetooth codec (there is the FastStream codec, but supporting headsets are extremely rare, I couldn't find anything with a proper mic that I would consider for video calls). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 2013236] Re: Failed to install bcmwl wireless driver during the install
@Brian: did you update the initramfs after blacklisting the module? sudo update-initramfs -u -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@Christian Mint is based on Ubuntu 22.04 which is from 2022 so uses old pulse-audio. > When I switch to A2DP I cannot use the headset mic. This is expected, A2DP is one direction only. > When I switch to HFP the sound in conversations is horrible. pulse-audio is kind of abandoned and actively developed. There are some fixes added but it seams that all effort goes to pipewire now. Give it a try. Add repositories for latest version: sudo add-apt-repository ppa:pipewire-debian/wireplumber-upstream sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream Follow instructions to install and enable pipewire. There are multiple guide on the Internet, for example: https://trendoceans.com/enable-pipewire-and-disable-pulseaudio-in-ubuntu/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 Status: Unknown => New -- 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: New 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 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
** Also affects: accountsservice via https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/113 Importance: Unknown Status: Unknown -- 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: New 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 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
Confirmed, the issue is also still there using accountsservices master, I've reported it upstream with a valgrind log now https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/113 ** Changed in: indicator-messages (Ubuntu) Importance: Undecided => High ** Changed in: accountsservice (Ubuntu) Importance: Undecided => High ** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: accountsservice (Ubuntu) Status: Confirmed => In Progress ** Bug watch added: gitlab.freedesktop.org/accountsservice/accountsservice/-/issues #113 https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/113 -- 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 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/ubuntu/+source/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 2009767] Update Released
The verification of the Stable Release Update for xorg-server has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: New Status in nvidia-graphics-drivers-525 source package in Focal: Fix Committed Status in xorg-server source package in Focal: New Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Committed Status in xorg-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Committed Status in xorg-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Lunar: Fix Committed Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] NVIDIA driver has a hardcoded version check to see if a bug has been fixed in the xserver version. It does not help to backport the fix to the jammy xserver, as the driver has no way to check if the fix is there or not. We need to backport xorg-server from kinetic to jammy. [Test case] install xserver update, check that lagginess is gone [Regression potential] This is a backport of kinetic xorg-server to jammy, with 34 new upstream commits of which three were already backported due to CVE's, and a bugfix. 18 commits only touch darwin/XQuartz and won't affect us. As such, there should be a low chance of things breaking. Here's a list of the remaining 12 commits with above filtered out: 6bf62381d0a1fb5 xserver 21.1.4 855b96a85bc0711 xfree86: Fix event data alignment in inputtest driver b713e717c34d539 dix: Correctly save replayed event into GrabInfoRec cd3d21d8c44a35c xkb: fix XkbSetMap when changing a keysym without changing a keytype f575524314e9f20 Revert "os: Try to discover the current seat with the XDG_SEAT var first" 433f53a1a08390a tests: Fix build failure from missing micmap.c 3868f364728ae0c xf86-input-inputtest: Fix build on systems without SOCK_NONBLOCK afcaaac96767d77 print_edid: Fix a format string error 663af2f17eec2cc X11Application: Ensure TIS operations are done on the main thread bd3564cf377deac rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is already defined) 53173fdab492f0f render: Fix build with gcc 12 69774044716039f present: Check for NULL to prevent crash --- original info [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be black in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Workaround] Downgrade to NVIDIA driver 515. [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+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 2009767] Re: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system
This bug was fixed in the package xorg-server - 2:21.1.4-2ubuntu1.7~22.04.1 --- xorg-server (2:21.1.4-2ubuntu1.7~22.04.1) jammy; urgency=medium * Backport to jammy. (LP: #2009767) -- Timo Aaltonen Tue, 04 Apr 2023 09:20:09 +0300 ** Changed in: xorg-server (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: New Status in nvidia-graphics-drivers-525 source package in Focal: Fix Committed Status in xorg-server source package in Focal: New Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Committed Status in xorg-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Committed Status in xorg-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Lunar: Fix Committed Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] NVIDIA driver has a hardcoded version check to see if a bug has been fixed in the xserver version. It does not help to backport the fix to the jammy xserver, as the driver has no way to check if the fix is there or not. We need to backport xorg-server from kinetic to jammy. [Test case] install xserver update, check that lagginess is gone [Regression potential] This is a backport of kinetic xorg-server to jammy, with 34 new upstream commits of which three were already backported due to CVE's, and a bugfix. 18 commits only touch darwin/XQuartz and won't affect us. As such, there should be a low chance of things breaking. Here's a list of the remaining 12 commits with above filtered out: 6bf62381d0a1fb5 xserver 21.1.4 855b96a85bc0711 xfree86: Fix event data alignment in inputtest driver b713e717c34d539 dix: Correctly save replayed event into GrabInfoRec cd3d21d8c44a35c xkb: fix XkbSetMap when changing a keysym without changing a keytype f575524314e9f20 Revert "os: Try to discover the current seat with the XDG_SEAT var first" 433f53a1a08390a tests: Fix build failure from missing micmap.c 3868f364728ae0c xf86-input-inputtest: Fix build on systems without SOCK_NONBLOCK afcaaac96767d77 print_edid: Fix a format string error 663af2f17eec2cc X11Application: Ensure TIS operations are done on the main thread bd3564cf377deac rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is already defined) 53173fdab492f0f render: Fix build with gcc 12 69774044716039f present: Check for NULL to prevent crash --- original info [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be black in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Workaround] Downgrade to NVIDIA driver 515. [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+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 2009767] Re: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system
the only remaining failing test is just bad (nvidia 390 on i386), as it's failing always -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: New Status in nvidia-graphics-drivers-525 source package in Focal: Fix Committed Status in xorg-server source package in Focal: New Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Committed Status in xorg-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Committed Status in xorg-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Lunar: Fix Committed Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] NVIDIA driver has a hardcoded version check to see if a bug has been fixed in the xserver version. It does not help to backport the fix to the jammy xserver, as the driver has no way to check if the fix is there or not. We need to backport xorg-server from kinetic to jammy. [Test case] install xserver update, check that lagginess is gone [Regression potential] This is a backport of kinetic xorg-server to jammy, with 34 new upstream commits of which three were already backported due to CVE's, and a bugfix. 18 commits only touch darwin/XQuartz and won't affect us. As such, there should be a low chance of things breaking. Here's a list of the remaining 12 commits with above filtered out: 6bf62381d0a1fb5 xserver 21.1.4 855b96a85bc0711 xfree86: Fix event data alignment in inputtest driver b713e717c34d539 dix: Correctly save replayed event into GrabInfoRec cd3d21d8c44a35c xkb: fix XkbSetMap when changing a keysym without changing a keytype f575524314e9f20 Revert "os: Try to discover the current seat with the XDG_SEAT var first" 433f53a1a08390a tests: Fix build failure from missing micmap.c 3868f364728ae0c xf86-input-inputtest: Fix build on systems without SOCK_NONBLOCK afcaaac96767d77 print_edid: Fix a format string error 663af2f17eec2cc X11Application: Ensure TIS operations are done on the main thread bd3564cf377deac rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is already defined) 53173fdab492f0f render: Fix build with gcc 12 69774044716039f present: Check for NULL to prevent crash --- original info [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be black in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Workaround] Downgrade to NVIDIA driver 515. [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+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
