indicator-messages-service crashed with SIGSEGV in free_fetch_user_request() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit()
Bug #2016312 reported by
errors.ubuntu.com bug bridge
This bug report is a duplicate of:
Bug #2015962: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose().
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
accountsservice (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://
affects: | indicator-messages (Ubuntu) → accountsservice (Ubuntu) |
Changed in accountsservice (Ubuntu): | |
status: | New → Fix Released |
summary: |
- /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages- - service:11:free_fetch_user_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit + indicator-messages-service crashed with SIGSEGV in + free_fetch_user_request() from g_closure_invoke() from + signal_emit_unlocked_R() from g_signal_emit_valist() from + g_signal_emit() |
To post a comment you must log in.