Re: [compiz] Window specific actions and edge buttons
David Reveman wrote: On Tue, 2007-05-15 at 00:29 +0100, Mike Dransfield wrote: There is a problem with some window specific actions like scale_group and rotate_with_window when they are activated by an edgebutton. The basic problem is that each of those actions use the window option provided to the action. When an edgebutton is used the window id sent is actually the id of the edge window, this means that actions which rely on this stop working. The obvious solution would be to change the affected functions to work on the active window rather that the one passed to the action. Yes, I think that's what should be done. OK - I did that for those two. I am just about to push out similar changes for close_window, minimize_window and maximize_window. If they reduce some functionality then please let me know and I will write it so that it checks for an edge and only uses activeWindow then. If close_window is used with edge+edgebutton then it crashes which is obviously a problem elsewhere. Is it fairly obvious to you where this bug would be? Otherwise I'll track that down too, I assume it must be just a case of setting the correct allowed actions hint on edges? It could also be possible to modify the actions higher up to ignore edge windows, but I suppose some people might want that functionality. - David ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
[compiz] compiz segfaults on starting second X server / suspend to ram
Hello, when I start a second X server or when I suspend (and resume) to ram compiz crashes. I tryed to debug this but its impossible to run gdb on compiz (=freeze). This happens with current git, but If I remember correctly not with 0.3.6 (and git versions 0.5.0 but I don't know when it started to happen). any ideas? ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] kde-window-decorator crashes
Diogo Ferreira wrote: Silvan Calarco wrote: Hi, I've updated compiz to the 0.5.0 release and since my release 0.3.something I keep on seeing seldom crashes from kde-window-decorator when running it both on Xorg with AIGLX+nvidia card and Xorg+Xgl+ATI card. The crashes most often happen at desktop login and when loading certain applications (kmail, kaffeine, ...). The strange thing is that if I try to attach to kde-window-decorator with gdb it doesn't crash anymore! What might be the reason? If anybody can tell how I can make more debugging and give you more information. The distribution is openmamba. Thanks, Silvan ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz Hi, now that you mention kde-window-decorator I thought I would refer something I notice from time to time and is quite annoying. I believe it's a problem across all libdecoration because I also get this with metacity on two (very) different setups (nvidia/64bits and ati/32bits). By metacity I meant gwd. What happens is that after some time of using the decorators the decorations stall, if I click a window it takes input focus but the decoration stays as if it wasn't. I guess more people have this problem ? Maybe someone who knows about libdecoration can offer some insight. Regards, Diogo ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] compiz segfaults on starting second X server / suspend to ram
Hello, when I start a second X server or when I suspend (and resume) to ram compiz crashes. I tryed to debug this but its impossible to run gdb on compiz (=freeze). This happens with current git, but If I remember correctly not with 0.3.6 (and git versions 0.5.0 but I don't know when it started to happen). any ideas? It is possible to debug compiz using gdb, you just can't run gdb in a terminal drawn by compiz. The simplest way is to run it remotely through ssh. If you don't have another computer at your disposal, it's still possible to run gdb+compiz on another VT, but you'll need to utilize the kernel's Magic SysRq key to escape from the freeze (to get back to the console). You can find more info on both ways (plus one more which doesn't seem to be much reliable) on these links: http://forum.compiz.org/viewtopic.php?p=111 http://www.ubaight.com/pipermail/compcomm/2007-May/000639.html [Thanks to the author of the latter post! I haven't heard about the key combination before.] I'd add that the SysRq key combinations may not be available by default, it depends on kernel compiling configuration and it can be turned on/off in addition. I don't know the various kernels, see your kernel documentation for details. For example, on my Fedora Core 6, the support is compiled in, but must be turned on as described in /usr/share/doc/kernel-doc-2.6.20/Documentation/sysrq.txt. And the situation is still a bit more tricky with nVidia because of its VT-switching bug (I may be wrong here), I solved this by switching to the X VT very very fast after the run command :-) ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
