Since, IIRC, gtk+3.0-3.11.6-1.mga5, ttx isn't rendered well anymore. The left and right border have needlessly grown a lot. Instead of clicking on a link in the colored part of the screen, it is now needed to click ± 4 cm to the left (or, more precisely, the amount of cms the left and right border have grown) I don't manage to find out why. Upstream couldn't reproduce it. I tried in several DEs with several themes (oxygen-gtk, black Mate, adwaita), but they all had this problem. Reproducible: Steps to Reproduce:
Whiteboard: (none) => NEEDHELP
the problem exists for all teletext services, except for the Italian on: for that one TTX looks and works normal
I'm considering obsoleting this package before Mga5 release, I don't have time to dig into what causes this bug, and maybe not even to remove the default NOS teletext service, which has become unusable. Otoh, if I still use it (it is quite usable once you know when you have to click ± 4cm to the left of the item you want to click), there might be some others who still use it, too.... and once obsoleted it cannot be added back to Mageia 5, if it does get fixed. @ Florian, @ Remco WDYT?
CC: (none) => doktor5000, remco
Well, it's probably a better idea to obsolete it. You could still offer it via e.g. pete910's FTP: http://mageia.unrealnetworks.co.uk/ if you like, or if anyone asks, you could send him the package. Unfortunately I'm not into GTK so can't help that much ...
(In reply to Florian Hubold from comment #3) > Well, it's probably a better idea to obsolete it. You could still offer it > via e.g. pete910's FTP: http://mageia.unrealnetworks.co.uk/ if you like, or > if anyone asks, you could send him the package. > > Unfortunately I'm not into GTK so can't help that much ... added it to task-obsolete and moved it to obsoletes Closing as WONTFIX, even if I might reopen it if I find time I should at least look at what the differences in gtk+3 are between fedora and us, because upstream said ttx kept working fine in Fc with the gtk+3 version and higher that introduced the bug, here.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX