On Tue, 26 Jun 2012 00:45:08 +0200 thomasg <tho...@gstaedtner.net> said:
> On Wed, Jun 20, 2012 at 2:49 PM, Michael Blumenkrantz > <michael.blumenkra...@gmail.com> wrote: > > If you have an e17 bug, reply to this mail or create a ticket for it on > > trac. This is the LAST call. Hint hint. > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > I still have a weird bug when using AMDs proprietary fglrx driver. > It very likely is just a driver bug, but everyone else seems to work > around it (or for whatever reason not affected), and there's just no > possibility to get it fixed upstream (because upstream doesn't give a > f***). > > When e17s composite module is enabled, every Cairo window goes > "semi-translucent", meaning that every pixel drawn uses some alpha > channel and windows/backgrounds behind bleed through. driver issue. the driver cares about the alpha pixel value BUT it doesnt PAD it with 0xff as an argb texture. with gl_blend disabled it still cares and hasn't done the padding so u get this result. so the upper byte of the pixel (MSB) should be 0xff. applications dont bother filling it as 0xff as they say "hey - i have no alpha channel. what are u talking about? i never heard of these things!" but the gl pipeline and compositor care. there may be a workaround, but as i swore off anything ati after my last round of craptasticness from fglrx, it won't be me doing anything about it. > Putting a black background behind the window makes the problem > "disappear", because everything looks exactly as it should then. > I strongly assume that it only affects cairo, because all E stuff as > well as all Qt stuff is fine, while most Gtk stuff and Firefox aren't. > For Firefox this means not only the Gtk menu elements, but also the > rendered sites which should also be drawn by cairo. > Some examples of affected applications: Firefox, Gimp, LibreOffice, > Gvim, Wireshark > Not all elements of every applications are affected. Sometimes white > planes stay non-translucent, often menuelements/toolbars do. Generally > images seem not affected. > > I'd be happy to provide more information or screenshots if requested. > > ~thomasg > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
