[Bug 2009687] Re: [lunar] Nvidia GPU unused but still powered
This might be related to a triple buffering issue: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1679803 If it is caused by triple buffering then you will find the issue is temporarily fixed in mutter 44~rc (which lacks triple buffering), and will return later in 44.0. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2009687 Title: [lunar] Nvidia GPU unused but still powered To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2009687/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012225] Re: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMP
This also looks relevant, though only appears in one crash report: gnome-shell[10846]: JS ERROR: GLib.Error cogl-framebuffer-error-quark: Failed to create an OpenGL framebuffer object _prepareAnimationInfo@resource:///org/gnome/shell/ui/windowManager.js:1285:34 _sizeChangeWindow@resource:///org/gnome/shell/ui/windowManager.js:1277:18 ** Tags added: nvidia ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gtk4 (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012225 Title: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cdd == 0x8cd5)"] from gsk_gl_command_queue_create_render_target() [gskglcommandqueue.c:1279] To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2012225/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012225] Re: /usr/libexec/mutter-x11-frames:6:g_assertion_message:g_assertion_message_cmpnum:gsk_gl_command_queue_create_render_target:gsk_gl_driver_create_render_target:gsk_gl_render_job_visit_b
This was meant to be fixed in bug 2007766, but it's still happening for some. ** Summary changed: - /usr/libexec/mutter-x11-frames:6:g_assertion_message:g_assertion_message_cmpnum:gsk_gl_command_queue_create_render_target:gsk_gl_driver_create_render_target:gsk_gl_render_job_visit_blurred_outset_shadow_node + mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() from gsk_gl_command_queue_create_render_target() from gsk_gl_driver_create_render_target() from gsk_gl_render_job_visit_blurred_outset_shadow_node() ** Summary changed: - mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() from gsk_gl_command_queue_create_render_target() from gsk_gl_driver_create_render_target() from gsk_gl_render_job_visit_blurred_outset_shadow_node() + mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cdd == 0x8cd5)"] from gsk_gl_command_queue_create_render_target() [gskglcommandqueue.c:1279] ** Package changed: mutter (Ubuntu) => gtk4 (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #5392 https://gitlab.gnome.org/GNOME/gtk/-/issues/5392 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/5392 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012225 Title: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cdd == 0x8cd5)"] from gsk_gl_command_queue_create_render_target() [gskglcommandqueue.c:1279] To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2012225/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012225] [NEW] mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_CO
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~rc-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7164cde08dbb940e13b49c4e92d4914b24e6c7dc 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: gtk Importance: Unknown Status: Unknown ** Affects: gtk4 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: lunar -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012225 Title: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cdd == 0x8cd5)"] from gsk_gl_command_queue_create_render_target() [gskglcommandqueue.c:1279] To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2012225/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012223] Re: mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size() from toplevel_compu
** Summary changed: - /usr/libexec/mutter-x11-frames:11:fetch_request_mode:fetch_request_mode:gtk_widget_get_request_mode:gtk_window_compute_default_size:toplevel_compute_size + mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size() from toplevel_compute_size() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012223 Title: mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size() from toplevel_compute_size() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012223/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012223] Re: /usr/libexec/mutter-x11-frames:11:fetch_request_mode:fetch_request_mode:gtk_widget_get_request_mode:gtk_window_compute_default_size:toplevel_compute_size
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012223 Title: mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size() from toplevel_compute_size() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012223/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012223] [NEW] mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size() from toplevel_com
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~beta-3ubuntu2, the problem page at https://errors.ubuntu.com/problem/461ff881978d26b3ab6a55c3a8b0cef1af4b5473 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: mutter (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: lunar -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012223 Title: mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size() from toplevel_compute_size() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012223/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011271] Re: gdm3: "Oh no! Something has gone wrong."
*** This bug is a duplicate of bug 2012068 *** https://bugs.launchpad.net/bugs/2012068 ** This bug has been marked a duplicate of private bug 2012068 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2011271 Title: gdm3: "Oh no! Something has gone wrong." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011271/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003168] Re: SIdebar, files gets unresponsive after unlocking locked season.
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003168 Title: SIdebar, files gets unresponsive after unlocking locked season. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966905] Re: Memory access errors in gnome-shell from accountsservice
Also tracking in https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 ** Description changed: + https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 + Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) - ==60511== + ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187)
[Bug 2012218] Re: /usr/bin/gnome-shell:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished:g_task_return_now
*** This bug is a duplicate of bug 1966905 *** https://bugs.launchpad.net/bugs/1966905 ** This bug has been marked a duplicate of bug 1966905 Memory access errors in gnome-shell from accountsservice -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012218 Title: /usr/bin/gnome- shell:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished:g_task_return_now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012218] [NEW] /usr/bin/gnome-shell:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished:g_task_return_now
*** This bug is a duplicate of bug 1966905 *** https://bugs.launchpad.net/bugs/1966905 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/d85747462e756cb405d1e87b9c59b0b995a7d394 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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012218 Title: /usr/bin/gnome- shell:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished:g_task_return_now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966905] Re: Memory access errors in gnome-shell from accountsservice
** Changed in: accountsservice (Ubuntu) Importance: Medium => High ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: Memory access errors in gnome-shell from accountsservice To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1966905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011801] Re: gdm3 crashes after installing the 'fuse' package
*** This bug is a duplicate of bug 1717878 *** https://bugs.launchpad.net/bugs/1717878 Thanks. Yes that confirms it is bug 1717878. ** This bug has been marked a duplicate of bug 1717878 gdm3/gdm-session-worker crashed with SIGTRAP logging "GdmSession: no session desktop files installed, aborting..." from get_fallback_session_name from get_default_session_name from get_session_name from get_session_filename from gdm_session_is_wayland_session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2011801 Title: gdm3 crashes after installing the 'fuse' package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2011801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
I believe we have a working patch for the problem. A quick summary of what it looks like is happening: Openbox maintains a list of windows organized by stacking order from highest to lowest. This is a doubly-linked list. There is a function in Openbox called client_calc_layer that uses a pointer into this list to walk through it while modifying it. When client_calc_layer modifies the list, it also messes up the pointer that it is actively using to walk through the list. The next element that Openbox loads contains a dangling pointer, and that promptly results in a segfault when Openbox tries to dereference that pointer. To solve the problem, I added a patch that makes Openbox save a pointer to the list element *before* the current element before modifying the list. When the list is then modified, the still-valid pointer to the previous list element is used to get a new (and actually usable!) pointer to the current list element. The old, broken pointer is then overwritten by the new, working pointer, and the segfaults stop. Using the patch, I am no longer able to reproduce this bug when following the testcase (open a browser fullscreen, right-click a link, and click "Open in new window"). I have the patched Openbox uploaded to a PPA here: https://launchpad.net/~arraybolt3/+archive/ubuntu/openbox -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
That's not this bug then, so please open a new one by running: ubuntu-bug gnome-shell -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011803] Re: Fullscreen games repeatedly fullscreen/unfullscreen in 44~rc
It was fixed in this instead: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2921 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-mutter-44.0 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2011803 Title: Fullscreen games repeatedly fullscreen/unfullscreen in 44~rc To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2011803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1980080] Re: Unable to eject SDcard -getting remounted immediately
Also wondering - my lspci output shows line: 72:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01) I'm wondering about the 'unassigned class' - might it be related to this issue. As most other devices besides NVMe disk starts from 00:, where NVMe starts from 01: Might this 72: mean that SD card reader has priority over NVMe disk ? ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1980080 Title: Unable to eject SDcard -getting remounted immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1980080/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1332623] Re: Thunar behaves inconsistently with USB flash drive FAT32 partitions
** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1332623 Title: Thunar behaves inconsistently with USB flash drive FAT32 partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1332623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012199] [NEW] nautilus crashes during search or bulk filename editing
Public bug reported: EVERY search or bulk file renaming action causes nautilus to crash immediately. All searches cause nautilus to crash immediately. No search ever comes through. Simple typing in the search bar, or as much as clicking on it causes nautilus to crash. Once multiple files are selected and Fn+F2 (Rename) action is selected, nautilus crashes even without allowing the rename dialog box to appear. Note that single file renaming still works. The crashed window gives the option to wait, but waiting never solves the problem, and I am always forced to restart nautilus after force- quitting. What is causing this problem? If this issue is not widespread enough to receive a bugfix, could the developers guide me with this. I find doing a fresh install risky because of lack of enough storage for a complete PC backup. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Package changed: grub-installer (Ubuntu) => nautilus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2012199 Title: nautilus crashes during search or bulk filename editing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2012199/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012199] [NEW] nautilus crashes during search or bulk filename editing
You have been subscribed to a public bug: EVERY search or bulk file renaming action causes nautilus to crash immediately. All searches cause nautilus to crash immediately. No search ever comes through. Simple typing in the search bar, or as much as clicking on it causes nautilus to crash. Once multiple files are selected and Fn+F2 (Rename) action is selected, nautilus crashes even without allowing the rename dialog box to appear. Note that single file renaming still works. The crashed window gives the option to wait, but waiting never solves the problem, and I am always forced to restart nautilus after force- quitting. What is causing this problem? If this issue is not widespread enough to receive a bugfix, could the developers guide me with this. I find doing a fresh install risky because of lack of enough storage for a complete PC backup. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- nautilus crashes during search or bulk filename editing https://bugs.launchpad.net/bugs/2012199 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
The workaround doesn't fix the problem for me. It's not only doesn't wake up the screen, it freezes the whole system and I have to hard reset! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
