Bug #56369 “akregator is not crash proof” : Bugs : KDE PIM

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

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.

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-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

KDE PIM

akregator is not crash proof

Bug Description

Other bug subscribers

Remote bug watches