messaging_ui_account_utils_ready_cb: Couldn't init account utils!messaging_ui_account_utils_ready_cb: got error code: 4, domain: dbus-glib-error-quark, message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
or you can try to backup and then restore, iirc this should recreate all of the databases
As I still switch between SIMs and also have a high swap usage I sometimes have the feeling that 'some swap thingy here goes crazy'. Please check your swap partitions or disable extended swap / enable stock swap partition and test once more. [a shot in the dark]
I don't suppose you have a log of that fsck? If you do, you should be able to identify which inodes were corrupted. Then you can run something like ls -aRi1 and grep for each inode to identify which filenames point to those inodes. You can then use dpkg -S with those filenames to identify which packages you should reinstall.
In my experience, fsck on flash/sd always ends in tears. It was disabled until cssu, then enabled and wrecking partitions, then disabled again, and now I don't know if it's armed to nuke /home or not. Anyway, my usual strategy after unexpected reboot, is to do as root: cd /home ls -laR >/dev/null fs errors usually show up with that. If the damage is sma, I've made tarball of /home in backupmenu, then recreated fs and untarred. If there are non-fs issues, like zeroed files, they wont be found by this. Good luck!
loodRose:~# mc-tool list mc-tool: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.