Re: Porteus-v1_beta-i486 ready for testing
Posted: 04 May 2011, 03:03
@brokenman,
@fanthom,
@Hamza,
I am trying to build a module for Google Earth for Porteus V 1.0 -32 bits. The first approach was to translate the google-earth-4.3.lzm from Slax-6.1.2 to Porteus. It runs, but I get empty boxes instead of fonts; the font control has only "Fixed" font size 10 type latin. In Slax 6.1.2 it hat a variety of fonts, sizes and types.
In Slax-Remix and in Porteus 0.9 there is only one fixed font, too.
Then I have built a module for google-earth-5.1.xzm and get also empty boxes where bigger fonts should come; to make it an exercise, I built the google-earth-6.0.1.xzm with the same results.
Running them with lxde did not help at all, same empty boxes. This last version is a pretty thing, for you can fly over the moon and over mars! I got it from slackyd as txz module for Slackware current, so it should run in Porteus, I thought....
http://www.mediafire.com/?zyu3mji9y0iv88g
All tested in 2 machines; external I have qt-4.6.2 installed; I tried with qt-4.7. without luck. Dependencies (ldd googleearth-bin) are all connected. What else could it be?
Good night!
____________________________________________________________________________________________________
The Porteus community never sleeps!
Posted after 23 hours 49 minutes 26 seconds:
Bad news guys!
I packaged the google-earth-6.0.1 directory to a sq3.lzm module for slax 6.1.2 and you can't believe it, the fonts appear ok.
http://www.mediafire.com/?rc6ycqj0b216lqa
You can test it by yourselves.
Checking the chain links we have kernel>core>xorg>kde or lxde>google-earth.
Porteus has a new kernel, a new kde, but not a new lxde, and I don't know if core and xorg are also new; so the bug is in the kernel or in xorg-if it is new-.
Apparently the fonts that fail are streamed by the google server; when you are not conected, the font control can not open the switch, it is grayed. When connected, the fonts can get through.
Our Porteus is sendig those fonts to /dev/null somehow.
Now I will subscribe myself to the XZM-TEAM! 8)
Cheers!
___________________________________________________________________________________________________
The porteus community never sleeps!
@fanthom,
@Hamza,
I am trying to build a module for Google Earth for Porteus V 1.0 -32 bits. The first approach was to translate the google-earth-4.3.lzm from Slax-6.1.2 to Porteus. It runs, but I get empty boxes instead of fonts; the font control has only "Fixed" font size 10 type latin. In Slax 6.1.2 it hat a variety of fonts, sizes and types.
In Slax-Remix and in Porteus 0.9 there is only one fixed font, too.
Then I have built a module for google-earth-5.1.xzm and get also empty boxes where bigger fonts should come; to make it an exercise, I built the google-earth-6.0.1.xzm with the same results.
Running them with lxde did not help at all, same empty boxes. This last version is a pretty thing, for you can fly over the moon and over mars! I got it from slackyd as txz module for Slackware current, so it should run in Porteus, I thought....
http://www.mediafire.com/?zyu3mji9y0iv88g
All tested in 2 machines; external I have qt-4.6.2 installed; I tried with qt-4.7. without luck. Dependencies (ldd googleearth-bin) are all connected. What else could it be?
Good night!
____________________________________________________________________________________________________
The Porteus community never sleeps!
Posted after 23 hours 49 minutes 26 seconds:
Bad news guys!
I packaged the google-earth-6.0.1 directory to a sq3.lzm module for slax 6.1.2 and you can't believe it, the fonts appear ok.
http://www.mediafire.com/?rc6ycqj0b216lqa
You can test it by yourselves.
Checking the chain links we have kernel>core>xorg>kde or lxde>google-earth.
Porteus has a new kernel, a new kde, but not a new lxde, and I don't know if core and xorg are also new; so the bug is in the kernel or in xorg-if it is new-.
Apparently the fonts that fail are streamed by the google server; when you are not conected, the font control can not open the switch, it is grayed. When connected, the fonts can get through.
Our Porteus is sendig those fonts to /dev/null somehow.
Now I will subscribe myself to the XZM-TEAM! 8)
Cheers!
___________________________________________________________________________________________________
The porteus community never sleeps!