Browser update

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
User avatar
Ed_P
Contributor
Contributor
Posts: 6108
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

Browser update

Post#1 by Ed_P » 12 Mar 2021, 20:43

Cinnamon 4.0 64-bit Firefox 78.6.1esr upgrading to 86.0.1

Code: Select all

firefox/plugin-container.sig
firefox/firefox.sig
firefox/libxul.so.sig
 Linking firefox binary ... 
/tmp/portff
 Copying firefox files ... 
 Creating default settings ... 
 Copying config files ... 
cp: cannot stat '/home/guest/files/*': No such file or directory
chown: cannot access '/tmp/portff/ff.3901/home/guest': No such file or directory
Adding home page ...
Creating module ...
Problem?? :%)
Ed

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 2962
Joined: 20 Mar 2012, 03:42
Distribution: 5.0rc1-64bit all-DE+more
Location: australia
Contact:

Browser update

Post#2 by ncmprhnsbl » 13 Mar 2021, 02:06

Ed_P wrote:
12 Mar 2021, 20:43
Problem??
you mean this bit? :

Code: Select all

Copying config files ... 
cp: cannot stat '/home/guest/files/*': No such file or directory
chown: cannot access '/tmp/portff/ff.3901/home/guest': No such file or directory
just some redundant lines in the script.. you get a new firefox module in /tmp, right? (i do)
have commented those lines now in the script on the server..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Ed_P
Contributor
Contributor
Posts: 6108
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

Browser update

Post#3 by Ed_P » 13 Mar 2021, 05:25

Yes, I got a new firefox module in /tmp and am using it as I write this.

A strange thing is a desktop file opening a webpage in firefox now doesn't open the url, it just brings up a firefox window with no open tabs. I don't know if it's a firefox 86.0.1 problem or a nucleus 5.11.6 problem since both are new at this point. :%)

Added in 11 minutes :
I don't have the problem with the desktop file using firefox 86.0.1 in Porteus 4.0. :o

Added in 1 day 10 hours 31 minutes 20 seconds:
Ed_P wrote:
13 Mar 2021, 05:36
A strange thing is a desktop file opening a webpage in firefox now doesn't open the url, it just brings up a firefox window with no open tabs. I don't know if it's a firefox 86.0.1 problem or a nucleus 5.11.6 problem since both are new at this point.
And today it works. :%) :unknown:
Ed

User avatar
Rava
Contributor
Contributor
Posts: 2944
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 5.0rc2 + 4.0 i586 XFCe
Location: Forests of Germany

Browser update

Post#4 by Rava » 02 Jun 2021, 17:46

I just ran update-browser -d -p with a manually downloaded palemoon-29.2.0.linux-x86_64-gtk3.tar.xz and got these errors:

Code: Select all

xargs: warning: options --max-args and --replace/-I/-i are mutually exclusive, ignoring previous --max-args value
xargs: warning: options --max-args and --replace/-I/-i are mutually exclusive, ignoring previous --max-args value
They come here:

Code: Select all

[…]
'palemoon/defaults/pref' -> '/Porteus_modules/5.0/palemoon/.pale.21574/package-palemoon/opt/palemoon/defaults/pref'
'palemoon/defaults/pref/channel-prefs.js' -> '/Porteus_modules/5.0/palemoon/.pale.21574/package-palemoon/opt/palemoon/defaults/pref/channel-prefs.js'
Setting Porteus Forum to Homepage
Adding home page ...
Fixing permissions ...
xargs: warning: options --max-args and --replace/-I/-i are mutually exclusive, ignoring previous --max-args value
xargs: warning: options --max-args and --replace/-I/-i are mutually exclusive, ignoring previous --max-args value
Setting libmozavutil.so as executable ...
Setting libnspr4.so as executable ...
Setting run-mozilla.sh as executable ...
Setting libxul.so as executable ...
Setting libsoftokn3.so as executable ...
[…]
Is that an issue?
Cheers!
Yours Rava

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 2962
Joined: 20 Mar 2012, 03:42
Distribution: 5.0rc1-64bit all-DE+more
Location: australia
Contact:

Browser update

Post#5 by ncmprhnsbl » 02 Jun 2021, 22:46

Rava wrote:
02 Jun 2021, 17:46
Is that an issue?
not really, because "ignoring previous --max-args value" does no harm.. have seen this in a lot of scripts recently, i guess that with some recent xargs update 'the rules' have been tightened around this...
and technically, a warning is not an error :)
i will get around to cleaning this up, though .. thanks
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Rava
Contributor
Contributor
Posts: 2944
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 5.0rc2 + 4.0 i586 XFCe
Location: Forests of Germany

Browser update

Post#6 by Rava » 02 Jun 2021, 23:42

ncmprhnsbl wrote:
02 Jun 2021, 22:46
have seen this in a lot of scripts recently, i guess that with some recent xargs update 'the rules' have been tightened around this...
and technically, a warning is not an error :)
i will get around to cleaning this up, though .. thanks
Makes sense that they changed the code when the warnings are all over the place.
ncmprhnsbl wrote:
02 Jun 2021, 22:46
because "ignoring previous --max-args value" does no harm..
When your code explicitly relies on the old behaviour, it can be the start of a bug.

Anyhow, I have a script question: Since it is off topic, I PM you, hopefully you have a tip for me. :)
Cheers!
Yours Rava

Post Reply