Version: 1.2.1 (using KDE 3.5.1, Kubuntu Package 4:3.5.1-0ubuntu7 dapper) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.15-15-686 I was adding all feeds at once (approx >15) from an article on the german www.netzeitung.de via the konqueror statusbar icon. Akregator crashed while being in the background. I think it crashed while fetching the description and the icons of the newly added feeds. I observed this crash bug more than once. It occurs generally when adding a relatively 'large' number of feeds. Everytime it crashes while fetching the icons and the description of the feed-entry. Data is lost. Have to re-add the feeds until it gets through. Backtrace follows: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 905377472 (LWP 9408)] [KCrash handler] #6 0x37e95602 in RSS::Image::slotData () from /usr/lib/libakregatorprivate.so #7 0x37e95f7a in RSS::Image::qt_invoke () from /usr/lib/libakregatorprivate.so #8 0x370af26d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #9 0x36b9ea56 in KIO::TransferJob::data (this=0x87046f8, t0=0x3f819100, t1=@0x3f819100) at jobclasses.moc:993 #10 0x36b9eac0 in KIO::TransferJob::slotData (this=0x87046f8, _data=@0x3f819100) at job.cpp:902 #11 0x36bf02de in KIO::TransferJob::qt_invoke (this=0x87046f8, _id=18, _o=0x3f818f04) at jobclasses.moc:1072 #12 0x370af26d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #13 0x36b9c242 in KIO::SlaveInterface::data (this=0x865e448, t0=@0x3f819100) at slaveinterface.moc:194 #14 0x36c081e5 in KIO::SlaveInterface::dispatch (this=0x865e448, _cmd=100, rawdata=@0x3f819100) at slaveinterface.cpp:234 #15 0x36baf2e9 in KIO::SlaveInterface::dispatch (this=0x865e448) at slaveinterface.cpp:173 #16 0x36bb3af0 in KIO::Slave::gotInput (this=0x865e448) at slave.cpp:300 #17 0x36bb3c85 in KIO::Slave::qt_invoke (this=0x865e448, _id=4, _o=0x3f819228) at slave.moc:113 #18 0x370af26d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #19 0x370afb7c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #20 0x3743f0f3 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3 #21 0x370cf59a in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3 #22 0x3704565a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #23 0x3704584c in QApplication::notify () from /usr/lib/libqt-mt.so.3 #24 0x3773dc7d in KApplication::notify (this=0x3f819804, receiver=0x862bcc0, event=0x3f819580) at kapplication.cpp:550 #25 0x36fd6967 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #26 0x37037177 in QEventLoop::activateSocketNotifiers () from /usr/lib/libqt-mt.so.3 #27 0x36fea72f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #28 0x3705e153 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #29 0x3705e076 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #30 0x37044169 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #31 0x08050e8b in ?? () #32 0x3f819804 in ?? () #33 0x00000001 in ?? () #34 0x00000001 in ?? () #35 0x00000000 in ?? ()
tested it with the new akregator on Kubuntu (KDE 3.5.4) with netzeitung.de and i can't confirm. Is it still occuring for you with a newer version?
I haven't added any new feeds since a long time so I have not seen this crash anymore. I will test it and report back, if it happens again with the latest edgy package.
I just added more than 50 different feeds from various places and it didn't crash anymore. Seems to be fixed!
Ok, closing.
*** Bug 136033 has been marked as a duplicate of this bug. ***
Reproduced on Akregator 1.2.9 (Using KDE 3.5.9).