GNOME Bugzilla – Bug 59500
panel crash on login [ gwmh_* ]
Last modified: 2019-10-28 21:23:17 UTC
Package: gnome-core Severity: normal Version: 1.4.0.4 Synopsis: panel crash on login Bugzilla-Product: gnome-core Bugzilla-Component: panel Description: I got a report of a panel crash on my initial login to a newly installed roswell installation. 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)... 0x405b45b9 in __wait4 () from /lib/i686/libc.so.6
+ Trace 8891
------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-08-24 17:27 ------- The original reporter (kodis@mail630.gsfc.nasa.gov) 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, panel-maint@bugzilla.gnome.org.
*** Bug 59944 has been marked as a duplicate of this bug. ***
*** Bug 61286 has been marked as a duplicate of this bug. ***
*** Bug 62275 has been marked as a duplicate of this bug. ***
*** Bug 62865 has been marked as a duplicate of this bug. ***
*** Bug 62930 has been marked as a duplicate of this bug. ***
*** Bug 62939 has been marked as a duplicate of this bug. ***
*** Bug 63166 has been marked as a duplicate of this bug. ***
*** Bug 63225 has been marked as a duplicate of this bug. ***
*** Bug 63227 has been marked as a duplicate of this bug. ***
*** Bug 63377 has been marked as a duplicate of this bug. ***
*** Bug 63457 has been marked as a duplicate of this bug. ***
*** Bug 63614 has been marked as a duplicate of this bug. ***
*** Bug 63713 has been marked as a duplicate of this bug. ***
*** Bug 63745 has been marked as a duplicate of this bug. ***
*** Bug 63776 has been marked as a duplicate of this bug. ***
*** Bug 63810 has been marked as a duplicate of this bug. ***
*** Bug 63856 has been marked as a duplicate of this bug. ***
*** Bug 63866 has been marked as a duplicate of this bug. ***
*** Bug 63928 has been marked as a duplicate of this bug. ***
*** Bug 63964 has been marked as a duplicate of this bug. ***
*** Bug 64519 has been marked as a duplicate of this bug. ***
*** Bug 64536 has been marked as a duplicate of this bug. ***
*** Bug 64599 has been marked as a duplicate of this bug. ***
*** Bug 64656 has been marked as a duplicate of this bug. ***
*** Bug 64290 has been marked as a duplicate of this bug. ***
*** Bug 64981 has been marked as a duplicate of this bug. ***
*** Bug 65010 has been marked as a duplicate of this bug. ***
*** Bug 65095 has been marked as a duplicate of this bug. ***
*** Bug 65646 has been marked as a duplicate of this bug. ***
*** Bug 65728 has been marked as a duplicate of this bug. ***
*** Bug 65793 has been marked as a duplicate of this bug. ***
*** Bug 66058 has been marked as a duplicate of this bug. ***
*** Bug 66343 has been marked as a duplicate of this bug. ***
*** Bug 66413 has been marked as a duplicate of this bug. ***
*** Bug 66485 has been marked as a duplicate of this bug. ***
*** Bug 66545 has been marked as a duplicate of this bug. ***
*** Bug 67069 has been marked as a duplicate of this bug. ***
*** Bug 67245 has been marked as a duplicate of this bug. ***
*** Bug 67447 has been marked as a duplicate of this bug. ***
*** Bug 67490 has been marked as a duplicate of this bug. ***
*** Bug 67592 has been marked as a duplicate of this bug. ***
*** Bug 67680 has been marked as a duplicate of this bug. ***
*** Bug 68071 has been marked as a duplicate of this bug. ***
*** Bug 68463 has been marked as a duplicate of this bug. ***
*** Bug 68525 has been marked as a duplicate of this bug. ***
*** Bug 68659 has been marked as a duplicate of this bug. ***
*** Bug 68693 has been marked as a duplicate of this bug. ***
*** Bug 68853 has been marked as a duplicate of this bug. ***
WTF? How did you guys mark nearly 50 duplicates and not confirm or close this bug? Am I missing something here?
Sorry about that :) This is very likely to be the same as 69333 too and hopefully that's fixed now.
Then resolving as fixed.
*** Bug 64418 has been marked as a duplicate of this bug. ***
*** Bug 65113 has been marked as a duplicate of this bug. ***
*** Bug 65466 has been marked as a duplicate of this bug. ***
*** Bug 65691 has been marked as a duplicate of this bug. ***
*** Bug 65692 has been marked as a duplicate of this bug. ***
*** Bug 65771 has been marked as a duplicate of this bug. ***
*** Bug 65773 has been marked as a duplicate of this bug. ***
*** Bug 66381 has been marked as a duplicate of this bug. ***
*** Bug 66423 has been marked as a duplicate of this bug. ***
*** Bug 67417 has been marked as a duplicate of this bug. ***
*** Bug 68291 has been marked as a duplicate of this bug. ***
*** Bug 68494 has been marked as a duplicate of this bug. ***
*** Bug 68974 has been marked as a duplicate of this bug. ***
*** Bug 69213 has been marked as a duplicate of this bug. ***
*** Bug 69236 has been marked as a duplicate of this bug. ***
*** Bug 69409 has been marked as a duplicate of this bug. ***
*** Bug 69729 has been marked as a duplicate of this bug. ***
*** Bug 69797 has been marked as a duplicate of this bug. ***
*** Bug 69891 has been marked as a duplicate of this bug. ***
*** Bug 69926 has been marked as a duplicate of this bug. ***
*** Bug 70930 has been marked as a duplicate of this bug. ***
*** Bug 71956 has been marked as a duplicate of this bug. ***
*** Bug 71658 has been marked as a duplicate of this bug. ***
*** Bug 71733 has been marked as a duplicate of this bug. ***
*** Bug 71736 has been marked as a duplicate of this bug. ***
*** Bug 71757 has been marked as a duplicate of this bug. ***
updated summary to make it easier to find.
*** Bug 71164 has been marked as a duplicate of this bug. ***
bug 71164 reports thie problem with gnome-core 1.4.0.6 that is worrying
reopening... this would have to be a 1.4.1 blocker.
*** Bug 66565 has been marked as a duplicate of this bug. ***
*** Bug 67276 has been marked as a duplicate of this bug. ***
*** Bug 66357 has been marked as a duplicate of this bug. ***
*** Bug 71914 has been marked as a duplicate of this bug. ***
*** Bug 72415 has been marked as a duplicate of this bug. ***
*** Bug 72442 has been marked as a duplicate of this bug. ***
*** Bug 72342 has been marked as a duplicate of this bug. ***
*** Bug 72662 has been marked as a duplicate of this bug. ***
*** Bug 73001 has been marked as a duplicate of this bug. ***
*** Bug 72966 has been marked as a duplicate of this bug. ***
*** Bug 72620 has been marked as a duplicate of this bug. ***
*** Bug 72746 has been marked as a duplicate of this bug. ***
*** Bug 73140 has been marked as a duplicate of this bug. ***
*** Bug 73152 has been marked as a duplicate of this bug. ***
*** Bug 73225 has been marked as a duplicate of this bug. ***
*** Bug 73384 has been marked as a duplicate of this bug. ***
*** Bug 73416 has been marked as a duplicate of this bug. ***
*** Bug 73482 has been marked as a duplicate of this bug. ***
*** Bug 73930 has been marked as a duplicate of this bug. ***
*** Bug 73999 has been marked as a duplicate of this bug. ***
*** Bug 74247 has been marked as a duplicate of this bug. ***
*** Bug 68631 has been marked as a duplicate of this bug. ***
*** Bug 71911 has been marked as a duplicate of this bug. ***
*** Bug 72769 has been marked as a duplicate of this bug. ***
*** Bug 74334 has been marked as a duplicate of this bug. ***
*** Bug 75087 has been marked as a duplicate of this bug. ***
*** Bug 75157 has been marked as a duplicate of this bug. ***
*** Bug 74034 has been marked as a duplicate of this bug. ***
*** Bug 75003 has been marked as a duplicate of this bug. ***
*** Bug 74918 has been marked as a duplicate of this bug. ***
*** Bug 74929 has been marked as a duplicate of this bug. ***
*** Bug 75548 has been marked as a duplicate of this bug. ***
*** Bug 75364 has been marked as a duplicate of this bug. ***
*** Bug 75901 has been marked as a duplicate of this bug. ***
*** Bug 75352 has been marked as a duplicate of this bug. ***
*** Bug 75625 has been marked as a duplicate of this bug. ***
bug 75625 is another gnome-core 1.4.0.6 report
*** Bug 75676 has been marked as a duplicate of this bug. ***
*** Bug 75723 has been marked as a duplicate of this bug. ***
*** Bug 75727 has been marked as a duplicate of this bug. ***
*** Bug 76156 has been marked as a duplicate of this bug. ***
*** Bug 76010 has been marked as a duplicate of this bug. ***
*** Bug 76079 has been marked as a duplicate of this bug. ***
*** Bug 76236 has been marked as a duplicate of this bug. ***
*** Bug 75946 has been marked as a duplicate of this bug. ***
*** Bug 76052 has been marked as a duplicate of this bug. ***
*** Bug 76247 has been marked as a duplicate of this bug. ***
*** Bug 76323 has been marked as a duplicate of this bug. ***
*** Bug 75242 has been marked as a duplicate of this bug. ***
As per heath@pointedstick.net's request, here's some more information about my system (http://bugzilla.gnome.org/show_bug.cgi?id=76323). This is a Red Hat 7.2 system running the latest version of Ximian Gnome desktop with the following rpms: gnome-libs-1.4.1.4-1.ximian.3 gtk+-1.2.10-ximian.21 XFree86-4.1.0-15 The graphics card is an NVidia GeForce 2. I am running the "nvidia" driver provided by NVidia. (I don't know what other information is relevant. I don't have a recipee for reproducing the bug except that it is triggered by Galeon opening a PDF document for me.)
*** Bug 76679 has been marked as a duplicate of this bug. ***
*** Bug 76718 has been marked as a duplicate of this bug. ***
*** Bug 76711 has been marked as a duplicate of this bug. ***
*** Bug 76697 has been marked as a duplicate of this bug. ***
*** Bug 76977 has been marked as a duplicate of this bug. ***
*** Bug 76979 has been marked as a duplicate of this bug. ***
*** Bug 76982 has been marked as a duplicate of this bug. ***
*** Bug 77085 has been marked as a duplicate of this bug. ***
*** Bug 76377 has been marked as a duplicate of this bug. ***
*** Bug 77107 has been marked as a duplicate of this bug. ***
*** Bug 77224 has been marked as a duplicate of this bug. ***
*** Bug 76931 has been marked as a duplicate of this bug. ***
*** Bug 77414 has been marked as a duplicate of this bug. ***
*** Bug 77468 has been marked as a duplicate of this bug. ***
Hmm. I been looking at a lot of these bugs that I have been closing and few that were marked need info. There seems to be a common tread - that is they were running Ximan gnome. So possibly its something wrong with their packages?
*** Bug 77511 has been marked as a duplicate of this bug. ***
*** Bug 77509 has been marked as a duplicate of this bug. ***
*** Bug 77500 has been marked as a duplicate of this bug. ***
*** Bug 77488 has been marked as a duplicate of this bug. ***
*** Bug 77522 has been marked as a duplicate of this bug. ***
*** Bug 71379 has been marked as a duplicate of this bug. ***
*** Bug 71383 has been marked as a duplicate of this bug. ***
*** Bug 77547 has been marked as a duplicate of this bug. ***
*** Bug 77553 has been marked as a duplicate of this bug. ***
*** Bug 77583 has been marked as a duplicate of this bug. ***
*** Bug 77604 has been marked as a duplicate of this bug. ***
*** Bug 77664 has been marked as a duplicate of this bug. ***
*** Bug 77449 has been marked as a duplicate of this bug. ***
*** Bug 78225 has been marked as a duplicate of this bug. ***
*** Bug 77863 has been marked as a duplicate of this bug. ***
*** Bug 77961 has been marked as a duplicate of this bug. ***
*** Bug 78002 has been marked as a duplicate of this bug. ***
hey, i added the following comments to bug 78225, but it looks like they would be better off being placed here. more info: note that this crash also occurred while opening a document using xpdf (as it did for one of the earlier bug reporters). the box is a IBM T23 laptop with a 1133 MHz mobile P3 and 640 Mbyte RAM. i'm running XFree86 v4.1.0 with some patches from S3 for the SuperSavage video chipset. because of bugs in the driver for my SuperSavage chipset the laptop occasionally crashes. perhaps that's the explanation for the panel crash? sorry i didn't mention that before; i didn't think of it. i've been running this config for at least a couple of months, and i think this is the first panel crash i've seen. more info: running Redhat 7.1 gnome upgraded to helix-gnome from ximian website to most recent version as of 4/1/02 (approximately) [charmer@elvis charmer]$ panel --version Gnome panel 1.4.0.6 [charmer@elvis charmer]$ here are the relevant set of packages (i think): [charmer@elvis charmer]$ rpm -q -a | grep gnome libunicode-0.4.gnome-ximian.1 gnome-audio-1.4.0-ximian.1 rhn_register-gnome-2.7.9-7.x.2 libgnomeprint15-0.35-1.ximian.1 gnome-core-devel-1.4.0.6-1.ximian.2 gnome-print-devel-0.35-1.ximian.1 gnome-users-guide-1.2-3 gnome-media-1.2.0-12 pygnome-libglade-0.6.6-7 rep-gtk-gnome-0.15-ximian.4 gnome-user-docs-1.4.1-ximian.2 xmms-gnome-1.2.5-ximian.4 openssh-askpass-gnome-3.1p1-1 up2date-gnome-2.7.61-7.x.1 gnome-print-0.35-1.ximian.1 gnome-objc-devel-1.0.2-11 gnome-vfs-devel-1.0.1-ximian.5 gnome-pim-devel-1.4.0-ximian.5 gnome-applets-1.4.0.1-ximian.5 gnomeicu-0.96.1-ximian.2 gnome-utils-1.4.0-ximian.8 gnome-games-devel-1.4.0.1-ximian.12 gnome-libs-1.4.1.4-1.ximian.3 gnome-libs-devel-1.4.1.4-1.ximian.3 gnome-pilot-0.1.64-ximian.1 gnome-audio-extra-1.0.0-12 switchdesk-gnome-3.9.5-1 pygnome-1.0.53-7 gnome-objc-1.0.2-11 gnome-vfs-1.0.1-ximian.5 gnome-pim-1.4.0-ximian.5 libunicode-devel-0.4.gnome-ximian.1 libgnomeprint11-0.25-ximian.6 gnome-games-1.4.0.1-ximian.12 gnome-core-1.4.0.6-1.ximian.2 [charmer@elvis charmer]$
*** Bug 78357 has been marked as a duplicate of this bug. ***
*** Bug 77611 has been marked as a duplicate of this bug. ***
*** Bug 78215 has been marked as a duplicate of this bug. ***
*** Bug 78400 has been marked as a duplicate of this bug. ***
*** Bug 78522 has been marked as a duplicate of this bug. ***
*** Bug 78519 has been marked as a duplicate of this bug. ***
*** Bug 78547 has been marked as a duplicate of this bug. ***
*** Bug 78561 has been marked as a duplicate of this bug. ***
*** Bug 78682 has been marked as a duplicate of this bug. ***
*** Bug 78690 has been marked as a duplicate of this bug. ***
*** Bug 78722 has been marked as a duplicate of this bug. ***
*** Bug 78922 has been marked as a duplicate of this bug. ***
*** Bug 78961 has been marked as a duplicate of this bug. ***
*** Bug 78979 has been marked as a duplicate of this bug. ***
*** Bug 78986 has been marked as a duplicate of this bug. ***
*** Bug 78987 has been marked as a duplicate of this bug. ***
*** Bug 79152 has been marked as a duplicate of this bug. ***
*** Bug 79186 has been marked as a duplicate of this bug. ***
*** Bug 79215 has been marked as a duplicate of this bug. ***
*** Bug 79240 has been marked as a duplicate of this bug. ***
*** Bug 79268 has been marked as a duplicate of this bug. ***
*** Bug 79269 has been marked as a duplicate of this bug. ***
*** Bug 79305 has been marked as a duplicate of this bug. ***
*** Bug 79387 has been marked as a duplicate of this bug. ***
*** Bug 79435 has been marked as a duplicate of this bug. ***
*** Bug 77575 has been marked as a duplicate of this bug. ***
*** Bug 79489 has been marked as a duplicate of this bug. ***
*** Bug 79502 has been marked as a duplicate of this bug. ***
*** Bug 75997 has been marked as a duplicate of this bug. ***
*** Bug 79304 has been marked as a duplicate of this bug. ***
*** Bug 73953 has been marked as a duplicate of this bug. ***
This is how it looks for me now: Program received signal SIGSEGV, Segmentation fault. gdk_window_add_filter (window=0x8163b80, function=0x805a528 <task_event_monitor>, data=0x8163cb0) at gdkwindow.c:1965 1965 filter = (GdkEventFilter *)tmp_list->data; (gdb) bt
+ Trace 21224
*** Bug 79651 has been marked as a duplicate of this bug. ***
FYI, this is not a Ximian Gnome problem. I see this bug on my own painfully-compiled-from-source-on-sparc-solaris Gnome.
*** Bug 79679 has been marked as a duplicate of this bug. ***
*** Bug 79773 has been marked as a duplicate of this bug. ***
*** Bug 79764 has been marked as a duplicate of this bug. ***
*** Bug 79799 has been marked as a duplicate of this bug. ***
*** Bug 79802 has been marked as a duplicate of this bug. ***
*** Bug 79867 has been marked as a duplicate of this bug. ***
*** Bug 79857 has been marked as a duplicate of this bug. ***
*** Bug 79924 has been marked as a duplicate of this bug. ***
*** Bug 79970 has been marked as a duplicate of this bug. ***
*** Bug 79975 has been marked as a duplicate of this bug. ***
*** Bug 80001 has been marked as a duplicate of this bug. ***
*** Bug 77210 has been marked as a duplicate of this bug. ***
*** Bug 79903 has been marked as a duplicate of this bug. ***
*** Bug 79906 has been marked as a duplicate of this bug. ***
*** Bug 80049 has been marked as a duplicate of this bug. ***
*** Bug 80158 has been marked as a duplicate of this bug. ***
*** Bug 80162 has been marked as a duplicate of this bug. ***
*** Bug 80169 has been marked as a duplicate of this bug. ***
*** Bug 80344 has been marked as a duplicate of this bug. ***
*** Bug 80343 has been marked as a duplicate of this bug. ***
*** Bug 80332 has been marked as a duplicate of this bug. ***
*** Bug 80371 has been marked as a duplicate of this bug. ***
*** Bug 80379 has been marked as a duplicate of this bug. ***
*** Bug 80393 has been marked as a duplicate of this bug. ***
*** Bug 80154 has been marked as a duplicate of this bug. ***
*** Bug 80436 has been marked as a duplicate of this bug. ***
*** Bug 80444 has been marked as a duplicate of this bug. ***
*** Bug 80464 has been marked as a duplicate of this bug. ***
*** Bug 80483 has been marked as a duplicate of this bug. ***
*** Bug 80546 has been marked as a duplicate of this bug. ***
*** Bug 80583 has been marked as a duplicate of this bug. ***
*** Bug 80563 has been marked as a duplicate of this bug. ***
*** Bug 80595 has been marked as a duplicate of this bug. ***
*** Bug 80613 has been marked as a duplicate of this bug. ***
*** Bug 80621 has been marked as a duplicate of this bug. ***
*** Bug 80666 has been marked as a duplicate of this bug. ***
*** Bug 80750 has been marked as a duplicate of this bug. ***
*** Bug 80695 has been marked as a duplicate of this bug. ***
*** Bug 80884 has been marked as a duplicate of this bug. ***
*** Bug 80890 has been marked as a duplicate of this bug. ***
*** Bug 80991 has been marked as a duplicate of this bug. ***
*** Bug 80969 has been marked as a duplicate of this bug. ***
*** Bug 80990 has been marked as a duplicate of this bug. ***
*** Bug 81105 has been marked as a duplicate of this bug. ***
*** Bug 81117 has been marked as a duplicate of this bug. ***
*** Bug 81206 has been marked as a duplicate of this bug. ***
*** Bug 81223 has been marked as a duplicate of this bug. ***
*** Bug 81349 has been marked as a duplicate of this bug. ***
*** Bug 81473 has been marked as a duplicate of this bug. ***
*** Bug 81492 has been marked as a duplicate of this bug. ***
*** Bug 80099 has been marked as a duplicate of this bug. ***
*** Bug 80844 has been marked as a duplicate of this bug. ***
*** Bug 80041 has been marked as a duplicate of this bug. ***
*** Bug 81371 has been marked as a duplicate of this bug. ***
*** Bug 80995 has been marked as a duplicate of this bug. ***
*** Bug 76520 has been marked as a duplicate of this bug. ***
*** Bug 79862 has been marked as a duplicate of this bug. ***
*** Bug 81307 has been marked as a duplicate of this bug. ***
*** Bug 81733 has been marked as a duplicate of this bug. ***
*** Bug 81746 has been marked as a duplicate of this bug. ***
*** Bug 81712 has been marked as a duplicate of this bug. ***
*** Bug 81680 has been marked as a duplicate of this bug. ***
*** Bug 81778 has been marked as a duplicate of this bug. ***
*** Bug 81744 has been marked as a duplicate of this bug. ***
*** Bug 79379 has been marked as a duplicate of this bug. ***
*** Bug 81970 has been marked as a duplicate of this bug. ***
*** Bug 81990 has been marked as a duplicate of this bug. ***
*** Bug 81993 has been marked as a duplicate of this bug. ***
*** Bug 82024 has been marked as a duplicate of this bug. ***
*** Bug 82066 has been marked as a duplicate of this bug. ***
*** Bug 82101 has been marked as a duplicate of this bug. ***
*** Bug 82121 has been marked as a duplicate of this bug. ***
*** Bug 82202 has been marked as a duplicate of this bug. ***
*** Bug 82222 has been marked as a duplicate of this bug. ***
*** Bug 82231 has been marked as a duplicate of this bug. ***
*** Bug 82277 has been marked as a duplicate of this bug. ***
*** Bug 82284 has been marked as a duplicate of this bug. ***
*** Bug 82367 has been marked as a duplicate of this bug. ***
*** Bug 82365 has been marked as a duplicate of this bug. ***
*** Bug 75149 has been marked as a duplicate of this bug. ***
*** Bug 80857 has been marked as a duplicate of this bug. ***
*** Bug 81254 has been marked as a duplicate of this bug. ***
*** Bug 81302 has been marked as a duplicate of this bug. ***
*** Bug 81461 has been marked as a duplicate of this bug. ***
*** Bug 81830 has been marked as a duplicate of this bug. ***
*** Bug 82311 has been marked as a duplicate of this bug. ***
*** Bug 82460 has been marked as a duplicate of this bug. ***
*** Bug 82462 has been marked as a duplicate of this bug. ***
*** Bug 82713 has been marked as a duplicate of this bug. ***
*** Bug 82709 has been marked as a duplicate of this bug. ***
*** Bug 75431 has been marked as a duplicate of this bug. ***
*** Bug 82435 has been marked as a duplicate of this bug. ***
*** Bug 81938 has been marked as a duplicate of this bug. ***
*** Bug 82566 has been marked as a duplicate of this bug. ***
*** Bug 82576 has been marked as a duplicate of this bug. ***
*** Bug 81691 has been marked as a duplicate of this bug. ***
*** Bug 81839 has been marked as a duplicate of this bug. ***
*** Bug 82531 has been marked as a duplicate of this bug. ***
*** Bug 82851 has been marked as a duplicate of this bug. ***
*** Bug 82804 has been marked as a duplicate of this bug. ***
*** Bug 82440 has been marked as a duplicate of this bug. ***
*** Bug 82995 has been marked as a duplicate of this bug. ***
*** Bug 83034 has been marked as a duplicate of this bug. ***
*** Bug 83245 has been marked as a duplicate of this bug. ***
*** Bug 83310 has been marked as a duplicate of this bug. ***
*** Bug 83436 has been marked as a duplicate of this bug. ***
*** Bug 83588 has been marked as a duplicate of this bug. ***
*** Bug 79940 has been marked as a duplicate of this bug. ***
Ok, I could not generate this bug on my system, UNTIL I got rid of "LC_ALL=POSIX" in my .bashrc Then all I have to do is right click on a pdf and to 'open with... xpf' and it crashes the panel almost everytime. This is with latest CVS. I am using Sawfish 1.0 (with 2x2 viewports). (the rest is stock RH 7.1/Xfree 4 with all gnome updated from CVS) Here is the stack I get (not much new here) from bug-buddy: (note I have my session manager set to run panel --sync) 0x4057de29 in __wait4 () from /lib/libc.so.6
+ Trace 23218
In vain hope I wondered if this might be a glib ghook bug. There have been a few bug fixes of the ghook code in glib 2.0.0. There was a simple fix to g_hook_compare_ids which I backported but didn't help. The most significant change is in this ChangeLog: Thu Mar 8 16:23:34 2001 Tim Janik <timj@gtk.org> * ghook.[hc]: destruction cleanup. there's one ->finalize_hook member in the hooklist now that gets called when a hook should be destroyed, that's it. that function is guarranteed to be called only when all ref_counts to the hook vanished, thus also when the hook is not in call. This is a bit complex this fix, so I haven't attempted to backport it. kmaraas: do you think this ghook fix could be it? or is it definitely a problem in our code? I sadly guess the latter option. I guess I will keep looking through the code in gnome-core/applets/desk-guide/gwmh.c (this is where the data corruption is happening right?) Why does this not occur with LC_ALL=POSIX ??? What difference would this make?
Created attachment 8972 [details] [review] patch against cvs
ok. there is a patch which minimises the calls to gwmh_desk_update in the idle handler. I don't understand why it was called twice in the handler. No, I don't really have any idea what I am doing. But, this patch does seem to greatly minimise the amount of crashes. Instead of 90% of the time it is now 20% of the time, roughly speaking. This is of course not really fixing the bug, but avoiding the crash. It makes good sense to me to minimise the work that happens in an idle handler. kmaraas: please tell me if how much, if any, this improves things for you. I know this is not a real solution, but I am just stabbing in the dark to improve the idle handler. I will keep working on this.
Didn't really help that much. I triggered the bug after doing the xpdf exercise 5-6 times.
*** Bug 71625 has been marked as a duplicate of this bug. ***
*** Bug 83822 has been marked as a duplicate of this bug. ***
*** Bug 83844 has been marked as a duplicate of this bug. ***
*** Bug 83846 has been marked as a duplicate of this bug. ***
*** Bug 83919 has been marked as a duplicate of this bug. ***
*** Bug 83998 has been marked as a duplicate of this bug. ***
*** Bug 84141 has been marked as a duplicate of this bug. ***
*** Bug 84167 has been marked as a duplicate of this bug. ***
*** Bug 84181 has been marked as a duplicate of this bug. ***
*** Bug 84265 has been marked as a duplicate of this bug. ***
ok gwmh_idle_handler is a run once idle handler... I can see one potential race near the end where we reset gwmh_idle_handler_id and then call gwmh_desk_update, which could in turn run gwmh_desk_queue_update which would trigger another idle handler running while the current one is in process. (eg: you would have the function gwmh_desk_update running twice, on the same data structures I think.) Unfortunately this is not the corruption, as reseting the handler_id as the last line of the function does not remove the crash. /me keeps looking Has Tim Janik had a look for this bug for us? He wrote most of this code didn't he?
*** Bug 84331 has been marked as a duplicate of this bug. ***
*** Bug 84342 has been marked as a duplicate of this bug. ***
*** Bug 84369 has been marked as a duplicate of this bug. ***
To help others... here are the clear instructions on how to reproduce the bug: 1. Make sure your shell has no LC_ALL setting (remove any LC_ALL=POSIX or C or whatever) 2. Open nautilus (eg: double click on your home icon on the desktop). 3. Find a PDF and right click on it, do 'open with' PDF. 4. As xpdf opens the panel will crash and you will get the gnome-segv dialog. If the panel doesn't crash, close the nautilus window and go back to step 2. My system gets it every second or third time.
oh, to clarify, step 3 above is done within the nautilus file browser window.
Gregory Merchan suggested in irc that there are some problems that require: Index: main.c =================================================================== RCS file: /cvs/gnome/gnome-core/panel/main.c,v retrieving revision 1.246.2.4 diff -u -r1.246.2.4 main.c --- main.c 28 May 2002 23:48:16 -0000 1.246.2.4 +++ main.c 7 Jun 2002 01:46:49 -0000 @@ -590,9 +590,9 @@ panel_tooltips = gtk_tooltips_new (); - status_applet_create_offscreen (); xstuff_init (); + status_applet_create_offscreen (); multiscreen_init (); gnome_win_hints_init (); eg: change the order.. This didn't fix this bug but he mentioned it might fix some startup crashes and status dock issues.
Tim Janik was helpful on IRC and offered some advice, none of which has helped me find the bug yet. We still think it is data corruption. Tim couldn't reproduce the problem on his debian system (with gnome 1.4 built from debian packaging) Is this a RedHat only bug? (eg: something weird in redhats glibc package?) Can anyone reproduce this on non-redhat systems? (I am on RedHat)
I see this bug on my system, which is up-to-date sources compiled myself on Solaris 8. Not Red-hat specific. I don't have LC_ALL set, and the crash happens about two out of three times.
*** Bug 84460 has been marked as a duplicate of this bug. ***
*** Bug 84329 has been marked as a duplicate of this bug. ***
We've already moved the status_applet_create_offscreen() call around a few times. Why did Gregory feel that another move was needed? The status dock is broken anyway and should probably be removed altogether.
Sorry, I see it now. There's a call to xstuff_setup_kde_something in status_applet_create_offscreen(). I'll move it around again.
Created attachment 9084 [details] [review] another attempt
ok the above patch is not perfect yet but a rough attempt. the latest theory is that our GdkWindow data is becoming invalid because we are not holding a reference to it. I think my patch gives us TOO MANY references, but I am just testing a theory right now. kmaraas: could you please try this patch out and see if you can reproduce the bug.
here is a RH 7.3 panel crash on startup backtrace which I think verifies my theory, or at least helps us get close to the source of the problem. I received it from Hal Hawkins <hal@compudrivel.com>, who has also submitted it to bugzilla somewhere (can't find it yet). Package: gnome-panel Severity: normal Version: 1.4.0.4 Synopsis: Segmentation fault in panel Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Description: I logged in as root, after Gnome desktop loads I get a segmentation fault in panel. 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 23534
*** Bug 84584 has been marked as a duplicate of this bug. ***
With the latest patch I get this on startup of the tasklist_applet: Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width 65527 and height 1 And later this crash: Program received signal SIGSEGV, Segmentation fault.
+ Trace 23541
Thread 1024 (LWP 16993)
I did not recompile the tasklist applet :/
*** Bug 84627 has been marked as a duplicate of this bug. ***
*** Bug 64587 has been marked as a duplicate of this bug. ***
Created attachment 9123 [details] [review] another try
the above patch is my latest attempt. it adds a new function to check against adding an xid to the list that is already there. it also fixes a theoretical bug where gdk_window_ref_from_xid didn't create a reference in the gdk_window_foreign_new case. it also adds some liberal sanity checks using g_return and reorders some elements of task_new to make better sense. this patch seems to protect the panel against the crash (please verify) but breaks the desk guide. Probably my bandaid is over zealous. more work to do...
*** Bug 84805 has been marked as a duplicate of this bug. ***
*** Bug 84820 has been marked as a duplicate of this bug. ***
It seems to work for me, but the task menu in the righthand top corner on the menu panel is also broken by the patch.
*** Bug 84813 has been marked as a duplicate of this bug. ***
*** Bug 84901 has been marked as a duplicate of this bug. ***
*** Bug 84970 has been marked as a duplicate of this bug. ***
*** Bug 79853 has been marked as a duplicate of this bug. ***
Created attachment 9188 [details] [review] I HAVE NO CLUE PLEASE SHOOT ME
my debug spew was showing that we were getting cases where gdk_window_ref_from_xid was getting called on cases where we already had the xid in the list but gdk_window_lookup was failing, so we were creating a new foreign window, which is bad on a function which is destroying the task. this might be a source of a/the bug. it doesn't break the deskguide/tasklist, and I haven't been able to reproduce the bug with it yet.
hmmm ok, it still crashes. why does task_delete need to call gdk_window_ref_from_xid anyway? don't we have this info in task->gdkwindow and task->gdkframe?
just to record a discussion from irc. try putting a: return (TRUE); at the top of task_notifier() in xstuff.c if this stops the crash happening, then it is partially related to the connection between gwmh_* and swallowed apps. the solution will be to kill swallowed apps, which are already hopelessly broken. BUT we still need gwmh_* for the foobar right hand corner... If it wasn't for that then we wouldn't link to gwmh at all. I need to think about this one...
I tried removing both swallowed apps and status docklets (same as has been done in HEAD) and I still get this crash. I'll try the above solution and see if that helps.
*** Bug 85112 has been marked as a duplicate of this bug. ***
Still see the crash after adding return TRUE; as the first line in task_notifier()
AAAARRRGHHHHH!!! 8)
*** Bug 85163 has been marked as a duplicate of this bug. ***
*** Bug 85170 has been marked as a duplicate of this bug. ***
*** Bug 85091 has been marked as a duplicate of this bug. ***
*** Bug 85094 has been marked as a duplicate of this bug. ***
*** Bug 85101 has been marked as a duplicate of this bug. ***
*** Bug 83797 has been marked as a duplicate of this bug. ***
*** Bug 82429 has been marked as a duplicate of this bug. ***
*** Bug 85183 has been marked as a duplicate of this bug. ***
*** Bug 85198 has been marked as a duplicate of this bug. ***
*** Bug 85218 has been marked as a duplicate of this bug. ***
*** Bug 85220 has been marked as a duplicate of this bug. ***
*** Bug 85396 has been marked as a duplicate of this bug. ***
*** Bug 85598 has been marked as a duplicate of this bug. ***
*** Bug 85737 has been marked as a duplicate of this bug. ***
*** Bug 86055 has been marked as a duplicate of this bug. ***
*** Bug 85805 has been marked as a duplicate of this bug. ***
*** Bug 85910 has been marked as a duplicate of this bug. ***
*** Bug 85988 has been marked as a duplicate of this bug. ***
*** Bug 86212 has been marked as a duplicate of this bug. ***
*** Bug 86220 has been marked as a duplicate of this bug. ***
*** Bug 86224 has been marked as a duplicate of this bug. ***
*** Bug 86265 has been marked as a duplicate of this bug. ***
*** Bug 86323 has been marked as a duplicate of this bug. ***
*** Bug 84722 has been marked as a duplicate of this bug. ***
*** Bug 84027 has been marked as a duplicate of this bug. ***
*** Bug 86194 has been marked as a duplicate of this bug. ***
*** Bug 86525 has been marked as a duplicate of this bug. ***
*** Bug 86595 has been marked as a duplicate of this bug. ***
*** Bug 86611 has been marked as a duplicate of this bug. ***
*** Bug 86622 has been marked as a duplicate of this bug. ***
*** Bug 86415 has been marked as a duplicate of this bug. ***
*** Bug 86671 has been marked as a duplicate of this bug. ***
*** Bug 86821 has been marked as a duplicate of this bug. ***
*** Bug 86906 has been marked as a duplicate of this bug. ***
*** Bug 86928 has been marked as a duplicate of this bug. ***
*** Bug 86945 has been marked as a duplicate of this bug. ***
*** Bug 86074 has been marked as a duplicate of this bug. ***
*** Bug 83061 has been marked as a duplicate of this bug. ***
*** Bug 83804 has been marked as a duplicate of this bug. ***
*** Bug 87209 has been marked as a duplicate of this bug. ***
*** Bug 86188 has been marked as a duplicate of this bug. ***
*** Bug 87272 has been marked as a duplicate of this bug. ***
*** Bug 87459 has been marked as a duplicate of this bug. ***
*** Bug 87442 has been marked as a duplicate of this bug. ***
*** Bug 87545 has been marked as a duplicate of this bug. ***
*** Bug 87098 has been marked as a duplicate of this bug. ***
*** Bug 84664 has been marked as a duplicate of this bug. ***
*** Bug 86519 has been marked as a duplicate of this bug. ***
*** Bug 87089 has been marked as a duplicate of this bug. ***
*** Bug 87726 has been marked as a duplicate of this bug. ***
*** Bug 88026 has been marked as a duplicate of this bug. ***
*** Bug 74295 has been marked as a duplicate of this bug. ***
*** Bug 76858 has been marked as a duplicate of this bug. ***
*** Bug 87699 has been marked as a duplicate of this bug. ***
*** Bug 82145 has been marked as a duplicate of this bug. ***
*** Bug 87884 has been marked as a duplicate of this bug. ***
*** Bug 88232 has been marked as a duplicate of this bug. ***
*** Bug 88233 has been marked as a duplicate of this bug. ***
*** Bug 88236 has been marked as a duplicate of this bug. ***
*** Bug 88224 has been marked as a duplicate of this bug. ***
*** Bug 88142 has been marked as a duplicate of this bug. ***
*** Bug 88146 has been marked as a duplicate of this bug. ***
*** Bug 88134 has been marked as a duplicate of this bug. ***
*** Bug 83658 has been marked as a duplicate of this bug. ***
This just keeps getting reported. It really needs to be fixed.
*** Bug 85922 has been marked as a duplicate of this bug. ***
*** Bug 88437 has been marked as a duplicate of this bug. ***
*** Bug 88435 has been marked as a duplicate of this bug. ***
*** Bug 88420 has been marked as a duplicate of this bug. ***
*** Bug 75565 has been marked as a duplicate of this bug. ***
*** Bug 77178 has been marked as a duplicate of this bug. ***
*** Bug 77140 has been marked as a duplicate of this bug. ***
*** Bug 77703 has been marked as a duplicate of this bug. ***
*** Bug 80963 has been marked as a duplicate of this bug. ***
*** Bug 76698 has been marked as a duplicate of this bug. ***
*** Bug 75645 has been marked as a duplicate of this bug. ***
*** Bug 75563 has been marked as a duplicate of this bug. ***
*** Bug 77232 has been marked as a duplicate of this bug. ***
*** Bug 88486 has been marked as a duplicate of this bug. ***
*** Bug 88501 has been marked as a duplicate of this bug. ***
*** Bug 88546 has been marked as a duplicate of this bug. ***
*** Bug 88523 has been marked as a duplicate of this bug. ***
*** Bug 88638 has been marked as a duplicate of this bug. ***
*** Bug 88682 has been marked as a duplicate of this bug. ***
*** Bug 88640 has been marked as a duplicate of this bug. ***
*** Bug 88658 has been marked as a duplicate of this bug. ***
*** Bug 88779 has been marked as a duplicate of this bug. ***
*** Bug 88811 has been marked as a duplicate of this bug. ***
*** Bug 88822 has been marked as a duplicate of this bug. ***
*** Bug 88625 has been marked as a duplicate of this bug. ***
*** Bug 88626 has been marked as a duplicate of this bug. ***
*** Bug 88950 has been marked as a duplicate of this bug. ***
*** Bug 88918 has been marked as a duplicate of this bug. ***
*** Bug 89087 has been marked as a duplicate of this bug. ***
*** Bug 89190 has been marked as a duplicate of this bug. ***
*** Bug 89220 has been marked as a duplicate of this bug. ***
*** Bug 89237 has been marked as a duplicate of this bug. ***
*** Bug 89271 has been marked as a duplicate of this bug. ***
*** Bug 89307 has been marked as a duplicate of this bug. ***
*** Bug 89303 has been marked as a duplicate of this bug. ***
*** Bug 89405 has been marked as a duplicate of this bug. ***
*** Bug 89534 has been marked as a duplicate of this bug. ***
*** Bug 89670 has been marked as a duplicate of this bug. ***
*** Bug 89662 has been marked as a duplicate of this bug. ***
*** Bug 89755 has been marked as a duplicate of this bug. ***
*** Bug 89765 has been marked as a duplicate of this bug. ***
*** Bug 89773 has been marked as a duplicate of this bug. ***
*** Bug 89797 has been marked as a duplicate of this bug. ***
*** Bug 89957 has been marked as a duplicate of this bug. ***
*** Bug 90013 has been marked as a duplicate of this bug. ***
*** Bug 90028 has been marked as a duplicate of this bug. ***
*** Bug 89793 has been marked as a duplicate of this bug. ***
*** Bug 90043 has been marked as a duplicate of this bug. ***
*** Bug 88459 has been marked as a duplicate of this bug. ***
This is the latest news on this: tir, 2002-08-06 kl. 14:10 skrev Kjartan Maraas: > ons, 2002-04-24 kl. 07:22 skrev Kjartan Maraas: > > Hi all. > > > > We've received a whole lot of crash reports in bugzilla for 1.4.x that > > points to problems with the desk-guide code, more specific - list > > handling in gwmh.c. It could be specific to the panel and it could be > > deskguide/tasklist specific. > > > > Take a look at http://bugzilla.gnome.org/show_bug.cgi?id=59500 to see > > the buglist. > > > > I've compiled a panel with efence linked in and a hacked glist.c (from > > owen) to make things more visible and this is the backtrace I get: > > > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 1024 (LWP 1345)] > > gdk_window_add_filter (window=0x43f3dfcc, > > function=0x805a538 <task_event_monitor>, data=0x44078f98) > > at gdkwindow.c:1966 > > 1966 if ((filter->function == function) && (filter->data == data)) > > (gdb) bt > > #0 gdk_window_add_filter (window=0x43f3dfcc, > > function=0x805a538 <task_event_monitor>, data=0x44078f98) > > at gdkwindow.c:1966 > > #1 0x0805bafc in task_new (window=0x43f3dfcc) at gwmh.c:1726 > > #2 0x0805be9c in client_list_sync (xwindow_ids=0x440b6fcc, n_ids=1) > > at gwmh.c:1862 > > #3 0x0805ac8d in gwmh_desk_update (imask=GWMH_DESK_INFO_CLIENT_LIST) > > at gwmh.c:1100 > > #4 0x0805b54e in gwmh_idle_handler (data=0x0) at gwmh.c:1490 > > #5 0x404b7ddc in g_idle_dispatch (source_data=0x805b510, > > dispatch_time=0xbffed6f0, user_data=0x0) at gmain.c:1367 > > #6 0x404b6e41 in g_main_dispatch (dispatch_time=0xbffed6f0) at > > gmain.c:656 > > #7 0x404b7445 in g_main_iterate (block=1, dispatch=1) at gmain.c:877 > > #8 0x404b75d4 in g_main_run (loop=0x47b93ffc) at gmain.c:935 > > #9 0x403e101b in gtk_main () at gtkmain.c:524 > > #10 0x0805e38f in main (argc=1, argv=0xbffed7f4) at main.c:423 > > #11 0x420174d9 in __libc_start_main () from /lib/i686/libc.so.6 > > (gdb) list > > 1961 tmp_list = gdk_default_filters; > > 1962 > > 1963 while (tmp_list) > > 1964 { > > 1965 filter = (GdkEventFilter *)tmp_list->data; > > 1966 if ((filter->function == function) && (filter->data == data)) > > 1967 return; > > 1968 tmp_list = tmp_list->next; > > 1969 } > > 1970 > > > > > > It would be really nice with some help tracking this issue down since > > it's become somewhat a showstopper for GNOME 1.4.1 just because of the > > sheer amount of people reporting it. > > I'll just follow up on this here. > > I've been doing some more investigation into this matter with the help > from a lot of very nice people (you know who you are - and beers are on > me when we next meet) and I've been able to corner the beast further. > > It seems that gdk_window_ref_from_xid() returns a window with garbage > data. After looking at that more closely it is really > gdk_window_lookup(), which again is a #define for gdk_xid_table_lookup() > that returns bogus data. > > This gives us the clue that it is the xid table that has been corrupted, > or am I wrong here? > > Example of a corrupted entry: > > Breakpoint 1, gdk_window_ref_from_xid (xwin=56623105) at gwmh.c:341 > 341 window = gdk_window_lookup (xwin); > (gdb) b gdk_xid_table_lookup > Breakpoint 2 at 0x405286b2: file gdkxid.c, line 64. > (gdb) c > Continuing. > > Breakpoint 2, gdk_xid_table_lookup (xid=56623105) at gdkxid.c:64 > 64 gpointer data = NULL; > (gdb) n > 66 if (xid_ht) > (gdb) n > 67 data = g_hash_table_lookup (xid_ht, &xid); > (gdb) n > 69 return data; > (gdb) p xid_ht > $1 = (GHashTable *) 0x80eadd8 > (gdb) p *xid_ht > $2 = {size = 163, nnodes = 149, frozen = 0, nodes = 0x81a4110, > hash_func = 0x405286f0 <gdk_xid_hash>, > key_compare_func = 0x40528700 <gdk_xid_compare>} > (gdb) p xid > $3 = 56623105 > (gdb) p &xid > $4 = (XID *) 0xbffff3a0 > (gdb) n > 70 } > (gdb) n > gdk_window_ref_from_xid (xwin=56623105) at gwmh.c:342 > 342 if (!window) > (gdb) p *window > $5 = {user_data = 0x406952e8} > (gdb) p *(GtkWidget*)0x406952e8 > $6 = {object = {klass = 0x406952e0, flags = 1080644320, ref_count = > 136022416, > object_data = 0x81b8990}, private_flags = 21232, state = 105 'i', > saved_state = 64 '@', > name = 0x406952f0 "\220\211\e\b\220\211\e\bðRi@ðRi@Ðq\e\bÐq\e\b", > style = 0x81b71d0, requisition = {width = 29136, height = 2075}, > allocation = {x = 21248, y = 16489, width = 21248, height = 16489}, > window = 0x81433c8, parent = 0x81433c8} > (gdb) > > Does anyone have a clue how to find out why/when/who corrupts this hash > table? I think this is maybe the way to proceed? > Correcting the mailing list address. And one more question. If this corrupts the xid hash table then is there a chance that the crashes we've seen in applet_widget_construct() is the same case? I ask because that's the only place in 1.4.x I can find a call to gdk_window_lookup() besides the gwmh.c file. Cheers Kjartan
*** Bug 90073 has been marked as a duplicate of this bug. ***
*** Bug 90116 has been marked as a duplicate of this bug. ***
*** Bug 90119 has been marked as a duplicate of this bug. ***
your comments reflect where I have been looking as well... I am guessing that gwmh.c is corrupting the data. (and not gtk) gdk_window_ref_from_xid will create a new foreign window if gdk_window_lookup fails. I think this is a point where we could insert a dodgy gdkwindow into the hash. (is this confirmed in the stack trace I posted above whiche contains a crash on gdk_window_foreign_new ?) The other way is if it is just plain X voodoo. It is dissappointing that there is no GTK way of testing if the gdkwindow is valid. Maybe we need to run some XLib command to test this for us? As I have also commented above, in the gdk_window_foreign_new case we do not hold a reference on the window, as we do in the gdk_window_lookup case. This inconsistency must be part of the problem. Why do we even bother with gdk_window_foreign_new? Why not just return NULL if gdk_window_lookup fails? Is it a valid X scenario for us to get an xid that isn't in our gdk window hash yet? I can't try this out as my source tree is too messed up right now.
*** Bug 90167 has been marked as a duplicate of this bug. ***
*** Bug 90163 has been marked as a duplicate of this bug. ***
*** Bug 90265 has been marked as a duplicate of this bug. ***
*** Bug 90285 has been marked as a duplicate of this bug. ***
*** Bug 90289 has been marked as a duplicate of this bug. ***
*** Bug 90303 has been marked as a duplicate of this bug. ***
*** Bug 90376 has been marked as a duplicate of this bug. ***
*** Bug 90415 has been marked as a duplicate of this bug. ***
*** Bug 90587 has been marked as a duplicate of this bug. ***
*** Bug 90876 has been marked as a duplicate of this bug. ***
*** Bug 90802 has been marked as a duplicate of this bug. ***
*** Bug 90277 has been marked as a duplicate of this bug. ***
Wayne, the problem is that it returns a valid xid but the data in the window is corrupt. So, from gdk's point of view it's a perfectly valid window - at least that's my understanding of it. I'd love to get together and set up some debugging to fix this once and for all. wrt not holding a reference in the case you mentioned, that's not true. I talked to Tim about that and he said that gdk_window_foreign_new() handles that for us.
*** Bug 76057 has been marked as a duplicate of this bug. ***
*** Bug 91063 has been marked as a duplicate of this bug. ***
*** Bug 91217 has been marked as a duplicate of this bug. ***
*** Bug 91220 has been marked as a duplicate of this bug. ***
*** Bug 91376 has been marked as a duplicate of this bug. ***
*** Bug 91498 has been marked as a duplicate of this bug. ***
*** Bug 91522 has been marked as a duplicate of this bug. ***
*** Bug 91634 has been marked as a duplicate of this bug. ***
*** Bug 91969 has been marked as a duplicate of this bug. ***
*** Bug 91943 has been marked as a duplicate of this bug. ***
*** Bug 91754 has been marked as a duplicate of this bug. ***
*** Bug 91049 has been marked as a duplicate of this bug. ***
*** Bug 91743 has been marked as a duplicate of this bug. ***
*** Bug 92206 has been marked as a duplicate of this bug. ***
*** Bug 92232 has been marked as a duplicate of this bug. ***
*** Bug 90506 has been marked as a duplicate of this bug. ***
*** Bug 92213 has been marked as a duplicate of this bug. ***
*** Bug 92128 has been marked as a duplicate of this bug. ***
*** Bug 92255 has been marked as a duplicate of this bug. ***
*** Bug 92296 has been marked as a duplicate of this bug. ***
*** Bug 92291 has been marked as a duplicate of this bug. ***
*** Bug 92286 has been marked as a duplicate of this bug. ***
*** Bug 92319 has been marked as a duplicate of this bug. ***
*** Bug 92393 has been marked as a duplicate of this bug. ***
*** Bug 92447 has been marked as a duplicate of this bug. ***
*** Bug 92612 has been marked as a duplicate of this bug. ***
*** Bug 92688 has been marked as a duplicate of this bug. ***
*** Bug 92528 has been marked as a duplicate of this bug. ***
*** Bug 92756 has been marked as a duplicate of this bug. ***
*** Bug 92972 has been marked as a duplicate of this bug. ***
*** Bug 92986 has been marked as a duplicate of this bug. ***
*** Bug 92978 has been marked as a duplicate of this bug. ***
*** Bug 92933 has been marked as a duplicate of this bug. ***
*** Bug 93048 has been marked as a duplicate of this bug. ***
*** Bug 93063 has been marked as a duplicate of this bug. ***
*** Bug 93151 has been marked as a duplicate of this bug. ***
*** Bug 93231 has been marked as a duplicate of this bug. ***
*** Bug 93260 has been marked as a duplicate of this bug. ***
*** Bug 92999 has been marked as a duplicate of this bug. ***
*** Bug 92849 has been marked as a duplicate of this bug. ***
*** Bug 93339 has been marked as a duplicate of this bug. ***
*** Bug 93368 has been marked as a duplicate of this bug. ***
*** Bug 93400 has been marked as a duplicate of this bug. ***
*** Bug 93431 has been marked as a duplicate of this bug. ***
*** Bug 93432 has been marked as a duplicate of this bug. ***
*** Bug 93425 has been marked as a duplicate of this bug. ***
*** Bug 93571 has been marked as a duplicate of this bug. ***
*** Bug 93657 has been marked as a duplicate of this bug. ***
*** Bug 93472 has been marked as a duplicate of this bug. ***
*** Bug 93720 has been marked as a duplicate of this bug. ***
*** Bug 93788 has been marked as a duplicate of this bug. ***
*** Bug 93799 has been marked as a duplicate of this bug. ***
*** Bug 93868 has been marked as a duplicate of this bug. ***
*** Bug 93903 has been marked as a duplicate of this bug. ***
*** Bug 93936 has been marked as a duplicate of this bug. ***
*** Bug 94017 has been marked as a duplicate of this bug. ***
*** Bug 94076 has been marked as a duplicate of this bug. ***
*** Bug 94390 has been marked as a duplicate of this bug. ***
*** Bug 94137 has been marked as a duplicate of this bug. ***
*** Bug 94140 has been marked as a duplicate of this bug. ***
*** Bug 94187 has been marked as a duplicate of this bug. ***
*** Bug 94189 has been marked as a duplicate of this bug. ***
*** Bug 94192 has been marked as a duplicate of this bug. ***
*** Bug 94225 has been marked as a duplicate of this bug. ***
*** Bug 94244 has been marked as a duplicate of this bug. ***
*** Bug 94292 has been marked as a duplicate of this bug. ***
*** Bug 94297 has been marked as a duplicate of this bug. ***
*** Bug 94320 has been marked as a duplicate of this bug. ***
*** Bug 94369 has been marked as a duplicate of this bug. ***
*** Bug 94447 has been marked as a duplicate of this bug. ***
*** Bug 94474 has been marked as a duplicate of this bug. ***
*** Bug 94475 has been marked as a duplicate of this bug. ***
*** Bug 94492 has been marked as a duplicate of this bug. ***
*** Bug 94501 has been marked as a duplicate of this bug. ***
*** Bug 94553 has been marked as a duplicate of this bug. ***
*** Bug 94671 has been marked as a duplicate of this bug. ***
*** Bug 94632 has been marked as a duplicate of this bug. ***
*** Bug 93842 has been marked as a duplicate of this bug. ***
*** Bug 94604 has been marked as a duplicate of this bug. ***
*** Bug 94743 has been marked as a duplicate of this bug. ***
*** Bug 94723 has been marked as a duplicate of this bug. ***
*** Bug 94809 has been marked as a duplicate of this bug. ***
*** Bug 94959 has been marked as a duplicate of this bug. ***
*** Bug 94977 has been marked as a duplicate of this bug. ***
*** Bug 95076 has been marked as a duplicate of this bug. ***
*** Bug 95178 has been marked as a duplicate of this bug. ***
*** Bug 95182 has been marked as a duplicate of this bug. ***
*** Bug 95207 has been marked as a duplicate of this bug. ***
*** Bug 95304 has been marked as a duplicate of this bug. ***
*** Bug 95241 has been marked as a duplicate of this bug. ***
*** Bug 95284 has been marked as a duplicate of this bug. ***
*** Bug 95325 has been marked as a duplicate of this bug. ***
*** Bug 95090 has been marked as a duplicate of this bug. ***
*** Bug 95426 has been marked as a duplicate of this bug. ***
*** Bug 95622 has been marked as a duplicate of this bug. ***
*** Bug 95663 has been marked as a duplicate of this bug. ***
*** Bug 95672 has been marked as a duplicate of this bug. ***
*** Bug 90611 has been marked as a duplicate of this bug. ***
*** Bug 84103 has been marked as a duplicate of this bug. ***
*** Bug 57079 has been marked as a duplicate of this bug. ***
*** Bug 93003 has been marked as a duplicate of this bug. ***
*** Bug 80428 has been marked as a duplicate of this bug. ***
*** Bug 95702 has been marked as a duplicate of this bug. ***
*** Bug 95279 has been marked as a duplicate of this bug. ***
*** Bug 95880 has been marked as a duplicate of this bug. ***
*** Bug 95974 has been marked as a duplicate of this bug. ***
*** Bug 96065 has been marked as a duplicate of this bug. ***
*** Bug 96155 has been marked as a duplicate of this bug. ***
*** Bug 96274 has been marked as a duplicate of this bug. ***
*** Bug 96232 has been marked as a duplicate of this bug. ***
*** Bug 96517 has been marked as a duplicate of this bug. ***
*** Bug 79444 has been marked as a duplicate of this bug. ***
*** Bug 96856 has been marked as a duplicate of this bug. ***
*** Bug 96549 has been marked as a duplicate of this bug. ***
*** Bug 96589 has been marked as a duplicate of this bug. ***
Bug 96589 seems to have a slightly different stack trace with evidence of the typical 59500 problem of gdkwindow corruption: 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)...0x4054c4d9 in wait4 () from /lib/libc.so.6
+ Trace 29462
*** Bug 97026 has been marked as a duplicate of this bug. ***
*** Bug 97055 has been marked as a duplicate of this bug. ***
*** Bug 97339 has been marked as a duplicate of this bug. ***
*** Bug 97515 has been marked as a duplicate of this bug. ***
*** Bug 98020 has been marked as a duplicate of this bug. ***
*** Bug 98382 has been marked as a duplicate of this bug. ***
*** Bug 98534 has been marked as a duplicate of this bug. ***
*** Bug 98550 has been marked as a duplicate of this bug. ***
*** Bug 99040 has been marked as a duplicate of this bug. ***
*** Bug 99058 has been marked as a duplicate of this bug. ***
*** Bug 99392 has been marked as a duplicate of this bug. ***
*** Bug 99819 has been marked as a duplicate of this bug. ***
*** Bug 100267 has been marked as a duplicate of this bug. ***
*** Bug 80364 has been marked as a duplicate of this bug. ***
*** Bug 101061 has been marked as a duplicate of this bug. ***
*** Bug 101062 has been marked as a duplicate of this bug. ***
*** Bug 101101 has been marked as a duplicate of this bug. ***
*** Bug 101302 has been marked as a duplicate of this bug. ***
*** Bug 101463 has been marked as a duplicate of this bug. ***
*** Bug 101451 has been marked as a duplicate of this bug. ***
*** Bug 101612 has been marked as a duplicate of this bug. ***
*** Bug 101675 has been marked as a duplicate of this bug. ***
*** Bug 101871 has been marked as a duplicate of this bug. ***
*** Bug 101872 has been marked as a duplicate of this bug. ***
*** Bug 101935 has been marked as a duplicate of this bug. ***
*** Bug 102027 has been marked as a duplicate of this bug. ***
*** Bug 102426 has been marked as a duplicate of this bug. ***
*** Bug 102817 has been marked as a duplicate of this bug. ***
*** Bug 102901 has been marked as a duplicate of this bug. ***
*** Bug 102977 has been marked as a duplicate of this bug. ***
Because of the release of GNOME 2.0 and 2.2, and the lack of interest in maintainership of GNOME 1.4, the gnome-core product is being closed. If y0u feel your bug is still of relevance to GNOME 2, please reopen it and refile it against a more appropriate component. Thanks...
Argh. Apologies for the double spam. Actually closing this time.
*** Bug 106179 has been marked as a duplicate of this bug. ***
*** Bug 108920 has been marked as a duplicate of this bug. ***
*** Bug 109175 has been marked as a duplicate of this bug. ***
*** Bug 126590 has been marked as a duplicate of this bug. ***
*** Bug 127724 has been marked as a duplicate of this bug. ***
*** Bug 135171 has been marked as a duplicate of this bug. ***
*** Bug 138022 has been marked as a duplicate of this bug. ***
*** Bug 308545 has been marked as a duplicate of this bug. ***