Bug 89267 - Error at startup too general
Summary: Error at startup too general
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords: needs_verification
Depends on:
Blocks:
 
Reported: 2004-09-10 23:45 UTC by Adam
Modified: 2008-12-20 18:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam 2004-09-10 23:45:19 UTC
Version:            (using KDE KDE 3.2.3)
Installed from:    Gentoo Packages

On startup an error message keeps appearing:

The specified folder does not exist or was not readable

It seems to be either a previous project I had opened that I deleted, or a configuration option specified a path that doesn't exist anymore.  But it's difficult to find out what the error is because the message doesn't give any details.  At least it should say which folder doesn't exist or was not readable, and probably also what KDevelop was trying to do with it.
Comment 1 Jens Dagerbo 2004-09-11 01:01:16 UTC
That error message actually comes from kdelibs/kio/kfile/kdiroperator.cpp. KDevelop (the FileSelector?) is probably trying to restore to a directory that is no longer available (deleted?) and this message is the result. 

I agree that the error could be better, but the messagebox is generated in kdelibs and there is no error return so we can't even explain it postfactum.
Comment 2 Adam 2004-09-11 01:12:32 UTC
OK, so should I switch "Product" to another component of KDE, and if so, which one?

What does "postfactum" mean?
Comment 3 Nick Savoiu 2005-04-03 05:30:53 UTC
I get the same message and it reminds me of many useless such error messages I get in Windows. For me 'specified' is a four letter word!
Comment 4 Chris Torske 2005-09-20 17:55:35 UTC
I too got this error message, though I am partly thinking it isn't directly from the kdelibs/kio/kfile/kdiroperator.cpp file.  The reason that I am thinking it isn't from that file, is that the file  is just doing it's job from a request up above it.  What I am thinking is the problem, is that initialy, kdevelop is requesting a invalid call to kdiroperator.cpp from a empty recent project list.  Now I haven't tested my theory yet to see how much ground it holds, but it may be something to look into.

Also I am thinking bug 109514 is also related to this one, could even be the direct reason why the error messages is coming up.
Comment 5 FiNeX 2008-11-17 14:58:00 UTC
Is this bug still reproducible on current KDE 4? 
Comment 6 FiNeX 2008-12-20 18:00:52 UTC
I'm not able to reproduce using current version. I'm closing it.