Confirming the bug, and also when akregator crashes it looks like the shortcuts like ALT+F2 don't seem to work. When trying to go to system settings and selecting keyboard shortcuts I get "Failed to contact the KDE global shortcuts daemon
Message: The name org.kde.kded was not provided by any .service files
Error: org.freedesktop.DBus.Error.ServiceUnknown".

*** Bug 164906 has been marked as a duplicate of this bug. ***

SVN commit 824854 by osterfeld:

Sanitize findByURL. This stops leaking empty QLists using operator[] and and maybe also fixes the crash in 164265
Needs to be merged into trunk/
CCBUG:164265


 M  +13 -14    feedlist.cpp  
 M  +11 -11    feedlist.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=824854

*** Bug 164821 has been marked as a duplicate of this bug. ***

Using KDE 4.1 RC1 I get a similar crash when akregator starts:

Application: Akregator (akregator), signal SIGSEGV
[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb50c36d0 (LWP 17083)]
[KCrash handler]
#6  0xb363ee02 in QHash<QString, QList<Akregator::Feed*> >::findNode (
    this=0x1c, akey=@0xbfb3ffac, ahp=0x0) at /usr/include/QtCore/qhash.h:862
#7  0xb363d7aa in Akregator::FeedList::findByURL (this=0x83ba6b8, 
    feedURL=@0xbfb3ffac) at /usr/include/QtCore/qhash.h:852
#8  0xb363d97c in Akregator::FeedList::findArticle (this=0x83ba6b8, 
    feedURL=@0xbfb3ffac, guid=@0xbfb3ffb0)
    at /usr/src/debug/kdepim-4.0.98/akregator/src/feedlist.cpp:328
#9  0xb3625b75 in Akregator::ArticleDeleteJob::doStart (this=0x8559468)
    at /usr/src/debug/kdepim-4.0.98/akregator/src/articlejobs.cpp:64
#10 0xb3625e35 in Akregator::ArticleDeleteJob::qt_metacall (this=0x8559468, 
    _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfb40068)
    at /usr/src/debug/kdepim-4.0.98/build/akregator/src/articlejobs.moc:65
#11 0xb65af3fa in QMetaObject::activate (sender=0x855dc68, 
    from_signal_index=4, to_signal_index=4, argv=0x0)
    at kernel/qobject.cpp:3007
#12 0xb65af972 in QMetaObject::activate (sender=0x855dc68, m=0xb6638a08, 
    local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080
#13 0xb65b6547 in QSingleShotTimer::timeout (this=0x855dc68)
    at .moc/release-shared/qtimer.moc:74
#14 0xb65b666c in QSingleShotTimer::timerEvent (this=0x855dc68)
    at kernel/qtimer.cpp:300
#15 0xb65abd1f in QObject::event (this=0x855dc68, e=0xbfb4050c)
    at kernel/qobject.cpp:1105
#16 0xb5a8decc in QApplicationPrivate::notify_helper (this=0x8068490, 
    receiver=0x855dc68, e=0xbfb4050c) at kernel/qapplication.cpp:3772
#17 0xb5a9431e in QApplication::notify (this=0xbfb40884, receiver=0x855dc68, 
    e=0xbfb4050c) at kernel/qapplication.cpp:3366
#18 0xb6d2383d in KApplication::notify (this=0xbfb40884, receiver=0x855dc68, 
    event=0xbfb4050c)
    at /usr/src/debug/kdelibs-4.0.98/kdeui/kernel/kapplication.cpp:311
#19 0xb659db51 in QCoreApplication::notifyInternal (this=0xbfb40884, 
    receiver=0x855dc68, event=0xbfb4050c) at kernel/qcoreapplication.cpp:583
#20 0xb65c6181 in QTimerInfoList::activateTimers (this=0x806b70c)
    at kernel/qcoreapplication.h:215
#21 0xb65c63fb in QEventDispatcherUNIX::processEvents (this=0x806ad80, flags=
      {i = -1078721016}) at kernel/qeventdispatcher_unix.cpp:899
#22 0xb5b180a2 in QEventDispatcherX11::processEvents (this=0x806ad80, flags=
      {i = -1078720568}) at kernel/qeventdispatcher_x11.cpp:154
#23 0xb659c2ca in QEventLoop::processEvents (this=0xbfb40830, flags=
      {i = -1078720504}) at kernel/qeventloop.cpp:149
