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

Ask Fedora
,
1

This only started happening recently.

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

image
image607×113 55.1 KB

and then this happens:

image
image643×112 37.6 KB

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:

image
image604×110 37.9 KB

The same happens with the docx:

(I cannot post another screenshot here, because I get an error saying “An error occurred: Sorry, new users can only put 3 embedded media items in a post.” – see link below to see all the screenshots)

Other times, it works well:

(I cannot post another screenshot here, because I get an error saying “An error occurred: Sorry, new users can only put 3 embedded media items in a post.” – see link below to see all the screenshots)

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

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

Originally reported in KDE Discuss (all screenshots here): Trying to rename a file - the name disappears, replacing with the extension in bold, making it really hard to edit - Help - KDE Discuss

A KDE developer replied:

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

Also reported in: I cannot rename a filename that contains an em-dash - Help - KDE Discuss
And: https://bugs.kde.org/show_bug.cgi?id=517392

All the people in all these links, so far, seem to be using Fedora.
So, it all points that Fedora may have caused this :slight_smile:

Is anyone aware of this? Do you know if this has been confirmed and/or fixed?

Hopefully this can be resolved! If you need anything else from me, please let me know.

Thank you very much!

1 Like
"Plasma Keyboard" can cause various input issues on KDE Plasma 6.6 systems
2

You could try changing the virtual keyboard in the system settings.
Other problems people have with input where fixed when something other then “plasma keyboard” is selected.

1 Like
3

wow…
How does that even work???

I did what you said – right after replicating the problem again, I changed the Virtual Keyboard to “Maliit”.

And now I cannot replicate the problem anymore.
I’m not even using the virtual keyboard!! :scream:

Thank you very much! This bug was really inconvenient to me.

Are Fedora devs aware of this? Will the cause be resolved?

Many thanks, again!

1 Like
4

@ghnp5, likewise: Mallitt does not reproduce this!

5

“Plasma keyboard” is a new piece of software destined to replace “mallit”.
Mallit has it’s own set of known issues. But “plasma keyboard” needs bug fixes to the new code.

1 Like
6

Yes, although as far as I know, if you enable Maliit but don’t actually use it - because you only use a physical keyboard and not the onscreen Maliit - none of the issues should affect you.

Whereas Plasma Keyboard isn’t intended to be just an on-screen keyboard, but also to do useful stuff with physical keyboard input, such as press-and-hold to get special characters. Unfortunately the downside is that bugs can impact you if PK is enabled, even when you’re not knowingly using any of its functionality.

It would be good to raise a bug against the plasma-keyboard component in Bugzilla. Looks like none of the existing listed ones cover this.

2 Likes