Version: 3.0.4 (using KDE 3.2.3, SuSE) Compiler: gcc version 3.3.3 (SuSE Linux) OS: Linux (i686) release 2.6.5-7.104-default History: I installed KDE 3.2.3 using SuSEs Yast2 (cmd was: "yast2 -i *.rpm") and yast2 did not find missing dependencies. RPM reported: libdb-4.1.so is needed by kdevelop3-3.0.4-3 (This just for clarification) When trying to load a project file in KDevelop an error dialog appeared saying: "Could not create language plugin for C++." This could be improved by 1) Trying to figure out what failed and reporting to the user Or: 2) Give a hint, that failed dependencies (like in this case libdb4.1) might be the problem. It is also a internationalization problem since the german text reads: "Die Sprachunterstützung für C++ kann nicht angelegt werden." which is more like "the language support for C++ can not be established". This does not even hint to a plugin load failure.
1. We do not build the rpm's ourselves. 2. You should listen to SuSE when they say that you need libdb4.1. 3. You are rigth the message could be more verbose.
1. I know, it was just to clarify the situation 2. Thats the thing: It didn't tell me. Fortunately rpm did :) I wrote those things just to describe how to reproduce the situation. How about: a "more detail" button where you could read that a specific plugin could not be loaded. Ideally with some additional message like "reason: failed to load libdb4.1.so". Don't know if such information is available in the KDevelop plugin system. At minimum the text should indicate a plugin load failure in the german translation to point the user to the right direction.
we support some basic information in KDevelop4/KDE4 but it really isn't possible to find out the cause of a dlopen failing. Thats a system limitation.