nautilus-sendto gets X BadWindow error when launching thunderbird

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

What videocard and videodrive do you use? Do you use the desktop effects option?

It also affects me for a while (on gusty, hardy, ...).
Always with compiz enable.
On my two laptops:
nvidia for the first:
glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4

ati for the second.
fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1700
OpenGL version string: 2.1.8087 Release

I will try to get more info (backtraces)

when I desactivate compiz, I have no problem

I can't get a backtrace: I create a breakpoint when I debug thunderbird (break gdk_x_error as they say), but the debugger never stop when the problem occur.

If you have some ideas, you're welcome.

To reproduce the bug:
in a console, run nautilus-sendto <file>. If no problem does no occur, I change of desktop and then I come back to the desktop that contains the console and I run the command once again.

With compiz activated of course.

appears to be compiz related as this happens with not just thunderbird and reporter states that compiz makes this go away.

Moreover it seems to be a problem of timing:
* when I launch, using alt-f2, firefox -profilemanager or thunderbird -profilemanager, I often get nothing. But if I selected 'run in command line', the firefox/thunderbird always appears.
* when I run nautilus-sendto within gdb I rarely get the described error; it seems that gdb slows down a few nautilus-sendto and the problem disappears.

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

still observe the same random working of the package
2.6.28-11-generic on 64
ubuntu jaunty
You find strace of the process;

I'm using nautilus script to realize the same function and this works systematically;
nautilus-sendto can't even be eliminated from distribution, because ubuntu-desktop needs nautilus-sendto ;

script :
name : send-thunder
°°°°°°°°°°
#!/bin/sh
# spedisce come allegato di posta di thunderbird

thunderbird -compose attachment="file://$NAUTILUS_SCRIPT_SELECTED_FILE_PATHS"
 °°°°°°°°°°

made executable in .gnome2/nautilus-scripts and having installed nautilus-scripts

but no way to execute nautilus-sendto in a regular way

Paolo

This issue is still here on jaunty for me with the same configs.

Seeing how Firefox 3.5 fixed this problem I'm guessing Thunderbird 3.0 will as well since it's most likely something with xulrunner going weird.

I have same problem in Karmic with firefox/swiftfox. Compiz enabled.

Seems indeed to be some timing issue, because when running FF/SF from the icon in menu/docky, it never appears, running just swiftfox/firefox command from terminal 99% of the times produces error message and no program running, but if I add --sync to the command line then most of the times (~ 90% ) brauser will run.

Oh, and when run from commandline without --sync, it shows profile selector window and then gets error.

will post this and come back with error message.

errormessage:

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

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 it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]