* Josh Rickmar (joshua_rick...@eumx.net) wrote:
starup-notification was updated, and I've just committed update of
awesome to 3.3-rc2. This should have no problems with new xcb-util.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber:
On Fri, 8 May 2009, Dmitry Marakasov wrote:
* Josh Rickmar (joshua_rick...@eumx.net) wrote:
starup-notification was updated, and I've just committed update of
awesome to 3.3-rc2. This should have no problems with new xcb-util.
Thanks!
Yeah, I saw the update to 3.3-rc2 and the new
* Josh Rickmar (joshua_rick...@eumx.net) wrote:
That's quite complicated problem actually - xcb-util update has
broken awesome; we could update awesome to 3.3-rc1, but it requires
startup-notification 0.10 (which likely requires new xcb-util as
well).
Thus we'll likely have to wait for s-n 0.10
On Fri, 8 May 2009, Dmitry Marakasov wrote:
* Josh Rickmar (joshua_rick...@eumx.net) wrote:
That's quite complicated problem actually - xcb-util update has
broken awesome; we could update awesome to 3.3-rc1, but it requires
startup-notification 0.10 (which likely requires new xcb-util as
On Thu, 2009-05-07 at 18:39 -0400, Josh Rickmar wrote:
On Fri, 8 May 2009, Dmitry Marakasov wrote:
* Josh Rickmar (joshua_rick...@eumx.net) wrote:
That's quite complicated problem actually - xcb-util update has
broken awesome; we could update awesome to 3.3-rc1, but it requires
* Robert Noland (rnol...@freebsd.org) wrote:
That's quite complicated problem actually - xcb-util update has
broken awesome; we could update awesome to 3.3-rc1, but it requires
startup-notification 0.10 (which likely requires new xcb-util as
well).
Thus we'll likely have to wait for
I've been following the discussions on awesome's IRC channel lately, and
there have been a lot of problems with users not being able to use their
modkey. It turned out that the problem was that a newer version of
xcb-util (0.3.4) conflicts with the current released stable version of
awesome.
