All of sudden, akregator now fails to start with graphical error message "Could not find the Akregator part; please check your installation" and then crashes. I also tried reinstalling the akregator package with no success.
severity 590147 serious
forwarded 590147 https://bugs.kde.org/show_bug.cgi?id=250162
I get a backtrace and forwarded to upstream. Akregator is unusable so
increase to serious.
Application: Akregator (akregator), signal: Segmentation fault
The current source language is "auto; currently asm".
[KCrash Handler]
#5 memcpy () at ../sysdeps/x86_64/memcpy.S:397
#6 0x00007f131945bd04 in c4_String::Init (this=0x7fff150e81a0, p=<value
optimized out>, n=1230779) at
../../../../akregator/plugins/mk4storage/metakit/src/string.cpp:195
#7 0x00007f1319453812 in c4_String (this=0x2032a30, ptr_=0x7fff150e8270,
selfDesc_=<value optimized out>) at
../../../../akregator/plugins/mk4storage/metakit/include/mk4str.inl:209
#8 c4_HandlerSeq::Prepare (this=0x2032a30, ptr_=0x7fff150e8270,
selfDesc_=<value optimized out>) at
../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:305
#9 0x00007f1319456e5d in c4_Persist::LoadAll (this=0x202ffc0) at
../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:1026
#10 0x00007f1319467479 in Akregator::Backend::StorageMK4Impl::open
(this=0x1ec4c00, autoCommit=true) at
../../../../akregator/plugins/mk4storage/storagemk4impl.cpp:134
#11 0x00007f131b125989 in Part (this=0x1ee83b0, parentWidget=<value optimized
out>, parent=<value optimized out>, __in_chrg=<value optimized out>,
__vtt_parm=<value optimized out>)
at ../../../akregator/src/akregator_part.cpp:222
#12 0x00007f131b1286cf in QObject*
KPluginFactory::createPartInstance<Akregator::Part>(QWidget*, QObject*,
QList<QVariant> const&) () from /usr/lib/kde4/akregatorpart.so
#13 0x00007f132cfd563c in KPluginFactory::create (this=0x1ef6880,
iface=0x7f132e2b6580 "KParts::ReadOnlyPart", parentWidget=<value optimized
out>, parent=0x1d9e0c0, args=...,
keyword=<value optimized out>) at ../../kdecore/util/kpluginfactory.cpp:191
#14 0x000000000040b014 in KPluginFactory::create<KParts::ReadOnlyPart>
(this=0x1d9e0c0) at /usr/include/KDE/../kpluginfactory.h:491
#15 Akregator::MainWindow::loadPart (this=0x1d9e0c0) at
../../../akregator/src/mainwindow.cpp:109
#16 0x000000000040b3a8 in Akregator::MainWindow::readProperties
(this=0x1d9e0c0, config=...) at ../../../akregator/src/mainwindow.cpp:152
#17 0x000000000040a829 in Akregator::MainWindow::autoReadProperties
(this=0x1d9e0c0) at ../../../akregator/src/mainwindow.cpp:266
#18 0x000000000040aae8 in MainWindow (this=0x1d9e0c0, parent=<value optimized
out>, f=<value optimized out>, __in_chrg=<value optimized out>,
__vtt_parm=<value optimized out>)
at ../../../akregator/src/mainwindow.cpp:89
#19 0x0000000000408c7a in Akregator::Application::newInstance
(this=0x7fff150e9db0) at ../../../akregator/src/main.cpp:58
#20 0x00007f132d4a3666 in KUniqueApplicationAdaptor::newInstance
(this=0x1e68ab0, asn_id=<value optimized out>, args=...) at
../../kdeui/kernel/kuniqueapplication.cpp:454
#21 0x00007f132d4a3ca6 in KUniqueApplicationAdaptor::qt_metacall
(this=0x1e68ab0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff150e8e20) at
./kuniqueapplication_p.moc:81
#22 0x00007f132c6e6421 in QDBusConnectionPrivate::deliverCall (this=<value
optimized out>, object=<value optimized out>, msg=<value optimized out>,
metaTypes=..., slotIdx=<value optimized out>)
at qdbusintegrator.cpp:904
#23 0x00007f132c6e762f in QDBusConnectionPrivate::activateCall (this=<value
optimized out>, object=0x1e68ab0, flags=337, msg=...) at
qdbusintegrator.cpp:809
#24 0x00007f132c6e810d in QDBusConnectionPrivate::activateObject (this=<value
optimized out>, node=<value optimized out>, msg=..., pathStartPos=<value
optimized out>) at qdbusintegrator.cpp:1364
#25 0x00007f132c6e83a8 in QDBusActivateObjectEvent::placeMetaCall
(this=0x1e7b290) at qdbusintegrator.cpp:1477
#26 0x00007f132cac3e89 in QObject::event (this=0x7fff150e9db0, e=0x1e7b290) at
kernel/qobject.cpp:1248
#27 0x00007f132bbdd69d in QApplication::event (this=0x7fff150e9db0,
e=0x1e7b290) at kernel/qapplication.cpp:2355
#28 0x00007f132bbd932c in QApplicationPrivate::notify_helper (this=0x1dac400,
receiver=0x7fff150e9db0, e=0x1e7b290) at kernel/qapplication.cpp:4302
#29 0x00007f132bbdf80b in QApplication::notify (this=0x7fff150e9db0,
receiver=0x7fff150e9db0, e=0x1e7b290) at kernel/qapplication.cpp:4185
#30 0x00007f132d49c836 in KApplication::notify (this=0x7fff150e9db0,
receiver=0x7fff150e9db0, event=0x1e7b290) at
../../kdeui/kernel/kapplication.cpp:302
#31 0x00007f132cab415c in QCoreApplication::notifyInternal
(this=0x7fff150e9db0, receiver=0x7fff150e9db0, event=0x1e7b290) at
kernel/qcoreapplication.cpp:726
#32 0x00007f132cab7804 in QCoreApplication::sendEvent (receiver=0x0,
event_type=<value optimized out>, data=0x1d7eec0) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#33 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value
optimized out>, data=0x1d7eec0) at kernel/qcoreapplication.cpp:1367
#34 0x00007f132caddbd3 in QCoreApplication::sendPostedEvents (s=<value
optimized out>) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#35 postEventSourceDispatch (s=<value optimized out>) at
kernel/qeventdispatcher_glib.cpp:276
#36 0x00007f13254f46c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#37 0x00007f13254f8538 in ?? () from /lib/libglib-2.0.so.0
#38 0x00007f13254f86ec in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#39 0x00007f132cadd713 in QEventDispatcherGlib::processEvents (this=0x1d7e630,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#40 0x00007f132bc8914e in QGuiEventDispatcherGlib::processEvents
(this=0x7f131931af96, flags=<value optimized out>) at
kernel/qguieventdispatcher_glib.cpp:204
#41 0x00007f132cab2a82 in QEventLoop::processEvents (this=<value optimized
out>, flags=) at kernel/qeventloop.cpp:149
#42 0x00007f132cab2e5c in QEventLoop::exec (this=0x7fff150e9d50, flags=) at
kernel/qeventloop.cpp:201
#43 0x00007f132cab7aeb in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1003
#44 0x00000000004096dd in main (argc=<value optimized out>, argv=<value
optimized out>) at ../../../akregator/src/main.cpp:103
I just fired up Akregator and it seems to work fine in sid. This bug may only affect squeeze testing. wt
Akregator starts and works correctly also for me, and the version in testing is the same as in unstable. Don't have a testing environment to test it there right now. Giovanni.
I have an install of Testing with Akregator with version 4.4.6-1 and it starts up just fine. I would appear that this problem is no longer an issue.
Hello, Can we both agree that this bug is not release-critical? Many users including me can start akregator fine. You probably ran into some kind of cache corruption issue here. It should be rare and many users will never see it hence it does not qualify as grave or serious, imho.
No this bug occurs after an upgrade. I could start agregator after deleting all my archive... So crash each time or loss all archive. It is for me release critical ask to kde teams but for me it is release critical.
Hello, Upgrade from what version? This supports my assumption that the problem is cache corruption. If I could reproduce it, I would agree it's RC. But now there are too many variables. To make things worse, akregator developement isn't very active upstream.
upgrade to 1.6.5 No it is an archive problem. Not a cahce problem. Cache could be purged (cahce does not have valuable data). Archive have valuable data and could not be purged without data loss Why ? I loss my archive. Some are now closed blog that I like to read ? I loss my data => RC by default When cache is corrupte I could not start it again... I need toi manually remove archive or do some manual and boring workarround see http://bugs.kde.org/show_bug.cgi?id=116482#c205 I have not the skills to debug this bug, but they are some file that coul allow youy to reproduce it at http://bugs.kde.org/attachment.cgi?id=48011 Bastien
metakit is a library bundled with Akregator. It is the source of the crash. I can reproduce this crash quite readily using the "Archive" directory from http://www.file-upload.net/download-2910539/Archive_old.tar.gz.html I minimized the details necessary to reproduce the bug and posted on upstream's bug tracker forum at http://www.equi4.com/fff/506 . In that post, I refer to "dump" -- this is a program from the upstream metakit tarball. As for what to do now: if someone wants to take a stab at *fixing* metakit's crash bug, that would be the next step!
tags 590147 help thanks Hello, All that stuff in bug report is useless because both this debian bug and upstream bug deal with consequences. When you see this crash and backtrace, the archive file had already been cut short and the data had already been lost. akregator is simply unable to read corrupt archive file on startup and rather than handling this condition gracefully, it crashes. However, there is no information how and when akregator fails to write correct archive file or otherwise corrupts it. So basically this bug is impossible to fix without a reliable way to reproduce it from the start to finish. During my 2 years of using akregator, I have never had this problem so there is not much I can do.
Do you agree that solving the first part of the problem will be really nice. Instead of alway crashing following a cosmics ray it will prompt and fix the error. I agree also with this part. But it is a second bug Should I duplicate the bug ? The two are from my point of view RC Thanks
Hello, No. No, the first part is not RC because: 1) it is rare enough 2) there is no data loss involved There is no info about the 2nd part and according to upstream, the bug has been there since etch (!!!) meaning two debian stable releases already have it. However, the debian bug has only been reported recently. This tells a lot about commodity of this bug. You may argue as much as you want but probability of this getting fixed is nearly 0% since it has not been fixed for many years and there is obvious lack of information. What is more, metakit has no future. Once akregrator is rewriten based on akonadi, this will go away.
--- Please enter the report below this line. --- Hi, I can confirm this bug. After one of the lasts "testing" upgrades, akregator crashes. Invoking the app deals with a couple of minutes of heavy hd activity (almost freezing the system) and then nothing takes place. Executing the app from a shell shows the following: <unknown program name>(3936)/: Communication problem with "akregator" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " KCrash: Application 'akregator' crashing... Debian Release: squeeze/sid 600 testing security.debian.org 600 testing ftp.es.debian.org 550 unstable www.debian-multimedia.org 550 unstable ftp.es.debian.org 500 testing-proposed-updates ftp.es.debian.org 500 stable dl.google.com --- Package information. --- Depends (Version) | Installed ========================================-+-================ kdebase-runtime | 4:4.4.5-1 libc6 (>= 2.2.5) | 2.11.2-7 libgcc1 (>= 1:4.1.1) | 1:4.4.5-8 libkde3support4 (>= 4:4.4) | 4:4.4.5-1 libkdecore5 (>= 4:4.4.4-2~) | 4:4.4.5-1 libkdepim4 (= 4:4.4.7-2) | 4:4.4.7-2 libkdeui5 (>= 4:4.4) | 4:4.4.5-1 libkhtml5 (>= 4:4.4) | 4:4.4.5-1 libkio5 (>= 4:4.4) | 4:4.4.5-1 libknotifyconfig4 (>= 4:4.4) | 4:4.4.5-1 libkontactinterface4 (>= 4:4.4.0) | 4:4.4.5-1 libkparts4 (>= 4:4.4) | 4:4.4.5-1 libkpimutils4 (>= 4:4.4) | 4:4.4.5-1 libkutils4 (>= 4:4.4) | 4:4.4.5-1 libqt4-dbus (>= 4:4.5.3) | 4:4.6.3-4 libqt4-xml (>= 4:4.5.3) | 4:4.6.3-4 libqtcore4 (>= 4:4.6.1) | 4:4.6.3-4 libqtgui4 (>= 4:4.5.3) | 4:4.6.3-4 libstdc++6 (>= 4.4.0) | 4.4.5-8 libsyndication4 (>= 4:4.4) | 4:4.4.5-1 Package's Recommends field is empty. Package's Suggests field is empty.
user release.debian.org@packages.debian.org usertag 590147 squeeze-can-defer tag 590147 squeeze-ignore kthxbye Seems like this doesn't affect everyone. We won't delay squeeze for this issue, so tagging accordingly. If a fix is available an update can still be considered, either before the release, or in a point update. Cheers, Julien
Could yoy post here the test case that you have posted here http://equi4.com/fff/506 Bastien
All I really did was rephrase the akregator issue in terms of the upstream "dump" command. If you look at the upstream tarball for "metakit", it builds a binary (command) called "dump". If you run it against one of the metakit database files from http://www.file-upload.net/download-2910539/Archive_old.tar.gz.html , you will find that it segfaults.
I am able to raise an exception with modification to metakit (upstream blessed) instead of crashing. I need a sponsor to upload a new version of metakit and finally fix this bug. Bastien
Is this still accurate? If so, where's the package you need sponsored? Cheers, Julien
Yes still accurate. Package libmetakit is under mentors, but you will open a flame war, last time I tried they said me that akregator is dead and I will lost my time and their time. Better will be to write new plugin using akonadi and so on. Bastien
Link to a .dsc please, or send the patch to the bug report, I won't go and troll the net to find it. Cheers, Julien
I propose to downgrade this to non-RC severity. If it all, it's a rare
corner-case.
Cheers,
Moritz
severity 590147 important
thanks
Going ahead, since noone objected.
Cheers,
Moritz