xfwm4 crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() from g_log_structured_array() from g_log_structured_standard() from _gdk_x11_display_error_event()
Bug #1877242 reported by
errors.ubuntu.com bug bridge
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xfwm4 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Triaged
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The Ubuntu Error Tracker has been receiving reports about a problem regarding xfwm4. This problem was most recently seen with package version 4.14.1-0ubuntu1, 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/xfwm4:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_standard:_gdk_x11_display_error_event + xfwm4 crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() + from g_log_structured_array() from g_log_structured_standard() from + _gdk_x11_display_error_event() |
Changed in xfwm4 (Ubuntu Focal): | |
status: | Confirmed → Triaged |
Changed in xfwm4 (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in xfwm4 (Ubuntu): | |
status: | Triaged → Fix Released |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.