Bug 105739

Summary: File dialog resets mouse status prematurely.
Product: [Applications] kfile Reporter: Dylan Griffiths <dylang>
Component: generalAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: nate
Priority: NOR Keywords: triaged
Version: unspecified   
Target Milestone: ---   
Platform: Slackware   
OS: Linux   
Latest Commit: Version Fixed In:

Description Dylan Griffiths 2005-05-16 03:09:37 UTC 
Version:           2.4 (using KDE KDE 3.4.0)
Installed from:    Slackware Packages
Compiler:          gcc 3.4.3 64-bit
OS:                Linux

When I hit ctrl+s in Kate, it properly sets the mouse cursor to busy.  This is done on an NFS folder that has quite a few files and takes a few seconds to read, so this makes sense.

Then the save dialog appears and the mouse cursor status is reset.  Unfortunately, the dialog is *still busy* and will not respond to input for another few seconds.  It should not reset the mouse cursor status until it is ready to accept input.

Also, despite me hitting ctrl+s over again, Kate still takes about 8-10s on 3000+ AMD64 w/ lots of RAM to redisplay the same NFS directory (each time).  There is obviously some sort of caching bug here, I'm just not sure if it's in the 2.6.11 kernel or in Kate/KDE.
Comment 1 Christoph Cullmann 2005-10-31 10:17:26 UTC 
That's a kfiledialog problem
Comment 2 Christoph Feck 2009-08-27 02:36:20 UTC 
Moving from "kio/kfile" component to "kfile" product, helps sorting out duplicates.
Comment 3 Nate Graham 2018-04-11 20:39:35 UTC 
Is this still an issue in KDE Frameworks 5?
Comment 4 Andrew Crouthamel 2018-09-28 03:09:54 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-28 03:35:31 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!