Version: (using Devel) Installed from: Compiled sources How to reproduce the crash: 1. Start a download with Kget (Download should be large enough, so that the download is not finished when doing step 2) 2. Put the Kde-Widget onto the desktop.
a) wrong component, it's kget b) backtrace?
Can't reproduce in current SVN. On which revision are you? Lukas
I am using KDE 4.0.1 release "12.6" Kget:2.0.1 Both from http://download.opensuse.org/repositories/KDE:/KDE4:/STABLE:/Desktop/openSUSE_10.3/ I am using the i586 branch.
Created attachment 23669 [details] The backtrace Here is a backtrace
Mmh do you have the *-dbg-packages for kdelibs, kdebase and kdenetwork installed? Lukas PS: From this small bt, it seems like it's Plasma's fault :/
Created attachment 23670 [details] A new backtrace Here is a new backtrace created with installed debug-packages
Hey, that looks better. :) Thx Lukas
Still crash with release "14.3".
An ther way to crash plasma with Kget-Widget: 1. Place the KGet-Widget onto the Desktop. 2. Start a download with Kget.
Created attachment 23845 [details] Bractrace with KDE/Kget 4.0.2 release "8.1" Here is a backtrace of the crash with KDe/Kget 4.0.2 release "8.1" How to reproduce: 1. Put the Kget Plasmoid onto the desktop 2. Start a downlaod with Kget
Created attachment 23902 [details] Backtrace kget/plasma crash
on comment #11 using fedora 9 rawhide, kde version 4.0.2
Can you install the debug-packages for this? Lukas
Created attachment 23904 [details] backtrace kget/plasma crash, with debug packages, (x86 architecture)
MMh not so useful, are you sure that you've also installed the kdenetwork debug packages and restarted plasma? Lukas
Created attachment 23905 [details] plasma started in konsole, kget messages These are the messages that plasma generated in konsole when i started plasma from the command line
Created attachment 23906 [details] backtrace plasma/kget this happened in the console when i added the kget applet: NOTE: kget still running after plasma crash plasma(3925) Plasma::AppletBrowserWidget::addApplet: Button ADD clicked plasma(3925) Plasma::AppletBrowserWidget::addApplet: Adding applet "KGet" to containment plasma(3925) Plasma::AppletBrowserWidget::appletAdded: "KGet" Plasma crashed, attempting to automatically recover KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma path = <unknown> pid = 3925
Comment on attachment 23904 [details] backtrace kget/plasma crash, with debug packages, (x86 architecture) no kdenetwork-debug package installed at the time of the crash
Hey thanks for this backtrace, that should be useful, I will look for the bug later in the evening =) Lukas
Created attachment 23908 [details] plasma crash on closing kget plasmoid I was trying to reproduce the kget applet making plasma crash. However, this time plasma did´t crash when adding the applet, it crashed when i manually closed the kget plasmoid by clicking the red X on the plasmoid transparent edge. Backtrace attatched I tried closing other few widgets, clicking their red X doesn´t crash plasma. steps to reproduce: 0. have widgets un-locked 1. close any kget instances that are running 2. add kget plasmoid 3. if plasmoid doesn´t crash, click ¨start Kget¨button 4. close main kget window that appears 5. clik on the red X button on the kget plasmoid
Ok the reason of this bug was already removed in 4.1-trunk... Anyway, Javier, can you look for this bug? Lukas
Yes its fixed in 4.1 devel
Is this bug (realy) resolved or is this something new ? I installed SuSE 11.0 today (june 20, 2008) on a VM-WARE virtual machine (1 cpu, 256 Mb, 8 GB disk (4x2GB), ethernet, iso-image as DVD drive) I added to the desktop the KGet widget and got some error message about plasma. However, the KGet widget is added and operates (as used so far). STACKTRACE ========== (no debugging symbols found) ................. ................. (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb63926d0 (LWP 31891)] [New Thread 0xb2954b90 (LWP 32207)] [New Thread 0xb4b13b90 (LWP 31892)] (no debugging symbols found) (no debugging symbols found) ........................... ............................ (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0x00000019 in ?? () #7 0xb408bf3e in ?? () from /usr/lib/kde4/plasma_applet_kget.so #8 0xb77f952c in qDeleteInEventHandler () from /usr/lib/libQtCore.so.4 #9 0xb77faf03 in QObject::event () from /usr/lib/libQtCore.so.4 #10 0xb6a63ecc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #11 0xb6a6a31e in QApplication::notify () from /usr/lib/libQtGui.so.4 #12 0xb7d6636d in KApplication::notify () from /usr/lib/libkdeui.so.5 #13 0xb77ecb51 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #14 0xb77ed411 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #15 0xb77ed5ad in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #16 0xb6aee00f in ?? () from /usr/lib/libQtGui.so.4 #17 0xb77eb2ca in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #18 0xb77eb48a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #19 0xb77ed66d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #20 0xb6a63d47 in QApplication::exec () from /usr/lib/libQtGui.so.4 #21 0xb8033671 in kdemain () from /usr/lib/libkdeinit4_plasma.so #22 0x080487c2 in _start () #0 0xffffe430 in __kernel_vsyscall ()
OpenSuSE 11 uses KDE 4.0 afaik, so the bug still exists in it... Lukas