Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#2082 - wxgtk 2.4.2 should not be linked against gtk+ 2.x.x

Attached to Project: Arch Linux
Opened by Raven Morris (Samus_Aran) - Thursday, 27 January 2005, 23:32 GMT
Last edited by Dale Blount (dale) - Friday, 28 January 2005, 02:28 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

The wxgtk 2.4.2 library is not meant to be linked against GTK+ 2.x.x. This is listed as "Experimental", and for good reason: it causes random application errors, memory leaking, high CPU usage and other strange side-effects on a consistant and regular basis. It is not at all meant for mainstream usage.

As an example, the aMule app which is linked against this wxGTK2 library causes consistantly bad memory leaks so that the app needs to be shut down every couple days (or a week if you have 1GB+ RAM) to avoid system slow-downs/out-of-memory errors.
(application/octet-stream)    PKGBUILD (2.3 KiB)
   cleanup.patch (17.7 KiB)
   gtk2.patch (1.8 KiB)
(application/octet-stream)    wx-config (0.2 KiB)
(application/octet-stream)    PKGBUILD (2.3 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 25 April 2005, 09:12 GMT
Reason for closing:  Fixed
Additional comments about closing:  wxgtk 2.6.0 in testing contains 3 versions, as suggested by Shastry.
Comment by celeron (celeron) - Thursday, 27 January 2005, 23:45 GMT
exactly, plz compile wxgtk against gtk+
Comment by celeron (celeron) - Monday, 31 January 2005, 22:37 GMT
or, use the wxgtk 2.5x, than other distros for example debian sid :P
Comment by Tobias Kieslich (tobias) - Monday, 31 January 2005, 23:26 GMT
ahem, nope, many current apps doesn't build against 2.5 series (audacity, eg). So we would have to patche these apps then, and againthis might raise issues. Out of the frying pan into the fire is not an option :)
Comment by Raven Morris (Samus_Aran) - Tuesday, 01 February 2005, 07:42 GMT
Just use GTK+ 1.2.x, it doesn't look as pretty, but for this it is stable.
Comment by Vinay S Shastry (shastry) - Sunday, 13 February 2005, 04:05 GMT
how abt having both ? gentoo solves the trick that way - it compiles against both gtk and gtk2 and have wx-config link to whatever we want.
Comment by Tobias Kieslich (tobias) - Sunday, 13 February 2005, 11:45 GMT
hm but since gentoo is source based the user can choose what toolkit wxgtk should link against. Actually I have the following plan:
wxgtk will be rolled back to gtk1, sorry guys, security comes first. In a second step, and that will go in a slow pace, I will try to roll stuff toward the wx devel releases, but only when ALL our apps build against wxgtk painlessly. If excessive patching is required to move stuff to wxgtk-devel I won't move apps this way since this like jumpung out of the frying pan into the fire. Any help on moving to wxgtk-devel is higly appreciated. Since this is a longer process I guess, prolly I will move things to unstable first and not to testing.
Comment by Vinay S Shastry (shastry) - Wednesday, 23 February 2005, 12:37 GMT
tobias i mean, we compile both, and make a script for wx-config - with a variable like WANT_WXGTK=foo, which intern calls , say wxgtk2-config or wxgtk1-config, and we use this feature in the PKGBUILDs. thus, we can have audacity link to gtk1 version and other stuff (xchm, and others) to gtk2 version.
(i'll look into the gentoo ebuilds for more info)
Comment by Vinay S Shastry (shastry) - Wednesday, 23 February 2005, 16:06 GMT
Attached initial release of multiple stuff - please check it out (i havent tested it properly, so there might be bugs- better try compling before updating)
now, all pkgs which use wxgtk need to set WANG_WXGTK to gtk for gtk1, gtk2 for gtk2 without unicode, and nothing for gtk2+unicode (gtk2+unicode is default)
Comment by Vinay S Shastry (shastry) - Wednesday, 23 February 2005, 16:07 GMT
err - its WANT_WXGTK , sorry for the typo
Comment by Vinay S Shastry (shastry) - Wednesday, 23 February 2005, 16:57 GMT
minor screwup with pkgbuild - fixed verion uploaded
Comment by Tobias Kieslich (tobias) - Monday, 18 April 2005, 15:52 GMT
Ok, finally I have made up my mind, sorry shastry, but this is how it works out:
wxgtk development is somehow stagnating and the gtk2 version of 2.4.2 is really buggy :/ For the better "optic" it might make sense to keep it, but it's a mess alltogether. So I will roll back to gtk1 and recompile the apps from the repos against it. So we have a secure, working and stable software in the repos. Sadly, it's not pretty.
I strongly encourage people to use the TUR to create a 2.5.x version of wx packages, which will make it possible to slowly migrate to a stable and "round" gtk2 based version of wxgtk applications.

For now wxgtk on gtk1 again will go to testing, until other apps have been recompiled against it.

Loading...