<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel">
    <title>gmane.comp.window-managers.awesome.devel</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8331"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8330"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8329"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8328"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8327"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8326"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8325"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8324"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8323"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8322"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8321"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8320"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8319"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8318"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8317"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8316"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8315"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8314"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8313"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8312"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8331">
    <title>[awesome bugs] #1149 - Support focus per "tag" (or 'screen')</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8331</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#1149 - Support focus per "tag" (or 'screen')
User who did this - Uli Schlachter (psychon)

Reason for closing: Works for me
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1149

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-05-18T13:54:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8330">
    <title>[awesome bugs] #1149 - Support focus per "tag" (or 'screen')</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8330</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1149 - Support focus per "tag" (or 'screen')
User who did this - Tomas Pruzina (Mepho)

----------
Wohoa, lovely, exactly what I wanted.
Love.

TP
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1149#comment3586

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-05-18T12:50:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8329">
    <title>[awesome bugs] #1149 - Support focus per "tag" (or 'screen')</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8329</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1149 - Support focus per "tag" (or 'screen')
User who did this - Uli Schlachter (psychon)

----------
Uhm. Do I understand this correctly:

You want the focus to follow the mouse (sloppy focus), except when the mouse switches between screens. In this case you don't want the input focus to follow the mouse?

If this is correct, go to your rc.lua and inside the "manage" hook, change the following:

    -- Enable sloppy focus
    c:connect_signal("mouse::enter", function(c)
        if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
            and awful.client.focus.filter(c) then
            client.focus = c
        end
    end)

into:

    -- Enable sloppy focus
    c:connect_signal("mouse::enter", function(c)
        if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
            and awful.client.focus.filter(c) and (client.focus == nil or client.focus.screen == mouse.screen) then
            clien&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-05-17T16:00:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8328">
    <title>[awesome bugs] #1149 - Support focus per "tag" (or 'screen')</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8328</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Tomas Pruzina (Mepho) 

Attached to Project - awesome
Summary - Support focus per "tag" (or 'screen')
Task Type - Feature Request
Category - Core
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - Hi,

could awesome support focus 'per screen'?
I'm having multiple monitors (3) and one annoying thing I noticed is that when I move mouse over screens,
old client loses focus which breaks for example fullscreen flash or my libnotify notifications.
Is this 'fixable' withing awesome? or is this stuff managed by xlib/xcb?

Could anyone point me towards solution to this? Thanks in advance.

Tomas Pruzina 

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1149

You are receiving this message because you&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-05-17T15:25:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8327">
    <title>[awesome bugs] #1148 - tooltip_bg_color always set to normal bg (can't change tooltip bg_color)</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8327</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1148 - tooltip_bg_color always set to normal bg (can't change tooltip bg_color)
User who did this - ayman (mony)

----------
ended with
- self.wibox.bg = beautiful.tooltip_bg_color or beautiful.bg_focus or "#ffcb60"
+ self.wibox:set_bg(beautiful.tooltip_bg_color or beautiful.bg_focus or "#ffcb60")

thank you :)
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1148#comment3584

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-05-13T17:39:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8326">
    <title>[awesome bugs] #1148 - tooltip_bg_color always set to normal bg (can't change tooltip bg_color)</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8326</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#1148 - tooltip_bg_color always set to normal bg (can't change tooltip bg_color)
User who did this - Uli Schlachter (psychon)

