Comment 2 for bug 1767446

Revision history for this message
ichro furuya (furuya) wrote :

(P.S.)

I reinstalled the system.
The same fault occurs fixedly.

I saw the log and there was a crash dump.
I think that you can send more information than the previous report.

I reported it by doing the following.
$ ubuntu-bug /var/crash/_usr_bin_fcitx-dbus-watcher.1000.crash

---
/var/log/apport.log.1

ERROR: apport (pid 3904) Mon May 7 21:23:47 2018: called for pid 3826, signal 3, core limit 0, dump mode 1
ERROR: apport (pid 1638) Mon May 7 21:27:35 2018: called for pid 1255, signal 6, core limit 0, dump mode 1
ERROR: apport (pid 1638) Mon May 7 21:27:35 2018: executable: /usr/bin/fcitx-dbus-watcher (command line "/usr/bin/fcitx-dbus-watcher unix:abstract=/tmp/dbus-nz01H9srUR,guid=0190960852f560e8cdc8c6125af0460f 1251")
ERROR: apport (pid 1638) Mon May 7 21:27:38 2018: gdbus call error: Error connecting: Could not connect: Connection refused

ERROR: apport (pid 1638) Mon May 7 21:27:38 2018: debug: session gdbus call:
ERROR: apport (pid 1638) Mon May 7 21:27:38 2018: wrote report /var/crash/_usr_bin_fcitx-dbus-watcher.1000.crash
ERROR: apport (pid 3102) Mon May 7 22:17:56 2018: called for pid 2849, signal 3, core limit 0, dump mode 1