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 116893 - mysterious segfaults from various gtk2 applications while idle; appears to be threading related
mysterious segfaults from various gtk2 applications while idle; appears to be...
Status: RESOLVED DUPLICATE of bug 107007
Product: gtk+
Classification: Platform
Component: .General
2.2.x
Other Linux
: High critical
: ---
Assigned To: gtk-bugs
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2003-07-07 15:35 UTC by Jeff MacDonald
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description Jeff MacDonald 2003-07-07 15:35:42 UTC
Package: gnomemeeting
Severity: major
Version: 0.96.0
Synopsis: segfault in gnome meeting while idle
Bugzilla-Product: gnomemeeting
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
without provocation, gnome meeting crashed. I was doing other things on
the workstation when the dialog box appeared. I do not have video or
microphone hardware installed, however that is configured. I am using
Red Hat Linux 9 after an upgrade from Pink Tie Linux 8.0. as far as I
know, I have configured everything properly.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?
needs additional testing

Additional Information:
I will be willing to provide further information regarding my setup,
however I would like to contact someone in such a way that I can encrypt
the files for trasmission over the network, and I would like it if my
sensitive information could be protected from the general public. this
is so that I don't need to doctor logs, and I can feel free to give you
*everything*.




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)...[New
Thread 1099900384 (LWP 2149)]
[New Thread 1142127920 (LWP 2165)]
[New Thread 1133735216 (LWP 2162)]
[New Thread 1125342512 (LWP 2161)]
[New Thread 1116949808 (LWP 2160)]
0xffffe002 in ??
    ()

Thread 1 (Thread 1099900384 (LWP 2149))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_widget_get_toplevel
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 gtk_false
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 g_main_dispatch
    at gmain.c line 1653
  • #8 g_main_context_dispatch
    at gmain.c line 2197
  • #9 g_main_context_iterate
    at gmain.c line 2278
  • #10 g_main_loop_run
    at gmain.c line 2498
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-07 11:35 -------

Reassigning to the default owner of the component, gnomemeeting-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-07-07 17:45:32 UTC
I believe this is a duplicate of bug 107007, which is a "random" gtk
crash.  Since you're using RedHat 9, can you please install
  http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm
and if the problem occurs again, submit the backtrace you get. 
Installing the debuginfo package will make the backtrace much more
useful and will help the developers track down the real problem (There
is a similar random gdk crash in bug 105745 that the developers were
only able to solve after someone sent in a stack trace with debugging
symbols several months after people started seeing crashes).

Note that we are interested in the backtrace regardless of the
application--the other people in bug 107007 received crashes in
nautilus, gnome-terminal, and gnome-panel.  So it could be just about
any application.

I'm marking as needinfo for now.
Comment 2 Jeff MacDonald 2003-07-08 11:56:40 UTC
this bug has been updated to track problems that I am having with
various gtk2 based tools. 

the stack trace already attached to this bug shows that gnome meeting
crashed, and in addition that threading was somehow involved. at this
point I suspect a problem in one of the other layers, not gnomemeeting
itself.

I have added keyword 'bugbuddy' to this bug so it will show up
immediately in a list should there be any other crashes. I need some
assistance in determining the right component to file this bug for so
that it will be noticed by other people having this problem.

Comment 3 Elijah Newren 2003-07-08 15:01:40 UTC
I'm pretty sure that this is a duplicate of bug 107007 (it's just that
I've had a pretty bad record at correctly identifying gtk+ duplicates,
so I tend to not mark them unless they're identical).  So I'm going to
reopen so that I can reassign this bug to the gtk maintainers so they
can decide for sure.

Also, since many more duplicates are in bug 107007, it (and perhaps
bug 105745 as well) should have the bugbuddy keyword, not this bug. 
I'll set priority and severity appropriately and set the GNOMEVER2.2
and bugsquad keywords.

Finally, did you install the debuginfo package, Jeff?  A stack trace
with debugging symbols would be really nice...
Comment 4 Elijah Newren 2003-07-08 15:02:16 UTC
...and now I'm reassign to gtk maintainers so they can determine if
this is a dup of bug 107007 and what to do with it.
Comment 5 Owen Taylor 2003-07-08 15:13:20 UTC
Duping. I'm actually pretty sure 107007 is itself a duplicate
of something I've investigated elsewhere, but couldn't
find it in a quick look.


*** This bug has been marked as a duplicate of 107007 ***
Comment 6 Jeff MacDonald 2003-07-09 07:11:29 UTC
hi,

no, I haven't installed the debuginfo package.. is it officially
distributed by redhat, or do I have to check other sources? I'd rather
install an rpm than have to rebuild all of GNOME :) I'll do some
checking real quick to be sure...

regards,
J
Comment 7 Owen Taylor 2003-07-09 13:49:29 UTC
The link to the debuginfo package was pasted by Elijah above:

http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm

While we dont' have a formalized mechanism for distributing these
packages, they are built along with the binary packages.