pak0st @ pak0st @fosstodon.org

Posts

0

Comments

5

Joined

3 yr. ago

@kde@floss.social @kde@lemmy.kde.social hmm... how to resolve this error?

    
QT\_IM\_MODULES=qtvirutalkeyboard ./bin/plasma-keyboard   
Failed to initialize input panel-shell integration, possibly because compositor does not support the layer-shell protocol  
ASSERT failure in Q\_UNREACHABLE(): "Q\_UNREACHABLE was reached", file /home/pak0stpc/Projects/plasma-keyboard/src/main.cpp, line 292  
Aborted (core dumped) QT\_IM\_MODULES=qtvirutalkeyboard ./bin/plasma-keyboard  
  

  

I would like to give it a shot on my system

@tertle950 @kde@floss.social @kde@lemmy.kde.social you can. I found it a bit unreliable sometimes because iOS does iOS stuff behind the scenes. The Android client is solid on my devices.

I swap between #localsend and #kdeconnect . Most of the time I don't need all the extras bundled with KDE Connect.

@usia @dingdongitsabear @HiddenLayer555 @postmarketOS I completely missed the deprecation notice. Thanks!

@dingdongitsabear @HiddenLayer555 take a look at pmOS osk-sdl for LUKS unlock: https://wiki.postmarketos.org/wiki/Osk-sdl

Heck- just try @postmarketOS on the thing 😄

@Lofenyy not so much apps but infrastructure pieces.
Better video camera support would be great (Dino would be awesome on Linux phone!).
A bit more integration with UnifiedPush. I'm looking at Firefox, Thunderbird and chat apps.
More streamlined solution for map navigation - it's janky atm.
OSKs (on-screen keyboard) can be temperamental. Lets see when we will get text-input protocol v4 for Wayland 😄