Distribution: Fedora Core release 2 (Tettnang)
Package: gnome-panel
Severity: normal
Version: GNOME2.6. 2.6.x
Gnome-Distributor: Red Hat, Inc
Synopsis: gnome-panel crashes when trying to add multiple background images at once
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
Bugzilla-Version: 2.6.x
Description:
Description of Problem:
gnome-pannel crashed.

Steps to reproduce the problem:
1. have gnome-panel running
2. Open up gnome-background-properties
3. click add Wallpaper
4. Select more than one image and click open (one image at a time seems
to not crash)

Actual Results:
gnome-panel crashed and disappeared. I can restart it manually though.


Expected Results:
No crash.

How often does this happen?
as often as i try to add multiple wallpapers. (completely reproducible
on my machine)


Additional Information:
[aiv@dhcp0010 ~]$ gnome-panel

Suspended
[aiv@dhcp0010 ~]$ bg
[aiv@dhcp0010 ~]$ The program 'gnome-panel' received an X Window System
error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 7224 error_code 13 request_code 62 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.)

[1]    Exit 1                        gnome-panel




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-16 11:12 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-panel".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was aiv@seas.upenn.edu.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.