Bug 248753 - KUIserver crashed opening a .torrent file directly from Konqueror
Summary: KUIserver crashed opening a .torrent file directly from Konqueror
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 0.8
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-08-23 06:00 UTC by Javier Martínez Ortiz
Modified: 2018-10-27 02:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Javier Martínez Ortiz 2010-08-23 06:00:01 UTC
Application: kuiserver (0.8)
KDE Platform Version: 4.5.00 (KDE 4.5.0)
Qt Version: 4.6.3
Operating System: Linux 2.6.34-12-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I'd open a .torrent file from the web, using Konqueror. When Konqueror asked for "Save" or "Open with KTorrent" and I choose "Open with KTorrent", the KUIserver crashed. Although that, the process to KTorrent still worked.

-- Backtrace:
Application: Job Manager (kuiserver), signal: Illegal instruction
[KCrash Handler]
#6  0x00007ff43d79ba88 in JobView::setProcessedAmount (this=0x6272f0, amount=10721, unit=...) at /usr/src/debug/kdebase-runtime-4.5.0/kuiserver/jobview.cpp:128
#7  0x00007ff43d7a1e65 in JobViewV2Adaptor::qt_metacall (this=0x717d20, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fff973a6610)
    at /usr/src/debug/kdebase-runtime-4.5.0/build/kuiserver/jobviewadaptor.moc:147
#8  0x00007ff43c732188 in QDBusConnectionPrivate::deliverCall (this=0x61f0c0, object=0x717d20, msg=..., metaTypes=..., slotIdx=12) at qdbusintegrator.cpp:904
#9  0x00007ff43c734245 in QDBusConnectionPrivate::activateCall (this=0x61f0c0, object=0x717d20, flags=273, msg=...) at qdbusintegrator.cpp:816
#10 0x00007ff43c734aae in QDBusConnectionPrivate::activateObject (this=0x61f0c0, node=..., msg=..., pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1364
#11 0x00007ff43c734cf8 in QDBusActivateObjectEvent::placeMetaCall (this=0x73a4c0) at qdbusintegrator.cpp:1477
#12 0x00007ff43c40c509 in QObject::event (this=0x6272f0, e=0x73a4c0) at kernel/qobject.cpp:1248
#13 0x00007ff43b7ec4d4 in QApplicationPrivate::notify_helper (this=0x62eb80, receiver=0x6272f0, e=0x73a4c0) at kernel/qapplication.cpp:4302
#14 0x00007ff43b7f4aca in QApplication::notify (this=<value optimized out>, receiver=0x6272f0, e=0x73a4c0) at kernel/qapplication.cpp:4185
#15 0x00007ff43cf960b6 in KApplication::notify (this=0x7fff973a73a0, receiver=0x6272f0, event=0x73a4c0) at /usr/src/debug/kdelibs-4.5.0/kdeui/kernel/kapplication.cpp:310
#16 0x00007ff43c3fae4c in QCoreApplication::notifyInternal (this=0x7fff973a73a0, receiver=0x6272f0, event=0x73a4c0) at kernel/qcoreapplication.cpp:726
#17 0x00007ff43c3fe5ba in sendEvent (receiver=0x0, event_type=0, data=0x603530) at kernel/qcoreapplication.h:215
#18 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x603530) at kernel/qcoreapplication.cpp:1367
#19 0x00007ff43c423173 in sendPostedEvents (s=<value optimized out>) at kernel/qcoreapplication.h:220
#20 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#21 0x00007ff437fd8a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007ff437fd9270 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007ff437fd9510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007ff43c42367f in QEventDispatcherGlib::processEvents (this=0x608fe0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00007ff43b88d14e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007ff43c3fa292 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#27 0x00007ff43c3fa495 in QEventLoop::exec (this=0x7fff973a72b0, flags=...) at kernel/qeventloop.cpp:201
#28 0x00007ff43c3fe88b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#29 0x00007ff43d795fd2 in kdemain (argc=1, argv=0x7fff973a76b8) at /usr/src/debug/kdebase-runtime-4.5.0/kuiserver/main.cpp:65
#30 0x00007ff43d447b7d in __libc_start_main () from /lib64/libc.so.6
#31 0x0000000000400699 in _start () at ../sysdeps/x86_64/elf/start.S:113

Reported using DrKonqi
Comment 1 Christoph Feck 2013-09-12 21:46:58 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 2 Andrew Crouthamel 2018-09-25 03:40:26 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 3 Andrew Crouthamel 2018-10-27 02:06:47 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!