Bug 531568 - Tooltip appearance crashes gnome panel on any but first display
Summary: Tooltip appearance crashes gnome panel on any but first display
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-28 19:15 UTC by Bill Crawford
Modified: 2009-11-04 18:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-04 18:30:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Backtrace from panel crash under compiz (18.62 KB, text/plain)
2009-10-31 16:21 UTC, Bill Crawford
no flags Details
Backtrace under metacity with compositing (5.73 KB, text/plain)
2009-10-31 16:22 UTC, Bill Crawford
no flags Details

Description Bill Crawford 2009-10-28 19:15:45 UTC
Description of problem:
"The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program."

Version-Release number of selected component (if applicable):
gnome-panel-2.28.0-11.fc12.x86_64


How reproducible:
Hold mouse over a button on the panel and it crashes. Only happens on screens 2 and 3, not first. Doesn't happen if I disable tooltips on the panel. I'm using compiz and emerald, which might contribute?

Steps to Reproduce:
1. Start gnome session with compiz as window manager.
2. Hover over button on panel on screen 2 or screen 3.
3. Watch it disappear and then reappear. Ad nauseam ... :)
  
Actual results:
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 7640 error_code 8 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

** (gnome-panel:9013): WARNING **: panel-applet-frame.c:1288: failed to load applet OAFIID:GNOME_WindowListApplet:
Failed to invoke method on the ActivationContext
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 7958 error_code 8 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

** (gnome-panel:9037): CRITICAL **: panel_applet_frame_change_background: assertion `PANEL_IS_WIDGET (GTK_WIDGET (frame)->parent)' failed

Expected results:
Panel fails to crash when hovering mouse over panel.

Additional info:
System fully up to date as of about 19:00 UTC today, including:
gnome-panel-2.28.0-11.fc12.x86_64
compiz-0.8.2-18.fc12.x86_64
compiz-fusion-0.8.2-4.fc12.x86_64
compiz-fusion-extras-0.8.2-2.fc12.x86_64
emerald-0.8.2-2.fc12.x86_64

Comment 1 Bill Crawford 2009-10-28 19:16:31 UTC
IIRC -12 build from koji does the same but fixes the padding issue on the panel.

Comment 2 Matthias Clasen 2009-10-29 03:02:46 UTC
You did not tell me what version of gtk2 you see this with. 
Would be good to try with gtk2-2.18.3-15.fc12 from koji.
And when you say screen 2 or 3, do you really mean screens, or monitors ?

Comment 3 Bill Crawford 2009-10-29 17:16:39 UTC
Whatever gtk 2 was current when I updated from rawhide Tuesday evening, and I really mean screens (:0.1 and :0.2).

Comment 4 Bill Crawford 2009-10-29 17:22:13 UTC
(I can't actually check the gtk2 directly without rebooting into the install as I'm currently in F8 which won't even mount the filesystem).

Comment 5 Bill Crawford 2009-10-30 20:46:01 UTC
Happening with gtk2-2.18.3-15.fc12.x86_64 too, sorry. Only happens with compiz and not with metacity, though, so of course it's entirely possible there's actually a bug in compiz or the X server :o)

I'm a bit puzzled why abrt doesn't seem to pick up on this ...

Comment 6 Matthias Clasen 2009-10-30 20:51:26 UTC
The panel is not crashing, it is exiting from the X error handler, thats why abrt does not catch this. 

Can you try doing what the error message recommends, and run the panel under gdb with --sync, and break in the X error handler ? That would be helpful.

Also, do you get the same crash with metacity when you turn on the metacity compositor with

gconftool-2 --type bool --set /apps/metacity/general/compositing_manager true

?

Comment 7 Bill Crawford 2009-10-31 16:19:12 UTC
Yes, and yes. Attaching in a moment ...

Comment 8 Bill Crawford 2009-10-31 16:21:31 UTC
Created attachment 366941 [details]
Backtrace from panel crash under compiz

I did "up" and "info locals" to get as much detail as possible, please tell me if there's anything else will help (but it may be a few days before you hear anything more :o)).

Comment 9 Bill Crawford 2009-10-31 16:22:32 UTC
Created attachment 366943 [details]
Backtrace under metacity with compositing

Looked about the same.

Comment 10 Matthias Clasen 2009-10-31 19:19:19 UTC
Oh, I think I know whats going on.

Can you try if this build fixes the problem ? 

http://koji.fedoraproject.org/koji/taskinfo?taskID=1780403

Comment 11 Bill Crawford 2009-11-02 18:38:37 UTC
Result :o) that fixes it.

[ on another note ... how do I turn off tooltips for the "window list" applet? ]

Comment 12 Matthias Clasen 2009-11-02 18:53:26 UTC
I'm not sure that you can turn them off, unfortunately.

But thanks for testing.

Comment 13 Bill Crawford 2009-11-03 08:55:32 UTC
Thanks for fixing it!

Comment 14 Bill Crawford 2009-11-04 18:17:34 UTC
The bugzilla front page says "You reported this bug, a change has been committed and you should verify the problem is fixed" and it seems to suggest I should change the status of the bug in some way, but I can only see 'CLOSED' as an option to change to. What should I do please?

Comment 15 Matthias Clasen 2009-11-04 18:30:08 UTC
Let me just close it now, since the fix was confirmed.


Note You need to log in before you can comment on or make changes to this bug.