Ralf,

I cannot reproduce the bug here.

Do you use wifi ?

Can you put a breakpoint in NetworkObserver::is_connection_available() ?
and see if it return true or false with unplugged network

Laurent

----- Original Message ----- 
From: "Ralf Schlatterbeck" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; 
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 08, 2008 12:15 PM
Subject: [issue101] Network loss results in freeze & SIP does not 
re-connect]



Ralf Schlatterbeck <[EMAIL PROTECTED]> added the comment:

Now on the X.31 (Debian Etch) *with* Laurents patches.
With unplugged network it takes about 10-15 seconds to start (much longer 
than
with connected network). Then I'm shown the main window with everything
greyed-out (screendump attached), it tries to connect for several seconds 
(in
the status bar I see the orange ball on the terminal symbol move). Then it
segfaults shortly after the orange ball stops moving.

When I run in in gdb, it seems gdb doesn't notice that the program crashed.
Kvats won't refresh the screen when something is moved over it. When I 
switch
virtual desktops and come back to the desktop running kvats, I'm seeing a
completely white window for kvats. This happens only when running inside 
gdb.

I can confirm that I see the same behaviour on my x61s with debian lenny 
with
Laurents patches.

Interesting to note: In the frozen state (white kvats window) when running
inside gdb I'm seeing the following in ps:
10157 pts/1    S      0:05 gdb build/debug/qutecom
10158 pts/1    Zl+    0:00 [qutecom] <defunct>
looks like the qutecom process is dead but gdb didn't notice? The "Z" 
indicates
a zombie process, the "l" that it is multithreaded and the "+" that it's in 
the
foreground process group.

So it seems we're getting a segfault with the new version but gdb can't 
detect
it (maybe because it's in another thread?). Note that pressing ^C in gdb has 
no
effect and I can only get rid of gdb by killing it (then the kvats window 
will
disappear, too).

_____________________________________________
"Kvats.net issue tracker" <[EMAIL PROTECTED]>
<http://tracker.kvats.net/kvats/issue101>
_____________________________________________

_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to