Trying to rename a file - the name disappears, replacing with the extension in bold, making it really hard to edit

This only started happening recently.

I often try to edit a file name, example files:

and then this happens:

And it’s really hard/impossible to edit the file name when it gets to this state.

If I do nothing and leave the editing, the file name actually becomes like that:

The same happens with the docx:

Other times, it works well:

I really can’t understand what causes this, and why sometimes it works.

2 Likes

What OS?
X11 or Wayland?
Basically sysinfo is always helpful

Sorry - completely forgot!

Operating System: Fedora Linux 43
KDE Plasma Version: 6.6.2
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 6.19.7-200.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3050
Manufacturer: PC Specialist LTD
Product Name: PRIME Z370-P

1 Like

Isn’t Fedora using LTO/PGO compilation option ?

That wouldn’t be the first time it introduces a bug in our software.

Looking at the screenshot that’s a very broken UI, we can see with invalid state drawn.

I haven’t been able to reproduce this so far (on Arch).

Thanks! This may be related, actually: I cannot rename a filename that contains an em-dash

Looks like the OP is also on Fedora.

At the end, there’s this link to this bug: https://bugs.kde.org/show_bug.cgi?id=517392

What you say about this being a bug caused by Fedora makes sense.

Do you have any idea if this has been reported to Fedora? Bugzilla is always very hard to use, every time I try. I tried searching for “kde rename”, but it shows no results… :slight_smile:

Many thanks!

2 Likes

Posted here: KDE - Trying to rename a file - the name disappears, replacing with the extension in bold, making it really hard to edit - Fedora Discussion

Hopefully this can be resolved!

wow…

as suggested by someone in that Fedora Discussion topic, a quick “fix” for this is to change the Virtual Keyboard to some that is not the Plasma Keyboard.

That fixed it immediately for me! :partying_face:

Now - I hope they can resolve the actual cause of the bug :grin: