Bug 60017

Summary: Hourglass cursor stays after posting a message
Product: [Unmaintained] knode Reporter: Alex Hermann <gaaf>
Component: generalAssignee: kdepim bugs <pim-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Alex Hermann 2003-06-18 20:46:37 UTC
Version:           0.7.6 (using KDE 3.1.9)
Compiler:          gcc version 3.3 (Debian)
OS:          Linux (i686) release 2.4.18-wolk3.8

Pressing the 'Send' button, the hourglass cursor appears, but never returns to the normal arrow after the message is sent.
Comment 1 Teemu Rytilahti 2003-07-13 18:11:22 UTC
It does same to me and it's very annoying.. 
Comment 2 Teemu Rytilahti 2003-09-26 23:59:04 UTC
Still broken in 20030916. Hopefully this will get fixed for 3.2 release... 
Comment 3 Roberto Teixeira 2003-09-29 14:05:11 UTC
tpr, you're going to be very mad but quite honestly, I cannot reproduce it here. :-) 
 
I've just sent several tests and not once did the cursor stay after posting the message. 
Maybe there's something more specific you guys can tell me to reproduce it? I'd really 
like to fix this for 3.2 if you can show me how to reproduce it. 
Comment 4 Teemu Rytilahti 2003-09-29 19:07:44 UTC
I just tried to move knoderc away, but it didn't help.. Is there any other things I could 
test? And then, I think this has been "broken" for a couple of months now.. 
 
But thanks for support and welcome back to develop KNode :) 
Comment 5 Alex Hermann 2003-10-21 17:42:52 UTC
I tried again, still the same. KNode 0.7.6 (Using KDE 3.1.92 (CVS >= 20031019))

The statusbar shows 'Loading folder...' instead of 'Ready' after sending the message. I tried it on 3 different servers, all the same.
Comment 6 Emond Papegaaij 2004-04-28 00:14:10 UTC
I think I managed to get rid of this bug by removing the .idx and .info files in .kde/share/apps/knode/folders. Maybe one of these files got corrupted?
Comment 7 Alex Hermann 2004-04-28 10:35:39 UTC
The solution from Emond Papegaaij solved the issue for me too.
I mark this bug as resolved.

Alex.