[Desktop-packages] [Bug 2011782] Re: gnome-shell crashed with SIGSEGV in g_hash_table_remove_all() from do_theme_change() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_
This seems to happen when I click Dark Style in quick settings. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/2011782 Title: gnome-shell crashed with SIGSEGV in g_hash_table_remove_all() from do_theme_change() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() 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~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/379c8c7c360c033e3135ef22242fd198891cbb2d 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/2011782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011782] Re: gnome-shell crashed with SIGSEGV in g_hash_table_remove_all() from do_theme_change() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/2011782 Title: gnome-shell crashed with SIGSEGV in g_hash_table_remove_all() from do_theme_change() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() 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~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/379c8c7c360c033e3135ef22242fd198891cbb2d 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/2011782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011781] [NEW] /usr/bin/gnome-shell:11:clutter_frame_clock_schedule_update:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit
*** This bug is a duplicate of bug 2011700 *** https://bugs.launchpad.net/bugs/2011700 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~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/433869a57fd92ff072080b57691ff91122f8e054 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/2011781 Title: /usr/bin/gnome- shell:11:clutter_frame_clock_schedule_update:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit 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~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/433869a57fd92ff072080b57691ff91122f8e054 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/2011781/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011781] Re: /usr/bin/gnome-shell:11:clutter_frame_clock_schedule_update:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit
*** This bug is a duplicate of bug 2011700 *** https://bugs.launchpad.net/bugs/2011700 ** This bug has been marked a duplicate of private bug 2011700 -- 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/2011781 Title: /usr/bin/gnome- shell:11:clutter_frame_clock_schedule_update:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit 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~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/433869a57fd92ff072080b57691ff91122f8e054 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/2011781/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011700] Re: gnome-shell crashed with SIGSEGV at clutter_frame_clock_schedule_update(frame_clock=NULL)
Tracking in https://errors.ubuntu.com/problem/433869a57fd92ff072080b57691ff91122f8e054 ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2011700/+attachment/5654641/+files/CoreDump.gz ** Description changed: - I have this error after opening libreoffice-base + https://errors.ubuntu.com/problem/433869a57fd92ff072080b57691ff91122f8e054 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 Uname: Linux 5.19.0-21-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 15 12:18:55 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1677216555 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/judemont ProcEnviron: - LANG=fr_FR.UTF-8 - PATH=(custom, user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + PATH=(custom, user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2011700 Title: gnome-shell crashed with SIGSEGV at clutter_frame_clock_schedule_update(frame_clock=NULL) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/433869a57fd92ff072080b57691ff91122f8e054 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 Uname: Linux 5.19.0-21-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 15 12:18:55 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1677216555 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/judemont ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2011700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011782] Re: gnome-shell crashed with SIGSEGV in g_hash_table_remove_all() from do_theme_change() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_
** Summary changed: - /usr/bin/gnome-shell:11:g_hash_table_remove_all:do_theme_change:update_current_theme:g_closure_invoke:signal_emit_unlocked_R + gnome-shell crashed with SIGSEGV in g_hash_table_remove_all() from do_theme_change() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() -- 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/2011782 Title: gnome-shell crashed with SIGSEGV in g_hash_table_remove_all() from do_theme_change() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() 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~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/379c8c7c360c033e3135ef22242fd198891cbb2d 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/2011782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011782] [NEW] gnome-shell crashed with SIGSEGV in g_hash_table_remove_all() from do_theme_change() from update_current_theme() from g_closure_invoke() from signal_emit_unlocke
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~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/379c8c7c360c033e3135ef22242fd198891cbb2d 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: High Status: Confirmed ** 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/2011782 Title: gnome-shell crashed with SIGSEGV in g_hash_table_remove_all() from do_theme_change() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() 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~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/379c8c7c360c033e3135ef22242fd198891cbb2d 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/2011782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011778] [NEW] Screenshot icon is missing (question mark shown instead)
Public bug reported: Screenshot icon is missing (question mark shown instead). See attached screenshot. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: lunar visual-quality ** Attachment added: "Screenshot from 2023-03-16 13-29-15.png" https://bugs.launchpad.net/bugs/2011778/+attachment/5654767/+files/Screenshot%20from%202023-03-16%2013-29-15.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2011778 Title: Screenshot icon is missing (question mark shown instead) Status in yaru-theme package in Ubuntu: New Bug description: Screenshot icon is missing (question mark shown instead). See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2011778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011777] [NEW] Rounded buttons in quick settings are broken
Public bug reported: Rounded buttons in quick settings are broken (see screenshot) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: lunar visual-quality ** Attachment added: "Screenshot from 2023-03-16 13-29-15.png" https://bugs.launchpad.net/bugs/2011777/+attachment/5654766/+files/Screenshot%20from%202023-03-16%2013-29-15.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2011777 Title: Rounded buttons in quick settings are broken Status in yaru-theme package in Ubuntu: New Bug description: Rounded buttons in quick settings are broken (see screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2011777/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988393] Re: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
** Tags added: regression-proposed -- 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/1988393 Title: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 Status in gjs: Fix Released Status in gjs package in Ubuntu: Fix Released Bug description: I'm seeing this in everyone's kinetic logs: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 and it appears gjs is the only place where too many arguments are provided. To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1988393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 might become a "Won't fix" for 525 but let's track it more accurately there for the time being. ** Summary changed: - external HDMI monitor is laggy on NV reverse PRIME system + External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system ** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Kinetic) Status: New => Confirmed ** No longer affects: nvidia-graphics-drivers (Ubuntu Kinetic) ** No longer affects: nvidia-graphics-drivers (Ubuntu) -- 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: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Confirmed Status in nvidia-graphics-drivers-525 source package in Kinetic: Confirmed Status in xorg-server source package in Kinetic: Fix Released Bug description: [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 blak 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 1988393] Re: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
Looks like the bug is in jammy proposed now too. ** Tags added: jammy -- 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/1988393 Title: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 Status in gjs: Fix Released Status in gjs package in Ubuntu: Fix Released Bug description: I'm seeing this in everyone's kinetic logs: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 and it appears gjs is the only place where too many arguments are provided. To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1988393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
On Lunar(23.04), I could reproduce this issue too. With upstream's patch, this issue is fixed on ThinkPad T14s. gnome-settings-daemon 44~rc-1ubuntu1 network-manager 1.40.12-1ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Triaged Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: The value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, which will lead to a airplane mode switching failure when host has WWAN device(s). There is a MR on the upstream project, which can solve this bug. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/310 The description copied from the MR: g-signal is not fired on property changes, so nm_signal is never called, and all changes of NetworkManager's WwanEnabled property are missed. That leads to an inability to disable the airplane mode on laptops with WWAN after the airplane mode was once enabled by button. Fix this by subscribing to g-properties-changed to actually listen to the updates of WwanEnabled. It also makes the code simpler. == 1. About Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and manager->wwan_enabled is set to the correct value. 4. Actual: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the initial value of manager->wwan_enabled is true, it will never be able to switch to airplane mode. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Triaged Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: The value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, which will lead to a airplane mode switching failure when host has WWAN device(s). There is a MR on the upstream project, which can solve this bug. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/310 The description copied from the MR: g-signal is not fired on property changes, so nm_signal is never called, and all changes of NetworkManager's WwanEnabled property are missed. That leads to an inability to disable the airplane mode on laptops with WWAN after the airplane mode was once enabled by button. Fix this by subscribing to g-properties-changed to actually listen to the updates of WwanEnabled. It also makes the code simpler. == 1. About Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and manager->wwan_enabled is set to the correct value. 4. Actual: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the initial value of manager->wwan_enabled is true, it will never be able to switch to airplane mode. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011760] Re: Clicking links on desktop doesn´t take me to the web
What is the file format/extension you are trying to click on? Also, did you try right clicking and selecting 'Allow Launching'? Please run: file ~/Desktop/* > ~/desktopfiles.txt and attach the resulting text file here. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-desktop-icons-ng (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons-ng (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/2011760 Title: Clicking links on desktop doesn´t take me to the web Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Incomplete Bug description: When I click a link on the desktop (i.e: Snap-store) it doesn´t take me to the web. I've also tested uploading a file, but the browse button to search the file doesn´t work. I have tested with Chrome.deb, firefox snap, opera deb, and snap-store, and the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-37.38~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 16 04:13:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (58 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2011760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011770] [NEW] [gsd-rfkill] WwanEnabled never get synced
Public bug reported: The value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, which will lead to a airplane mode switching failure when host has WWAN device(s). There is a MR on the upstream project, which can solve this bug. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/310 The description copied from the MR: g-signal is not fired on property changes, so nm_signal is never called, and all changes of NetworkManager's WwanEnabled property are missed. That leads to an inability to disable the airplane mode on laptops with WWAN after the airplane mode was once enabled by button. Fix this by subscribing to g-properties-changed to actually listen to the updates of WwanEnabled. It also makes the code simpler. == 1. About Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and manager->wwan_enabled is set to the correct value. 4. Actual: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the initial value of manager->wwan_enabled is true, it will never be able to switch to airplane mode. ** Affects: oem-priority Importance: Critical Assignee: Atlas Yu (pseudoc) Status: Triaged ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2007638 sutton ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Triaged ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Atlas Yu (pseudoc) ** Tags added: oem-priority originate-from-2007638 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Triaged Status in gnome-settings-daemon package in Ubuntu: New Bug description: The value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, which will lead to a airplane mode switching failure when host has WWAN device(s). There is a MR on the upstream project, which can solve this bug. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/310 The description copied from the MR: g-signal is not fired on property changes, so nm_signal is never called, and all changes of NetworkManager's WwanEnabled property are missed. That leads to an inability to disable the airplane mode on laptops with WWAN after the airplane mode was once enabled by button. Fix this by subscribing to g-properties-changed to actually listen to the updates of WwanEnabled. It also makes the code simpler. == 1. About Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and manager->wwan_enabled is set to the correct value. 4. Actual: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the initial value of manager->wwan_enabled is true, it will never be able to switch to airplane mode. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
Seems like a fix exists, but it got stalled/forgotten: https://gitlab.gnome.org/GNOME/gsettings-desktop- schemas/-/merge_requests/55 ** No longer affects: curtin (Ubuntu) ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in gsettings-desktop-schemas package in Ubuntu: In Progress Status in subiquity package in Ubuntu: Won't Fix Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
I'm experiencing the same issue and it is really annoying. I don't remember mounting anything that connects with the internet. How can I make sure of that? -- 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/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING Status in nautilus package in Ubuntu: Confirmed Bug description: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer- to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg- run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011760] [NEW] Clicking links on desktop doesn´t take me to the web
Public bug reported: When I click a link on the desktop (i.e: Snap-store) it doesn´t take me to the web. I've also tested uploading a file, but the browse button to search the file doesn´t work. I have tested with Chrome.deb, firefox snap, opera deb, and snap-store, and the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-37.38~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 16 04:13:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (58 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2011760 Title: Clicking links on desktop doesn´t take me to the web Status in gnome-shell package in Ubuntu: New Bug description: When I click a link on the desktop (i.e: Snap-store) it doesn´t take me to the web. I've also tested uploading a file, but the browse button to search the file doesn´t work. I have tested with Chrome.deb, firefox snap, opera deb, and snap-store, and the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-37.38~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 16 04:13:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (58 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 NV reverse PRIME system
** Description changed: [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 blak 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 -- 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 NV reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Confirmed Status in nvidia-graphics-drivers source package in Kinetic: New Status in xorg-server source package in Kinetic: Fix Released Bug description: [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 blak 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 1956099] Re: WiFi scan MAC is not randomized
** Tags added: kinetic lunar -- 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/1956099 Title: WiFi scan MAC is not randomized Status in network-manager package in Ubuntu: New Bug description: Every distribution, Gnome itself, and OS are moving or have moved forward with this as a basic privacy measure. The old bugs and abstractions no longer exist AFAIK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1956099/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007262] Re: Ubuntu's GNOME desktop is higher latency than necessary
** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2007262 Title: Ubuntu's GNOME desktop is higher latency than necessary Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Triaged Status in mutter source package in Kinetic: Triaged Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] Ubuntu's GNOME desktop is higher latency than necessary. It's stuck in triple buffering when it should be dropping to double buffering during light rendering. [ Test Plan ] 1. Add this to /etc/environment: MUTTER_DEBUG=kms 2. Reboot and log into a Wayland session. 3. Open a Terminal and run: journalctl -f /usr/bin/gnome-shell | grep 'Swap buffers' 4. Drag the Terminal window rapidly with the mouse (a high sample rate mouse will also help). Observed bug: "KMS: Swap buffers: 2 frames pending (triple-buffering)" Expected fix: "KMS: Swap buffers: 1 frames pending (double-buffering)" If you don't at first confirm the bug prior to the fix then try dragging the window to the top bar before wiggling it or opening the overview to make the render load higher. The fix will make the log messages return to double buffering much sooner and stay there more reliably. [ Where problems could occur ] Any part of the smoothness of the desktop experience could be impacted since the fix involves changing the frame clock for frame scheduling. [ Other Info ] Upstream fix: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441/diffs?commit_id=17ea73d0570318926899c4e3e4821a8b7b21edae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2007262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
>I would appreciate if you avoided adding uninvolved components to the bug What is the correct package for an existing gsetting and GUI selectable feature that should be a default based purely on install selectable variables? >Last I see they are sitting in a "volunteers welcome" state, or dependencies on things that need further work. So it will never happen then. It is already a setting based on a selection that is already done in the installer [timezone based on area]. >Official time standards for the or one of the largest install bases in the world is not justification because Ubuntu chose this specific DE? >This sort of change is really best done in a package in the archive Something like a gnome-fix-usa-time.deb that adds 12h upon install and is triggered by selecting a US timezone? Sounds great. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in curtin package in Ubuntu: Invalid Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: Won't Fix Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/1949340 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in GTK+: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
Curtin is not the appropriate place to land fixes or even quirk workarounds for this problem. I would appreciate if you avoided adding uninvolved components to the bug, especially when it has already been pointed out that this is the wrong spot. The linked threads you mention do not appear to me to have an "all but refused" stance. Last I see they are sitting in a "volunteers welcome" state, or dependencies on things that need further work. This sort of change is really best done in a package in the archive, and I'm not hearing appropriate justification for installer quirks. Declining for Subiquity, thanks. ** Changed in: subiquity (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in curtin package in Ubuntu: Invalid Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: Won't Fix Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 595934] Re: gvfs-backends should be split in multiple sub-packages
** Tags added: bloat gvfs jammy kinetic lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/595934 Title: gvfs-backends should be split in multiple sub-packages Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: New Bug description: Binary package hint: gvfs The gvfs-backends should be transformed in a meta-package that only recommends other more specific sub-packages. Currently the gvfs-backends package contains «the afc, archive, burn, cdda, dav, dnssd, ftp, gphoto2, http, network, obexftp, sftp, smb and smb-browse backends» and depends on 22 different libraries. While all these backends may come handy at times, low-resource computer would benefit if some of these where not installed. For example cd-less computers (not only netbooks) do not need the "burn" or "cdda" backends. These two backends install and run a demon that requires memory and installs unneeded libraries. A similar argument applies to the AFS backend (not that much useful these days to a wide audience, runs a daemon), gphoto2 (office workstation and thin clients do not need it, runs a daemon), obexftp (makes any Gnome installation dependent on Bluetooth libraries) and any other protocol. While installing all these backends by default is certainly a good thing, not having a way to remove them when not needed is a problem. Making gvfs-backends a meta-package and splitting its current content in multiple packages (gvfs-backends-afs, gvfs-backends-sftp, gvfs- backends-smb) would retain the good behaviour while still allowing users with little resources (RAM, disk, CPU) to remove the unneeded components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/595934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956109] Re: printer-driver-ptouch is included with metapackages for the minimal install
** Tags added: kinetic lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956109 Title: printer-driver-ptouch is included with metapackages for the minimal install Status in ubuntu-meta package in Ubuntu: New Bug description: A label printer driver is a recommended dependency of many desktop, core, and minimal ubuntu metapackages. It is installed with the minimal Ubuntu option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956109/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956110] Re: upower requires libimobiledevice6 as a dependency
** Tags added: kinetic lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1956110 Title: upower requires libimobiledevice6 as a dependency Status in libimobiledevice package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: An iPhone library is required to have power management required by Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1956110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
** Changed in: curtin (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in curtin package in Ubuntu: Invalid Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: Incomplete Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011740] [NEW] segfault trying to scan fingerprint with Goodix on MSI
Public bug reported: [44598.119761] fprintd[13]: segfault at 0 ip 7f6e3c356210 sp 7ffc7facaba0 error 4 in libfprint-2.so.2.0.0[7f6e3c32b000+4a000] [44598.119773] Code: 04 24 00 00 00 00 eb a8 e8 4d 79 fd ff 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 55 48 89 d5 53 48 89 fb 48 83 ec 08 <0f> b6 0e 84 c9 78 19 c7 43 78 00 00 00 00 48 83 c4 08 48 89 ee 48 [44599.086567] usb 3-3: USB disconnect, device number 4 [44599.502418] usb 3-3: new full-speed USB device number 12 using xhci_hcd [44599.651809] usb 3-3: New USB device found, idVendor=27c6, idProduct=6094, bcdDevice= 1.00 [44599.651812] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [44599.651813] usb 3-3: Product: Goodix USB2.0 MISC [44599.651814] usb 3-3: Manufacturer: Goodix Technology Co., Ltd. [44599.651814] usb 3-3: SerialNumber: UID5B6ECFF9__MOC_B0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libfprint-2-2 1:1.94.5+tod1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Mar 15 15:10:32 2023 InstallationDate: Installed on 2022-09-30 (165 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: libfprint UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2011740 Title: segfault trying to scan fingerprint with Goodix on MSI Status in libfprint package in Ubuntu: New Bug description: [44598.119761] fprintd[13]: segfault at 0 ip 7f6e3c356210 sp 7ffc7facaba0 error 4 in libfprint-2.so.2.0.0[7f6e3c32b000+4a000] [44598.119773] Code: 04 24 00 00 00 00 eb a8 e8 4d 79 fd ff 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 55 48 89 d5 53 48 89 fb 48 83 ec 08 <0f> b6 0e 84 c9 78 19 c7 43 78 00 00 00 00 48 83 c4 08 48 89 ee 48 [44599.086567] usb 3-3: USB disconnect, device number 4 [44599.502418] usb 3-3: new full-speed USB device number 12 using xhci_hcd [44599.651809] usb 3-3: New USB device found, idVendor=27c6, idProduct=6094, bcdDevice= 1.00 [44599.651812] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [44599.651813] usb 3-3: Product: Goodix USB2.0 MISC [44599.651814] usb 3-3: Manufacturer: Goodix Technology Co., Ltd. [44599.651814] usb 3-3: SerialNumber: UID5B6ECFF9__MOC_B0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libfprint-2-2 1:1.94.5+tod1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Mar 15 15:10:32 2023 InstallationDate: Installed on 2022-09-30 (165 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: libfprint UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2011740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
I would point to the new ubuntu-desktop-installer directly but it isn't listed here. I don't care where in that stack it is done. Gnome has all but refused to address this. A post-install or live preinstall hook fixes this. Both linked packages contain one or both of these features as listed in their documentation. https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues/30 https://gitlab.gnome.org/GNOME/glib/-/issues/2575 https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/merge_requests/55 https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2422 If it can be handled by simple gsettings or locale defaults, it should be done until a better fix comes along. It is an option to click on that should be the default by any official consumer or commercial standard in the USA. I don't think this should require justification in 2023. ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2575 https://gitlab.gnome.org/GNOME/glib/-/issues/2575 ** No longer affects: curtain (Ubuntu) ** Also affects: curtin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in curtin package in Ubuntu: New Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: Incomplete Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
Curtin (no "a") doesn't manage time settings, so the fix definitely isn't going there. Comment #4 though makes this sound like it needs to be in the image, and isn't installer specific? Or can you clarify what you'd like the installer to do here? ** Changed in: curtain (Ubuntu) Status: New => Invalid ** Changed in: subiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in curtain package in Ubuntu: Invalid Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: Incomplete Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: curtain (Ubuntu) Importance: Undecided Status: New ** Tags added: kinetic lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in curtain package in Ubuntu: New Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: New Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735002] Re: Allow configuring Wi-Fi MAC Randomization feature from GUI
I don't want to re-enable this feature until there is a GUI way to turn it off either altogether or for a particular network. It's nice that it works in most places but there are still cases where a user may want to disable it for themselves. -- 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/1735002 Title: Allow configuring Wi-Fi MAC Randomization feature from GUI Status in gnome-control-center: Confirmed Status in NetworkManager: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: Recent versions of NetworkManager have a feature enabled by default to use a random MAC address when scanning for available Wi-Fi networks for privacy. My understanding is that the spoofed MAC address is not used when actually connecting to a network. This feature was disabled in Ubuntu 17.10 because it broke scanning with some Wi-Fi drivers. My understanding is that there is a bug in some drivers when attempting to change the MAC address. See LP: #1681513. The bug might not be as big of an issue with the latest version of NetworkManager because 1) There are helpful commits like this (it was not backported to 17.04): https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=46d53e1 2) It is also possible now to selectively disable Wi-Fi MAC Randomization for specific drivers. https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b869d9 However, I'm really hesitant to re-enable this feature as long as A) we don't know for sure which drivers are affected, B) and more importantly, there is no GUI way to turn the feature on or off. Asking users to edit config files isn't very nice. The MAC Address Randomization feature is really nice (Windows 10 has a similar feature) but I think we need a GUI on/off switch in Settings > Wi-Fi or Settings > Privacy. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1735002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735002] Re: Allow configuring Wi-Fi MAC Randomization feature from GUI
Has the non-GUI part of issue not been solved through blacklists, configuration or internal NM bugfixes yet? Most other distributions and NM themselves have scan randomization enabled as a default. -- 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/1735002 Title: Allow configuring Wi-Fi MAC Randomization feature from GUI Status in gnome-control-center: Confirmed Status in NetworkManager: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: Recent versions of NetworkManager have a feature enabled by default to use a random MAC address when scanning for available Wi-Fi networks for privacy. My understanding is that the spoofed MAC address is not used when actually connecting to a network. This feature was disabled in Ubuntu 17.10 because it broke scanning with some Wi-Fi drivers. My understanding is that there is a bug in some drivers when attempting to change the MAC address. See LP: #1681513. The bug might not be as big of an issue with the latest version of NetworkManager because 1) There are helpful commits like this (it was not backported to 17.04): https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=46d53e1 2) It is also possible now to selectively disable Wi-Fi MAC Randomization for specific drivers. https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b869d9 However, I'm really hesitant to re-enable this feature as long as A) we don't know for sure which drivers are affected, B) and more importantly, there is no GUI way to turn the feature on or off. Asking users to edit config files isn't very nice. The MAC Address Randomization feature is really nice (Windows 10 has a similar feature) but I think we need a GUI on/off switch in Settings > Wi-Fi or Settings > Privacy. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1735002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011727] [NEW] Seemingly random crashes of all terminal windows
Public bug reported: Typically this happens when I have 4 windows open. This seems to be a new issue for me, dating back perhaps a couple of weeks. I've used this particular 4 terminal setup for years without issues. When the issue occurs, all terminal windows vanish instantly, and I need to restart all of them. Other applications seem unaffected. Details are: log 1005=> lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 log 1006=> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages And in /var/log/syslog I'm seeing the following - (Server ID removed from log): Mar 15 10:16:19 gnome-terminal-server[96577]: VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:19 gnome-terminal-server[96577]: Bail out! VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Main process exited, code=dumped, status=6/ABRT Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Failed with result 'core-dump'. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2011727 Title: Seemingly random crashes of all terminal windows Status in gnome-terminal package in Ubuntu: New Bug description: Typically this happens when I have 4 windows open. This seems to be a new issue for me, dating back perhaps a couple of weeks. I've used this particular 4 terminal setup for years without issues. When the issue occurs, all terminal windows vanish instantly, and I need to restart all of them. Other applications seem unaffected. Details are: log 1005=> lsb_release -rd Description: Ubuntu 20.04.5 LTS Release: 20.04 log 1006=> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages And in /var/log/syslog I'm seeing the following - (Server ID removed from log): Mar 15 10:16:19 gnome-terminal-server[96577]: VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:19 gnome-terminal-server[96577]: Bail out! VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row >= m_start): (10011 >= 14401) Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Main process exited, code=dumped, status=6/ABRT Mar 15 10:16:20 systemd[2497]: gnome-terminal-server.service: Failed with result 'core-dump'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2011727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007746] Re: [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver
** Tags added: se sts -- 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/2007746 Title: [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Focal: In Progress Bug description: [ Impact ] * Microsoft Azure NV-series instances with NVidia GRID drivers started to experience xserver crashes while following Microsoft's official guide to installing Nvidia drivers [1]. * Root cause analysis showed that it was due to having a device with BusID "PCI:0@:0:0", where domain id is >= 32767 while the hyperv_drm kernel module is loaded. * Removing either the BusID specification or unloading the hyperv_drm kernel module seems to fix the crash. * The crash is happening while X.server is trying to enumerate PCI devices. X.server dereferences a NULL pointer while trying to access to the PCI device info. * The reason why it only happens while the hyperv_drm kernel module is loaded is that the hyperv_drm module does not expose PCI hardware information since it's a virtual device. * The upstream patch [2] addresses the issue and it's confirmed that the xserver with the patch does not experience the crash. * Ubuntu Focal `xorg-server` package does not include the patch [2] at the moment (xserver-xorg-core=2:1.20.13-1ubuntu1~20.04.6). [1]: https://learn.microsoft.com/en-us/azure/virtual-machines/linux/n-series-driver-setup#install-grid-drivers-on-nv-or-nvv3-series-vms [2]: https://github.com/freedesktop/xorg-xserver/commit/0d93bbfa2cfacbb73741f8bed0e32fa1a656b928 [ Test Plan ] Part (a) is quoted from Microsoft's official guide [1]. Part (a): * Spawn a Microsoft Azure NV-series instance with an NVidia GRID-supported GPU - e.g. `NV36adms A10` * Install updates, required tooling, and the desktop environment: - sudo apt-get update - sudo apt-get upgrade -y - sudo apt-get dist-upgrade -y - sudo apt-get install build-essential ubuntu-desktop -y - sudo apt-get install linux-azure -y * Disable nouveau kernel driver: # Create a blacklist file /etc/modprobe.d/nouveau.conf with following contents: blacklist nouveau blacklist lbm-nouveau * Reboot the VM, re-connect, and then stop X server: - sudo reboot # wait for the reboot, reconnect, and continue: - sudo systemctl stop lightdm.service * Download and install the NVidia GRID driver: - wget -O NVIDIA-Linux-x86_64-grid.run https://go.microsoft.com/fwlink/?linkid=874272 - chmod +x NVIDIA-Linux-x86_64-grid.run - sudo ./NVIDIA-Linux-x86_64-grid.run - # When the setup asks whether you want to run the nvidia-xconfig utility to update your X configuration file, select Yes. * Copy /etc/nvidia/gridd.conf.template to /etc/nvidia/gridd.conf - sudo cp /etc/nvidia/gridd.conf.template /etc/nvidia/gridd.conf * Edit /etc/nvidia/grid.conf - sudo nano /etc/nvidia/grid.conf # Append the following lines: IgnoreSP=FALSE EnableUI=FALSE # Remove this line if present: FeatureType=0 # And save. * Reboot the VM Part (b): * Ensure that the hyperv_drm kernel module is loaded: - sudo modprobe hyperv_drm * Use the attached xorg.conf file to override /etc/X11/xorg.conf file * try to start the `xserver`: - sudo startx * `xserver` should crash with a similar output to the following: X.Org X Server 1.20.13 X Protocol Version 11, Revision 0 Build Operating System: linux Ubuntu Current Operating System: Linux a10test 5.15.0-1031-azure #38~20.04.1-Ubuntu SMP Mon Jan 9 18:23:48 UTC 2023 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1031-azure root=PARTUUID=4cac852b-afba-447b-b3e7-c002155c1305 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 panic=-1 Build Date: 07 February 2023 12:48:13PM xorg-server 2:1.20.13-1ubuntu1~20.04.6 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Sat Feb 18 10:54:26 2023 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55e7787c5ecc] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f9576cac420] (EE) 2: /usr/lib/xorg/Xorg
[Desktop-packages] [Bug 2011717] Re: settings crash on open
*** This bug is a duplicate of bug 2011313 *** https://bugs.launchpad.net/bugs/2011313 Thanks for your report. I suspect this is a duplicate of bug #2011313, so marking it as such. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011717/+attachment/5654657/+files/CoreDump.gz ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 2011313 gnome-control-center crashes after launch -- 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/2011717 Title: settings crash on open Status in gnome-control-center package in Ubuntu: New Bug description: Just tried to open and then select a section on left and it closed and crashed. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 Uname: Linux 6.1.0-16-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 15 09:53:35 2023 ExecutablePath: /usr/bin/gnome-control-center ExecutableTimestamp: 1673628537 ProcCmdline: /usr/bin/gnome-control-center ProcCwd: /home/rick ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-control-center UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011656] Re: ibus-x11 crashed with SIGSEGV in _int_malloc()
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2011656/+attachment/5654564/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2011656 Title: ibus-x11 crashed with SIGSEGV in _int_malloc() Status in ibus package in Ubuntu: New Bug description: editing python code with idle, doing a select with shift-arrow in prep to a cut operation ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-1 ProcVersionSignature: Ubuntu 5.19.0-1012.19-raspi 5.19.17 Uname: Linux 5.19.0-1012-raspi aarch64 ApportVersion: 2.26.0-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 23:41:55 2023 ExecutablePath: /usr/libexec/ibus-x11 ImageMediaBuild: 20221018.1 JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/ibus-x11 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: ibus StacktraceTop: _int_malloc (av=av@entry=0x892f0b00 , bytes=bytes@entry=48) at ./malloc/malloc.c:3923 __GI___libc_malloc (bytes=48) at ./malloc/malloc.c:3305 g_malloc () from /lib/aarch64-linux-gnu/libglib-2.0.so.0 g_source_new () from /lib/aarch64-linux-gnu/libglib-2.0.so.0 g_timeout_source_new () from /lib/aarch64-linux-gnu/libglib-2.0.so.0 Title: ibus-x11 crashed with SIGSEGV in _int_malloc() UpgradeStatus: Upgraded to lunar on 2023-01-31 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2011656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011722] [NEW] Move oem-config-setup steps into ubuntu-raspi-settings-desktop
Public bug reported: When building images with livecd-rootfs, there is a hook to set up oem- config for preinstalled raspi desktop images. As we move away from livecd-rootfs (and the use of hooks in general), this step should be moved into a package. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2011722 Title: Move oem-config-setup steps into ubuntu-raspi-settings-desktop Status in ubuntu-settings package in Ubuntu: New Bug description: When building images with livecd-rootfs, there is a hook to set up oem-config for preinstalled raspi desktop images. As we move away from livecd-rootfs (and the use of hooks in general), this step should be moved into a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2011722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011595] Re: Wrong shell icons in lunar
** Changed in: gnome-shell (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 in Ubuntu. https://bugs.launchpad.net/bugs/2011595 Title: Wrong shell icons in lunar Status in gnome-shell package in Ubuntu: Fix Released Bug description: At each boot the icons in the dock are wrong (left column of the attached image) then i open gmome-tweaks - icons active are Yaru - I select another icon set, the go back to Yaru end the icons change to the correct type (right column of attached image) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-ubuntu-dock 79ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 16:09:22 2023 InstallationDate: Installed on 2023-02-25 (17 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011595/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009481] Re: FFE: mesa 23.0.1
** Description changed: Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch to use for Ubuntu 23.04. This release includes improvements across the board, and packaging adds a package for mesa-drm-shim. 23.0.1 should be released on week 10, so it's a good candidate for an upload. + + + diffstat: + git diff mesa-22.3.6..mesa-23.0.0 | diffstat | tail -1 + 2493 files changed, 710212 insertions(+), 170014 deletions(-) + + commits: + git log1 mesa-22.3.6..mesa-23.0.0 | wc -l +3157 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2009481 Title: FFE: mesa 23.0.1 Status in mesa package in Ubuntu: Incomplete Bug description: Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch to use for Ubuntu 23.04. This release includes improvements across the board, and packaging adds a package for mesa-drm-shim. 23.0.1 should be released on week 10, so it's a good candidate for an upload. diffstat: git diff mesa-22.3.6..mesa-23.0.0 | diffstat | tail -1 2493 files changed, 710212 insertions(+), 170014 deletions(-) commits: git log1 mesa-22.3.6..mesa-23.0.0 | wc -l 3157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280527] Re: Xorg crashed with SIGABRT in fbBltOne()
Visit this https://downloadingbeasts.com/;>Site To Download the Cracks Software For Free there is No need of any kind of Subscription. Just download and install the Software and enjoy the Premium Items for free. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1280527 Title: Xorg crashed with SIGABRT in fbBltOne() Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: Ubuntu 14.04 Trusty ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu6 Uname: Linux 3.12.9-031209-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Fri Feb 14 23:41:42 2014 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2014-02-12 (3 days ago) InstallationMedia: Kubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140205) ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: fbBltOne () from /usr/lib/xorg/modules/libfb.so fbPutXYImage () from /usr/lib/xorg/modules/libfb.so fbPutImage () from /usr/lib/xorg/modules/libfb.so ?? () from /usr/lib/x86_64-linux-gnu/libglamor.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libglamor.so.0 Title: Xorg crashed with SIGABRT in fbBltOne() UpgradeStatus: Upgraded to trusty on 2014-02-12 (2 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1280527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011708] [NEW] [snap] Cannot open containing folder from a downloaded item if the default path is changed
Public bug reported: Note: This was filled on request. See https://bugzilla.mozilla.org/show_bug.cgi?id=1693302 for more information. Affected versions Firefox snap 111.0 Firefox snap 112.0b2 Firefox snap 102.9.0esr Tested platforms Affected platforms: Ubuntu 18.04 Unaffected platforms: Ubuntu 20.04, Ubuntu 22.04 Steps to reproduce 1. Install Firefox snap using: sudo snap install firefox --candidate. 2. Open Firefox snap and change the default download folder from about:preferences. 3. Download a random file e.g: https://www.thinkbroadband.com/download. 4. Click on Show in folder button from the downloads panel. Expected result The folder is opened as expected. Actual result The folder is not opened. Notes I cannot reproduce the issue with regular Firefox builds. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2011708 Title: [snap] Cannot open containing folder from a downloaded item if the default path is changed Status in firefox package in Ubuntu: New Bug description: Note: This was filled on request. See https://bugzilla.mozilla.org/show_bug.cgi?id=1693302 for more information. Affected versions Firefox snap 111.0 Firefox snap 112.0b2 Firefox snap 102.9.0esr Tested platforms Affected platforms: Ubuntu 18.04 Unaffected platforms: Ubuntu 20.04, Ubuntu 22.04 Steps to reproduce 1. Install Firefox snap using: sudo snap install firefox --candidate. 2. Open Firefox snap and change the default download folder from about:preferences. 3. Download a random file e.g: https://www.thinkbroadband.com/download. 4. Click on Show in folder button from the downloads panel. Expected result The folder is opened as expected. Actual result The folder is not opened. Notes I cannot reproduce the issue with regular Firefox builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2011708/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720250] Re: im-config configuration ignored with gdm3
Your analysis is absolutely correct. On my system the whole directory /usr/share/im-config/data was missing. So I did "sudo apt install --reinstall im-config" as you suggested, and, behold, that directory was restored, including the two 78* files you mentioned. Then I removed my "return" at the top of /etc/profile.d/input-method-config.sh and logged out, and then logged in again -- no more error messages. Thank you very much, Gunnar. You were very helpful and patient :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 Status in gdm3 package in Ubuntu: Invalid Status in im-config package in Ubuntu: Fix Released Bug description: After having logged in via gdm3, the IM related environment variables are always set like this: $ env | grep -E '_IM|XMOD' QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Changing ~/.xinputrc to e.g. xim makes no difference, so gdm3 prevents all other IM frameworks but IBus from working. This problem seems to be similar to bug #1594681 (which was fixed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011697] [NEW] [FFe] Ubuntu Pro integration outside of the LTS
Public bug reported: The Ubuntu Pro tab of software-properties-gtk is currently only enabled on LTS series. We would like to activate with a modified UI (to match the restricted set of services available on the serie) for Lunar. There are no changes to the existing backend code compared to what is currently being used in LTS series and the action are done through the 'pro' client so the 'new code' is limited to the UI layout tweaks. The corresponding code changes can be found on https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/438549 and ppa is available which includes a package build with the changes on https://launchpad.net/~nteodosio/+archive/ubuntu/ubuntu-pro ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2011697 Title: [FFe] Ubuntu Pro integration outside of the LTS Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Pro tab of software-properties-gtk is currently only enabled on LTS series. We would like to activate with a modified UI (to match the restricted set of services available on the serie) for Lunar. There are no changes to the existing backend code compared to what is currently being used in LTS series and the action are done through the 'pro' client so the 'new code' is limited to the UI layout tweaks. The corresponding code changes can be found on https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/438549 and ppa is available which includes a package build with the changes on https://launchpad.net/~nteodosio/+archive/ubuntu/ubuntu-pro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2011697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790608] Re: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp)
This is terrible for every small team that has files shared in NFS mounted directories that snaps cannot access. This looks essentially to be the same problem this one: https://bugs.launchpad.net/snapd/+bug/1972762 This needs a simple, user-friendly fix ASAP. -- 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/1790608 Title: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp) Status in snapd: New Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I received a document via e-mail in Thunderbird. I have the Libreoffice snap package installed. When I want to open the document from Thunderbird, I see the Libreoffice splash screen, and then a dialog stating "/tmp/mozilla_0/.docx does not exist." The same dialog appears when I navigate to the folder in Files and want to open it. When I copy the file to my desktop, however, I can open it without problems. I guess the source of the issue is confinement, that the Libreoffice snap can only access files from $HOME. But this breaks the case where thunderbird creates a temporary copy in /tmp. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1790608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching Status in OEM Priority Project: New Status in X.Org X server: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Bug description: [ Impact ] * This change will force update keyboard LED status after calling EnableDevice, in order to resolve LED status not syncing after switching VT to a X session. * This also fixes the issue with NVIDIA driver and Xorg, that after resuming from suspend the keyboard LED is always off. [ Test Plan ] 1. Log onto an GNOME Xorg session (KDE Kwin worked this issue around) 2. Turn on NumLock on the keyboard 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop NumLock LED should be on after switching back to the desktop [ Where problems could occur ] * The changes are to push status to the device when enabling it regardless of actual keyboard state change, therefore switching between VTs and adding/removing keyboard/mouse/xinput devices should be affected by this change. [ Original Report ] Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs. This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04) To reproduce: 1. Log on a X session desktop (GNOME Xorg for example) 2. Turn on NumLock 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop Expected: NumLock LED should be on Actual: NumLock LED is off, but functions like NumLock is on. If NumLock is pressed the LED turns off as well as the function. If CapsLock is pressed the LED states sync back (LED turns back on). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 NV reverse PRIME system
** Also affects: xorg-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Kinetic) Status: New => 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 NV reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Confirmed Status in nvidia-graphics-drivers source package in Kinetic: New Status in xorg-server source package in Kinetic: Fix Released Bug description: [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 blak 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 [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 2009481] Re: FFE: mesa 23.0.1
I think it makes sense to go with 23.0.1 indeed, we'll probably update it regardless. A bit unfortunate that this didn't happen earlier, but it's outside of our control. I'd still like to see the list of changes for 23.0.0 + 23.0.1, but let's consider this a pre-ACK for the FFe. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2009481 Title: FFE: mesa 23.0.1 Status in mesa package in Ubuntu: Incomplete Bug description: Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch to use for Ubuntu 23.04. This release includes improvements across the board, and packaging adds a package for mesa-drm-shim. 23.0.1 should be released on week 10, so it's a good candidate for an upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching
the nvidia autopkgtest failures are due to linux-doc not being installable on i386 anymore, the others passed now -- 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/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching Status in OEM Priority Project: New Status in X.Org X server: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Bug description: [ Impact ] * This change will force update keyboard LED status after calling EnableDevice, in order to resolve LED status not syncing after switching VT to a X session. * This also fixes the issue with NVIDIA driver and Xorg, that after resuming from suspend the keyboard LED is always off. [ Test Plan ] 1. Log onto an GNOME Xorg session (KDE Kwin worked this issue around) 2. Turn on NumLock on the keyboard 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop NumLock LED should be on after switching back to the desktop [ Where problems could occur ] * The changes are to push status to the device when enabling it regardless of actual keyboard state change, therefore switching between VTs and adding/removing keyboard/mouse/xinput devices should be affected by this change. [ Original Report ] Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs. This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04) To reproduce: 1. Log on a X session desktop (GNOME Xorg for example) 2. Turn on NumLock 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop Expected: NumLock LED should be on Actual: NumLock LED is off, but functions like NumLock is on. If NumLock is pressed the LED turns off as well as the function. If CapsLock is pressed the LED states sync back (LED turns back on). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected
I am facing exactly the same issue. I have tried using 2-3 headphones (having inbuilt microphone as wel), but the OS is not recognizing any, as if the headphone jack is broken/faulty. These headpones are working well on another PC (Dell) though. ravi@razer:~$ sudo hdajacksensetest -a //without plugging the headphone Pin 0x12 (Internal Mic, Mobile-In): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Black Mic, Right side): present = No Pin 0x1a (Not connected): present = No Pin 0x1b (Not connected): present = Yes Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Right side): present = No ravi@razer:~$ sudo hdajacksensetest -a //with plugging the headhone Pin 0x12 (Internal Mic, Mobile-In): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Black Mic, Right side): present = No Pin 0x1a (Not connected): present = No Pin 0x1b (Not connected): present = Yes Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Right side): present = No Under the "Output Devices" tab in the pavucontrol, it shows "Headphones (unplugged)". Strangely, selecting "Headphones (unplugged)" from the dropdown menu makes sound in my headphone. In summary, headphones are not detected automatically. I can hear using headphones after selecting them inside pavucontrol, but even inside pavucontrol, headphones are shown as "Headphones (unplugged)" I reported at AskUbuntu (https://askubuntu.com/q/1454505) but no response. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1807138 Title: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade
