akregator crashed with SIGSEGV in Akregator::FeedList::findByURL()

[Thomas Neumann]

Binary package hint: kdepim

Akregator crashed without user action after sitting idle for multiple hours.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/akregator
NonfreeKernelModules: nvidia
Package: akregator 4:4.1.1a-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/akregator -icon akregator -caption Akregator
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_DE.UTF-8
Signal: 11
SourcePackage: kdepim
StacktraceTop:
 ?? () from /usr/lib/kde4/akregatorpart.so
 Akregator::FeedList::findByURL ()
 Akregator::FeedList::findArticle ()
 ?? () from /usr/lib/kde4/akregatorpart.so
 ?? () from /usr/lib/kde4/akregatorpart.so
Title: akregator crashed with SIGSEGV in Akregator::FeedList::findByURL()
Uname: Linux 2.6.27-3-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm lpadmin plugdev scanner vboxusers video

[Thomas Neumann (tneumann)]

After looking at the data more closely, I think this was a crash at startup, not during idling (apport confused me there). I had to clean .kde/share/apps/akregator/Archive to get it running again.

[Apport retracing service (apport)]

StacktraceTop:?? () from /usr/lib/kde4/akregatorpart.so
Akregator::FeedList::findByURL () from /usr/lib/kde4/akregatorpart.so
Akregator::FeedList::findArticle () from /usr/lib/kde4/akregatorpart.so
?? () from /usr/lib/kde4/akregatorpart.so
?? () from /usr/lib/kde4/akregatorpart.so

[Xosé (ubuntu-galizaweb)]

At startup here. Then, if I start it from the command line it just shows a blank pane; a few seconds later, it disappears.

[Richard Birnie (rbirnie-deactivatedaccount)]

Has this crash recurred since this report? If so is there any reliable way to trigger it. I've tried running akregator in an Intrepid VM and it seems to behave fine for me. I even tried disabling the network and starting akregator, restarting the VM etc.

I did notice that the original report is x86_64, are you running 64-bit? I wonder if there is anything in that. Is it possible to reproduce this crash on i386?

[Thomas Neumann (tneumann)]

It crashed on me today, so the bug seems still in there. It manfiests itself roughly like this:
1. start akkregator
2. use it for a few hours, read messages. No problem.
3. quit akregator
4. restart akregator. crash.

I think the crash does not occur for each restart, but once akregator crashes at restart it continues crashing. The only way to to get it working again is to delete the content of .kde/share/apps/akregator/Archive
Most likely akregator is writing something invalid in its Archive directory, and then crashes when trying to re-read it at startup.

All this is on x86_64, I am running 64-bit. Should I try to capture my Archive when it crashes? It might show you if something is corrupted.

[Richard Birnie (rbirnie-deactivatedaccount)]

Thomas,

Thanks for the extra information. I'll keep an eye out for this. I don't
think there's much else we can do right now. It can't hurt to capture the
archive if you get another crash.

[Thomas Neumann (tneumann)]

I attached an apparently corrupted akregator archive. The file is the content of .kde/share/apps/akregator, as written by akregator itself. At startup akregator crashes reproducible until I delete the content of the Archive directory.

[Richard Birnie (rbirnie-deactivatedaccount)]

Thanks for following up and providing data. I've imported your feeds.opml into akregator and I'll leave it idling for a while then see if I can cause the crash.

I'm afraid I wouldn't recognise a corrupt archive but someone else might be able to use that.

[Lari Natri (larva)]

I have the same problem, and it still exists with akregator-4.1.2-0ubuntu1: akregator crashes almost on every startup when loading the archived feeds. Removing contents of ~/.kde/share/apps/akregator/Archive allows Akregator to start up again.

Unfortunately i filed a duplicate bug report #276129 before finding this. (Now I've marked mine as a duplicate of this report.)

BTW; Akregator's configuration dialog doesn't allow changing of any feed archiving related options, including disabling of archiving. You can change the options in the GUI, but Apply button doesn't become active. If one clicks OK and returns, the settings are as they were before trying to change them.

[Richard Birnie (rbirnie-deactivatedaccount)]

This bug should be fixed by version 4.1.2-0ubuntu2. Is anyone still experiencing this bug or can we close it? If you are still experiencing the bug can you check the output of the command 'sudo apt-cache policy akregator'

thanks

[Jonathan Thomas (echidnaman)]

Assuming fixed.