Thanks for testing the 'keyboard shortcuts' i will start digging elsewhere for the cause. FYI, I am building under gcc-4.5.2 and have no such kwrite crashes.
Jay
On Sun, Apr 29, 2012 at 10:08 PM, Darrell Anderson humanreadable@yahoo.comwrote:
Yes Porteus is slackware based.
I just finished running some nominal tests of kcmshell in Trinity in Current. Everything worked as expected (except kwrite, reported in a different thread). I used all of the different methods do open the keyboard shortcut dialog and they all worked. No crashes.
Are you saying that more recent versions of VirtualBox can be built against Qt3?
Yes. I am currently using Virtualbox 4.1.8 built (on Porteus) from Trinity with no KDE4. Virtualbox supplies its own qt libraries in /opt/Virtualbox
libQtCoreVBox.so.4 libQtGuiVBox.so.4 libQtNetworkVBox.so.4 libQtOpenGLVBox.so.4
Ah, I see. Thank you. I'm using 3.2.12 OSE on 13.1. I don't like playing the bleeding edge game. Once I get my production system running to taste I tend to leave things alone. Thus, I don't keep pace with VirtualBox releases.
In my Trinity build environments for Slackware I don't install the Qt4 and KDE4 packages to avoid potential conflicts during the builds. I have a Qt4/KDE4 installed in virtual machines where I want to test Trinity but that is all run-time. Regardless, that VirtualBox can be built without Qt4 is good to know.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting