THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added:
FS#1112 - Notifications with icons cause awesome to block User who did this - Uli Schlachter (psychon) ---------- Could you launch dbus-monitor and get me the raw data for some of these? Awesome handles these notifications in lua and gets the pixel data as a string. (For 3.5) it then has to convert this pixel data into a cairo image surface and for that it does some substring-and-reverse-string-magic which can't possibly be fast. It might be possible to add a "fast path" if the pixel data already matches what cairo expects, but I fear that this is just way too different from what the notification spec dictates. Of course, someone has to make sure that it really is this part which is slow (dunno how I can easily generate such a notification to test), but it seems like the most likely cause to me. ---------- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1112#comment3446 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 awesome-devel-unsubscr...@naquadah.org.
