GNOME Bugzilla – Bug 116001
gnomemeeting 0.98 crashes when you try to make the first call
Last modified: 2004-12-22 21:47:04 UTC
Package: gnomemeeting Severity: normal Version: 0.98.0 Synopsis: gnomemeeting 0.98 crashes when you try to make the first call Bugzilla-Product: gnomemeeting Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Steps to reproduce the problem: 1. install 0.98 2. try calling a host via "h323:hostname" 3. a moment later it crashes Actual Results: segfault Expected Results: call gets made How often does this happen? So far once. Additional Information: RedHat 9 ALSA audio drivers (cmi8330) A test was made with the previous version of Gnomemeeting minutes before and it worked just fine. Debugging Information: Backtrace was generated from '/usr/bin/gnomemeeting' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 17772)] [New Thread 32769 (LWP 17811)] [New Thread 16386 (LWP 17812)] [New Thread 32771 (LWP 17813)] [New Thread 49156 (LWP 17839)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x4168d10a in waitpid () from /lib/libpthread.so.0
+ Trace 38190
Thread 1 (Thread 16384 (LWP 17772))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-26 02:46 ------- The original reporter (hugh@toad.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gnomemeeting-maint@bugzilla.gnome.org.
Are you sure that your installation is correct? That is very weird, it is the first bug report of that kind. How did you install? Have you tried to do a gnomemeeting-config-tool --clean ? Can you reproduce it or did it really happen only once?
Also notice that it seems to crash in a gtk_widget_destroy destroying the incoming call popup, but that code didn't change for long...
That was a bug and that has been fixed in 0.98.x. Sorry for not closing it.