Bug 183183 - It just crashed and said send this report
Summary: It just crashed and said send this report
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
: 193334 198592 200480 212446 216785 220140 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-02-04 15:01 UTC by Tony Clifton
Modified: 2018-10-27 04:09 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
backtrace (3.92 KB, application/octet-stream)
2009-08-26 00:21 UTC, nogg321
Details
backtrace (1.88 KB, application/octet-stream)
2009-08-26 00:22 UTC, nogg321
Details
backtrace (1.88 KB, application/octet-stream)
2009-08-26 00:22 UTC, nogg321
Details
backtrace (1.88 KB, application/octet-stream)
2009-08-26 00:23 UTC, nogg321
Details
error message (74.53 KB, image/png)
2009-08-26 00:24 UTC, nogg321
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tony Clifton 2009-02-04 15:01:16 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Fedora RPMs

I was trying to read some RSS feeds added a URL for the feed and *BOOM* it just crashed

This is as close as I'm going to get to sending a backtrace. You seem to think that everyone will have time to install all the de-bugging tools
Amarok crashed and you said you wanted me to install about 4 such tools and I haven't got a clue what you mean, nor how to use these tools if I knew where to get them from



Application: Akregator (akregator), signal SIGSEGV
[Current thread is 1 (Thread 0xb8047770 (LWP 4397))]

Thread 2 (Thread 0xb51a0b90 (LWP 6245)):
#0  0x009ae416 in __kernel_vsyscall ()
#1  0x00bfd3d1 in select () from /lib/libc.so.6
#2  0x0211b627 in ?? () from /usr/lib/libQtCore.so.4
#3  0x0204b75e in ?? () from /usr/lib/libQtCore.so.4
#4  0x00ccf51f in start_thread () from /lib/libpthread.so.0
#5  0x00c0504e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb8047770 (LWP 4397)):
[KCrash Handler]
#6  0x0100e215 in Akregator::Article::title () from /usr/lib/kde4/akregatorpart.so
#7  0x01018636 in Akregator::ArticleModel::Private::Private () from /usr/lib/kde4/akregatorpart.so
#8  0x01018888 in Akregator::ArticleModel::ArticleModel () from /usr/lib/kde4/akregatorpart.so
#9  0x0103579e in ?? () from /usr/lib/kde4/akregatorpart.so
#10 0x010360db in ?? () from /usr/lib/kde4/akregatorpart.so
#11 0x02150df0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0x02151b72 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0x0218bc37 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#14 0x0215779e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#15 0x0214b8cf in QObject::event () from /usr/lib/libQtCore.so.4
#16 0x026bd68c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#17 0x026c54ce in QApplication::notify () from /usr/lib/libQtGui.so.4
#18 0x0304772d in KApplication::notify () from /usr/lib/libkdeui.so.5
#19 0x0213c1c1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#20 0x0216a081 in ?? () from /usr/lib/libQtCore.so.4
#21 0x021668a0 in ?? () from /usr/lib/libQtCore.so.4
#22 0x00197238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#23 0x0019a8e3 in ?? () from /lib/libglib-2.0.so.0
#24 0x0019aaa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#25 0x021667f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#26 0x02756515 in ?? () from /usr/lib/libQtGui.so.4
#27 0x0213a88a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#28 0x0213aa4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#29 0x02a969e1 in QMenu::exec () from /usr/lib/libQtGui.so.4
#30 0x0103562b in ?? () from /usr/lib/kde4/akregatorpart.so
#31 0x010360f5 in ?? () from /usr/lib/kde4/akregatorpart.so
#32 0x02150df0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#33 0x02151b72 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#34 0x02705333 in QWidget::customContextMenuRequested () from /usr/lib/libQtGui.so.4
#35 0x02715a19 in QWidget::event () from /usr/lib/libQtGui.so.4
#36 0x02a4b943 in QFrame::event () from /usr/lib/libQtGui.so.4
#37 0x02ae211f in QAbstractScrollArea::viewportEvent () from /usr/lib/libQtGui.so.4
#38 0x02b8d60f in QAbstractItemView::viewportEvent () from /usr/lib/libQtGui.so.4
#39 0x02bc52e4 in QTreeView::viewportEvent () from /usr/lib/libQtGui.so.4
#40 0x02ae46c5 in ?? () from /usr/lib/libQtGui.so.4
#41 0x0213b3aa in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib/libQtCore.so.4
#42 0x026bd66a in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#43 0x026c59f5 in QApplication::notify () from /usr/lib/libQtGui.so.4
#44 0x0304772d in KApplication::notify () from /usr/lib/libkdeui.so.5
#45 0x0213c1c1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#46 0x026c860e in QCoreApplication::sendSpontaneousEvent () from /usr/lib/libQtGui.so.4
#47 0x0272fc3f in ?? () from /usr/lib/libQtGui.so.4
#48 0x0272e7e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#49 0x02756e1a in ?? () from /usr/lib/libQtGui.so.4
#50 0x00197238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#51 0x0019a8e3 in ?? () from /lib/libglib-2.0.so.0
#52 0x0019aaa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#53 0x021667f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#54 0x02756515 in ?? () from /usr/lib/libQtGui.so.4
#55 0x0213a88a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#56 0x0213aa4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#57 0x0213d105 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#58 0x026bd507 in QApplication::exec () from /usr/lib/libQtGui.so.4
#59 0x0804e357 in _start ()
Comment 1 Dario Andres 2009-05-20 15:50:00 UTC
*** Bug 193334 has been marked as a duplicate of this bug. ***
Comment 2 Christophe Marin 2009-07-04 16:26:14 UTC
*** Bug 198592 has been marked as a duplicate of this bug. ***
Comment 3 Christophe Marin 2009-07-16 23:13:11 UTC
*** Bug 200480 has been marked as a duplicate of this bug. ***
Comment 4 nogg321 2009-08-26 00:21:01 UTC
Created attachment 36448 [details]
backtrace
Comment 5 nogg321 2009-08-26 00:22:01 UTC
Created attachment 36449 [details]
backtrace
Comment 6 nogg321 2009-08-26 00:22:44 UTC
Created attachment 36450 [details]
backtrace
Comment 7 nogg321 2009-08-26 00:23:37 UTC
Created attachment 36451 [details]
backtrace
Comment 8 nogg321 2009-08-26 00:24:56 UTC
Created attachment 36452 [details]
error message
Comment 9 nogg321 2009-08-26 00:25:57 UTC
I also get this. It happens about twice a day at different times, sometimes when I mark mail as read or anything, even all by itself!
I will try to attach some backtraces and a png of error.
It runs on Jaunty in VirtualBox, with Hardy as the host.
I  liked the version in Hardy, it never crashes, had to change some feeds to get them to work in Jaunty, I don't see any new function in the Jaunty version so why should it crash?
Comment 10 Christophe Marin 2009-10-30 23:50:55 UTC
*** Bug 212446 has been marked as a duplicate of this bug. ***
Comment 11 Christophe Marin 2009-11-30 16:10:05 UTC
*** Bug 216785 has been marked as a duplicate of this bug. ***
Comment 12 Christophe Marin 2009-12-28 13:27:59 UTC
*** Bug 220140 has been marked as a duplicate of this bug. ***
Comment 13 jamundso 2010-04-08 04:05:46 UTC
1. This might be a duplicate of bug #194591, but I'm guessing.
2. The backtrace attachments should be mimetype text/plain.
3. The bug Description is not helpful.
4. My account here cannot do anything about 1-3 above.

In summary, this bug needs love.
Comment 14 Christoph Feck 2013-09-12 21:39:45 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Comment 15 Andrew Crouthamel 2018-09-24 02:19:13 UTC
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!
Comment 16 Andrew Crouthamel 2018-10-27 04:09:48 UTC
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!