Registered Member
|
opensuse 11.0 x86
Qt: 4.4.3 KDE: 4.1.71 (KDE 4.1.71 (KDE 4.2 >= 20081023)) "release 5.1" Akregator: 1.3.50 i recently upgraded kde from 4.1.70 to 4.1.71 and now akregator crashes as soon as it's window tries to open. here is the output: Object::connect: No such signal Akregator::SubscriptionListView::signalContextMenu(K3ListView*,Akregator::TreeNode*,QPoint) Object::connect: (sender name: 'feedtree') Object::connect: (receiver name: 'akregator_view') Object::connect: No such signal Akregator::SubscriptionListView::signalDropped(KUrl::List&,Akregator::TreeNode*,Akregator::Folder*) Object::connect: (sender name: 'feedtree') Object::connect: (receiver name: 'akregator_view') echoes@echoes:~> KCrash: Application 'akregator' crashing... sock_file=/home/echoes/.kde4/socket-echoes/kdeinit4__0 is anyone else experiencing this and does anyone know a possible solution?
Last edited by echoes on Thu Nov 06, 2008 6:18 pm, edited 1 time in total.
|
Administrator
|
When you upgraded KDE to 4.1.71 did you update akregator at the same time?
If you didn't well then there is your cause. Alternatively you could try removing / moving the config file ( akregatorrc in ~/.kde4/share/config ) and trying again.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
yes i did upgrade akregator along with the upgrade to 4.1.71.
removing the config file totally slipped my mind. i tried it, but unfortunately it didn't make a difference. i also tried reinstalling akregator but that didn't work either.[hr] is it possible to run akregator from command line? what i mean is, does akregator have a command line client/interface?
Last edited by echoes on Mon Oct 27, 2008 5:19 pm, edited 1 time in total.
|
Administrator
|
I just checked my akregator. It appears that the "Object::" things also affect me, although my akregator does load. Comparing them however i have two more than you.
You may want to ( assuming you are using build service packages ) update the akregator package again, because it may have already been fixed, and if that fails contact it's developers.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
good to know it isn't just me. (as weird as that may sound).
i am not using build service packages. i assume from what you said that you are using opensuse too?
Last edited by echoes on Tue Oct 28, 2008 5:03 pm, edited 1 time in total.
|
Administrator
|
I use build service packages for everything i can. Yes, I also run openSuSE but I use KDE 4.1.2, if you just want to follow the progress of trunk then you should use the KDE:KDE4:UNSTABLE repository. You could also try removing the ~/.kde4/share/apps/akregator folder ( which is a cache of all posts it has downloaded, the format may have changed / your cache may be corrupt )
Last edited by bcooksley on Wed Oct 29, 2008 2:56 am, edited 1 time in total.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
no such luck. renamed the folder & launched akregator again but the same problem. :'( |
Administrator
|
Failing everything, you could svn up just akregator and recompile it. it sounds like you just hit a time where the developers were in the middle of making changes ( grasping straws here.. ).
Also check to make sure you are using the right versions of the libraries the akregator needs.(They may be close enough to compile, but too far apart to work)
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Today I recompiled my svn KDE with kdesvn-build and Akregator came back to rock!
In the times it didn't worked, I used it by launching Kontact and using its Feeds tab, which loaded the KPart of Akregator. |
Registered Member
|
not that i can't compile anything, but i think i'll wait till kde 4.1.71+ hits opensuse. here is what happened when i tried a backtrace, but it didn't produce anything of worth afaik: This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. [?1034h(no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb4b656d0 (LWP 1526)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe430 in __kernel_vsyscall () [Current thread is 0 (process 1526)] Thread 1 (Thread 0xb4b656d0 (LWP 1526)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb520c0c0 in nanosleep () from /lib/libc.so.6 #2 0xb520bece in sleep () from /lib/libc.so.6 #3 0xb7a22e90 in ?? () from /usr/lib/libkdeui.so.5 #4 0xb7a23854 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5 #5 #6 0xb3463622 in Akregator::FeedList::findByID () from /usr/lib/kde4/akregatorpart.so #7 0xb3484d99 in ?? () from /usr/lib/kde4/akregatorpart.so #8 0xb34850ee in ?? () from /usr/lib/kde4/akregatorpart.so #9 0xb7edc730 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #10 0xb7edd4b2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb7ee2b77 in ?? () from /usr/lib/libQtCore.so.4 #12 0xb7ee2c9c in ?? () from /usr/lib/libQtCore.so.4 #13 0xb7ed71ef in QObject::event () from /usr/lib/libQtCore.so.4 #14 0xb55b682c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #15 0xb55be6ce in QApplication::notify () from /usr/lib/libQtGui.so.4 #16 0xb79b7e8d in KApplication::notify () from /usr/lib/libkdeui.so.5 #17 0xb7ec7a61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #18 0xb7ef5dd6 in ?? () from /usr/lib/libQtCore.so.4 #19 0xb7ef22a0 in ?? () from /usr/lib/libQtCore.so.4 #20 0xb50e92d9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #21 0xb50ec85b in ?? () from /usr/lib/libglib-2.0.so.0 #22 0xb50ec9d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #23 0xb7ef21f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #24 0xb564f885 in ?? () from /usr/lib/libQtGui.so.4 #25 0xb7ec613a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #26 0xb7ec62fa in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #27 0xb7ec8995 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #28 0xb55b66a7 in QApplication::exec () from /usr/lib/libQtGui.so.4 #29 0x0804ef51 in _start () #0 0xffffe430 in __kernel_vsyscall ()
Last edited by echoes on Wed Oct 29, 2008 6:42 pm, edited 1 time in total.
|
Registered Member
|
UPDATE:
FYI, kde 4.1.72 does indeed fix this problem. |
Administrator
|
Good to hear you managed to resolve your problem. Please mark the thread as solved ( edit the subject to include [SOLVED] at the start )
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Global Moderator
|
Argh, this has hit me now! Started after a system breakdown (my RAM is dodgy, ran memtest overnight and got 12 errors )
I've tried reinstalling akregator and kontact but no joy as yet. All the other kontact modules work okay.
Debian testing
|
Administrator
|
Toad: try removing $(kde4-config --localprefix)/share/apps/akregator
Note that this will likely erase your feed configuration.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Global Moderator
|
Cheers for the feedback - for some reason I didn't get notified, so that is why a) I didn't follow your advice and b) I am answering late
I managed to get it sorted by removing the akregator directory from ~/.kde4/share/apps and it worked again, ergo: some data was corrupted. Turned out it was the BBC news that got corrupted and threw akregator. Took some investigation and I lost all 7000 news entries, but they are amassing again nicely Once again, thanks for replying.
Debian testing
|
Registered users: Bing [Bot], daret, Google [Bot], sandyvee, Sogou [Bot]