← Back to team overview

desktop-packages team mailing list archive

[Bug 463168] Re: gnome-panel crashes with a BadPixmap X error


** Changed in: gnome-panel (Debian)
       Status: Confirmed => Fix Released

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.

  gnome-panel crashes with a BadPixmap X error

Status in Desktop panel for GNOME:
Status in “gnome-panel” package in Ubuntu:
Status in “gnome-panel” package in Debian:
  Fix Released

Bug description:
  Binary package hint: gnome-panel

  Regularly, gnome-panel crashes and is then restarted immediately. It
  still noticeable because some icons in the notification area are lost

  Here are some interesting logs in the .xsession-errors :

  The program 'gnome-panel' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadPixmap (invalid Pixmap parameter)'.
    (Details: serial 30701 error_code 4 request_code 54 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.)

  There are so far two different things causing this crash :

  * Wine applications having a notification area icon
  The regular crash is caused by Lotus Notes running in Wine showing up a notification area icon upon receiving a new mail. Since I disabled this notification, no more crashes.

  * Quitting Transmission through it's notification area icon, as
  described by the referenced debian bug.

  So this BadPixmap error is definitely linked to the notification area,
  probably by client applications corrupting their notification area

  However, there should be enough sanity checks in gnome-panel (or the
  notification area applet) so that it doesn't crash.

To manage notifications about this bug go to: