362107 - The program 'thunderbird-bin' received an X Window System error

Status: RESOLVED WORKSFORME

(Thunderbird :: General, defect)

Description

[Nir]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061126 Minefield/3.0a1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061126 Minefield/3.0a1

Using TB-3a1 under Fedora core 5.

while trying to start TB from console window (Yakuake), TB failed to start and console window shows this error message:

[root@localhost ~]# cd /usr/thu*
[root@localhost thunderbird]# ./thunderbird
The program 'thunderbird-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 1159 error_code 3 request_code 20 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.)


although on 2nd attempt TB ( using --sync ) opens normally 

Reproducible: Didn't try

Steps to Reproduce:
1.open TB from console window .



Actual Results:  
TB fails to load and Console window shows an error message

Expected Results:  
Thunderbird should open normally

I haven't yet succeeded to reproduce it and haven't occurred before . As i have mentioned already that on 2nd attempt TB opens normally .

Comment 1

[Nir]

This problem occurred again after a crash ( id - TB26795396W ), console window shows same error message.

Comment 2

[Nir]

Attachment: Screen shot of Console window containing error message

Comment 3

[thinksimilar]

Using 2.0.0.0 (20070326) (tar from mozilla.com) on Ubuntu 7.04, over ssh -X

everett@quitefeisty:~$ mozilla-thunderbird &
[2] 5572
everett@quitefeisty:~$ The program 'thunderbird-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2064 error_code 3 request_code 20 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.)

[2]+  Exit 1                  mozilla-thunderbird

(mozilla-thunderbird is a shell script in my /usr/bin that does:

cd /opt/thunderbird
./thunderbird

)


Running it a second time in the same way resulted in it working as expected.

Comment 4

[Jean Monnat]

I have similar problem with icedove version 2.0.0.19 on Debian. Here below the error message.

The program 'gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 66301 error_code 3 request_code 20 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.)

Program exited with code 01.
(gdb)
Thanks

Comment 5

[Jason Oster (:Parasyte)]

I just got this on a nightly build trying to restart Thunderbird after installing a new calendar nightly:

Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.1pre) Gecko/20090710 Lightning/1.0pre Shredder/3.0b3pre

Shown in the console during the restart:

The program 'thunderbird-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 384 error_code 3 request_code 20 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.)

Comment 6

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

I wonder if this might be related to libraries in any way. Running the command in Ubuntu has consistently worked for me in the past months. Does this still occur consistently and reproducibly for folks in recent days? (If so, please elaborate and give STR)

Comment 7

[Jason Oster (:Parasyte)]

Sorry, this has not been reproducible for me.  The one time I got this error, I posted all the information I could get out of it.

Comment 8

[Joshua Cranmer [:jcranmer]]

RESOLVED WFM per comment 7.