Bug 33217 - timeout connecting to server then crashes
Summary: timeout connecting to server then crashes
Status: RESOLVED WORKSFORME
Alias: None
Product: knode
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 33611 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-10-02 14:18 UTC by Gavin Wing
Modified: 2004-04-05 12:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gavin Wing 2001-10-02 14:05:54 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           knotes
Version:           KDE 2.2.1 
Severity:          normal
Installed from:    RedHat RPMs
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

I am running RH7.1 and used knote ok until I upgraded to kde2.2.1 now it just say's connecting to server but never makes the connection then after a while it just hangs (can't close app) and have to use xkill to close it. I have deleted the ~/.kde/share/knote dir to see it this would help but no go.

(Submitted via bugs.kde.org)
Comment 1 Michael Brade 2001-10-02 21:51:02 UTC
On Tuesday 02 October 2001 16:05 you wrote:
> Package: knotes
> Version: KDE 2.2.1
> Severity: normal
> Installed from:    RedHat RPMs
> Compiler:          Not Specified
> OS:                Linux
> OS/Compiler notes: Not Specified
>
> I am running RH7.1 and used knote ok until I upgraded to kde2.2.1 now it
> just say's connecting to server but never makes the connection then after
> a while it just hangs (can't close app) and have to use xkill to close it.
> I have deleted the ~/.kde/share/knote dir to see it this would help but no
> go.
I guess you mean knode ;) I'll reassign this bug.

Ciao
 Michael

-- 

       Some operating systems are called `user friendly'
             Linux however is `expert friendly'.
Comment 2 Gavin Wing 2001-10-03 07:03:42 UTC
On Tuesday 02 October 2001 23:51 you wrote:
> On Tuesday 02 October 2001 16:05 you wrote:
> > Package: knotes
> > Version: KDE 2.2.1
> > Severity: normal
> > Installed from:    RedHat RPMs
> > Compiler:          Not Specified
> > OS:                Linux
> > OS/Compiler notes: Not Specified
> >
> > I am running RH7.1 and used knote ok until I upgraded to kde2.2.1 now it
> > just say's connecting to server but never makes the connection then
> > after a while it just hangs (can't close app) and have to use xkill to
> > close it. I have deleted the ~/.kde/share/knote dir to see it this would
> > help but no go.
>
> I guess you mean knode ;) I'll reassign this bug.

Sorry I realised my typo after I had sent the bug report.

>
> Ciao
>  Michael

-- 
Gavin Wing
IS Admin/Tech Support
---------------------
The Box said: "Requires Windows95 or better ..." So I installed Linux.
---------------------
Microsoft gives you Windows
Linux gives you the whole house
---------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review re-transmission dissemination or other use of or
taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error please contact the sender and delete the material from any
computer.
---------------------
Comment 3 Ian Jones 2001-10-07 01:28:09 UTC
I can confirm this behaviour on my installation.
I upgraded RH7.1 (with all vendor updates) to KDE 2.2.1 using the RPM's in 
RedHat-unofficial. My KDE version is listed as 2.2.1-0.rh71.1.cups

knode appears to freeze on any network access attempt. The first time I ran 
knode after the upgrade it migrated data from an earlier version of knode (I 
did not tell it to create backups during the conversion) and when I attempted 
to refresh my groups list I got an application lockup. The same happens if I 
delete the server profile and attempt to fetch a group listing.

tcpdump shows a successful three-way handshake which is stalled waiting for 
knode to respond:

18:22:05.737401 eth0 > 192.168.1.1.1142 > 192.168.1.100.nntp: S 
3758550627:3758550627(0) win 5840 <mss 1460sackOKtimestamp 278140 
0nopwscale 0> (DF) (ttl 64 id 53279)
                         4500 003c d01f 4000 4006 e6e6 c0a8 0101
                         c0a8 0164 0476 0077 e006 ee63 0000 0000
                         a002 16d0 9ba9 0000 0204 05b4 0402 080a
                         0004 3e7c 0000 0000 0103 0300
18:22:05.737401 eth0 < 192.168.1.100.nntp > 192.168.1.1.1142: S 
3753781549:3753781549(0) ack 3758550628 win 5792 <mss 1460sackOKtimestamp 
54132775 278140nopwscale 0> (DF) (ttl 64 id 0)
                         4500 003c 0000 4000 4006 b706 c0a8 0164
                         c0a8 0101 0077 0476 dfbe 292d e006 ee64
                         a012 16a0 8f7b 0000 0204 05b4 0402 080a
                         033a 0027 0004 3e7c 0103 0300
18:22:05.737401 eth0 > 192.168.1.1.1142 > 192.168.1.100.nntp: . 1:1(0) ack 1 
win 5840 <nopnoptimestamp 278141 54132775> (DF) (ttl 64 id 53280)
                         4500 0034 d020 4000 4006 e6ed c0a8 0101
                         c0a8 0164 0476 0077 e006 ee64 dfbe 292e
                         8010 16d0 be0f 0000 0101 080a 0004 3e7d
                         033a 0027
18:22:05.767404 eth0 < 192.168.1.100.nntp > 192.168.1.1.1142: P 1:61(60) ack 
1 win 5792 <nopnoptimestamp 54132779 278141> (DF) (ttl 64 id 10505)
                         4500 0070 2909 4000 4006 8dc9 c0a8 0164
                         c0a8 0101 0077 0476 dfbe 292e e006 ee64
                         8018 16a0 256c 0000 0101 080a 033a 002b
                         0004 3e7d 3230 3020 4c65 6166 6e6f 6465
                         204e 4e54 5020 4461 656d 6f6e 2c20 7665
                         7273 696f 6e20 312e 392e 3137 2072 756e
                         6e69 6e67 2061 7420 6261 7266 6c79 0d0a
18:22:05.767404 eth0 > 192.168.1.1.1142 > 192.168.1.100.nntp: . 1:1(0) ack 61 
win 5840 <nopnoptimestamp 278144 54132779> (DF) (ttl 64 id 53281)
                         4500 0034 d021 4000 4006 e6ec c0a8 0101
                         c0a8 0164 0476 0077 e006 ee64 dfbe 296a
                         8010 16d0 bdcc 0000 0101 080a 0004 3e80
                         033a 002b
Comment 4 Mek Buhl Nielsen 2001-11-01 11:31:56 UTC
Hi

I too can confirm the behavior. I have the same RH7.1 KDE2.2.1 build and the 
same problem.

cheers
Mek
Comment 5 Cp Hennessy 2002-09-25 02:45:05 UTC
The last update to this bug report was nearly a year ago.  
Can you please give us an updated on whether this is still a problem for you  
with a more recent version of knode?  
If it is not a problem - the status of this bug report will be changed to closed.  
 
Comment 6 Cp Hennessy 2002-09-30 01:41:32 UTC
*** Bug 33611 has been marked as a duplicate of this bug. ***
Comment 7 Rainer Endres 2004-04-05 12:30:11 UTC
I close this bug since this seems to be fixed. I think not being able to connect to the network would be report more than this. All reports were specific to KDE 2.2.1

	Rainer