[Desktop-packages] [Bug 2015041] Re: gnome-shell crashed with SIGTRAP in g_log_structured_array() from g_log_default_handler() from g_logv() from g_log() from display_error_event() [The error was 'Bad
** Summary changed: - /usr/bin/gnome-shell:5:g_log_structured_array:g_log_default_handler:g_logv:g_log:display_error_event + gnome-shell crashed with SIGTRAP in g_log_structured_array() from g_log_default_handler() from g_logv() from g_log() from display_error_event() [The error was 'BadMatch (invalid parameter attributes)'.\n (Details: serial error_code 8 request_code 147 (unknow"...] -- 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/2015041 Title: gnome-shell crashed with SIGTRAP in g_log_structured_array() from g_log_default_handler() from g_logv() from g_log() from display_error_event() [The error was 'BadMatch (invalid parameter attributes)'.\n (Details: serial error_code 8 request_code 147 (unknow"...] Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/900549c5a5f0e016f97439ac2b3829882c826689 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/2015041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015041] [NEW] gnome-shell crashed with SIGTRAP in g_log_structured_array() from g_log_default_handler() from g_logv() from g_log() from display_error_event() [The error was 'B
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/900549c5a5f0e016f97439ac2b3829882c826689 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/2015041 Title: gnome-shell crashed with SIGTRAP in g_log_structured_array() from g_log_default_handler() from g_logv() from g_log() from display_error_event() [The error was 'BadMatch (invalid parameter attributes)'.\n (Details: serial error_code 8 request_code 147 (unknow"...] Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/900549c5a5f0e016f97439ac2b3829882c826689 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/2015041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015040] [NEW] /usr/bin/gnome-shell:5:XFlush:meta_cursor_renderer_x11_update_cursor:meta_cursor_renderer_update_cursor:meta_cursor_renderer_force_update:update_cursors
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/cd7e4f922cf2eed2f52eb9887d5413fe137c3de0 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/2015040 Title: /usr/bin/gnome- shell:5:XFlush:meta_cursor_renderer_x11_update_cursor:meta_cursor_renderer_update_cursor:meta_cursor_renderer_force_update:update_cursors Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/cd7e4f922cf2eed2f52eb9887d5413fe137c3de0 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/2015040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015040] Re: /usr/bin/gnome-shell:5:XFlush:meta_cursor_renderer_x11_update_cursor:meta_cursor_renderer_update_cursor:meta_cursor_renderer_force_update:update_cursors
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 ** This bug has been marked a duplicate of bug 2014986 [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] -- 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/2015040 Title: /usr/bin/gnome- shell:5:XFlush:meta_cursor_renderer_x11_update_cursor:meta_cursor_renderer_update_cursor:meta_cursor_renderer_force_update:update_cursors Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/cd7e4f922cf2eed2f52eb9887d5413fe137c3de0 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/2015040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015039] [NEW] /usr/bin/gnome-shell:5:XPending:g_main_context_prepare:g_main_context_iterate:g_main_loop_run:meta_context_run_main_loop
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 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-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c6063fbb3a541487a381237ffa308e1ecb9cc16b 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/2015039 Title: /usr/bin/gnome- shell:5:XPending:g_main_context_prepare:g_main_context_iterate:g_main_loop_run:meta_context_run_main_loop 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~rc-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c6063fbb3a541487a381237ffa308e1ecb9cc16b 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/2015039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015039] Re: /usr/bin/gnome-shell:5:XPending:g_main_context_prepare:g_main_context_iterate:g_main_loop_run:meta_context_run_main_loop
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 ** This bug has been marked a duplicate of bug 2014986 [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] -- 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/2015039 Title: /usr/bin/gnome- shell:5:XPending:g_main_context_prepare:g_main_context_iterate:g_main_loop_run:meta_context_run_main_loop 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~rc-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c6063fbb3a541487a381237ffa308e1ecb9cc16b 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/2015039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015035] Re: gnome-shell crashed with SIGTRAP in XInternAtom() from get_property() from meta_input_settings_x11_set_click_method() from settings_device_set_uint_setting() from
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 ** This bug has been marked a duplicate of bug 2014986 [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] -- 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/2015035 Title: gnome-shell crashed with SIGTRAP in XInternAtom() from get_property() from meta_input_settings_x11_set_click_method() from settings_device_set_uint_setting() from settings_set_uint_setting() ["The error was 'BadMatch (invalid parameter attributes)'.\n (Details: serial error_code 8 request_code 131 (XInputEx"...] Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/66f84c7f27c6678fb9c61b1742ea7409773bf8b3 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/2015035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015038] Re: gnome-shell crashed with SIGTRAP in XInternAtom() from change_property() from meta_input_settings_x11_set_disable_while_typing() from settings_device_set_bool_sett
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 ** Summary changed: - /usr/bin/gnome-shell:5:XInternAtom:change_property:meta_input_settings_x11_set_disable_while_typing:settings_device_set_bool_setting:settings_set_bool_setting + gnome-shell crashed with SIGTRAP in XInternAtom() from change_property() from meta_input_settings_x11_set_disable_while_typing() from settings_device_set_bool_setting() from settings_set_bool_setting() ** Summary changed: - gnome-shell crashed with SIGTRAP in XInternAtom() from change_property() from meta_input_settings_x11_set_disable_while_typing() from settings_device_set_bool_setting() from settings_set_bool_setting() + gnome-shell crashed with SIGTRAP in XInternAtom() from change_property() from meta_input_settings_x11_set_disable_while_typing() from settings_device_set_bool_setting() from settings_set_bool_setting() [The error was 'BadMatch (invalid parameter attributes)'.\n (Details: serial error_code 8 request_code 131 (XInputEx"...] ** Tags added: nvidia ** This bug has been marked a duplicate of bug 2014986 [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] -- 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/2015038 Title: gnome-shell crashed with SIGTRAP in XInternAtom() from change_property() from meta_input_settings_x11_set_disable_while_typing() from settings_device_set_bool_setting() from settings_set_bool_setting() [The error was 'BadMatch (invalid parameter attributes)'.\n (Details: serial error_code 8 request_code 131 (XInputEx"...] Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/20ff019874e2868e3340c579921525a3e6a2dbc7 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/2015038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2014986] Re: [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExt
** Summary changed: - [nvidia] gnome-shell crashed with signal 5 in _XEventsQueued() [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] + [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] -- 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/2014986 Title: [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015042] Re: gnome-shell crashed with double free in g_datalist_clear() from g_object_unref() from clutter_event_free()
Note this is a generic double-free bucket so incorrectly appears to affect all Ubuntu series. The only current double free of interest however is in g_datalist_clear() from g_object_unref() from clutter_event_free(). ** Summary changed: - /usr/bin/gnome-shell:free(): double free detected in tcache 2 + gnome-shell crashed with double free in g_datalist_clear() from g_object_unref() from clutter_event_free() ** Tags removed: eoan groovy hirsute -- 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/2015042 Title: gnome-shell crashed with double free in g_datalist_clear() from g_object_unref() from clutter_event_free() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/2f1a309a018d04ec84a3d6699472cadf1e5e3424 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/2015042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
Hi Seth, hi nem000, the bug (https://bugs.launchpad.net/bugs/2013453), that nem000 created was marked as a duplicate of this one. This is the case for most of the related bugs listed here. So it seems that this here is the issue to go ahead with? -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: New Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015042] [NEW] gnome-shell crashed with double free in g_datalist_clear() from g_object_unref() from clutter_event_free()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/2f1a309a018d04ec84a3d6699472cadf1e5e3424 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: bionic focal jammy kinetic 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/2015042 Title: gnome-shell crashed with double free in g_datalist_clear() from g_object_unref() from clutter_event_free() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/2f1a309a018d04ec84a3d6699472cadf1e5e3424 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/2015042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2014986] Re: [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExt
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High ** Tags added: regression-release rls-ll-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2014986 Title: [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013271] Re: GTK3 titlebar buttons are bigger than GTK4 titlebar buttons
** Bug watch added: github.com/ubuntu/yaru/issues #3882 https://github.com/ubuntu/yaru/issues/3882 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/3882 Importance: Unknown Status: Unknown -- 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/2013271 Title: GTK3 titlebar buttons are bigger than GTK4 titlebar buttons Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Confirmed Bug description: GTK3 titlebar buttons are bigger than GTK4 titlebar buttons To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2013271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013107] Re: [lunar] GNOME does not display high contrast app icons
** Bug watch added: github.com/ubuntu/yaru/issues #3878 https://github.com/ubuntu/yaru/issues/3878 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/3878 Importance: Unknown Status: Unknown -- 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/2013107 Title: [lunar] GNOME does not display high contrast app icons Status in Yaru Theme: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in gnome-themes-extra package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: New Bug description: gnome-accessibility-themes (3.28-2ubuntu1) offers an incomplete set of high contrast icons, resulting in a very inconsistent look when the user enables Accessibility > Seeing > High Contrast from gnome- control-center. A screenshot showing of the current sad state of affairs is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2013107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013107] Re: [lunar] GNOME does not display high contrast app icons
** Changed in: yaru Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2013107 Title: [lunar] GNOME does not display high contrast app icons Status in Yaru Theme: New Status in gnome-shell package in Ubuntu: Triaged Status in gnome-themes-extra package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: New Bug description: gnome-accessibility-themes (3.28-2ubuntu1) offers an incomplete set of high contrast icons, resulting in a very inconsistent look when the user enables Accessibility > Seeing > High Contrast from gnome- control-center. A screenshot showing of the current sad state of affairs is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2013107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015049] [NEW] gnome-shell-extension-prefs doesn't need to exist
Public bug reported: gnome-shell-extension-prefs doesn't need to exist. It only provides wrapper scripts to launch org.gnome.Extensions from gnome-shell-common. To further demonstrate the point, you don't even need 'gnome-shell- extension-prefs' installed to launch the app: gjs /usr/share/gnome-shell/org.gnome.Extensions Is there a good reason why the desktop file and wrapper scripts exist in a separate package to the app itself? ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jammy lunar ** Description changed: gnome-shell-extension-prefs doesn't need to exist. It only provides wrapper scripts to launch org.gnome.Extensions from gnome-shell-common. So it's only logical they should be installed by default whenever gnome- shell-common is. + + To further demonstrate the point, you don't even need 'gnome-shell- + extension-prefs' installed to launch the app: + + gjs /usr/share/gnome-shell/org.gnome.Extensions ** Tags added: jammy lunar ** Description changed: gnome-shell-extension-prefs doesn't need to exist. It only provides wrapper scripts to launch org.gnome.Extensions from gnome-shell-common. - So it's only logical they should be installed by default whenever gnome- - shell-common is. To further demonstrate the point, you don't even need 'gnome-shell- extension-prefs' installed to launch the app: - gjs /usr/share/gnome-shell/org.gnome.Extensions + gjs /usr/share/gnome-shell/org.gnome.Extensions + + Is there a good reason why the desktop file and wrapper scripts exist in + a separate package to the app itself? -- 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/2015049 Title: gnome-shell-extension-prefs doesn't need to exist Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell-extension-prefs doesn't need to exist. It only provides wrapper scripts to launch org.gnome.Extensions from gnome-shell- common. To further demonstrate the point, you don't even need 'gnome-shell- extension-prefs' installed to launch the app: gjs /usr/share/gnome-shell/org.gnome.Extensions Is there a good reason why the desktop file and wrapper scripts exist in a separate package to the app itself? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989477] Re: Switching to dark mode in settings does not change shell theme.
as far I can tell from the 23.04 dev version, this seems to now be resolved. Can anyone else confirm? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1989477 Title: Switching to dark mode in settings does not change shell theme. Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: Changing the "Style" in the "Appearance" section of "Settings" (gnome- control-center), does not update the shell theme. When I select dark mode from settings, Libadwaita apps respond to the changes, but the shell theme and GTK3 applications do not. This has been observed on both Wayland and X11. Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10 Package Version: 1:43~rc-1ubuntu2 What I Expected: Changing the style in settings will affect all the apps that support changing light/dark mode. The shell theme will also respond to the change. What happened instead: Only libadwaita apps are affected by changing the style in Settings. GTK3 apps and the shell theme do not change. When changing to dark mode via the quick settings menu, all the apps change their color scheme appropriately. However, there is not a smooth transition when switching the style from quick settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2014136] Re: gnome-shell[957]: message repeated 2 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native
** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress -- 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/2014136 Title: gnome-shell[957]: message repeated 2 times: [ (../src/backends/native/meta-onscreen- native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)] Status in gnome-shell package in Ubuntu: In Progress Bug description: Just got on inactivity ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 22:13:08 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1679944760 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/sem33 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no 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/ubuntu/+source/gnome-shell/+bug/2014136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015054] [NEW] /usr/bin/gnome-control-center:11:cc_display_config_manager_get_night_light_supported:dialog_update_state:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_va
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:44.0-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/c917df7aa152ef3144e7356e4290c799e31475b3 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-control-center (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kinetic lunar -- 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/2015054 Title: /usr/bin/gnome-control- center:11:cc_display_config_manager_get_night_light_supported:dialog_update_state:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist Status in gnome-control-center package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:44.0-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/c917df7aa152ef3144e7356e4290c799e31475b3 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-control-center/+bug/2015054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015054] Re: /usr/bin/gnome-control-center:11:cc_display_config_manager_get_night_light_supported:dialog_update_state:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_vali
reported bug #2006500 ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2015054 Title: /usr/bin/gnome-control- center:11:cc_display_config_manager_get_night_light_supported:dialog_update_state:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist Status in gnome-control-center package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:44.0-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/c917df7aa152ef3144e7356e4290c799e31475b3 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-control-center/+bug/2015054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015056] [NEW] No wallpaper / no option to open the dialog for changing the wallpaper
Public bug reported: # System information: System has upgraded from 22.10 -> 23.04 # How to reproduce 1. start up the computer. No wallpaper visible just black background. 2. right click on desktop "Change background" # Expected result Wallpaper visible / ability to change wallpaper. # output on logfile ``` 2023-04-03T10:16:46.216657+02:00 utopia-Ubuntu gnome-shell[3652]: DING: (gjs:4392): Gjs-CRITICAL **: 10:16:46.213: JS ERROR: TypeError: desktopFile is null 2023-04-03T10:16:46.216882+02:00 utopia-Ubuntu gnome-shell[3652]: DING: _createDesktopBackgroundMenu/<@/usr/share/gnome-shell/extensions/d...@rastersoft.com/desktopManager.js:1114:13 2023-04-03T10:16:46.216971+02:00 utopia-Ubuntu gnome-shell[3652]: DING: @/usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js:206:13 ``` ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gjs 1.76.0-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 10:22:09 2023 InstallationDate: Installed on 2022-11-19 (134 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gjs UpgradeStatus: Upgraded to lunar on 2023-03-31 (3 days ago) ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- 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/2015056 Title: No wallpaper / no option to open the dialog for changing the wallpaper Status in gjs package in Ubuntu: New Bug description: # System information: System has upgraded from 22.10 -> 23.04 # How to reproduce 1. start up the computer. No wallpaper visible just black background. 2. right click on desktop "Change background" # Expected result Wallpaper visible / ability to change wallpaper. # output on logfile ``` 2023-04-03T10:16:46.216657+02:00 utopia-Ubuntu gnome-shell[3652]: DING: (gjs:4392): Gjs-CRITICAL **: 10:16:46.213: JS ERROR: TypeError: desktopFile is null 2023-04-03T10:16:46.216882+02:00 utopia-Ubuntu gnome-shell[3652]: DING: _createDesktopBackgroundMenu/<@/usr/share/gnome-shell/extensions/d...@rastersoft.com/desktopManager.js:1114:13 2023-04-03T10:16:46.216971+02:00 utopia-Ubuntu gnome-shell[3652]: DING: @/usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js:206:13 ``` ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gjs 1.76.0-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 10:22:09 2023 InstallationDate: Installed on 2022-11-19 (134 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gjs UpgradeStatus: Upgraded to lunar on 2023-03-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2015056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2014136] Re: gnome-shell[957]: message repeated 2 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native
Fixed upstream in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1713158 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2014136 Title: gnome-shell[957]: message repeated 2 times: [ (../src/backends/native/meta-onscreen- native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)] Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Just got on inactivity ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 22:13:08 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1679944760 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/sem33 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no 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/ubuntu/+source/gnome-shell/+bug/2014136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006500] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported()
https://errors.ubuntu.com/problem/c917df7aa152ef3144e7356e4290c799e31475b3 in the error tracker ** Information type changed from Private to Public ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2333 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2333 -- 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/2006500 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported() Status in gnome-control-center package in Ubuntu: Triaged Bug description: gnome-control-center crashed when i try change refresh rate to other value than 60 Hz. Its crash after I tap keep changes ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 7 19:59:50 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-02-07 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) JournalErrors: lut 07 19:59:50 hostname kernel: show_signal_msg: 4 callbacks suppressed ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55a5f2b496d4:mov(%rdi),%rax PC (0x55a5f2b496d4) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2006500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006500] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported()
Seems similar to upstream https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/2333 -- 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/2006500 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported() Status in gnome-control-center package in Ubuntu: Triaged Bug description: gnome-control-center crashed when i try change refresh rate to other value than 60 Hz. Its crash after I tap keep changes ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 7 19:59:50 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-02-07 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) JournalErrors: lut 07 19:59:50 hostname kernel: show_signal_msg: 4 callbacks suppressed ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55a5f2b496d4:mov(%rdi),%rax PC (0x55a5f2b496d4) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2006500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013070] Re: 100% CPU after clicking a mountable in the dock [Attempting to call back into JSAPI ... locations.js:380]
This is the beginning of loop on my system: Apr 01 08:37:46 corrado-ll-beta udisksd[878]: Mounted /dev/sdb5 at /media/corrado/datib on behalf of uid 1000 Apr 01 08:37:46 corrado-ll-beta kernel: EXT4-fs (sdb5): recovery complete Apr 01 08:37:46 corrado-ll-beta kernel: EXT4-fs (sdb5): mounted filesystem ad275f40-453a-4d0a-9a64-9f4aad3be1df with ordered data mode. Quota mode: none. Apr 01 08:37:46 corrado-ll-beta dbus-daemon[1658]: [session uid=1000 pid=1658] Activating service name='org.gnome.Shell.HotplugSniffer' requested by ':1.32' (uid=1000 pid=1844 comm="/usr/bin/gnome-shell" label="unconfined") Apr 01 08:37:46 corrado-ll-beta dbus-daemon[1658]: [session uid=1000 pid=1658] Successfully activated service 'org.gnome.Shell.HotplugSniffer' Apr 01 08:37:46 corrado-ll-beta gnome-shell[1844]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _onMountAdded@resource:///org/gnome/shell/ui/components/autorunManager.js:146:24 Apr 01 08:37:50 corrado-ll-beta gnome-shell[1844]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Apr 01 08:37:50 corrado-ll-beta gnome-shell[1844]: == Stack trace for context 0x5589569e8900 == Apr 01 08:37:50 corrado-ll-beta gnome-shell[1844]: #0 7ffefd45b480 I /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:380 (12f3f35b6d80 @ 362) Apr 01 08:37:50 corrado-ll-beta gnome-shell[1844]: #1 5589581f83a0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:172 (12f3f35b6740 @ 127) Apr 01 08:37:50 corrado-ll-beta gnome-shell[1844]: #2 5589581f82e8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:571 (12f3f35ba5b0 @ 229) Apr 01 08:37:50 corrado-ll-beta gnome-shell[1844]: #3 5589581f8238 i self-hosted:632 (2f715e045060 @ 15) Apr 01 08:37:50 corrado-ll-beta gnome-shell[1844]: The offending callback was SourceFunc(). Apr 01 08:37:50 corrado-ll-beta gnome-shell[1844]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Apr 01 08:37:50 corrado-ll-beta gnome-shell[1844]: == Stack trace for context 0x5589569e8900 == Apr 01 08:37:50 corrado-ll-beta gnome-shell[1844]: #0 7ffefd45b480 I /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:380 (12f3f35b6d80 @ 362) Apr 01 08:37:50 corrado-ll-beta gnome-shell[1844]: #1 5589581f83a0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:172 (12f3f35b6740 @ 127) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2013070 Title: 100% CPU after clicking a mountable in the dock [Attempting to call back into JSAPI ... locations.js:380] Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: I click a mountable volume in the Gnome dock, gnome-shell starts consuming 100% CPU and also it misbehaves: New windows don't show up, if you try to logout via upper-right corner > Log out it doesn't show the log out dialog. Killing it twice restores a working session. I reproduce it on Xorg and Wayland, started with either GDM or SDDM. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 28 08:44:07 2023 DisplayManager: sddm InstallationDate: Installed on 2022-05-16 (315 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (69 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2013070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015059] [NEW] Dead zone below the tray icon area
Public bug reported: Since upgrading to Ubuntu 23.04, I have an issue where the zone below tray icons is partly blocked by some transparent dead zone. With AnyDesk open and its tray icon in the bar, clicking below the tray icon (on a window title for example) triggers the click event on the AnyDesk tray icon, and opens the AnyDesk software. With AnyDesk closed (and the tray icon missing), the dead zone is still present, however clicking on it does nothing. You'll find attached a screenshot showcasing the dead zone (marked in orange, it is invisible), I can't click within this dead zone. When I have a maximized window for example, I can't click on the window buttons. I tried resetting all gnome-related dconf settings after upgrading, to no avail. It worked perfectly fine with Ubuntu 22.10. Here are Gnome-related packages versions I currently have installed: ``` $ dpkg -l | grep gnome rc chrome-gnome-shell 10.1-5 all GNOME Shell extensions integration for web browsers ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator1:44.0-1ubuntu1 amd64GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center1:44.0-1ubuntu4 amd64utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4 all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4 all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1 amd64GNOME keyring services (daemon and tools) ii gnome-keyring-pkcs11:amd64 42.1-1 amd64GNOME keyring module for the PKCS#11 module loading library ii gnome-logs 43.0-1
[Desktop-packages] [Bug 2015061] [NEW] Corrupted/missing windows title background when opening windows
Public bug reported: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re- focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator1:44.0-1ubuntu1 amd64GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center1:44.0-1ubuntu4 amd64utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4 all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4 all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1 amd64GNOME keyring services (daemon and tools) ii gnome-keyring-pkcs11:amd64 42.1-1 amd64GNOME keyring module for the PKCS#11 module loading library ii gnome-logs 43.0-1 amd64viewer for the systemd journal ii gnome-mahjongg
[Desktop-packages] [Bug 2015059] Re: Dead zone below the tray icon area
*** This bug is a duplicate of bug 2012388 *** https://bugs.launchpad.net/bugs/2012388 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2012388, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: gdm3 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid ** This bug has been marked a duplicate of bug 2012388 AnyDesk X11 window is invisible and steals mouse clicks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2015059 Title: Dead zone below the tray icon area Status in Ubuntu: Invalid Bug description: Since upgrading to Ubuntu 23.04, I have an issue where the zone below tray icons is partly blocked by some transparent dead zone. With AnyDesk open and its tray icon in the bar, clicking below the tray icon (on a window title for example) triggers the click event on the AnyDesk tray icon, and opens the AnyDesk software. With AnyDesk closed (and the tray icon missing), the dead zone is still present, however clicking on it does nothing. You'll find attached a screenshot showcasing the dead zone (marked in orange, it is invisible), I can't click within this dead zone. When I have a maximized window for example, I can't click on the window buttons. I tried resetting all gnome-related dconf settings after upgrading, to no avail. It worked perfectly fine with Ubuntu 22.10. Here are Gnome-related packages versions I currently have installed: ``` $ dpkg -l | grep gnome rc chrome-gnome-shell 10.1-5 all GNOME Shell extensions integration for web browsers ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1
[Desktop-packages] [Bug 2012388] Re: AnyDesk X11 window is invisible and steals mouse clicks
** Package changed: gnome-shell (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: AnyDesk X11 window is invisible and steals mouse clicks Status in Ubuntu: Invalid Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2012388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015061] Re: Corrupted/missing windows title background when opening windows
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2015061 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: 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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and m
[Desktop-packages] [Bug 2015061] Re: Corrupted/missing windows title background when opening windows
apport information ** Tags added: apport-collected ** Description changed: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re- focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1 amd64GNOME keyring services (daemon and tools) ii gnome-keyring-pkcs11:amd64 42.1-1 amd64GNOME keyring module for the PKCS#11 module loading library ii gnome-logs 43.0
[Desktop-packages] [Bug 2015061] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660355/+files/GsettingsChanges.txt -- 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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660356/+files/ProcCpuinfoMinimal.txt -- 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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1
[Desktop-packages] [Bug 2015061] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660358/+files/ShellJournal.txt -- 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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660357/+files/ProcEnviron.txt -- 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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660359/+files/monitors.xml.txt -- 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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 1956248] Re: I get two characters in Activities when I press one key for the first key I press...
Also seen on 22.04 LTS running gnome-shell 42.5-0ubuntu1. Seen for the first time today; as noted above, restarting the shell fixes the issue, at least temporarily. -- 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/1956248 Title: I get two characters in Activities when I press one key for the first key I press... Status in Dash to dock: New Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: If I click the Activities in the upper right hand corner of the screen, then do NOT click in the search bar and begin to type, I get two of whatever character I hit. At first I thought it was due to my keyboard wearing out, but it happens on multiple computers, and whatever key I type, even infrequently used ones. If I click in the search bar before I type, then the characters are not duplicated. If I then backspace over the single character that was correctly displayed in the search bar and type another character, that character is doubled. Bounce keys will not eliminate this either. I started noticing doubling characters a couple of weeks (approximately) ago. I didn't start to suspect the real reason until recently. Thanks for working on this for all of us! Rob ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jan 3 11:43:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-19 (990 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-12 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1956248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/2006669 Title: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915]) Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Jammy: Confirmed Status in mesa source package in Kinetic: Confirmed Status in mesa source package in Lunar: Confirmed Bug description: GUI hard lock during zoom session and gnome-terminal kern.log shows a mix of errors __ kernel: [ 3627.948545] Asynchronous wait on fence :00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready [i915]) kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in chrome [5521] kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset due to GPU hang kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled ___ I suspect this issue to be upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755 upstream commit: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217 Reproducer: Although I don't have my own reproducer, the upstream mesa reproducer does trigger a hang on my machine. Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it loads, you will see pikachu. Press "S", he will go back. My whole system freezes from this in Wayland, regardless of the browser. Kernel: 6.0.0-1008-oem Mesa: 22.2.5-0ubuntu0.1~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9 Uname: Linux 6.0.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 21:40:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b1a] Subsystem: Dell Device [1028:0b1a] InstallationDate: Installed on 2022-07-13 (211 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: Dell Inc. Precision 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 03M8N5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-pack
[Desktop-packages] [Bug 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Jammy) Status: New => Confirmed -- 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/2006669 Title: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915]) Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Jammy: Confirmed Status in mesa source package in Kinetic: Confirmed Status in mesa source package in Lunar: Confirmed Bug description: GUI hard lock during zoom session and gnome-terminal kern.log shows a mix of errors __ kernel: [ 3627.948545] Asynchronous wait on fence :00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready [i915]) kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in chrome [5521] kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset due to GPU hang kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled ___ I suspect this issue to be upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755 upstream commit: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217 Reproducer: Although I don't have my own reproducer, the upstream mesa reproducer does trigger a hang on my machine. Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it loads, you will see pikachu. Press "S", he will go back. My whole system freezes from this in Wayland, regardless of the browser. Kernel: 6.0.0-1008-oem Mesa: 22.2.5-0ubuntu0.1~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9 Uname: Linux 6.0.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 21:40:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b1a] Subsystem: Dell Device [1028:0b1a] InstallationDate: Installed on 2022-07-13 (211 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: Dell Inc. Precision 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 03M8N5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006669/+subscriptions -- Mailing list: https://launchpad.net/~deskto
[Desktop-packages] [Bug 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Kinetic) Status: New => Confirmed -- 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/2006669 Title: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915]) Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Jammy: Confirmed Status in mesa source package in Kinetic: Confirmed Status in mesa source package in Lunar: Confirmed Bug description: GUI hard lock during zoom session and gnome-terminal kern.log shows a mix of errors __ kernel: [ 3627.948545] Asynchronous wait on fence :00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready [i915]) kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in chrome [5521] kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset due to GPU hang kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled ___ I suspect this issue to be upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755 upstream commit: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217 Reproducer: Although I don't have my own reproducer, the upstream mesa reproducer does trigger a hang on my machine. Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it loads, you will see pikachu. Press "S", he will go back. My whole system freezes from this in Wayland, regardless of the browser. Kernel: 6.0.0-1008-oem Mesa: 22.2.5-0ubuntu0.1~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9 Uname: Linux 6.0.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 21:40:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b1a] Subsystem: Dell Device [1028:0b1a] InstallationDate: Installed on 2022-07-13 (211 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: Dell Inc. Precision 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 03M8N5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006669/+subscriptions -- Mailing list: https://launchpad.net/~desk
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
Hello, I experienced this issue as well (EOG 42 on Pop!_OS/Ubuntu 22.04 LTS). I just described it here: https://gitlab.gnome.org/GNOME/eog/-/issues/289 I solved the issue by disabling the auto-generated colour profile in the gnome settings. As I said in the description, I can't assess if this issue is related to some specific monitors (I have a ThinkPad T480 monitor), or it's a common problem. ** Bug watch added: gitlab.gnome.org/GNOME/eog/-/issues #289 https://gitlab.gnome.org/GNOME/eog/-/issues/289 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in GNOME Shell: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: 1. Settings > Colour > turn off the toggle switch for your monitor. 2. Restart any affected apps. Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015068] [NEW] /usr/bin/nautilus:11:nautilus_view_model_get_item_from_file:on_clipboard_contents_received:g_task_return_now:complete_in_idle_cb:g_main_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:44~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e82e592c46a293ab04f74131b772ffe3a40a374c 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: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2015068 Title: /usr/bin/nautilus:11:nautilus_view_model_get_item_from_file:on_clipboard_contents_received:g_task_return_now:complete_in_idle_cb:g_main_dispatch Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:44~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e82e592c46a293ab04f74131b772ffe3a40a374c 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/nautilus/+bug/2015068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
Launchpad has imported 8 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=423756. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-07-01T18:07:31+00:00 Idarktemplar wrote: SUMMARY Since cgroup is created in kio after process startup, there is a race condition present if started process forks and starts some children before cgroup creation is processed. Currently, situation sometimes, depending on various circumstances, may be following: 1. kio starts new process via KProcessRunner class. 2. Started process runs and forks, creating one or more children. 3. kio creates new cgroup and puts started process to this new cgroup. All children created by started process stay in current cgroup. STEPS TO REPRODUCE 1. Try starting via KProcessRunner class applications which fork soon after launch. Modern firefox, for example. If application forks and parent exits, it's even better. OBSERVED RESULT Sometimes created cgroup would contain only parent process without any it's children. If parent process quits, it may result even into an empty cgroup. Children of launched process would be left in the cgroup of parent of launched process. Should not be reliably reproducible. EXPECTED RESULT Cgroup should contain both started process and all it's children reliably. ADDITIONAL INFORMATION I did not try reproducing it. Currently, cgroup created when process is already running, and if this process creates some children fast, it may lead to described issue. Here's the link to code: https://invent.kde.org/frameworks/kio/-/blob/8d6b306f585920230acecd19903325f6f0387b8e/src/gui/kprocessrunner.cpp#L226 Function 'registerCGroup()' is called in 'KProcessRunner::slotProcessStarted()' slot, which is invoked after process started, within some undetermined timeframe. In my opinion, proper way to start process in new cgroup in order to fix this issue looks like following: 1. KProcessRunner forks. 2. Fork sets up cgroup, puts itself into it, waits until it's confirmed that OS finished moving it into new cgroup. Optionally between forking and setting up cgroup, it may exec into some helper which would setup cgroup. 3. Fork (or helper used to setup cgroup, if one is used) execs into the new process. Since it's already running in new cgroup before exec, when new process is started it's already contained in new cgroup, and even if first thing it does is fork() call, all children would be contained in that new cgroup as well, without any race conditions. AFAIK, systemd-run actually setups cgroup and reliably puts requested process and all it's children into newly created cgroup, but I might be wrong. Not sure which interfaces are available from systemd via dbus or some library for starting process similarly to systemd-run. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2011806/comments/0 On 2020-07-02T09:56:24+00:00 U26 wrote: There is a theoretical race, yes. The landed patch was a somewhat "lite" and invasive version of introducing the concept. What you describe is how systemd-run does it. But there's a much simpler solution, we can just use startTransientService(execLine) instead of startTransientScope(somePid) then it all becomes someone else's problem. See: https://invent.kde.org/frameworks/kio/-/merge_requests/71 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2011806/comments/1 On 2020-07-04T09:12:11+00:00 Idarktemplar wrote: (In reply to David Edmundson from comment #1) > There is a theoretical race, yes. > > The landed patch was a somewhat "lite" and invasive version of introducing > the concept. > > What you describe is how systemd-run does it. > > But there's a much simpler solution, we can just use > startTransientService(execLine) instead of startTransientScope(somePid) then > it all becomes someone else's problem. > > See: > > https://invent.kde.org/frameworks/kio/-/merge_requests/71 I've looked a bit at this merge request and it looks like it should fix this issue. And it should also allow to implement later something like CgroupV2ProcessRunner for systems with no systemd. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2011806/comments/2 On 2023-03-31T04:56:26+00:00 James Henstridge wrote: We've been seeing reports of problems launching snap applications on the Ubuntu 23.04 development release that seem to relate to this race condition. At first we thought it was only a gnome-shell problem, but some KDE users also encountered the pro
[Desktop-packages] [Bug 2015056] Re: No wallpaper / no option to open the dialog for changing the wallpaper
Installing ```apt-get install gnome-control-center``` resolved the issue. Seems this is removed during the upgrade. -- 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/2015056 Title: No wallpaper / no option to open the dialog for changing the wallpaper Status in gjs package in Ubuntu: New Bug description: # System information: System has upgraded from 22.10 -> 23.04 # How to reproduce 1. start up the computer. No wallpaper visible just black background. 2. right click on desktop "Change background" # Expected result Wallpaper visible / ability to change wallpaper. # output on logfile ``` 2023-04-03T10:16:46.216657+02:00 utopia-Ubuntu gnome-shell[3652]: DING: (gjs:4392): Gjs-CRITICAL **: 10:16:46.213: JS ERROR: TypeError: desktopFile is null 2023-04-03T10:16:46.216882+02:00 utopia-Ubuntu gnome-shell[3652]: DING: _createDesktopBackgroundMenu/<@/usr/share/gnome-shell/extensions/d...@rastersoft.com/desktopManager.js:1114:13 2023-04-03T10:16:46.216971+02:00 utopia-Ubuntu gnome-shell[3652]: DING: @/usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js:206:13 ``` ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gjs 1.76.0-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 10:22:09 2023 InstallationDate: Installed on 2022-11-19 (134 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gjs UpgradeStatus: Upgraded to lunar on 2023-03-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2015056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015071] [NEW] [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem
Public bug reported: broken pipe error 32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 15:39:13 2023 InstallationDate: Installed on 2023-03-12 (21 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Sisäinen äänentoisto - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2015071 Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: broken pipe error 32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 15:39:13 2023 InstallationDate: Installed on 2023-03-12 (21 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Sisäinen äänentoisto - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2015071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015075] [NEW] [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
Public bug reported: pulse audio broken pipe error 32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 16:04:49 2023 InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Sisäinen äänentoisto - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2015075 Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: pulse audio broken pipe error 32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 16:04:49 2023 InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Sisäinen äänentoisto - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2015075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.lau
[Desktop-packages] [Bug 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions
Yeah, I've been looking into this some weeks ago already, but I feel it's something yaru could handle (even though my first attempts were failing) Paul: Main change is that now those frames are gtk4 windows, using a GtkHeaderBar, but I'm not sure how that is different from normal ones. However, gtk inspector can be used with: ❯ pkill -f /usr/libexec/mutter-x11-frames ❯ GTK_DEBUG=interactive /usr/libexec/mutter-x11-frame -- 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/2012733 Title: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions Status in Yaru Theme: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Hi, Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar X1 session: If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish + icons). No issue with GNOME apps (and some other like FF or TB snaps, etc.). Wayland session: all is ok (except many other bugs!) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2012733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2014976] Re: CUPS doesnt work anymore with my HP Printer
** Changed in: cups (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2014976 Title: CUPS doesnt work anymore with my HP Printer Status in cups package in Ubuntu: In Progress Bug description: With 22.10, the autogenerated PPD has much more info inside then with 23.10. My printer needs about 5 Minutes now to start printing and prints only black and white, no colour. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 2 00:57:13 2023 InstallationDate: Installed on 2022-10-13 (170 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: ASUS System Product Name Papersize: a4 PpdFiles: HP_Color_LaserJet_MFP_M280nw_83DB46: HP ColorLaserJet MFP M278-M281, driverless, 2.0b4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (1 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2014976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2014976] Re: CUPS doesnt work anymore with my HP Printer
I was able to reproduce the bug with the IPP printer emulation utility ippeveprinter (package cups-ipp-utils). It is actually 2 bugs: One is that cups-browsed (which automatically creates a CUPS queue for your printer) sends PDF and not Apple Raster to your printer, and your printer is slow on processing the complex PDF format. I have done a fix on the upstream code now that if the destination printer supports both Apple Raster and PDF, the former gets preferred. This way the computer and not the printer renders and rasterizes the PDF input, and the computer has usually a much higher performance for doing this work. Upstream fix in cups-browsed: https://github.com/OpenPrinting/cups-browsed/commit/3eb66da The monochrome output is due to a bug in the PPD file generator for driverless IPP printers. If the printer reports "auto" as default for the color output mode, it selects gray instead of RGB as default. This I have fixed in libppd now: https://github.com/OpenPrinting/libppd/commit/1934a6c341 These fixes will be included in the next uploads of libppd and cups- browsed. ** Changed in: cups (Ubuntu) Importance: Undecided => High ** Package changed: cups (Ubuntu) => cups-browsed (Ubuntu) ** Also affects: libppd (Ubuntu) Importance: Undecided Status: New ** Changed in: libppd (Ubuntu) Status: New => In Progress ** Changed in: libppd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2014976 Title: CUPS doesnt work anymore with my HP Printer Status in cups-browsed package in Ubuntu: In Progress Status in libppd package in Ubuntu: In Progress Bug description: With 22.10, the autogenerated PPD has much more info inside then with 23.10. My printer needs about 5 Minutes now to start printing and prints only black and white, no colour. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 2 00:57:13 2023 InstallationDate: Installed on 2022-10-13 (170 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: ASUS System Product Name Papersize: a4 PpdFiles: HP_Color_LaserJet_MFP_M280nw_83DB46: HP ColorLaserJet MFP M278-M281, driverless, 2.0b4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (1 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2014976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011837] Re: Nvidia with Wayland or Xorg issue
apport information ** Tags added: apport-collected ** Description changed: I will summarize here what I put at https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6 On Ubuntu 23.04, if I install it, it works fine but there is a considerable lag for everything. This is when using Wayland. If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt. If I do put in on xorg, then an image I posted on the 1st link happens and it stays there, does not matter if I change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back). The hardware that I was using for testing is: CPU - 13900k MOBO - Asus Z790 Hero RAM: DDR5 128GB VID: Nvidia 4090 (Drivers were automatically installed during setup) SSD - SN850x It is a computer just for Ubuntu 23.04 testing right now. + --- + ProblemType: Bug + ApportVersion: 2.26.0-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: pass + CasperVersion: 1.480 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 23.04 + LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: gnome-shell 44.0-2ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + LANG=C.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= + ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 + RelatedPackageVersions: mutter-common 44.0-2ubuntu2 + Tags: lunar + Uname: Linux 6.2.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2011837/+attachment/5660469/+files/Dependencies.txt -- 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/2011837 Title: Nvidia with Wayland or Xorg issue Status in gnome-shell package in Ubuntu: Incomplete Bug description: I will summarize here what I put at https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6 On Ubuntu 23.04, if I install it, it works fine but there is a considerable lag for everything. This is when using Wayland. If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt. If I do put in on xorg, then an image I posted on the 1st link happens and it stays there, does not matter if I change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back). The hardware that I was using for testing is: CPU - 13900k MOBO - Asus Z790 Hero RAM: DDR5 128GB VID: Nvidia 4090 (Drivers were automatically installed during setup) SSD - SN850x It is a computer just for Ubuntu 23.04 testing right now. --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 44.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Tags: lunar Uname: Linux 6.2.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sud
[Desktop-packages] [Bug 2011837] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/2011837/+attachment/5660470/+files/GsettingsChanges.txt -- 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/2011837 Title: Nvidia with Wayland or Xorg issue Status in gnome-shell package in Ubuntu: Incomplete Bug description: I will summarize here what I put at https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6 On Ubuntu 23.04, if I install it, it works fine but there is a considerable lag for everything. This is when using Wayland. If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt. If I do put in on xorg, then an image I posted on the 1st link happens and it stays there, does not matter if I change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back). The hardware that I was using for testing is: CPU - 13900k MOBO - Asus Z790 Hero RAM: DDR5 128GB VID: Nvidia 4090 (Drivers were automatically installed during setup) SSD - SN850x It is a computer just for Ubuntu 23.04 testing right now. --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 44.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Tags: lunar Uname: Linux 6.2.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011837] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2011837/+attachment/5660471/+files/ProcCpuinfoMinimal.txt -- 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/2011837 Title: Nvidia with Wayland or Xorg issue Status in gnome-shell package in Ubuntu: Incomplete Bug description: I will summarize here what I put at https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6 On Ubuntu 23.04, if I install it, it works fine but there is a considerable lag for everything. This is when using Wayland. If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt. If I do put in on xorg, then an image I posted on the 1st link happens and it stays there, does not matter if I change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back). The hardware that I was using for testing is: CPU - 13900k MOBO - Asus Z790 Hero RAM: DDR5 128GB VID: Nvidia 4090 (Drivers were automatically installed during setup) SSD - SN850x It is a computer just for Ubuntu 23.04 testing right now. --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 44.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Tags: lunar Uname: Linux 6.2.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011837] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/2011837/+attachment/5660472/+files/ShellJournal.txt -- 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/2011837 Title: Nvidia with Wayland or Xorg issue Status in gnome-shell package in Ubuntu: Incomplete Bug description: I will summarize here what I put at https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6 On Ubuntu 23.04, if I install it, it works fine but there is a considerable lag for everything. This is when using Wayland. If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt. If I do put in on xorg, then an image I posted on the 1st link happens and it stays there, does not matter if I change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back). The hardware that I was using for testing is: CPU - 13900k MOBO - Asus Z790 Hero RAM: DDR5 128GB VID: Nvidia 4090 (Drivers were automatically installed during setup) SSD - SN850x It is a computer just for Ubuntu 23.04 testing right now. --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 44.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Tags: lunar Uname: Linux 6.2.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011837] Re: Nvidia with Wayland or Xorg issue
Hi Daniel, I think I am done, is there anything else? Motherboard, RAM type, Video card? -- 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/2011837 Title: Nvidia with Wayland or Xorg issue Status in gnome-shell package in Ubuntu: Incomplete Bug description: I will summarize here what I put at https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6 On Ubuntu 23.04, if I install it, it works fine but there is a considerable lag for everything. This is when using Wayland. If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt. If I do put in on xorg, then an image I posted on the 1st link happens and it stays there, does not matter if I change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back). The hardware that I was using for testing is: CPU - 13900k MOBO - Asus Z790 Hero RAM: DDR5 128GB VID: Nvidia 4090 (Drivers were automatically installed during setup) SSD - SN850x It is a computer just for Ubuntu 23.04 testing right now. --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 44.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Tags: lunar Uname: Linux 6.2.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1594085] Re: Software app very slow to fully start up
i have also facing the same issue on my client's site: https://www.pikashowhd.com/pikashow-for-pc/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1594085 Title: Software app very slow to fully start up Status in gnome-software package in Ubuntu: Triaged Bug description: This is follow-up for bug 1592678 which more or less requests that gnome-software not run a background service. 1. From a terminal, run pkill gnome-software to kill the background service. 2. Start the Software app and click one of the apps on the front page to see more info about it. What happens In my testing on a Ubuntu 16.04 Live DVD in VirtualBox with a traditional non-SSD hard drive and 1.5 GB allocated RAM (admittedly not the speediest environment), it took 90 seconds for that info page to load! Once that page is loaded, browsing to other pages doesn't take long at all. Or if you just wait 2 minutes first then it's not that slow either. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13 Uname: Linux 4.4.0-25-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jun 19 04:59:00 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-09 (70 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1594085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions
Looking better I think there are two bugs, one is in mutter the other is in yaru where the look of these decorations isn't fully themed to be consistent with others. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Won't Fix ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress ** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Triaged ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Medium ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: yaru-theme (Ubuntu) Status: Triaged => In Progress -- 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/2012733 Title: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions Status in Yaru Theme: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: In Progress Bug description: Hi, Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar X1 session: If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish + icons). No issue with GNOME apps (and some other like FF or TB snaps, etc.). Wayland session: all is ok (except many other bugs!) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2012733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817785] Re: installation of texlive-latex-base-doc does not make the documentation available to 'texdoc'
This is affecting me in Ubuntu 22.10, upgraded from 22.04 LTS. I also found the Stack Exchange question linked above. The `dpkg-recognfigure` command did not work for me, but `sudo mktexlsr /usr/share/doc/texlive- doc` did work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1817785 Title: installation of texlive-latex-base-doc does not make the documentation available to 'texdoc' Status in texlive-base package in Ubuntu: Confirmed Bug description: I had texlive installed previously, on a freshly installed 18.04 system. Now I installed texlive-latex-base-doc. after installation, texdoc did not find the requested documentation, e.g. $texdoc amsldoc Sorry, no documentation found for amsldoc. Only after executing 'dpkg-reconfigure texlive-base' the documentation was found. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: texlive-latex-base-doc (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 26 20:56:05 2019 InstallationDate: Installed on 2014-08-28 (1643 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) SourcePackage: texlive-base UpgradeStatus: Upgraded to bionic on 2018-08-14 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1817785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2014957] Re: XP Pen 13 tablet has swapped axes for input
filed upstream as https://gitlab.freedesktop.org/libinput/libinput/-/issues/886 ** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #886 https://gitlab.freedesktop.org/libinput/libinput/-/issues/886 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/2014957 Title: XP Pen 13 tablet has swapped axes for input Status in libinput package in Ubuntu: New Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: On jammy, an XP Pen 13 tablet (shown in the hardware as "UGTABLET 11.6 inch PenDisplay") is unusable because the axes for the stylus are swapped: moving the stylus up on the screen moves the cursor to the left, moving it down moves it right, moving the stylus to the left moves the cursor up, moving it to the right moves the cursor down. I am reporting this bug initially against Xorg, but the problem is present using either Xorg or Wayland. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-core 2:21.1.3-2ubuntu2.9 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 1 02:12:10 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2023-01-22 (68 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c415e6a8-5cd2-4d08-913d-14c00b792374 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.release: 2.57 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:br2.57:efr1.13:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2306: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2014957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015124] [NEW] xorg drivers
Public bug reported: xorg HP monitor screen and logitech keyboard and hyperx mouse ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Lupa evätty: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 21:58:00 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: MSI MS-7817 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=7937a7b0-31fc-4dec-b3c2-51df4e876c20 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.1~kisak1~j version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy third-party-packages ubuntu wayland-session ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015124 Title: xorg drivers Status in xorg package in Ubuntu: Incomplete Bug description: xorg HP monitor screen and logitech keyboard and hyperx mouse ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Lupa evätty: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 21:58:00 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: MSI MS-7817 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=7937a7b0-31fc-4dec-b3c2-51df4e876c20 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:s
[Desktop-packages] [Bug 2015075] Re: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2015075 Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all Status in pulseaudio package in Ubuntu: Incomplete Bug description: pulse audio broken pipe error 32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 16:04:49 2023 InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Sisäinen äänentoisto - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2015075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015071] Re: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem
** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/2015071 Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: Incomplete Bug description: broken pipe error 32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 15:39:13 2023 InstallationDate: Installed on 2023-03-12 (21 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Sisäinen äänentoisto - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2015071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862549] Re: memory leak when annotating PDFs
** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #1010 https://gitlab.gnome.org/GNOME/evince/-/issues/1010 ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/-/issues/1010 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1862549 Title: memory leak when annotating PDFs Status in Evince: Unknown Status in evince package in Ubuntu: Confirmed Bug description: When annotating PDFs or scrolling through larger PDFs that contain lots of annotations, evince claims a large amount of memory and never releases it. This becomes especially apparent when using the highlight feature, i.e. highlighting various parts of the text on the PDF. On a 12-page PDF, not annotated, evince used about 35 MB of RAM and claimed an additional 30 as soon as I used the highlight feature the first time, then this repeats with about the same amount or more for each additional highlight. The interface starts to lag visibly the more memory is allocated. Occasionally, the memory usage goes down by a few percent when scrolling, but it tends to allocate more and more memory until the system runs out of memory. Using the same 12-page PDF with about 100 highlighted lines and quickly scrolling through the document multiple times, evince reached about 6 GB of memory usage in less than one minute. This issue also makes closing documents very slow, taking about 5 to 10 seconds for each gigabyte of memory allocated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.34.1-1build1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 23:13:02 2020 InstallationDate: Installed on 2020-01-30 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1862549/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions
Mutter issue is handled in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2948 Yaru changes in https://github.com/ubuntu/yaru/pull/3884 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012733 Title: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions Status in Yaru Theme: Unknown Status in mutter package in Ubuntu: Fix Committed Status in yaru-theme package in Ubuntu: In Progress Bug description: Hi, Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar X1 session: If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish + icons). No issue with GNOME apps (and some other like FF or TB snaps, etc.). Wayland session: all is ok (except many other bugs!) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2012733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862549] Re: memory leak when annotating PDFs
** Changed in: evince Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1862549 Title: memory leak when annotating PDFs Status in Evince: New Status in evince package in Ubuntu: Confirmed Bug description: When annotating PDFs or scrolling through larger PDFs that contain lots of annotations, evince claims a large amount of memory and never releases it. This becomes especially apparent when using the highlight feature, i.e. highlighting various parts of the text on the PDF. On a 12-page PDF, not annotated, evince used about 35 MB of RAM and claimed an additional 30 as soon as I used the highlight feature the first time, then this repeats with about the same amount or more for each additional highlight. The interface starts to lag visibly the more memory is allocated. Occasionally, the memory usage goes down by a few percent when scrolling, but it tends to allocate more and more memory until the system runs out of memory. Using the same 12-page PDF with about 100 highlighted lines and quickly scrolling through the document multiple times, evince reached about 6 GB of memory usage in less than one minute. This issue also makes closing documents very slow, taking about 5 to 10 seconds for each gigabyte of memory allocated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.34.1-1build1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 23:13:02 2020 InstallationDate: Installed on 2020-01-30 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1862549/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015129] [NEW] gstreamer 1.22.1 bugfix release
Public bug reported: Impact -- This is a stable bugfix release See https://gstreamer.freedesktop.org/releases/1.22/#1.22.1 for more details. ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: Triaged ** Tags: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015129 Title: gstreamer 1.22.1 bugfix release Status in gstreamer1.0 package in Ubuntu: Triaged Bug description: Impact -- This is a stable bugfix release See https://gstreamer.freedesktop.org/releases/1.22/#1.22.1 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2015129/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015129] Re: gstreamer 1.22.1 bugfix release
** Also affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gst-plugins-bad1.0 (Ubuntu) Status: New => Triaged ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => Triaged ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: New => Triaged ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015129 Title: gstreamer 1.22.1 bugfix release Status in gst-plugins-bad1.0 package in Ubuntu: Triaged Status in gst-plugins-base1.0 package in Ubuntu: Triaged Status in gst-plugins-good1.0 package in Ubuntu: Triaged Status in gstreamer1.0 package in Ubuntu: Triaged Bug description: Impact -- This is a stable bugfix release See https://gstreamer.freedesktop.org/releases/1.22/#1.22.1 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2015129/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999201] Re: right click on file/folder icon shows broken menu
I resolved the issue. It appeared to be graphics driver related. I have updated to the latest MESA git from the oibaf PPA and now the issue is gone. -- 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/1999201 Title: right click on file/folder icon shows broken menu Status in nautilus package in Ubuntu: Confirmed Bug description: Hi, Ubuntu 22.10 here Open Nautilus. Right click on any file or folder. Often shows a visually and functionally broken menu, where some items are hidden / overlapped by others. And those items can't be triggered. Screenshot attached. ( that screenshot may also serve to show a gnome-screenshot bug which is unable to correctly capture mouse cursor, see https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1989295 ) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-27 (43 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Package: nautilus 1:43.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: wayland-session kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-27 (44 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Package: nautilus 1:43.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1999201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013469] gnome-shell crashed with SIGSEGV in g_object_unref()
*** This bug is a duplicate of bug 1974293 *** https://bugs.launchpad.net/bugs/1974293 StacktraceTop: js::gc::Cell::storeBuffer (this=, this=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/Cell.h:357 js::gc::PostWriteBarrierImpl (next=, prev=, cellp=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:646 js::gc::PostWriteBarrier (next=, prev=, vp=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:658 js::InternalBarrierMethods::postBarrier (next=, prev=, vp=0x56552ed00d10) at /usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:350 js::InternalBarrierMethods::postBarrier (vp=0x56552ed00d10, prev=, next=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:349 -- 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/2013469 Title: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer() Status in gnome-shell package in Ubuntu: New Bug description: Double click on a partition listed in ubuntu dock. Partition does not open but system hang. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 09:42:01 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-02-25 (34 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-102.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013469] StacktraceSource.txt
*** This bug is a duplicate of bug 1974293 *** https://bugs.launchpad.net/bugs/1974293 ** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/2013469/+attachment/5660608/+files/StacktraceSource.txt -- 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/2013469 Title: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer() Status in gnome-shell package in Ubuntu: New Bug description: Double click on a partition listed in ubuntu dock. Partition does not open but system hang. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 09:42:01 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-02-25 (34 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-102.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013469] Stacktrace.txt
*** This bug is a duplicate of bug 1974293 *** https://bugs.launchpad.net/bugs/1974293 ** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2013469/+attachment/5660607/+files/Stacktrace.txt -- 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/2013469 Title: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer() Status in gnome-shell package in Ubuntu: New Bug description: Double click on a partition listed in ubuntu dock. Partition does not open but system hang. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 09:42:01 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-02-25 (34 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-102.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013469] ThreadStacktrace.txt
*** This bug is a duplicate of bug 1974293 *** https://bugs.launchpad.net/bugs/1974293 ** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2013469/+attachment/5660609/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2013469/+attachment/5659433/+files/CoreDump.gz ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Summary changed: - gnome-shell crashed with SIGSEGV in g_object_unref() + gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer() -- 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/2013469 Title: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer() Status in gnome-shell package in Ubuntu: New Bug description: Double click on a partition listed in ubuntu dock. Partition does not open but system hang. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 09:42:01 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-02-25 (34 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-102.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015135] [NEW] hewlett packard xorg slow
Public bug reported: hewlett packard xorg slow reboot and restart xorg updates hewlett packard monitor screen and keyboard and mouse hyperX ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Lupa evätty: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 00:50:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] InstallationDate: Installed on 2023-03-11 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Hewlett-Packard HP Compaq 6000 Pro MT PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3a5032f6-26b3-4d7d-9b50-c35b2460dffe ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2009 dmi.bios.release: 1.9 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G2 v01.09 dmi.board.asset.tag: CZC0195QPD dmi.board.name: 3048h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC0195QPD dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G2v01.09:bd08/25/2009:br1.9:svnHewlett-Packard:pnHPCompaq6000ProMTPC:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct6:cvr:skuVN784ET#UUW: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 6000 Pro MT PC dmi.product.sku: VN784ET#UUW dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.1~kisak1~j version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy third-party-packages ubuntu wayland-session ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015135 Title: hewlett packard xorg slow Status in xorg package in Ubuntu: Incomplete Bug description: hewlett packard xorg slow reboot and restart xorg updates hewlett packard monitor screen and keyboard and mouse hyperX ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Lupa evätty: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 00:50:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] InstallationDate: Installed on 2023-03-11 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Hewlett-Packard HP Compaq 6000 Pro MT PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3a5032f6-26b3-4d7d-9b50-c35b2460dffe ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2009 dmi.bios.release: 1.9 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G2 v01.09 dmi.board.asset.tag: CZC0195QPD dmi.board.name: 3048h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC0195QPD dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G2v01.09:bd08/25/2009:br1.9:svnHewlett-Packard:pnHPCompaq6000ProMTPC:pvr:rvnHewl
[Desktop-packages] [Bug 2015134] [NEW] libdmapsharing with 3.0 API is incompatible with libsoup3
Public bug reported: The version of the libdmapsharing API found in the libdmapsharing packages shipped by Ubuntu is obsolete, and the versions of libdmapsharing that provide it are incompatible with libsoup3. Since more applications are requiring libsoup3, and libsoup3 cannot exist with libsoup2 in the same process, Ubuntu should move to libdmapsharing-3.9.12+ in its upcoming release. Libdmapsharing-3.9.12+ makes use of libsoup3. The packages that use libdmapsharing include Rhythmbox and grilo-plugins, and both recently moved to libsoup3: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1996 https://gitlab.gnome.org/GNOME/grilo-plugins/-/commit/ae34da2264eab49eceaeeb0d1510b952a65ae030 The 3.9 series of libdmapsharing is available at: https://www.flyn.org/projects/libdmapsharing/ ** Affects: libdmapsharing (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libdmapsharing in Ubuntu. https://bugs.launchpad.net/bugs/2015134 Title: libdmapsharing with 3.0 API is incompatible with libsoup3 Status in libdmapsharing package in Ubuntu: New Bug description: The version of the libdmapsharing API found in the libdmapsharing packages shipped by Ubuntu is obsolete, and the versions of libdmapsharing that provide it are incompatible with libsoup3. Since more applications are requiring libsoup3, and libsoup3 cannot exist with libsoup2 in the same process, Ubuntu should move to libdmapsharing-3.9.12+ in its upcoming release. Libdmapsharing-3.9.12+ makes use of libsoup3. The packages that use libdmapsharing include Rhythmbox and grilo-plugins, and both recently moved to libsoup3: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1996 https://gitlab.gnome.org/GNOME/grilo-plugins/-/commit/ae34da2264eab49eceaeeb0d1510b952a65ae030 The 3.9 series of libdmapsharing is available at: https://www.flyn.org/projects/libdmapsharing/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdmapsharing/+bug/2015134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2014141] ThreadStacktrace.txt
*** This bug is a duplicate of bug 2012974 *** https://bugs.launchpad.net/bugs/2012974 ** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2014141/+attachment/5660639/+files/ThreadStacktrace.txt ** Tags added: apport-failed-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2014141 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: Trying to reproduce bug 2013469 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 21:16:41 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1679944760 InstallationDate: Installed on 2023-03-31 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/corrado ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7fd10e690ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffd4ee4dce0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2014141] gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 2012974 *** https://bugs.launchpad.net/bugs/2012974 Stacktrace: #0 0x7fd10e690ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffd4ee4dce0 StacktraceSource: #0 0x7fd10e690ffb in ?? () StacktraceTop: ?? () -- 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/2014141 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: Trying to reproduce bug 2013469 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 21:16:41 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1679944760 InstallationDate: Installed on 2023-03-31 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/corrado ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7fd10e690ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffd4ee4dce0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015006] gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 2012974 *** https://bugs.launchpad.net/bugs/2012974 Stacktrace: #0 0x7f053fa90ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffe4d747b20 StacktraceSource: #0 0x7f053fa90ffb in ?? () StacktraceTop: ?? () -- 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/2015006 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: just started, only firefox active ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 2 12:00:37 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-04-02 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230402) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f053fa90ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffe4d747b20 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015006] ThreadStacktrace.txt
*** This bug is a duplicate of bug 2012974 *** https://bugs.launchpad.net/bugs/2012974 ** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2015006/+attachment/5660680/+files/ThreadStacktrace.txt ** Tags added: apport-failed-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2015006 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: just started, only firefox active ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 2 12:00:37 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-04-02 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230402) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f053fa90ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffe4d747b20 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015013] gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 2012974 *** https://bugs.launchpad.net/bugs/2012974 Stacktrace: #0 0x7f7cc8c90ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffcb2a427e0 StacktraceSource: #0 0x7f7cc8c90ffb in ?? () StacktraceTop: ?? () -- 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/2015013 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: unexpected crashed when relogin ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 06:15:24 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-06-25 (1011 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f7cc8c90ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffcb2a427e0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: Upgraded to lunar on 2022-09-30 (184 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015013] ThreadStacktrace.txt
*** This bug is a duplicate of bug 2012974 *** https://bugs.launchpad.net/bugs/2012974 ** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2015013/+attachment/5660689/+files/ThreadStacktrace.txt ** Tags added: apport-failed-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2015013 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: unexpected crashed when relogin ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 06:15:24 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-06-25 (1011 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f7cc8c90ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffcb2a427e0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: Upgraded to lunar on 2022-09-30 (184 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015006] ThreadStacktrace.txt
*** This bug is a duplicate of bug 2012974 *** https://bugs.launchpad.net/bugs/2012974 ** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2015006/+attachment/5660688/+files/ThreadStacktrace.txt -- 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/2015006 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: just started, only firefox active ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 2 12:00:37 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-04-02 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230402) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f053fa90ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffe4d747b20 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015006] gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 2012974 *** https://bugs.launchpad.net/bugs/2012974 Stacktrace: #0 0x7f053fa90ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffe4d747b20 StacktraceSource: #0 0x7f053fa90ffb in ?? () StacktraceTop: ?? () -- 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/2015006 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: just started, only firefox active ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 2 12:00:37 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-04-02 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230402) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f053fa90ffb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffe4d747b20 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
I was also able to recreate this today using the ubuntu-desktop-legacy- amd64 image with serial 20230403. I neglected to check the 'ubuntu- drivers install' in the live environment but will run through the process again. bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ ubuntu-drivers devices == /sys/devices/pci:00/:00:02.4/:05:00.0 == modalias : pci:v14E4d43B1sv1043sd85BAbc02sc80i00 vendor : Broadcom Inc. and subsidiaries model: BCM4352 802.11ac Wireless Network Adapter driver : broadcom-sta-dkms - distro non-free bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ ubuntu-drivers list broadcom-sta-dkms, (kernel modules provided by broadcom-sta-dkms) bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ apt-cache policy broadcom-sta-dkms broadcom-sta-dkms: Installed: (none) Candidate: 6.30.223.271-23ubuntu1 Version table: 6.30.223.271-23ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/restricted amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu lunar/restricted i386 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
In a live session 'ubuntu-drivers install' indicates that "All the available drivers are already installed". Additionally, the bcma kernel module is loaded and used by my broadcom device. However, no wireless device is currently available and the "Additional Drivers" section of software-properties-gtk is somewhat confusing because the two radio buttons say "Using dkms..." and "Do not use device" but "Do not use device" is selected. (I wouldn't expect the words "Using" if it isn't being used.) Using software-properties-gtk to install the additional drivers did not end up allowing the wireless device to be available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
> I can enable that successfully from the live session but > wireless networks are not available in network manager This is expected if SecureBoot is enabled on your system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013267] Re: GNOME Maps silently fails to launch under Ubuntu MATE Lunar Beta
This bug was fixed in the package librest - 0.9.1-6 --- librest (0.9.1-6) unstable; urgency=medium * Build-Depend on dh-sequence-gir to fix missing dependencies from the gir packages (Closes: #1033715) (LP: #2013267) -- Jeremy Bicha Thu, 30 Mar 2023 15:52:01 -0400 ** Changed in: librest (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librest in Ubuntu. https://bugs.launchpad.net/bugs/2013267 Title: GNOME Maps silently fails to launch under Ubuntu MATE Lunar Beta Status in gnome-maps package in Ubuntu: Invalid Status in librest package in Ubuntu: Fix Released Status in librest package in Debian: Fix Released Bug description: Steps to reproduce: 1. Boot the Ubuntu MATE Lunar Beta ISO, and click "Try Ubuntu MATE". 2. Open the application menu, and search for "Maps". 3. Click "Maps". Expected result: GNOME Maps should open. Actual result: Nothing happens. Additional info: Attempting to launch GNOME Maps from the terminal results in this: ** (org.gnome.Maps:8037): WARNING **: 05:06:41.954: Failed to load shared library 'librest-1.0.so.0' referenced by the typelib: librest-1.0.so.0: cannot open shared object file: No such file or directory (org.gnome.Maps:8037): Gjs-Console-CRITICAL **: 05:06:41.955: Error: Unsupported type void, deriving from fundamental void @resource:///org/gnome/Maps/js/osmOAuthProxyCall.js:25:8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-maps/+bug/2013267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken
This bug was fixed in the package ibus - 1.5.28-3 --- ibus (1.5.28-3) experimental; urgency=medium * Team upload * Fix broken code point feature (LP: #2012788) - d/p/src-Call-IBUS_TYPE_EMOJI_DATA-in-ibus_init.patch -- Gunnar Hjalmarsson Wed, 29 Mar 2023 16:38:51 +0200 ** Changed in: ibus (Ubuntu) Status: In Progress => Fix Released -- 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/2012788 Title: Entering Unicode characters with code points broken Status in ibus: Fix Released Status in ibus package in Ubuntu: Fix Released Bug description: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2012788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2014957] Re: XP Pen 13 tablet has swapped axes for input
** Also affects: libinput via https://gitlab.freedesktop.org/libinput/libinput/-/issues/886 Importance: Unknown Status: Unknown ** No longer affects: xserver-xorg-input-libinput (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/2014957 Title: XP Pen 13 tablet has swapped axes for input Status in libinput: Unknown Status in libinput package in Ubuntu: New Bug description: On jammy, an XP Pen 13 tablet (shown in the hardware as "UGTABLET 11.6 inch PenDisplay") is unusable because the axes for the stylus are swapped: moving the stylus up on the screen moves the cursor to the left, moving it down moves it right, moving the stylus to the left moves the cursor up, moving it to the right moves the cursor down. I am reporting this bug initially against Xorg, but the problem is present using either Xorg or Wayland. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-core 2:21.1.3-2ubuntu2.9 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 1 02:12:10 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2023-01-22 (68 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c415e6a8-5cd2-4d08-913d-14c00b792374 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.release: 2.57 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:br2.57:efr1.13:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2306: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/2014957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Milestone: None => ubuntu-23.04 -- 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/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: New Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mozjs102 package in Ubuntu: Confirmed Status in mozjs91 package in Ubuntu: Confirmed Status in gnome-shell package in Fedora: Confirmed Bug description: https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
On Mon, Apr 03, 2023 at 06:57:36AM -, Ralf Dünkelmann wrote: > the bug (https://bugs.launchpad.net/bugs/2013453), that nem000 created > was marked as a duplicate of this one. This is the case for most of the > related bugs listed here. So it seems that this here is the issue to go > ahead with? Heh, yeah, I'as surprised, I figured keeping newer implementations of this flaw separate from the older ones would have been the thing to do. FWIW I've been handing out the "the only safe thing to do is to lock your workstation before you walk away from it / suspend it" as advice for twenty years... Thanks -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: New Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015040] Re: gnome-shell crashed with SIGTRAP in XFlush() from meta_cursor_renderer_x11_update_cursor() from meta_cursor_renderer_update_cursor() from meta_cursor_renderer_forc
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 ** Summary changed: - /usr/bin/gnome-shell:5:XFlush:meta_cursor_renderer_x11_update_cursor:meta_cursor_renderer_update_cursor:meta_cursor_renderer_force_update:update_cursors + gnome-shell crashed with SIGTRAP in XFlush() from meta_cursor_renderer_x11_update_cursor() from meta_cursor_renderer_update_cursor() from meta_cursor_renderer_force_update() from update_cursors() -- 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/2015040 Title: gnome-shell crashed with SIGTRAP in XFlush() from meta_cursor_renderer_x11_update_cursor() from meta_cursor_renderer_update_cursor() from meta_cursor_renderer_force_update() from update_cursors() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/cd7e4f922cf2eed2f52eb9887d5413fe137c3de0 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/2015040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991901] Re: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
This is still appearing in so many peoples' logs that it misleads you into thinking it's the cause of whatever crash happens after it. ** Tags added: 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/1991901 Title: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available Status in gnome-shell package in Ubuntu: Confirmed Bug description: This error is too noisy and also not an error. Many systems and most desktops won't have fingerprint devices. JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2580 https://gitlab.gnome.org/GNOME/mutter/-/issues/2580 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2580 Importance: Unknown Status: Unknown -- 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/2012733 Title: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions Status in Mutter: Unknown Status in Yaru Theme: Unknown Status in mutter package in Ubuntu: Fix Committed Status in yaru-theme package in Ubuntu: In Progress Bug description: Hi, Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar X1 session: If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish + icons). No issue with GNOME apps (and some other like FF or TB snaps, etc.). Wayland session: all is ok (except many other bugs!) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
** Also affects: eog via https://gitlab.gnome.org/GNOME/eog/-/issues/289 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in Eye of GNOME: Unknown Status in GNOME Shell: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: 1. Settings > Colour > turn off the toggle switch for your monitor. 2. Restart any affected apps. Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1199409] Re: Xrandr twitches when using DVI-VGA adapter via triple AMD card setup
Other individuals wear them merely for fun, as a means to feel more confident and powerful about their sexuality. https://allmyneed.online/ -- 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/1199409 Title: Xrandr twitches when using DVI-VGA adapter via triple AMD card setup Status in xserver-xorg-video-ati package in Ubuntu: Triaged Bug description: What I expected to happen is a normal picture on all four of my monitors. What happened instead xrandr will twitch when using a DVI-VGA adapter via ubuntu 12.04-14.04: lspci | grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4250] 02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV610 [Radeon HD 2400 PRO] 06:06.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV250/M9 GL [Mobility FireGL 9000/Radeon 9000] (rev 02) fglrx-* in Precise did not recognize all my cards so I was unable to test it. The IGP is connected via DVI to a 24" monitor and via VGA to a 17" monitor, all good so far. Then I have three monitors left, two 15" VGA and one 17" vga, so to use all monitors, I have to use one DVI-VGA adapter. No matter in what order/combination I connect the monitors to the video cards, the monitor that is connected via the adapter always flickers along with the other monitor on that same card (does not matter which card). It seems like the two monitors have two sperate framebuffers, but by default they both show the framebuffer for the monitor with adapter, but when I move the mouse they switch rapidly from that framebuffer to the other and back. Here are three video's showing the problem: http://www.youtube.com/watch?v=tQiJADHGuZg (Top-Right monitor connected via adapter, in the same card as Bottom-Right) http://www.youtube.com/watch?v=lk9muK8f06c (Top-Left monitor connected via adapter, in the same card as Bottom-Right) http://www.youtube.com/watch?v=6Ses1jUcu2k (Top-Left monitor connected via adapter, in the same card as Top-Right) I think it's a xrandr problem because using the same setup with zaphodhead mode and xinerama, it works but its EXTREMELY slow. I have already tried another DVI-VGA adapter, but with the same results. Another strange thing is that xrandr seems to think that two monitors are clones, but one of which is not connected. xrandr --verbose log: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1199409/+attachment/3944844/+files/xrandr%20--verbose I have cut out the various supported modes, the full xrandr --verbose output is attached. As you see, VGA-2 and DVI-1 apparently are clones, but in this case only VGA-2 is connected, I don't know if that is normal. I now have connected two monitors (both 15") to VGA-2 and DVI-1, and the xrandr output has not changed, it still shows VGA-2 and DVI-1 as cloned, but the two displays still twitch as in the video's... --- .tmp.unity.support.test.0: ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.336ubuntu1 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: No LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140105) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: xorg 1:7.7+1ubuntu7 PackageArchitecture: amd64 ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Tags: third-party-packages trusty ubuntu reproducible compiz-0.9 Uname: Linux 3.12.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 880GMH/USB3. dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd12/06/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn880GMH/USB3.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: l
[Desktop-packages] [Bug 2015135] Re: hewlett packard xorg slow
Thanks for the bug report. Unfortunately some of your graphics packages are from an unsupported PPA 'kisak' and so we cannot accept bug reports from the machine while that is installed. Please uninstall the 'kisak' PPA from the machine and continue to report new bugs about each problem you encounter. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015135 Title: hewlett packard xorg slow Status in Ubuntu: Invalid Bug description: hewlett packard xorg slow reboot and restart xorg updates hewlett packard monitor screen and keyboard and mouse hyperX ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Lupa evätty: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 00:50:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] InstallationDate: Installed on 2023-03-11 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Hewlett-Packard HP Compaq 6000 Pro MT PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3a5032f6-26b3-4d7d-9b50-c35b2460dffe ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2009 dmi.bios.release: 1.9 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G2 v01.09 dmi.board.asset.tag: CZC0195QPD dmi.board.name: 3048h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC0195QPD dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G2v01.09:bd08/25/2009:br1.9:svnHewlett-Packard:pnHPCompaq6000ProMTPC:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct6:cvr:skuVN784ET#UUW: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 6000 Pro MT PC dmi.product.sku: VN784ET#UUW dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.1~kisak1~j version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2015135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015124] Re: xorg drivers
Thanks for the bug report. Please: 1. Remove the unsupported 'kisak' PPA from the machine. 2. Open new bugs about any remaining problems you encounter. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015124 Title: xorg drivers Status in Ubuntu: Invalid Bug description: xorg HP monitor screen and logitech keyboard and hyperx mouse ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Lupa evätty: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 21:58:00 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: MSI MS-7817 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=7937a7b0-31fc-4dec-b3c2-51df4e876c20 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.1~kisak1~j version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2015124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011837] Re: Nvidia with Wayland or Xorg issue
Thanks. Yes please run: lspci -k > lspcik.txt journalctl -b0 > journal.txt and attach the resulting text files here. Without that information I can only guess that the problem is you're using the default 'nouveau' driver which won't support the NVIDIA RTX 4090 properly. To fix that, please open the 'Additional Drivers' app and use it to choose a recent NVIDIA driver. -- 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/2011837 Title: Nvidia with Wayland or Xorg issue Status in gnome-shell package in Ubuntu: Incomplete Bug description: I will summarize here what I put at https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6 On Ubuntu 23.04, if I install it, it works fine but there is a considerable lag for everything. This is when using Wayland. If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt. If I do put in on xorg, then an image I posted on the 1st link happens and it stays there, does not matter if I change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back). The hardware that I was using for testing is: CPU - 13900k MOBO - Asus Z790 Hero RAM: DDR5 128GB VID: Nvidia 4090 (Drivers were automatically installed during setup) SSD - SN850x It is a computer just for Ubuntu 23.04 testing right now. --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 44.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Tags: lunar Uname: Linux 6.2.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Your log shows you are also experiencing bug 2014986 so please subscribe to that too. -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1 amd64
[Desktop-packages] [Bug 2015061] Re: Corrupted/missing windows title background when opening windows
I wonder if this is related to bug 2012225... Next time the issue happens, please run: journalctl -b0 > journal.txt lspci -k > lspcik.txt and attach the resulting text files here. ** Tags added: hybrid multigpu nvidia ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Summary changed: - Corrupted/missing windows title background when opening windows + [nvidia][lunar] Corrupted/missing windows title background when opening windows -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1