Reason for closing: Fixed
Additional comments about closing: commit 14daf85fe91780e4ef49465c94e1cfb671391f0d
Author: Uli Schlachter &amp;lt;psychon&amp;lt; at &amp;gt;znc.in&amp;gt;
Date:   Mon May 13 19:27:19 2013 +0200

    awful.tooltip: Set the bg color correctly (FS#1148)
    
    Well, whoops. There is no .bg property on wiboxes for quite a while already, it
    is now a :set_bg member function.


More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1148

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-05-13T17:28:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8325">
    <title>[awesome bugs] #1148 - tooltip_bg_color always set to normal bg (can't change tooltip bg_color)</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8325</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - ayman (mony) 

Attached to Project - awesome
Summary - tooltip_bg_color always set to normal bg (can't change tooltip bg_color)
Task Type - Bug Report
Category - awful
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Normal
Reported Version - 3.5.1
Due in Version - Undecided
Due Date - Undecided
Details - theme.lua
https://github.com/mony960/dotfiles/blob/master/.config/awesome/themes/solarized/theme.lua
[code]
...
theme.tooltip_bg_color = "#586e75"
theme.tooltip_fg_color = "#fdf6e3"
...
[/code]

the bg color doesn't change
even if i changed 'self.wibox.gb' in tooltip.lua
its always set to theme.bg_normal

rc.lua if needed
https://github.com/mony960/dotfiles/blob/master/.config/awesome/rc.lua

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1148

You are receiving this message because &lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-05-13T17:10:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8324">
    <title>[awesome bugs] #1147 - Nested menus do not appear on the right-click menu.</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8324</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1147 - Nested menus do not appear on the right-click menu.
User who did this - Uli Schlachter (psychon)

----------
Your "menu3" is broken. Instead of

 { "menu3", { "submenu", terminal } }, 

you need

 { "menu3", { { "submenu", terminal } } }, 

However, even before this change, all the other parts of this work fine here. Since I don't have any good ideas: Could you attach your rc.lua?
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1147#comment3583

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-05-13T06:34:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8323">
    <title>[awesome bugs] #982 - Mouse events under non-English keyboard layout</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8323</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#982 - Mouse events under non-English keyboard layout
User who did this - Nikolaj Sjujskij (krigstask)

----------
Bug persists in Gentoo, and Xorg guys conclude that bug lurks in awesome: https://bugs.freedesktop.org/show_bug.cgi?id=50611#c7
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=982#comment3582

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-05-12T12:06:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8322">
    <title>[awesome bugs] #1147 - Nested menus do not appear on the right-click menu.</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8322</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Andrea Baisero (bais) 

Attached to Project - awesome
Summary - Nested menus do not appear on the right-click menu.
Task Type - Bug Report
Category - awful
Status - Unconfirmed
Assigned To - 
Operating System - Linux
Severity - Medium
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - Running awesome, the git/master version v3.5.1-1-g2d31033 on a fresh install of Ubuntu 13.04.

In rc.lua, every nested submenu (table of table) that I define ends up not appearing in the gui.
All direct menu options work fine.

For example:

[code]
myawesomemenu = {
   { "manual", terminal .. " -e man awesome" },
   { "edit config", editor_cmd .. " " .. awesome.conffile },
   { "restart", awesome.restart },
   { "quit", awesome.quit }
}
 
menu1 = {
   { "one", terminal },
   { "two", terminal },
   { "three", terminal }
}
 
menu2 = {
   { "one", termin&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-05-11T19:34:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8321">
    <title>[awesome bugs] #1145 - transparency with xcompmgr is broken</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8321</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#1145 - transparency with xcompmgr is broken
User who did this - Uli Schlachter (psychon)

Reason for closing: Won't fix
Additional comments about closing: The right fix for this would be to remove --no-argb. Not a good idea.

A better fix would be to only use ARGB visuals for frames of windows which themselves use an ARGB visual. I'd like to avoid this and instead have the various video drivers fixed...

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1145

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-05-04T15:39:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8320">
    <title>[awesome bugs] #1145 - transparency with xcompmgr is broken</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8320</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1145 - transparency with xcompmgr is broken
User who did this - Hannes (h2)

----------
&amp;lt; at &amp;gt;psychon: yeah, I was running with --no-argb in hope to fix a different issue. Taking that out fixes transparency again. I will close this.

&amp;lt; at &amp;gt;arnau: FreeBSD's libxcb is still at 1.7 and would need to be at 1.8 IIRC.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1145#comment3581

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-04-30T10:19:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8319">
    <title>[awesome bugs] #1145 - transparency with xcompmgr is broken</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8319</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1145 - transparency with xcompmgr is broken
User who did this - Arnaud Fontaine (arnau)

----------
A bit out of context, but I would be interested to know why unagi does not work on FreeBSD?
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1145#comment3580

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-04-30T01:04:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8318">
    <title>[awesome bugs] #1145 - transparency with xcompmgr is broken</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8318</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1145 - transparency with xcompmgr is broken
User who did this - Uli Schlachter (psychon)

----------
Ah, are you running awesome with the --no-argb? (If you have no idea what I am talking about, then you likely aren't)

If you use --no-argb, then non-working transparency is pretty much expected (Although I am not sure if you are seeing exactly this failure-pattern, do things like transset still work?).
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1145#comment3579

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-04-29T16:30:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8317">
    <title>[awesome bugs] #1144 - Floating windows resized improperly</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8317</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1144 - Floating windows resized improperly 
User who did this - Hannes (h2)

----------
killing xcompmgr has no effect....

Thanks for your help!
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1144#comment3578

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-04-28T20:56:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8316">
    <title>[awesome bugs] #1145 - transparency with xcompmgr is broken</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8316</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1145 - transparency with xcompmgr is broken
User who did this - Hannes (h2)

----------
Thanks for your reply. The video illustrates that the terminal is not transparent and the surrounding of the program launcher isn't either...

This was no problem with 3.4
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1145#comment3577

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-04-28T20:56:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8315">
    <title>[awesome bugs] #1146 - 3.5.1 crash when started using xdm on Freebsd.</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8315</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1146 - 3.5.1 crash when started using xdm on Freebsd.
User who did this - Uli Schlachter (psychon)

----------
No, you did not attach it.

Also, if it crashes, could you run awesome under valgrind and gdb and see if they have anything interesting to say?
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1146#comment3576

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-04-28T19:22:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8314">
    <title>[awesome bugs] #1146 - 3.5.1 crash when started using xdm on Freebsd.</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8314</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Michel (Troyax) 

Attached to Project - awesome
Summary - 3.5.1 crash when started using xdm on Freebsd.
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To - 
Operating System - FreeBSD
Severity - Critical
Priority - Normal
Reported Version - 3.5.1
Due in Version - Undecided
Due Date - Undecided
Details - Awesome crash when started using xdm, but I can use other window manager (like wmaker).
I tried to run awesome through Xnest and it worked without any problems.
Attached is my xsession-errors after the crash.

My Xorg version:
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 9.1-RELEASE amd64 
Current Operating System: FreeBSD zangetzu 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec  4 09:23:10 UTC 2012     root&amp;lt; at &amp;gt;farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
Build Date: 11 March 2013  11&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-04-28T17:39:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8313">
    <title>[awesome bugs] #1144 - Floating windows resized improperly</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8313</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1144 - Floating windows resized improperly 
User who did this - Uli Schlachter (psychon)

----------
Since you are saying you are using xcompmgr: How much of this bug disappears when you are not using xcompmgr but "plain old X11"?
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1144#comment3575

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-04-28T12:25:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8312">
    <title>[awesome bugs] #1145 - transparency with xcompmgr is broken</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8312</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1145 - transparency with xcompmgr is broken
User who did this - Uli Schlachter (psychon)

----------
Wrong link to video? Or what am I supposed to look at in that video?

Also, I can't do anything about xcompmgr being broken (and it really is known to be broken a lot).
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1145#comment3574

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-04-28T12:20:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8311">
    <title>[awesome bugs] #1145 - transparency with xcompmgr is broken</title>
    <link>http://permalink.gmane.org/gmane.comp.window-managers.awesome.devel/8311</link>
    <description>&lt;pre&gt;THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Hannes (h2) 

Attached to Project - awesome
Summary - transparency with xcompmgr is broken
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - Since 3.5 the transparency provided by xcompmgr doesn't work anymore. I know there is unagi, but it doesn't yet work on FreeBSD and possibly there are other reasons for using xcompmgr ..

Also, see this screencast: http://soulrebel.in-berlin.de/awesome_yakuake.ogv

Thanks for your help!

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&amp;amp;task_id=1145

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, yo&lt;/pre&gt;</description>
    <dc:creator>awesome</dc:creator>
    <dc:date>2013-04-28T11:43:05</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.window-managers.awesome.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.window-managers.awesome.devel</link>
  </textinput>
</rdf:RDF>
