Bug #56369 “akregator is not crash proof” : Bugs : kdepim package : Ubuntu

Revision history for this message

In KDE Bug Tracking System #116482, Luciano Montanaro (mikelima) wrote on 2005-11-16:

#10

Version: 3.5rc1 (using KDE KDE 3.5.0)
Installed from: SuSE RPMs

Akregator cannot be started for me since I upgraded to RC1.
Beta2 was ok.
starting akregator from the command line, I get the following message:
akregator: ERROR: Communication problem with akregator, it probably crashed.

The crash window does not appear, however, strace output suggests akregator actually crashes.

I see also this line:

*** glibc detected *** malloc(): memory corruption: 0x08393f88 ***
I'll attach the strace output.

Revision history for this message

In KDE Bug Tracking System #116482, Luciano Montanaro (mikelima) wrote on 2005-11-16:

#11

Created attachment 13495
The strace output for the failing execution

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-01-04:

#12

Have you upgraded to 3.5.0? Does Akregator work now for you?

Revision history for this message

In KDE Bug Tracking System #116482, Murtaza-iit84 (murtaza-iit84) wrote on 2006-01-04:

#13

Created attachment 14131
Backtrace produced by KDE crash handler

Akregator crashes on startup saying "Communication problem with akregator, it
probably crashed." This problem started when I upgraded to KDE 3.5.0 and also
upgraded akregator with packages obtained from
http://pkg-kde.alioth.debian.org.

Revision history for this message

In KDE Bug Tracking System #116482, Thiago Macieira (thiago-kde) wrote on 2006-01-06:

#14

Download full text (3.6 KiB)

Pasting the backtrace:

(no debugging symbols found)
[KCrash handler]
#3 0x4241f89a in c4_FormatB::Define ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#4 0x4242491b in c4_HandlerSeq::Prepare ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#5 0x42424e7a in c4_Persist::LoadAll ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#6 0x4242509c in c4_Storage::c4_Storage ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#7 0x42407e54 in Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#8 0x4240844a in Akregator::Backend::StorageMK4Impl::archiveFor ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#9 0x400c1e96 in Akregator::Feed::loadArticles ()
   from /usr/lib/libakregatorprivate.so
#10 0x400c2a02 in Akregator::Feed::fromOPML ()
   from /usr/lib/libakregatorprivate.so
#11 0x400c2e22 in Akregator::FeedList::parseChildNodes ()
   from /usr/lib/libakregatorprivate.so
#12 0x400c339a in Akregator::FeedList::readFromXML ()
   from /usr/lib/libakregatorprivate.so
#13 0x422e49ba in Akregator::View::loadFeeds ()
   from /usr/lib/kde3/libakregatorpart.so
#14 0x422e4d4a in Akregator::Part::openFile ()
   from /usr/lib/kde3/libakregatorpart.so
#15 0x422dc0f5 in Akregator::Part::openURL ()
   from /usr/lib/kde3/libakregatorpart.so
#16 0x422b8d02 in Akregator::Part::openStandardFeedList ()
   from /usr/lib/kde3/libakregatorpart.so
#17 0x422ee1b2 in Akregator::AkregatorPartIface::process ()
   from /usr/lib/kde3/libakregatorpart.so
#18 0x40994415 in DCOPClient::receive () from /usr/lib/libDCOP.so.4
#19 0x409949f9 in DCOPClient::send () from /usr/lib/libDCOP.so.4
#20 0x40994fd0 in DCOPRef::sendInternal () from /usr/lib/libDCOP.so.4
#21 0x08051540 in ?? ()
#22 0xbfffee40 in ?? ()
#23 0xbfffee94 in ?? ()
#24 0xbfffeeb4 in ?? ()
#25 0xbfffee74 in ?? ()
#26 0xbfffeeb4 in ?? ()
#27 0x08052fd9 in vtable for QGList ()
#28 0xbfffee84 in ?? ()
#29 0xbfffee48 in ?? ()
#30 0x40268ea2 in free () from /lib/tls/libc.so.6
#31 0x408e3684 in KUniqueApplication::processDelayed ()
   from /usr/lib/libkdecore.so.4
#32 0x408e4fc9 in KUniqueApplication::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#33 0x40cb5b57 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#34 0x41046055 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#35 0x40cd3a40 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#36 0x40cdb354 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#37 0x40c4b698 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#38 0x40c4b8b6 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#39 0x408d1abc in KApplication::notify () from /usr/lib/libkdecore.so.4
#40 0x40bdb5e5 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#41 0x40c3c98c in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#42 0x40bef35c in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#43 0x40c63da2 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#44 0x40c63ccb in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#45 0x40c4a225 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#46 0x08050d80 in ?? ()
#47 0xbffff664 in ?? ()
#48 ...

Pasting the backtrace:

(no debugging symbols found)
[KCrash handler]
#3  0x4241f89a in c4_FormatB::Define ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#4  0x4242491b in c4_HandlerSeq::Prepare ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#5  0x42424e7a in c4_Persist::LoadAll ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#6  0x4242509c in c4_Storage::c4_Storage ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#7  0x42407e54 in Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#8  0x4240844a in Akregator::Backend::StorageMK4Impl::archiveFor ()
   from /usr/lib/kde3/libakregator_mk4storage_plugin.so
#9  0x400c1e96 in Akregator::Feed::loadArticles ()
   from /usr/lib/libakregatorprivate.so
#10 0x400c2a02 in Akregator::Feed::fromOPML ()
   from /usr/lib/libakregatorprivate.so
#11 0x400c2e22 in Akregator::FeedList::parseChildNodes ()
   from /usr/lib/libakregatorprivate.so
#12 0x400c339a in Akregator::FeedList::readFromXML ()
   from /usr/lib/libakregatorprivate.so
#13 0x422e49ba in Akregator::View::loadFeeds ()
   from /usr/lib/kde3/libakregatorpart.so
#14 0x422e4d4a in Akregator::Part::openFile ()
   from /usr/lib/kde3/libakregatorpart.so
#15 0x422dc0f5 in Akregator::Part::openURL ()
   from /usr/lib/kde3/libakregatorpart.so
#16 0x422b8d02 in Akregator::Part::openStandardFeedList ()
   from /usr/lib/kde3/libakregatorpart.so
#17 0x422ee1b2 in Akregator::AkregatorPartIface::process ()
   from /usr/lib/kde3/libakregatorpart.so
#18 0x40994415 in DCOPClient::receive () from /usr/lib/libDCOP.so.4
#19 0x409949f9 in DCOPClient::send () from /usr/lib/libDCOP.so.4
#20 0x40994fd0 in DCOPRef::sendInternal () from /usr/lib/libDCOP.so.4
#21 0x08051540 in ?? ()
#22 0xbfffee40 in ?? ()
#23 0xbfffee94 in ?? ()
#24 0xbfffeeb4 in ?? ()
#25 0xbfffee74 in ?? ()
#26 0xbfffeeb4 in ?? ()
#27 0x08052fd9 in vtable for QGList ()
#28 0xbfffee84 in ?? ()
#29 0xbfffee48 in ?? ()
#30 0x40268ea2 in free () from /lib/tls/libc.so.6
#31 0x408e3684 in KUniqueApplication::processDelayed ()
   from /usr/lib/libkdecore.so.4
#32 0x408e4fc9 in KUniqueApplication::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#33 0x40cb5b57 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#34 0x41046055 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#35 0x40cd3a40 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#36 0x40cdb354 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#37 0x40c4b698 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#38 0x40c4b8b6 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#39 0x408d1abc in KApplication::notify () from /usr/lib/libkdecore.so.4
#40 0x40bdb5e5 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#41 0x40c3c98c in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#42 0x40bef35c in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#43 0x40c63da2 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#44 0x40c63ccb in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#45 0x40c4a225 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#46 0x08050d80 in ?? ()
#47 0xbffff664 in ?? ()
#48 0xbffff664 in ?? ()
#49 0xbffff788 in ?? ()
#50 0x08050d22 in ?? ()
#51 0x403371e0 in __malloc_initialize_hook () from /lib/tls/libc.so.6
#52 0x0000000c in ?? ()
#53 0x00000069 in ?? ()
#54 0x401c6cb8 in ?? () from /usr/lib/libstdc++.so.6
#55 0x0000000c in ?? ()
#56 0x08061830 in ?? ()
#57 0xbffff678 in ?? ()
#58 0x40fb6bd5 in QAsciiBucket::QAsciiBucket () from /usr/lib/libqt-mt.so.3
#59 0x40216ec0 in __libc_start_main () from /lib/tls/libc.so.6
#60 0x08050051 in ?? ()

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-02-13:

#15

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-02-13:

#16

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-02-13:

#17

It seems that Akregator crashes while accessing the backend corrupt the metakit storage, which causes crashes then at startup.
A workaround is to move ~/.kde/share/apps/akregator/Archive/*mk4 somewhere else. That should make Akregator start again, but all archived articles are lost.You can then copy mk4 files back and test which one causes the crash...

It would be _very_ useful if someone experiencing this crash could zip the files in Archive/ and send them to me (frank.osterfeld at gmail.com) and also his feeds.opml. (If you want to help even more, identify the exact archive file that causes the crash).

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-02-25:

#18

Download full text (7.7 KiB)

SVN commit 513455 by osterfeld:

Lock archive to avoid metakit archive corruption due to multiple write access.
Usually Akregator being a KUniqueApplication avoids multiple Akregator instances accessing the archive, but there seem to
be some cases where KUniqueApp is not safe enough (right after update, multiple KDE sessions, when using --nofork option).
So we lock the archive like KMail does: if locking fails, show an error message to the user, giving him the possibility to
either continue without archive, or to force access.
As this is a severe bug (multiple write access can corrupt archives, which can make Akregator crash at startup), I think
making use of the message unfreeze is justified.
CCBUG: 116482
CCMAIL:<email address hidden>
CCMAIL:<email address hidden>

M +133 -1 akregator_part.cpp
M +2 -0 akregator_part.h
A kcursorsaver.h [License: no copyright]

--- branches/KDE/3.5/kdepim/akregator/src/akregator_part.cpp #513454:513455
@@ -56,6 +56,13 @@
#include <qwidgetlist.h>
#include <private/qucomextra_p.h>

+#include <cerrno>
+#include <sys/types.h>
+#include <signal.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include <unistd.h>
+
#include "aboutdata.h"
#include "actionmanagerimpl.h"
#include "akregator_part.h"
@@ -68,6 +75,7 @@
#include "frame.h"
#include "article.h"
#include "kernel.h"
+#include "kcursorsaver.h"
#include "notificationmanager.h"
#include "pageviewer.h"
#include "plugin.h"
@@ -135,8 +143,21 @@

     m_storage = 0;
     Backend::StorageFactory* factory = Backend::StorageFactoryRegistry::self()->getFactory(Settings::archiveBackend());
+
     if (factory != 0)
- m_storage = factory->createStorage(QStringList());
+ {
+
+ if (Settings::archiveBackend() == "metakit")
+ {
+ if (tryToLock(factory->name()))
+ m_storage = factory->createStorage(QStringList());
+ else
+ m_storage = dummyFactory->createStorage(QStringList());
+ }
+ else
+ m_storage = factory->createStorage(QStringList());
+ }
+

     if (!m_storage) // Houston, we have a problem
     {
@@ -877,6 +898,117 @@
     return false;
}

+static QString getMyHostName()
+{
+ char hostNameC[256];
+ // null terminate this C string
+ hostNameC[255] = 0;
+ // set the string to 0 length if gethostname fails
+ if(gethostname(hostNameC, 255))
+ hostNameC[0] = 0;
+ return QString::fromLocal8Bit(hostNameC);
+}

+// taken from KMail
+bool Part::tryToLock(const QString& backendName)
+{
+// Check and create a lock file to prevent concurrent access to metakit archive
+ QString appName = kapp->instanceName();
+ if ( appName.isEmpty() )
+ appName = "akregator";
+
+ QString programName;
+ const KAboutData *about = kapp->aboutData();
+ if ( about )
+ programName = about->programName();
+ if ( programName.isEmpty() )
+ programName = i18n("Akregator");
+
+ QString lockLocation = locateLocal("data", "akregator/lock");
+ KSimpleConfig config(lockLocation);
+ int oldPid = config.readNumEntry("pid", -1);
+ const QString oldHostName = config.readEnt...

SVN commit 513455 by osterfeld:

Lock archive to avoid metakit archive corruption due to multiple write access.
Usually Akregator being a KUniqueApplication avoids multiple Akregator instances accessing the archive, but there seem to
be some cases where KUniqueApp is not safe enough (right after update, multiple KDE sessions, when using --nofork option).
So we lock the archive like KMail does: if locking fails, show an error message to the user, giving him the possibility to 
either continue without archive, or to force access.
As this is a severe bug (multiple write access can corrupt archives, which can make Akregator crash at startup), I think 
making use of the message unfreeze is justified.
CCBUG: 116482
CCMAIL:kde-i18n-doc@kde.org
CCMAIL:akregator-devel@lists.sf.net

M  +133 -1    akregator_part.cpp  
 M  +2 -0      akregator_part.h  
 A             kcursorsaver.h   [License: no copyright]

--- branches/KDE/3.5/kdepim/akregator/src/akregator_part.cpp #513454:513455
@@ -56,6 +56,13 @@
 #include <qwidgetlist.h>
 #include <private/qucomextra_p.h>
 
+#include <cerrno>
+#include <sys/types.h>
+#include <signal.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include <unistd.h>
+
 #include "aboutdata.h"
 #include "actionmanagerimpl.h"
 #include "akregator_part.h"
@@ -68,6 +75,7 @@
 #include "frame.h"
 #include "article.h"
 #include "kernel.h"
+#include "kcursorsaver.h"
 #include "notificationmanager.h"
 #include "pageviewer.h"
 #include "plugin.h"
@@ -135,8 +143,21 @@
 
 m_storage = 0;
 Backend::StorageFactory* factory = Backend::StorageFactoryRegistry::self()->getFactory(Settings::archiveBackend());
+ 
 if (factory != 0)
- m_storage = factory->createStorage(QStringList());
+ {
+ 
+ if (Settings::archiveBackend() == "metakit")
+ {
+ if (tryToLock(factory->name()))
+ m_storage = factory->createStorage(QStringList());
+ else 
+ m_storage = dummyFactory->createStorage(QStringList());
+ }
+ else
+ m_storage = factory->createStorage(QStringList());
+ }
+ 
 
 if (!m_storage) // Houston, we have a problem
 {
@@ -877,6 +898,117 @@
 return false;
 }
 
+static QString getMyHostName()
+{
+ char hostNameC[256];
+ // null terminate this C string
+ hostNameC[255] = 0;
+ // set the string to 0 length if gethostname fails
+ if(gethostname(hostNameC, 255))
+ hostNameC[0] = 0;
+ return QString::fromLocal8Bit(hostNameC);
+}
 
+// taken from KMail
+bool Part::tryToLock(const QString& backendName)
+{
+// Check and create a lock file to prevent concurrent access to metakit archive
+ QString appName = kapp->instanceName();
+ if ( appName.isEmpty() )
+ appName = "akregator";
+
+ QString programName;
+ const KAboutData *about = kapp->aboutData();
+ if ( about )
+ programName = about->programName();
+ if ( programName.isEmpty() )
+ programName = i18n("Akregator");
+
+ QString lockLocation = locateLocal("data", "akregator/lock");
+ KSimpleConfig config(lockLocation);
+ int oldPid = config.readNumEntry("pid", -1);
+ const QString oldHostName = config.readEntry("hostname");
+ const QString oldAppName = config.readEntry( "appName", appName );
+ const QString oldProgramName = config.readEntry( "programName", programName );
+ const QString hostName = getMyHostName();
+ bool first_instance = false;
+ if ( oldPid == -1 )
+ first_instance = true;
+ // check if the lock file is stale by trying to see if
+ // the other pid is currently running.
+ // Not 100% correct but better safe than sorry
+ else if (hostName == oldHostName && oldPid != getpid()) {
+ if ( kill(oldPid, 0) == -1 )
+ first_instance = ( errno == ESRCH );
+ }
+
+ if ( !first_instance )
+ {
+ QString msg;
+ if ( oldHostName == hostName ) 
+ {
+ // this can only happen if the user is running this application on
+ // different displays on the same machine. All other cases will be
+ // taken care of by KUniqueApplication()
+ if ( oldAppName == appName )
+ msg = i18n("<qt>%1 already seems to be running on another display on "
+ "this machine. Running %2 more than once is not supported "
+ "by the %3 backend and "
+ "can cause the loss of archived articles and crashes at startup. "
+ "You should disable the archive for now "
+ "unless you are sure that %2 is not already running.</qt>")
+ .arg( programName, programName, backendName );
+ // QString::arg( st ) only replaces the first occurrence of %1
+ // with st while QString::arg( s1, s2 ) replacess all occurrences
+ // of %1 with s1 and all occurrences of %2 with s2. So don't
+ // even think about changing the above to .arg( programName ).
+ else
+ msg = i18n("<qt>%1 seems to be running on another display on this "
+ "machine. Running %1 and %2 at the same "
+ "time is not supported by the %3 backend and can cause "
+ "the loss of archived articles and crashes at startup. "
+ "You should disable the archive for now "
+ "unless you are sure that %2 is not already running.</qt>")
+ .arg( oldProgramName, programName, backendName );
+ }
+ else
+ {
+ if ( oldAppName == appName )
+ msg = i18n("<qt>%1 already seems to be running on %2. Running %1 more "
+ "than once is not supported by the %3 backend and can cause "
+ "the loss of archived articles and crashes at startup. "
+ "You should disable the archive for now "
+ "unless you are sure that it is "
+ "not already running on %2.</qt>")
+ .arg( programName, oldHostName, backendName );
+ else
+ msg = i18n("<qt>%1 seems to be running on %3. Running %1 and %2 at the "
+ "same time is not supported by the %4 backend and can cause "
+ "the loss of archived articles and crashes at startup. "
+ "You should disable the archive for now "
+ "unless you are sure that %1 is "
+ "not running on %3.</qt>")
+ .arg( oldProgramName, programName, oldHostName, backendName );
+ }
+
+ KCursorSaver idle( KBusyPtr::idle() );
+ if ( KMessageBox::No ==
+ KMessageBox::warningYesNo( 0, msg, QString::null,
+ i18n("Force Access"),
+ i18n("Disable Archive")) )
+ {
+ return false;
+ }
+ }
+
+ config.writeEntry("pid", getpid());
+ config.writeEntry("hostname", hostName);
+ config.writeEntry( "appName", appName );
+ config.writeEntry( "programName", programName );
+ config.sync();
+ return true;
+}
+
+
 } // namespace Akregator
 #include "akregator_part.moc"
--- branches/KDE/3.5/kdepim/akregator/src/akregator_part.h #513454:513455
@@ -195,6 +195,8 @@
 /** creates an OPML file containing the initial feeds (KDE feeds) */
 static QDomDocument createDefaultFeedList();
 
+ bool tryToLock(const QString& backendName);
+ 
 private: // attributes
 
 class ApplyFiltersInterceptor;

Revision history for this message

In KDE Bug Tracking System #116482, Y-coolo (y-coolo) wrote on 2006-03-03:

#19

Are you still interested in a corrupted file? I have one :)

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-03-09:

#20

*** This bug has been marked as a duplicate of 121826 ***

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-03-09:

#21

eh, wrong direction. need coffee.

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-03-09:

#22

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-03-24:

#23

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-06-19:

#24

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-07-05:

#25

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-07-06:

#26

Ken writes in 130224:

"This happened after a power outage so I am not surprised something got
corrupted. [...]"

Revision history for this message

In KDE Bug Tracking System #116482, Bugs-kde-org-g (bugs-kde-org-g) wrote on 2006-07-07:

#27

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.

Revision history for this message

In KDE Bug Tracking System #116482, Bugs-kde-org-g (bugs-kde-org-g) wrote on 2006-07-07:

#28

According to the other bugs I've seen around, I guess this is an upstream problem with metakit not handling correctly corrupted archive files. So it should probably be reported here : http://www.equi4.com/cgi-bin/cvstrac/metakit/rptview?rn=4 but as I said, I don't know how to determine which file is corrupted. I would send it to you if I could find a way...

Revision history for this message

Fred van Zwieten (fvzwieten) wrote on 2006-08-14:

#1

Update: just found out that removing the archive map and the lock file from ~/.kde/share/apps/akregator/archive solves this keeping all my subscription info intact (but empty).

Revision history for this message

Fred van Zwieten (fvzwieten) wrote on 2006-08-15:

#2

I'm running kubuntu dapper with all updates up till now (15-aug-06). Running KDE 3.5.4 with kontact v1.2.3 and akregator v1.2.4

Revision history for this message

Andreas Simon (andreas-w-simon) wrote on 2006-08-20:

#3

This looks very much like upstream KDE bug #116482. When the system crashes or when a power outage happens, akregator's archive gets corrupted which causes akgregator to segfault.

Bug Watch Updater (bug-watch-updater) on 2006-08-21

Changed in kdepim:
status:	Unknown → Confirmed

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-09-03:

#29

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-09-04:

#30

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

Revision history for this message

Scott Beamer (angrykeyboarder) wrote on 2006-10-06:

#4

Just wondering...

Is *any* application "crash-proof"?

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-11-03:

#31

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2006-11-27:

#32

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

Revision history for this message

In KDE Bug Tracking System #116482, Jure Repinc (jlp) wrote on 2007-01-22:

#33

Download full text (5.1 KiB)

I also have a crash at sturtup. This is with Akregator 3.5.5 on Gentoo Linux. Here is the backtrace:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1244051760 (LWP 1558)]
[KCrash handler]
#6 c4_Column::PullValue (ptr_=@0xbfc4b634) at column.cpp:777
#7 0xb5967b73 in c4_FormatV::SetupAllSubviews (this=0x85bdbb8)
    at format.cpp:1026
#8 0xb59681ee in c4_FormatV::Get (this=0x85bdbb8, index_=0,
    length_=@0xbfc4b69c) at format.cpp:1096
#9 0xb596b790 in c4_Handler::GetBytes (this=0x85bdbb8, index_=0,
    buf_=@0xbfc4b710, copySmall_=false) at handler.cpp:58
#10 0xb597b237 in c4_Sequence::Get (this=0x85be370, index_=0, propId_=35,
    buf_=@0xbfc4b710) at viewx.cpp:356
#11 0xb596fb4a in c4_Reference::GetData (this=0xbfc4b74c, buf_=@0xbfc4b710)
    at ./../include/mk4.inl:421
#12 0xb597aab7 in c4_ViewRef::operator c4_View (this=0xbfc4b74c)
    at viewx.cpp:643
#13 0xb5974e15 in c4_Storage::Description (this=0x855eea0,
    name_=0xb4f0046a "articles") at store.cpp:360
#14 0xb597504d in c4_Storage::GetAs (this=0x855eea0,
    description_=0xb5993924 "articles[guid:S,title:S,hash:I,guidIsHash:I,guidIsPermaLink:I,description:S,link:S,comments:I,commentsLink:S,status:I,pubDate:I,tags[tag:S],hasEnclosure:I,enclosureUrl:S,enclosureType:S,enclosureLengt"...)
    at store.cpp:279
#15 0xb5955279 in FeedStorageMK4Impl (this=0x85bdf70, url=@0x85bde00,
    main=0x8091458) at feedstoragemk4impl.cpp:156
#16 0xb5958e7a in Akregator::Backend::StorageMK4Impl::archiveFor (
    this=0x8091458, url=@0x85bde00) at storagemk4impl.cpp:278
#17 0xb7f7b2e7 in Akregator::Feed::loadArticles (this=0x85bdd98)
    at feed.cpp:221
#18 0xb7f7c14a in Akregator::Feed::fromOPML (e=@0xbfc4bb84) at feed.cpp:165
#19 0xb7f878ba in Akregator::FeedList::parseChildNodes (this=0x82436d8,
    node=@0xbfc4bbf4, parent=0x85bc180) at feedlist.cpp:117
#20 0xb7f8784d in Akregator::FeedList::parseChildNodes (this=0x82436d8,
    node=@0xbfc4bd0c, parent=0x82435c0) at feedlist.cpp:135
#21 0xb7f87d74 in Akregator::FeedList::readFromXML (this=0x82436d8,
    doc=@0xbfc4bebc) at feedlist.cpp:175
#22 0xb5b625fc in Akregator::View::loadFeeds (this=0x8093cf8,
    doc=@0xbfc4bebc, parent=0x0) at akregator_view.cpp:541
#23 0xb5b59a22 in Akregator::Part::openFile (this=0x812db68)
    at akregator_part.cpp:443
#24 0xb5b56b94 in Akregator::Part::openURL (this=0x812db68, url=@0xbfc4bf84)
    at akregator_part.cpp:332
#25 0xb5b59fd2 in Akregator::Part::openStandardFeedList (this=0x812db68)
    at akregator_part.cpp:337
#26 0xb5b6c156 in Akregator::AkregatorPartIface::process (this=0x812dc14,
    fun=@0xbfc4c224, data=@0xbfc4c25c, replyType=@0xbfc4c1b4,
    replyData=@0xbfc4c1ac) at akregator_partiface_skel.cpp:39
#27 0xb6dd1fa8 in DCOPClient::receive (this=0x8063c38, objId=@0xbfc4c2a4,
    fun=@0xbfc4c224, data=@0xbfc4c25c, replyType=@0xbfc4c1b4,
    replyData=@0xbfc4c1ac) at dcopclient.cpp:1640
#28 0xb6dd27ee in DCOPClient::send (this=0x8063c38, remApp=@0xbfc4c29c,
    remObjId=@0xbfc4c2a4, remFun=@0xbfc4c224, data=@0xbfc4c25c)
    at dcopclient.cpp:1060
#29 0xb6dcba03 in DCOPRef::sendInternal (this=0xbfc4c29c, fun=@0xbfc4c2...

I also have a crash at sturtup. This is with Akregator 3.5.5 on Gentoo Linux. Here is the backtrace:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1244051760 (LWP 1558)]
[KCrash handler]
#6  c4_Column::PullValue (ptr_=@0xbfc4b634) at column.cpp:777
#7  0xb5967b73 in c4_FormatV::SetupAllSubviews (this=0x85bdbb8)
    at format.cpp:1026
#8  0xb59681ee in c4_FormatV::Get (this=0x85bdbb8, index_=0, 
    length_=@0xbfc4b69c) at format.cpp:1096
#9  0xb596b790 in c4_Handler::GetBytes (this=0x85bdbb8, index_=0, 
    buf_=@0xbfc4b710, copySmall_=false) at handler.cpp:58
#10 0xb597b237 in c4_Sequence::Get (this=0x85be370, index_=0, propId_=35, 
    buf_=@0xbfc4b710) at viewx.cpp:356
#11 0xb596fb4a in c4_Reference::GetData (this=0xbfc4b74c, buf_=@0xbfc4b710)
    at ./../include/mk4.inl:421
#12 0xb597aab7 in c4_ViewRef::operator c4_View (this=0xbfc4b74c)
    at viewx.cpp:643
#13 0xb5974e15 in c4_Storage::Description (this=0x855eea0, 
    name_=0xb4f0046a "articles") at store.cpp:360
#14 0xb597504d in c4_Storage::GetAs (this=0x855eea0, 
    description_=0xb5993924 "articles[guid:S,title:S,hash:I,guidIsHash:I,guidIsPermaLink:I,description:S,link:S,comments:I,commentsLink:S,status:I,pubDate:I,tags[tag:S],hasEnclosure:I,enclosureUrl:S,enclosureType:S,enclosureLengt"...)
    at store.cpp:279
#15 0xb5955279 in FeedStorageMK4Impl (this=0x85bdf70, url=@0x85bde00, 
    main=0x8091458) at feedstoragemk4impl.cpp:156
#16 0xb5958e7a in Akregator::Backend::StorageMK4Impl::archiveFor (
    this=0x8091458, url=@0x85bde00) at storagemk4impl.cpp:278
#17 0xb7f7b2e7 in Akregator::Feed::loadArticles (this=0x85bdd98)
    at feed.cpp:221
#18 0xb7f7c14a in Akregator::Feed::fromOPML (e=@0xbfc4bb84) at feed.cpp:165
#19 0xb7f878ba in Akregator::FeedList::parseChildNodes (this=0x82436d8, 
    node=@0xbfc4bbf4, parent=0x85bc180) at feedlist.cpp:117
#20 0xb7f8784d in Akregator::FeedList::parseChildNodes (this=0x82436d8, 
    node=@0xbfc4bd0c, parent=0x82435c0) at feedlist.cpp:135
#21 0xb7f87d74 in Akregator::FeedList::readFromXML (this=0x82436d8, 
    doc=@0xbfc4bebc) at feedlist.cpp:175
#22 0xb5b625fc in Akregator::View::loadFeeds (this=0x8093cf8, 
    doc=@0xbfc4bebc, parent=0x0) at akregator_view.cpp:541
#23 0xb5b59a22 in Akregator::Part::openFile (this=0x812db68)
    at akregator_part.cpp:443
#24 0xb5b56b94 in Akregator::Part::openURL (this=0x812db68, url=@0xbfc4bf84)
    at akregator_part.cpp:332
#25 0xb5b59fd2 in Akregator::Part::openStandardFeedList (this=0x812db68)
    at akregator_part.cpp:337
#26 0xb5b6c156 in Akregator::AkregatorPartIface::process (this=0x812dc14, 
    fun=@0xbfc4c224, data=@0xbfc4c25c, replyType=@0xbfc4c1b4, 
    replyData=@0xbfc4c1ac) at akregator_partiface_skel.cpp:39
#27 0xb6dd1fa8 in DCOPClient::receive (this=0x8063c38, objId=@0xbfc4c2a4, 
    fun=@0xbfc4c224, data=@0xbfc4c25c, replyType=@0xbfc4c1b4, 
    replyData=@0xbfc4c1ac) at dcopclient.cpp:1640
#28 0xb6dd27ee in DCOPClient::send (this=0x8063c38, remApp=@0xbfc4c29c, 
    remObjId=@0xbfc4c2a4, remFun=@0xbfc4c224, data=@0xbfc4c25c)
    at dcopclient.cpp:1060
#29 0xb6dcba03 in DCOPRef::sendInternal (this=0xbfc4c29c, fun=@0xbfc4c2c8, 
    args=@0xbfc4c264, data=@0xbfc4c25c) at dcopref.cpp:102
#30 0x080519a7 in DCOPRef::send (this=0xbfc4c29c, fun=@0xbfc4c2c8)
    at /usr/kde/3.5/include/dcopref.h:1118
#31 0x080513be in Akregator::Application::newInstance (this=0xbfc4ca80)
    at main.cpp:65
#32 0xb6f1c553 in KUniqueApplication::processDelayed (this=0xbfc4ca80)
    at kuniqueapplication.cpp:444
#33 0xb6f1c6d8 in KUniqueApplication::qt_invoke (this=0xbfc4ca80, _id=18, 
    _o=0xbfc4c458) at kuniqueapplication.moc:86
#34 0xb66fb1f3 in QObject::activate_signal (this=0x80e18f8, clist=0x80dc7f8, 
    o=0xbfc4c458) at kernel/qobject.cpp:2356
#35 0xb6af82e7 in QSignal::signal (this=0x80e18f8, t0=@0x80e1920)
    at .moc/debug-shared-mt/moc_qsignal.cpp:100
#36 0xb671f47b in QSignal::activate (this=0x80e18f8) at kernel/qsignal.cpp:212
#37 0xb672966c in QSingleShotTimer::event (this=0x80e18d0)
    at kernel/qtimer.cpp:286
#38 0xb6686923 in QApplication::internalNotify (this=0xbfc4ca80, 
    receiver=0x80e18d0, e=0xbfc4c7f8) at kernel/qapplication.cpp:2635
#39 0xb668889b in QApplication::notify (this=0xbfc4ca80, receiver=0x80e18d0, 
    e=0xbfc4c7f8) at kernel/qapplication.cpp:2358
#40 0xb6e7d1b2 in KApplication::notify (this=0xbfc4ca80, receiver=0x80e18d0, 
    event=0xbfc4c7f8) at kapplication.cpp:550
#41 0xb6610b1f in QApplication::sendEvent (receiver=0x80e18d0, 
    event=0xbfc4c7f8) at ../include/qapplication.h:496
#42 0xb6677738 in QEventLoop::activateTimers (this=0x80863c0)
    at kernel/qeventloop_unix.cpp:556
#43 0xb66270bb in QEventLoop::processEvents (this=0x80863c0, flags=4)
    at kernel/qeventloop_x11.cpp:389
#44 0xb66a493d in QEventLoop::enterLoop (this=0x80863c0)
    at kernel/qeventloop.cpp:198
#45 0xb66a475e in QEventLoop::exec (this=0x80863c0)
    at kernel/qeventloop.cpp:145
#46 0xb66885e7 in QApplication::exec (this=0xbfc4ca80)
    at kernel/qapplication.cpp:2758
#47 0x080510a8 in main (argc=) at main.cpp:110

Should I send the compressed folder of Akregator?

Revision history for this message

In KDE Bug Tracking System #116482, Jure Repinc (jlp) wrote on 2007-01-27:

#34

I just upgraded to 3.5.6 an the crash remains.

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2007-02-25:

#35

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

Revision history for this message

Sarah Kowalik (hobbsee-deactivatedaccount) wrote on 2007-03-20:

#5

will attempt to grab that patch post-beta

Changed in kdepim:
assignee:	nobody → hobbsee
status:	Unconfirmed → In Progress

Revision history for this message

Andrew Ash (ash211) wrote on 2007-04-22:

#6

Were you able to get that patch into feisty, hobbsee?

Revision history for this message

Sarah Kowalik (hobbsee-deactivatedaccount) wrote on 2007-04-28:

#7

no.

it'll be in kde 3.5.7, out soon.

Changed in kdepim:
status:	In Progress → Fix Committed

Revision history for this message

Sarah Kowalik (hobbsee-deactivatedaccount) wrote on 2007-05-22:

#8

fixed in gutsy. (or will be, when i get it uploaded)

Changed in kdepim:
status:	Fix Committed → Fix Released

Revision history for this message

In KDE Bug Tracking System #116482, Raul Sanchez Siles (rasasi78) wrote on 2007-05-27:

#36

Download full text (4.8 KiB)

Seems this is the right one. It happens to me as well on kde 3.5.7. This is my backtrace:
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1243031856 (LWP 9057)]
[KCrash handler]
#6 0xb7cbba1c in memcpy () from /lib/i686/cmov/libc.so.6
#7 0xb5707153 in c4_String::Init (this=0xb562cc6c, p=0x80aa39b, n=135651325)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mk4storage/metakit/src/string.cpp:212
#8 0xb571bb03 in c4_HandlerSeq::Prepare (this=0x80a9bb8, ptr_=0xbf8acc60,
 selfDesc_=true)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mk4storage/metakit/src/../include/mk4str.inl:209
#9 0xb571fea5 in c4_Persist::LoadAll (this=0x80aa2e8)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mk4storage/metakit/src/persist.cpp:1043
#10 0xb572010d in c4_Storage (this=0x80abf60,
 fname_=0x80aa138 "/home/rasasi/.kde/share/apps/akregator/Archive/archiveindex.mk4", mode_=1)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mk4storage/metakit/src/store.cpp:217
#11 0xb5702971 in Akregator::Backend::StorageMK4Impl::open (this=0x80a9da0,
 autoCommit=true)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mk4storage/storagemk4impl.cpp:129
#12 0xb5a17aab in Part (this=0x8116528, parentWidget=0x8098500,
 parent=0x8098500, name=0x8052f3d "akregator_part")
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/akregator_part.cpp:181
#13 0xb5a25808 in KParts::GenericFactory<Akregator::Part>::createPartObject (
 this=0x81102a8, parentWidget=0x8098500,
 widgetName=0x8052f3d "akregator_part", parent=0x8098500,
 name=0x8052f3d "akregator_part",
 className=0x8052f28 "KParts::ReadOnlyPart", args=@0xbf8acf00)
 at /usr/include/kde/kgenericfactory.tcc:146
#14 0xb7f6177f in KParts::Factory::createPart (this=0x81102a8,
 parentWidget=0x8098500, widgetName=0x8052f3d "akregator_part",
 parent=0x8098500, name=0x8052f3d "akregator_part",
 classname=0x8052f28 "KParts::ReadOnlyPart", args=@0xbf8acf00)
 at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kparts/factory.cpp:44
#15 0xb7f617e1 in KParts::Factory::createObject (this=0x81102a8,
 parent=0x8098500, name=0x8052f3d "akregator_part",
 classname=0x8052f28 "KParts::ReadOnlyPart", args=@0xbf8acf00)
 at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kparts/factory.cpp:80
#16 0xb76a3931 in KLibFactory::create (this=0x81102a8, parent=0x8098500,
 name=0x8052f3d "akregator_part",
 classname=0x8052f28 "KParts::ReadOnlyPart", args=@0xbf8acf00)
 at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/klibloader.cpp:83
#17 0x08051dc7 in Akregator::MainWindow::loadPart (this=0x8098500)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mainwindow.cpp:107
#18 0x080524e9 in Akregator::Application::newInstance (this=0xbf8ad690)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/main.cpp:61
#19 0xb7769b86 in KUniqueApplication::newInstanceNoFork (this=0xbf8ad690)
 at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kuniqueapplication.cpp:378
#20 0xb776ff28 in KUniqueApplication::qt_invoke (this=0xbf8ad690, _id=20,
 _o=0xbf8ad098) at ./kuniqueapplication.moc:87
#21 0xb70a9e1b in QObject::activate_signal (this=0x809dff8, clist=0x8095650,
 o=0xbf8a...

Seems this is the right one. It happens to me as well on kde 3.5.7. This is my backtrace:
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1243031856 (LWP 9057)]
[KCrash handler]
#6 0xb7cbba1c in memcpy () from /lib/i686/cmov/libc.so.6
#7 0xb5707153 in c4_String::Init (this=0xb562cc6c, p=0x80aa39b, n=135651325)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mk4storage/metakit/src/string.cpp:212
#8 0xb571bb03 in c4_HandlerSeq::Prepare (this=0x80a9bb8, ptr_=0xbf8acc60, 
 selfDesc_=true)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mk4storage/metakit/src/../include/mk4str.inl:209
#9 0xb571fea5 in c4_Persist::LoadAll (this=0x80aa2e8)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mk4storage/metakit/src/persist.cpp:1043
#10 0xb572010d in c4_Storage (this=0x80abf60, 
 fname_=0x80aa138 "/home/rasasi/.kde/share/apps/akregator/Archive/archiveindex.mk4", mode_=1)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mk4storage/metakit/src/store.cpp:217
#11 0xb5702971 in Akregator::Backend::StorageMK4Impl::open (this=0x80a9da0, 
 autoCommit=true)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mk4storage/storagemk4impl.cpp:129
#12 0xb5a17aab in Part (this=0x8116528, parentWidget=0x8098500, 
 parent=0x8098500, name=0x8052f3d "akregator_part")
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/akregator_part.cpp:181
#13 0xb5a25808 in KParts::GenericFactory<Akregator::Part>::createPartObject (
 this=0x81102a8, parentWidget=0x8098500, 
 widgetName=0x8052f3d "akregator_part", parent=0x8098500, 
 name=0x8052f3d "akregator_part", 
 className=0x8052f28 "KParts::ReadOnlyPart", args=@0xbf8acf00)
 at /usr/include/kde/kgenericfactory.tcc:146
#14 0xb7f6177f in KParts::Factory::createPart (this=0x81102a8, 
 parentWidget=0x8098500, widgetName=0x8052f3d "akregator_part", 
 parent=0x8098500, name=0x8052f3d "akregator_part", 
 classname=0x8052f28 "KParts::ReadOnlyPart", args=@0xbf8acf00)
 at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kparts/factory.cpp:44
#15 0xb7f617e1 in KParts::Factory::createObject (this=0x81102a8, 
 parent=0x8098500, name=0x8052f3d "akregator_part", 
 classname=0x8052f28 "KParts::ReadOnlyPart", args=@0xbf8acf00)
 at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kparts/factory.cpp:80
#16 0xb76a3931 in KLibFactory::create (this=0x81102a8, parent=0x8098500, 
 name=0x8052f3d "akregator_part", 
 classname=0x8052f28 "KParts::ReadOnlyPart", args=@0xbf8acf00)
 at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/klibloader.cpp:83
#17 0x08051dc7 in Akregator::MainWindow::loadPart (this=0x8098500)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/mainwindow.cpp:107
#18 0x080524e9 in Akregator::Application::newInstance (this=0xbf8ad690)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/main.cpp:61
#19 0xb7769b86 in KUniqueApplication::newInstanceNoFork (this=0xbf8ad690)
 at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kuniqueapplication.cpp:378
#20 0xb776ff28 in KUniqueApplication::qt_invoke (this=0xbf8ad690, _id=20, 
 _o=0xbf8ad098) at ./kuniqueapplication.moc:87
#21 0xb70a9e1b in QObject::activate_signal (this=0x809dff8, clist=0x8095650, 
 o=0xbf8ad098) at kernel/qobject.cpp:2356
#22 0xb7432f87 in QSignal::signal (this=0x809dff8, t0=@0x809e020)
 at .moc/debug-shared-mt/moc_qsignal.cpp:100
#23 0xb70c999e in QSignal::activate (this=0x809dff8) at kernel/qsignal.cpp:212
#24 0xb70d1370 in QSingleShotTimer::event (this=0x809dfd0)
 at kernel/qtimer.cpp:286
#25 0xb7041cf2 in QApplication::internalNotify (this=0xbf8ad690, 
 receiver=0x809dfd0, e=0xbf8ad408) at kernel/qapplication.cpp:2635
#26 0xb7043b0f in QApplication::notify (this=0xbf8ad690, receiver=0x809dfd0, 
 e=0xbf8ad408) at kernel/qapplication.cpp:2358
#27 0xb775b142 in KApplication::notify (this=0xbf8ad690, receiver=0x809dfd0, 
 event=0xbf8ad408)
 at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kapplication.cpp:550
#28 0xb6fd54c1 in QApplication::sendEvent (receiver=0x809dfd0, 
 event=0xbf8ad408) at ../include/qapplication.h:520
#29 0xb70346c3 in QEventLoop::activateTimers (this=0x806e5e0)
 at kernel/qeventloop_unix.cpp:556
#30 0xb6fe980f in QEventLoop::processEvents (this=0x806e5e0, flags=4)
 at kernel/qeventloop_x11.cpp:389
#31 0xb705c245 in QEventLoop::enterLoop (this=0x806e5e0)
 at kernel/qeventloop.cpp:198
#32 0xb705c066 in QEventLoop::exec (this=0x806e5e0)
 at kernel/qeventloop.cpp:145
#33 0xb704388b in QApplication::exec (this=0xbf8ad690)
 at kernel/qapplication.cpp:2758
#34 0x0805174e in main (argc=)
 at /tmp/buildd/kdepim-3.5.7/./akregator/src/main.cpp:112
#35 0xb7c61ebc in __libc_start_main () from /lib/i686/cmov/libc.so.6
#36 0x08050a21 in _start ()

And also I'll attach a tarball for the ~/.kde/share/apps/akregator dir which makes possible to reproduce the problem. A little later I'll try to isolate the blaming corrupted file.

Revision history for this message

In KDE Bug Tracking System #116482, Raul Sanchez Siles (rasasi78) wrote on 2007-05-27:

#37

The file I got is 6MB, unfortunately I have no web space available. If you are interested on it, please let me know and also how should I send it to you.

Revision history for this message

In KDE Bug Tracking System #116482, Jack Bunce (jackbunce) wrote on 2007-05-29:

#38

Download full text (3.5 KiB)

I am having a crash on Startup also. It started after an update to KDE 3.5.7 release 10.1 which was followed by a power hit which caused the computer to restart. I am not certain which was the cause of the problem. Here is the trace:

System configuration startup check disabled.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1235679536 (LWP 13322)]
[KCrash handler]
#9 0xb6f444cc in memcpy () from /lib/libc.so.6
#10 0xb59e22c3 in c4_String::Init ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#11 0xb59d90d3 in c4_HandlerSeq::Prepare ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#12 0xb59dcaa5 in c4_Persist::LoadAll ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#13 0xb59e170d in c4_Storage::c4_Storage ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#14 0xb59c5b06 in Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#15 0xb59c7f21 in Akregator::Backend::StorageMK4Impl::archiveFor ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#16 0xb7f422c8 in Akregator::Feed::loadArticles ()
   from /opt/kde3/lib/libakregatorprivate.so
#17 0xb7f43030 in Akregator::Feed::fromOPML ()
   from /opt/kde3/lib/libakregatorprivate.so
#18 0xb7f4d805 in Akregator::FeedList::parseChildNodes ()
   from /opt/kde3/lib/libakregatorprivate.so
#19 0xb7f4d90c in Akregator::FeedList::parseChildNodes ()
   from /opt/kde3/lib/libakregatorprivate.so
#20 0xb7f4dd7e in Akregator::FeedList::readFromXML ()
   from /opt/kde3/lib/libakregatorprivate.so
#21 0xb6274cdc in Akregator::View::loadFeeds ()
   from /opt/kde3/lib/kde3/libakregatorpart.so
#22 0xb62703ab in Akregator::Part::openFile ()
   from /opt/kde3/lib/kde3/libakregatorpart.so
#23 0xb626df4c in Akregator::Part::openURL ()
   from /opt/kde3/lib/kde3/libakregatorpart.so
#24 0xb626a91b in Akregator::Part::openStandardFeedList ()
   from /opt/kde3/lib/kde3/libakregatorpart.so
#25 0xb6269770 in Akregator::AkregatorPartIface::process ()
   from /opt/kde3/lib/kde3/libakregatorpart.so
#26 0xb7812e77 in DCOPClient::receive () from /opt/kde3/lib/libDCOP.so.4
#27 0xb7813602 in DCOPClient::send () from /opt/kde3/lib/libDCOP.so.4
#28 0xb7813c3f in DCOPRef::sendInternal () from /opt/kde3/lib/libDCOP.so.4
#29 0x08050796 in Akregator::Application::newInstance ()
#30 0xb798f26d in KUniqueApplication::processDelayed ()
   from /opt/kde3/lib/libkdecore.so.4
#31 0xb79d4eb8 in KUniqueApplication::qt_invoke ()
   from /opt/kde3/lib/libkdecore.so.4
#32 0xb738bf1d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0xb76c70ae in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0xb73a7ff7 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0xb73af383 in QSingleShotTimer::event ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0xb732c9c7 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0xb732d791 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#38 0xb79e4202 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#39 0xb7321bd3 in QEventL...

I am having a crash on Startup also.  It started after an update to KDE 3.5.7 release 10.1 which was followed by a power hit which caused the computer to restart. I am not certain which was the cause of the problem. Here is the trace:

System configuration startup check disabled.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1235679536 (LWP 13322)]
[KCrash handler]
#9  0xb6f444cc in memcpy () from /lib/libc.so.6
#10 0xb59e22c3 in c4_String::Init ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#11 0xb59d90d3 in c4_HandlerSeq::Prepare ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#12 0xb59dcaa5 in c4_Persist::LoadAll ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#13 0xb59e170d in c4_Storage::c4_Storage ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#14 0xb59c5b06 in Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#15 0xb59c7f21 in Akregator::Backend::StorageMK4Impl::archiveFor ()
   from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so
#16 0xb7f422c8 in Akregator::Feed::loadArticles ()
   from /opt/kde3/lib/libakregatorprivate.so
#17 0xb7f43030 in Akregator::Feed::fromOPML ()
   from /opt/kde3/lib/libakregatorprivate.so
#18 0xb7f4d805 in Akregator::FeedList::parseChildNodes ()
   from /opt/kde3/lib/libakregatorprivate.so
#19 0xb7f4d90c in Akregator::FeedList::parseChildNodes ()
   from /opt/kde3/lib/libakregatorprivate.so
#20 0xb7f4dd7e in Akregator::FeedList::readFromXML ()
   from /opt/kde3/lib/libakregatorprivate.so
#21 0xb6274cdc in Akregator::View::loadFeeds ()
   from /opt/kde3/lib/kde3/libakregatorpart.so
#22 0xb62703ab in Akregator::Part::openFile ()
   from /opt/kde3/lib/kde3/libakregatorpart.so
#23 0xb626df4c in Akregator::Part::openURL ()
   from /opt/kde3/lib/kde3/libakregatorpart.so
#24 0xb626a91b in Akregator::Part::openStandardFeedList ()
   from /opt/kde3/lib/kde3/libakregatorpart.so
#25 0xb6269770 in Akregator::AkregatorPartIface::process ()
   from /opt/kde3/lib/kde3/libakregatorpart.so
#26 0xb7812e77 in DCOPClient::receive () from /opt/kde3/lib/libDCOP.so.4
#27 0xb7813602 in DCOPClient::send () from /opt/kde3/lib/libDCOP.so.4
#28 0xb7813c3f in DCOPRef::sendInternal () from /opt/kde3/lib/libDCOP.so.4
#29 0x08050796 in Akregator::Application::newInstance ()
#30 0xb798f26d in KUniqueApplication::processDelayed ()
   from /opt/kde3/lib/libkdecore.so.4
#31 0xb79d4eb8 in KUniqueApplication::qt_invoke ()
   from /opt/kde3/lib/libkdecore.so.4
#32 0xb738bf1d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0xb76c70ae in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0xb73a7ff7 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0xb73af383 in QSingleShotTimer::event ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0xb732c9c7 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0xb732d791 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#38 0xb79e4202 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#39 0xb7321bd3 in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#40 0xb72dbc40 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#41 0xb73437f0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#42 0xb7343686 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#43 0xb732c57f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#44 0x0805025e in main ()

Revision history for this message

In KDE Bug Tracking System #116482, Rosenauer (rosenauer) wrote on 2007-06-21:

#39

same here on Kubuntu Feisty KDE 3.5.7.
Akregator does not start but eats 100% CPU until killed.
Removing my feeds (the OPML-file) "help" in that starting Akregator produces a normal crash.
Only when removing the Archive-folder in .kde/share/apps/akregator, Akregator starts up normally again.
Mine is only 450K so I'll attach it here.
This has happened before already, so I know the procedure, but I don't know the cause. I am using Akregator embedded in Kontact, maybe the Akregator-Archive got corrupted when Kontact crashed.

Revision history for this message

In KDE Bug Tracking System #116482, Rosenauer (rosenauer) wrote on 2007-06-21:

#40

Created attachment 20916
problematic feed-archive

when uncompressing this archive to your akregator-configdir, akregator will
crash at startup.

Revision history for this message

In KDE Bug Tracking System #116482, Chain (chain) wrote on 2007-06-22:

#41

You can check your files with the utilities on their page.
http://www.equi4.com/metakit/stats.html

I had a problem with my harddrive and a file got corrupted. Unfortunately it cannot repair, but the one defective file removed, everything works again :)

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2008-01-13:

#42

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

Revision history for this message

grauscho (grauscho) wrote on 2008-03-03:

#9

When shutting down three days ago, there was a kernel panic before syncing the disks.

After that, akregator crashed, too. I'm running KDE 3.5.8, Kontact
Version 1.2.4 (enterprise 0.20070907.709405) on Gutsy.

To resolve this, I deleted two files in .kde/share/apps/akregator: lock and lockPgRNWa.new.

akregator seems to work again now.

Revision history for this message

In KDE Bug Tracking System #116482, Pnemec (pnemec) wrote on 2008-03-18:

#43

reproducet with openSUSE 10.3. KDE 3.5.7 novell bugzilla #371701. I am contacting Frank with PM.

Revision history for this message

In KDE Bug Tracking System #116482, Thomas Koch (thomas-koch-ro) wrote on 2008-04-15:

#44

I had a similiar problem. For me akregator just freezed. I did a
lsof -p AKREGATORPID
to see the files opened by akregator. The last file opened was a .mk4 file inside ~/.kde/share/apps/akregator/Archive

You can get the AKREGATORPID with
ps aux|grep akregator

After renaming the last file listed by lsof, akregator started again, but the respective feed did not have any archived entries anymore. Now I'd like to know, how to resque a corrupted .mk4 file...

Revision history for this message

In KDE Bug Tracking System #116482, Chris-fritz (chris-fritz) wrote on 2008-06-01:

#45

Created attachment 25029
Working and broken copies of an .mk4 file, and associated feeds.opml file.

This zip file contains a data folder with the feeds.opml and an Archive folder
with two .mk4 files.

One .mk4 file is my original from using a KDE 3.5 release of Akregator (program
version unknown, I'm afraid). This one has .BROKEN appended to the filename.

The other .mk4 file is one freshly created by Akregator Version 1.2.50, on KDE
4.00.72, everything installed on Fedora 9 via from RPM.

I use Okteta (or KHexedit on KDE 3.X) to view the files and modify them.

(Note: At roughly location 0x23A0 in the .BROKEN file, the text is corrupted.
This has no negative impact on loading the file.)

The .BROKEN file ends at roughly location 0x24020. At this point, the .WORKING
continues with more data.

If I delete the contents of .BROKEN from 0x3F00 to the end of the file, and
then paste onto the end the contents of .WORKING from 0x23F00 to the end of
that file, the .BROKEN file will load successfully in Akregator (assuming I've
renamed it to remove the ".BROKEN" from the filename).

I don't know how to put together an environment for editing/building source
code, so I can't look into this problem in any more depth.

Revision history for this message

In KDE Bug Tracking System #116482, Chris-fritz (chris-fritz) wrote on 2008-06-01:

#46

Correction to my comment:

"If I delete the contents of .BROKEN from 0x3F00 to the end of the file"

...should read:
If I delete the contents of .BROKEN from 0x23F00 to the end of the file

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2008-07-24:

#47

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2008-07-24:

#48

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2008-07-24:

#49

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

Revision history for this message

In KDE Bug Tracking System #116482, Goetzchrist-m (goetzchrist-m) wrote on 2008-07-29:

#50

I have the same crash using KDE 4.1 from Kubuntu Members PPA in Hardy:

The application Akregator (akregator) crashed and caused the signal 11 (SIGSEGV).

Backtrace:

Application: Akregator (akregator), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)

... 37 times more ...

(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5424720 (LWP 6276)]
(no debugging symbols found)
(no debugging symbols found)

... 75 times more ...

(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb3d48b25 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#7 0xb3d48be1 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#8 0xb3d44454 in Akregator::FeedList::findByURL ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#9 0xb3d4570c in Akregator::FeedList::findArticle ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#10 0xb3d2c66a in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#11 0xb3d2c853 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#12 0xb77b84f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb77b8bc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb77bf037 in ?? () from /usr/lib/libQtCore.so.4
#15 0xb77bf15c in ?? () from /usr/lib/libQtCore.so.4
#16 0xb77b3c9a in QObject::event () from /usr/lib/libQtCore.so.4
#17 0xb6e02c0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#18 0xb6e07799 in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0xb7c32ef3 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#20 0xb77a36a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#21 0xb77d11a1 in ?? () from /usr/lib/libQtCore.so.4
#22 0xb77cea40 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb5bbfbf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb5bc2e5e in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb5bc33ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb77cef98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#27 0xb6e96195 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb77a292d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#29 0xb77a2abd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#30 0xb77a4d3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#31 0xb6e02567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#32 0x0804edab in _start ()
#0 0xb7efe410 in __kernel_vsyscall ()

I have the same crash using KDE 4.1 from Kubuntu Members PPA in Hardy:

The application Akregator (akregator) crashed and caused the signal 11 (SIGSEGV).

Backtrace:

Application: Akregator (akregator), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)

... 37 times more ...

(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5424720 (LWP 6276)]
(no debugging symbols found)
(no debugging symbols found)

... 75 times more ...

(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb3d48b25 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#7  0xb3d48be1 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#8  0xb3d44454 in Akregator::FeedList::findByURL ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#9  0xb3d4570c in Akregator::FeedList::findArticle ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#10 0xb3d2c66a in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#11 0xb3d2c853 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#12 0xb77b84f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb77b8bc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb77bf037 in ?? () from /usr/lib/libQtCore.so.4
#15 0xb77bf15c in ?? () from /usr/lib/libQtCore.so.4
#16 0xb77b3c9a in QObject::event () from /usr/lib/libQtCore.so.4
#17 0xb6e02c0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#18 0xb6e07799 in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0xb7c32ef3 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#20 0xb77a36a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#21 0xb77d11a1 in ?? () from /usr/lib/libQtCore.so.4
#22 0xb77cea40 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb5bbfbf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb5bc2e5e in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb5bc33ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb77cef98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#27 0xb6e96195 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb77a292d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#29 0xb77a2abd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#30 0xb77a4d3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#31 0xb6e02567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#32 0x0804edab in _start ()
#0  0xb7efe410 in __kernel_vsyscall ()

Revision history for this message

In KDE Bug Tracking System #116482, Goetzchrist-m (goetzchrist-m) wrote on 2008-07-29:

#51

Also, when removing the folder ~/.kde4/share/apps/akregator/Archive Akregator starts again.

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2008-08-13:

#52

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

Revision history for this message

In KDE Bug Tracking System #116482, Goetzchrist-m (goetzchrist-m) wrote on 2008-08-14:

#53

I realized that when I set a limit to the Archive size, at the next startup Akregator crashes if the archive limit is exceeded.

Revision history for this message

In KDE Bug Tracking System #116482, Datradan (datradan) wrote on 2008-08-16:

#54

Download full text (9.0 KiB)

I have the same problem with KDE 4.1.0 from Kubuntu Members PPA in Hardy, like G. Christ in comment #40.

Here my backtrace (without "(no debugging symbols found)":

Application: Akregator (akregator), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb545c720 (LWP 6958)]
[KCrash handler]
#6 0xb3d65b29 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#7 0xb3d65be1 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#8 0xb3d61454 in Akregator::FeedList::findByURL ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#9 0xb3d6270c in Akregator::FeedList::findArticle ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#10 0xb3d4966a in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#11 0xb3d49853 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#12 0xb77f24f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb77f2bc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb77f9037 in ?? () from /usr/lib/libQtCore.so.4
#15 0xb77f915c in ?? () from /usr/lib/libQtCore.so.4
#16 0xb77edc9a in QObject::event () from /usr/lib/libQtCore.so.4
#17 0xb6e3dc0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#18 0xb6e427a9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0xb7c74f53 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#20 0xb77dd6a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#21 0xb780b1a1 in ?? () from /usr/lib/libQtCore.so.4
#22 0xb7808a40 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb5bf9dd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb5bfd193 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb5bfd74e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb7808f98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#27 0xb6ed11b5 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb77dc92d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#29 0xb77dcabd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#30 0xb77ded3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#31 0xb6e3d567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#32 0x0804edab in _start ()
#0 0xb7f3f410 in __kernel_vsyscall ()

and here terminal messages when i run akregator:

othmane@kubuntu:~/Desktop$ akregator
akregator(6958) Akregator::PluginManager::query: Plugin trader constraint: "[X-KDE-akregator-framework-version] == 2 and [X-KDE-akregator-plugintype] == 'storage' and [X-KDE-akregator-rank] > 0"
akregator(6958) Akregator::PluginManager::createFromService: Trying to load: "akregator_mk4storage_plugin"
akregator(6958) Akregator::PluginManager::dump: PluginManager Service Info:
---------------------------
name : "Metakit storage ...

I have the same problem with KDE 4.1.0 from Kubuntu Members PPA in Hardy, like G. Christ in comment #40.

Here my backtrace (without "(no debugging symbols found)":

Application: Akregator (akregator), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb545c720 (LWP 6958)]
[KCrash handler]
#6  0xb3d65b29 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#7  0xb3d65be1 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#8  0xb3d61454 in Akregator::FeedList::findByURL ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#9  0xb3d6270c in Akregator::FeedList::findArticle ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#10 0xb3d4966a in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#11 0xb3d49853 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#12 0xb77f24f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb77f2bc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb77f9037 in ?? () from /usr/lib/libQtCore.so.4
#15 0xb77f915c in ?? () from /usr/lib/libQtCore.so.4
#16 0xb77edc9a in QObject::event () from /usr/lib/libQtCore.so.4
#17 0xb6e3dc0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#18 0xb6e427a9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0xb7c74f53 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#20 0xb77dd6a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#21 0xb780b1a1 in ?? () from /usr/lib/libQtCore.so.4
#22 0xb7808a40 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb5bf9dd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb5bfd193 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb5bfd74e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb7808f98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#27 0xb6ed11b5 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb77dc92d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#29 0xb77dcabd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#30 0xb77ded3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#31 0xb6e3d567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#32 0x0804edab in _start ()
#0  0xb7f3f410 in __kernel_vsyscall ()

and here terminal messages when i run akregator:

othmane@kubuntu:~/Desktop$ akregator 
akregator(6958) Akregator::PluginManager::query: Plugin trader constraint: "[X-KDE-akregator-framework-version] == 2 and [X-KDE-akregator-plugintype] == 'storage' and [X-KDE-akregator-rank] > 0" 
akregator(6958) Akregator::PluginManager::createFromService: Trying to load: "akregator_mk4storage_plugin" 
akregator(6958) Akregator::PluginManager::dump: PluginManager Service Info: 
--------------------------- 
name : "Metakit storage backend" 
library : "akregator_mk4storage_plugin" 
desktopEntryPath : "akregator_mk4storage_plugin.desktop" 
X-KDE-akregator-plugintype : "storage" 
X-KDE-akregator-name : "metakit" 
X-KDE-akregator-authors : ("Frank Osterfeld") 
X-KDE-akregator-rank : "255" 
X-KDE-akregator-version : "1" 
X-KDE-akregator-framework-version: "2" 
Object::connect: No such signal Akregator::SubscriptionListView::signalContextMenu(K3ListView*,Akregator::TreeNode*,QPoint) 
Object::connect: (sender name: 'feedtree') 
Object::connect: (receiver name: 'akregator_view') 
Object::connect: No such signal Akregator::SubscriptionListView::signalDropped(KUrl::List&,Akregator::TreeNode*,Akregator::Folder*) 
Object::connect: (sender name: 'feedtree') 
Object::connect: (receiver name: 'akregator_view') 
Object::connect: No such slot Akregator::ArticleListView::slotPaletteOrFontChanged() 
akregator(6958) Akregator::SubscriptionListView::loadHeaderSettings: 0 210 
akregator(6958) Akregator::SubscriptionListView::loadHeaderSettings: 1 56 
akregator(6958) Akregator::SubscriptionListView::loadHeaderSettings: 2 58 
Object::disconnect: Unexpected null parameter 
akregator(6958) Akregator::Part::initFonts: Part::initFonts(): set UnderlineLinks to true 
akregator(6958) Akregator::FeedList::readFromOpml: loading OPML feed "opml" 
akregator(6958) Akregator::FeedList::readFromOpml: measuring startup time: START 
akregator(6958) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://feeds.feedburner.com/7yearwinter" 
akregator(6958) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://feeds.feedburner.com/Blu" 
akregator(6958) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://feeds.feedburner.com/oneOpenSource" 
akregator(6958) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://feeds.feedburner.com/pollycokenet" 
akregator(6958) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://www.kde.org/dotkdeorg.rdf" 
akregator(6958) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://www.kubuntu.org/news/feed" 
akregator(6958) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://pinheiro-kde.blogspot.com/feeds/posts/default" 
akregator(6958) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://aseigo.blogspot.com/feeds/posts/default" 
akregator(6958) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://www.repubblica.it/rss/homepage/rss2.0.xml" 
akregator(6958) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://www.corriere.it/rss/homepage.xml" 
akregator(6958) Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl: "http://www.lastampa.it/redazione/rss_home.xml" 
akregator(6958) Akregator::FeedList::readFromOpml: measuring startup time: STOP, 556 ms 
akregator(6958) Akregator::FeedList::readFromOpml: Number of articles loaded: 1019 
akregator(6958) Akregator::SubscriptionListView::loadHeaderSettings: 0 210 
akregator(6958) Akregator::SubscriptionListView::loadHeaderSettings: 1 56 
akregator(6958) Akregator::SubscriptionListView::loadHeaderSettings: 2 58 
KCrash: crashing... crashRecursionCounter = 2 
KCrash: Application Name = akregator path = <unknown> pid = 6958 
sock_file=/home/othmane/.kde4/socket-kubuntu/kdeinit4__0

I think the same thing of G.Christ in comment #43.

Revision history for this message

In KDE Bug Tracking System #116482, Datradan (datradan) wrote on 2008-08-17:

#55

I've found why akreagator crash,
in ~/.kde4/share/apps/akregator/data/feeds.oplm , when I increase maxArticleNumber over my number of feeds saved, and I set archiveMode="globalDefault", akregator will not crash.

I hope this is useful to resolve this bug :-)

Revision history for this message

In KDE Bug Tracking System #116482, Goetzchrist-m (goetzchrist-m) wrote on 2008-09-26:

#56

I have still the same issue, but now in openSUSE 11 with KDE 4.1.1 and Akregator 1.3.1.

If the saved feeds number is bigger than the limit to save, Akregator will crash at the next startup.

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2008-10-19:

#57

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

Revision history for this message

In KDE Bug Tracking System #116482, Dominik Tritscher (dominik-tritscher) wrote on 2008-11-09:

#58

I Played arrount a bit with the maxArticleNumber and removed the archiveMode="globalDefault". I wasn't able to crash Akregator 1.3.3 at startup.

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2009-05-14:

#59

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-06-18:

#60

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

Revision history for this message

In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote on 2009-06-20:

#61

I think this could be another instance of bug 191685, based on its duplicates.

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-06-21:

#62

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

Revision history for this message

In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote on 2009-06-28:

#63

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-07-04:

#64

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

Revision history for this message

In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote on 2009-07-07:

#65

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-07-09:

#66

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-07-15:

#67

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2009-08-02:

#68

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-08-15:

#69

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-08-19:

#70

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-08-20:

#71

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-08-25:

#72

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-08-25:

#73

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-08-26:

#74

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

Revision history for this message

In KDE Bug Tracking System #116482, Samuel-brack (samuel-brack) wrote on 2009-08-26:

#75

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-09-02:

#76

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-09-03:

#77

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-09-12:

#78

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

Revision history for this message

In KDE Bug Tracking System #116482, Heimen Stoffels (vistaus) wrote on 2009-09-12:

#79

Any updates on this? It still happens on KDE 4.3.1:

https://bugs.kde.org/show_bug.cgi?id=207180

Revision history for this message

In KDE Bug Tracking System #116482, T-artem (t-artem) wrote on 2009-09-12:

#80

Updates? 36 duplicates and still counting. :)

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-09-15:

#81

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-09-26:

#82

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-10-07:

#83

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-10-11:

#84

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-10-11:

#85

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

Revision history for this message

In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote on 2009-10-12:

#86

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-10-20:

#87

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

Revision history for this message

In KDE Bug Tracking System #116482, Seba78 (teo78) wrote on 2009-10-24:

#88

On Lun 19 Oct 2009 20:44:11 Christophe Giboudeaux escribió:
> https://bugs.kde.org/show_bug.cgi?id=116482
>
>
> Christophe Giboudeaux <email address hidden> changed:
>
> What |Removed |Added
> ---------------------------------------------------------------------------
>- CC| |<email address hidden>
>
>
>
>
> --- Comment #77 from Christophe Giboudeaux <cgiboudeaux
gmail com>
> 2009-10-20 00:44:06 --- *** Bug 211092 has been marked as a
duplicate of
> this bug. ***

Revision history for this message

In KDE Bug Tracking System #116482, Heimen Stoffels (vistaus) wrote on 2009-10-24:

#89

What's the status of this bug? Because it's still not fixed...

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-10-28:

#90

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-10-29:

#91

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-10-30:

#92

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-11-01:

#93

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-11-04:

#94

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

Revision history for this message

In KDE Bug Tracking System #116482, FranJPR (fjperezor) wrote on 2009-11-06:

#95

I have installed kubuntu 9.10 karmic and this bug has been fixed in Akregator. I have been able to import a huge number of feeds without problems.

Great!

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-11-12:

#96

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-11-15:

#97

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-11-27:

#98

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-11-27:

#99

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-11-27:

#100

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-11-30:

#101

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

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2009-12-02:

#102

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-12-04:

#103

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

Revision history for this message

In KDE Bug Tracking System #116482, Primoz (papic644) wrote on 2009-12-04:

#104

I think I might have solved the bug, at least for me...
You just delete feeds.opml and it should work... But you do lose all of the feeds....

Revision history for this message

In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote on 2009-12-06:

#105

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-12-07:

#106

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

Revision history for this message

In KDE Bug Tracking System #116482, Psychonaut (psychonaut) wrote on 2009-12-10:

#107

As per Comment #94, deleting feeds.opml has suppressed this bug for me. As I don't use Akregator any more, this is an acceptable workaround for me, though obviously it may not be for others.

Revision history for this message

In KDE Bug Tracking System #116482, helios (martin-lichtvoll) wrote on 2009-12-10:

#108

Strangely enough I have not seen this in ages. I think last time I had such a crash was with some KDE 3.x version. I do not thing I had Akregator crashing at startup with any KDE 4.x version - currently using 4.3.2 debian packages. And I use it with a quite insane amount of newsfeeds ;-). At least more as 50 estimated quickly totalling to more than 139600 unread messages. My ~/.kde/share/apps/akregator directory is 303MiB big.

Would be interesting to know who updated akregator with data from KDE 3.x to 4.x and who started clean with 3.x. Maybe on update it might make sense to recreate feeds.opml?

Revision history for this message

In KDE Bug Tracking System #116482, helios (martin-lichtvoll) wrote on 2009-12-10:

#109

thing=>think. And who started clean with 4.x of course.

Revision history for this message

In KDE Bug Tracking System #116482, Nicolás Alvarez (nicolas-alvarez) wrote on 2009-12-10:

#110

I think this is pretty simple. If your amarok is crashing, and moving feeds.opml away* makes it stop crashing, please post your file here so a developer can reproduce the problem, since it must be a problem in it.

(* Don't delete it!)

Revision history for this message

In KDE Bug Tracking System #116482, Christopherheiny (christopherheiny) wrote on 2009-12-10:

#111

Discarding all feeds is *not* an acceptable solution, especially for those of us with large numbers of feeds. Sort of in the line of "removing the patient's head to prevent further sneezing" :-)

Anyway, yesterday afternoon I pulled down the latest Fedora 12 updates, and this problem has mysteriously cured itself (at least on my machine).

Revision history for this message

In KDE Bug Tracking System #116482, Nicolás Alvarez (nicolas-alvarez) wrote on 2009-12-10:

#112

Well, I wasn't saying removing all feeds was a *solution*.

"If replacing the patient's head makes him stop sneezing (which some people -*already* tried), the problem was indeed in the head; please sends us the old head so we can track down the sneezing cause in more detail" :)

Revision history for this message

In KDE Bug Tracking System #116482, Alexo-tmp (alexo-tmp) wrote on 2009-12-11:

#113

Created attachment 38978
/home/alex/.kde4/share/apps/akregator/Archive/feedlistbackup.mk4

Revision history for this message

In KDE Bug Tracking System #116482, Mark Rose (markrose) wrote on 2009-12-12:

#114

This feed was causing akregator to crash on startup, and crash when I add it.

http://feeds.feedburner.com/corbettreport_articles

It does NOT parse correctly. Here is the malformed entry:

<item>
 <title>UK Group Proposes Using Carbon Offsets to Stop Poor From Breeding</title>
 <description>Carbon hysteria reaches its logical conclusion</description>
 <linkhttp://www.corbettreport.com/articles/20091209_optimum_population.htm</link>
 </item>

Apparently this wasn't an issue, as until I upgraded to Kubuntu 9.10 (with KDE 4.3.2), I never had this issue with this malformed feed (I've been starting Kontact successfully every day).

Revision history for this message

In KDE Bug Tracking System #116482, Dominik Tritscher (dominik-tritscher) wrote on 2009-12-12:

#115

Download full text (9.8 KiB)

I can reproduce the crash with the feed posted by Mark Rose using KDE 4.3.4 from Kubuntu packages. But according to the backtrace, this seems to be a QT issue not an akregator one. But anyway, here is the backtrace:

Application: Kontact (kontact), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5 QDomNodePrivate::setLocation (this=0x7fffd69ae5c0, nsURI=<value optimized out>, qName=<value optimized out>, atts=...) at dom/qdom.cpp:1923
#6 QDomHandler::startElement (this=0x7fffd69ae5c0, nsURI=<value optimized out>, qName=<value optimized out>, atts=...) at dom/qdom.cpp:7418
#7 0x00007f72a5b8aae7 in QXmlSimpleReaderPrivate::processElementEmptyTag (this=0x3c326b0) at sax/qxml.cpp:3987
#8 0x00007f72a5b96df8 in QXmlSimpleReaderPrivate::parseElement (this=0x3c326b0) at sax/qxml.cpp:3955
#9 0x00007f72a5b96288 in QXmlSimpleReaderPrivate::parseContent (this=0x3c326b0) at sax/qxml.cpp:4408
#10 0x00007f72a5b96d70 in QXmlSimpleReaderPrivate::parseElement (this=0x3c326b0) at sax/qxml.cpp:3934
#11 0x00007f72a5b96288 in QXmlSimpleReaderPrivate::parseContent (this=0x3c326b0) at sax/qxml.cpp:4408
#12 0x00007f72a5b96d70 in QXmlSimpleReaderPrivate::parseElement (this=0x3c326b0) at sax/qxml.cpp:3934
#13 0x00007f72a5b96288 in QXmlSimpleReaderPrivate::parseContent (this=0x3c326b0) at sax/qxml.cpp:4408
#14 0x00007f72a5b96d70 in QXmlSimpleReaderPrivate::parseElement (this=0x3c326b0) at sax/qxml.cpp:3934
#15 0x00007f72a5b971d8 in QXmlSimpleReaderPrivate::parseBeginOrContinue (this=0x3c326b0, state=0, incremental=false) at sax/qxml.cpp:3479
#16 0x00007f72a5b9754e in QXmlSimpleReader::parse (this=<value optimized out>, input=0x7fffd69ae6a0, incremental=17) at sax/qxml.cpp:3421
#17 0x00007f72a5b7e822 in QDomDocumentPrivate::setContent (this=0x1c74c10, source=<value optimized out>, reader=0x7fffd69ae690, errorMsg=0x0, errorLine=0x0, errorColumn=0x0) at dom/qdom.cpp:6245
#18 0x00007f728c113a3c in Syndication::DocumentSource::asDomDocument (this=0x7fffd69ae870) at ../../syndication/documentsource.cpp:89
#19 0x00007f728c0cd42a in Syndication::RSS2::Parser::accept (this=<value optimized out>, source=...) at ../../syndication/rss2/parser.cpp:39
#20 0x00007f728c11fe06 in Syndication::ParserCollectionImpl<Syndication::Feed>::parse(Syndication::DocumentSource const&, QString const&) () from /usr/lib/libsyndication.so.4
#21 0x00007f728c11e1c7 in Syndication::Loader::slotRetrieverDone (this=0x3a59620, data=..., success=true) at ../../syndication/loader.cpp:133
#22 0x00007f728c11e51d in Syndication::Loader::qt_metacall (this=0x3a59620, _c=QMetaObject::InvokeMetaMethod, _id=-1, _a=0x7fffd69aea20) at ./loader.moc:73
#23 0x00007f72a9ddcddc in QMetaObject::activate (sender=0x3a2de70, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0xffffffff) at kernel/qobject.cpp:3113
#24 0x00007f728c120553 in Syndication::DataRetriever::dataRetrieved (this=0x2de3e00, _t1=<value optimized out>, _t2=true) at ./dataretriever.moc:79
#25 0x00007f728c12130f in Syndication::FileRetriever::slotResult (this=0x3a2de70, job=0x29919d0) at ../../syndication/dataretriever.cpp:132
#26 0x00007f728c121493 in Syndication::FileRet...

I can reproduce the crash with the feed posted by Mark Rose using KDE 4.3.4 from Kubuntu packages. But according to the backtrace, this seems to be a QT issue not an akregator one. But anyway, here is the backtrace:

Application: Kontact (kontact), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5 QDomNodePrivate::setLocation (this=0x7fffd69ae5c0, nsURI=<value optimized out>, qName=<value optimized out>, atts=...) at dom/qdom.cpp:1923
#6 QDomHandler::startElement (this=0x7fffd69ae5c0, nsURI=<value optimized out>, qName=<value optimized out>, atts=...) at dom/qdom.cpp:7418
#7 0x00007f72a5b8aae7 in QXmlSimpleReaderPrivate::processElementEmptyTag (this=0x3c326b0) at sax/qxml.cpp:3987
#8 0x00007f72a5b96df8 in QXmlSimpleReaderPrivate::parseElement (this=0x3c326b0) at sax/qxml.cpp:3955
#9 0x00007f72a5b96288 in QXmlSimpleReaderPrivate::parseContent (this=0x3c326b0) at sax/qxml.cpp:4408
#10 0x00007f72a5b96d70 in QXmlSimpleReaderPrivate::parseElement (this=0x3c326b0) at sax/qxml.cpp:3934
#11 0x00007f72a5b96288 in QXmlSimpleReaderPrivate::parseContent (this=0x3c326b0) at sax/qxml.cpp:4408
#12 0x00007f72a5b96d70 in QXmlSimpleReaderPrivate::parseElement (this=0x3c326b0) at sax/qxml.cpp:3934
#13 0x00007f72a5b96288 in QXmlSimpleReaderPrivate::parseContent (this=0x3c326b0) at sax/qxml.cpp:4408
#14 0x00007f72a5b96d70 in QXmlSimpleReaderPrivate::parseElement (this=0x3c326b0) at sax/qxml.cpp:3934
#15 0x00007f72a5b971d8 in QXmlSimpleReaderPrivate::parseBeginOrContinue (this=0x3c326b0, state=0, incremental=false) at sax/qxml.cpp:3479
#16 0x00007f72a5b9754e in QXmlSimpleReader::parse (this=<value optimized out>, input=0x7fffd69ae6a0, incremental=17) at sax/qxml.cpp:3421
#17 0x00007f72a5b7e822 in QDomDocumentPrivate::setContent (this=0x1c74c10, source=<value optimized out>, reader=0x7fffd69ae690, errorMsg=0x0, errorLine=0x0, errorColumn=0x0) at dom/qdom.cpp:6245
#18 0x00007f728c113a3c in Syndication::DocumentSource::asDomDocument (this=0x7fffd69ae870) at ../../syndication/documentsource.cpp:89
#19 0x00007f728c0cd42a in Syndication::RSS2::Parser::accept (this=<value optimized out>, source=...) at ../../syndication/rss2/parser.cpp:39
#20 0x00007f728c11fe06 in Syndication::ParserCollectionImpl<Syndication::Feed>::parse(Syndication::DocumentSource const&, QString const&) () from /usr/lib/libsyndication.so.4
#21 0x00007f728c11e1c7 in Syndication::Loader::slotRetrieverDone (this=0x3a59620, data=..., success=true) at ../../syndication/loader.cpp:133
#22 0x00007f728c11e51d in Syndication::Loader::qt_metacall (this=0x3a59620, _c=QMetaObject::InvokeMetaMethod, _id=-1, _a=0x7fffd69aea20) at ./loader.moc:73
#23 0x00007f72a9ddcddc in QMetaObject::activate (sender=0x3a2de70, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0xffffffff) at kernel/qobject.cpp:3113
#24 0x00007f728c120553 in Syndication::DataRetriever::dataRetrieved (this=0x2de3e00, _t1=<value optimized out>, _t2=true) at ./dataretriever.moc:79
#25 0x00007f728c12130f in Syndication::FileRetriever::slotResult (this=0x3a2de70, job=0x29919d0) at ../../syndication/dataretriever.cpp:132
#26 0x00007f728c121493 in Syndication::FileRetriever::qt_metacall (this=0x3a2de70, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd69aeba0) at ./dataretriever.moc:195
#27 0x00007f72a9ddcddc in QMetaObject::activate (sender=0x29919d0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0xffffffff) at kernel/qobject.cpp:3113
#28 0x00007f72aa1b2e62 in KJob::result (this=0x2de3e00, _t1=0x29919d0) at ./kjob.moc:188
#29 0x00007f72aa1b31df in KJob::emitResult (this=0x29919d0) at ../../kdecore/jobs/kjob.cpp:304
#30 0x00007f72a823bd93 in KIO::SimpleJob::slotFinished (this=0x29919d0) at ../../kio/kio/job.cpp:477
#31 0x00007f72a823c253 in KIO::TransferJob::slotFinished (this=0x29919d0) at ../../kio/kio/job.cpp:948
#32 0x00007f72a823ab61 in KIO::TransferJob::qt_metacall (this=0x29919d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd69aefc0) at ./jobclasses.moc:343
#33 0x00007f72a9ddcddc in QMetaObject::activate (sender=0x2991930, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0xffffffff) at kernel/qobject.cpp:3113
#34 0x00007f72a82fca91 in KIO::SlaveInterface::dispatch (this=0x2991930, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#35 0x00007f72a82f9343 in KIO::SlaveInterface::dispatch (this=0x2991930) at ../../kio/kio/slaveinterface.cpp:91
#36 0x00007f72a82ec15d in KIO::Slave::gotInput (this=0x2991930) at ../../kio/kio/slave.cpp:322
#37 0x00007f72a82ee27c in KIO::Slave::qt_metacall (this=0x2991930, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd69af380) at ./slave.moc:76
#38 0x00007f72a9ddcddc in QMetaObject::activate (sender=0x2d1d200, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0xffffffff) at kernel/qobject.cpp:3113
#39 0x00007f72a8208ed7 in KIO::ConnectionPrivate::dequeue (this=0x23c65c0) at ../../kio/kio/connection.cpp:82
#40 0x00007f72a8208ffd in KIO::Connection::qt_metacall (this=0x2d1d200, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x3aef110) at ./connection.moc:73
#41 0x00007f72a9dd70f9 in QObject::event (this=0x2d1d200, e=0x388a610) at kernel/qobject.cpp:1111
#42 0x00007f72aa6ebefc in QApplicationPrivate::notify_helper (this=0x17d9060, receiver=0x2d1d200, e=0x388a610) at kernel/qapplication.cpp:4056
#43 0x00007f72aa6f31ce in QApplication::notify (this=0x7fffd69b0800, receiver=0x2d1d200, e=0x388a610) at kernel/qapplication.cpp:4021
#44 0x00007f72ab322e56 in KApplication::notify (this=0x7fffd69b0800, receiver=0x2d1d200, event=0x388a610) at ../../kdeui/kernel/kapplication.cpp:302
#45 0x00007f72a9dc7c2c in QCoreApplication::notifyInternal (this=0x7fffd69b0800, receiver=0x2d1d200, event=0x388a610) at kernel/qcoreapplication.cpp:610
#46 0x00007f72a9dc880a in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x179b080) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#47 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x179b080) at kernel/qcoreapplication.cpp:1247
#48 0x00007f72a9df0533 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#49 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#50 0x00007f72a3641bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#51 0x00007f72a3645588 in ?? () from /lib/libglib-2.0.so.0
#52 0x00007f72a36456b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#53 0x00007f72a9df01a6 in QEventDispatcherGlib::processEvents (this=0x179acb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#54 0x00007f72aa7804be in QGuiEventDispatcherGlib::processEvents (this=0x2de3e00, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#55 0x00007f72a9dc6532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#56 0x00007f72a9dc6904 in QEventLoop::exec (this=0x7fffd69afc80, flags=) at kernel/qeventloop.cpp:201
#57 0x00007f72aab669de in QDialog::exec (this=0x299d8c0) at dialogs/qdialog.cpp:498
#58 0x00007f728c80429d in Akregator::CreateFeedCommand::Private::doCreate (this=0x3beff10) at ../../../akregator/src/createfeedcommand.cpp:98
#59 0x00007f728c804451 in Akregator::CreateFeedCommand::qt_metacall (this=0x2abad10, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=<value optimized out>)
 at ./createfeedcommand.moc:66
#60 0x00007f72a9ddcddc in QMetaObject::activate (sender=0x35f3af0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0xffffffff) at kernel/qobject.cpp:3113
#61 0x00007f72a9de1e1f in QSingleShotTimer::timerEvent (this=0x35f3af0) at kernel/qtimer.cpp:298
#62 0x00007f72a9dd6d83 in QObject::event (this=0x35f3af0, e=0x0) at kernel/qobject.cpp:1075
#63 0x00007f72aa6ebefc in QApplicationPrivate::notify_helper (this=0x17d9060, receiver=0x35f3af0, e=0x7fffd69b04a0) at kernel/qapplication.cpp:4056
#64 0x00007f72aa6f31ce in QApplication::notify (this=0x7fffd69b0800, receiver=0x35f3af0, e=0x7fffd69b04a0) at kernel/qapplication.cpp:4021
#65 0x00007f72ab322e56 in KApplication::notify (this=0x7fffd69b0800, receiver=0x35f3af0, event=0x7fffd69b04a0) at ../../kdeui/kernel/kapplication.cpp:302
#66 0x00007f72a9dc7c2c in QCoreApplication::notifyInternal (this=0x7fffd69b0800, receiver=0x35f3af0, event=0x7fffd69b04a0) at kernel/qcoreapplication.cpp:610
#67 0x00007f72a9df2862 in QCoreApplication::sendEvent (this=0x17d9d70) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#68 QTimerInfoList::activateTimers (this=0x17d9d70) at kernel/qeventdispatcher_unix.cpp:572
#69 0x00007f72a9df025d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#70 0x00007f72a3641bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#71 0x00007f72a3645588 in ?? () from /lib/libglib-2.0.so.0
#72 0x00007f72a36456b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#73 0x00007f72a9df01a6 in QEventDispatcherGlib::processEvents (this=0x179acb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#74 0x00007f72aa7804be in QGuiEventDispatcherGlib::processEvents (this=0x2de3e00, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#75 0x00007f72a9dc6532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#76 0x00007f72a9dc6904 in QEventLoop::exec (this=0x7fffd69b0740, flags=) at kernel/qeventloop.cpp:201
#77 0x00007f72a9dc8ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#78 0x0000000000403f47 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:218

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2009-12-16:

#116

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

Revision history for this message

In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote on 2009-12-29:

#117

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

Revision history for this message

In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote on 2009-12-29:

#118

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-01-01:

#119

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-01-01:

#120

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-01-01:

#121

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

Revision history for this message

In KDE Bug Tracking System #116482, Jimmy Berry (boombatower) wrote on 2010-01-20:

#122

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2010-02-06:

#123

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2010-02-06:

#124

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2010-02-06:

#125

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

Revision history for this message

In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote on 2010-02-06:

#126

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

Revision history for this message

In KDE Bug Tracking System #116482, Juha Tiensyrjä (juha-tiensyrja) wrote on 2010-02-11:

#127

Created attachment 40660
New crash information added by DrKonqi

I just rebooted my computer the second time after upgrading to KDE SC 4.4.0. Akregator just crashed right after login, I was not doing anything special.

Revision history for this message

In KDE Bug Tracking System #116482, Juha Tiensyrjä (juha-tiensyrja) wrote on 2010-02-11:

#128

I just found out that removing the feed cache files solved the problem. It may be that the abrupt power loss of my computer caused some corruption which manifested as a crash on startup.

Sorry, my bad. I should've checked the situation more carefully.

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-02-21:

#129

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-02-22:

#130

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

Revision history for this message

In KDE Bug Tracking System #116482, Marc Hildebrandt (serenity.) wrote on 2010-03-07:

#131

Created attachment 41391
New crash information added by DrKonqi

Kontact worked fine and normal. Then, day to day, it refused to start.

Revision history for this message

In KDE Bug Tracking System #116482, Herr-schneider-m (herr-schneider-m) wrote on 2010-03-09:

#132

Created attachment 41470
New crash information added by DrKonqi

The same thing happens when trying to fetch all sources from the tray icon...

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-03-16:

#133

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

Revision history for this message

In KDE Bug Tracking System #116482, KIAaze (zohn-joidberg) wrote on 2010-03-23:

#134

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-25:

#135

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-25:

#136

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-25:

#137

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-26:

#138

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-26:

#139

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-27:

#140

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-27:

#141

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-27:

#142

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-27:

#143

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-28:

#144

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-28:

#145

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-28:

#146

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

Revision history for this message

In KDE Bug Tracking System #116482, CTown (ctownthug711) wrote on 2010-03-30:

#147

Hello, I can confirm that Frank Osterfeld is correct. For me, the only feed that seems to have caused this is from the BBC:

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-03-30:

#148

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

Revision history for this message

In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote on 2010-04-18:

#149

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

Revision history for this message

In KDE Bug Tracking System #116482, E-6at-t (e-6at-t) wrote on 2010-04-18:

#150

I went through my mk4 files one at a time, and found one which causes the problems. Renamed it and off we go.
file:///home/laptop/.kde/share/apps/akregatorold/Archive/http___minneapolis.craigslist.org_search_sss%3Fquery=auction&format=rss.mk4old
I can send the file to anyone if it will be useful to them (but it is 11.2Mb)

Revision history for this message

In KDE Bug Tracking System #116482, Diazona (diazona) wrote on 2010-05-14:

#151

Created attachment 43558
New crash information added by DrKonqi

First time running Akregator after a power outage and, it crashes immediately; the main window doesn't even appear. Renaming/deleting $KDEHOME/share/apps/akregator/Archive allows Akregator to run normally. Alternatively, deleting $KDEHOME/share/apps/akregator/Archive/archiveindex.mk4 (without touching any of the http___*.mk4 files) allows the main window to appear, although that leads to another separate crash after a second or so. I could provide the mk4 files if needed.

Revision history for this message

In KDE Bug Tracking System #116482, Flope (flope) wrote on 2010-05-21:

#152

Created attachment 43783
New crash information added by DrKonqi

After a power outage Akregator crashes immediatly with segfault if i want to start it.

Revision history for this message

In KDE Bug Tracking System #116482, James Holby (jamesdholby) wrote on 2010-06-01:

#153

Created attachment 47555
New crash information added by DrKonqi

After a restart Akregator comes up with a segmentation fault after logging in.

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-06-04:

#154

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

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-06-04:

#155

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

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-06-04:

#156

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

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-06-04:

#157

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

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-06-04:

#158

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

Revision history for this message

In KDE Bug Tracking System #116482, Nicolás Alvarez (nicolas-alvarez) wrote on 2010-06-04:

#159

Reported in 2005, 95 duplicates, and it's still not fixed. You must be proud.

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-05:

#160

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-05:

#161

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-05:

#162

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-05:

#163

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-05:

#164

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-05:

#165

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-06:

#166

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-06:

#167

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-06:

#168

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-06:

#169

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-07:

#170

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-07:

#171

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-07:

#172

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-07:

#173

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-07:

#174

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

Revision history for this message

In KDE Bug Tracking System #116482, helios (martin-lichtvoll) wrote on 2010-06-07:

#175

Re Nicolás, comment #149: Nicolás, I don't think there is a contest amongst developers who gets the most duplicate reports. Maybe there are no active aKregator haxx0rz at the moment? Does anyone know the state of Akregator maintenance? I will ask on kdepim in a moment.

Aside from that: Betatesters *should* look for duplicates and usually in the reporting process Bugzilla presents possible duplicates. How >100 bug reporters fail to see those duplicates actually is *completely beyond me*.

*Please watch out for duplicates!* It does not help the process to report the same issue again and again and again and again...

Revision history for this message

In KDE Bug Tracking System #116482, helios (martin-lichtvoll) wrote on 2010-06-07:

#176

To: <email address hidden>
Date: Today 10:29:06
Subject: Does anybody know the state of Akregator maintenance?

Hello!

Does anybody know the maintenance state of Akregator? Are any aKregator haxx0rz still with KDE development?

I am asking cause

Bug 116482 - metakit: akregator crashes at startup
https://bugs.kde.org/show_bug.cgi?id=116482

collects duplicates like dust without anyone apparently working on it.

Actually I cannot reproduce it at all since ages, Akregator just works for me, but AFAIR there have been several mk4-Files posted that should trigger the problem.

Anyone knows whom to contact about this?

Ciao,
--
Martin[...]

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-09:

#177

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-10:

#178

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

Revision history for this message

In KDE Bug Tracking System #116482, József Kószó (k-joe) wrote on 2010-06-14:

#179

Created attachment 48011
A good and a bad .mk4 file for same feed.

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-16:

#180

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-21:

#181

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-06-24:

#182

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

Revision history for this message

In KDE Bug Tracking System #116482, Thomas Tanghus (tanghus) wrote on 2010-06-25:

#183

Created attachment 48329
New crash information added by DrKonqi

I had a kernel crash and after REISUB'ing out of it Akregators archives was apparently corrupted thus giving this crash. Tried 3 times with Kontact; same crash. Tried stand-alone Akregator; same crash.
Now I hope I can get it running again without having to loose all the status of the archive :-/
Well the BT should be good anyways...

Revision history for this message

In KDE Bug Tracking System #116482, SKAL (sir-kalot) wrote on 2010-06-30:

#184

Created attachment 48479
New crash information added by DrKonqi

starting up akregator I get the following error

akregator
Object::connect: No such signal Akregator::SubscriptionListView::signalDropped (KUrl::List &, Akregator::TreeNode*, Akregator::Folder*)
Object::connect: (sender name: 'feedtree')
Object::connect: (receiver name: 'akregator_view')
z-lmutt@z-lmutt-desktop:~$ KCrash: Application 'akregator' crashing...
sock_file=/home/z-lmutt/.kde/socket-z-lmutt-desktop/kdeinit4__0

Revision history for this message

In KDE Bug Tracking System #116482, SKAL (sir-kalot) wrote on 2010-06-30:

#185

Comment on attachment 48479
New crash information added by DrKonqi

Removing the ~/.kde/share/apps/akregator/Archive dir fixed the problem

Revision history for this message

In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote on 2010-07-25:

#186

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

Revision history for this message

In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote on 2010-07-25:

#187

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

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-08-12:

#188

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

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-08-12:

#189

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

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-08-12:

#190

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

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-08-12:

#191

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

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-08-12:

#192

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

Revision history for this message

In KDE Bug Tracking System #116482, Alvin (alvind) wrote on 2010-08-12:

#193

Created attachment 50087
New crash information added by DrKonqi

kontact (4.4.5) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.7.0

This is the crash in as occuring in KDE 4.5.

-- Backtrace (Reduced):
#6 memcpy () at ../sysdeps/x86_64/memcpy.S:527
#7 0x00007f531ee71474 in c4_String::Init (this=0x7fffdb23d000, p=<value optimized out>, n=18032842) at /usr/include/bits/string3.h:52
#8 0x00007f531ee68c52 in c4_String (this=0x20e3340, ptr_=0x7fffdb23d0b0, selfDesc_=<value optimized out>) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4str.inl:209
#9 c4_HandlerSeq::Prepare (this=0x20e3340, ptr_=0x7fffdb23d0b0, selfDesc_=<value optimized out>) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:305
#10 0x00007f531ee6c470 in c4_Persist::LoadAll (this=0x20dc7c0) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:1026

Revision history for this message

In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote on 2010-08-22:

#194

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

Revision history for this message

In KDE Bug Tracking System #116482, FiNeX (finex) wrote on 2010-09-12:

#195

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

Revision history for this message

In KDE Bug Tracking System #116482, Roucaries-bastien+bug (roucaries-bastien+bug) wrote on 2010-09-13:

#196

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

Revision history for this message

In KDE Bug Tracking System #116482, Roucaries-bastien+bug (roucaries-bastien+bug) wrote on 2010-09-13:

#197

This is debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590147 that does not allow akregator to release.

Please correct it before release.

Bastien

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-09-14:

#198

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-09-14:

#199

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-09-14:

#200

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-09-14:

#201

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-09-14:

#202

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-09-14:

#203

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

Revision history for this message

In KDE Bug Tracking System #116482, matthiasf (matthiasf) wrote on 2010-09-15:

#204

Download full text (6.4 KiB)

Akregator nowadas hangs on startup for me, I have to kill it. This is the bt I got via gdb. Btw. if it is of use I could upload my akregator direcotry somewhere and my config.

Thread 2 (Thread 0x7f6222f28710 (LWP 7286)):
#0 0x00007f6237c1040c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007f6224035e30 in ?? () from /usr/lib/libQtWebKit.so.4
#2 0x00007f6224035e69 in ?? () from /usr/lib/libQtWebKit.so.4
#3 0x00007f6237c0bcb0 in start_thread () from /lib/libpthread.so.0
#4 0x00007f623b5207ad in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f623e8ec760 (LWP 7285)):
#0 0x00007f62274625e1 in c4_Handler::GetBytes (this=<value optimized out>, index_=<value optimized out>, buf_=..., copySmall_=false)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/handler.cpp:55
#1 0x00007f622746fdb2 in c4_Sequence::Get (this=0x313a400, index_=19181, propId_=<value optimized out>, buf_=...)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/viewx.cpp:319
#2 0x00007f62274707c4 in GetData (this=0x7fffb37c7dd0) at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/include/mk4.inl:421
#3 c4_IntRef::operator t4_i32 (this=0x7fffb37c7dd0) at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/viewx.cpp:404
#4 0x00007f622746742d in c4_HashViewer::IsUnused (this=0x3126b00, row_=<value optimized out>)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/remap.cpp:130
#5 0x00007f6227467e0f in c4_HashViewer::LookDict (this=0x3126b00, hash_=-32661358, cursor_=...)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/remap.cpp:255
#6 0x00007f62274681c2 in c4_HashViewer::Lookup (this=0x3126b00, key_=..., count_=@0x7fffb37c837c)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/remap.cpp:344
#7 0x00007f622745a46a in c4_CustomSeq::RestrictSearch (this=<value optimized out>, cursor_=..., pos_=@0x7fffb37c83ac, count_=@0x7fffb37c840c)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/custom.cpp:110
#8 0x00007f622746e93a in c4_View::Find (this=0x32ae5e8, crit_=<value optimized out>, start_=0)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/view.cpp:830
#9 0x00007f6227472544 in Akregator::Backend::FeedStorageMK4Impl::findArticle (this=0x2a4c5f0, guid=...)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/feedstoragemk4impl.cpp:298
#10 0x00007f6227475b20 in Akregator::Backend::FeedStorageMK4Impl::status (this=0x2a4c5f0, guid=<value optimized out>)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/feedstoragemk4impl.cpp:384
#11 0x00007f6229098967 in Akregator::Article::Private::Private (this=<value optimized out>, guid_=<value optimized out>, feed_=<value optimized out>,
 archive_=<value optimized out>) at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/src/articl...

