Bug 173 - WR can't handle broken network connections
Status:
RESOLVED FIXED
Component:
Core
Version:
1.0.0
Hardware:
PC Windows 2000
Importance:
P3 normal
Target Milestone:
---
Assignee:
Rob Caelers
URL:
Depends on:
Blocks:
Reported:
Jan 15 2003 03:37:33 UTC
by:
Kees-Jan Dijkzeul
Modified:
Jan 27 2003 06:24:07 UTC
WhoWhenWhatRemovedAdded
Rob CaelersJan 25 2003 14:32:33 UTCstatusNEWRESOLVED
resolutionFIXED
Description
Kees-Jan Dijkzeul  Jan 15 2003 03:37:34 UTC
Testcase:
Have two instances of wr running on different pc's. Shut down the pc on which
you are currently active. Start working on the other pc.

Expected result:
WR detects that you are active and starts timers. In some cases (unplugged
network cables, instead of proper shutdown), it may be acceptable to use older
values for the timers, instead of current ones.

Actual result:
The WR main window keeps showing "inactive" and otherwise does nothing. WR needs
to be quit and restarted in order to recover.
Comment 1
Rob Caelers  Jan 25 2003 14:32:33 UTC
It seems that when you disconnect the network clable, Linux closes the
connection after about 15 minutes...I added some pinging. Connection is now
closes after about 1 minute.
Comment 2
Kees-Jan Dijkzeul  Jan 27 2003 01:18:06 UTC
???
I don't understand this remark. This was on my two laptops, one running W XP,
one running W ME. No Linux involved :-(
Comment 3
Rob Caelers  Jan 27 2003 06:24:07 UTC
I don't have two Windows boxes available at home. I reproduced your bug by
removing the network cable between 2 linux boxes. It took linux about 15 linux
to report this to workrave...I assume windows is no better...So I added some
pinging. Workrave will now close the connection way before 15 minutes.