Bug 218466 - Kget widget crashes making it unusable
Summary: Kget widget crashes making it unusable
Status: RESOLVED WORKSFORME
Alias: None
Product: kget
Classification: Applications
Component: plasma widget (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-12-13 07:30 UTC by DEEPAK
Modified: 2018-10-21 05:10 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 DEEPAK 2009-12-13 07:30:15 UTC
Version:           4.3.80 (using Devel)
OS:                Linux
Installed from:    Compiled sources

Kget widget on desktop crashes when trying to add files (by dropping or clicking) to download.

The crash also triggers plasma-workspace to crash immediately. 

Again plasma-desktop crashes when drop target is used from konqueror for downloading files (when trying to drop files). But this happens only when there are kget widget on desktop. Otherwise kget works normaly from konqueror.

backtrace:

Application: Plasma Workspace (kdeinit4), signal: Floating point exception
[KCrash Handler]
#6  0x03448e9d in ?? () from /usr/lib/kde4/plasma_kget_barapplet.so
#7  0x03449786 in ?? () from /usr/lib/kde4/plasma_kget_barapplet.so
#8  0x034424c2 in ?? () from /usr/lib/kde4/plasma_kget_barapplet.so
#9  0x0027c95a in QMetaObject::metacall (object=0x9ab2d80, cl=QMetaObject::ReadProperty, idx=0, argv=0x9ac9b68) at kernel/qmetaobject.cpp:237
#10 0x0028b0db in QMetaObject::activate (sender=0x9ae2538, m=0x60e4d44, local_signal_index=0, argv=0xbfd39764) at kernel/qobject.cpp:3294
#11 0x05f829e9 in Plasma::SignalRelay::dataUpdated (this=0x9ae2538, _t1=..., _t2=...) at ./datacontainer_p.moc:85
#12 0x05f82d51 in Plasma::SignalRelay::timerEvent (this=0x9ae2538, event=0xbfd39c30) at ../../plasma/private/datacontainer_p.cpp:158
#13 0x00287f44 in QObject::event (this=0x9ae2538, e=0x0) at kernel/qobject.cpp:1224
#14 0x04f391dc in QApplicationPrivate::notify_helper (this=0x8f23fc8, receiver=0x9ae2538, e=0xbfd39c30) at kernel/qapplication.cpp:4242
#15 0x04f3fe37 in QApplication::notify (this=0x8f1dbc8, receiver=0x9ae2538, e=0xbfd39c30) at kernel/qapplication.cpp:3661
#16 0x00ea518a in KApplication::notify (this=0x8f1dbc8, receiver=0x9ae2538, event=0xbfd39c30) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x002776fb in QCoreApplication::notifyInternal (this=0x8f1dbc8, receiver=0x9ae2538, event=0xbfd39c30) at kernel/qcoreapplication.cpp:704
#18 0x002a6aa6 in QCoreApplication::sendEvent (this=0x8f26694) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x8f26694) at kernel/qeventdispatcher_unix.cpp:603
#20 0x002a3737 in timerSourceDispatch (source=0x8f26b00) at kernel/qeventdispatcher_glib.cpp:184
#21 idleTimerSourceDispatch (source=0x8f26b00) at kernel/qeventdispatcher_glib.cpp:231
#22 0x00ba4fd8 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#23 0x00ba8880 in ?? () from /lib/libglib-2.0.so.0
#24 0x00ba89b3 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#25 0x002a33f5 in QEventDispatcherGlib::processEvents (this=0x8edc898, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#26 0x04ff6ba5 in QGuiEventDispatcherGlib::processEvents (this=0x8edc898, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#27 0x00275d19 in QEventLoop::processEvents (this=0xbfd39ef4, flags=) at kernel/qeventloop.cpp:149
#28 0x0027616a in QEventLoop::exec (this=0xbfd39ef4, flags=...) at kernel/qeventloop.cpp:201
#29 0x0027a35f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#30 0x04f39277 in QApplication::exec () at kernel/qapplication.cpp:3570
#31 0x0852f05e in kdemain (argc=1, argv=0x8f11e90) at ../../../../plasma/desktop/shell/main.cpp:112
#32 0x0804dfc1 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x8edc990 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x8051429 "0") at ../../kinit/kinit.cpp:705
#33 0x0804ec15 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at ../../kinit/kinit.cpp:1197
#34 0x0804f08c in handle_requests (waitForPid=<value optimized out>) at ../../kinit/kinit.cpp:1390
#35 0x0804fe27 in main (argc=4, argv=0xbfd3a9a4, envp=0xbfd3a9b8) at ../../kinit/kinit.cpp:1825


Executable: kdeinit4 PID: 1865 Signal: 8 (Floating point exception)
Comment 1 Lukas Appelhans 2009-12-20 17:24:26 UTC
We need a better backtrace for this. Please install debug-symbols for KGet...

Lukas
Comment 2 DEEPAK 2009-12-24 04:03:41 UTC
________________________________
From: Lukas Appelhans <l.appelhans@gmx.de>
To: deepakk79@yahoo.com
Sent: Sun, December 20, 2009 9:54:27 PM
Subject: [Bug 218466] Kget widget crashes making it unusable

https://bugs.kde.org/show_bug.cgi?id=218466


--- Comment #1 from Lukas Appelhans <l appelhans gmx de>  2009-12-20 17:24:26 ---
We need a better backtrace for this. Please install debug-symbols for KGet...

Lukas

========================================

Lukas I beleive I had already installed debugging  symbols for kde, But I am unable to reproduce the bug now as the plasma itself crashes completely on startup .(this bug has already been filed  by others). Now plasma also crashes on fresh install also. I tried to upgrade and also downgrade. but no diff. I hav no solution  i dont  understand  y its happeing now out of blue. I am really sorry I am unable to help u.

Deepak
Comment 3 Lukas Appelhans 2009-12-24 13:37:55 UTC
Hey!

No problem, I hope you get your problems sorted out soon :) This could as well be a duplicate of 219702... so well, just test in a further version and check whether you have problems... :)

Lukas
Comment 4 Andrew Crouthamel 2018-09-20 03:17:01 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 5 Andrew Crouthamel 2018-10-21 05:10:15 UTC
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!