>On the other hand I know development resources are limited and I won't blame you if you decide it's not worth the effort because of the very few people it affects, and the fact that it's AMD's fault not Ubuntu's.
this is something I don't understand, sorry. I caused a regression, and I will fix it. I don't care about how difficult it might be, or how many times I'll have to ask you to test a fix, but if you agree, lets trace this issue to the bottom, and then forward the issue upstream. I did a new test build, since the difference between the working one and the bad one are 4 patches, and two of them are just null pointer checks, I disabled one of the two, in particular: "upstream/8d58c890646fc1f43bcab702bb9ed6bae94daefe.patch" this patch changes a little bit the API to get the gl context, so maybe since the proprietary drivers are old, it might be causing your issue. The other patch that might be source of troubles is this one: debian/patches/upstream/b3b8bd9af7bf1fcfe544fd131f4d4f0d117ae7bc.patch because of this change: -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libepoxy in Ubuntu. https://bugs.launchpad.net/bugs/1698233 Title: New libepoxy0 causes hang at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1698233/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
