@micland WOOW!!! Thank you sooo much micland!! It works!!! I tried a code similar to yours but some data were missing. Just needed to do a very tiny modification on your code: qDebug() << key << value.variant().toString(); or directly qDebug() << value.variant().toString(); Except it, it is perfect! Thank you again. @micland said: I have no clue why the qdbusviewer of Qt 5.6 is unable to call the DBus method but the code snippet above is working fine. I hope it is going to change as I intend to use it or the 5.7 version very soon. Cheers again.

Hi, AFAIK, there's no such feature. You can check the bug report system to see if there's already something about it.

4.7 ? Then you will have to take a look at the Qt Mobility module. If you are locked to the Qt 4 series, please upgrade to at least 4.8.7. If not locked then consider using Qt 5.6.0 which just got released and is LTS.

@CarlosQ said: But the connect in MainWindow is: connect(myDialog, SIGNAL(myClicked()), this, SLOT(ShowText())); Exaxctly, that means you understood what I was talking about =) Thanks a lot. I'm very happy. Glad to hear that!

@AlterX Ok, I see, I will change this for the device internal pointers, but the "currentDevice" is used many times from outside to access that data. That's why I kept it public, I didn't really see much sense it making that private and then allow to read it anyway. I see the issue of it being written from outside, but I checked all occurences and they all solely query data and call methods, so I didn't think it helps me with the segmentation fault, what do you think? Stephan