Comment 27 for bug 56369

Hi !

I got a problem starting akregator after a machine crash. It's due to a corrupted archive file because moving my archive folder solved the startup issue. But I'm a bit puzzled : how can I identify which mk4 is causing the crash ? It looks like moving some mk4 files out of the Archive folder is making Akregator hang (not crash).

Thus a little feature request : could it be possible to display on output (when launching from the command line) which mk4 file is being read/parsed ? It would be easier to identify the corrupted one.