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 81830 - crash after redhat 7.3 upgrade
crash after redhat 7.3 upgrade
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-14 14:22 UTC by Phil.K.Jansen
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Phil.K.Jansen 2002-05-15 06:14:53 UTC 
Package: gnome-panel
Severity: major
Version: 1.4.0.4
Synopsis: crash after redhat 7.3 upgrade
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel

Description:
I had RedHat 7.1 installed;

I upgraded to RedHat 7.3 (with the three install disks in the "personal" boxed edition).

During my upgrade, I added several new packages which I hadn't installed before, 
such as "wine", "ruby", etc.

And, the first time I tried to log in, I got this crash.  I suspect it's "panel" which 
crashed, but I can't really tell -- something in gnome startup crashed.


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

+ Trace 22184

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #3 <signal handler called>
  • #4 chunk_alloc
    from /lib/i686/libc.so.6
  • #5 malloc
    from /lib/i686/libc.so.6
  • #6 g_malloc
    from /usr/lib/libglib-1.2.so.0
  • #7 gdk_window_foreign_new
    from /usr/lib/libgdk-1.2.so.0
  • #8 gdk_window_ref_from_xid
  • #9 client_list_sync
  • #10 gwmh_desk_update
  • #11 gwmh_idle_handler
  • #12 g_idle_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #13 g_main_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #14 g_main_iterate
    from /usr/lib/libglib-1.2.so.0
  • #15 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #16 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #17 main
  • #18 __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_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #3 <signal handler called>
  • #4 chunk_alloc
    from /lib/i686/libc.so.6
  • #5 malloc
    from /lib/i686/libc.so.6
  • #6 g_malloc
    from /usr/lib/libglib-1.2.so.0
  • #7 gdk_window_foreign_new
    from /usr/lib/libgdk-1.2.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-15 02:14 -------

The original reporter (Phil.K.Jansen@Tektronix.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, gnome-panel-maint@bugzilla.gnome.org.
Comment 1 Kjartan Maraas 2002-05-15 22:09:01 UTC 
Please try gnome-libs-1.4.1.6 and gnome-core-1.4.0.8 or newer. I've
made RPMS available at http://www.gnome.org/~kmaraas if you can make
use of those. Please report back here whether this fixes the problem
or not.
Comment 2 Phil.K.Jansen 2002-05-16 14:46:50 UTC 
I have not seen this crash since that one "first login after 7.1->7.3 
upgrade" time.

I've not upgraded since, so maybe I'm not duplicating original 
conditions enough.

Since I can't duplicate the crash with the current installation, I 
don't think it's worth upgrading gnome-libs or gnome-core -- I doubt 
they have much trouble either.
Comment 3 Phil.K.Jansen 2002-05-16 15:47:04 UTC 
Oh, sorry... I should have ALSO said

"This bug doesn't seem to be very repeatable.  I'm not sure its worth 
pursuing.  Close it out?"
Comment 4 Kjartan Maraas 2002-05-21 15:12:30 UTC 

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