Would it be possible for you to send a backtrace of the druid assistant
test crash?
Also are you using OSS or ALSA? Some OSS drivers are problematic with
full-duplex. It will be impossible to close/read/write from them,
resulting in the kind of freeze you are describing.
Le mer, 07/07/2004 à 16:14 +0200, JC Castellani a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> [This message is in 2 langages: english first, and french then (my
> native langage)]
>
> Hello !
>
> I have a problem with GnomeMeeting, and the error message is not clear
> for me (neither for Google).
> First, i want to say that i'm on Debian Unstable, but the problem is the
> same on Debian Testing (i have passed on unstable with hope that the
> problem would be solved, but it's not the case).
>
> So, when i start GnomeMeeting on my user session, it freeze when i want
> to make the tests for the audio devices in the assistant. I have to
> kill GnomeMeeting process to quit. With an other user session, there is
> no problem. With root session, no problem too.
> I have started GnomeMeeting with debug command: This is the result:
>
> [marmotte @ bourriquet] (~)
> $ gnomemeeting -d 4
> Bonobo accessibility support initialized
> GTK Accessibility Module initialized
> 2004/07/06 16:35:49.013 0:02.196 gnomemeeting Set TCP
> port range to 3000030010
> 2004/07/06 16:35:49.026 0:02.235 gnomemeeting Set RTP
> port range to 50005007
> 2004/07/06 16:35:49.062 0:02.271 gnomemeeting Set UDP
> port range to 50105013
> 2004/07/06 16:35:50.740 0:03.921 gnomemeeting H323
> Added capability: iLBC-13k3{sw} <1>
> 2004/07/06 16:35:50.752 0:03.974 gnomemeeting H323
> Added capability: iLBC-15k2{sw} <2>
> 2004/07/06 16:35:50.802 0:04.013 gnomemeeting H323
> Added capability: SpeexNarrow-15k{sw} <3>
> 2004/07/06 16:35:50.845 0:04.059 gnomemeeting H323
> Added capability: SpeexNarrow-8k{sw} <4>
> 2004/07/06 16:35:50.890 0:04.102 gnomemeeting H323
> Added capability: MS-GSM{sw} <5>
> 2004/07/06 16:35:50.935 0:04.147 gnomemeeting H323
> Added capability: G.711-uLaw-64k{sw} <6>
> 2004/07/06 16:35:50.975 0:04.156 gnomemeeting H323
> Added capability: G.711-ALaw-64k{sw} <7>
> 2004/07/06 16:35:50.976 0:04.156 gnomemeeting H323
> Added capability: GSM-06.10{sw} <8>
> 2004/07/06 16:35:50.976 0:04.157 gnomemeeting H323
> Added capability: G.726-32k{sw} <9>
> 2004/07/06 16:35:50.976 0:04.157 gnomemeeting H323
> FindCapability: "G.723.1"
> 2004/07/06 16:35:50.977 0:04.158 gnomemeeting H323
> Added capability: H.261-QCIF <10>
> 2004/07/06 16:35:50.978 0:04.158 gnomemeeting H323
> Added capability: H.261-CIF <11>
> 2004/07/06 16:35:50.978 0:04.159 gnomemeeting H323
> Added capability: UserInput/hookflash <12>
> 2004/07/06 16:35:50.979 0:04.159 gnomemeeting H323
> Added capability: UserInput/basicString <13>
> 2004/07/06 16:35:50.979 0:04.159 gnomemeeting H323
> Added capability: UserInput/dtmf <14>
> 2004/07/06 16:35:50.979 0:04.160 gnomemeeting H323
> Added capability: UserInput/RFC2833 <15>
> 2004/07/06 16:35:50.985 0:04.165 gnomemeeting H323
> Started listener Listener[ip$*:1720]
> 2004/07/06 16:35:50.985 0:04.166 H323 Listener:8360c08 H323
> Awaiting TCP connections on port 1720
> 2004/07/06 16:35:50.985 0:04.166 H323 Listener:8360c08 TCP
> Waiting on socket accept on ip$*:1720
> 2004/07/06 16:35:51.426 0:04.606 H323 Listener:8360c08 H323TCP
> Started connection: host=213.193.144.104:50572, if=80.8.172.193:1720,
> handle=45
> 2004/07/06 16:35:51.426 0:04.607 H323 Listener:8360c08 TCP
> Waiting on socket accept on ip$*:1720
> 2004/07/06 16:35:51.462 0:04.647 H225 Answer:8385da8 H225
> Started incoming call thread
> 2004/07/06 16:35:51.467 0:04.647 H225 Answer:8385da8 H225
> Awaiting first PDU
> 2004/07/06 16:35:51.468 0:04.648 H225 Answer:8385da8 H225
> Read error (0):
> 2004/07/06 16:35:51.468 0:04.648 H225 Answer:8385da8 H225
> Failed to get initial Q.931 PDU, connection not started.
>
> I don't understand the last 2 rows. Can you help me ?
> Thanks !
>
>
>
> ****************************
> [version française]
> Sous ma session d'utilisateur normal, GnomeMeeting se freeze à chaque
> fois que je veux faire le test audio de l'assistant, et je doit le
> "killer" pour le fermer. Celà ne se produit pas sous la session d'un
> autre utilisateur, ou même root.
> J'ai donc lancer GnomeMeeting avec débugage pour avoir plus d'info, mais
> le message d'erreur ne me donne pas plus d'info, ni à Google d'ailleurs.
> Est-ce que quelqu'un a un indice de réponse SVP ?
> Merci d'avance.
>
> Je suis sous Debian unstable, mais le problème était présent quand
> j'étais en testing (je suis passé en unstable en espérant que la
> nouvelle version de GnomeMeeting résolve le problème).
>
> Voici la trace du débugage, l'erreur est à la dernière ligne. Quand je
> lance le test, aucune ligne supplémentaire ne s'affiche dans la console,
> ce qui me fait penser que le problème vient de cette dernière ligne.
> (cf debug ci-dessus).
> Je ne comprends pas les 2 dernières lignes. Quelqu'un pourrait m'aider ?
>
> Merci d'avance !
>
>
> - --
> Cordialement,
>
> Jean-Charles Castellani
> Jabber ID: marmotte amessage info
> GPG fingerprint: 3A12 BB75 447F 6F6F FE53 C2B3 C398 3331 A277 95C6
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFA7AUkw5gzMaJ3lcYRAmtxAKDFF6tzXOuW9+w9J4n7BwstASlPMACeOM4b
> q2N0EPsJkLGyGWrbLGiuXfY=
> =ZXHm
> -----END PGP SIGNATURE-----
> _______________________________________________
> GnomeMeeting-list mailing list
> GnomeMeeting-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
--
_ Damien Sandras
(o- GnomeMeeting: http://www.gnomemeeting.org/
//\ FOSDEM : http://www.fosdem.org
v_/_ H.323 phone : callto:ils.seconix.com/dsandras seconix com
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=