https://bugs.kde.org/show_bug.cgi?id=116482
Jaak Ristioja <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #250 from Jaak Ristioja <jaak ristioja ee> 2011-11-24 21:59:40 --- (In reply to comment #242) > For anybody hitting this issue, here's an easy way to identify the corrupt mk4 > file: > > cd ~/.kde4/share/apps/akregator/Archive > for i in *.mk4; do echo $i; ./mku.linux $i > /dev/null; done > > Each file name followed by "Segmentation fault" is corrupt and should be > removed in order to successfuly start akregator. I wouldn't say so, because I couldn't find where I could get this ./mku.linux executable. Another way to detect which mk4 file in ~/.kde4/share/apps/akregator/Archive/ causes Akregator to crash is to use strace to trace the akregator process to find out which file it (opens and) reads last. Just move the corrupted file somewhere else (in case you need to restore the data somehow) to get akregator running again. One might have to do this multiple times if multiple files are corrupt. When oh when are you KDE guys going to add a decent backend to akregator?! Akregator is destroying my feed data too often and it's getting my the nerves. And there seems to be no recovery option *sob* =[ -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
