Re: PA OpenEmbedded support (WIP)
2012/4/19 Lamarque V. Souza lamarque.souza@basyskom.com: Em Thursday 19 April 2012, Samuel Stirtzel escreveu: Another idea, could this be a visibility problem? Log of binutils nm: - samuel@s-stirtzel-linux:/work/oe-core/tmp-eglibc/sysroots/overo/usr/lib/kde 4$ nm -C plasma_appletscript_declarative.so | grep script 00023c68 t global constructors keyed to declarativescriptenv.cpp 000347d8 r qt_meta_data_JavascriptAddonPackageStructure 00034790 r qt_meta_stringdata_JavascriptAddonPackageStructure 0002b3b0 T DeclarativeAppletScript::scriptEnv() 0001ed60 T JavascriptAddonPackageStructure::pathChanged() 0001ecb4 T JavascriptAddonPackageStructure::qt_metacall(QMetaObject::Call, int, void**) 0001ecb8 T JavascriptAddonPackageStructure::qt_metacast(char const*) 00038138 D JavascriptAddonPackageStructure::staticMetaObject 0001ec84 T JavascriptAddonPackageStructure::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) 00038130 D JavascriptAddonPackageStructure::staticMetaObjectExtraData 0001efcc T JavascriptAddonPackageStructure::JavascriptAddonPackageStructure(QObject*, QListQVariant const) 0001efcc T JavascriptAddonPackageStructure::JavascriptAddonPackageStructure(QObject*, QListQVariant const) 0001f9bc t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() 0001f988 t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() 0001f988 t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() 0001ec88 T JavascriptAddonPackageStructure::metaObject() const U Plasma::AppletScript::description() const U Plasma::DeclarativeWidget::scriptEngine() const 00038194 D typeinfo for JavascriptAddonPackageStructure 000347b4 R typeinfo name for JavascriptAddonPackageStructure 00038148 D vtable for JavascriptAddonPackageStructure - U means undefined and U Plasma::DeclarativeWidget::scriptEngine() const exports no function. Any ideas where I could look next? On Meego x86 image: [root@localhost ~]# nm -C /usr/lib/kde4/plasma_appletscript_declarative.so nm: /usr/lib/kde4/plasma_appletscript_declarative.so: no symbols Of course I did that before the library was stripped, otherwise it doesn't show any symbols. On my device I get the same message as you. Regarding kdelibs-4.8.2, I don't see a git tag or something looking like 4.8.2 at [1], maybe it wasn't pushed yet? [1] http://quickgit.kde.org/index.php?p=kdelibs.gita=summary -- Regards Samuel ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA OpenEmbedded support (WIP)
2012/4/20 Samuel Stirtzel s.stirt...@googlemail.com: 2012/4/19 Lamarque V. Souza lamarque.souza@basyskom.com: Em Thursday 19 April 2012, Samuel Stirtzel escreveu: Another idea, could this be a visibility problem? Log of binutils nm: - samuel@s-stirtzel-linux:/work/oe-core/tmp-eglibc/sysroots/overo/usr/lib/kde 4$ nm -C plasma_appletscript_declarative.so | grep script 00023c68 t global constructors keyed to declarativescriptenv.cpp 000347d8 r qt_meta_data_JavascriptAddonPackageStructure 00034790 r qt_meta_stringdata_JavascriptAddonPackageStructure 0002b3b0 T DeclarativeAppletScript::scriptEnv() 0001ed60 T JavascriptAddonPackageStructure::pathChanged() 0001ecb4 T JavascriptAddonPackageStructure::qt_metacall(QMetaObject::Call, int, void**) 0001ecb8 T JavascriptAddonPackageStructure::qt_metacast(char const*) 00038138 D JavascriptAddonPackageStructure::staticMetaObject 0001ec84 T JavascriptAddonPackageStructure::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) 00038130 D JavascriptAddonPackageStructure::staticMetaObjectExtraData 0001efcc T JavascriptAddonPackageStructure::JavascriptAddonPackageStructure(QObject*, QListQVariant const) 0001efcc T JavascriptAddonPackageStructure::JavascriptAddonPackageStructure(QObject*, QListQVariant const) 0001f9bc t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() 0001f988 t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() 0001f988 t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() 0001ec88 T JavascriptAddonPackageStructure::metaObject() const U Plasma::AppletScript::description() const U Plasma::DeclarativeWidget::scriptEngine() const 00038194 D typeinfo for JavascriptAddonPackageStructure 000347b4 R typeinfo name for JavascriptAddonPackageStructure 00038148 D vtable for JavascriptAddonPackageStructure - U means undefined and U Plasma::DeclarativeWidget::scriptEngine() const exports no function. Any ideas where I could look next? On Meego x86 image: [root@localhost ~]# nm -C /usr/lib/kde4/plasma_appletscript_declarative.so nm: /usr/lib/kde4/plasma_appletscript_declarative.so: no symbols Of course I did that before the library was stripped, otherwise it doesn't show any symbols. On my device I get the same message as you. Regarding kdelibs-4.8.2, I don't see a git tag or something looking I will try commit d2ce1819baa85ad0e895971ca25232327e9fc91e until there is a git tag. [1] http://quickgit.kde.org/index.php?p=kdelibs.gita=summary -- Regards Samuel -- Regards Samuel ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA OpenEmbedded support (WIP)
Em Friday 20 April 2012, Samuel Stirtzel escreveu: 2012/4/20 Samuel Stirtzel s.stirt...@googlemail.com: 2012/4/19 Lamarque V. Souza lamarque.souza@basyskom.com: Em Thursday 19 April 2012, Samuel Stirtzel escreveu: Another idea, could this be a visibility problem? Log of binutils nm: - samuel@s-stirtzel-linux:/work/oe-core/tmp-eglibc/sysroots/overo/usr/lib /kde 4$ nm -C plasma_appletscript_declarative.so | grep script 00023c68 t global constructors keyed to declarativescriptenv.cpp 000347d8 r qt_meta_data_JavascriptAddonPackageStructure 00034790 r qt_meta_stringdata_JavascriptAddonPackageStructure 0002b3b0 T DeclarativeAppletScript::scriptEnv() 0001ed60 T JavascriptAddonPackageStructure::pathChanged() 0001ecb4 T JavascriptAddonPackageStructure::qt_metacall(QMetaObject::Call, int, void**) 0001ecb8 T JavascriptAddonPackageStructure::qt_metacast(char const*) 00038138 D JavascriptAddonPackageStructure::staticMetaObject 0001ec84 T JavascriptAddonPackageStructure::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) 00038130 D JavascriptAddonPackageStructure::staticMetaObjectExtraData 0001efcc T JavascriptAddonPackageStructure::JavascriptAddonPackageStructure(QObjec t*, QListQVariant const) 0001efcc T JavascriptAddonPackageStructure::JavascriptAddonPackageStructure(QObjec t*, QListQVariant const) 0001f9bc t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() 0001f988 t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() 0001f988 t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() 0001ec88 T JavascriptAddonPackageStructure::metaObject() const U Plasma::AppletScript::description() const U Plasma::DeclarativeWidget::scriptEngine() const 00038194 D typeinfo for JavascriptAddonPackageStructure 000347b4 R typeinfo name for JavascriptAddonPackageStructure 00038148 D vtable for JavascriptAddonPackageStructure - U means undefined and U Plasma::DeclarativeWidget::scriptEngine() const exports no function. Any ideas where I could look next? On Meego x86 image: [root@localhost ~]# nm -C /usr/lib/kde4/plasma_appletscript_declarative.so nm: /usr/lib/kde4/plasma_appletscript_declarative.so: no symbols Of course I did that before the library was stripped, otherwise it doesn't show any symbols. On my device I get the same message as you. Regarding kdelibs-4.8.2, I don't see a git tag or something looking I will try commit d2ce1819baa85ad0e895971ca25232327e9fc91e until there is a git tag. Yes, that commit includes the fix. The tags tends to enter the repository a little latter after the release. Well, v4.8.2 should be there by now, maybe someone missed it. -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA OpenEmbedded support (WIP)
2012/4/19 Lamarque V. Souza lamarque.souza@basyskom.com: Em Thursday 19 April 2012, Samuel Stirtzel escreveu: 2012/3/30 Lamarque V. Souza lamarque.souza@basyskom.com: Em Friday 30 March 2012, Samuel Stirtzel escreveu: Hi, Hi, lately I have good progress on my work, normal KDE applications seem to work fine in OpenEmbedded. But my main goal, to port PA, still needs some effort. Currently I'm at the point that the home screen of PA shows up, but it seems like something went wrong with the declarative scriptengine. So there is a big sign with a X as label showing the text: Could not create a declarativeappletscript sctiptengine Enable all debug messages using kdebugdialog program (if possible), restart the graphical interface, try again and send me the ~/.xsession-errors file. Hi, I'm still working on this and looked through it once again, and there seem to be more relevant parts in the logfile: You are probably using packages compiled with different versions of Qt, kdelibs or other dependencies of DeclarativeWidget. Send me the output of the command rpm -qa. Please note I am a developer, I am not using any precompiled iso/images. Currently I am running on an ARMv7a Overo Gumstix and create build instructions (to cross compile PA on a tool-chain) for OpenEmbedded [1] and the Yocto Project [2]. I am building everything from source, so I don't have them installed via RPM. But as opkg (the package manager I use) shows them as: libqtcore4 - 4.8.0 kdelibs4 - 4.8.0 kde-runtime - 4.8.0 ... A full list of _all_ installed packages: http://pastebin.com/CVV2zRvy [1] http://www.openembedded.org/wiki/Main_Page [2] http://www.yoctoproject.org/ -- Regards Samuel ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA OpenEmbedded support (WIP)
Em Thursday 19 April 2012, Samuel Stirtzel escreveu: 2012/4/19 Lamarque V. Souza lamarque.souza@basyskom.com: Em Thursday 19 April 2012, Samuel Stirtzel escreveu: 2012/3/30 Lamarque V. Souza lamarque.souza@basyskom.com: Em Friday 30 March 2012, Samuel Stirtzel escreveu: Hi, Hi, lately I have good progress on my work, normal KDE applications seem to work fine in OpenEmbedded. But my main goal, to port PA, still needs some effort. Currently I'm at the point that the home screen of PA shows up, but it seems like something went wrong with the declarative scriptengine. So there is a big sign with a X as label showing the text: Could not create a declarativeappletscript sctiptengine Enable all debug messages using kdebugdialog program (if possible), restart the graphical interface, try again and send me the ~/.xsession-errors file. Hi, I'm still working on this and looked through it once again, and there seem to be more relevant parts in the logfile: You are probably using packages compiled with different versions of Qt, kdelibs or other dependencies of DeclarativeWidget. Send me the output of the command rpm -qa. Please note I am a developer, I am not using any precompiled iso/images. Currently I am running on an ARMv7a Overo Gumstix and create build instructions (to cross compile PA on a tool-chain) for OpenEmbedded [1] and the Yocto Project [2]. Well, there must be something wrong with the kde-runtime package you compiled. The message plasma-device(583)/libplasma Plasma::loadEngine: Couldn't load script engine for language declarativeappletscript ! error reported: The service 'Declarative widget' does not provide an interface 'Plasma::AppletScript' w DeclarativeAppletScript (from plasma_appletscript_declarative.so, which is the library used by 'Declarative widget' service) inherits from Plasma::AppletScript. I am building everything from source, so I don't have them installed via RPM. But as opkg (the package manager I use) shows them as: libqtcore4 - 4.8.0 kdelibs4 - 4.8.0 kde-runtime - 4.8.0 That seems fine regarding this particular problem. You should use kdelibs-4.8.2, which includes a fix for a slowness problem in nepomuk. -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA OpenEmbedded support (WIP)
2012/4/2 Samuel Stirtzel s.stirt...@googlemail.com: 2012/3/30 Lamarque V. Souza lamarque.souza@basyskom.com: Em Friday 30 March 2012, Samuel Stirtzel escreveu: Hi, Hi, lately I have good progress on my work, normal KDE applications seem to work fine in OpenEmbedded. But my main goal, to port PA, still needs some effort. Currently I'm at the point that the home screen of PA shows up, but it seems like something went wrong with the declarative scriptengine. So there is a big sign with a X as label showing the text: Could not create a declarativeappletscript sctiptengine Enable all debug messages using kdebugdialog program (if possible), restart the graphical interface, try again and send me the ~/.xsession-errors file. Enabled the debug messages, but it doesn't create a .xsession-errors file, I should note that I don't use kdm, currently I boot into the console and start PA via xinit /usr/bin/startkde or xinit /usr/bin/startactive I use plasma-contour-config-0.2.13 from ftp.kde.org. the console log had some relevant looking parts: - plasma-device(553)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-device(553)/libplasma Plasma::PluginLoader::loadApplet: we have a script using the declarativeappletscript API plasma-device(553)/libplasma Plasma::loadEngine: Couldn't load script engine for languagedeclarativeappletscript ! error reported:The service 'Declarative widget' does not provide an interface 'Plasma::AppletScript' w - Under /usr/lib/kde4 there are these (relevant?) libraries found: - plasma_appletscriptengine_dashboard.so plasma_runnerscript_javascript.so plasma_dataenginescript_javascript.so plasma_appletscript_simple_javascript.so plasma_appletscriptengine_webapplet.so plasma_appletscript_declarative.so - Are you using KDE SC 4.8.0 as I told you? Yes all cloned repositories use the v4.8.0 respective Active/2.0 tag. The Qt and kde libs are at /usr/lib: - libQtDeclarative.so.4.8.0 libkdeclarative.so.5 libQtDeclarative.so.4.8 libQtDeclarative.so.4 libkdeclarative.so.5.8.0 - So I assume that some library like plasma_appletscriptengine_declarative.so is missing. But kde-runtime logs don't indicate something like that. Probably you are using the wrong version of the libraries or something else is missing. For exampe, this week a guy tried to install PA on OpenSuse 12.1 and it only succeeded when he installed share-like-connect pacakge. Do you have share-like-connect installed? The package share-like-connect is installed (git tag Active/2.0). -- Lamarque V. Souza http://www.basyskom.com/ -- Regards Samuel -- Regards Samuel ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA OpenEmbedded support (WIP)
Em Friday 30 March 2012, Samuel Stirtzel escreveu: Hi, Hi, lately I have good progress on my work, normal KDE applications seem to work fine in OpenEmbedded. But my main goal, to port PA, still needs some effort. Currently I'm at the point that the home screen of PA shows up, but it seems like something went wrong with the declarative scriptengine. So there is a big sign with a X as label showing the text: Could not create a declarativeappletscript sctiptengine Enable all debug messages using kdebugdialog program (if possible), restart the graphical interface, try again and send me the ~/.xsession-errors file. Under /usr/lib/kde4 there are these (relevant?) libraries found: - plasma_appletscriptengine_dashboard.so plasma_runnerscript_javascript.so plasma_dataenginescript_javascript.so plasma_appletscript_simple_javascript.so plasma_appletscriptengine_webapplet.so plasma_appletscript_declarative.so - Are you using KDE SC 4.8.0 as I told you? The Qt and kde libs are at /usr/lib: - libQtDeclarative.so.4.8.0 libkdeclarative.so.5 libQtDeclarative.so.4.8 libQtDeclarative.so.4 libkdeclarative.so.5.8.0 - So I assume that some library like plasma_appletscriptengine_declarative.so is missing. But kde-runtime logs don't indicate something like that. Probably you are using the wrong version of the libraries or something else is missing. For exampe, this week a guy tried to install PA on OpenSuse 12.1 and it only succeeded when he installed share-like-connect pacakge. Do you have share-like-connect installed? -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
