mageiawelcome uses gtk+2.0 and webkit. It should use gtk+3.0 and webkit2. Especially usage of webkit results in a lot of extra space in the GNOME images (rest of GNOME uses webkit2). Reproducible: Steps to Reproduce:
Assignee: bugsquad => napcok
Keywords: (none) => Triaged
I will try to do that for MGA6.
Status: NEW => ASSIGNEDWhiteboard: (none) => OK
Target Milestone: --- => Mageia 6
I've a year old WIP patches that I've sent to author. There's signal looping issue though
CC: (none) => thierry.vignaud
Keywords: (none) => PATCH
Created attachment 7036 [details] automatic conversion from gtk2 to gtk3
Created attachment 7037 [details] Gdk is needed too
Created attachment 7038 [details] fix automatic conversion for WebKit
Created attachment 7039 [details] fix import warnings with latest gi
Created attachment 7040 [details] fix a deprecation warning
Created attachment 7041 [details] kill uneeded import
Created attachment 7042 [details] workaround sizing loop issue with gtk+3
I've attached my last year's patches plus more patches on top (fixing warnings with mga6's python-gi/gnome-3.1[68] I've workarounded the sizing loop issue by adding a ScrolledWindow
@Daniel: do you want me to "git push" those?
Created attachment 7043 [details] workaround sizing loop issue with gtk+3 (reaping an unrelated/uneeded debuging change)
Attachment 7042 is obsolete: 0 => 1
(In reply to Thierry Vignaud from comment #11) > @Daniel: do you want me to "git push" those? Yes please push.
Fixed in git
Now it just needs to be ported to python3 :-)
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
CC: (none) => yves.brungard_mageia
Ok, I can take care of the port to Python 3.