On Sun, Feb 08, 2004 at 10:47:47AM +1100, Scott Smedley wrote: |Hi Xavier, | |> are you able to reproduce the bug ? | |No. I just tried it on my RH7.3 system. |
In my tries (4 Fvwmtabs holding 6 xterms each), I'm able to reproduce the bug only if fvwmtab is focused... i don't know really if this is linked or not. .xsession-errors : FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs: Window doesn't exist. FvwmTabs (v2.8) started with: Perl 5.8.2, X11::Protocol 0.52, Tk 800.024. _cdim: --- not moved 0x0815ba68 'FvwmTabs [0]' xterm: warning, error event received: xterm: warning, error event received: X Error of failed request: BadDrawable (invalid Pixmap or Window parameter) Major opcode of failed request: 76 (X_ImageText8) Resource id in failed request: 0x7400018 Serial number of failed request: 3747 Current serial number in output stream: 3747 X Error of failed request: BadDrawable (invalid Pixmap or Window parameter) Major opcode of failed request: 76 (X_ImageText8) Resource id in failed request: 0x8800018 Serial number of failed request: 35796 Current serial number in output stream: 35796 xterm: warning, error event received: X Error of failed request: BadDrawable (invalid Pixmap or Window parameter) Major opcode of failed request: 76 (X_ImageText8) Resource id in failed request: 0x1e00018 Serial number of failed request: 15531 Current serial number in output stream: 15531 -- xavier -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
