mini-dweeb.org projects: Issueshttps://projects.mini-dweeb.org/https://projects.mini-dweeb.org/favicon.ico?16699090422012-03-24T19:16:20Zmini-dweeb.org projects
Redmine Unagi Compositing Manager - Bug #44 (New): Unagi fail to apply alpha mask for Wibox in AwesomeWMhttps://projects.mini-dweeb.org/issues/442012-03-24T19:16:20ZEmmanuel Lepage Vallee
<p>Hi,</p>
<p>I have seen there is new work on unagi, so I took some time to try it. To make some test, I tried to prototype this<br /><a class="external" href="http://kde-look.org/content/show.php/BeClock?content=117542">http://kde-look.org/content/show.php/BeClock?content=117542</a><br />and this<br /><a class="external" href="http://rmbiggs.files.wordpress.com/2010/06/ipaddropdownmenu2.png?w=630">http://rmbiggs.files.wordpress.com/2010/06/ipaddropdownmenu2.png?w=630</a></p>
<p>Both failed. The menu regressed from non composited awesome while the "clock" prototype show a dark square when opacity is enabled. It have been tested in Awesome 3.4.11.</p>
<p>Screenshots (with and without unagi) and code is attached to this bug</p>
<p>(ps: the blue square and arrows are there only when dragging a client with tabbar, I show them only to point you that the arrow alpha mask is fine, somehow)</p> Unagi Compositing Manager - Bug #43 (New): segfault when bringing guake window in fronthttps://projects.mini-dweeb.org/issues/432012-03-23T00:22:32Zflo stoeffelmayr
<p>Guake is a top-down terminal for Gnome (in the style of Yakuake for KDE, Tilda or the terminal used in Quake).</p>
<p>It is written in python, and I do not think it uses a special window type - maybe I am wrong...</p>
<pre><code>unagi output:<br />WARN: event_handle_error:186: X error: request=DamageCreate (major=152, minor=1, resource=140066a), error=BadDrawable<br />WARN: event_handle_error:186: X error: request=DamageCreate (major=152, minor=1, resource=e00099), error=BadDrawable<br />WARN: event_handle_error:186: X error: request=DamageSubtract (major=152, minor=3, resource=2a0003f), error=BadDamage<br />WARN: event_handle_unmap_notify:636: Window 1c00023 disappeared<br />Segmentation fault (core dumped)</code></pre>
<p>I am using ubuntu precise pangolin, in a virtual box virtual machine, with pure vesa graphics.</p>
<p>I tried to use gdb, but that freezes the machine when I do sth with guake.. no keyboard or mouse events possible then - acpi shutdown works though</p> Unagi Compositing Manager - Bug #41 (New): Not playing well with conky if "own_window" is turned ...https://projects.mini-dweeb.org/issues/412012-02-22T12:33:49ZRichard Grenville
<p>If unagi is started, and I have "double_buffer" turned on and "own_window" turned off in .conkyrc, all windows vanish when conky updates; If I turn off both "double_buffer" and "own_window", conky does not get rendered correctly, sometimes conky gets rendered on the top of all windows, sometimes the new graph overlaps on the old graph. Turning "own_window" on in .conkyrc fixes it. So essentially if conky tries to draw on the root window when unagi is on, weird things start happening. At first I thought it was a conflict related to fvwm, yet eventually found it's conky.</p>
<p>It's probably not an issue of unagi itself, though, because xcompmgr has the same problem with its default compositing mode. I prefer to run conky with "own_window" turned off since then I could open fvwm's root menu when clicking on conky.</p>
<p>I noticed nothing really wrong in the output of unagi, but the log is attached, anyway.</p> Unagi Compositing Manager - Bug #39 (New): Does not work with traditional window movement method ...https://projects.mini-dweeb.org/issues/392012-02-22T12:13:52ZRichard Grenville
<p>unagi-0.3 and the current git version fail to render a window correctly on my fvwm 2.6.3 after I move the window when I'm using the default window movement method in fvwm.</p>
<p>Basically fvwm provides two window movement methods: "traditional rubber-band outline" movement and opaque movement. Opaque movement is how most modern window managers behave: When the user uses a mouse to drag a window, the window's content gets moved altogether. The traditional method is, however, displaying an outline showing to where a window will to be moved when the window is dragged, and only actually moving the window's content after the user releases his mouse button. The traditional approach is default behavior in fvwm <em>(as it probably did not change its behaviors much since it was forked from twm in 1993...)</em> and theoretically could save some CPU cycles.</p>
<p>Unfortunately I found unagi feels uncomfortable when dealing with the traditional window movement in fvwm (which I have gotten used to). After a window is moved, if I have unagi running, some parts of the window does not get rendered. The attached file unagi-fvwm-trad-movement-issue.png shows what happens after I move the urxvt window in the middle.</p>
<p>When the problem appears unagi also prints some warning messages about CompositeNameWindowPixmap and such. The output of unagi (built with the debugging option) is attached. You could use "grep -v DEBUG" to find out the warning messages.</p>
<p>Fvwm by default uses a similar mechanism when resizing a window, so the problem appears after a window resize, too.</p>
<p>This is not a very important problem after all. Fvwm does not have many users currently, and will never have many. Thus low in priority.</p>
<p>By the way, seemingly unagi works pretty well in Openbox, and I'm glad to see there's an alternative to the broken xcompmgr or memory-hogging cairo-compmgr.</p> Unagi Compositing Manager - Bug #36 (Feedback): configure.ac autogen error https://projects.mini-dweeb.org/issues/362012-02-17T09:29:55Zjorge perez
<p>tryed to generat config file but</p>
<p>configure.ac:9: error: possibly undefined macro: AM_INIT_AUTOMAKE<br /> If this token and others are legitimate, please use m4_pattern_allow.<br /> See the Autoconf documentation.<br />configure.ac:10: error: possibly undefined macro: AM_MAINTAINER_MODE<br />configure.ac:22: error: possibly undefined macro: AC_LIBTOOL_DLOPEN<br />configure.ac:23: error: possibly undefined macro: AC_PROG_LIBTOOL<br />configure.ac:108: error: possibly undefined macro: AM_CONDITIONAL</p>
<p>debug info <br />git-t/unagi [ autoconf --trace=AC_INIT configure.ac master ] 3:23 AM<br />configure.ac:4:AC_INIT:unagi:0.3:Arnaud Fontaine <<a class="email" href="mailto:arnau@mini-dweeb.org">arnau@mini-dweeb.org</a><br />and<br />git-t/unagi [ autoconf --trace='AC_INIT:version is $2' master ] 3:24 AM<br />version is 0.3</p>
<p>"That generally means that the package had an overquoted macro in its<br />configure.ac."</p> Unagi Compositing Manager - Bug #35 (New): Painting issue with the background wallpaper on startuphttps://projects.mini-dweeb.org/issues/352012-02-14T13:47:50ZArnaud Fontaine
<p>Hey there Arnud,</p>
<p>When i start up xorg/awesome the screen is black, and i have to move the terminal window around to refresh those areas.</p>
<p>Screen shots attached. Let me know how i can help you debug this.</p>
<p>Thanks!!</p>
<p>gentoo kernel 3.2.1<br />x86_64 intel core 2 quad Q9300 8g ram<br />xorg 1.11.2-r2<br />nvidia-drivers: 290.10<br />nvidia 8800 GT</p> Unagi Compositing Manager - Bug #31 (New): Warning about XFixeshttps://projects.mini-dweeb.org/issues/312012-02-03T09:58:29ZMarc Dequènes
<p>Another bunch of unidentified warnings linked with no special action i can remember:<br /><pre>
WARN: event_handle_error:186: X error: request=XFixesCreateRegionFromWindow (major=148, minor=7, resource=1000468), error=BadWindow
WARN: event_handle_error:186: X error: request=XFixesTranslateRegion (major=148, minor=17, resource=2426083), error=BadRegion
WARN: event_handle_error:186: X error: request=XFixesUnionRegion (major=148, minor=13, resource=2426083), error=BadRegion
WARN: event_handle_error:186: X error: request=XFixesDestroyRegion (major=148, minor=10, resource=2426083), error=BadRegion
WARN: event_handle_error:186: X error: request=XFixesCreateRegionFromWindow (major=148, minor=7, resource=1c02f32), error=BadWindow
WARN: event_handle_error:186: X error: request=XFixesTranslateRegion (major=148, minor=17, resource=242657d), error=BadRegion
WARN: event_handle_error:186: X error: request=XFixesUnionRegion (major=148, minor=13, resource=242657d), error=BadRegion
WARN: event_handle_error:186: X error: request=XFixesDestroyRegion (major=148, minor=10, resource=242657d), error=BadRegion
WARN: event_handle_error:186: X error: request=XFixesCreateRegionFromWindow (major=148, minor=7, resource=1c02f32), error=BadWindow
WARN: event_handle_error:186: X error: request=XFixesTranslateRegion (major=148, minor=17, resource=242657e), error=BadRegion
WARN: event_handle_error:186: X error: request=CompositeNameWindowPixmap (major=152, minor=6, resource=1c02f32), error=BadWindow
WARN: event_handle_error:186: X error: request=XFixesUnionRegion (major=148, minor=13, resource=242657e), error=BadRegion
WARN: event_handle_error:186: X error: request=XFixesDestroyRegion (major=148, minor=10, resource=242657e), error=BadRegion
</pre></p> Unagi Compositing Manager - Bug #30 (New): Warning about pixmaphttps://projects.mini-dweeb.org/issues/302012-01-31T16:16:25ZMarc Dequènes
<p>Another strange warnings:<br /><pre>
WARN: event_handle_error:186: X error: request=CompositeNameWindowPixmap (major=152, minor=6, resource=2070c76), error=BadMatch
WARN: event_handle_error:186: X error: request=FreePixmap (major=54, minor=0, resource=2c0041c), error=BadPixmap
</pre></p>
<p>I try to add empty lines to the output to better see when messages appears, but without timestamps i cannot be 100% sure they came at the same time.</p> Unagi Compositing Manager - Bug #28 (New): DamageSubtract warninghttps://projects.mini-dweeb.org/issues/282012-01-31T13:05:44ZMarc Dequènes
<p>I don't think i reported this one. I got it only once since this morning, but don't know what triggered it.</p>
<pre>
WARN: event_handle_error:186: X error: request=DamageSubtract (major=153, minor=3, resource=2c0bb87), error=BadDamage
</pre> Unagi Compositing Manager - Enhancement #22 (New): Do not paint windows behind an opaque windowhttps://projects.mini-dweeb.org/issues/222012-01-05T03:38:34ZArnaud Fontaine
<p>For performance reasons, any windows behind an opaque one should not be painted at all. This should greatly improved performances when using for example the max layout of Awesome.</p> Unagi Compositing Manager - Bug #17 (Assigned): expose ignores window shape (and most likely "rea...https://projects.mini-dweeb.org/issues/172010-02-14T09:45:55ZUli Schlachter
<p>If you open xeyes and press F12, behind the xeyes window there is a scaled down version of the background image.</p>
<p>This might be fixed by using XRender for scaling windows, I think (feel free to correct me).</p>