THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#662 - awesome.restart crash
User who did this - Matthew Schoolmaster (msch)

----------
I can confirm it is no longer happening for me.  I think it was the libxcb 
updates that hit debian on April 13th (to 1.6-1) as I was still having this bug 
shortly after I built on March 29th.  Just a hunch though...

Currently:

awesome --version
awesome v3.4.4-17-ge6a1f8b (Jet Sex)
• Build: Mar 29 2010 11:06:00 for x86_64 by gcc version 4.4.3 (r...@claire)
• D-Bus support: ?

apt-show-versions | grep libxcb
libxcb-atom1/testing uptodate 0.3.6-1
libxcb-atom1-dev/testing uptodate 0.3.6-1
libxcb-aux0/testing uptodate 0.3.6-1
libxcb-aux0-dev/testing uptodate 0.3.6-1
libxcb-event1/testing uptodate 0.3.6-1
libxcb-event1-dev/testing uptodate 0.3.6-1
libxcb-icccm1/testing uptodate 0.3.6-1
libxcb-icccm1-dev/testing uptodate 0.3.6-1
libxcb-image0/testing uptodate 0.3.6-1
libxcb-image0-dev/testing uptodate 0.3.6-1
libxcb-keysyms1/testing uptodate 0.3.6-1
libxcb-keysyms1-dev/testing uptodate 0.3.6-1
libxcb-property1/testing uptodate 0.3.6-1
libxcb-property1-dev/testing uptodate 0.3.6-1
libxcb-randr0/testing uptodate 1.6-1
libxcb-randr0-dev/testing uptodate 1.6-1
libxcb-render-util0/testing uptodate 0.3.6-1
libxcb-render-util0-dev/testing uptodate 0.3.6-1
libxcb-render0/testing uptodate 1.6-1
libxcb-render0-dev/testing uptodate 1.6-1
libxcb-shape0/testing uptodate 1.6-1
libxcb-shape0-dev/testing uptodate 1.6-1
libxcb-shm0/testing uptodate 1.6-1
libxcb-shm0-dev/testing uptodate 1.6-1
libxcb-xinerama0/testing uptodate 1.6-1
libxcb-xinerama0-dev/testing uptodate 1.6-1
libxcb-xtest0/testing uptodate 1.6-1
libxcb-xtest0-dev/testing uptodate 1.6-1
libxcb-xv0/testing uptodate 1.6-1
libxcb1/testing uptodate 1.6-1
libxcb1-dev/testing uptodate 1.6-1

----------

More information can be found at the following URL:
http://awesome.naquadah.org/bugs/index.php?do=details&task_id=662#comment1976

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.

--
To unsubscribe, send mail to [email protected].

Reply via email to