Bug 186068 - Plasma crash - change file name + copy using mouse
Summary: Plasma crash - change file name + copy using mouse
Status: RESOLVED DUPLICATE of bug 188807
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-03-03 20:40 UTC by Milosz Graj
Modified: 2009-05-26 09:10 UTC (History)
4 users (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 Milosz Graj 2009-03-03 20:40:10 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

Plasma crashes when trying to copy a file name:

Desktop(Plasma Workspace) -> Right click on a file -> 'Change file name' or F2 -> right click on the file name -> Copy.

And that is the moment when everything goes black. 
When I turn on the Desktops Cube there are no Desktops visible.
Comment 1 Aaron J. Seigo 2009-03-04 03:38:03 UTC
please read this page:

http://techbase.kde.org/Development/Tutorials/Debugging
/How_to_create_useful_crash_reports

for how to generate a useful backtrace, and then include it here.thanks :)
Comment 2 Marek 2009-04-21 21:17:36 UTC
Plasma Workspace crashed when using Dolphin to rename a directory. System is Kubuntu 9.04 RC, KDE 4.2.2, and compositing is enabled if that makes a difference.

A window with the following message pops-up:

"""
A Fatal Error Occurred
The application Plasma Workspace (plasma) crashed and caused the signal 11 (SIGSEGV).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc.
"""

The "Show details" checkbox has the following:

"""
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
...
...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb3c39730 (LWP 3727)]
[New Thread 0xa7c6db90 (LWP 3732)]
[New Thread 0xa84fab90 (LWP 3731)]
(no debugging symbols found)
...
...
(no debugging symbols found)
0xb7f0f430 in __kernel_vsyscall ()
[Current thread is 0 (LWP 3727)]

Thread 3 (Thread 0xa84fab90 (LWP 3731)):
#0  0xb7f0f430 in __kernel_vsyscall ()
#1  0xb50530e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb62622ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb644e9b2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb78d0152 in ?? () from /usr/lib/libQtNetwork.so.4
#5  0xb644d96e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb504f4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb625349e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xa7c6db90 (LWP 3732)):
#0  0xb7f0f430 in __kernel_vsyscall ()
#1  0xb50530e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb62622ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb644e9b2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xa868ab9a in ?? () from /usr/lib/kde4/plasma_wallpaper_image.so
#5  0xb644d96e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb504f4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb625349e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb3c39730 (LWP 3727)):
#0  0xb7f0f430 in __kernel_vsyscall ()
#1  0xb620e7a6 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb620e5be in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb76b78b2 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb76b8274 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb7a73527 in KFileItem::isLocalFile () from /usr/lib/libkio.so.5
#7  0xb7a59ca9 in ?? () from /usr/lib/libkio.so.5
#8  0xb6557ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#9  0xb6558932 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb7a66169 in OrgKdeKDirNotifyInterface::FileRenamed () from /usr/lib/libkio.so.5
#11 0xb7a66291 in OrgKdeKDirNotifyInterface::qt_metacall () from /usr/lib/libkio.so.5
#12 0xb665ad7a in ?? () from /usr/lib/libQtDBus.so.4
#13 0xb6663187 in ?? () from /usr/lib/libQtDBus.so.4
#14 0xb65523a0 in QObject::event () from /usr/lib/libQtCore.so.4
#15 0xb67eef2c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#16 0xb67f722e in QApplication::notify () from /usr/lib/libQtGui.so.4
#17 0xb764794d in KApplication::notify () from /usr/lib/libkdeui.so.5
#18 0xb6541a3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#19 0xb6542695 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#20 0xb654288d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#21 0xb656d7ef in ?? () from /usr/lib/libQtCore.so.4
#22 0xb4e4db88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb4e510eb in ?? () from /usr/lib/libglib-2.0.so.0
#24 0xb4e51268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0xb656d438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#26 0xb68903f5 in ?? () from /usr/lib/libQtGui.so.4
#27 0xb654006a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#28 0xb65404aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#29 0xb6542959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#30 0xb67eeda7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#31 0xb7ebdb56 in kdemain () from /usr/lib/libkdeinit4_plasma.so
#32 0x08048712 in _start ()
#0  0xb7f0f430 in __kernel_vsyscall ()
"""
Comment 3 A. Spehr 2009-05-26 09:10:34 UTC
Thanks!

*** This bug has been marked as a duplicate of bug 188807 ***