Same thing happened to me on winxp. It takes a long time and finally get the same error

Do you uncomment this line in .pro file?

Also don’t forget to recompile :) Furthermore, you should check that there is only one instance of the app running (this one might block the port). If the problem persists, please also check out the application output (should contain something like “Waiting for connection on port xxxx…”).

Sorry for the late reply! This time I didn’t receive an email notification, so I thought anybody had answered.

My .pro file didn’t have such a line (commented or not) when it was created by Qt Creator, but I’ve found somewhere a reference to it, and then I put it there. But the problem persists, and I’m sure there’s only one instance of the application running.

The only message shown in the process of starting the debbuger (apart from that of the popup) is: “QML Debugger connecting…” in the debugger view. My app doesn’t output anything specifically related to the debug process, but it outputs the following when it starts (on Linux; I’m not with my Mac right now to test it on there):

(6685) KSharedDataCache::Private::mapSharedMemory: Opening cache “/var/tmp/kdecache-gustavo/icon-cache.kcache” page size is 4096
(6685) KSharedDataCache::Private::mapSharedMemory: Attached to cache, determining if it must be initialized
(6685) KSharedDataCache::Private::mapSharedMemory: Cache fully initialized — attached to memory mapping
(6685) KSharedDataCache::Private::mapSharedMemory: 4329472 bytes available out of 10485760
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Arquivo ou diretório não encontrado
QFileSystemWatcher: failed to add paths: /home/gustavo/.config/ibus/bus
Bus::open: Can not get ibus-daemon’s address.
IBusInputContext::createInputContext: no connection to ibus-daemon

Is this somehow related to the problem?

ok finally got a chance to try this and got this error:

have to get 4.7.1 … ummm wasn’t aware of no support on 4.7.0

Hmmm… no suport for qml debugging on 4.7.0? This explains why I’m not being able to use the debugger. :)

Chetan, you are using 4.7.0, right?
So, can anyone confirm this is working only on more recent versions of Qt? I didn’t find this information in any doc I’ve read so far.

Thanks!

Chetan, you are using 4.7.0, right?

yes as of now I’m on 4.7.0, but will try to get 4.7.1 from git today and revert if debugging works with that

Ok
Thanks

I’m having serious issues trying to download the 4.7.1 from repository :( … unsuccessful past 2 days, keeps disconnecting or timing out and just aborts. will try again over weekend.

meanwhile, saw this video [youtube.com] on youtube

finally got to the master branch without issues, the qml observer works fine as shown in the youtube video but not able to debug qml apps properly … still trying further

I guess we have to wait for more stable release of this feature. Keep getting this error when I try to debug qml …

Maybe some Troll can throw more light on this dump from the debugger log…

Also found this strange message:

Sadly, as it´s a very usefull feature…

I will try to do the same at home later, on my Linux machine, to see if I get a better result.

@chetankjain: I’m pretty sure QtCreator doesn’t contain any references to qt-greenhouse :)

Anyhow, the debugger log looks indeed strange: What happens is that a connection to the client program was established, and both services (QDeclarativeObserverMode, JSDebugger) are found. However, afterwards the JSDebugger becomes unavailable again. This could happen e.g. because the QmlEngine on the client side is destroyed … Can you tell exactly with which QtCreator version / Qt branch this happened? Or could you try with finalized 4.7.1 and latest QtCreator 2.1 ? Preferably as a bug report at bugreports.qt.nokia.com. Thanks in advance!

kkoehne wrote:

@chetankjain: I’m pretty sure QtCreator doesn’t contain any references to qt-greenhouse :)

Anyhow, the debugger log looks indeed strange: What happens is that a connection to the client program was established, and both services (QDeclarativeObserverMode, JSDebugger) are found. However, afterwards the JSDebugger becomes unavailable again. This could happen e.g. because the QmlEngine on the client side is destroyed … Can you tell exactly with which QtCreator version / Qt branch this happened? Or could you try with finalized 4.7.1 and latest QtCreator 2.1 ? Preferably as a bug report at bugreports.qt.nokia.com. Thanks in advance!

Hi Koehne, thanks for the reply.
yes the latest creator doesn’t have any references to qt-greenhouse, its cleaned up now :)

I tried on the final Qt 4.7.1 and Creator 2.1 itself. I’ll log a bug