Falkon, installed by snap (using snap kde-frameworks-5 & connected), cannot change the language. Every time I change it to Czech and restart, it says English. That prevents me to use keyboard combo to write Czech characters with diacritic.
(In reply to Tom Kijas from comment #0) > > That prevents me to use keyboard combo to write Czech characters with > diacritic. That should not work like that, you should be able to write czech diacritics regardless of interface language.
Strange. I have no problems in KDE apps nor in GNOME apps, just Falkon.
I found something! Combo of key should (and in KDE&GNOME does) write this:_ ć _ (nonsense with c, but it doesn't matter), instead, it write this_ ç _ To me, it seems Falkon use another type of language.
Installed Qt WebEngine locales directory not found at location /usr/share/qt5/translations/qtwebengine_locales. Trying application directory... Qt WebEngine locales directory not found at location /snap/falkon/23/usr/bin/qtwebengine_locales. Trying fallback directory... Translations MAY NOT not be correct. and Qt WebEngine resources not found at /snap/falkon/23/usr/bin. Trying fallback directory... The application MAY NOT work.
May the problem be in the connection to kde-frameworks-5 ? I had to install snap version of it, so it probably does not use system-installed version (I use NEON so I presume I have it installed). I can provide info and cooperation if u want it.
I was going to report the same issue. Using the compose key, and I can enter a few non-acsii characters like ç, é and æ, but most others, like č → —, don't work in Falkon. (I had to paste them from another app since I'm using Falkon now.) One other thing I noticed is that it's not just in the web content, but also Falkon's inter I'm also using the Snap.
Sorry, I accidentally pressed save to early! One other thing I noticed is that it's not just in the web content, but also Falkon's user interface that has this problem, such as the URL bar and the password search in the preferences. I am also using the Snap. I tried the Snap of KeepassXC, another Qt app, but not a KDE one, and it works fine. I also just tried the Snap of Okular, which I believe does use the KDE Frameworks Snap, and it *does* have the same problem as Falkon.
Thank you for additional info, so now we just need someone to set status to CONFIRMED and to cooperate with us to solve this issue and... I am not sure whether someone is taking care about Falkon now?
This is issue in QtWebEngine, please report it on Qt bugtracker.
Well, I do not think so, because it affects only software, that has been packaged into snaps. It seems the connection to our KDE desktop doesn't work, because Falkon doesn't see our KDE printers too, making it almost impossible to use. Are u developer of Falkon?
Yes, I am developer of Falkon. Well, I've seen this issue in past also on my system with normal build, although it's not reproducible all the time. If you have this issue only in snap package, then I have no solution for you. Snap/Flatpak/AppImage are all experimental builds that are expected to have various issues with desktop integration.
And to add to this, I have been closing all issues that were present only on Flatpak/AppImage builds with QupZilla, and I plan to do the same with Falkon (with addition of snap builds).
Ok thanks for the info. I had no problems with ppa's version of falkon (but it is outdated). What other way can we use to get the new Falkon in KDE Neon (e.g. not to use Snap/flatpak/etc.)?
Either build latest QupZilla or wait for new release (which is still waiting for Qt 5.9.2 release). There wasn't any Falkon release yet, so I actually would not recommend to use it as there may be backwards incompatible changes until the first release is made.
According to Qt developers, it is not bug in Qtwebengine. Here is what they said: "I don't see how this could possibly be a problem in WebEngine. WebEngine only renders web content, not the address bar or other UI elements, and Okular does not even use WebEngine. If it works in all normal KDE apps and doesn't work in any snaps, then most likely the problem is either with the packaging of the snaps or snapd. I would suggest following your initial guess and reporting this to KDE neon." Where is the true?
Sorry, I missed the part that it also occurs in text inputs outside of webpages. But sure, if the issue occurs only in snaps then the problem is there and not in Qt.
I have not (yet) tried compiling master, but I have now tried the version in Ubuntu 17.10 (2.1.2, with QtWebEngine version 5.9.1, so not too much older), and all the characters are working.
Just to be clear, I agree that this is an issue with Snaps, or at least the KDE Frameworks 5 Snap, not with Falkon itself.
Changing status. If there is a better place for this (i.e. if the snaps are created by a central tool), please re-assign.
I'd like to check this but I cannot find the Falkon AppImage (QupZilla has one). Where do I find it for Falkon?
(In reply to probono from comment #20) > I'd like to check this but I cannot find the Falkon AppImage (QupZilla has > one). Where do I find it for Falkon? The only release I've seen under the "Falkon" name is the experimental Snap package from Neon. All official releases are still under the QupZilla name.
Hi, using the latest falkon from the Falkon PPA on a kubuntu system, I do not see any issue. So this is defintely a problem with the kde snaps, not with Falkon. If I remember properly neon is ubuntu based, so the debs from the Falkon ppa can probably work just fine there.
Tom can you please confirm this is still an issue with 3.1.0 while not using snaps/appimages/flapaks. If the issue is related to containerisation you'll need to take it up with the packager.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!