Page 9 of 11

Posted: Tue 12 Mar 2013, 05:01
by Makoto
Nah. It's just that for some reason, Firefox thinks my setup isn't worthy of the more recent versions. :mrgreen:

Everything else works fine (including Firefox, in general), and it's not really a big issue, so... :oops: (Although technically, I should be running Puppy 5 on this hardware, over Puppy 4.3.1. Someday, maybe. Probably five months after Puppy 6 is released. :P)

Posted: Tue 12 Mar 2013, 07:55
by nooby
The surprising thing is that it do say that my FF17 is the latest.

I tried to make a screeny of it but that failed.
But reading it and manually retelling it says.

"17.0 Firefox is up to date.
You are currently on the default update channel."

and I delete all cookies each time I shut it down
so ???

What could mess it up would be that I have the .mozilla
manually moved to /mnt/home/.mozilla and that way
maybe it look in wrong place? But it has worked before
on other puppy. Lupu updated from 12 to 16 to 17 and
I had that one on the mnt home too.

How bad is it to drive with 17 instead of 19?

Posted: Tue 12 Mar 2013, 10:58
by Semme
Is moved to /mnt/home/.mozilla via symlink? And no, 17's not a biggie so long as.... :lol:

Posted: Tue 12 Mar 2013, 11:14
by nooby
I tried to do as kickstart recommended in his thread here
http://www.murga-linux.com/puppy/viewtopic.php?t=84780
Running Firefox from outside Save file [solved]


And it worked well. FF19 even updated to a recent FF19

then I realized that my save file will grow so I moved the .mozilla file
to /mnt/home/ and then made a symlink back to root directory.

Lo and behold now Firefox says it is FF17 again.

so it somehow pick that up from my older install
despite me renaming those to dozilla and nozilla that did not help.

So not sure what to do now. Took me hours to restore all addons
and bookmarks and passwords and now I am back on Square One
or Get Go and nothing changed I only lost the cute Bookmark tool bars I had. all else is the same

So I need some other solution for to get FF19 going.

Maybe that Slacko update to a version with FF19 in it.

Posted: Tue 12 Mar 2013, 11:52
by Semme
Having mimicked your setup- update loads. Did you ice these cookies?

Where's the bulk of your FF install reside?

Posted: Tue 12 Mar 2013, 15:25
by nooby
Double post I explain in this post and ask you to ignore the next :)

Finally I get what is going on at my place.

It really works with FF19 and many time but when one shut it down
for to use geany or to listen to music or to look at saved pictures
of cool Bikes whatever and then restart it

then it check if the extensions are compatible with FF19
and them realize they are not updated to be able to be used
on FF19 so it instantly goes back to a FF17 backup somewhere
it was done within a second so it must have prepared for it.

So now we know how it works at my install but who knows
maybe Makoto or others have other factors that set in.

So there is nothing to do about it just wait for that they update
ASAP

Posted: Tue 12 Mar 2013, 18:29
by nooby
look at text above that one explain what goes on.

Posted: Tue 12 Mar 2013, 19:15
by Semme
Image too big? Upload, then link your shot from here.

And I'd agree- Makotos`cause is different I'm sure..

