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!
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!
FS#30938 - [wxgtk] problem with wxWidgets after last updates (probably not just wxWidgets)
Attached to Project:
Arch Linux
Opened by Jacek Poplawski (Jacek Poplawski) - Tuesday, 31 July 2012, 12:33 GMT
Last edited by Eric Belanger (Snowman) - Saturday, 06 October 2012, 01:11 GMT
Opened by Jacek Poplawski (Jacek Poplawski) - Tuesday, 31 July 2012, 12:33 GMT
Last edited by Eric Belanger (Snowman) - Saturday, 06 October 2012, 01:11 GMT
|
DetailsDescription:
This problem appears on wxWidgets, but I am not sure is it just wxWidgets or we have some mess in binaries after last update of libraries and maybe /usr/lib /lib conversion. https://bbs.archlinux.org/viewtopic.php?pid=1139425#p1139425 in short: wxWidgets stopped working correctly, the package was not updated for a long time, applications using wxWidgets work, but there is one case when output is broken, I found it in my application but I linked demo site with short test to perform tested on both wxWidgets 2.8 and wxWidgets 2.9 from Arch repo, I suspect it's not wxWidgets fault but some other libraries like gtk+ or X, I don't know how to revert whole system to older state of libraries to test when it stopped working Steps to reproduce: 1. download demo described on forum thread 2. compile it (remove xpm icon lines) 3. run it and observe result |
This task depends upon
Closed by Eric Belanger (Snowman)
Saturday, 06 October 2012, 01:11 GMT
Reason for closing: No response
Additional comments about closing: no response/upstream
Saturday, 06 October 2012, 01:11 GMT
Reason for closing: No response
Additional comments about closing: no response/upstream
Comment by Eric Belanger (Snowman) -
Tuesday, 31 July 2012, 20:11 GMT
From a quick glance (I haven't tried the test yet), it looks like an upstream issue. Did you tried rebuilding wxgtk to see if that fix it?