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() from meta_x_error() from _XError()
Bug #2015041 reported by
errors.ubuntu.com bug bridge
This bug report is a duplicate of:
Bug #2117487: gnome-shell crash with X11 error 'BadWindow (invalid Window parameter)'.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
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:/
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://
| summary: |
- /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 xxxx error_code 8 request_code 147 + (unknow"...] |
| summary: |
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 xxxx error_code 8 request_code 147 - (unknow"...] + display_error_event() |
| summary: |
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() + display_error_event() from meta_x_error() from _XError() |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #1 |
| tags: |
added: noble plucky questing removed: lunar |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #2 |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #3 |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #4 |
To post a comment you must log in.
Today the error looks very similar to bug 2117487, so keep an eye on that.