THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#772 - Window flickering and visual artifacts with 3.4.5
User who did this - Stjujsckij Nickolaj (krigstask)

----------
@Julien
Could you do a git bisect between 3.4.4 and 3.4.5

Yep, I think I could, but not soon I'm afraid (I'm not that much of git expert 
and awesome-git guy). But of course, if nobody except me is affected, then it's 
my duty, I understand (-:E


@Uli
For visual artifacts, I always love to blame the X server (or kernel mode 
setting). Are we really sure this doesn't have to do anything with it?

Yes, that's obvious thoughts, but 3.4.4 works fine on the very same system. Checked it several 
times: 3.4.5 flickers -> downgrade & restart awesome with hotkey -> 3.4.4 behaves fine. 
Or: run 3.4.4 in one console -> upgrade -> run 3.4.5 in other session -> see the 
flickering.
Of course, 3.4.5 could reveal some bug in Xorg or something.

For the taskbar: Do you happen to be using any transparency anywhere?
Aye, I have pseudotransparency set in theme. But again: for 3.4.4 it worked 
fine. On the screenshot you could see indeed three urxvt buttons painted above 
four (three previously painted + one just opened).

Oh and could you attach your config so we can test this ourselves?
Sorry, forgot about it. Browse it here: 
http://code.google.com/p/krigstasks-samling/source/browse?repo=awesome
It's quite a bit of vanilla one, and I'm going to test standard one and report 
results.
I'll attached theme file too, just in case.

Thanks for feedback, by the way.
----------

One or more files have been attached.

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

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