[dolphin] [Bug 497666] New: Mallit opening cancels file or folder rename, seemingly making renaming impossible

Ellie bugzilla_noreply at kde.org
Thu Dec 19 00:19:19 GMT 2024


https://bugs.kde.org/show_bug.cgi?id=497666

            Bug ID: 497666
           Summary: Mallit opening cancels file or folder rename,
                    seemingly making renaming impossible
    Classification: Applications
           Product: dolphin
           Version: 24.08.3
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: el at horse64.org
                CC: kfm-devel at kde.org
  Target Milestone: ---

SUMMARY

The Mallit touch keyboard will when opening up cancel the file or folder rename
in dolphin, at least on my machine, seemingly making renaming impossible when
using touch input. This might also concern convertibles and laptops with a
touch screen, not just tablets and such. Sorry if this is just a user error on
my end.

STEPS TO REPRODUCE

1. Enable dolphin's menu bar if not currently enabled, and enable the maliit
touch keyboard in KDE preferences since it seems to be disabled by default
2. Select a file in dolphin
3. Press File > Rename in dolphin's top menu bar, preferably via touch input
4. The file should now be in rename mode with a blinking input cursor. However,
Maliit isn't visible yet.
5. Tap the blinking input cursor with your finger. Maliit will now open.

OBSERVED RESULT

Maliit opening seems to instantly cancel the rename, making it seemingly
impossible to actually enter a new name

EXPECTED RESULT

Maliit opening won't interfere with the ongoing rename

SOFTWARE/OS VERSIONS

Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: postmarketOS 
KDE Plasma Version: 6.2.4
KDE Frameworks Version:  6.8.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list