Page 8 of 11

Posted: Sat 09 Mar 2013, 22:14
by Makoto
If it was my only system and I was using Firefox on the Puppy system more than SM, maybe. :) I'm not at my Puppy system right now, so maybe I'll try some of the checks later, when I can. :oops:

I've heard the update checkers in Firefox/Thunderbird also do some additional checks to see whether or not you can run a certain update for other reasons (hardware/software, such as stopping Win9X/ME users from updating FF past a certain point). Maybe there's another reason other than some sort of block at the update servers for my FF not 'seeing' the newer versions. v17-19 do act very strange on my Puppy setup, after all, though it's surprising it never throws any sort of error message.

I'd think if it was a matter of being unable to access the update server, Firefox would at least display a simple error message, in that regard. (Also, wasn't there an extension to change the update server, or was that just to switch update channels?)

Edit: Okay, semi-long day. :roll:

Here's the app.update.url value:

Code: Select all

https://aus3.mozilla.org/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
And the result of netstat -tn:

Code: Select all

# netstat -tn
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 172.16.1.38:34835       205.188.13.78:443       ESTABLISHED 
tcp        0      0 172.16.1.38:35882       72.21.91.19:80          TIME_WAIT   
tcp        0      0 172.16.1.38:39596       173.194.79.125:5222     ESTABLISHED 
tcp        0      0 172.16.1.38:56601       205.188.4.127:443       ESTABLISHED 
tcp        0      0 172.16.1.38:42020       64.12.104.224:443       ESTABLISHED 
tcp        0      0 172.16.1.38:47092       66.196.121.24:5050      ESTABLISHED 
tcp        0      0 172.16.1.38:54133       65.55.71.43:1863        ESTABLISHED

Posted: Sun 10 Mar 2013, 11:17
by Semme
63.245.217.44 should've been among those results.

Did you add that bit to your hosts file?

Where does https://aus3.mozilla.org/ take you, FF?

Redirect to http://www.mozilla.org/*

With extensions disabled: firefox -safe-mode

Posted: Sun 10 Mar 2013, 18:39
by Makoto
Yes, I added "127.0.0.1 aus3.mozilla.org" to hosts, like you asked.

Before, https://aus3.mozilla.org/ would load, then redirect to www.mozilla.org. With the hosts entry in place, it just throws the Unable to Connect error, now.

As for Safe Mode, you can also use Help > Restart with Add-ons Disabled..., right? :) But, no, it won't connect to https://aus3.mozilla.org/ then, either (and the update check still thinks 16.0.2 is up-to-date).

Posted: Sun 10 Mar 2013, 20:28
by Semme
Say Makoto- are you using your old *.default profile when you fresh install? Have you tried with a clean one?

Posted: Sun 10 Mar 2013, 20:35
by Makoto
Yeah, I've tried it with both a default/blank profile and my regular profile, when I was trying to get v18 to work. No change.

Posted: Mon 11 Mar 2013, 14:31
by Semme
Makoto- you use private browsing mode or keep a cache and hang onto cookies?

Posted: Tue 12 Mar 2013, 02:27
by Makoto
The latter. Never really tried private-browsing mode.

Posted: Tue 12 Mar 2013, 04:15
by Semme
Ha! Stale cookies.. Remove all aus2.mozilla.org and aus3.mozilla.org entries and I'll bet update loads..

Posted: Tue 12 Mar 2013, 04:22
by Makoto
No. I said above that I tried it with a completely new/blank default profile (and nothing else in the .mozilla directory except my Seamonkey profile data; recreated my FF profile afterward), and it didn't work, remember?

Posted: Tue 12 Mar 2013, 04:32
by Semme
Sure do.. Had to be sure. I can only think of your save file at this point..

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.