akregator is not crash proof
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE PIM |
New
|
High
|
|||
kdepim (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: akregator
Sometimes, my laptop runs flat out of juice, while in suspend. After a full boot, akregator (as part of kontact) crashes. If the current part in kantact was akregator before the depleted power situation, then kontact crashes. Removing everything in ~\.kde\
In KDE Bug Tracking System #116482, Luciano Montanaro (mikelima) wrote : | #10 |
In KDE Bug Tracking System #116482, Luciano Montanaro (mikelima) wrote : | #11 |
Created attachment 13495
The strace output for the failing execution
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #12 |
Have you upgraded to 3.5.0? Does Akregator work now for you?
In KDE Bug Tracking System #116482, Murtaza-iit84 (murtaza-iit84) wrote : | #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://
In KDE Bug Tracking System #116482, Thiago Macieira (thiago-kde) wrote : | #14 |
Pasting the backtrace:
(no debugging symbols found)
[KCrash handler]
#3 0x4241f89a in c4_FormatB::Define ()
from /usr/lib/
#4 0x4242491b in c4_HandlerSeq:
from /usr/lib/
#5 0x42424e7a in c4_Persist::LoadAll ()
from /usr/lib/
#6 0x4242509c in c4_Storage:
from /usr/lib/
#7 0x42407e54 in Akregator:
from /usr/lib/
#8 0x4240844a in Akregator:
from /usr/lib/
#9 0x400c1e96 in Akregator:
from /usr/lib/
#10 0x400c2a02 in Akregator:
from /usr/lib/
#11 0x400c2e22 in Akregator:
from /usr/lib/
#12 0x400c339a in Akregator:
from /usr/lib/
#13 0x422e49ba in Akregator:
from /usr/lib/
#14 0x422e4d4a in Akregator:
from /usr/lib/
#15 0x422dc0f5 in Akregator:
from /usr/lib/
#16 0x422b8d02 in Akregator:
from /usr/lib/
#17 0x422ee1b2 in Akregator:
from /usr/lib/
#18 0x40994415 in DCOPClient::receive () from /usr/lib/
#19 0x409949f9 in DCOPClient::send () from /usr/lib/
#20 0x40994fd0 in DCOPRef:
#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 KUniqueApplicat
from /usr/lib/
#32 0x408e4fc9 in KUniqueApplicat
from /usr/lib/
#33 0x40cb5b57 in QObject:
#34 0x41046055 in QSignal::signal () from /usr/lib/
#35 0x40cd3a40 in QSignal::activate () from /usr/lib/
#36 0x40cdb354 in QSingleShotTime
#37 0x40c4b698 in QApplication:
#38 0x40c4b8b6 in QApplication:
#39 0x408d1abc in KApplication:
#40 0x40bdb5e5 in QApplication:
#41 0x40c3c98c in QEventLoop:
#42 0x40bef35c in QEventLoop:
#43 0x40c63da2 in QEventLoop:
#44 0x40c63ccb in QEventLoop::exec () from /usr/lib/
#45 0x40c4a225 in QApplication::exec () from /usr/lib/
#46 0x08050d80 in ?? ()
#47 0xbffff664 in ?? ()
#48 ...
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #15 |
*** Bug 119476 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #16 |
*** Bug 120446 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #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/
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).
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #18 |
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/
@@ -56,6 +56,13 @@
#include <qwidgetlist.h>
#include <private/
+#include <cerrno>
+#include <sys/types.h>
+#include <signal.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include <unistd.h>
+
#include "aboutdata.h"
#include "actionmanageri
#include "akregator_part.h"
@@ -68,6 +75,7 @@
#include "frame.h"
#include "article.h"
#include "kernel.h"
+#include "kcursorsaver.h"
#include "notificationma
#include "pageviewer.h"
#include "plugin.h"
@@ -135,8 +143,21 @@
m_storage = 0;
Backend:
+
if (factory != 0)
- m_storage = factory-
+ {
+
+ if (Settings:
+ {
+ if (tryToLock(
+ m_storage = factory-
+ else
+ m_storage = dummyFactory-
+ }
+ else
+ m_storage = factory-
+ }
+
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[0] = 0;
+ return QString:
+}
+// taken from KMail
+bool Part::tryToLock
+{
+// Check and create a lock file to prevent concurrent access to metakit archive
+ QString appName = kapp->instanceN
+ if ( appName.isEmpty() )
+ appName = "akregator";
+
+ QString programName;
+ const KAboutData *about = kapp->aboutData();
+ if ( about )
+ programName = about->
+ if ( programName.
+ programName = i18n("Akregator");
+
+ QString lockLocation = locateLocal("data", "akregator/lock");
+ KSimpleConfig config(
+ int oldPid = config.
+ const QString oldHostName = config.readEnt...
In KDE Bug Tracking System #116482, Y-coolo (y-coolo) wrote : | #19 |
Are you still interested in a corrupted file? I have one :)
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #20 |
*** This bug has been marked as a duplicate of 121826 ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #21 |
eh, wrong direction. need coffee.
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #22 |
*** Bug 121826 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #23 |
*** Bug 124201 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #24 |
*** Bug 129452 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #25 |
*** Bug 130224 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #26 |
Ken writes in 130224:
"This happened after a power outage so I am not surprised something got
corrupted. [...]"
In KDE Bug Tracking System #116482, Bugs-kde-org-g (bugs-kde-org-g) wrote : | #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.
In KDE Bug Tracking System #116482, Bugs-kde-org-g (bugs-kde-org-g) wrote : | #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://
Fred van Zwieten (fvzwieten) wrote : | #1 |
Update: just found out that removing the archive map and the lock file from ~/.kde/
Fred van Zwieten (fvzwieten) wrote : | #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
Andreas Simon (andreas-w-simon) wrote : | #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.
Changed in kdepim: | |
status: | Unknown → Confirmed |
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #29 |
*** Bug 117978 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #30 |
*** Bug 128313 has been marked as a duplicate of this bug. ***
Scott Beamer (angrykeyboarder) wrote : | #4 |
Just wondering...
Is *any* application "crash-proof"?
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #31 |
*** Bug 132411 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #32 |
*** Bug 137976 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Jure Repinc (jlp) wrote : | #33 |
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
[Thread debugging using libthread_db enabled]
[New Thread -1244051760 (LWP 1558)]
[KCrash handler]
#6 c4_Column:
#7 0xb5967b73 in c4_FormatV:
at format.cpp:1026
#8 0xb59681ee in c4_FormatV::Get (this=0x85bdbb8, index_=0,
length_
#9 0xb596b790 in c4_Handler:
buf_
#10 0xb597b237 in c4_Sequence::Get (this=0x85be370, index_=0, propId_=35,
buf_
#11 0xb596fb4a in c4_Reference:
at ./../include/
#12 0xb597aab7 in c4_ViewRef:
at viewx.cpp:643
#13 0xb5974e15 in c4_Storage:
name_
#14 0xb597504d in c4_Storage::GetAs (this=0x855eea0,
description
at store.cpp:279
#15 0xb5955279 in FeedStorageMK4Impl (this=0x85bdf70, url=@0x85bde00,
main=0x8091458) at feedstoragemk4i
#16 0xb5958e7a in Akregator:
this=0x8091458, url=@0x85bde00) at storagemk4impl.
#17 0xb7f7b2e7 in Akregator:
at feed.cpp:221
#18 0xb7f7c14a in Akregator:
#19 0xb7f878ba in Akregator:
node=
#20 0xb7f8784d in Akregator:
node=
#21 0xb7f87d74 in Akregator:
doc=
#22 0xb5b625fc in Akregator:
doc=
#23 0xb5b59a22 in Akregator:
at akregator_
#24 0xb5b56b94 in Akregator:
at akregator_
#25 0xb5b59fd2 in Akregator:
at akregator_
#26 0xb5b6c156 in Akregator:
fun=
replyData=
#27 0xb6dd1fa8 in DCOPClient::receive (this=0x8063c38, objId=@0xbfc4c2a4,
fun=
replyData=
#28 0xb6dd27ee in DCOPClient::send (this=0x8063c38, remApp=@0xbfc4c29c,
remObjId=
at dcopclient.cpp:1060
#29 0xb6dcba03 in DCOPRef:
In KDE Bug Tracking System #116482, Jure Repinc (jlp) wrote : | #34 |
I just upgraded to 3.5.6 an the crash remains.
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #35 |
*** Bug 141665 has been marked as a duplicate of this bug. ***
Sarah Kowalik (hobbsee-deactivatedaccount) wrote : | #5 |
will attempt to grab that patch post-beta
Changed in kdepim: | |
assignee: | nobody → hobbsee |
status: | Unconfirmed → In Progress |
Andrew Ash (ash211) wrote : | #6 |
Were you able to get that patch into feisty, hobbsee?
Sarah Kowalik (hobbsee-deactivatedaccount) wrote : | #7 |
no.
it'll be in kde 3.5.7, out soon.
Changed in kdepim: | |
status: | In Progress → Fix Committed |
Sarah Kowalik (hobbsee-deactivatedaccount) wrote : | #8 |
fixed in gutsy. (or will be, when i get it uploaded)
Changed in kdepim: | |
status: | Fix Committed → Fix Released |
In KDE Bug Tracking System #116482, Raul Sanchez Siles (rasasi78) wrote : | #36 |
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/
[Thread debugging using libthread_db enabled]
[New Thread -1243031856 (LWP 9057)]
[KCrash handler]
#6 0xb7cbba1c in memcpy () from /lib/i686/
#7 0xb5707153 in c4_String::Init (this=0xb562cc6c, p=0x80aa39b, n=135651325)
at /tmp/buildd/
#8 0xb571bb03 in c4_HandlerSeq:
selfDesc_=true)
at /tmp/buildd/
#9 0xb571fea5 in c4_Persist::LoadAll (this=0x80aa2e8)
at /tmp/buildd/
#10 0xb572010d in c4_Storage (this=0x80abf60,
fname_
at /tmp/buildd/
#11 0xb5702971 in Akregator:
autoCommit=
at /tmp/buildd/
#12 0xb5a17aab in Part (this=0x8116528, parentWidget=
parent=
at /tmp/buildd/
#13 0xb5a25808 in KParts:
this=0x81102a8, parentWidget=
widgetName=
name=0x8052f3d "akregator_part",
className=
at /usr/include/
#14 0xb7f6177f in KParts:
parentWidge
parent=
classname=
at /tmp/buildd/
#15 0xb7f617e1 in KParts:
parent=
classname=
at /tmp/buildd/
#16 0xb76a3931 in KLibFactory::create (this=0x81102a8, parent=0x8098500,
name=0x8052f3d "akregator_part",
classname=
at /tmp/buildd/
#17 0x08051dc7 in Akregator:
at /tmp/buildd/
#18 0x080524e9 in Akregator:
at /tmp/buildd/
#19 0xb7769b86 in KUniqueApplicat
at /tmp/buildd/
#20 0xb776ff28 in KUniqueApplicat
_o=0xbf8ad098) at ./kuniqueapplic
#21 0xb70a9e1b in QObject:
o=0xbf8a...
In KDE Bug Tracking System #116482, Raul Sanchez Siles (rasasi78) wrote : | #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.
In KDE Bug Tracking System #116482, Jack Bunce (jackbunce) wrote : | #38 |
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
[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/
#11 0xb59d90d3 in c4_HandlerSeq:
from /opt/kde3/
#12 0xb59dcaa5 in c4_Persist::LoadAll ()
from /opt/kde3/
#13 0xb59e170d in c4_Storage:
from /opt/kde3/
#14 0xb59c5b06 in Akregator:
from /opt/kde3/
#15 0xb59c7f21 in Akregator:
from /opt/kde3/
#16 0xb7f422c8 in Akregator:
from /opt/kde3/
#17 0xb7f43030 in Akregator:
from /opt/kde3/
#18 0xb7f4d805 in Akregator:
from /opt/kde3/
#19 0xb7f4d90c in Akregator:
from /opt/kde3/
#20 0xb7f4dd7e in Akregator:
from /opt/kde3/
#21 0xb6274cdc in Akregator:
from /opt/kde3/
#22 0xb62703ab in Akregator:
from /opt/kde3/
#23 0xb626df4c in Akregator:
from /opt/kde3/
#24 0xb626a91b in Akregator:
from /opt/kde3/
#25 0xb6269770 in Akregator:
from /opt/kde3/
#26 0xb7812e77 in DCOPClient::receive () from /opt/kde3/
#27 0xb7813602 in DCOPClient::send () from /opt/kde3/
#28 0xb7813c3f in DCOPRef:
#29 0x08050796 in Akregator:
#30 0xb798f26d in KUniqueApplicat
from /opt/kde3/
#31 0xb79d4eb8 in KUniqueApplicat
from /opt/kde3/
#32 0xb738bf1d in QObject:
from /usr/lib/
#33 0xb76c70ae in QSignal::signal () from /usr/lib/
#34 0xb73a7ff7 in QSignal::activate () from /usr/lib/
#35 0xb73af383 in QSingleShotTime
from /usr/lib/
#36 0xb732c9c7 in QApplication:
from /usr/lib/
#37 0xb732d791 in QApplication:
#38 0xb79e4202 in KApplication:
#39 0xb7321bd3 in QEventL...
In KDE Bug Tracking System #116482, Rosenauer (rosenauer) wrote : | #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/
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.
In KDE Bug Tracking System #116482, Rosenauer (rosenauer) wrote : | #40 |
Created attachment 20916
problematic feed-archive
when uncompressing this archive to your akregator-
crash at startup.
In KDE Bug Tracking System #116482, Chain (chain) wrote : | #41 |
You can check your files with the utilities on their page.
http://
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 :)
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #42 |
*** Bug 155260 has been marked as a duplicate of this bug. ***
grauscho (grauscho) wrote : | #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/
akregator seems to work again now.
In KDE Bug Tracking System #116482, Pnemec (pnemec) wrote : | #43 |
reproducet with openSUSE 10.3. KDE 3.5.7 novell bugzilla #371701. I am contacting Frank with PM.
In KDE Bug Tracking System #116482, Thomas Koch (thomas-koch-ro) wrote : | #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/
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...
In KDE Bug Tracking System #116482, Chris-fritz (chris-fritz) wrote : | #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.
In KDE Bug Tracking System #116482, Chris-fritz (chris-fritz) wrote : | #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
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #47 |
*** Bug 150543 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #48 |
*** Bug 152542 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #49 |
*** Bug 147673 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Goetzchrist-m (goetzchrist-m) wrote : | #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/
#7 0xb3d48be1 in ?? () from /usr/lib/
#8 0xb3d44454 in Akregator:
from /usr/lib/
#9 0xb3d4570c in Akregator:
from /usr/lib/
#10 0xb3d2c66a in ?? () from /usr/lib/
#11 0xb3d2c853 in ?? () from /usr/lib/
#12 0xb77b84f9 in QMetaObject:
#13 0xb77b8bc2 in QMetaObject:
#14 0xb77bf037 in ?? () from /usr/lib/
#15 0xb77bf15c in ?? () from /usr/lib/
#16 0xb77b3c9a in QObject::event () from /usr/lib/
#17 0xb6e02c0c in QApplicationPri
from /usr/lib/
#18 0xb6e07799 in QApplication:
#19 0xb7c32ef3 in KApplication:
#20 0xb77a36a9 in QCoreApplicatio
from /usr/lib/
#21 0xb77d11a1 in ?? () from /usr/lib/
#22 0xb77cea40 in ?? () from /usr/lib/
#23 0xb5bbfbf8 in g_main_
#24 0xb5bc2e5e in ?? () from /usr/lib/
#25 0xb5bc33ac in g_main_
#26 0xb77cef98 in QEventDispatche
from /usr/lib/
#27 0xb6e96195 in ?? () from /usr/lib/
#28 0xb77a292d in QEventLoop:
#29 0xb77a2abd in QEventLoop::exec () from /usr/lib/
#30 0xb77a4d3d in QCoreApplicatio
#31 0xb6e02567 in QApplication::exec () from /usr/lib/
#32 0x0804edab in _start ()
#0 0xb7efe410 in __kernel_vsyscall ()
In KDE Bug Tracking System #116482, Goetzchrist-m (goetzchrist-m) wrote : | #51 |
Also, when removing the folder ~/.kde4/
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #52 |
*** Bug 169066 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Goetzchrist-m (goetzchrist-m) wrote : | #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.
In KDE Bug Tracking System #116482, Datradan (datradan) wrote : | #54 |
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/
#7 0xb3d65be1 in ?? () from /usr/lib/
#8 0xb3d61454 in Akregator:
from /usr/lib/
#9 0xb3d6270c in Akregator:
from /usr/lib/
#10 0xb3d4966a in ?? () from /usr/lib/
#11 0xb3d49853 in ?? () from /usr/lib/
#12 0xb77f24f9 in QMetaObject:
#13 0xb77f2bc2 in QMetaObject:
#14 0xb77f9037 in ?? () from /usr/lib/
#15 0xb77f915c in ?? () from /usr/lib/
#16 0xb77edc9a in QObject::event () from /usr/lib/
#17 0xb6e3dc0c in QApplicationPri
from /usr/lib/
#18 0xb6e427a9 in QApplication:
#19 0xb7c74f53 in KApplication:
#20 0xb77dd6a9 in QCoreApplicatio
from /usr/lib/
#21 0xb780b1a1 in ?? () from /usr/lib/
#22 0xb7808a40 in ?? () from /usr/lib/
#23 0xb5bf9dd6 in g_main_
#24 0xb5bfd193 in ?? () from /usr/lib/
#25 0xb5bfd74e in g_main_
#26 0xb7808f98 in QEventDispatche
from /usr/lib/
#27 0xb6ed11b5 in ?? () from /usr/lib/
#28 0xb77dc92d in QEventLoop:
#29 0xb77dcabd in QEventLoop::exec () from /usr/lib/
#30 0xb77ded3d in QCoreApplicatio
#31 0xb6e3d567 in QApplication::exec () from /usr/lib/
#32 0x0804edab in _start ()
#0 0xb7f3f410 in __kernel_vsyscall ()
and here terminal messages when i run akregator:
othmane@
akregator(6958) Akregator:
akregator(6958) Akregator:
akregator(6958) Akregator:
-------
name : "Metakit storage ...
In KDE Bug Tracking System #116482, Datradan (datradan) wrote : | #55 |
I've found why akreagator crash,
in ~/.kde4/
I hope this is useful to resolve this bug :-)
In KDE Bug Tracking System #116482, Goetzchrist-m (goetzchrist-m) wrote : | #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.
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #57 |
*** Bug 153615 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Dominik Tritscher (dominik-tritscher) wrote : | #58 |
I Played arrount a bit with the maxArticleNumber and removed the archiveMode=
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #59 |
*** Bug 191645 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #60 |
*** Bug 197069 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote : | #61 |
I think this could be another instance of bug 191685, based on its duplicates.
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #62 |
*** Bug 194192 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote : | #63 |
*** Bug 198101 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #64 |
*** Bug 197830 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote : | #65 |
*** Bug 199194 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #66 |
*** Bug 199443 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #67 |
*** Bug 200373 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #68 |
*** Bug 163572 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #69 |
*** Bug 203892 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #70 |
*** Bug 204392 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #71 |
*** Bug 204489 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #72 |
*** Bug 205040 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #73 |
*** Bug 205063 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #74 |
*** Bug 205177 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Samuel-brack (samuel-brack) wrote : | #75 |
*** Bug 205197 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #76 |
*** Bug 205981 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #77 |
*** Bug 206123 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #78 |
*** Bug 207180 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Heimen Stoffels (vistaus) wrote : | #79 |
Any updates on this? It still happens on KDE 4.3.1:
In KDE Bug Tracking System #116482, T-artem (t-artem) wrote : | #80 |
Updates? 36 duplicates and still counting. :)
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #81 |
*** Bug 207478 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #82 |
*** Bug 208582 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #83 |
*** Bug 209738 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #84 |
*** Bug 210184 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #85 |
*** Bug 209798 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote : | #86 |
*** Bug 210372 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #87 |
*** Bug 211092 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Seba78 (teo78) wrote : | #88 |
On Lun 19 Oct 2009 20:44:11 Christophe Giboudeaux escribió:
> https:/
>
>
> 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. ***
In KDE Bug Tracking System #116482, Heimen Stoffels (vistaus) wrote : | #89 |
What's the status of this bug? Because it's still not fixed...
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #90 |
*** Bug 212185 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #91 |
*** Bug 212238 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #92 |
*** Bug 212354 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #93 |
*** Bug 212636 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #94 |
*** Bug 213106 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, FranJPR (fjperezor) wrote : | #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!
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #96 |
*** Bug 214113 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #97 |
*** Bug 214688 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #98 |
*** Bug 216163 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #99 |
*** Bug 216164 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #100 |
*** Bug 216337 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #101 |
*** Bug 216757 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #102 |
*** Bug 217050 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #103 |
*** Bug 217345 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Primoz (papic644) wrote : | #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....
In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote : | #105 |
*** Bug 216830 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #106 |
*** Bug 217401 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Psychonaut (psychonaut) wrote : | #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.
In KDE Bug Tracking System #116482, helios (martin-lichtvoll) wrote : | #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/
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?
In KDE Bug Tracking System #116482, helios (martin-lichtvoll) wrote : | #109 |
thing=>think. And who started clean with 4.x of course.
In KDE Bug Tracking System #116482, Nicolás Alvarez (nicolas-alvarez) wrote : | #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!)
In KDE Bug Tracking System #116482, Christopherheiny (christopherheiny) wrote : | #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).
In KDE Bug Tracking System #116482, Nicolás Alvarez (nicolas-alvarez) wrote : | #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" :)
In KDE Bug Tracking System #116482, Alexo-tmp (alexo-tmp) wrote : | #113 |
Created attachment 38978
/home/alex/
In KDE Bug Tracking System #116482, Mark Rose (markrose) wrote : | #114 |
This feed was causing akregator to crash on startup, and crash when I add it.
http://
It does NOT parse correctly. Here is the malformed entry:
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).
In KDE Bug Tracking System #116482, Dominik Tritscher (dominik-tritscher) wrote : | #115 |
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
#6 QDomHandler:
#7 0x00007f72a5b8aae7 in QXmlSimpleReade
#8 0x00007f72a5b96df8 in QXmlSimpleReade
#9 0x00007f72a5b96288 in QXmlSimpleReade
#10 0x00007f72a5b96d70 in QXmlSimpleReade
#11 0x00007f72a5b96288 in QXmlSimpleReade
#12 0x00007f72a5b96d70 in QXmlSimpleReade
#13 0x00007f72a5b96288 in QXmlSimpleReade
#14 0x00007f72a5b96d70 in QXmlSimpleReade
#15 0x00007f72a5b971d8 in QXmlSimpleReade
#16 0x00007f72a5b9754e in QXmlSimpleReade
#17 0x00007f72a5b7e822 in QDomDocumentPri
#18 0x00007f728c113a3c in Syndication:
#19 0x00007f728c0cd42a in Syndication:
#20 0x00007f728c11fe06 in Syndication:
#21 0x00007f728c11e1c7 in Syndication:
#22 0x00007f728c11e51d in Syndication:
#23 0x00007f72a9ddcddc in QMetaObject:
#24 0x00007f728c120553 in Syndication:
#25 0x00007f728c12130f in Syndication:
#26 0x00007f728c121493 in Syndication:
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #116 |
*** Bug 218692 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote : | #117 |
*** Bug 220471 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote : | #118 |
*** Bug 220564 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #119 |
*** Bug 220401 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #120 |
*** Bug 220084 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #121 |
*** Bug 220061 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Jimmy Berry (boombatower) wrote : | #122 |
*** Bug 223529 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #123 |
*** Bug 223023 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #124 |
*** Bug 222115 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #125 |
*** Bug 221678 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Osterfeld (osterfeld) wrote : | #126 |
*** Bug 221658 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Juha Tiensyrjä (juha-tiensyrja) wrote : | #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.
In KDE Bug Tracking System #116482, Juha Tiensyrjä (juha-tiensyrja) wrote : | #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.
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #129 |
*** Bug 225882 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #130 |
*** Bug 224867 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Marc Hildebrandt (serenity.) wrote : | #131 |
Created attachment 41391
New crash information added by DrKonqi
Kontact worked fine and normal. Then, day to day, it refused to start.
In KDE Bug Tracking System #116482, Herr-schneider-m (herr-schneider-m) wrote : | #132 |
Created attachment 41470
New crash information added by DrKonqi
The same thing happens when trying to fetch all sources from the tray icon...
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #133 |
*** Bug 230815 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, KIAaze (zohn-joidberg) wrote : | #134 |
*** Bug 231908 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #135 |
*** Bug 232076 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #136 |
*** Bug 231920 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #137 |
*** Bug 230523 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #138 |
*** Bug 226506 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #139 |
*** Bug 229677 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #140 |
*** Bug 232310 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #141 |
*** Bug 223837 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #142 |
*** Bug 226042 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #143 |
*** Bug 224971 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #144 |
*** Bug 223552 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #145 |
*** Bug 221487 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #146 |
*** Bug 218838 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, CTown (ctownthug711) wrote : | #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:
<outline title="BBC News | News Front Page | World Edition" useCustomFetchI
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #148 |
*** Bug 232731 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote : | #149 |
*** Bug 234739 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, E-6at-t (e-6at-t) wrote : | #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://
I can send the file to anyone if it will be useful to them (but it is 11.2Mb)
In KDE Bug Tracking System #116482, Diazona (diazona) wrote : | #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/
In KDE Bug Tracking System #116482, Flope (flope) wrote : | #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.
In KDE Bug Tracking System #116482, James Holby (jamesdholby) wrote : | #153 |
Created attachment 47555
New crash information added by DrKonqi
After a restart Akregator comes up with a segmentation fault after logging in.
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #154 |
*** Bug 240688 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #155 |
*** Bug 238978 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #156 |
*** Bug 238023 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #157 |
*** Bug 237982 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #158 |
*** Bug 234014 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Nicolás Alvarez (nicolas-alvarez) wrote : | #159 |
Reported in 2005, 95 duplicates, and it's still not fixed. You must be proud.
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #160 |
*** Bug 237569 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #161 |
*** Bug 236958 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #162 |
*** Bug 238479 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #163 |
*** Bug 237763 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #164 |
*** Bug 236423 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #165 |
*** Bug 234208 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #166 |
*** Bug 240766 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #167 |
*** Bug 240559 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #168 |
*** Bug 240154 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #169 |
*** Bug 238686 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #170 |
*** Bug 236468 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #171 |
*** Bug 235747 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #172 |
*** Bug 235646 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #173 |
*** Bug 235332 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #174 |
*** Bug 235221 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, helios (martin-lichtvoll) wrote : | #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...
In KDE Bug Tracking System #116482, helios (martin-lichtvoll) wrote : | #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:/
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[...]
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #177 |
*** Bug 241151 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #178 |
*** Bug 241264 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, József Kószó (k-joe) wrote : | #179 |
Created attachment 48011
A good and a bad .mk4 file for same feed.
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #180 |
*** Bug 241928 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #181 |
*** Bug 242369 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #182 |
*** Bug 242422 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Thomas Tanghus (tanghus) wrote : | #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...
In KDE Bug Tracking System #116482, SKAL (sir-kalot) wrote : | #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:
Object::connect: (sender name: 'feedtree')
Object::connect: (receiver name: 'akregator_view')
z-lmutt@
sock_file=
In KDE Bug Tracking System #116482, SKAL (sir-kalot) wrote : | #185 |
Comment on attachment 48479
New crash information added by DrKonqi
Removing the ~/.kde/
In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote : | #186 |
*** Bug 245728 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Jonathan Thomas (echidnaman) wrote : | #187 |
*** Bug 244268 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #188 |
*** Bug 247457 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #189 |
*** Bug 247309 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #190 |
*** Bug 247298 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #191 |
*** Bug 244290 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #192 |
*** Bug 243660 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Alvin (alvind) wrote : | #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/
#7 0x00007f531ee71474 in c4_String::Init (this=0x7fffdb2
#8 0x00007f531ee68c52 in c4_String (this=0x20e3340, ptr_=0x7fffdb23
#9 c4_HandlerSeq:
#10 0x00007f531ee6c470 in c4_Persist::LoadAll (this=0x20dc7c0) at ../../.
In KDE Bug Tracking System #116482, Neoclust-kde (neoclust-kde) wrote : | #194 |
*** Bug 248631 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, FiNeX (finex) wrote : | #195 |
*** Bug 250655 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Roucaries-bastien+bug (roucaries-bastien+bug) wrote : | #196 |
*** Bug 250162 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Roucaries-bastien+bug (roucaries-bastien+bug) wrote : | #197 |
This is debian bug http://
Please correct it before release.
Bastien
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #198 |
*** Bug 250936 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #199 |
*** Bug 246990 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #200 |
*** Bug 249538 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #201 |
*** Bug 250299 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #202 |
*** Bug 247829 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #203 |
*** Bug 246975 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, matthiasf (matthiasf) wrote : | #204 |
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_
#1 0x00007f6224035e30 in ?? () from /usr/lib/
#2 0x00007f6224035e69 in ?? () from /usr/lib/
#3 0x00007f6237c0bcb0 in start_thread () from /lib/libpthread
#4 0x00007f623b5207ad in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()
Thread 1 (Thread 0x7f623e8ec760 (LWP 7285)):
#0 0x00007f62274625e1 in c4_Handler:
at /home/anke/
#1 0x00007f622746fdb2 in c4_Sequence::Get (this=0x313a400, index_=19181, propId_=<value optimized out>, buf_=...)
at /home/anke/
#2 0x00007f62274707c4 in GetData (this=0x7fffb37
#3 c4_IntRef::operator t4_i32 (this=0x7fffb37
#4 0x00007f622746742d in c4_HashViewer:
at /home/anke/
#5 0x00007f6227467e0f in c4_HashViewer:
at /home/anke/
#6 0x00007f62274681c2 in c4_HashViewer:
at /home/anke/
#7 0x00007f622745a46a in c4_CustomSeq:
at /home/anke/
#8 0x00007f622746e93a in c4_View::Find (this=0x32ae5e8, crit_=<value optimized out>, start_=0)
at /home/anke/
#9 0x00007f6227472544 in Akregator:
at /home/anke/
#10 0x00007f6227475b20 in Akregator:
at /home/anke/
#11 0x00007f6229098967 in Akregator:
archive_=<value optimized out>) at /home/anke/
In KDE Bug Tracking System #116482, matthiasf (matthiasf) wrote : | #205 |
Created attachment 51674
Debug output
Here is the debug output of akregator when it fails to start.
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #206 |
*** Bug 251398 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #207 |
*** Bug 246024 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #208 |
*** Bug 252034 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #209 |
*** Bug 251736 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #210 |
*** Bug 252525 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #211 |
*** Bug 250249 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #212 |
*** Bug 253082 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #213 |
*** Bug 253854 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Marcel9 (marcel9) wrote : | #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/
#9 0xb084b14c in c4_String (this=0x8137da8, ptr_=0xbfca43bc, selfDesc_=true) at /usr/src/
#10 c4_HandlerSeq:
#11 0xb084e8ea in c4_Persist::LoadAll (this=0x8137ea0) at /usr/src/
#12 0xb0852cbe in c4_Storage:
at /usr/src/
In KDE Bug Tracking System #116482, Marcel9 (marcel9) wrote : | #215 |
Hey,
Here is my Archive: http://
I solved the problem:
rename the archive folder /home/.
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
In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote : | #216 |
*** Bug 256621 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote : | #217 |
*** Bug 257120 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote : | #218 |
*** Bug 257250 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #219 |
*** Bug 256963 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote : | #220 |
[Comment from a bug triager]
Bug 258115 comment 1 contains a feed that seem to cause this crash on 4.6beta1
In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote : | #221 |
*** Bug 258115 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Hobbyblobby (hobbyblobby) wrote : | #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=0x7fff857
#8 0x00007fcafec431f2 in c4_String (this=0xdc9160, ptr_=0x7fff8579
#9 c4_HandlerSeq:
#10 0x00007fcafec46b10 in c4_Persist::LoadAll (this=0xdc8eb0) at /usr/src/
#11 0x00007fcafec52b02 in Akregator:
at /usr/src/
In KDE Bug Tracking System #116482, Dario Andres (andresbajotierra) wrote : | #223 |
*** Bug 259492 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #224 |
*** Bug 259694 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #225 |
*** Bug 259789 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Jason Mours (jason-mours) wrote : | #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/
#11 0x00007f1a58abcdbf in c4_FormatB::SetOne (this=0xd83630, index_=851085, xbuf_=<value optimized out>, ignoreMemos_=<value optimized out>)
at /usr/src/
#12 0x00007f1a58abd0d4 in c4_FormatB::Commit (this=0xd83630, ar_=...) at /usr/src/
#13 0x00007f1a58ac17d4 in c4_SaveContext:
at /usr/src/
#14 0x00007f1a58ac18fe in c4_SaveContext:
at /usr/src/
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #227 |
*** Bug 261211 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #228 |
*** Bug 261805 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #229 |
*** Bug 262244 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, helios (martin-lichtvoll) wrote : | #230 |
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:/
>
> 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://
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...
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #231 |
*** Bug 253625 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #232 |
*** Bug 264178 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, ronny (ronny-standtke) wrote : | #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 ../../.
#7 c4_FormatB:
#8 0x00007f397e082af3 in c4_FormatB::Define (this=0xe6c400, ptr_=0x7fff4461
#9 0x00007f397e08475e in c4_HandlerSeq:
#10 0x00007f397e087fd0 in c4_Persist::LoadAll (this=0xe3c9a0) at ../../.
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #234 |
*** Bug 264527 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Jemand (jemand) wrote : | #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/
#7 0x00007f9cacc41853 in c4_Column:
#8 0x00007f9cacc49b64 in c4_FormatB::GetOne (this=0x733e7b0, index_=<value optimized out>, length_
#9 0x00007f9cacc49b89 in c4_FormatS::Get (this=0x4db3eb0, index_=7602577, length_
#10 0x00007f9cacc4c1d6 in c4_Handler:
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #236 |
*** Bug 265594 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #237 |
*** Bug 266053 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #238 |
*** Bug 266511 has been marked as a duplicate of this bug. ***
Changed in kdepim: | |
importance: | Unknown → High |
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #239 |
*** Bug 267299 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Roucaries-bastien+bug (roucaries-bastien+bug) wrote : | #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
In KDE Bug Tracking System #116482, Samuel-brack (samuel-brack) wrote : | #241 |
Bastien, is there a patch available yet? If yes, we'd appreciate it if you'd upload it here, too.
In KDE Bug Tracking System #116482, Roucaries-bastien+bug (roucaries-bastien+bug) wrote : | #242 |
see http://
Will not fix the crash but instead of segv raise exception
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #243 |
*** Bug 267620 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #244 |
*** Bug 268493 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #245 |
*** Bug 269138 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #246 |
*** Bug 270645 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #247 |
*** Bug 270727 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #248 |
*** Bug 271312 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #249 |
*** Bug 271944 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #250 |
*** Bug 273099 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #251 |
*** Bug 276452 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Andrei Slavoiu (ansla80) wrote : | #252 |
For anybody hitting this issue, here's an easy way to identify the corrupt mk4 file:
cd ~/.kde4/
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.
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #253 |
*** Bug 275754 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #254 |
*** Bug 277212 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, trionghost (trionghost) wrote : | #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/
#7 c4_FormatB:
#8 0x00007f52119f3a63 in c4_FormatB::Define (this=0x8c5940, ptr_=0x7fff343b
#9 0x00007f52119f61ce in c4_HandlerSeq:
#10 0x00007f52119f9b50 in c4_Persist::LoadAll (this=0x8a6f90) at /usr/src/
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #256 |
*** Bug 279447 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #257 |
*** Bug 280579 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #258 |
*** Bug 281645 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #259 |
*** Bug 282563 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Jaak-x (jaak-x) wrote : | #260 |
(In reply to comment #242)
> For anybody hitting this issue, here's an easy way to identify the corrupt mk4
> file:
>
> cd ~/.kde4/
> 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/
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* =[
In KDE Bug Tracking System #116482, Andrei Slavoiu (ansla80) wrote : | #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://
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #262 |
*** Bug 291403 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #263 |
*** Bug 296791 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #264 |
*** Bug 298843 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, adaptee (adaptee) wrote : | #265 |
*** Bug 299644 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #266 |
*** Bug 305250 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Christoph-maxiom (christoph-maxiom) wrote : | #267 |
*** Bug 305938 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Christoph-maxiom (christoph-maxiom) wrote : | #268 |
*** Bug 307368 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, adaptee (adaptee) wrote : | #269 |
*** Bug 308076 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Winter-s (winter-s) wrote : | #270 |
*** Bug 313221 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Christoph-maxiom (christoph-maxiom) wrote : | #271 |
*** Bug 313074 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, De-meyer-maarten (de-meyer-maarten) wrote : | #272 |
*** Bug 313554 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, adaptee (adaptee) wrote : | #273 |
*** Bug 318425 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, adaptee (adaptee) wrote : | #274 |
*** Bug 330095 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, sergiomb (sergio-sergiomb) wrote : | #275 |
149 users , 9 years , 274 comments , any solution ?
In KDE Bug Tracking System #116482, sergiomb (sergio-sergiomb) wrote : | #276 |
Cleaning archive doing:
mv ./.kde/
fixed the crash
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #277 |
*** Bug 333440 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #278 |
*** Bug 331119 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #279 |
*** Bug 326343 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cgiboudeaux (cgiboudeaux) wrote : | #280 |
*** Bug 255744 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote : | #281 |
*** Bug 353607 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote : | #282 |
*** Bug 379496 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote : | #283 |
*** Bug 382936 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote : | #284 |
*** Bug 384207 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Squan (squan) wrote : | #285 |
The correct location of feeds.opml seems to be in ~/.local/
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?
In KDE Bug Tracking System #116482, Orivej Desh (orivej) wrote : | #286 |
The only backup is feeds.opml~ in the same directory.
In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote : | #287 |
*** Bug 386013 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote : | #288 |
*** Bug 398866 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote : | #289 |
*** Bug 398557 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote : | #290 |
*** Bug 398559 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Nicolás Alvarez (nicolas-alvarez) wrote : | #291 |
Why did you mark this as fixed, rubi ortiz?
In KDE Bug Tracking System #116482, KAMiKAZOW (kamikazow) wrote : | #292 |
Hardly any commits in https:/
Changed in kdepim: | |
status: | Confirmed → New |
In KDE Bug Tracking System #116482, Götz Christ (g-christ) wrote : | #293 |
*** This bug has been confirmed by popular vote. ***
Changed in kdepim: | |
status: | New → Unknown |
In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote : | #294 |
*** Bug 418507 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Cfeck (cfeck) wrote : | #295 |
*** Bug 422594 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #116482, Thanhvuy02 (thanhvuy02) wrote : | #296 |
Application: kdeconnectd (1.4.0)
Qt Version: 5.14.2
Frameworks Version: 5.70.0
Operating System: Linux 5.7.0-2parrot2-
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_
[Current thread is 1 (Thread 0x7f5748672600 (LWP 83677))]
Thread 4 (Thread 0x7f57449a4700 (LWP 83731)):
#0 0x00007f574ca11e8c in read () from /lib/x86_
#1 0x00007f574b60df4f in ?? () from /lib/x86_
#2 0x00007f574b5c633e in g_main_
#3 0x00007f574b5c6792 in ?? () from /lib/x86_
#4 0x00007f574b5c690f in g_main_
#5 0x00007f574cfab90b in QEventDispatche
#6 0x00007f574cf5389b in QEventLoop:
#7 0x00007f574cd7e8be in QThread::exec() () from /lib/x86_
#8 0x00007f574cd7f988 in ?? () from /lib/x86_
#9 0x00007f574bf6bea7 in start_thread () from /lib/x86_
#10 0x00007f574ca20daf in clone () from /lib/x86_
Thread 3 (Thread 0x7f5745c71700 (LWP 83723)):
#0 0x00007f574b6127b9 in g_mutex_lock () from /lib/x86_
#1 0x00007f574b5c5d7a in g_main_
#2 0x00007f574b5c671b in ?? () from /lib/x86_
#3 0x00007f574b5c690f in g_main_
#4 0x00007f574cfab90b in QEventDispatche
#5 0x00007f574cf5389b in QEventLoop:
#6 0x00007f574cd7e8be in QThread::exec() () from /lib/x86_
#7 0x00007f574d1fc507 in ?? () from /lib/x86_
#8 0x00007f574cd7f988 in ?? () from /lib/x86_
#9 0x00007f574bf6bea7 in start_thread () from /lib/x86_
#10 0x00007f574ca20daf in clone () from /lib/x86_
Thread 2 (Thread 0x7f5747890700 (LWP 83707)):
#0 0x00007f574ca163bf in poll () from /lib/x86_
#1 0x00007f574b299d02 in ?? () from /lib/x86_
#2 0x00007f574b29b98a in xcb_wait_for_event () from /lib/x86_
#3 0x00007f5748280dc0 in ?? () from /lib/x86_
#4 0x00007f574cd7f988 in ?? () from /lib/x86_
#5 0x00007f574bf6bea7 in start_thread () from /lib/x86_
#6 0x00007f574ca20daf in clone () from /lib/x86_
Changed in kdepim: | |
status: | Unknown → New |
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.