jmc-88/tint3

BadPixmap errors

Closed this issue · 8 comments

gijsbers commented

Still getting these:

 -> Xlib error (4): BadPixmap (invalid Pixmap parameter)
 -> Xlib error (4): BadPixmap (invalid Pixmap parameter)
 -> Xlib error (4): BadPixmap (invalid Pixmap parameter)
 -> Xlib error (4): BadPixmap (invalid Pixmap parameter)
 -> Xlib error (4): BadPixmap (invalid Pixmap parameter)
 -> Xlib error (4): BadPixmap (invalid Pixmap parameter)
 -> Xlib error (4): BadPixmap (invalid Pixmap parameter)

It's a developer-only message. User has no clue what to do about it.
Should he be concerned or not??? etc. Where to start?

jmc-88 commented

Agreed, this is not really useful. I might consider printing these only on Debug builds, for a start.
Still, they shouldn't occur. May I see your configuration (if you're not using the default, that is) so to help pinpoint where the problem lies?

gijsbers commented

The BadPixmap occur always, also with the default config. Here is mine:
tint3rc.zip
Sometimes I also get BadWindow:

 -> Xlib error (4): BadPixmap (invalid Pixmap parameter)
 -> Xlib error (3): BadWindow (invalid Window parameter)
 -> Xlib error (3): BadWindow (invalid Window parameter)
 -> Xlib error (4): BadPixmap (invalid Pixmap parameter)
jmc-88 commented

I'm not sure when those errors might be occurring, as I'm having trouble reproducing.
I've add more verbose error logging in 68043f5, perhaps you can run a Debug build for me and report back on that? At least I'll see what X request is causing those, which is a weak signal, but still better than nothing.

gijsbers commented 
Real transparency: off, depth: 24
NO XSETTINGS manager, tint3 use config 'launcher_icon_theme'.
 -> Xlib error: BadPixmap (invalid Pixmap parameter)
XErrorEvent {
  error_code:   4
  request_code: 56
  minor_code:   0
  resourceid:   0
}
 -> Xlib error: BadPixmap (invalid Pixmap parameter)
XErrorEvent {
  error_code:   4
  request_code: 56
  minor_code:   0
  resourceid:   0
}
 -> Xlib error: BadWindow (invalid Window parameter)
XErrorEvent {
  error_code:   3
  request_code: 20
  minor_code:   0
  resourceid:   54525962
}
 -> Xlib error: BadWindow (invalid Window parameter)
XErrorEvent {
  error_code:   3
  request_code: 20
  minor_code:   0
  resourceid:   50331658
}
 -> Xlib error: BadPixmap (invalid Pixmap parameter)
XErrorEvent {
  error_code:   4
  request_code: 56
  minor_code:   0
  resourceid:   0
}
 -> Xlib error: BadPixmap (invalid Pixmap parameter)
XErrorEvent {
  error_code:   4
  request_code: 56
  minor_code:   0
  resourceid:   0
}
 -> Xlib error: BadPixmap (invalid Pixmap parameter)
XErrorEvent {
  error_code:   4
  request_code: 56
  minor_code:   0
  resourceid:   0
}
jmc-88 commented

On the off chance that you're still willing to test this, I pushed some changes which might or might not help (they do help on cases which I managed to reproduce, but they might not coincide with yours, especially the BadWindow one). If you can, please try running a Debug build and post the results.

A word of warning though:

  • 5781cf6 made X11 operations synchronous in Debug builds, which also means they're slower.
  • 9ed0a0d made X11 errors fatal in Debug builds, so if there's still some it would kill tint3 in the process; please only use this when debugging issues, and rely on Release binaries for normal operation.
gijsbers commented 
$ tint3
Real transparency: off, depth: 24
NO XSETTINGS manager, tint3 use config 'launcher_icon_theme'.
X Error of failed request:  BadPixmap (invalid Pixmap parameter)
  Major opcode of failed request:  56 (X_ChangeGC)
  Resource id in failed request:  0x0
  Serial number of failed request:  736
  Current serial number in output stream:  737
jmc-88 commented

Ah, I forgot about the GC errors, but those I could not reproduce.
At this point, may I ask you more about your setup? (Distro, WM or DE, I take it you're not running a compositor, etc...)

jmc-88 commented

No activity on this, assuming fixed. Please reopen if still occurring.