Version: (using KDE 4.1.3) OS: Linux Installed from: Ubuntu Packages I am trying to delete several files from the trash, and each time I try, I receive the message "The process for the trash protocol died unexpectedly", and the files are not deleted. I'm not sure what other information I can give you; please let me know what else would be useful. Right now, this is completely reproducible on my system, which is an up-to-date 64-bit Kubuntu machine.
Debug output from ~/.xsession-errors would be useful. Even better would be to install debug packages, then do cd export KDE_DEBUG=1 ulimit -c unlimited kdeinit4 then try again and look for a "core" file in your Home. If there's one, gdb kdeinit4 core bt
I have the same issue after upgrading KDE 4.1.4 to KDE 4.2.00. I'm running Kubuntu 8.10 on an i386 platform (Toshiba Satellite P105-S6147). After logging in via KDM, and as the desktop is loading, I get a pop notification: Error - Plasma Workspace The process for the trash protocol died unexpectedly. There is only an acknowledgment (OK) and when pressed, the notification goes away. I can send items to the trash. I can open the trash with a left-click (Dolphin). I can delete the items in the trash (right-click). So, the trash is working correctly. cat .xsession-errors | grep trash plasma(6380) KServiceFactory::findServiceByDesktopPath: "findServiceByDesktopPath: kcmtrash not found" sudo find /* -mount -name kcmtrash doesn't locate kcmtrash.
Paul: the file is called kcmtrash.desktop
(In reply to comment #3) > Paul: the file is called kcmtrash.desktop > Okay. So is this fixable by the user? What file/process is incorrectly referring to kcmtrash instead of kcmtrash.desktop, i.e., what process is resulting in: plasma(6380) KServiceFactory::findServiceByDesktopPath: "findServiceByDesktopPath: kcmtrash not found" that appears in .xsession-errors? Or is this a true bug that needs a patch/fix developed and released?
This just started happening again. KDE 4.1.4. 64-bit. (In reply to comment #1) > Even better would be to install debug packages, then do > > cd > export KDE_DEBUG=1 > ulimit -c unlimited > kdeinit4 > > > then try again and look for a "core" file in your Home. If there's one, > > gdb kdeinit4 core > bt > (gdb) bt #0 0x00007f986baad015 in raise () from /lib/libc.so.6 #1 0x00007f986baaeb83 in abort () from /lib/libc.so.6 #2 0x00007f986cfb96b5 in qt_message_output () from /usr/lib/libQtCore.so.4 #3 0x00007f986cfb97fd in qFatal () from /usr/lib/libQtCore.so.4 #4 0x00007f9865d3c4ae in TrashImpl::trashDirectoryPath (this=0x7fff7670b4d8, trashId=0) at /build/buildd/kdebase-runtime-4.1.4/kioslave/trash/trashimpl.cpp:933 #5 0x00007f9865d3cba3 in TrashImpl::infoPath (this=0x4b11, trashId=6, fileId=@0xffffffffffffffff) at /build/buildd/kdebase-runtime-4.1.4/kioslave/trash/trashimpl.cpp:325 #6 0x00007f9865d3d589 in TrashImpl::del (this=0x7fff7670b4d8, trashId=0, fileId=@0x7fff7670b1f0) at /build/buildd/kdebase-runtime-4.1.4/kioslave/trash/trashimpl.cpp:491 #7 0x00007f9865d33bd8 in TrashProtocol::del (this=0x7fff7670b4a0, url=@0x7fff7670b2e0) at /build/buildd/kdebase-runtime-4.1.4/kioslave/trash/kio_trash.cpp:323 #8 0x00007f986df8020d in KIO::SlaveBase::dispatch (this=0x7fff7670b4b0, command=75, data=@0x7fff7670b420) at /build/buildd/kde4libs-4.1.4/kio/kio/slavebase.cpp:1130 #9 0x00007f986df854ec in KIO::SlaveBase::dispatchLoop (this=0x7fff7670b4b0) at /build/buildd/kde4libs-4.1.4/kio/kio/slavebase.cpp:282 #10 0x00007f9865d33906 in kdemain (argc=4, argv=<value optimized out>) at /build/buildd/kdebase-runtime-4.1.4/kioslave/trash/kio_trash.cpp:62 #11 0x0000000000407015 in launch (argc=4, _name=0x1445fd8 "kio_trash", args=0x1446051 "", cwd=0x0, envc=0, envs=<value optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40a1df "0") at /build/buildd/kde4libs-4.1.4/kinit/kinit.cpp:702 #12 0x00000000004078c2 in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.1.4/kinit/kinit.cpp:1282 #13 0x0000000000407e1a in handle_requests (waitForPid=0) ---Type <return> to continue, or q <return> to quit--- at /build/buildd/kde4libs-4.1.4/kinit/kinit.cpp:1474 #14 0x00000000004089a8 in main (argc=1, argv=0x7fff7670c338, envp=0x7fff7670c348) at /build/buildd/kde4libs-4.1.4/kinit/kinit.cpp:1943 (gdb) The process for the trash protocol died unexpectedly.
Thanks! I see where the bug is now.
SVN commit 924868 by dfaure: Initialize trashimpl so that kio_trash doesn't crash when the first operation that is done in a new kio_trash process is deleting a file. Fix will be in 4.2.1 BUG: 177866 M +1 -0 kio_trash.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=924868
It's so cool when the bug-reporting/fixing system works :-) Thanks muchly.
" ------- Comment #7 From David Faure 2009-02-11 21:50:20 (-) [reply] ------- SVN commit 924868 by dfaure: Initialize trashimpl so that kio_trash doesn't crash when the first operation that is done in a new kio_trash process is deleting a file. Fix will be in 4.2.1 BUG: 177866 M +1 -0 kio_trash.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=924868" Today, October 13, 2009, I upgraded 32-bit Intrepid Ibex KDE 4.2.x to 32-bit Jaunty Jackalope KDE 4.2.2. Upgrade was via Internet and it went flawlessly. Everything that was working in Intrepid was working in Jaunty when I rebooted. But, this 'bug' appeared again. So, was it actually fixed after all?
Paul: a program can crash for many reasons. So unless you got the same backtrace, it's very unlikely that you're hitting the same bug. Please try to get a backtrace (you might have to install debug packages for that, like "kdelibs-dbg") and open a new bug. Also, 4.2.2 is a bit old already; we released 4.3, 4.3.1, 4.3.2 already.