Maliit, Plasma Active and Mer

[Thomas Pfeiffer]

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