(old)Puppy Linux Discussion Forum

Posted: **Sun 26 Apr 2015, 03:36**

I've tried --

chromium_37.0.2062.120+pepper_15.0.0.152_lx.sfs
chromium_40.0.2214.111+pepper_16.0.0.305_lx.sfs

...and the most recent Chromium 42 .sfs from PeeBee's thread. All give the same results

Posted: **Sun 26 Apr 2015, 03:49**

@starhawk,

chromium-40.0.2214.91.sfs doesn't seem to be available, the original download link is dead, I could upload it if you want to try that.

Posted: **Sun 26 Apr 2015, 03:54**

That's alright.

I'm starting to think that something changed in glibc2.20 that's causing this.

X-Slacko -- glibc2.15 -- works, albeit only without sandboxing which requires a newer kernel.

TahrPup 6.0.2 -- glibc2.19 -- works flawlessly.

Caro Vanguard -- glibc2.20 -- kaboom

not so much.

I'm currently trying to find another glibc2.20 Pup I can try it on, to see if that's what it is. Would make sense -- the fundamental error is a failed malloc() call (or something like that) and, near as I can tell from Google (I am not a programmer!), malloc() is a glibc thing.

Posted: **Sun 26 Apr 2015, 04:14**

starhawk wrote:I'm currently trying to find another glibc2.20 Pup I can try it on, to see if that's what it is.

No luck

LxPupTahr, X-Precise, etc. All too early.

Uhm, if I wanted to take Caro Vanguard and stick in eg TahrPup's glibc2.19, would that likely break everything? Do you know?

EDIT: It does

kind of predictable tho. Hm. How else could I go about pulling this off? Kernel swap? Dunno.

Posted: **Sun 26 Apr 2015, 14:03**

Geoffrey wrote:@starhawk,

chromium-40.0.2214.91.sfs doesn't seem to be available, the original download link is dead, I could upload it if you want to try that.

There is your out starhawk. Or are you just being stubborn?

Posted: **Sun 26 Apr 2015, 16:42**

A later version works fine on the desktop. The mystery is, why doesn't it work with the exact same setup anywhere else?

Posted: **Sun 26 Apr 2015, 22:36**

Another clue. Maybe.

I keep seeing this whenever I drop into text mode and go back to GUI --

Code: Select all

10130 ?        Ss 0:00 dbus-daemon

It's only up for a split second before XWin kicks in... local guru guy says that it means dbus-daemon is in sleep mode.

Maybe that's the problem? Dunno.

Posted: **Wed 29 Apr 2015, 16:30**

...and, answer. Not what I was imagining, to say the least.

Both the netbook and the Dell laptop are Intel based. My desktop is AMD based. On a lark (and a suggestion from my local guru friend), I tried running Caro Vanguard and Chromium on my mother's desktop as well -- it's an AMD Compaq -- and it worked.

So it's an AMD vs Intel thing. AMD works, Intel does not.

Very interesting.

Posted: **Fri 01 May 2015, 00:01**

Hey battleshooter, when you get a minute --

Can you tell me if your computer that you compiled the glibc and kernel updates on, for Vanguard, is AMD or Intel based...? (what CPU manufacturer)

That might help with this.

Posted: **Sat 02 May 2015, 01:33**

Final note on this for a while, unless someone actually bothers to respond -- which, at this point I'm really not expecting...

Downloaded the Google Chrome to dotPET script (aka Chrome2Pet, too lazy to link right now, sorry) and while it didn't run properly on Caro Vanguard, I got it to work in another Pup and copied the resulting Chrome dotPET over.

I'm typing from it now. I had to disable sandboxing (which ticks it off enough to complain at me) to get past a problem with the Native Client -- but it DOES work.

Seems to me then that it's the packages. It's not Vanguard, it's not Puppy, it's the source of the packages. That would be a guy named alienbob -- who packages Chromium for Slackware. peebee tells me that he repackages alienbob's TXZs. (For the record, I emailed alienbob about this, and he was actually rather nasty to me. I'm glad I don't run Slackware, since I'd have to deal with him far more often if I did.)

I think it's about time someone started doing proper compiling of Chromium specifically for Puppy... to be entirely honest, if I were able to do it myself I'd already be doing it. I can't

Posted: **Tue 05 May 2015, 20:15**

hi

Wine says these are missing:

liblcms2.so.2
libmpg123.so.0
libldap_r-2.4.so.2 liblber-2.4.so.2
libgettextpo.so.0
libgettextpo.so.0

they are not available in the lina ppm.

should i get these from ubuntu, slackware, arch, or.... ?

wine-1.6.2-i486_v1.1.pet installed from green dome's repo
http://version2013.yolasite.com/page1.php#wine-1.6.2

on vlina-r2, of course.

thx!

also asked here:
http://murga-linux.com/puppy/viewtopic. ... 830#843830

Posted: **Tue 05 May 2015, 21:35**

johnywhy wrote:hi

Wine says these are missing:

liblcms2.so.2
libmpg123.so.0
libldap_r-2.4.so.2 liblber-2.4.so.2
libgettextpo.so.0
libgettextpo.so.0

they are not available in the lina ppm.

They are in the ppm

search for:

lcms2
mpg123
openldap
gettext-tools

Posted: **Tue 05 May 2015, 22:09**

Geoffrey wrote:They are in the ppm
search for:
lcms2
mpg123
openldap
gettext-tools

thx, G!

Posted: **Wed 06 May 2015, 15:45**

soon!

---------------

zagreb3.iso

xfce 4.10-4.12

thunar 1.6

puppyzagreb

kernel latest 4.0

based on vlina

!!!!!!!!!!three times fastest than vlina!!!!!!!!!!!

regards.[img]

soon!

---------------

zagreb3.iso

xfce 4.10-4.12

thunar 1.6

puppyzagreb

kernel latest 4.0

based on vlina

!!!!!!!!!!three times fastest than vlina!!!!!!!!!!!

regards.

[/img]

Posted: **Wed 06 May 2015, 15:54**

zagreb, please stop posting in this thread about versions of Puppy other than Carolina Vanguard.

I will be glad to PM Flash if you need assistance with this.

Posted: **Wed 06 May 2015, 18:05**

IT IS VANGUARD CAROLINA!
REGARDS.

Posted: **Wed 06 May 2015, 18:10**

It is not. It has a different name and set of features. It's your own remix.

If I see another ad from you in here, I *will* report it.

Also, typing in all caps is the Internet way of shouting. Indoor voices, please!

Posted: **Thu 07 May 2015, 19:23**

zagreb999 wrote:IT IS VANGUARD CAROLINA!.

ETP wrote:It is based on Slacko 5.9.3 and uses Stemsee’s 3.19.2-EmSee-32-pae (i686) kernel.
http://www.murga-linux.com/puppy/viewto ... 007#842007

that does not sound like it has any connection to Vlina.

Posted: **Sun 10 May 2015, 00:15**

Hi.

I'm currently doing some work using Carolina Vanguard.

Had to fix the settings of Geany to be able to execute scripts from within geany.

Now it works, the scripts are executed as usual, but all the scripts do give terminal message below:

Code: Select all

Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 84: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 84: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 93: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 93: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 102: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 102: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 60: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 69: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 69: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 80: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 80: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 80: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 89: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 75: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 75: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 10: Having multiple values in <test> isn't supported and may not work as expected

How to get rid of this / fix this?

Thanks

Posted: **Sun 10 May 2015, 01:55**

@LazY Puppy
I compiled fontconfig-2.11.1 and freetype-2.5.5, see if that fixes it for you.

fontconfig-2.11.1-i486.pet

fontconfig_DEV-2.11.1-i486.pet

fontconfig_DOC-2.11.1-i486.pet

freetype-2.5.5-i486.pet

freetype_DEV-2.5.5-i486.pet

freetype_DOC-2.5.5-i486.pet

As usual, use at your own peril

no need to install the DEV and DOC pet's
Everything appears to be working fine for me.

(old)Puppy Linux Discussion Forum

Carolina: Vanguard Edition Release 2 December 2014

zagreb3.iso

vanguard carolina

Re: vanguard carolina