Posted: Wed 13 Mar 2013, 01:27
by Makoto
In my case, it's probably something about Puppy 4.3.1 or some of my installed libs it doesn't like (though you'd think that with the latter, it would throw error messages).

For all I know, it looks at my kernel version and politely declines any more updates, because it thinks the system can't properly run it. The same behavior happens if you try to update past FF2 on a Win9X/ME system, IIRC. (It doesn't see the updates, and doesn't really tell you why.)

Posted: Wed 13 Mar 2013, 02:46
by James C
Makoto wrote:In my case, it's probably something about Puppy 4.3.1 or some of my installed libs it doesn't like (though you'd think that with the latter, it would throw error messages).

For all I know, it looks at my kernel version and politely declines any more updates, because it thinks the system can't properly run it. The same behavior happens if you try to update past FF2 on a Win9X/ME system, IIRC. (It doesn't see the updates, and doesn't really tell you why.)
You can eliminate the kernel...... I used the kernel from 4.3.1 when I built Lucid Retro and I'm posting from Firefox 19.0.2 right now. Newer Firefox builds are probably requiring some built-in lib that's too old in the 4 series Puppy's.
Pretty sure Firefox quit updating in my install of Ttuuxxx's 4.32, I'll reboot and check.

On Windows 2000 Firefox won't update past 12.0 either.

Posted: Wed 13 Mar 2013, 03:10
by James C
Requirements for Firefox 19.0
Firefox will not run at all without the following libraries or packages:

GTK+ 2.18 or higher
GLib 2.22 or higher
Pango 1.14 or higher
X.Org 1.0 or higher (1.7 or higher is recommended)
libstdc++ 4.3 or higher
http://www.mozilla.org/en-US/firefox/19 ... uirements/

Posted: Wed 13 Mar 2013, 03:15
by James C
I had forgotten but Firefox 19.0.2 also works in 4.3.2. Not sure what Ttuuxxx upgraded from 431 though.

Posted: Wed 13 Mar 2013, 03:36
by Makoto
Hmm... well, I think my Puppy has GTK+ at 2.14.7, and glib at 2.18.3. The odd thing is, though, as I noted above - if I try running the v18/19 binaries from Mozilla, they'll run, but for some reason, believe they're v12 or earlier. :shock:

Edit: Ran a couple of basic ldd attempts against 19.0.2:

Code: Select all

# ldd -v firefox
	linux-gate.so.1 =>  (0xffffe000)
	libpthread.so.0 => /lib/libpthread.so.0 (0xb7fb6000)
	libdl.so.2 => /lib/libdl.so.2 (0xb7fb2000)
	libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7ecb000)
	libm.so.6 => /lib/libm.so.6 (0xb7ea9000)
	libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb7e9e000)
	libc.so.6 => /lib/libc.so.6 (0xb7da2000)
	/lib/ld-linux.so.2 (0xb7fcc000)

	Version information:
	./firefox:
		libgcc_s.so.1 (GLIBC_2.0) => /usr/lib/libgcc_s.so.1
		ld-linux.so.2 (GLIBC_2.3) => /lib/ld-linux.so.2
		libdl.so.2 (GLIBC_2.1) => /lib/libdl.so.2
		libdl.so.2 (GLIBC_2.0) => /lib/libdl.so.2
		libstdc++.so.6 (GLIBCXX_3.4) => /usr/lib/libstdc++.so.6
		libstdc++.so.6 (CXXABI_1.3) => /usr/lib/libstdc++.so.6
		libpthread.so.0 (GLIBC_2.1) => /lib/libpthread.so.0
		libpthread.so.0 (GLIBC_2.0) => /lib/libpthread.so.0
		libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.3) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.3.2) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
	/lib/libpthread.so.0:
		ld-linux.so.2 (GLIBC_2.3) => /lib/ld-linux.so.2
		ld-linux.so.2 (GLIBC_2.1) => /lib/ld-linux.so.2
		ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2
		libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.3.2) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.2) => /lib/libc.so.6
		libc.so.6 (GLIBC_PRIVATE) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
	/lib/libdl.so.2:
		ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2
		libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
		libc.so.6 (GLIBC_PRIVATE) => /lib/libc.so.6
	/usr/lib/libstdc++.so.6:
		ld-linux.so.2 (GLIBC_2.3) => /lib/ld-linux.so.2
		libgcc_s.so.1 (GCC_3.3) => /usr/lib/libgcc_s.so.1
		libgcc_s.so.1 (GCC_3.0) => /usr/lib/libgcc_s.so.1
		libc.so.6 (GLIBC_2.3) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.2) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
	/lib/libm.so.6:
		ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2
		libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
	/usr/lib/libgcc_s.so.1:
		libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.2.4) => /lib/libc.so.6
		libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
	/lib/libc.so.6:
		ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2
		ld-linux.so.2 (GLIBC_2.3) => /lib/ld-linux.so.2
		ld-linux.so.2 (GLIBC_2.1) => /lib/ld-linux.so.2

Posted: Tue 02 Apr 2013, 22:28
by Semme

Posted: Wed 15 May 2013, 10:30
by Semme

Posted: Wed 15 May 2013, 13:59
by nooby
Good that you tell us they have new versions already.

I am too dumb to get this feature.

https://blog.mozilla.org/privacy/2013/01/28/newdntui/

" the Do Not Track feature really has three states: “user says nothing

Posted: Mon 10 Jun 2013, 19:43
by vicmz
Hello everyone

This is Firefox 21 ↓
Find the dependencies for Wary / Racy at /root/Firefox-Dependencies (install and reboot)

Posted: Fri 21 Jun 2013, 03:37
by vicmz
Latest versions of Firefox won't run in Wary:
urxvt terminal emulator wrote:Couldn't load XRE functions.
I tried an older pet (version 16.0.1) and it runs fine. Those who wish to use the latest versions (21 and later) will have to switch to a Puppy that can run them (Precise, Slacko, Dpup, etc.) until a solution for this is found. Tman's got packages for older versions in the link he posted in the first page of this thread.

**EDIT**
According to some Mozilla pages the affected versions are 18 and later.

Posted: Fri 21 Jun 2013, 05:04
by nooby
I use an old Lupu 528-005 and FireFox 21 works with that one
use it daily. But I have not tested what you talk about.

Do you have frugal install on HD or what kind of install do you use?

When does one have to use urxvt terminal emulator wrote:
Couldn't load XRE functions.

Posted: Fri 21 Jun 2013, 18:18
by vicmz
nooby wrote:I use an old Lupu 528-005 and FireFox 21 works with that one
use it daily. But I have not tested what you talk about.

Do you have frugal install on HD or what kind of install do you use?

When does one have to use urxvt terminal emulator wrote:
Couldn't load XRE functions.
Yes, it's a frugal install to HD of Wary 5.5. User VV5 has had the same problem.

I found a Mozilla page (sorry I missed the link) where someone says Firefox 18 and later requires glibc 2.11+, while Wary Puppy has glibc 2.10.

Actually I use Precise the most, but I thought others would want to know.