Sadly, with this update doublecmd-gtk2 was removed from the Official Repositories (extra) and an automatic update to doublecmd-qt6 happened.
The problems are, for one, the horribly blurred fonts, but even worse is that the QT version does not take any keyboard input, only mouse.
So I downgraded back to the Gtk version for now. Any ideas how fix the QT problems (I am using Cinnamon), or if the Gtk version was removed by mistake and is coming back?
Have you tried Krusader as a potential replacement? Thereās also Total Commander or even Midnight Commander that might be worth some consideration.
Note that your posts have been moved to a dedicated topic, as they are not directly related to an update. Here, others might share information they may have regarding any changes to Double Commander.
These changes may have coincided with the update but were no doubt upstream decisions, and out of Manjaroās control.
$ pamac info doublecmd-qt6
Name : doublecmd-qt6
Version : 1.1.22-3
Description : twin-panel (commander-style) file manager
(Qt6)
URL : http://doublecmd.sourceforge.net/
Licenses : GPL-2.0-or-later LGPL-2.0-or-later MIT
MPL-1.1 MPL-2.0 Apache-2.0 BSD-2-Clause Zlib
Repository : extra
Installed Size : 45,0 MB
Groups : --
Depends On : qt6pas desktop-file-utils hicolor-icon-theme
shared-mime-info
Optional Dependencies : lua: scripting [Installed]
unzip: support extracting zip archives [Installed]
zip: suport packing zip archives [Installed]
p7zip: support for 7zip archives [Installed]
libunrar: support for rar archives
imagemagick: preview xcf files [Installed]
ffmpegthumbnailer: preview video files
mplayer: to make use of the wlxmplayer plugin
Required By : --
Optional For : --
Provides : doublecmd
Replaces : --
Conflicts With : doublecmd-gtk2 doublecmd-qt5
Packager : Ike Devolder <ike.devolder@archlinux.org>
Build Date : man 27 jan 2025 09:51:32 CET
Install Date : lĆør 15 feb 2025 11:11:14 CET
Install Reason : Explicitly installed
Validated By : Signature
Backup files : --
As you were explicitly referring to the removal of the gtk2 version - I think your issue is related to your themeās support for qt application.
You should consider updating your theme.
I disagree with your assessment - using double commander on plasma 6 works nicely - including keyboard input.
I will wait a bit if it get fixed, otherwise I could live with the mentioned work-around.
However, not sure how to address the blurry fonts. The decorations/design at first startup did not work at all for me (it needs to look like the other Cinnamon apps, not like Plasma). I made changes with the āQT5 Settingsā app so Double Commander properly integrates - except for the blurry fontsā¦
So your Qt5 test was flawlessā¦ As mentioned in https://doublecmd.h1n.ru/viewtopic.php?p=45733#p45733 , the root issue seems to be whether the virtual keyboard is activated in Cinnamon SystemSettings/Accessibility/Keyboard/Enable the on-screen keyboard. Which was in my case too, and I have some reason for this. Did you test what happens when you switch this on/off? I had lost all of the keyboard in Double Commander, including āspaceā, ātabā and cursor keys.
I installed the minimal cinnamon in virtual machine.
I didnāt think it was necessary - now I did it gives a direction - the developer(s) of double commander should be able to navigate further into the issue.
Enable / disable the virtual keyboard in accessibility - made the keypresses functional in th qt6 version. This tells me that a setting in the configuration was altered
I tried removing local dconf settings and doublecmd settings
rm -r ~/.config/dconf ~/.config/doublecmd
And this made keyboard work OOB using the qt6 version.
This makes me think that somewhere the doublecmd reads a dconf setting which controls how keyboard is working.
Read this with a
This points to a setting in Cinnamon - it may not be an obvious one - but it is one that the doublecmd developers didnāt see as an issue - perhaps even thought of making an issue.
I say so because I am a developer and I am dealing with endusers regularly when I am being debriefed on the project.
Believe me - endusers do not think like developers - and endusers do things developers didnāt think of - I think this is one of such cases - endusers can do things in the OS which affects double commander qt6 in a way the developer(s) didnāt even think was possible.