I have been having issues with Kbasic 1 (releases 8 & 9) in openSUSE 11.2 KDE, yet, just checked it in another Linux Distro I no longer use, which did not have these issues…
I’ve been getting what appear to be “external errors” to KBasic these past couple of weeks when using the
OpenDialog.GetFile, OpenDialog.GeDir calls,
even though, in general, they still work (IOW, the string variables are still get filled with their values).
The errors pop up in dialogs (generally 3 of them, sometimes 2, sometimes 1), and at times (though not always), and also “yellow baloon popups” regarding an error like with
'Debug: kfilemodule(15396) / kde core (Services) now parsing Now Parsing '/home/opensuse/.local/share/mime/magic "
and at times, a kbrun error when this occurs, but not always.
One of them Dialog Errors is
Debug: (31629): Trying to open ksycoca from "/var/tmp/kdecache-opensuseVpx75k/ksycoca4"
I was wonder if there are issues with the ‘kde’ files, and/or, maybe it is an issue the chmod settings for these ‘ksycoca4*’ files…
-rw-r--r-- 1 opensuse users 1923350 2010-05-14 14:24 /var/tmp/kdecache-opensuseVpx75k/ksycoca4
-rw-r--r-- 1 opensuse users 686 2010-05-14 14:24 /var/tmp/kdecache-opensuseVpx75k/ksycoca4stamp
The other day, I deleted those files to see if the issue would be resolved, and woah, over 10 dialogs popped up with error messages - will not try that again!
As I said, KBasic continues to work most of the time when this happens, so I was not in a hurry to try and see if anyone knows how I can rectify the problems - I have yet to try the other OpenDialog Methods.
Ironically, when this occurs, a KBasic Icon is placed in the system tray - curious, a no mouse clicks brings up anything when clicking on it.
Now, I did want to note that the errors occur only for the initial (first time) usage of OpenDialog.GetDirectory(…) during a program execution…
IOW, Once the OpenDialog.GetDirectory(…) is used the FIRST time while the program is running, the errors do NOT occur anythime you use it again, even when calling the very same method - it appears after the first usage, you can call the OpenDialog.GetDirectory(…) all day long as long as the program is running,
Another thing: I compiled the program to be an binary executable, and the errors did NOT occur when executing the binary file from the Konsole/Bash command line - everything worked fine there.
Regards,
Clifton
