GNOME Bugzilla – Bug 543748
GUI freeze while hanging up (500 call)
Last modified: 2009-08-25 15:56:11 UTC
hi, When I tried to hang up the 500 call (pushing the red phone button), the GUI freezed, but the video was still running fine... bt: Program received signal SIGINT, Interrupt. [Switching to Thread 0x7f4df96517a0 (LWP 8045)] 0x00007f4df0bd5da2 in select () from /lib/libc.so.6 (gdb) thread apply all bt
+ Trace 203268
Thread 1 (Thread 0x7f4df96517a0 (LWP 8045))
-- This message was broadcast to you by the "daily bug report"...
*** Bug 544691 has been marked as a duplicate of this bug. ***
Is it still reproducable ?
No answer from reporter. That code having been reworked several times by Robert, I can tell it seems to be FIXED. If not, please reopen.
I cannot hang up: calling 500, try to hang up^as soon as the call start. I had to CTRL-C: Program received signal SIGINT, Interrupt. [Switching to Thread 0x7f83ca02b7a0 (LWP 6624)] 0x00007f83c0e1ec76 in poll () from /lib/libc.so.6 (gdb) thread apply fu full_auth_demarshal_in full_auth_free_in full_auth_marshal_in funcs funlockfile@plt futimes full_auth_demarshal_out full_auth_free_out full_auth_marshal_out funlockfile futimens futimesat (gdb) thread apply fu full_auth_demarshal_in full_auth_free_in full_auth_marshal_in funcs funlockfile@plt futimes full_auth_demarshal_out full_auth_free_out full_auth_marshal_out funlockfile futimens futimesat (gdb) thread apply full bt (gdb) thread apply all bt
+ Trace 206601
Thread 15 (Thread 0x40ff5950 (LWP 6784))
Addition to comment #4: the GUI is not freezed anymore. Might be the same symptom, but another issue...
I can reproduce easily only if there is video (h261), and trying to hang up at the moment the video driver is initialising, thus i think it is related to bug #549643 Is this a duplicate?
I have added an artificial 10 seconds delay to open my camera. No way to reproduce.
Yannick, do you still have this issue with recent code?
I think this is fixed with recent code...
http://bugzilla.gnome.org/show_bug.cgi?id=586913 appears to be the same issue, but with slightly more information. Marking as a duplicate, change if you feel this is a different issue. Thanks. *** This bug has been marked as a duplicate of bug 586913 ***