#24 0xb659c48a in QEventLoop::exec (this=0xbfb40830, flags={i = -1078720456})
    at kernel/qeventloop.cpp:196
#25 0xb659e66d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#26 0xb5a8dd47 in QApplication::exec () at kernel/qapplication.cpp:3304
#27 0x0804eb97 in main (argc=)
    at /usr/src/debug/kdepim-4.0.98/akregator/src/main.cpp:115
#0  0xffffe430 in __kernel_vsyscall ()

Well Akregator seems to work just fine in RC1, installed from Kubuntu binary packages. The problem remains in trunk.

Thanks for the feedback, Matej. It seems that akregatorrc was the cause of the crash here. It works fine now.

*** Bug 166569 has been marked as a duplicate of this bug. ***

*** Bug 166920 has been marked as a duplicate of this bug. ***

Is bug http://bugs.kde.org/show_bug.cgi?id=116482 not related?

> Is bug http://bugs.kde.org/show_bug.cgi?id=116482 not related?

No it's another issue.

I'm not sure if this is really the same as #166569...however, I can dump my feeds.opml and archive contents somewhere if it'll help.

after clean settings in ./kde folder everything is ok 

Update related to my report (#166569, which was apparently marked as a duplicate of this one) - I completely deleted the .kde/share/apps/akregator directory and the .kde/share/config/akregator* files.  I opened a akregator.  I deleted the "KDE" default feeds.  I added a single feed ( http://www.twis.org/audio/podcast.rss , though I suspect the feed's not at fault here ).  I configure the feed to check every 5 days, and limit to 20 articles.  I exit.  I attempt to restart akregator: segfault again.

I've tried it without deleting the KDE default feeds as well - same results.

AMD64, gcc 4.3.1, KDE 4.1.0 release source complied from Gentoo's KDE4 overlay.

(One additional followup - the same set of files opens fine, repeatedly, with my old parallel install of Akregator from KDE 3.5.9, so I'm guessing it's not a magically repeatedly-"corrupted" file problem.)

I tried that, cleaning akregator related files from ~/.kde4 (commetn #13), but it does not work for me using KDE 4.1.0, Akregator 1.2.50. Could one set this bug back to new?

reopen

*** Bug 167924 has been marked as a duplicate of this bug. ***

*** Bug 168778 has been marked as a duplicate of this bug. ***

And another followup, I can confirm this is still a problem in 4.1.1...
Anything I can supply from this end that might help solve this one?  Akregator and k3b are the only two KDE 3.5.x applications remaining that make me keep the 3.5.x install in parallel on my machine here.

Used System is Kubuntu 8.04 with KDE 4.1.1
here is a paste of the Crashmanager 
http://paste.ubuntu.com/44547/

I also confirm the behavior. I use  Kubuntu 8.04 with KDE 4.1.1. You find the  paste of the Crashmanager at http://paste.ubuntu.com/48882/

Same here.
If I remove ~/.kde4/share/apps/akregator/Archive/* Akregator starts again. But if i pull the feeds, quit akregator and try to start it again, it crashes with the following dump http://paste.ubuntu.com/50747/

Hope that helps and I can soon start to use the KDE4 PIM-Suite.

The things are really even worse: akregator not only crashes itself but the whole kontact.

Ok, I removed and readded all of my feeds and found the one that seems to make problems: Its the RSS Feed of sueddeutsche.de found under
http://www.sueddeutsche.de/app/service/rss/alles/rss.xml
If this feed is removed from feeds.opml akregator starts without problems, if I add it again, close akregator und start it again, the problem returns.
Why is this feed causing so much trouble?

I can confirm this bug.
It happens on my Debian machine (lenny) using kde 4.1.2 and on my gentoo machine using the same 4.1.2.
On the first start it works fine... after deleting the default feeds and adding my standard feeds, it crashes and won't start again.
The used feeds are the following:
- lwn.net
- phoronix.com
- heise.de
- planetkde.org

Architecture, both amd64.

I can confirm this bug on OpenSUSE 11.0, Version 1.3.1, Using KDE 4.1.2 (KDE 4.1.2) "release 44.5".  This bug occurs when you limit the number of article stored in the archive.  Changing the archiveMode in the feeds.opml file in .kde4/share/apps/akregator/data to globalDefault makes akregator start normally again.

I am not able to confirm this workaround. It does not work for me on KDE 4.1.2 (Kubuntu 8.04 w/ ppa repos). removing ./.kde4/share/apps/akregator/Archive/* is still needed here to make akregator start again.

SVN commit 873573 by osterfeld:

don't crash on startup when expiry is enabled
BUG:164265


 M  +24 -7     articlejobs.cpp  
 M  +5 -4      articlejobs.h  
 M  +7 -6      expireitemscommand.cpp  
 M  +12 -11    kernel.cpp  
 M  +17 -8     mainwidget.cpp  
 M  +3 -1      mainwidget.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=873573

SVN commit 873575 by osterfeld:

backport 873573: don't crash on startup when expiry is enabled
CCBUG:164265 


 M  +24 -7     articlejobs.cpp  
 M  +5 -4      articlejobs.h  
 M  +7 -6      expireitemscommand.cpp  
 M  +17 -8     mainwidget.cpp  
 M  +5 -2      mainwidget.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=873575

Still crashes for me in trunk.
I removed [Archive] section from akregatorrc (and tried to remove that whole file too - didn't help). 
Also I removed all maxArticleCount entries from feeds.opml. Didn't help too.

Crashes are happening at startup and 100% reproducible.

Here's the backtrace:

Application: Akregator (akregator), signal SIGSEGV

Thread 1 (Thread 0xb4cb2b00 (LWP 3623)):
[KCrash Handler]
#6  0xb343458b in Akregator::FeedList::findByID (this=0x0, id=1174317961) at /home/ulet/kde-svn/kdepim/akregator/src/feedlist.cpp:390
#7  0xb3462035 in Akregator::ExpireItemsCommand::Private::createDeleteJobs (this=0x9d69c28) at /home/ulet/kde-svn/kdepim/akregator/src/expireitemscommand.cpp:89
#8  0xb3462127 in Akregator::ExpireItemsCommand::qt_metacall (this=0x9d6d068, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfc82048)
    at /home/ulet/kde-svn/build/kdepim/akregator/src/expireitemscommand.moc:67
#9  0xb6de7d8a in QMetaObject::activate (sender=0x9d69cc0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3025
#10 0xb6de8302 in QMetaObject::activate (sender=0x9d69cc0, m=0xb6e71dc4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3098
#11 0xb6deee57 in QSingleShotTimer::timeout (this=0x9d69cc0) at .moc/release-shared/qtimer.moc:74
#12 0xb6deef7c in QSingleShotTimer::timerEvent (this=0x9d69cc0) at kernel/qtimer.cpp:300
#13 0xb6de466f in QObject::event (this=0x9d69cc0, e=0xbfc824fc) at kernel/qobject.cpp:1117
#14 0xb65061ec in QApplicationPrivate::notify_helper (this=0x9b1a4f0, receiver=0x9d69cc0, e=0xbfc824fc) at kernel/qapplication.cpp:3809
#15 0xb650c62e in QApplication::notify (this=0xbfc82774, receiver=0x9d69cc0, e=0xbfc824fc) at kernel/qapplication.cpp:3399
#16 0xb729c76b in KApplication::notify (this=0xbfc82774, receiver=0x9d69cc0, event=0xbfc824fc) at /home/ulet/kde-svn/kdelibs/kdeui/kernel/kapplication.cpp:307
#17 0xb6dd6541 in QCoreApplication::notifyInternal (this=0xbfc82774, receiver=0x9d69cc0, event=0xbfc824fc) at kernel/qcoreapplication.cpp:589
#18 0xb6e001a1 in QTimerInfoList::activateTimers (this=0x9b1fcf4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 0xb6dfcd20 in timerSourceDispatch (source=0x9b1fcc0) at kernel/qeventdispatcher_glib.cpp:166
#20 0xb56f61b8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb56f9853 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0x09b1f220 in ?? ()
#23 0x00000000 in ?? ()

r875380 seems to have fixed it for me. 
Thank you very much!

Fixed

*** Bug 173474 has been marked as a duplicate of this bug. ***

*** Bug 174403 has been marked as a duplicate of this bug. ***

*** Bug 174862 has been marked as a duplicate of this bug. ***

*** Bug 174888 has been marked as a duplicate of this bug. ***

*** Bug 175095 has been marked as a duplicate of this bug. ***

*** Bug 174821 has been marked as a duplicate of this bug. ***

*** Bug 175702 has been marked as a duplicate of this bug. ***

*** Bug 177369 has been marked as a duplicate of this bug. ***