Version: 1.6.3 (using KDE KDE 3.2.2) Installed from: Gentoo Packages Compiler: gcc 3.3.3 OS: Linux I'm using Kile 1.6.3 with a current Gentoo Linux on kernel 2.6. Since some time Kile is quite regularly popping up error messages saying "The process for the file protocol died unexpectedly." ("Der Prozess für das Protokoll file wurde unerwartet beendet" in the German translation.) Apparently this does happen while autosaving and only under high system load. These windows are modal. They are useless. And I get about one for each open file. (Any of these points is bad.) Reproducible: Always Steps to Reproduce: 1. Start kile 2. Set the autosave interval to something low (e.g. 1 Minute) 3. Open some files. (In my experience it doesn't matter whether they are modified) 4. Create some sytem activity, e.g. run updatedb or compile OpenOffice or something similar Actual Results: Displays annoying, meaningless error messages Expected Results: Either no error condition should happen at all (as far as I can see nothing really went wrong) or it should be displayed in a less intrusive way.
These messages are not shown by Kile, but by the underlying KDE libraries. The fact that it happens points to a bug in those libraries, or a disfunctional KDE installation on your system. Whichever is the case, I will reassign this bug to the KDE libraries. Thanks for the bug report! best, Jeroen
Well, if the problem is with "file" then the bug should be moved to the right component. Have a nice day!
If kio_file dies, and if that's related to high system load, it basically means the kernel killed it? In case there's no bug here, only expected behavior. Your system isn't supposed to get to that state. But any process can be killed, I don't see why it should be kio_file everytime. Please provide output from ~/.xsession-errors and /var/log/messages so that we can see what's happening, it's hard to guess otherwise.
There is nothing in /var/log/messages about that. The kernel did not kill anything (that would be easy to spot). But you're right, there was something in the .xsession-errors: kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) (resulting in 4 error popups)
*** Bug 132587 has been marked as a duplicate of this bug. ***
David: I think it's more like that there is somewhere a timeout in KIO that kills ioslaves after "idle" timeout (https://bugzilla.novell.com/show_bug.cgi?id=233602).
Along the lines of <http://bugs.kde.org/show_bug.cgi?id=132587>, on a user's normally crowded desktop I see the infamous alert declaring "The process for the file protocol died unexpectedly.", and no icons. The user's ~/.xsession-errors has kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KLauncher): ERROR: SlavePool: No communication with slave. The machine is an AND64 dual core, so by no means slow, but the user's home is on NFS. Moving to K Menu::Settings::Desktop::Behavior, then ticking off "Show icons on desktop", hitting Apply, then ticking it on again brings back the icons. Switching off the desktop image used to help, but does not any more.
Is this still an issue in KDE 4 ?
(In reply to comment #8) > Is this still an issue in KDE 4 ? Hi Dawit, I'm using kde 4.8 and I sometimes come across those error popups during session restoration, which is accompanied by high load average. The error messages are brought about by kate. By the way, the bug didn't occur when I was using kde 4.7.
Please post errors from ~/.xsession-errors for more details about the issue. The messages from KDE 3 don't exist anymore in the code, so it must be something else nowadays. If you export KDE_DEBUG_TIMESTAMP=1 in your kde startup (e.g. ~/.kde/env/debug.sh) you'll also get time information in front of every line there, to spot if they are indeed related to the error message you get.
(In reply to comment #10) > Please post errors from ~/.xsession-errors for more details about the issue. > The messages from KDE 3 don't exist anymore in the code, so it must be > something else nowadays. > > If you export KDE_DEBUG_TIMESTAMP=1 in your kde startup (e.g. > ~/.kde/env/debug.sh) you'll also get time information in front of every line > there, to spot if they are indeed related to the error message you get. I've added export KDE_DEBUG_TIMESTAMP=1 to debug.sh. However, this bug is not easily reproducible. I don't know when I can reproduce it. Yet I'll let you know once I can.
KDE 3 is no longer maintained. Feel free to reopen this ticket if you can reproduce this bug under KDE 4.