Hi Don, on which distributions and versions of those distributions were
you
deploying your apps on? We’ve found this bug is triggered by the version
of
pixman that the distribution is using.
I found a discussion that I think is the same issue here, I’ll add it to
the
bug:
No worries, thanks heaps for your input Don. No rush either, this is a
pretty longstanding bug by now.
Ubuntu 10.04, with ruby 1.8.7p330, IIRC. All updated to -stableAny more
details will have to wait until. I get back to Arizona next week. I can
check the pixman tarball, though I know I never deliberately messed with
it
on either 32 or 64,
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 09.05.2011 22:01, schrieb Alex F.:
the issues on the Ubuntu bugtracker. I was half-thinking of switching to
Fedora anyway before the next Ubuntu came out - maybe this will tip me
over.
I think I already mentioned it, but it was exaktly wxRuby that was the
final reason for me to switch from Ubuntu to Arch Linux. I really enjoy
the rolling release model now–no way back. 
However, Ubuntu is the most-widespread Linux distribution out there.
It’s not wise to drop support for it I think, because it would
significantly state a contrast to the platform-indepentness wxRuby aims
to provide.
Martin, I have been quite successful at deploying both 32 bit and
64-bit
10.04 installations of wxRuby. I had to go back to the 2.0.0 gem for
64, but
it seems to work quite fine with our rather elaborate application.
Ubuntu Lucid 64bit worked without a problem for me, even though I had to
compile wxRuby 2.0.1 myself. It’s just that wxRuby doesn’t work on each
and every Ubuntu after Lucid.
And btw. my name is Marvin, note the v.
Hi Don, on which distributions and versions of those distributions
were you
deploying your apps on?
I can confirm wxRuby not working for Ubuntu Maverick 64bit, Ubuntu
Maverick 32bit, Ubuntu Natty 32bit (the last to being virtual machines)
and Arch Linux 64bit (completely updated last Friday)*. But I suppose it
doesn’t work for different reasons on each machine… 
Here’s the bug that discussion references, in Debian:
Thanks! It really looks like a bug in pixman then.
###########################
So, what can we do now? wxRuby’s obviously not at fault, it’s
a) pixman that is broken and
b) Debian/Ubuntu that ships broken wxWidgets packages
b) is marked as fixed for Oneiric, but I doubt wheather wxRuby will run
then, because of a) and a symbol lookup error I already described on
Launchpad (this would be c) then I think).
The pixman bug breaks wxRuby on nearly every recent Linux distribution,
and Debian/Ubuntu breaks it a second time due to their package
management, which is especially problementic because of their
popularity.
To conclude: I’m worried about wxRuby’s future, although it seems that
wxRuby can’t do much about the mentioned problems.
best
alex
Valete,
Marvin
iQEcBAEBAgAGBQJNyXOBAAoJELh1XLHFkqhajpYIAK0/ZBrho5fd9fGaEkGGQbal
+uwRxdavIldM38I8wolfIomPEZxTzupim+NPLigB1NHToUrSjhhCGkg482YuJR9u
HMncfRInw5eK/rXo1xHwF213sY3bZtxy9EOG+lJ/qLCm6qrke5tAGBKLzsY62QtG
v4KOXGNOyC+NEtdHFyPhancvwqrjfnyL/OjgUMku03saLq58vDZMiv1rAz++m69c
RO5h6sIZ+ZHp4tVIKSMKjLYoyQrVfuNK/A0RJMdpnLlsz+oAiP36sS65wKEL1wB4
+F62p7Ow/yjgItqAeG2HgKRcJyKwRT9tXSK8M83dsxWk9hyJVubILa2dWpvsD70=
=12Su
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 05.10.2011 03:28, schrieb David B.:
- Previously, running any wxruby app would cause a crash in
pixman. This has possibly been narrowed down to a problem with
mesa or opengl drivers and it affects many projects that link
dynamically to wxwidgets as well as other gui toolkits. Excluding
opengl support seems to fix this for wxruby. See
Bug #756237 “wxRuby crashes with segmentation fault in pixman_im...” : Bugs : pixman package : Ubuntu
Maybe I’m a bit too optimistic, but wxRuby works again with pixman
version 0.22.2, at least on my system (Arch Linux). It seems the bug
has been fixed. Hopefully it stays like this…
Valete,
Marvin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOjFmvAAoJELh1XLHFkqhaLWUH/2v6HwKgghqsOEA7j8hbyagP
5cwZrd+5xl8io4dHG7w454gpQsuP4tohQjs29+RPg9doUy7Y0OseXuv3A4+28jfX
YkreGzLG4RxyagFIdGJM/kQDIjo/GclIiAp72fmtx6hXFJOjox5nDPZMY+erKlh/
XP1AhktqX+Ia8WqF31C6vDHoOgjRBDJimL6wY+RQnhVbtpLfIgPxxmqyXMDKfVGl
ce5PL14zNSqCx/S9XbbRz1Bgxp+Ko0B+w3/2Mx1YxfmxZGgoF8M6aSWO8ofTQ+Fs
FQni3ItsaKHaqIIfoK0nZOYutLatNFeOaVysO6lw6gl0z7ldPefVkIGRacwi3zM=
=I8GM
-----END PGP SIGNATURE-----
hello all - have now committed this patch - looks excellent and works
fine on my main Ubuntu box (11.10). Thanks again and sorry to be slow -
have just started a new job and moved hosts.
We should look to release a bug-fix 2.0.2 soon - I have a little bit of
time this weekend. There are some uncommitted patches I’d like to review
at http://rubyforge.org/tracker/?atid=220&group_id=35&func=browse
We had thought that we wouldn’t add features to 2.0.x line, but I’d
favour merging these given our slow (!) release schedule. Discussion
welcome (preferably on wxruby-dev).
best
alex
Hi everyone, an update on this problem and wxruby’s gem and build
troubles.
I was just able to build wxruby and run bigdemo with the help of a
proposed
natty (11.04) fix for Ubuntu’s apt wxwidgets package. This is great
progress! As soon as the natty fix is released, binary gems might be
ready
to go again.
To summarise the problems and their fixes so far:
Previously, running any wxruby app would cause a crash in pixman.
This
has possibly been narrowed down to a problem with mesa or opengl drivers
and
it affects many projects that link dynamically to wxwidgets as well as
other
gui toolkits. Excluding opengl support seems to fix this for wxruby. See
Bug #756237 “wxRuby crashes with segmentation fault in pixman_im...” : Bugs : pixman package : Ubuntu
An additional problem cropped up in Natty, and maybe other versions.
The
Xinerama library is in an unusual place in Ubuntu 64-bit. wxwidget’s
configure script can’t find it and so it disables support for the
wxDisplay
class (as if --disable-display was given,) and this causes rake compile
to
fail because there’s no definition of wxDisplay::ResetMode. There is an
official proposed fix for this now, see
Bug #828999 “wxDisplay unexpectedly disabled” : Bugs : wxwidgets2.8 package : Ubuntu, and
follow the directions to get the fixed package. Please take a moment to
verify the fix on the bug page, if you try it.
Just today, I discovered a problem with the wxruby rake files. The
rake
files exclude various classes from the build on linux, but the logic
fails
because code reads the array $excluded_classes in rakeunixish.rb before
the
array is actually set up at the bottom of rakeconfigure.rb. This causes
link
to fail because libgtk-media isn’t present, and MediaCtrl should be
excluded
from the build. I added a class to wrap the functionality of extracting
and
testing for wx features, and it’s implemented such that querying wx
features
should be insensitive to the order of different bits of code. Please
apply
the attached patch to fix this, let me know if you have problems with
it.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs