Bug 150947 - Akregator SIGSEGV on import feeds from previous version (Ubuntu Feisty Fawn)
Summary: Akregator SIGSEGV on import feeds from previous version (Ubuntu Feisty Fawn)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 158557 160742 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-10-17 18:52 UTC by Raine Hander
Modified: 2017-01-07 22:12 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Archive and data folder with feeds indexes and contents that causes crashes. Comes from previous version: Ubuntu feisty 7.04 (324.10 KB, application/octet-stream)
2007-10-17 18:56 UTC, Raine Hander
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Raine Hander 2007-10-17 18:52:41 UTC
Version:           1.2.7 (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

Upgraded to Ubuntu Gutsy Gibbon v7.10 from Ubuntu Feisty v7.04

Akregator crashes when importing my previous akregator 'Archive' and 'data' folder contents in manual (copying directly into v1.2.7 folder) or from 'Import' option on Akregator 'File' menu.

I would like to append my 'Archive' and 'data' folders in a compressed file (about 324KB).

Thanks for the attention and support!

Regards,
Raine
Comment 1 Raine Hander 2007-10-17 18:56:11 UTC
Created attachment 21844 [details]
Archive and data folder with feeds indexes and contents that causes crashes. Comes from previous version: Ubuntu feisty 7.04

Just uncompress on /home/<user>/.kde/share/apps/akregator overwriting actual
ones. Launch Akregator v1.2.7 (Ubuntu Gutsy v7.10 RC updated until this date)
Comment 2 Raine Hander 2007-10-17 18:59:56 UTC
Please rename 'attachment.cgi' to a 'attachment.tar.gz'.

Sorry ^_^'
Comment 3 Eckhart Wörner 2007-10-17 19:32:22 UTC
Backtrace:

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb5e1c6c0 (LWP 3892)]
[KCrash handler]
#6  0xb7c95513 in strlen () from /lib/i686/cmov/libc.so.6
#7  0xb57d9e48 in c4_StringRef::operator= (this=0xbf8c4a24, value_=0x0)
    at /build/buildd/kdepim-3.5.8/./akregator/src/mk4storage/metakit/src/viewx.cpp:634
#8  0xb57ba9a5 in Akregator::Backend::StorageMK4Impl::archiveFor (
    this=0x8099ca0, url=@0x8288730)
    at /build/buildd/kdepim-3.5.8/./akregator/src/mk4storage/storagemk4impl.cpp:284
#9  0xb7ec66d0 in Akregator::Feed::loadArticles (this=0x8281e18)
    at /build/buildd/kdepim-3.5.8/./akregator/src/feed.cpp:223
#10 0xb7ec743b in Akregator::Feed::fromOPML (e=@0xbf8c4be4)
    at /build/buildd/kdepim-3.5.8/./akregator/src/feed.cpp:167
#11 0xb7ed1ae5 in Akregator::FeedList::parseChildNodes (this=0x82508e8, 
    node=@0xbf8c4c54, parent=0x8263e30)
    at /build/buildd/kdepim-3.5.8/./akregator/src/feedlist.cpp:117
#12 0xb7ed1bec in Akregator::FeedList::parseChildNodes (this=0x82508e8, 
    node=@0xbf8c4d0c, parent=0x8250968)
    at /build/buildd/kdepim-3.5.8/./akregator/src/feedlist.cpp:135
#13 0xb7ed20ae in Akregator::FeedList::readFromXML (this=0x82508e8, 
    doc=@0xbf8c4e90)
    at /build/buildd/kdepim-3.5.8/./akregator/src/feedlist.cpp:175
#14 0xb596b669 in Akregator::View::loadFeeds (this=0x814bb18, 
    doc=@0xbf8c4e90, parent=0x0)
    at /build/buildd/kdepim-3.5.8/./akregator/src/akregator_view.cpp:531
#15 0xb5966c78 in Akregator::Part::openFile (this=0x813bf50)
    at /build/buildd/kdepim-3.5.8/./akregator/src/akregator_part.cpp:457
#16 0xb5964a4c in Akregator::Part::openURL (this=0x813bf50, url=@0xbf8c4f44)
    at /build/buildd/kdepim-3.5.8/./akregator/src/akregator_part.cpp:332
#17 0xb5960e34 in Akregator::Part::openStandardFeedList (this=0x813bf50)
    at /build/buildd/kdepim-3.5.8/./akregator/src/akregator_part.cpp:337
#18 0xb5976c4e in Akregator::AkregatorPartIface::process (this=0x813bffc, 
    fun=@0xbf8c5214, data=@0xbf8c528c, replyType=@0xbf8c51b4, 
    replyData=@0xbf8c51ac) at akregator_partiface_skel.cpp:39
#19 0xb7573027 in DCOPClient::receive (this=0x8062cc0, objId=@0xbf8c5258, 
    fun=@0xbf8c5214, data=@0xbf8c528c, replyType=@0xbf8c51b4, 
    replyData=@0xbf8c51ac)
    at /build/buildd/kdelibs-3.5.7.dfsg.1/./dcop/dcopclient.cpp:1640
#20 0xb75737b2 in DCOPClient::send (this=0x8062cc0, remApp=@0xbf8c5250, 
    remObjId=@0xbf8c5258, remFun=@0xbf8c5214, data=@0xbf8c528c)
    at /build/buildd/kdelibs-3.5.7.dfsg.1/./dcop/dcopclient.cpp:1060
#21 0xb7573def in DCOPRef::sendInternal (this=0xbf8c5250, fun=@0xbf8c52bc, 
    args=@0xbf8c529c, data=@0xbf8c528c)
    at /build/buildd/kdelibs-3.5.7.dfsg.1/./dcop/dcopref.cpp:102
#22 0x080510ba in Akregator::Application::newInstance (this=0xbf8c5a00)
    at /usr/include/kde/dcopref.h:1118
#23 0xb773f2df in KUniqueApplication::processDelayed (this=0xbf8c5a00)
    at /build/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kuniqueapplication.cpp:444
#24 0xb77459c8 in KUniqueApplication::qt_invoke (this=0xbf8c5a00, _id=19, 
    _o=0xbf8c5448) at ./kuniqueapplication.moc:86
#25 0xb7076b10 in QObject::activate_signal (this=0x80ec930, clist=0x80ecac0, 
    o=0xbf8c5448) at kernel/qobject.cpp:2356
#26 0xb740632e in QSignal::signal (this=0x80ec930, t0=@0x80ec958)
    at .moc/debug-shared-mt/moc_qsignal.cpp:100
#27 0xb7095cc6 in QSignal::activate (this=0x80ec930) at kernel/qsignal.cpp:212
#28 0xb709deaa in QSingleShotTimer::event (this=0x80ec908)
    at kernel/qtimer.cpp:286
#29 0xb700b36a in QApplication::internalNotify (this=0xbf8c5a00, 
    receiver=0x80ec908, e=0xbf8c5788) at kernel/qapplication.cpp:2635
#30 0xb700d193 in QApplication::notify (this=0xbf8c5a00, receiver=0x80ec908, 
    e=0xbf8c5788) at kernel/qapplication.cpp:2358
#31 0xb774dff2 in KApplication::notify (this=0xbf8c5a00, receiver=0x80ec908, 
    event=0xbf8c5788)
    at /build/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kapplication.cpp:550
#32 0xb6f9c6c9 in QApplication::sendEvent (receiver=0x80ec908, 
    event=0xbf8c5788) at ../include/qapplication.h:520
#33 0xb6ffe1b1 in QEventLoop::activateTimers (this=0x8089258)
    at kernel/qeventloop_unix.cpp:556
#34 0xb6fb119a in QEventLoop::processEvents (this=0x8089258, flags=4)
    at kernel/qeventloop_x11.cpp:389
#35 0xb70266e4 in QEventLoop::enterLoop (this=0x8089258)
    at kernel/qeventloop.cpp:198
#36 0xb70263e2 in QEventLoop::exec (this=0x8089258)
    at kernel/qeventloop.cpp:145
#37 0xb700cf13 in QApplication::exec (this=0xbf8c5a00)
    at kernel/qapplication.cpp:2758
#38 0x08050b7e in main (argc=)
    at /build/buildd/kdepim-3.5.8/./akregator/src/main.cpp:112
#39 0xb7c3b050 in __libc_start_main () from /lib/i686/cmov/libc.so.6
#40 0x08050a41 in _start ()
Comment 4 Eckhart Wörner 2007-10-17 20:10:13 UTC
Your feeds.opml contains a bad line:
   <outline htmlUrl="http://www.elotrolado.net" ... xmlUrl="" ... />
The xmlUrl parameter is the most important of all, and must never be empty. Not sure how this might have happened.
Comment 5 Raine Hander 2007-10-19 15:32:17 UTC
Oh...i've forgotten! About 2 weeks ago, whenever akregator refreshed this site, a lot of 'deleted' entries came back again. I was like akregator didn't synchronize in a good manner. Also another feed happened the same way. So i decided to disable that feed, nothing more (but not in a manual way, i mean, editing manually anything-> i just used the context menu in akregator to disable it).

Could be a bug, dunno :(

Comment 6 Christophe Marin 2008-07-24 11:59:20 UTC
*** Bug 158557 has been marked as a duplicate of this bug. ***
Comment 7 Christophe Marin 2008-07-24 11:59:36 UTC
*** Bug 160742 has been marked as a duplicate of this bug. ***
Comment 8 Denis Kurz 2016-09-24 19:42:55 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 9 Denis Kurz 2017-01-07 22:12:20 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.