I'm a bit lost, 2 mails ago you wrote that the problem started after an update and now you are telling you have not updated anything... If the problem started after an upgrade, then the upgrade is the problem and I have no single idea what can be broken. It is not really possible to guess what you have broken when doing the update. If you can provide a full backtrace of the crash, that could perhaps help. Run gnomemeeting that way : gdb gnomemeeting type 'run' and when it crashes, type 'thread apply all bt' Le mardi 26 octobre 2004 à 23:18 -0200, Antonio Carlos Ribeiro Nogueira a écrit : > My gnomemeeting is closing by itself just after I got connected with someone. > I would like to know how I could get information about what is happening (in > which log should I look for). And I didn't do any upgrade or package update. > Even why Mandrake 10.1 don't have yet the update feature. So what do you > recomend me to do? To reinstall the full Mandrake 10.1 again? But I am afraid > that the problem persists... > Hope someone may help me. > > > Em Seg 25 Out 2004 19:25, Damien Sandras escreveu: > > Hello Giancarlo, > > > > The upgrade has broken some library, but I have no idea which one. > > > > In such a case, there is in general no other way than reinstalling the > > full system :-/ > > > > Le lun 25/10/2004 à 21:45, Giancarlo Sangalli a écrit : > > > Dear Damien, > > > thank you so much for you answer. > > > Actually the problem started after the update done on 10/10/04. It > > > involved the cyrus and pango packages; here is the yum log: > > > > > > 10/10/04 18:44:03 Updated: pango 1.4.1-1.i386 > > > 10/10/04 18:44:03 Updated: cyrus-sasl-plain 2.1.18-2.2.i386 > > > 10/10/04 18:44:03 Updated: cyrus-sasl-devel 2.1.18-2.2.i386 > > > 10/10/04 18:44:03 Updated: pango-devel 1.4.1-1.i386 > > > 10/10/04 18:44:03 Updated: cyrus-sasl 2.1.18-2.2.i386 > > > 10/10/04 18:44:03 Updated: cyrus-sasl-md5 2.1.18-2.2.i386 > > > > > > pango is indeed on the gnomemeeting deps; now, I have just installed the > > > old version of pango (rpm -Uvh --force pango-1.4.0-2 ...) but then X > > > stopped working because of the wrong pango libs.... > > > > > > > > > By the way, I also tryed, days ago, to compile gnomemeeting from the > > > source, in order to be sure that it was linking the present libraries, > > > but still I had a segmentation fault. > > > > > > I there something else I can try? > > > Thanks a lot! Regards, > > > Giancarlo > > > > > > On Mon, 2004-10-25 at 12:16, Damien Sandras wrote: > > > > Hello, > > > > > > > > There can be several reasons to the problem. The conclusion is just > > > > that you are using a broken distribution unable to handle updates > > > > correctly. > > > > > > > > I think that there should be broken dependancies, you will have to > > > > check each of the gnomemeeting RPM deps, and see which one can > > > > potentially be broken... > > > > > > _______________________________________________ > > > GnomeMeeting-list mailing list > > > GnomeMeeting-list gnome org > > > http://mail.gnome.org/mailman/listinfo/gnomemeeting-list > _______________________________________________ > 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?=