As the subject says I'm trying to run a program who's owner is root
but has set UID and I'm running it as a normal user. I must admit I'm not really sure what Qt tries to do here but I thought since it uses KDE maybe someone here has any ideas.
(-r-s--x--x 1 root root 6223862 Sep 13 12:28 /usr/lib/VirtualBox/VirtualBox*)

When it gets to QFileDialog::getOpenFileName it fails to open the
native KDE file dialogue with this error:

kdeinit4: Shutting down running client.
klauncher(2029) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
end from FAM server connection
klauncher(2033) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
klauncher(2036) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(2006): couldn't create slave: "Cannot
talk to klauncher: Not connected to D-Bus server"
klauncher(2039) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
klauncher(2042) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(2006): couldn't create slave: "Cannot
talk to klauncher: Not connected to D-Bus server"
end from FAM server connection
klauncher(2045) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
klauncher(2048) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(2006): couldn't create slave: "Cannot
talk to klauncher: Not connected to D-Bus server"
klauncher(2051) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
klauncher(2054) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(2006): couldn't create slave: "Cannot
talk to klauncher: Not connected to D-Bus server"
klauncher(2057) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(2006): Couldn't start knotify from
knotify4.desktop: "KLauncher could not be reached via D-Bus. Error
when calling start_service_by_desktop_path:
Not connected to D-Bus server
"

end from FAM server connection
end from FAM server connection
klauncher(2060) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
klauncher(2063) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(2006): couldn't create slave: "Cannot
talk to klauncher: Not connected to D-Bus server"
end from FAM server connection
end from FAM server connection
end from FAM server connection

I'm sure it's probably something that me or my distro have badly
configured but I don't really understand what. I do get the DBUS not
stated message but I'm not sure what the problem is , should DBUS de
started for root also because the program runs as root.

Any help would be appreciated , thanks.