Re: Maliit, Plasma Active and Mer
Thomas Hi, could you try to remove /home/mer/.kde and a reboot afterwards? Cheers Maurice On May 23, 2012 at 8:48 PM Thomas Pfeiffer colo...@autistici.org wrote: On Monday 21 May 2012 19:26:08 Marco Martin wrote: I updated my Meego Devel image today, it installed Maliit Co but the keyboard does not show up. Do I need to change a config file or do something else for it to work? ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active -- Maurice S. de la Ferté basysKom GmbH Südwestpark 108 | 90449 Nürnberg | Germany Tel: +49 911 689 367 - 0 | Fax: +49 911 689 367 - 299 maurice.fe...@basyskom.com | www.basyskom.com Handelsregister: Darmstadt HRB 9352 | Sitz: Darmstadt Geschäftsführung: Dr.-Ing. Eva Brucherseifer ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Maliit, Plasma Active and Mer
On Thursday 24 May 2012, Thomas Pfeiffer wrote: On Thursday 24 May 2012 00:06:29 Lamarque V. Souza wrote: Em Wednesday 23 May 2012, Thomas Pfeiffer escreveu: On Monday 21 May 2012 19:26:08 Marco Martin wrote: I updated my Meego Devel image today, it installed Maliit Co but the keyboard does not show up. Do I need to change a config file or do something else for it to work? When I tested maliit I needed to edit /usr/share/kde4/apps/startactive/env.conf and change QT_IM_MODULE value to Maliit, like this: QT_IM_MODULE=Maliit Probably you need to do the same. That file was already correct on my system. I also tried deleting (or actually moving) my .kde folder as Maurice suggested, but that did not help either. The problem seems to be elsewhere... just to get an idea where things may go wrong, try to do the whole procedure (that should already be done in scripts, that's weird) in konsole export QT_IM_MODULE=Maliit export QML_IMPORT_PATH=/usr/lib/kde4/imports killall maliit-server maliit-server then launch any app, like another konsole or active-filebrowser, active- webbrowser from that konsole session (btw i don't think meego will stay supported or tested for long) -- Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Maliit, Plasma Active and Mer
On Thursday 24 May 2012 11:15:11 Marco Martin wrote: just to get an idea where things may go wrong, try to do the whole procedure (that should already be done in scripts, that's weird) in konsole export QT_IM_MODULE=Maliit export QML_IMPORT_PATH=/usr/lib/kde4/imports killall maliit-server maliit-server This is what I get when I execute maliit-server (after doing the things above): WARNING: QObject::connect: Cannot connect Plasma::EffectWatcher::destroyed() to (null)::_k_x11FilterDestroyed() WARNING: void MIMPluginManagerPrivate::addHandlerMap(Maliit::HandlerState, const QString) Could not find plugin: libmaliit-keyboard-plugin.so then launch any app, like another konsole or active-filebrowser, active- webbrowser from that konsole session Still nothing. (btw i don't think meego will stay supported or tested for long) Well, I've been wanting to finally ditch Meego for months now. However, there are still quite a few problems with the mer kernel on x86 (or at least on Wetab). Most notably the device not starting after any kernel update (you know about it: https://bugs.nemomobile.org/show_bug.cgi?id=179), but also problems with the hardware power button, resuming from sleep and detection of removable devices. I cannot use a device for tracking development if I cannot update it, so I'm still stuck with Meego until at least this issue is resolved. I know Meego is outdated and I was among the first to ask Why do we still support it?, but the sad truth is that I don't have a viable alternative right now. Cheers, Thomas ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Maliit, Plasma Active and Mer
On Thursday 24 May 2012, Thomas Pfeiffer wrote: This is what I get when I execute maliit-server (after doing the things above): WARNING: QObject::connect: Cannot connect Plasma::EffectWatcher::destroyed() to (null)::_k_x11FilterDestroyed() WARNING: void MIMPluginManagerPrivate::addHandlerMap(Maliit::HandlerState, const QString) Could not find plugin: libmaliit-keyboard-plugin.so so, from a terminal before the above procedure, try to type: gconftool-2 --set /maliit/onscreen/enabled --type list --list-type=string [active-keyboard.qml,en_us] gconftool-2 --set /maliit/onscreen/active --type list --list-type=string [active-keyboard.qml,en_us] Cheers, Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Maliit, Plasma Active and Mer
On Thursday 24 May 2012 14:24:40 Marco Martin wrote: On Thursday 24 May 2012, Thomas Pfeiffer wrote: This is what I get when I execute maliit-server (after doing the things above): WARNING: QObject::connect: Cannot connect Plasma::EffectWatcher::destroyed() to (null)::_k_x11FilterDestroyed() WARNING: void MIMPluginManagerPrivate::addHandlerMap(Maliit::HandlerState, const QString) Could not find plugin: libmaliit-keyboard-plugin.so so, from a terminal before the above procedure, try to type: gconftool-2 --set /maliit/onscreen/enabled --type list --list-type=string [active-keyboard.qml,en_us] gconftool-2 --set /maliit/onscreen/active --type list --list-type=string [active-keyboard.qml,en_us] I just tried this and it seems to have been correctly written into the correct %gconf.xml, but I still get the same warnings and still no keyboard popping up :( ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
