From kde-windows Wed Dec 06 11:33:46 2006 From: Ralf Habacker Date: Wed, 06 Dec 2006 11:33:46 +0000 To: kde-windows Subject: Re: everything compiles but nothing runs Message-Id: <4576AA9A.5050607 () freenet ! de> X-MARC-Message: https://marc.info/?l=kde-windows&m=116540483431670 Rikardo Tinauer schrieb: > > Ralf Habacker wrote: > >> Rikardo Tinauer schrieb: >> >>> Paulo Jorge Guedes wrote: >>> >>> >>>>> -----Original Message----- >>>>> From: Rikardo Tinauer [mailto:rikardo.tinauer@eba.si] >>>>> Sent: terça-feira, 5 de Dezembro de 2006 14:11 >>>>> To: kde-windows@kde.org >>>>> Subject: everything compiles but nothing runs >>>>> >>>>> >>>>> I successfully compiled kdewin32 and kdelibs and installed them. But >>>>> nothing >>>>> runs, every application that I try to run >>>>> crashes and gives back the same Bimbows dialog about sending error. >>>>> >>>>> Did anyone successfully run any KDE4 gui app? Did anyone succeeded to >>>>> compile and run test for KHTML component? >>>>> >>>>> >>>> Can you paste the console output? >>>> >>>> Paulo >>>> >>>> I have managed to run some apps. But I had to build everything in >>>> release >>>> mode. But I still have problem running KHTMLPart. Here is the console >>>> output: >>>> >>>> [3032] kio (KSycoca): ERROR: No database available! >>>> KUrl::setPath / >>>> [3032] kio (KSycoca): ERROR: No database available! >>>> KIO::Slave::createSlave "http" "www.kde.org" "1062" >>>> [3032] testkhtml: ERROR: : couldn't create slave : Cannot talk to >>>> klauncher: Did not receive a reply. Possible causes include: the remote >>>> application did not send a reply, the message bus security policy >>>> blocked >>>> the reply, the reply timeout expired, or the network connection was >>>> broken. >>>> [3032] kio (KSycoca): ERROR: No database available! >>>> KUrl::setPath >>>> KUrl::setPath >>>> >>>> >>>> >> It is required to start klauncher and kded before. Additional it is >> required to have an initial install of kdelibs. With mingw I have done >> something like the following >> >> set >> PATH=c:\Programme\dbus\bin;c:\Programme\gnuwin32\bin;c:\Programme\kdewin32\bin;%PATH% >> >> mingw32-make install -> will install kdelibs into c:\Programme\kelibs >> (german os) >> >> set PATH=c:\Programme\kdelibs\bin;c:\Programme\kdelibs\lib;%PATH% >> set KDEDIRS=c:\Programme\kdelibs >> >> kdeinit -> will starts dbus-daemon, klauncher and kde in silent >> mode >> >> or to get each application in an separate windows >> >> dbus-launch.bat >> start klauncher >> start kded -> this will start kbuildsycoca and kconf_update >> >> Then you are ready to run other applications >> >> Ralf >> >> I did exaclty that. I tried again but nothing chagned. I still get the >> message: >> KDED says: KLaucher could not be reached via D-Bus >> >> My app shows up, then it takes a long time when trying to create KIO Slave >> (this time is probably timeout period). >> Then my app says: could not create slave: Cannot talk to KLauncher. .... >> >> I think my D-Bus is not configured OK, I ran it like this: start >> bin\dbus-deamon --config-file=etc\session.conf >> >> please run the following commands and paste the related output to this list. dbus-launch.bat start klauncher start kded qdbus qdbus (commandline) or dbus-viewer (gui) from Qt's bin dir. qdbus should show something like this. The line org.kde.klauncher is the important one, showing that klauncher is running base service: :1.18 :1.17 org.kde.klauncher org.kde.klauncher-1572 :1.18 org.freedesktop.DBus Then run "qdbus org.kde.klauncher ", which should print base service: :1.19 / /KDebug /KLauncher /MainApplication Then run "qdbus org.kde.klauncher /" , which should print base service: :1.20 method void org.kde.KLauncher.autoStart() method void org.kde.KLauncher.autoStart(int phase) signal void org.kde.KLauncher.autoStart0Done() signal void org.kde.KLauncher.autoStart1Done() signal void org.kde.KLauncher.autoStart2Done() method void org.kde.KLauncher.exec_blind(QString name, QStringList arg_list) method void org.kde.KLauncher.exec_blind(QString name, QStringList arg_list, QStringList envs, QString startup_id) method int org.kde.KLauncher.kdeinit_exec(QString app, QStringList args, QStringList env, QString startup_id, QString& dbusServiceName, QStr ing& error, int& pid) method int org.kde.KLauncher.kdeinit_exec_wait(QString app, QStringList args, QStringList env, QString startup_id, QString& dbusServiceName, QString& error, int& pid) method void org.kde.KLauncher.reparseConfiguration() method int org.kde.KLauncher.requestHoldSlave(QString url, QString app_socket) method int org.kde.KLauncher.requestSlave(QString protocol, QString host, QString app_socket, QString& error) method void org.kde.KLauncher.setLaunchEnv(QString name, QString value) method int org.kde.KLauncher.start_service_by_desktop_name(QString serviceName, QStringList urls, QStringList envs, QString startup_id, bool blind, QString& dbusServiceName, QString& error, int& pid) method int org.kde.KLauncher.start_service_by_desktop_path(QString serviceName, QStringList urls, QStringList envs, QString startup_id, bool blind, QString& dbusServiceName, QString& error, int& pid) method int org.kde.KLauncher.start_service_by_name(QString serviceName, QStringList urls, QStringList envs, QString startup_id, bool blind, QString& dbusServiceName, QString& error, int& pid) method void org.kde.KLauncher.waitForSlave(int pid) method QDBusVariant org.freedesktop.DBus.Properties.Get(QString interface_name, QString property_name) method void org.freedesktop.DBus.Properties.Set(QString interface_name, QString property_name, QDBusVariant value) method QString org.freedesktop.DBus.Introspectable.Introspect() If you can see the above message, klauncher is running well Ralf _______________________________________________ Kde-windows mailing list Kde-windows@kde.org https://mail.kde.org/mailman/listinfo/kde-windows