After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 129111 - gnomemeeting segfaults after first time druid window comes up
gnomemeeting segfaults after first time druid window comes up
Status: RESOLVED DUPLICATE of bug 122183
Product: ekiga
Classification: Applications
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2003-12-11 19:18 UTC by Alex
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alex 2003-12-11 19:19:07 UTC
Distribution: Red Hat Linux release 8.0 (Psyche)
Package: gnomemeeting
Severity: normal
Version: GNOME2.4.1 unspecified
Gnome-Distributor: GARNOME
Synopsis: gnomemeeting segfaults after first time druid window comes up
Bugzilla-Product: gnomemeeting
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.0.3)
Description:
Description of the crash:

Just installed gnomemeeting 0.98.5 (using plib (pwlib-1.5.2)  and
openh323 (openh323-1.12)  tarballs from the gnomemeeting site).  when
run, the first time druid window begins to come up, and then the
application segfaults.



Steps to reproduce the crash:
1. run gnomemeeting
2. 
3. 

Expected Results:


How often does this happen?
every time

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/local/gnome-2.4.0/bin/gnomemeeting'




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-12-11 14:19 -------

The original reporter (spam@skander.net) 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.

Comment 1 Damien Sandras 2003-12-11 19:52:42 UTC
Please give a backtrace. I see you are using a different prefix for
the installation, I'm nearly sure your GConf schemas are badly installed.
Did you have to force a specific value for a given GConf key to make
GnomeMeeting start?
Comment 2 Alex 2003-12-12 13:39:38 UTC
Hi,

I'm new to the bug sumission process.  Could you point me to some docs
on how to get you a backtrace?

> Did you have to force a specific value for a given GConf key to make
> GnomeMeeting start?

No.

The alternate prefix is a result of gnomemeeting being installed as
part of garnome (version 0.27.1).

--Alex
Comment 3 Damien Sandras 2003-12-12 13:47:42 UTC
ok then I know what the problem is. It is not GnomeMeeting. Please
check the duplicate bug report and comments at the end, including
comments from Matthieu Lacage.
Comment 4 Damien Sandras 2003-12-12 13:48:40 UTC

*** This bug has been marked as a duplicate of 122183 ***