Summary: | Error at startup too general | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kdelibs | Reporter: | Adam <adam.richard2023> |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | wishlist | CC: | apaku, finex |
Priority: | NOR | Keywords: | needs_verification |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Adam
2004-09-10 23:45:19 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. OK, so should I switch "Product" to another component of KDE, and if so, which one? What does "postfactum" mean? 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! 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. Is this bug still reproducible on current KDE 4? I'm not able to reproduce using current version. I'm closing it. |