I will run gaim and it will work for a while. Normally when my message window loses focus because I'm on the web and I click back to my message window all gaim windows disappear. When I run it from the command line I get messages like this: The program 'gaim' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 27021 error_code 3 request_code 10 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.) I have tried to run it through gdb after recompiling it and having it not stripped. It won't let me break on gdk_x_error, and when it dies, I try to get a backtrace and it says that there is no stack. This seemed to happen some time around gtk+2.4.0, though I have NO idea if that was the cause. I'm also running the latest gnome which I removed from the packages.mask though my problem existed before this upgrade. Reproducible: Always Steps to Reproduce: 1. Run gaim (presently gaim-0.75-r11) 2. Keep clicking on contacts, and opening new message windows and closing them. Sometimes clicking on a 3rd party software like gnome-terminal. 3. Repeate #2 for less than a minute and gaim goes away. Actual Results: If gaim was run from the command line, all of the gaim windows disappear and the output of gaim is generally like this: The program 'gaim' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 27021 error_code 3 request_code 10 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.) Expected Results: Gaim should have kept running. I'm not really sure if there's more information I can give until it's requested. It could very well be a supporting library that I need to up/downdgrade? I'll wait to see what ideas you guys can throw at me.
I'd like to see you try to duplicate this on a lower version of gnome/glib/gtk+ or even a different WM if you don't want to downgrade gnome. gnome/glib/gtk+ upgrades have been the cause of many problems with many packages lately.
I am on a fairly slow machine so I would prefer not to be doing any large compiles to go back versions. However, if it helps anyone else that may run into this problem, it seems to be isolated to the mouse gestures plugin. It also exists back into -r8. I turned off that plugin and I can no longer cause the bug to occure. I'm willing to live with this until what I'm running is considered stable. I'll miss my mouse gestures, but at least it's stable again. That is unless this sheds new light onto the problem and you want to see if we can fix it the way it is. As I said, this machine is too slow to be doing much upgrading and downgrading when I don't have to. Thanks,
The gaim devs tell me that it might be upstream since they don't have much faith in the mouse gestures plugin to begin with. Do you think your bug might be related to this: http://sourceforge.net/tracker/?group_id=235&atid=100235&func=detail&aid=735859
I'm waiting to chat with the dev who wrote the Mouse Gestures plugin. I'll let you know afterwards. We may be sending this upstream.
Apparently I had a mail problem and my last response didn't get to here. The forementioned bug you pointed me to doesn't appear to be the same problem, at least not directly. Gaim does not crash when actually using Mouse Gestures, it just crashes when it's loaded. But I'm not actually attempting to do any mouse gestures. So what does that mean that you may be sending me upstream?
Can you see if this happens with gaim-0.76 as well?
Yep, it still happens in 0.76
I have a similar problem with gkrellm over ssh: $ ssh <host> gkrellm2 Xlib: extension "RENDER" missing on display "localhost:12.0". The program 'gkrellm2' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 2556 error_code 3 request_code 38 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.) I fixed it by adding the following to /etc/portage/package.mask: >=dev-libs/glib-2.4.0 >=x11-libs/gtk+-2.4.0 >=x11-libs/pango-1.4.0 >=net-misc/openssh-3.8_p1
The problem is with the new openssh-3.8_p1 - the fix is to use the -Y switch, new with openssh-3.8. The alternative is to add the following line to /etc/ssh/ssh_config: ForwardX11Trusted yes I suggest that the ebuild for openssh-3.8_p1 be changed to add that line to /etc/ssh/ssh_config, even if commented, so that users know about it.
On a completely separate note, thank you very much about that ssh information. I believe you may have just fixed a separate problem I had with my encrypted x2x setup I have and openssh 3.8!
Jerry were you running gaim via ssh X11 forwarding? I don't see how the openssh issue is of consequence to this bug otherwise.
No, I'm really sorry, my other openssh problem had absolutely nothing to do with my gaim problem. I was just glad to have fixed my other problem.
20:25 < grim> rizzo: it's probably something to do with gdk_drawables.. have you user enable the plugin, but turn off the visual drawing or whatever the pref is named.. Can you try it and disable visuable gesture display? Be sure to upgrade to gaim-0.77
I am running gaim-0.77. I turned on mouse gestures again to verify it would fail like normal. It did. I went into the settings, removed the visual gestures check and I've been trying to crash it but so far I have been unable to. It 'appears' to have fixed the problem. If you would like for me to hammer it a bit more before we are sure that it is the problem I'll gladly give a report a little later in the day.
It's gone on two days or so, and no crash with mouse gestures turned on, but visual gestures turned off. I'd say that's definitely the problem.
Many thanks, guys! 1. turning off 'visual' mode solved gaim problem for me. 2. adding -Y solved the openSSH problem (with same error code) All the best! Alex
Jerry can you get a backtrace from gaim-0.77-r2 with this crash. I can't duplicate it any more for some reason.
and be sure you build gaim with USE="debug"
Also upgrade to gtk+-2.4.1 if you haven't already.
I still get no backtrace when this crashes like this. If I file gaim. /usr/bin/gaim: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.1, dynamically linked (uses shared libs), not stripped Then I gdb gaim (gdb) run Starting program: /usr/bin/gaim warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. Detaching after fork from child process 8996. Detaching after fork from child process 8997. Detaching after fork from child process 8998. The program 'gaim' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 21325 error_code 3 request_code 10 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) bt No stack. I am running gaim-0.77-r2 (+debug) and gtk+-2.4.1
13:11 #gaim: < ChipX86> rizzo: that's a known bug, but I've never been able to find the cause of it 13:52 < ChipX86> rizzo: I've never been able to figure that out :/ 13:52 < ChipX86> may just disable that So I'm marking this upstream. I wouldn't file a bug with them as Chip is probably just going to remove the visualization anyway.
Thanks guys, as long as I have mouse gestures, I don't care if I can see them or not.
