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 71213 - Panel crashed while looking at menus
Panel crashed while looking at menus
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: panel
1.5.x
Other other
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 80607 82932 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-02-11 22:22 UTC by David Hampton
Modified: 2015-03-24 13:00 UTC
See Also:
GNOME target: Old
GNOME version: ---


Attachments
stacktrace from crash (textshell) (2.00 KB, text/plain)
2002-05-06 17:07 UTC, martin H.
Details

Description David Hampton 2002-02-11 22:22:07 UTC
Package: gnome-core
Severity: normal
Version: 1.5.7
Synopsis: Panel crashed while looking at menus
Bugzilla-Product: gnome-core
Bugzilla-Component: panel
BugBuddy-GnomeVersion: 2.0 (1.110.1)

Description:
Description of Problem:
I was looking at the applications menu when the panel crashed.


Steps to reproduce the problem:
1. Pull down app menu.  While holding mouse button down, move up and
down the list.
2. 
3. 

Actual Results:
Crash

Expected Results:
See menus pop up and go away.

How often does this happen?
First time.  Haven't tried to recreate yet.

Additional Information:




Debugging Information:

[New Thread 1024 (LWP 1178)]
0x40921a49 in __wait4 () from /lib/i686/libc.so.6

Thread 1 (Thread 1024 (LWP 1178))

  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 621
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 g_type_check_instance_cast
    at gtype.c line 2600
  • #7 load_icons_handler
    at menu.c line 779
  • #8 g_idle_dispatch
    at gmain.c line 3123
  • #9 g_main_dispatch
    at gmain.c line 1616
  • #10 g_main_context_dispatch
    at gmain.c line 2155
  • #11 g_main_context_iterate
    at gmain.c line 2236
  • #12 g_main_loop_run
    at gmain.c line 2456
  • #13 gtk_main
    at gtkmain.c line 793
  • #14 main
    at main.c line 245
  • #15 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 621
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 g_type_check_instance_cast
    at gtype.c line 2600
  • #7 load_icons_handler
    at menu.c line 779




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-02-11 17:22 -------

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

Comment 1 Roy-Magne Mo 2002-02-11 22:57:59 UTC
tagging as gnome2
Comment 2 Mark McLoughlin 2002-02-12 09:10:19 UTC
Yes, I've seen this before - couldn't figure it out at the time
though.

I think it may have something to do with unreffed GtkImage not being
taken off the icon list.
Comment 3 Luis Villa 2002-02-14 04:44:09 UTC
Mark: is this bug 69596? That seems to indicate the problem is fixed
in CVS...
Roy/guape: BTW, while you're sticking keywords in, make sure all
feature requests are marked 'enhancement' and crashes are 'critical.'
Just one more way to save me time ;)
Comment 4 Mark McLoughlin 2002-02-14 16:18:23 UTC
Luis: oh yeah, it is - well the second trace in #69596 anyway. The
first one is fixed ..
Comment 5 Mark McLoughlin 2002-02-19 18:48:06 UTC

*** This bug has been marked as a duplicate of 71816 ***
Comment 6 Mark McLoughlin 2002-02-19 18:50:59 UTC
Note, this is not a duplicate 71816 ...

wrong button clicked :(
Comment 7 Arvind S N 2002-02-26 11:59:48 UTC
Not simulatable in panel version 1.5.10
Comment 8 Luis Villa 2002-02-26 15:15:23 UTC
Mark, David: is this fixed? Please close if so. [Sounds like it is,
but perhaps I'm a bit unclear.]
Comment 9 David Hampton 2002-03-02 22:53:14 UTC
Yes, but I haven't been able to upgrade in a while.  I've been using the
packages from red-carpet's Gnome 2 Snapshot, and I can't update anything
because all the Gnome 1 packages require atk-0.11 and all the Gnome 2
packages require atk-0.13 (one of several similar problems.)
Comment 10 Luis Villa 2002-03-03 06:00:22 UTC
David: hrm... RC may be saying that, but I'm almost 100% certain that
isn't the case, since atk isn't a part of the 1.4 platform. :) What
package is it saying needs the older atk?
Comment 11 David Hampton 2002-03-03 19:13:12 UTC
	libatk.so.11   is needed by
gnome-applets-1.91.1.0.200202062313-snap.ximian.1
	libatk.so.11   is needed by gnome-utils-1.98.0.0.200202062313-snap.ximian.1
	libatk.so.11   is needed by gnome-core-1.5.7.0.200202062313-snap.ximian.1
	libatk.so.11   is needed by eog-0.110.0.0.200202062313-snap.ximian.1
	libatk.so.11   is needed by gdm-2.3.90.1.0.200202062313-snap.ximian.1
	libatk.so.11   is needed by bug-buddy-2.1.3.0.200202062313-snap.ximian.1
	libatk.so.11   is needed by gnome-games-1.90.1.0.200202062313-snap.ximian.1
	libatk.so.11   is needed by
libpanel-applet2-1.5.7.0.200202101248-snap.ximian.1
Comment 12 Luis Villa 2002-03-03 19:43:46 UTC
Hrm. All of those should be being upgraded as well, right? Are you
trying to upgrade them as well or just specific programs? For what
it's worth, in the edit menu, Red Carpet has a 'check all' option;
that may or may not help the case. If that doesn't work, you should be
able to safely 'rpm -e --force atk' and then immediately do the
upgrade from redcarpet [note that this will break things until you
upgrade everything, of course :)
Comment 13 David Hampton 2002-03-03 22:02:26 UTC
They should be being upgraded, but they're not. OTOH, I now see
packages like gnome-applets2, eog2, etc., so maybe there was a small
window where these files had the wrong name and I got hit by it.  I'll
try to back out these files and then see where I am.
Comment 14 David Hampton 2002-03-03 23:18:29 UTC
All packages updated.  I don't see this problem any more.
Comment 15 Luis Villa 2002-03-04 01:04:18 UTC
Closing then. Thanks for helping out, David.
Comment 16 martin H. 2002-05-06 17:06:19 UTC
Hallo I still have this Problem (v-b-s(head); annoncvs; last rebuild 
all (from 'scratch') Apr 30 14:32; last update from panel May  5 
20:56)

First I admit it hard to reproduce. Almost a heisenbug ;-).

But I got I one time without trying, that's why I'm reporting this 
one.
Ok the best way to reproduce is from my experience:
	1. have a panel ready with a Gnome-menu
	2. Open the Menu
	3. move the mouse fast up and down at the 1st level of the
	   menu while shifting the mouse a bit left and right so
	   that it opens a submenu sometimes.
	4. Continue until you get a nice gnome-segv2 dialog.

Yeah, I admit it's not really that usual use pattern of the panel, 
but an idle user sometimes does strange things(seems people select 
random things on the screen or just play with the menus 
(menu-surfing?)).

So I think this bug should be reopened.

I'll attach a stacktrace from my system:
Comment 17 martin H. 2002-05-06 17:07:27 UTC
Created attachment 8236 [details]
stacktrace from crash (textshell)
Comment 18 Luis Villa 2002-05-10 04:50:25 UTC
*** Bug 80607 has been marked as a duplicate of this bug. ***
Comment 19 Luis Villa 2002-05-10 04:50:51 UTC
Reopening.
Comment 20 George Lebl 2002-05-17 21:44:35 UTC
Found it, whacked it ... (or so I think, can you still verify?)

It had to do with the icons to load being added twice to the queue,
this could happen if the map on the image happened twice before the
idle ran.
Comment 21 David Hampton 2002-05-18 07:14:10 UTC
I don't see th eproblem anymore.
Comment 22 Mark McLoughlin 2002-05-27 00:08:18 UTC
*** Bug 82932 has been marked as a duplicate of this bug. ***