Akregator nowadas hangs on startup for me, I have to kill it. This is the bt I got via gdb. Btw. if it is of use I could upload my akregator direcotry somewhere and my config.

Thread 2 (Thread 0x7f6222f28710 (LWP 7286)):
#0  0x00007f6237c1040c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f6224035e30 in ?? () from /usr/lib/libQtWebKit.so.4
#2  0x00007f6224035e69 in ?? () from /usr/lib/libQtWebKit.so.4
#3  0x00007f6237c0bcb0 in start_thread () from /lib/libpthread.so.0
#4  0x00007f623b5207ad in clone () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f623e8ec760 (LWP 7285)):
#0 0x00007f62274625e1 in c4_Handler::GetBytes (this=<value optimized out>, index_=<value optimized out>, buf_=..., copySmall_=false)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/handler.cpp:55
#1 0x00007f622746fdb2 in c4_Sequence::Get (this=0x313a400, index_=19181, propId_=<value optimized out>, buf_=...)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/viewx.cpp:319
#2 0x00007f62274707c4 in GetData (this=0x7fffb37c7dd0) at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/include/mk4.inl:421
#3 c4_IntRef::operator t4_i32 (this=0x7fffb37c7dd0) at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/viewx.cpp:404
#4 0x00007f622746742d in c4_HashViewer::IsUnused (this=0x3126b00, row_=<value optimized out>)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/remap.cpp:130
#5 0x00007f6227467e0f in c4_HashViewer::LookDict (this=0x3126b00, hash_=-32661358, cursor_=...)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/remap.cpp:255
#6 0x00007f62274681c2 in c4_HashViewer::Lookup (this=0x3126b00, key_=..., count_=@0x7fffb37c837c)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/remap.cpp:344
#7 0x00007f622745a46a in c4_CustomSeq::RestrictSearch (this=<value optimized out>, cursor_=..., pos_=@0x7fffb37c83ac, count_=@0x7fffb37c840c)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/custom.cpp:110
#8 0x00007f622746e93a in c4_View::Find (this=0x32ae5e8, crit_=<value optimized out>, start_=0)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/metakit/src/view.cpp:830
#9 0x00007f6227472544 in Akregator::Backend::FeedStorageMK4Impl::findArticle (this=0x2a4c5f0, guid=...)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/feedstoragemk4impl.cpp:298
#10 0x00007f6227475b20 in Akregator::Backend::FeedStorageMK4Impl::status (this=0x2a4c5f0, guid=<value optimized out>)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/plugins/mk4storage/feedstoragemk4impl.cpp:384
#11 0x00007f6229098967 in Akregator::Article::Private::Private (this=<value optimized out>, guid_=<value optimized out>, feed_=<value optimized out>, 
 archive_=<value optimized out>) at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/src/article.cpp:148
#12 0x00007f6229098a95 in Akregator::Article::Article (this=0x7fffb37c8680, guid=..., feed=0x7f621c001da0)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/src/article.cpp:241
#13 0x00007f62290a7fcd in Akregator::Feed::loadArticles (this=0x7f621c001da0) at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/src/feed.cpp:239
#14 0x00007f62290a987d in Akregator::Feed::fromOPML (e=<value optimized out>, storage=0x25c6c60) at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/src/feed.cpp:174
#15 0x00007f62290b2cb5 in Akregator::FeedList::parseChildNodes (this=0x7f621c003c10, node=<value optimized out>, parent=0x7f621c001a30)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/src/feedlist.cpp:237
#16 0x00007f62290b3686 in Akregator::FeedList::readFromOpml (this=0x7f621c003c10, doc=<value optimized out>)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/src/feedlist.cpp:295
#17 0x00007f62290eab6b in Akregator::LoadFeedListCommand::Private::handleDocument (this=0x24fbc40, doc=...)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/src/loadfeedlistcommand.cpp:68
#18 0x00007f62290eb603 in Akregator::LoadFeedListCommand::Private::doLoad (this=0x24fbc40)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/src/loadfeedlistcommand.cpp:173
#19 0x00007f62290eb9c2 in Akregator::LoadFeedListCommand::qt_metacall (this=0x24fa700, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffb37c93f0)
 at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/src/loadfeedlistcommand.moc:78
#20 0x00007f623c0b8def in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#21 0x00007f623c0bddef in ?? () from /usr/lib/libQtCore.so.4
#22 0x00007f623c0b63ae in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#23 0x00007f623ca35ae4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#24 0x00007f623ca39bca in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#25 0x00007f623d712da6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#26 0x00007f623c0a4d8c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#27 0x00007f623c0d0222 in ?? () from /usr/lib/libQtCore.so.4
---Type <return> to continue, or q <return> to quit---
#28 0x00007f623c0cd1d4 in ?? () from /usr/lib/libQtCore.so.4
#29 0x00007f62362dbb33 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0x00007f62362dc310 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#31 0x00007f62362dc5ad in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0x00007f623c0cd87f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#33 0x00007f623cad560e in ?? () from /usr/lib/libQtGui.so.4
#34 0x00007f623c0a4172 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#35 0x00007f623c0a43ac in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#36 0x00007f623c0a87bb in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#37 0x00000000004096a5 in main (argc=<value optimized out>, argv=<value optimized out>) at /home/anke/kdemod/core/kdepim/src/kdepim-4.4.5/akregator/src/main.cpp:103

Revision history for this message

In KDE Bug Tracking System #116482, matthiasf (matthiasf) wrote on 2010-09-15:

#205

Created attachment 51674
Debug output

Here is the debug output of akregator when it fails to start.

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-09-18:

#206

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-09-19:

#207

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-09-22:

#208

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-09-24:

#209

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-09-29:

#210

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-10-02:

#211

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-10-13:

#212

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-10-13:

#213

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

Revision history for this message

In KDE Bug Tracking System #116482, Marcel9 (marcel9) wrote on 2010-10-22:

#214

Created attachment 52763
New crash information added by DrKonqi

akregator (1.6.5) on KDE Platform 4.5.2 (KDE 4.5.2) "release 5" using Qt 4.6.3

Hey,
don´t know if it helps, but here is my crash report.
I think it was after a hang of the system.

-- Backtrace (Reduced):
#8 0xb0853c59 in c4_String::Init (this=0xbfca4318, p=0x8137de4, n=1253886) at /usr/include/bits/string3.h:52
#9 0xb084b14c in c4_String (this=0x8137da8, ptr_=0xbfca43bc, selfDesc_=true) at /usr/src/debug/kdepim-4.4.6/akregator/plugins/mk4storage/metakit/include/mk4str.inl:209
#10 c4_HandlerSeq::Prepare (this=0x8137da8, ptr_=0xbfca43bc, selfDesc_=true) at /usr/src/debug/kdepim-4.4.6/akregator/plugins/mk4storage/metakit/src/handler.cpp:305
#11 0xb084e8ea in c4_Persist::LoadAll (this=0x8137ea0) at /usr/src/debug/kdepim-4.4.6/akregator/plugins/mk4storage/metakit/src/persist.cpp:1026
#12 0xb0852cbe in c4_Storage::c4_Storage (this=0x816ce20, fname_=0x816f368 "/home/marcel/.kde4/share/apps/akregator/Archive/archiveindex.mk4", mode_=1)
at /usr/src/debug/kdepim-4.4.6/akregator/plugins/mk4storage/metakit/src/store.cpp:202

Revision history for this message

In KDE Bug Tracking System #116482, Marcel9 (marcel9) wrote on 2010-10-22:

#215

Hey,

Here is my Archive: http://www.file-upload.net/download-2910539/Archive_old.tar.gz.html

I solved the problem:
rename the archive folder /home/.kde4/share/apps/akregator
start akregator and close it
copy the files in the new created archive folder
do NOT copy the index and backup file, use the new one instea:-)

open_assistant

Revision history for this message

In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote on 2010-11-20:

#216

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

Revision history for this message

In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote on 2010-11-20:

#217

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

Revision history for this message

In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote on 2010-11-20:

#218

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-11-26:

#219

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

Revision history for this message

In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote on 2010-11-27:

#220

[Comment from a bug triager]
Bug 258115 comment 1 contains a feed that seem to cause this crash on 4.6beta1

Revision history for this message

In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote on 2010-11-27:

#221

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

Revision history for this message

In KDE Bug Tracking System #116482, Hobbyblobby (hobbyblobby) wrote on 2010-12-08:

#222

Created attachment 54301
New crash information added by DrKonqi

akregator (1.6.0) on KDE Platform 4.5.80 (4.6 Beta1) using Qt 4.7.1

- What I was doing when the application crashed: because of a X-Server crash I killed the session. After that akregator wont start anymore

-- Backtrace (Reduced):
#7 0x00007fcafec4cf34 in c4_String::Init (this=0x7fff8579a470, p=<value optimized out>, n=160062574) at /usr/include/bits/string3.h:52
#8 0x00007fcafec431f2 in c4_String (this=0xdc9160, ptr_=0x7fff8579a520, selfDesc_=<value optimized out>) at /usr/src/debug/kdepim-4.5.80/akregator/plugins/mk4storage/metakit/include/mk4str.inl:209
#9 c4_HandlerSeq::Prepare (this=0xdc9160, ptr_=0x7fff8579a520, selfDesc_=<value optimized out>) at /usr/src/debug/kdepim-4.5.80/akregator/plugins/mk4storage/metakit/src/handler.cpp:305
#10 0x00007fcafec46b10 in c4_Persist::LoadAll (this=0xdc8eb0) at /usr/src/debug/kdepim-4.5.80/akregator/plugins/mk4storage/metakit/src/persist.cpp:1026
#11 0x00007fcafec52b02 in Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl (this=0xdc8c50, url=<value optimized out>, main=<value optimized out>)
at /usr/src/debug/kdepim-4.5.80/akregator/plugins/mk4storage/feedstoragemk4impl.cpp:152

Revision history for this message

In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote on 2010-12-11:

#223

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-12-13:

#224

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-12-14:

#225

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

Revision history for this message

In KDE Bug Tracking System #116482, Jason Mours (jason-mours) wrote on 2010-12-16:

#226

Created attachment 54832
New crash information added by DrKonqi

akregator (1.6.0) on KDE Platform 4.5.85 (4.6 Beta2) using Qt 4.7.1

Using the latest openSUSE factory build of KDE 4.6beta2. Same problem with crashes on startup. Some improvment. Desktop widgets show feeds now before crash. Tray icon is no longer cruppted.

-- Backtrace (Reduced):
#10 0x00007f1a58ab51ed in c4_Column::Shrink (this=0xd83648, off_=<value optimized out>, diff_=<value optimized out>)
 at /usr/src/debug/kdepim-4.5.85/akregator/plugins/mk4storage/metakit/src/column.cpp:612
#11 0x00007f1a58abcdbf in c4_FormatB::SetOne (this=0xd83630, index_=851085, xbuf_=<value optimized out>, ignoreMemos_=<value optimized out>)
 at /usr/src/debug/kdepim-4.5.85/akregator/plugins/mk4storage/metakit/src/format.cpp:610
#12 0x00007f1a58abd0d4 in c4_FormatB::Commit (this=0xd83630, ar_=...) at /usr/src/debug/kdepim-4.5.85/akregator/plugins/mk4storage/metakit/src/format.cpp:792
#13 0x00007f1a58ac17d4 in c4_SaveContext::CommitSequence (this=0x7fff25934fb0, seq_=..., selfDesc_=<value optimized out>)
 at /usr/src/debug/kdepim-4.5.85/akregator/plugins/mk4storage/metakit/src/persist.cpp:842
#14 0x00007f1a58ac18fe in c4_SaveContext::SaveIt (this=0x7fff25934fb0, root_=..., spacePtr_=0xd8c9c0, rootWalk_=...)
 at /usr/src/debug/kdepim-4.5.85/akregator/plugins/mk4storage/metakit/src/persist.cpp:603

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2010-12-25:

#227

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-01-03:

#228

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-01-06:

#229

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

Revision history for this message

In KDE Bug Tracking System #116482, helios (martin-lichtvoll) wrote on 2011-01-09:

#230

Download full text (3.2 KiB)

From what I read from the mails posted below this is unlikely to be fixed in the current "stable" pre-akonadi version of Akregator and the Akregator akonadi ports needs someone to work on it.

Please refrain from reporting the same bug over and over and - guess what? - over again. Dr. Konqi gives quite some help when it comes to check for duplicates. Reporting it a million times will not help a single bit in resolving this more quickly. So please either help with coding or keep quiet and hope that someone else does it. Or try to find someone to fix the bug.

Thanks.

Re: [Kde-pim] Does anybody know the state of Akregator maintenance?
From: Frank Osterfeld
To: KDE PIM mailing list
Date: 10.06.2010 23:18

On Jun 7, 2010, at 10:29 AM, Martin Steigerwald wrote:
> Hello!
>
> Does anybody know the maintenance state of Akregator? Are any aKregator
> haxx0rz still with KDE development?

I am the maintainer, but I am lacking both time and motivation to work on it. And nobody else appeared so far to take over.

> I am asking cause
>
> Bug 116482 - metakit: akregator crashes at startup
> https://bugs.kde.org/show_bug.cgi?id=116482
>
> collects duplicates like dust without anyone apparently working on it.
>
> Actually I cannot reproduce it at all since ages, Akregator just works for
> me, but AFAIR there have been several mk4-Files posted that should trigger
> the problem.

The issue is known for a long time, and easy to trigger, by using any corrupted mk4 file. The problem is that metakit allocates memory after reading the size of some value in the db. If that value is bogus, which means it's some random value, and far too high most of the time and the process either starts to allocate huge amounts of memory or just crashes (if the value is above the OS limit), or both.
The only real solution I see is to move away from metakit to Akonadi. That was started (krss) and is now lingering in the akonadi-ports branch, but it needs someone with both time and motivation (see above) to complete it.

http://lists.kde.org/?l=kde-pim&m=127620477618025&w=2

Re: [Kde-pim] Status of Akregator Akonadi port...
From: Frank Osterfeld
To: KDE PIM mailing list
Date: 16.07.2010 11:06
On Jul 15, 2010, at 1:44 AM, Pierre wrote:

> Hi
>
> I'm currently searching through blogs, this mailing list and the SVN
> repository,
> and it looks like the Akregator Akonadi port went silent a few months ago.
> Is there still someone working on it ?

No, currently there is nobody working on it.

> What is the current status of this port ?

The basics were working, but it showed some performance issues when importing larger rss archives.
The implementation also shows that it was started in the early days of Akonadi resource development and we wanted replace some of krss-specific models etc. by the new like EntityTreeModel.
And then I'd like to cleanup the resource implementation, which became overly complex by adding another layer of abstraction to support
both local storage and online RSS readers (newsgator in particular, which then closed down).

> Where can we download the latest source code if we want to help (or try to
> help) ?

See Krenar's post. akonadi-ports needs to be...

From what I read from the mails posted below this is unlikely to be fixed in the current "stable" pre-akonadi version of Akregator and the Akregator akonadi ports needs someone to work on it.

Please refrain from reporting the same bug over and over and - guess what? - over again. Dr. Konqi gives quite some help when it comes to check for duplicates. Reporting it a million times will not help a single bit in resolving this more quickly. So please either help with coding or keep quiet and hope that someone else does it. Or try to find someone to fix the bug.

Thanks.

Re: [Kde-pim] Does anybody know the state of Akregator maintenance?
From: Frank Osterfeld
To: KDE PIM mailing list
Date: 10.06.2010 23:18
 
On Jun 7, 2010, at 10:29 AM, Martin Steigerwald wrote: 
> Hello!
> 
> Does anybody know the maintenance state of Akregator? Are any aKregator 
> haxx0rz still with KDE development?

I am the maintainer, but I am lacking both time and motivation to work on it. And nobody else appeared so far to take over.

