I can confirm that in Spanish n, w, y, ñ, V, é, Í, ú don’t work and that ó works as “home” key in the line. I haven’t tried all the keys, so probably there are more bugs
1 Like
I haven’t had any problems with the “Q” or “K” keys on Signal. The only problem I have is with capital “C” where it basically acts as a backspace. This is for default English US keyboard
interestingly, my capital C works fine. but if I turn on caps, the Q and K characters work and some others don’t. Pretty crazy bug, lol.
2 Likes
I think the missing letters issue with the OSK happens on Wayland only. See here several other issues.
I can use all letters when not running using Wayland for the flatpak.
2 Likes
just tried this by removing the wayland arguments from desktop file. Confirmed all keys work except capital C which now works like a backspace, lol.
And of course things are a lot more blurry 
EDIT: After testing more, Ive found this to be worse on balance so I reverted back. attachments now crash the app, and the app is blurry. Looks like the issues were reported some time ago so shame there is still no fix yet…
As far as the ceyboard is concerned, here’s the suggestion I was given:
1 Like
I’m not entirely sure but looking into this issue on squeekboard: “Make sure Electron applications receive correct input”, it appears as though @dos may have already fixed this here.
Did I understand this correctly to be a temporary workaround for the Chromium bug that would fix the Signal (and other Chromium related) input issues? I’m assuming this hasn’t been rolled out yet?
Perhaps @dos would like to shed some light on this as I’m a little out of my depth
1 Like
Good find! The MR hasn’t been merged yet or included in a release.
I just tested the proposed change and found it to work flawlessly on the Signal Desktop flatpak.
2 Likes
Awesome!
Now if you wouldn’t mind showing us noobs the steps you used to test it that would be equally appreciated!
EDIT: Just realised your link pointed to instructions! Haha, my bad.
Btw, you might have to install the devscripts, git and git-buildpackage packages before you begin following the steps from the merge request:
sudo apt update
sudo apt full-upgrade
sudo apt install devscripts git git-buildpackage
1 Like
Confirmed that input is now fixed (with the US Keyboard layout at least).
Hopefully this doesn’t break anything when the real update is rolled out later!
Great work @dos , this actually makes essential apps finally “work”!
3 Likes
Hi, I am relatively new to Linux and just received my L5.
I wish to install Signal so I can talk and text over WiFi.
I ran:
sudo apt update
sudo apt full-upgrade
sudo apt install devscripts git git-buildpackage
But now I have a screen that is looking for the default mirror for pbuilder.
I dont know what that is and the terminal does not seem to accept any inputs.
Can you help?
Thanks, Tom
Hi Tom,
I got exactly the same dialog. I don’t know what that is either.
The only thing that ultimately helped was typing into the text field the exact example URL that the dialog suggested.
1 Like
If I remember correctly, in the same message to supply a mirror, it gives you an example for a debian mirror domain. I’m pretty sure I used the same domain and that worked for me.
Keyboard Snag After Updating
Just a quick warning - after testing the new keyboard for another day, I’ve notice one snag. In Terminal (when using nano in this case), the keyboard was not recognising the ALT+X commands to save, etc. In order to get that to work, I had to pull up the screen that shows the “ESC” key, press that and then try to do the ALT + X commands again - and it doesn’t always work, you may need to try it a couple times which is less than ideal. Also, you need to make sure you used the capital version of the character, etc. So yeah, unfortunately it does seem to negatively effect terminal input.
Perhaps @dos may want to update the fix to account for that? Or at worst, keep the “Terminal” layout working using the old system and all the other standard layouts using the new one? Just a suggestion
1 Like
Exactly. That’s what I meant to say. Thanks for clarifying!
Ok, you might be running into issue squeekboard!373 (explanation).
1 Like
Yep, just noticed that @Dos mentions it under your post.
Hopefully they can figure out a solution and fix both at the same time.
1 Like
For the record, all you need to get the command to register anyway is to toggle the modifier back and forth after pressing the key and then retry. It’s just really annoying 
2 Likes
Haha, indeed it is!
When trying to edit a file in nano I couldn’t get it to work that way, I had to go into that little screen where the ESC key is and after pressing escape it would allow me to “lock” the alt key first before trying (worked around 50% of the time lol). It seemed I had slightly better luck that way so I don’t know if that helps with the fix at all but thought I’d share
In any case, great work so far on the input fix for Chromium-based apps. It makes me not want to throw myself over a cliff when using Signal, haha. Seriously, that alone is making the Librem5 a waaaay more productive device for me because it’s reconnected me to my social circle!
If we can nail that final snag with the Terminal we’ll be golden!
2 Likes
@dos, thank you for your help. Now that i am past the mirror for pbuilder,
are these the correct instructions for installing Signal?
sudo flatpak remote-add --title=‘Signal Desktop’
signal https://elagost.com/flatpak/signal.flatpakrepo
sudo flatpak install signal org.signal.Signal
Thanks, Tom
Video calls do not work yet on L5, camera needs better integration other than just the Dev Camera application.