I have been having issues with Kbasic 1 (releases 8 & 9) for KDE in openSUSE 11.2 KDE, yet, just checked it in another Linux Distro (KDE) I no longer use, which did not have these issues...

I've been getting what appear to be "external errors" to KBasic using the
OpenDialog.GetFiles, OpenDialog.GetFile, OpenDialog.GetDir 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

Code: Select all

'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

Code: Select all

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...

Code: Select all

-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

I tried deleting 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!

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 a OpenDialog.* method 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, i.e. OpenDialog.GetFile - it appears after the first usage, you can call the OpenDialog.GetDirectory(...) all day long as long as the program is running,

Another thing: When I compile a program to be an binary executable, the errors do NOT occur when executing the binary file from the Konsole/Bash command line - everything works fine there.

Regards,
Clifton

Those messages should not create message dialogs in any case, as they are for debugging purposes only. I would recommend asking on KBasic's forums regarding this issue, as it is a bug.

http://www.kbasic.com/forum/

bcooksley wrote:Those messages should not create message dialogs in any case, as they are for debugging purposes only. I would recommend asking on KBasic's forums regarding this issue, as it is a bug.

http://www.kbasic.com/forum/

Hi bcooksley,

Thanks for the response. I did start a thread in the KBasic forum first,
http://kbasic.com/forum/viewtopic.php?f=6&t=624

And it appears that the KBasic Programmer, and another user, which tried it on UBuntu has not witness the error (and/or debug) reports;


And as I pointed out, I went into another KDE version of Linux (I was referring to PCLinuxOS 2010 KDE), and the problem did not occur there as it does in openSUSE 11.2 KDE.

Perhaps I have downloaded some "debugging" files onto my openSUSE system?

I did start a thread on the openSUSE and LinuxQuestions forums too, but got no response,

Regards,
Clifton

Try running "kdebugdialog" and disabling everything.

bcooksley wrote:Try running "kdebugdialog" and disabling everything.

Thanks. I did run that program, and even the second time I ran it, I selected the "disable all debug output", and still get an error message, but at least, it has gotten down to just one error message appearing...

Debug: Default Project(6791)/: Trying to open ksycoca from "/var/tmp/kdecache-opensuseVpx75k/ksycoca4"

Note that the number after "Default Project", here 6791, is different on these calls to KBasic's OpenDialog Methods (getfiles, etc.)

I did a Google search for the phrase:
"Trying to open ksycoca"
and there were 5,650 results from that search - apparently this high number is due to the posts/etc, in this year, 2010 C.E., and the "kyscoca" warning is appearing with various software packages being used in KDE - I noticed that Amarok which mentioned quite a bit, but Amarok does fine here.

At least the Kbasic calls does not crash the program and stop it from running as it should, so I don't understand for the "error" dialog and yellow baloon error notice.

Regards,
Clifton

The message "opening sycoca" is simply KApplication initialising caches which KDE applications depend upon and use to find plugins, file associations and other data.