> I am asking cause
> 
> Bug 116482 -  metakit: akregator crashes at startup
> https://bugs.kde.org/show_bug.cgi?id=116482
> 
> collects duplicates like dust without anyone apparently working on it.
> 
> Actually I cannot reproduce it at all since ages, Akregator just works for 
> me, but AFAIR there have been several mk4-Files posted that should trigger 
> the problem.

The issue is known for a long time, and easy to trigger, by using any corrupted mk4 file. The problem is that metakit allocates memory after reading the size of some value in the db. If that value is bogus, which means it's some random value, and far too high most of the time and the process either starts to allocate huge amounts of memory or just crashes (if the value is above the OS limit), or both.
The only real solution I see is to move away from metakit to Akonadi. That was started (krss) and is now lingering in the akonadi-ports branch, but it needs someone with both time and motivation (see above) to complete it.

http://lists.kde.org/?l=kde-pim&m=127620477618025&w=2

Re: [Kde-pim] Status of Akregator Akonadi port...
From: Frank Osterfeld
To: KDE PIM mailing list
Date: 16.07.2010 11:06
On Jul 15, 2010, at 1:44 AM, Pierre wrote:

> Hi
> 
> I'm currently searching through blogs, this mailing list and the SVN
> repository, 
> and it looks like the Akregator Akonadi port went silent a few months ago.
> Is there still someone working on it ?

No, currently there is nobody working on it.

> What is the current status of this port ?

The basics were working, but it showed some performance issues when importing larger rss archives.
The implementation also shows that it was started in the early days of Akonadi resource development and we wanted replace some of krss-specific models etc. by the new like EntityTreeModel.
And then I'd like to cleanup the resource implementation, which became overly complex by adding another layer of abstraction to support
both local storage and online RSS readers (newsgator in particular, which then closed down).

> Where can we download the latest source code if we want to help (or try to 
> help) ?

See Krenar's post. akonadi-ports needs to be rebased against current trunk though.

http://lists.kde.org/?l=kde-pim&m=127927242109681&w=2

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-01-23:

#231

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-01-24:

#232

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

Revision history for this message

In KDE Bug Tracking System #116482, ronny (ronny-standtke) wrote on 2011-01-28:

#233

Created attachment 56549
New crash information added by DrKonqi

akregator (1.6.5) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.0

- What I was doing when the application crashed:

I was just starting up KDE when akregator suddenly produced a crash message.

-- Backtrace (Reduced):
#6 0x00007f397e081c42 in SetAt (this=0xe6c400, sizes_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/univ.inl:101
#7 c4_FormatB::InitOffsets (this=0xe6c400, sizes_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:560
#8 0x00007f397e082af3 in c4_FormatB::Define (this=0xe6c400, ptr_=0x7fff4461afd0) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:396
#9 0x00007f397e08475e in c4_HandlerSeq::Prepare (this=0xe3cf40, ptr_=0x7fff4461afd0, selfDesc_=<value optimized out>) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:321
#10 0x00007f397e087fd0 in c4_Persist::LoadAll (this=0xe3c9a0) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:1026

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-01-28:

#234

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

Revision history for this message

In KDE Bug Tracking System #116482, Jemand (jemand) wrote on 2011-01-30:

#235

Created attachment 56664
New crash information added by DrKonqi

kontact (4.4.9) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.0

- What I was doing when the application crashed:

About 2 minutes before I had switched to Akregator.

-- Backtrace (Reduced):
#6 memcpy () at ../sysdeps/x86_64/memcpy.S:161
#7 0x00007f9cacc41853 in c4_Column::FetchBytes (this=<value optimized out>, pos_=<value optimized out>, len_=<value optimized out>, buffer_=..., forceCopy_=false) at /usr/include/bits/string3.h:52
#8 0x00007f9cacc49b64 in c4_FormatB::GetOne (this=0x733e7b0, index_=<value optimized out>, length_=@0x7fffc709070c) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:583
#9 0x00007f9cacc49b89 in c4_FormatS::Get (this=0x4db3eb0, index_=7602577, length_=@0xffffffffff553cc7) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:842
#10 0x00007f9cacc4c1d6 in c4_Handler::GetBytes (this=0x4db3eb0, index_=7602577, buf_=..., copySmall_=249) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:53

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-02-06:

#236

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-02-11:

#237

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-02-17:

#238

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

Bug Watch Updater (bug-watch-updater) on 2011-02-27

Changed in kdepim:
importance:	Unknown → High

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-02-28:

#239

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

Revision history for this message

In KDE Bug Tracking System #116482, Roucaries-bastien+bug (roucaries-bastien+bug) wrote on 2011-03-02:

#240

I have found the bug in the metakit package and proposed to debian to upload a new metakit in order to raise exception instead to crash

Will solve this bug

Revision history for this message

In KDE Bug Tracking System #116482, Samuel-brack (samuel-brack) wrote on 2011-03-02:

#241

Bastien, is there a patch available yet? If yes, we'd appreciate it if you'd upload it here, too.

Revision history for this message

In KDE Bug Tracking System #116482, Roucaries-bastien+bug (roucaries-bastien+bug) wrote on 2011-03-02:

#242

see http://git.debian.org/?p=collab-maint/metakit.git;a=summary patch branch is debian-patches/2.4.9.7-1

Will not fix the crash but instead of segv raise exception

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-03-04:

#243

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-03-14:

#244

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-03-25:

#245

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-04-11:

#246

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-04-13:

#247

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-04-19:

#248

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-04-29:

#249

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-05-12:

#250

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-06-25:

#251

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

Revision history for this message

In KDE Bug Tracking System #116482, Andrei Slavoiu (ansla80) wrote on 2011-07-04:

#252

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.

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-07-05:

#253

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-07-07:

#254

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

Revision history for this message

In KDE Bug Tracking System #116482, trionghost (trionghost) wrote on 2011-07-20:

#255

Created attachment 62022
New crash information added by DrKonqi

akregator (1.6.6) on KDE Platform 4.6.5 (4.6.5) "release 8" using Qt 4.7.3

- What I was doing when the application crashed: I just start application after login to KDE on my openSUSE 11.4 with KDE4.6

-- Backtrace (Reduced):
#6 SetAt (this=0x8c5940, sizes_=...) at /usr/src/debug/kdepim-4.4.11.1/akregator/plugins/mk4storage/metakit/src/univ.inl:101
#7 c4_FormatB::InitOffsets (this=0x8c5940, sizes_=...) at /usr/src/debug/kdepim-4.4.11.1/akregator/plugins/mk4storage/metakit/src/format.cpp:560
#8 0x00007f52119f3a63 in c4_FormatB::Define (this=0x8c5940, ptr_=0x7fff343b9450) at /usr/src/debug/kdepim-4.4.11.1/akregator/plugins/mk4storage/metakit/src/format.cpp:396
#9 0x00007f52119f61ce in c4_HandlerSeq::Prepare (this=0x8b8410, ptr_=0x7fff343b9450, selfDesc_=<value optimized out>) at /usr/src/debug/kdepim-4.4.11.1/akregator/plugins/mk4storage/metakit/src/handler.cpp:321
#10 0x00007f52119f9b50 in c4_Persist::LoadAll (this=0x8a6f90) at /usr/src/debug/kdepim-4.4.11.1/akregator/plugins/mk4storage/metakit/src/persist.cpp:1026

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-08-05:

#256

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-08-28:

#257

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-09-13:

#258

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2011-10-02:

#259

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

Revision history for this message

In KDE Bug Tracking System #116482, Jaak-x (jaak-x) wrote on 2011-11-24:

#260

(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* =[

Revision history for this message

In KDE Bug Tracking System #116482, Andrei Slavoiu (ansla80) wrote on 2011-11-25:

#261

I don't remember exactly where I got the mku.utility initially, I must have copied it there and later thought Akregator installed it... Anyway, a google search revealed it's part of the mkstats.kit utility http://equi4.com/metakit/stats.html

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2012-01-12:

#262

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2012-03-30:

#263

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2012-04-26:

#264

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

Revision history for this message

In KDE Bug Tracking System #116482, adaptee (adaptee) wrote on 2012-05-09:

#265

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2012-08-28:

#266

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

Revision history for this message

In KDE Bug Tracking System #116482, Christoph-maxiom (christoph-maxiom) wrote on 2012-08-28:

#267

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

Revision history for this message

In KDE Bug Tracking System #116482, Christoph-maxiom (christoph-maxiom) wrote on 2012-09-25:

#268

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

Revision history for this message

In KDE Bug Tracking System #116482, adaptee (adaptee) wrote on 2012-10-08:

#269

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

Revision history for this message

In KDE Bug Tracking System #116482, Winter-s (winter-s) wrote on 2013-01-14:

#270

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

Revision history for this message

In KDE Bug Tracking System #116482, Christoph-maxiom (christoph-maxiom) wrote on 2013-01-19:

#271

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

Revision history for this message

In KDE Bug Tracking System #116482, De-meyer-maarten (de-meyer-maarten) wrote on 2013-02-08:

#272

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

Revision history for this message

In KDE Bug Tracking System #116482, adaptee (adaptee) wrote on 2013-04-16:

#273

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

Revision history for this message

In KDE Bug Tracking System #116482, adaptee (adaptee) wrote on 2014-01-19:

#274

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

Revision history for this message

In KDE Bug Tracking System #116482, sergiomb (sergio-sergiomb) wrote on 2014-11-19:

#275

149 users , 9 years , 274 comments , any solution ?

Revision history for this message

In KDE Bug Tracking System #116482, sergiomb (sergio-sergiomb) wrote on 2014-11-20:

#276

Cleaning archive doing:
mv ./.kde/share/apps/akregator/Archive/* akregator/Archive/

fixed the crash

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2015-03-01:

#277

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2015-03-01:

#278

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2015-03-01:

#279

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

Revision history for this message

In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote on 2015-03-01:

#280

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

Revision history for this message

In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote on 2015-12-03:

#281

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

Revision history for this message

In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote on 2017-05-04:

#282

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

Revision history for this message

In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote on 2017-08-01:

#283

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

Revision history for this message

In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote on 2017-09-13:

#284

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

Revision history for this message

In KDE Bug Tracking System #116482, Squan (squan) wrote on 2017-09-14:

#285

The correct location of feeds.opml seems to be in ~/.local/share/akregator/data (and not in .kde4 as it used to be in earlier times of this issue).

After a failed resume from suspend to RAM (which since several weeks is a common experience with openSUSE Leap/Tumbleweed with both NVidia and AMD graphics) my feeds.opml got corrupted (Bug 384207).
Is there a backup to be found somewhere may be?

Revision history for this message

In KDE Bug Tracking System #116482, Orivej Desh (orivej) wrote on 2017-09-14:

#286

The only backup is feeds.opml~ in the same directory.

Revision history for this message

In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote on 2018-10-03:

#287

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

Revision history for this message

In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote on 2018-10-03:

#288

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

Revision history for this message

In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote on 2018-10-03:

#289

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

Revision history for this message

In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote on 2018-10-03:

#290

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

Revision history for this message

In KDE Bug Tracking System #116482, Nicolás Alvarez (nicolas-alvarez) wrote on 2020-02-22:

#291

Why did you mark this as fixed, rubi ortiz?

Revision history for this message

In KDE Bug Tracking System #116482, KAMiKAZOW (kamikazow) wrote on 2020-02-22:

#292

Hardly any commits in https://github.com/KDE/akregator/commits/master/plugins/mk4storage over a few years.

Bug Watch Updater (bug-watch-updater) on 2020-02-24

Changed in kdepim:
status:	Confirmed → New

Revision history for this message

In KDE Bug Tracking System #116482, Götz Christ (g-christ) wrote on 2020-02-28:

#293

*** This bug has been confirmed by popular vote. ***

Bug Watch Updater (bug-watch-updater) on 2020-03-30

Changed in kdepim:
status:	New → Unknown

Revision history for this message

In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote on 2020-07-01:

#294

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

Revision history for this message

In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote on 2020-07-01:

#295

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

Revision history for this message

In KDE Bug Tracking System #116482, Thanhvuy02 (thanhvuy02) wrote on 2021-06-03:

#296

Download full text (5.2 KiB)

Application: kdeconnectd (1.4.0)

Qt Version: 5.14.2
Frameworks Version: 5.70.0
Operating System: Linux 5.7.0-2parrot2-amd64 x86_64
Distribution: Parrot GNU/Linux 4.10

-- Information about the crash:
<In detail, tell us what you were doing when the application crashed.>

-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5748672600 (LWP 83677))]

Thread 4 (Thread 0x7f57449a4700 (LWP 83731)):
#0 0x00007f574ca11e8c in read () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f574b60df4f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f574b5c633e in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f574b5c6792 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f574b5c690f in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f574cfab90b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007f574cf5389b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007f574cd7e8be in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007f574cd7f988 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x00007f574bf6bea7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007f574ca20daf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f5745c71700 (LWP 83723)):
#0 0x00007f574b6127b9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007f574b5c5d7a in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f574b5c671b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f574b5c690f in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f574cfab90b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007f574cf5389b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007f574cd7e8be in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007f574d1fc507 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#8 0x00007f574cd7f988 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x00007f574bf6bea7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007f574ca20daf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7f5747890700 (LWP 83707)):
#0 0x00007f574ca163bf in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f574b299d02 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2 0x00007f574b29b98a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1
#3 0x00007f5748280dc0 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4 0x00007f574cd7f988 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007f574bf6bea7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#6 0x00007f574ca20daf in clone () from /lib/x86_64-linux-gnu/...

Application: kdeconnectd (1.4.0)

Qt Version: 5.14.2
Frameworks Version: 5.70.0
Operating System: Linux 5.7.0-2parrot2-amd64 x86_64
Distribution: Parrot GNU/Linux 4.10

-- Information about the crash:
<In detail, tell us what you were doing when the application crashed.>

-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5748672600 (LWP 83677))]

Thread 4 (Thread 0x7f57449a4700 (LWP 83731)):
#0 0x00007f574ca11e8c in read () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f574b60df4f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f574b5c633e in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f574b5c6792 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f574b5c690f in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f574cfab90b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007f574cf5389b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007f574cd7e8be in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007f574cd7f988 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x00007f574bf6bea7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007f574ca20daf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f5745c71700 (LWP 83723)):
#0 0x00007f574b6127b9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007f574b5c5d7a in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f574b5c671b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f574b5c690f in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f574cfab90b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007f574cf5389b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007f574cd7e8be in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007f574d1fc507 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#8 0x00007f574cd7f988 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x00007f574bf6bea7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007f574ca20daf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7f5747890700 (LWP 83707)):
#0  0x00007f574ca163bf in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f574b299d02 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f574b29b98a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f5748280dc0 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f574cd7f988 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f574bf6bea7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#6  0x00007f574ca20daf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f5748672600 (LWP 83677)):
[KCrash Handler]
#4 0x00007f574c77633f in QSslSocket::connectToHost(QString const&, unsigned short, QFlags<QIODevice::OpenModeFlag>, QAbstractSocket::NetworkLayerProtocol) () from /lib/x86_64-linux-gnu/libQt5Network.so.5
#5 0x00007f574c73b24e in QAbstractSocket::connectToHost(QHostAddress const&, unsigned short, QFlags<QIODevice::OpenModeFlag>) () from /lib/x86_64-linux-gnu/libQt5Network.so.5
#6 0x00007f574e4736a9 in LanLinkProvider::udpBroadcastReceived() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.1
#7 0x00007f574cf896fe in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007f574c73be54 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5
#9 0x00007f574c73bee5 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5
#10 0x00007f574c74de71 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5
#11 0x00007f574da84ccf in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f574da8de10 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f574cf54d02 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f574cfac4b5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f574b5c65fd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f574b5c6880 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f574b5c690f in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f574cfab8ee in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f574cf5389b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f574cf5b672 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x000055a39a758966 in ?? ()
#22 0x00007f574c949cca in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#23 0x000055a39a758bca in _start ()
[Inferior 1 (process 83677) detached]

Bug Watch Updater (bug-watch-updater) on 2021-06-05

Changed in kdepim:
status:	Unknown → New

Affects		Status	Importance	Assigned to	Milestone
	KDE PIM	New	High	kde-bugs #116482
	kdepim (Ubuntu)	Fix Released	Undecided	Unassigned

Ubuntu
kdepim package

akregator is not crash proof

Bug Description

Other bug subscribers

Remote bug watches

Ubuntukdepim package

akregator is not crash proof

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
kdepim package