Overall performance and operation has been excellent, until recently, which **may** coincide with upgrade from KDE 4.11.x to KDE 4.12.y.

The issue I am seeing is related to opening files.

If I navigate to a file.dxf in Dolphin (KDE file manager), then right click on it and select Open With: qcad, all is wellIf I start qcad with ./qcad from the install directory, or if I start it from the GUI (using a customized qcad.desktp file),then chose File-Open Recent and select from the list, file.dxf opens OK If I start qcad with ./qcad from the install directory, or if I start it from the GUI (using a customized qcad.desktp file), then choose File-Open, a file browser opens (I believe this is called the kde file chooser interface), I can navigate my file system to a file, I left click on a file , which normally would select it, the file chooser window closes but no file gets opened in QCADCAM.

./qcadDebug: RCamScriptsPlugin: init Debug: RDxfPlugin::init Debug: RHelpPlugin::init Debug: RProScriptsPlugin::init Debug: TIMER: 77 ms - "loading add-ons" Debug: TIMER: 772 ms - "initializing add-ons" Debug: RPluginBase: postInit: "CAM" Debug: RPluginBase: postInit: "DWG" Debug: RPluginBase: postInit: "Pro Tools" [b]Warning: KGlobal::locale(): Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not workWarning: Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)Warning: Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)[/b]

The highlighted CLI messages appear when I move the mouse into the tree hierarchy of the file chooser interface.((Hmmm, color and bold highlighting not working in code window?))I tried similar CLI starups with gimp and inkscape, but thesy seem to use a differnt file chooser interface (I believe called the qT file chooser)QCAD seems to use the KDE chooser (via KDE integration), so I tried a know KDE App with these results

QCAD uses Qt for its user interface, including file dialogs. QCAD tells Qt to use the native file dialog since it has major advantages over the Qt file dialog, especially under Mac OS X and Windows. If the native file dialog does not work, this is either a bug between Qt and KDE or due to the fact that we use Qt 4.8.4 which might simply not support your updated KDE version.

If you are comfortable with a plain text editor and JavaScript source code, you can resort to using the Qt file dialog instead:

I suspect it is related to your comment:"...this is either a bug between Qt and KDE or due to the fact that we use Qt 4.8.4 which might simply not support your updated KDE version."

I'll pursue this on openSUSE forum and see what I can find.

Something is for sure changed in the implementation of KDE 4.12.y from previous releases(e.g. 4.11.x)I found I had very intermittent (infrequent) crashes of the whole desktop session (not QCAD related) and the file chooser interface discussed here would cause QCAD to seg fault soon after the mouse entered the file tree hierarchy; I decided to rebuild my .kde4 profile. So far, no desktop crashes and this new, different, but still defective behavior of QCAD when using the file chooser.

For now, I know how to start QCAD and get work done.I may try reverting to the QT interface with you suggested tweak as a "learning adventure"

It would appear that in my initial attempts to debug KDE desktop crashes that **appeared** to be QCAD related I borked the script ...../scripts/OpenFile/OpenFile.js while chasing the error message related to KGlobal::locale():.

A clean unpacking of QCADCAM 3.4.6 works fineMY bad....

PS: It would appear that the root cause of my desktop crashes was an out of date ~/.kde4 config directory.I rebuilt a new ~/.kde4 and crashes have stopped (so far).Some difference between KDE 4.11.x and 4.12.y probably the cause; I was unable to pinpoint it.Issue was broader than QCADCAM.