Application: akregator (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.1 Operating System: Linux 3.3.4-3.fc17.i686.PAE i686 Distribution: "Fedora release 17 (Beefy Miracle)" -- Information about the crash: - What I was doing when the application crashed: Just opened new rss tab, then opened external link, and then new external link... when switched back - crash -- Backtrace: Application: Akregator (akregator), signal: Aborted Using host libthread_db library "/lib/libthread_db.so.1". [KCrash Handler] #7 0xb7797424 in __kernel_vsyscall () #8 0x4bb9491f in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #9 0x4bb96273 in __GI_abort () at abort.c:91 #10 0x413ec7c5 in __gnu_cxx::__verbose_terminate_handler() () from /lib/libstdc++.so.6 #11 0x413ea3c4 in ?? () from /lib/libstdc++.so.6 #12 0x413ea400 in std::terminate() () from /lib/libstdc++.so.6 #13 0x413ea706 in __cxa_rethrow () from /lib/libstdc++.so.6 #14 0x4162fe07 in QEventLoop::exec (this=0xbf8ccd48, flags=...) at kernel/qeventloop.cpp:218 #15 0x41634dbb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #16 0x423b7de5 in QApplication::exec () at kernel/qapplication.cpp:3815 #17 0x0804e411 in main (argc=5, argv=0xbf8ccf14) at /usr/src/debug/kdepim-4.8.3/akregator/src/main.cpp:103 This bug may be a duplicate of or related to bug 290555. Possible duplicates by query: bug 299539, bug 299471, bug 299137, bug 298695, bug 298128. Reported using DrKonqi
Which external link ?
first - http://ozz.tv/serial/31 second - http://rutracker.org/forum/viewtopic.php?t=3998140 This all happens only in KDE workspace... i tested in GNOME with using Akregator - no problems
Sorry! I gave you wrong links... The right is that: first - http://to-artsound.ru/forum/19-486-1 second (folowing) - http://portalfilm.ifolder.ru/30359074 And in Gnome workspace Akregator crashes too... Sorry...
Unfortunately, the backtrace doesn't contain much helpful information due to uncaught exception (not your fault). If you can reproduce the crash every time, please follow the guide[1] and try to run it under gdb to get a better backtrace. [1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!