Bug 179883 - plasma crashes during file operations in folder view plasmoid
Summary: plasma crashes during file operations in folder view plasmoid
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-07 06:26 UTC by Sputnik
Modified: 2009-01-07 20:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sputnik 2009-01-07 06:26:39 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

I am sorry not excactly to remember what I did. I moved  some files into a folder on the plasmoid. This had worked several times before.


Here is the report that I got:
Anwendung: Plasma-Arbeitsfläche (plasma), Signal SIGSEGV
9x (no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb55756c0 (LWP 6984)]
[New Thread 0xac492b90 (LWP 7000)]
[New Thread 0xacc93b90 (LWP 6998)]
[New Thread 0xad4beb90 (LWP 6997)]
[New Thread 0xae346b90 (LWP 6996)]
[New Thread 0xaeb47b90 (LWP 6995)]
[New Thread 0xaf515b90 (LWP 6994)]
[New Thread 0xb00ffb90 (LWP 6993)]
[New Thread 0xb14a2b90 (LWP 6992)]
[New Thread 0xb1ca3b90 (LWP 6991)]
[New Thread 0xb24a4b90 (LWP 6990)]
[New Thread 0xb2d3cb90 (LWP 6987)]
[KCrash handler]
#6  0x00000000 in ?? ()
#7  0xb7b7a5da in KAbstractWidgetJobTracker::slotStop ()
   from /usr/lib/libkdeui.so.5
#8  0xb7b7d052 in KWidgetJobTracker::Private::ProgressWidget::_k_stop ()
   from /usr/lib/libkdeui.so.5
#9  0xb7b7d0eb in KWidgetJobTracker::Private::ProgressWidget::qt_metacall ()
   from /usr/lib/libkdeui.so.5
#10 0xb76cda60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb76cde60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb722fe61 in QAbstractButton::clicked () from /usr/lib/libQtGui.so.4
#13 0xb6f83199 in ?? () from /usr/lib/libQtGui.so.4
#14 0xb6f84d94 in ?? () from /usr/lib/libQtGui.so.4
#15 0xb6f85026 in QAbstractButton::mouseReleaseEvent ()
   from /usr/lib/libQtGui.so.4
#16 0xb6c99962 in QWidget::event () from /usr/lib/libQtGui.so.4
#17 0xb6f8303e in QAbstractButton::event () from /usr/lib/libQtGui.so.4
#18 0xb7029910 in QPushButton::event () from /usr/lib/libQtGui.so.4
#19 0xb6c418ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#20 0xb6c4a0e1 in QApplication::notify () from /usr/lib/libQtGui.so.4
#21 0xb7b87b2d in KApplication::notify () from /usr/lib/libkdeui.so.5
#22 0xb76b8e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#23 0xb6c4936e in QApplicationPrivate::sendMouseEvent ()
   from /usr/lib/libQtGui.so.4
#24 0xb6cb3656 in ?? () from /usr/lib/libQtGui.so.4
#25 0xb6cb29e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#26 0xb6cdc7aa in ?? () from /usr/lib/libQtGui.so.4
#27 0xb5a066f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#28 0xb5a09da3 in ?? () from /usr/lib/libglib-2.0.so.0
#29 0xb5a09f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#30 0xb76e3478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#31 0xb6cdbea5 in ?? () from /usr/lib/libQtGui.so.4
#32 0xb76b752a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#33 0xb76b76ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#34 0xb76b9da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#35 0xb6c41767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#36 0xb8033491 in kdemain () from /usr/lib/libkdeinit4_plasma.so
#37 0x080485b2 in _start ()
#0  0xb807f430 in __kernel_vsyscall ()
Comment 1 Dario Andres 2009-01-07 15:08:50 UTC
I have experienced similar bugs, you probably started a non-valid file operation, and when you tried to stop it (as it was a non-sense operation (another bug)), plasma crashed.
May be related to bug 168276, bug 171415, or even to my report bug 168427
Comment 2 Sputnik 2009-01-07 20:44:28 UTC
Darío, thanks for your attention! - There may have been some broken packages as well ... I will close this bug now as I could fix the trouble with the packages. - Please feel free to reopen this bug if you think this might be the best! - I would prefer to open a new bug if similar things will happen again because I will now be able to get better bug reports (due to resolved packages problems I was now able to install more dbg-packages)...