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 131436 - Crashes on startup
Crashes on startup
Status: VERIFIED DUPLICATE of bug 122183
Product: ekiga
Classification: Applications
Component: Documentation
0.98.5
Other other
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
: 135996 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-01-14 11:41 UTC by Alan Miller
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alan Miller 2004-01-14 11:41:09 UTC 
Distribution: SuSE Linux 8.2 (i586)
Package: gnomemeeting
Severity: normal
Version: GNOME2.4.1 0.98.5
Gnome-Distributor: GNOME.Org
Synopsis: Crashes on startup
Bugzilla-Product: gnomemeeting
Bugzilla-Component: Documentation
Bugzilla-Version: 0.98.5
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:

gnomemeeting crashes at startup.

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

Expected Results:


How often does this happen?
everytime app is started

Additional Information:



Debugging Information:

Backtrace was generated from '/opt/gnome/bin/gnomemeeting'

[New Thread 16384 (LWP 3886)]
[New Thread 32769 (LWP 3931)]
[New Thread 16386 (LWP 3932)]
[New Thread 32771 (LWP 3933)]
0x41ba0d2a in waitpid () from /lib/libpthread.so.0

+ Trace 43214

Thread 1 (Thread 16384 (LWP 3886))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 GMH323EndPoint
    at endpoint.cpp line 197
  • #5 GnomeMeeting::InitComponents()
    at gnomemeeting.cpp line 406
  • #6 main
    at main_window.cpp line 1748
  • #7 __libc_start_main
    from /lib/libc.so.6
  • #0 waitpid
    from /lib/libpthread.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-01-14 06:41 -------

Reassigning to the default owner of the component, gnomemeeting-maint@bugzilla.gnome.org.
Comment 1 Damien Sandras 2004-01-14 11:48:47 UTC 
Hello, how did you install it and how?
Comment 2 Damien Sandras 2004-01-14 11:49:28 UTC 
(I meants what, not how).

At first sight, it seems taht your GConf schemas are not installed and
that causes the crash.
Comment 3 Alan Miller 2004-01-14 12:00:47 UTC 
1. Upgraded system to gnome 2.4
   (rpms from
http://www.suse.de/de/private/download/gnomes/i386/update_for_8_2/index.html)

2. Then Upgraded packages:
   gnomemeeting-0.98.5-4.i586.rpm
   openh323-1.12.3-4.i586.rpm
   pwlib-1.5.3-5.i586.rpm
Comment 4 Damien Sandras 2004-01-14 12:04:34 UTC 
I don't have 0.98.5 at hand anymore, but checking if GConf is
correctly installed should be straightforward :
- Did you have to change the value of a GConf key to force its startup?
- What is the result of gconftool-2 -g
/apps/gnomemeeting/port/tcp_port_range ?
Comment 5 Alan Miller 2004-01-14 12:21:15 UTC 
I didn't change/update any "keys" to my knowledge.
To be honest I'm not sure what your referring to.
I just rpm -Uhv the gnome2.4 packages to get things working
and then ran ldconfig && SuSEconfig.

Also not farmiliar with gconf2 but here's the output.

[alan@linux]  gconftool-2 -g /apps/gnomemeeting/port/tcp_port_range  
                                                    
No value set for `/apps/gnomemeeting/port/tcp_port_range'

[alan@linux]  gconftool-2 --all-dirs /apps/gnomemeeting
 /apps/gnomemeeting/general
 /apps/gnomemeeting/call_forwarding
 /apps/gnomemeeting/audio_codecs
 /apps/gnomemeeting/devices
Comment 6 Damien Sandras 2004-01-14 12:29:51 UTC 
ok, so that is indeed a misconfiguration problem. I suggest you to use
the mailing list to get help, I have never used SuSE, so I can't
really help with it.
Comment 7 Damien Sandras 2004-01-14 12:31:15 UTC 

*** This bug has been marked as a duplicate of 122183 ***
Comment 8 Alan Miller 2004-01-14 12:45:59 UTC 
Okay· Thanks for pointing me in the right direction.
I've located the suse install-schema scripts and will adjustment them.
Comment 9 Damien Sandras 2004-03-02 19:08:14 UTC 
*** Bug 135996 has been marked as a duplicate of this bug. ***