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 83588 - xpdf tar sources crash the gnome panel every time
xpdf tar sources crash the gnome panel every time
Status: RESOLVED DUPLICATE of bug 59500
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-30 20:47 UTC by sgrannis
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sgrannis 2002-05-30 20:48:17 UTC 
Package: gnome-panel
Severity: normal
Version: 1.4.0.8
Synopsis: xpdf tar sources crash the gnome panel every time
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel

Description:
installed xpdf from source (xpdf-1.01-linux.tar.gz) -- every time i open
xpdf it crashes teh panel in gnome (ximian 1.4) but the panel re-spawns
immediately and xpdf is fully dunctional.



Debugging Information:

(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)...0x420b4769 in wait4 () from /lib/i686/libc.so.6

+ Trace 23052

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_init
    from /usr/lib/libgnomeui.so.32
  • #3 <signal handler called>
  • #4 gdk_window_add_filter
    from /usr/lib/libgdk-1.2.so.0
  • #5 gwmh_task_notifier_remove_func
  • #6 gwmh_task_notifier_remove_func
  • #7 gwmh_root_put_atom_window
  • #8 gwmh_root_put_atom_window
  • #9 g_timeout_add
    from /usr/lib/libglib-1.2.so.0
  • #10 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #11 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #12 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #14 main
  • #15 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_init
    from /usr/lib/libgnomeui.so.32
  • #3 <signal handler called>
  • #4 gdk_window_add_filter
    from /usr/lib/libgdk-1.2.so.0
  • #5 gwmh_task_notifier_remove_func
  • #6 gwmh_task_notifier_remove_func
  • #7 gwmh_root_put_atom_window 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-30 16:48 -------

The original reporter (sgrannis@regenstrief.org) 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, gnome-panel-maint@bugzilla.gnome.org.
Comment 1 Kjartan Maraas 2002-05-30 22:39:19 UTC 
This is being worked on, but progress is slow. It's caused by
corruption of internal data structures in the panel and we've yet to
find the bug. Stay tuned.

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