thunderbird crashes with gecko error if run over ssh
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
thunderbird (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: thunderbird
SSHing in to a server running Karmic with X (tests OK using xcalc) and attempting to run thunderbird gets the following error. Logging this under thunderbird because there is no "gecko" program listed by apt-cache. Note that neither server nor client are running another copy of thunderbird and that the server is not even running X:
Last login: Sat Nov 14 09:55:03 2009
vik@vik:~$ thunderbird &
[1] 8323
vik@vik:~$ The program 'gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 275 error_code 2 request_code 140 minor_code 3)
(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 thunderbird
ProblemType: Bug
Architecture: i386
Date: Sat Nov 14 10:34:39 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelMo
Package: thunderbird 2.0.0.23+
ProcEnviron:
PATH=(custom, user)
LANG=en_NZ.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: thunderbird
Uname: Linux 2.6.31-14-generic i686
XsessionErrors: (polkit-
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.04). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 482373, and any other logs that are relevant for this particular issue.