gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from _meta_idle_monitor_watch_fire() from idle_monitor_dispatch_timeout() while logging {"Function IdleMonitorWatchFunc terminated with uncatchable exception"}
Bug #1799714 reported by
errors.ubuntu.com bug bridge
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-shell (Ubuntu) |
Fix Released
|
High
|
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 3.30.1-2ubuntu1, 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:gjs_callback_closure:ffi_closure_unix64_inner:ffi_closure_unix64:_meta_idle_monitor_watch_fire:idle_monitor_dispatch_timeout + gnome-shell crashed with SIGTRAP in gjs_callback_closure() from + ffi_closure_unix64_inner() from ffi_closure_unix64() from + _meta_idle_monitor_watch_fire() from idle_monitor_dispatch_timeout() |
| summary: |
gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from _meta_idle_monitor_watch_fire() from idle_monitor_dispatch_timeout() + while logging {"Function IdleMonitorWatchFunc terminated with + uncatchable exception"} |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in gnome-shell (Ubuntu): | |
| status: | New → Confirmed |
| tags: | added: disco |
| tags: | added: bionic |
| Changed in gnome-shell (Ubuntu): | |
| importance: | Undecided → High |
| tags: | removed: cosmic kylin-18.10 |
| tags: | removed: disco |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #2 |
| Changed in gnome-shell (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.