Description of problem: When using the schematics editor of kicad, there's a display/refresh problem leaving a trail of crosshairs all over the place where the mouse goes. The problem is described here: https://bugs.launchpad.net/kicad/+bug/1461698 and the conclusion there is that this is not a bug in kicad but in wxgtk3, which happens specifically and only when wxgtk3 is built against gtk3 as opposed to gtk2 which (according to the page) is the default. They go on explaining that WXGTK doesn't work correctly with GTK3 and shouldn't be built with GTK3 but with (the default) GTK2. Ref: another mention of this bug encountered too by another mga user in a bug report for another bug (old kicad version): https://bugs.mageia.org/show_bug.cgi?id=16402 Version-Release number of selected component (if applicable): lib64wxgtkugl3.0_0-3.0.2-7.mga6 , wxgtk-3.0.2-7.mga6 , kicad-4.0.1-4.mga6 How reproducible: always Steps to Reproduce: 1. install kicad 2. observe crosshair cursor bug within kicad in the schematics editor (leaving a trace of crosshairs all over the place where the mouse goes) 3.
Summary: wxgtk: diplay problems probably due to being built against gtk3 instead of (default) gtk2 => wxgtk: diplay problems in kicad probably due to being built against gtk3 instead of (default) gtk2
as mentioned in the above mentioned bug report page for kicad, in order to check the strong "build wxgtk against gtk2, not gtk3" conveyed by the page linked by Milan, I just built wxgtk3 (using gtk2) and kicad 4.0.2 from source tarballs (and into a prefix dir to keep it separated), and as expected, the above mentioned display problems are all gone, kicad works perfectly. => my suggestion is the same as that of that page: build wxgtk against gtk2, not gtk3.
Summary: wxgtk: diplay problems in kicad probably due to being built against gtk3 instead of (default) gtk2 => wxgtk: display problems due to use of gtk3 instead of (default) gtk2, as seen e.g. in kicad
Assigning to all packagers collectively, since there is no maintainer for wxgtk
CC: (none) => marja11Assignee: bugsquad => pkg-bugs
Additional Info: 1) apart from the canvas rendering problem that occurs in kicad, multiple sources found while googling for this, say that wxgtk3 built against gtk3 also has other gui bugs not occurring in wxgtk3 builds against gtk2, e.g. widget sizing and resizing issues and refresh issues. I could reproduce a re-sizing bug here with filezilla. Other examples: this page mentions such wxgtk3+gtk3 bugs occurring in applications including GRASS, GNUMed, Cura, OpenSTV, Pronterface, Taskcoach and Timeline : http://osdir.com/ml/wx-users/2015-02/msg00020.html 2) Solution options: While many seem to advocate to only build wxgtk3 against gtk2 (never against gtk3) and many distributions handle it like this (Nick Ãstergaard lists among them: Archlinux, slackware (on slackbuilds.org), debian, ubuntu), there's another possible solution: fedora handles this problem differently: they added a package compat-wxGTK3-gtk2 that is a wxgtk3 built against gtk2
Building wxgtk against Gtk+2.0 isn't a long-term solution, as it also links webkit, so a Gtk+2.0 build will forever be married to the old, dead, insecure webkit1 (2.4.x). Although the Gtk+3.0 build also is currently, it at least has some hope of being ported to webkit2 at some point (the version 4 API).
There is always in our repo a wxgtk2.8 who is built against GTK+2.0 if it can help.
CC: (none) => geiger.david68210
(In reply to David Walser from comment #4) yeah well i'm all for gtk3 (as opposed to gtk2) in the long-term, and i sure hope for the day when the gtk3 backend of wxgtk3 will work as much as you heed your hope to see the day where webkit1 is replaced with webkit2. But until then, the problem in the short-term remains: wxgtk3 doesn't function correctly when built against gtk3. And the only working short-term solution is having a wxgtk3 that's built against gtk2. A wxgtk that works _now_ with gtk2 doesn't mean one has to give up the hope that it will work later/long-term with gtk3 and webkit2. And there's still the redhat/fedora-type solution to package both with the gtk2 version as compat-wxGTK3-gtk2 or something like that. (In reply to David GEIGER from comment #5) Nah, afaik that won't help - kicad requires wxgtk3.
Well! should be fixed now with kicad-4.0.1-5.mga6 rebuilt against wxgtk compiled with gtk2. please test, thanks in advance!
So closing as Fixed!
Status: NEW => RESOLVEDResolution: (none) => FIXED