So, does that mean that it doesn't matter if something doesn't work with
proprietary driver?
I can't use radeon driver due to it's instability on this particular
card. I have no other choice than using this proprietary driver and I
believe I'm not the only one in such situation.
I see no reason why qtcreator should not work with this proprietary
driver while everything else does work. I.e. it looks like a bug in
qtcreator/Qt/QML, not the driver.
I already tested this on other machine with open source driver. I can't
reproduce it there. Yes, it's graphics-driver-specific. What's the point
of trying to reproduce it on radeon driver when I can reproduce it in
100% of cases on fglrx-driver?
I can try to find out if it's issue with qtcreator or with Qt/QML. Some
pointers what to try would be helpful, I'm not familiar with Qt and QML.
Thanks,
Martin
On 12.2.2015 03:22, Lisandro Damián Nicanor Pérez Meyer wrote:
On Wednesday 11 February 2015 14:30:51 Martin Kourim wrote:
See inline.
[snip]
Which driver are you using for it?
fglrx-driver (1:14.9+ga14.201-2) from non-free
A proprietary driver, that's what I've expected :)
Did you test it in another machine with different video specs?
Yes, I can't reproduce this issue on my ThinkPad x220 with Intel graphics.
Please try to reproduce the bug without the proprietary driver, ie, using the
radeon one.
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54dc6e40.9050...@gmail.com