Double Commander issues

Double Commander Issues

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.

Regards.

1 Like

gtk2 has been unsupported for a long time now - it was bound to happen at some point

double-commander exist with both qt5 and qt6 versions.

The change to qt6 has been brought in by doublecmd-qt6 providing doublemcd as the qt6 version is to supersede the qt5 version.

Expected to happen

 $ pamac search double commander
doublecmd-qt5  1.1.22-3                                          extra
    twin-panel (commander-style) file manager (Qt5)
doublecmd-qt6  1.1.22-3 [Installed]                              extra
    twin-panel (commander-style) file manager (Qt6)

 $ 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.

Summary

1 Like

Seems like I am not the only one with the keyboard problem, others with Cinnamon have reported the same problems:

https://github.com/doublecmd/doublecmd/issues/2159
https://doublecmd.h1n.ru/viewtopic.php?p=45733#p45733

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ā€¦

You might find something helpful here:

Regards.

1 Like

I have checked with a fully updated default Cinnamon (installed from ISO 240729.

The package provides some - at least to - strange defaults :man_shrugging: but nothing that makes it unusable

I installed the qt5 version - because you mentioned qt5ct

  • no blurred fonts (bold faced text can appear blurred - change to regular font face)
  • input works
  • I expect the input - if not F-key - to jump to cmdline
  • surprise - it is a listing filter mechanism
  • it requires some adjustment of theming
  • kvantum and qt5ct need the personal touch to get themed correct

I replaced the qt5 version with the qt6 version

  • theming appear correct (not light but matching OS theme)
  • the listing filter mechanism appears to be removed or failing
  • the F-keys e.g. view/edit/copy is not working

But this is hardly a Manjaro issue - and should be reported upstream - packaged by Arch Linux by Ike Devolder <ike.devolder@archlinux.org>

ā†’ PKGBUILD Ā· main Ā· Arch Linux / Packaging / Packages / doublecmd Ā· GitLab

As noted before - on Plasma the qt6 version works without issues.

I am guessing it something internal triggered by the Cinnamon GTK backend.

It is possible to download a portable image - Double Commander / Wiki / Download - unpack the archive in your home folder and run it from there.

//EDIT
I tested doublecmd qt6 on Linux Mint where it work without the aforementioned issues.

I canā€™t say why this is so - Manjaro provides the package as part of sync from upstream Arch Linux.

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 :slight_smile: 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 :smile:

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.