Version: (using KDE 4.4.3) OS: Linux Installed from: openSUSE RPMs Guys, There has been a regression in the file-saveas dialog behavior for .jpg files and a new bug introduced that moves the cursor to the end of the filename edit field when you change any character in the filename if the filename has a .jpg extension. I have captured a series of 3 screenshots that captures the exact problem: (45k each) http://www.3111skyline.com/dl/bugs/kde4/file-saveas-1.jpg http://www.3111skyline.com/dl/bugs/kde4/file-saveas-2.jpg http://www.3111skyline.com/dl/bugs/kde4/file-saveas-3.jpg (attached as .tar.gz later) file-saveas-1, just shows the initial state of the file-saveas dialog for ksnapshot. file-saveas-2 show the click of the cursor between the '1' and the '.' so I can backspace over the last char of the filename and change it to '2' (or whatever) file-saveas-3 shows the regression and bug. If you have previously taken a screenshot and saved with the extension .jpg when you backspace over 'any' character in the filename, (1) the extension automatically changes from .jpg to .jpeg (the regression, initially fixed in 4.3 beta), and frustratingly (2) the cursor position is moved to the end of the filename (the end of .jpeg). This causes you to have to completely reset the cursor position so you can continue to modify the filename. GRRrrr... This behavior is wrong. When the cursor is in the position shown in 'file-saveas-2.jpg' and you backspace over the '1', the extension should NOT change from .jpg to .jpeg (regardless of the automatic extension checkbox) and the cursor should NOT be magically moved to the far end of the filename as shown in 'file-saveas-3.jpg' Let me know if I can send anything else. This bug bites me every time I take a screenshot now. There were no problems from the time the .jpg -> .jpeg issue was fixed the first time, (it's been about a year ago). This bug was introduced (re-introduced) in 4.4.3. Keep the faith and keep up the good work :p
Created attachment 43703 [details] All 3 screenshots referenced in the bug report.
not a plasma bug
(In reply to comment #2) > not a plasma bug OK, where dos it belong? Also, I have confirmed this bug is present in 4.4 as well.
> OK, where dos it belong? > kdelibs (the old "read below stupid" :p)-- got it, thanks!
*** Bug 287065 has been marked as a duplicate of this bug. ***
So the bug reported in november, 2011 is a duplicate of the bug reported in may, 2010... That looks like an easy one. Oh wait... I've been a KDE user for 10+ years, and that's the thing that frustrates me most : the commitment of the KDE team to develop new, often useless, gadgets, rather than fixing known existing bugs...
I'm not able to reproduce this issue with KDE Frameworks 5.45.