Page 15 of 15

Porteus v5.0rc1 problems

Posted: 21 Nov 2020, 12:07
by Rava
ncmprhnsbl wrote:
20 Nov 2020, 21:42
thanks for reporting :)
You are very welcome. :beer:


I did not continue the update-browser, but seems the script is too naughty stubborn well coded to be easily stopped:

Code: Select all

Choose a locale from the list.
All other locales will be removed.
1) am	    10) es	19) hr	    28) ml	37) ru	    46) tr
2) ar	    11) es-419	20) hu	    29) mr	38) sk	    47) uk
3) bg	    12) et	21) id	    30) ms	39) sl	    48) vi
4) bn	    13) fi	22) it	    31) nb	40) sr	    49) zh-CN
5) ca	    14) fil	23) ja	    32) nl	41) sv	    50) zh-TW
6) cs	    15) fr	24) kn	    33) pl	42) sw
7) da	    16) gu	25) ko	    34) pt-BR	43) ta
8) el	    17) he	26) lt	    35) pt-PT	44) te
9) en-US    18) hi	27) lv	    36) ro	45) th
#? ^C^C^C^C^C^C^C^C^C^C^C^Z
[1]+  Stopped                 update-browser -d -g
root@porteus:/path# killall update-browser
root@porteus:/path# 
root@porteus:/path# killall update-browser
root@porteus:/path# psg update-browser
 5353 pts/0    T      0:00 /bin/bash /usr/bin/update-browser -d -g
root@porteus:/path# type psg
psg is a function
psg () 
{ 
    /bin/ps ax | /bin/grep "$1" | /bin/grep -v grep
}
root@porteus:/path# 
:ROFL:

But the ultima ratio did it in:

Code: Select all

root@porteus:/path# killall -9 update-browser
[1]+  Killed                  update-browser -d -g
root@porteus:/path# ./update-chrome-live: line 133: read error: 0: Input/output error

Signal caught, cleaning up

root@porteus:/path# psg update-browser
root@porteus:/path# 

Porteus v5.0rc1 problems

Posted: 22 Nov 2020, 06:46
by Rava
In case someone might wonder, /Porteus_modules/5.0/chrome/update is a symlink, the target is ext3 fs folder. (the /Porteus_modules/ part being symlink)

Code: Select all

root@porteus:/Porteus_modules/5.0/chrome/update# update-browser -d -g 
 Starting checks ... 
[OK] User is root.
[OK] Distro is Porteus
Downloading live script ...
Downloading: update-chrome-live  DONE
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing update-chrome-live  100%  
  Please enter the path to the directory you want to use 
  to do the file operations:  
/Porteus_modules/5.0/chrome/update
Work will be done in:  /Porteus_modules/5.0/chrome/update 
google-chrome is not installed

 Checking latest google-chrome version ... 
[PASS] Latest ver: 87.0.4280.66

 Finished checks. 


#############################################
Welcome to the Porteus google-chrome updater.

Installed version:    
Porteus server version:   87.0.4280.66 
Latest version:   87.0.4280.66 

 Would you like to download the porteus server version? [y/n]
 Would you like to create the module with the latest version? [y/n]

 Checking for required libs.. 

[OK] libbfd was found
 Set your home page. 
 Leave blank for: https://forum.porteus.org and press Enter to continue.
> 
[PASS] Homepage is available

Choose a locale from the list.
All other locales will be removed.
1) am	    10) en-GB	19) gu	    28) ko	37) pt-BR   46) ta
2) ar	    11) en-US	20) he	    29) lt	38) pt-PT   47) te
3) bg	    12) es	21) hi	    30) lv	39) ro	    48) th
4) bn	    13) es-419	22) hr	    31) ml	40) ru	    49) tr
5) ca	    14) et	23) hu	    32) mr	41) sk	    50) uk
6) cs	    15) fa	24) id	    33) ms	42) sl	    51) vi
7) da	    16) fi	25) it	    34) nb	43) sr	    52) zh-CN
8) de	    17) fil	26) ja	    35) nl	44) sv	    53) zh-TW
9) el	    18) fr	27) kn	    36) pl	45) sw
#? 10
 en-GB locale chosen 
 Would you like to create a Porteus module? [y/n]
Downloading latest google-chrome ...
Downloading: google-chrome-stable_current_amd64.deb  12%
So far so good. But it did not end well.
Returning to that xterm it gave me only the end tail of what the script was doing - xfce4-terminal's scrollback was set to 1000 lines limit:

Code: Select all

home/guest/.config/google-chrome/Default/Extensions/felcaaldnbdncclmgdcncolpebgiejap/1.1_0/main.html
home/guest/.config/google-chrome/Default/Extensions/
[…]
usr/share/gnome-control-center/default-apps/google-chrome.xml
usr/share/menu/
usr/share/menu/google-chrome.menu
usr/share/pixmaps/
and now the errors begin, I presume at one point the working directory switched from /Porteus_modules/5.0/chrome/update to /tmp.

Code: Select all

WARNING:  zero length file home/guest/.config/google-chrome/First Run
WARNING:  zero length file home/guest/.config/google-chrome/Default/Web Data-journal
WARNING:  zero length file usr/man/man1/google-chrome-stable.1.gz
WARNING:  zero length file usr/share/menu/google-chrome.menu
WARNING:  zero length file usr/share/gnome-control-center/default-apps/google-chrome.xml
WARNING:  zero length file usr/share/doc/google-chrome-stable/changelog.gz
WARNING:  zero length file usr/share/applications/browser.desktop
WARNING:  zero length file usr/share/applications/google-chrome.desktop
WARNING:  zero length file usr/share/appdata/google-chrome.appdata.xml
WARNING:  zero length file opt/google/chrome/xdg-settings
WARNING:  zero length file opt/google/chrome/xdg-mime
WARNING:  zero length file opt/google/chrome/v8_context_snapshot.bin
WARNING:  zero length file opt/google/chrome/swiftshader/libGLESv2.so
WARNING:  zero length file opt/google/chrome/resources.pak
WARNING:  zero length file opt/google/chrome/product_logo_64.png
WARNING:  zero length file opt/google/chrome/product_logo_48.png
WARNING:  zero length file opt/google/chrome/product_logo_32.xpm
WARNING:  zero length file opt/google/chrome/product_logo_32.png
WARNING:  zero length file opt/google/chrome/product_logo_256.png
WARNING:  zero length file opt/google/chrome/product_logo_24.png
WARNING:  zero length file opt/google/chrome/product_logo_16.png
WARNING:  zero length file opt/google/chrome/product_logo_128.png
WARNING:  zero length file opt/google/chrome/nacl_irt_x86_64.nexe
WARNING:  zero length file opt/google/chrome/nacl_helper_bootstrap
WARNING:  zero length file opt/google/chrome/nacl_helper
WARNING:  zero length file opt/google/chrome/locales/en-GB.pak
WARNING:  zero length file opt/google/chrome/libGLESv2.so
WARNING:  zero length file opt/google/chrome/libEGL.so
WARNING:  zero length file opt/google/chrome/icudtl.dat
WARNING:  zero length file opt/google/chrome/google-chrome
WARNING:  zero length file opt/google/chrome/default_apps/youtube.crx
WARNING:  zero length file opt/google/chrome/default_apps/gmail.crx
WARNING:  zero length file opt/google/chrome/default_apps/external_extensions.json
WARNING:  zero length file opt/google/chrome/default_apps/drive.crx
WARNING:  zero length file opt/google/chrome/default_apps/docs.crx
WARNING:  zero length file opt/google/chrome/default-app-block
WARNING:  zero length file opt/google/chrome/cron/google-chrome
WARNING:  zero length file opt/google/chrome/crashpad_handler
WARNING:  zero length file opt/google/chrome/chrome_200_percent.pak
WARNING:  zero length file opt/google/chrome/chrome_100_percent.pak
WARNING:  zero length file opt/google/chrome/chrome-sandbox
WARNING:  gzip test failed on usr/man/man1/google-chrome-stable.1.gz
WARNING:  gzip test failed on usr/share/doc/google-chrome-stable/changelog.gz

Slackware package /Porteus_modules/5.0/chrome/update/google-chrome-87.0.4280.66-x86_64-en-GB-1.txz created.
I have a sneaking suspicion the google-chrome-87.0.4280.66-x86_64-en-GB-1.txz might malfunction…

Code: Select all

 Creating Porteus module ... 
Verifying package google-chrome-87.0.4280.66-x86_64-en-GB-1.txz.
Installing package google-chrome-87.0.4280.66-x86_64-en-GB-1.txz:
PACKAGE DESCRIPTION:
Executing install script for google-chrome-87.0.4280.66-x86_64-en-GB-1.txz.
cp: error writing '/tmp/txz2xzm19934/var/lib/pkgtools/scripts/google-chrome-87.0.4280.66-x86_64-en-GB-1': No space left on device
Package google-chrome-87.0.4280.66-x86_64-en-GB-1.txz installed.

gzip: /tmp/txz2xzm19934/usr/man/man1/google-chrome.1.gz: unexpected end of file

gzip: /tmp/txz2xzm19934/usr/man/man1/google-chrome-stable.1.gz: unexpected end of file
Creating /mnt/sdXY/Porteus_modules/5.0/chrome/update/google-chrome-87.0.4280.66-x86_64-en-GB-1.xzm


gzip: /tmp/txz2xzm19934/usr/man/man1/google-chrome.1.gz: unexpected end of file

gzip: /tmp/txz2xzm19934/usr/man/man1/google-chrome-stable.1.gz: unexpected end of file

Your file is at:  /Porteus_modules/5.0/chrome/update/google-chrome-87.0.4280.66-x86_64-en-GB-1.xzm 
Please move it to your modules folder to survive a reboot.
Why trying to create google-chrome-87.0.4280.66-x86_64-en-GB-1.xzm from a path where the files sit in /tmp/txz2xzm19934/ instead e.g. /Porteus_modules/5.0/chrome/update/tmp/txz2xzm19934 ?

Have the extracted files from google-chrome-stable_current_amd64.deb extracted to a path in /tmp/ or one in /Porteus_modules/ ?

/tmp/ has insufficient free space, but all downloads, extracting and creating of txz and xzm should have happened in /Porteus_modules/5.0/chrome/update/ and not in /tmp/ .

And sadly update-browser seems to have no -k aka --keep option, so aside from corrupted google-chrome-87.0.4280.66-x86_64-en-GB-1.txz and corrupted google-chrome-87.0.4280.66-x86_64-en-GB-1.xzm I not even have google-chrome-stable_current_amd64.deb for manually creating the module.

Porteus v5.0rc1 problems

Posted: 22 Nov 2020, 07:17
by Ed_P
FWIW 5.0rc2 ISO boot using the Porteus Browser Tool

Code: Select all

 Starting checks ... 
[OK] User is root.
[OK] Distro is Porteus
Downloading live script ...
Downloading: update-chrome-live  DONE
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing update-chrome-live  100%  
Work will be done in:  /tmp 
google-chrome is not installed

 Checking latest google-chrome version ... 
[PASS] Latest ver: 87.0.4280.66

 Finished checks. 


#############################################
Welcome to the Porteus google-chrome updater.

Installed version:    
Porteus server version:   87.0.4280.66 
Latest version:   87.0.4280.66 

 Would you like to download the porteus server version? [y/n]
Downloading: google-chrome-87.0.4280.66-x86_64-en-US-1.xzm DONE

Your file is at:  /tmp/google-chrome-87.0.4280.66-x86_64-en-US-1.xzm 
Please move it to your modules folder to survive a reboot.

Code: Select all

guest@porteus:~$ ls -lgh /tmp
total 75M
drwx------ 2 users   40 Nov 22 02:03 Temp-7e0c9964-4c37-413a-8b01-0f0b9156258a/
-rw------- 1 root   75M Nov 19 23:44 google-chrome-87.0.4280.66-x86_64-en-US-1.xzm
drwx------ 2 users   40 Nov 21 16:46 mozilla_guest0/
-rw------- 1 users 514K Nov 21 11:32 tmpaddon
guest@porteus:~$ 

Porteus v5.0rc1 problems

Posted: 22 Nov 2020, 09:00
by ncmprhnsbl
Rava wrote:
22 Nov 2020, 06:46
Why trying to create google-chrome-87.0.4280.66-x86_64-en-GB-1.xzm from a path where the files sit in /tmp/txz2xzm19934/ instead e.g. /Porteus_modules/5.0/chrome/update/tmp/txz2xzm19934 ?
because that's where txz2xzm does it's thing.. as it always has..
basicly makes the working directory option useless, unless also implemented in txz2xzm... or not use that and do it directly(installpkg -root $WRKDIR/blah .. etc) in update-chrome-live..
or probly even better: bypass the whole makepkg/txz2zxm part and make a xzm out of the extracted .deb .. unless someone wants a txz specificly..

Porteus v5.0rc1 problems

Posted: 22 Nov 2020, 17:28
by raja
bypass the whole makepkg/txz2zxm part
Correct. May be due to loyalty to Mother Slackware.

I build Firefox/Opera directly, works just fine

Porteus v5.0rc1 problems

Posted: 22 Nov 2020, 23:59
by Rava
ncmprhnsbl wrote:
22 Nov 2020, 09:00
because that's where txz2xzm does it's thing.. as it always has..
basicly makes the working directory option useless, unless also implemented in txz2xzm... or not use that and do it directly(installpkg -root $WRKDIR/blah .. etc) in update-chrome-live..
or probly even better: bypass the whole makepkg/txz2zxm part and make a xzm out of the extracted .deb .. unless someone wants a txz specificly..
So what can l do getting my module?

Would using dir2xzm instead of txz2xzm do the trick?

And how to prevent update-browser from deleting the downloaded file, google-chrome-stable_current_amd64.deb in this case?

Porteus v5.0rc1 problems

Posted: 23 Nov 2020, 04:55
by ncmprhnsbl
Rava wrote:
22 Nov 2020, 23:59
So what can l do getting my module?
:cry:
Rava wrote:
22 Nov 2020, 23:59
And how to prevent update-browser from deleting the downloaded file, google-chrome-stable_current_amd64.deb in this case?
if you go to <whereever-the-heck-google-keeps-it> grab it directly, put it in the folder you're using as a work directory and the script will find it and use it(and not delete it when it's finished) .. yes, yes, you'll need a browser for that, probly one of the other ones..
i'm considering adding this "keep" type option, the trick is not adding too much complexity, and not breaking stuff.
also need to find another way to find the lastest version, instead of using https://www.whatismybrowser.com/guides/ ... ion/chrome because they block your IP after a while, cause they don't like being scraped for info..

Porteus v5.0rc1 problems

Posted: 23 Nov 2020, 11:22
by Rava
ncmprhnsbl wrote:
23 Nov 2020, 04:55
if you go to <whereever-the-heck-google-keeps-it> grab it directly, put it in the folder you're using as a work directory and the script will find it and use it(and not delete it when it's finished) ..
Can your script be hacked so that it only does the downloading and then stops?

Is that part of the plain text script or part of binary makeself?

Porteus v5.0rc1 problems

Posted: 23 Nov 2020, 12:33
by ncmprhnsbl
new version uploaded: now it just makes a module from the extracted .deb, without making a slackware package first, so your issues with running out of space should be dealt with.
also found a better source for the version info, that shouldn't get blocked.
Rava wrote:
23 Nov 2020, 11:22
Can your script be hacked so that it only does the downloading and then stops?
sure
Rava wrote:
23 Nov 2020, 11:22
Is that part of the plain text script or part of binary makeself?
the script (hint "cleanup")
but it's far easier to :
if you go to <whereever-the-heck-google-keeps-it> grab it directly, put it in the folder you're using as a work directory and the script will find it and use it(and not delete it when it's finished) ..

Porteus v5.0rc1 problems

Posted: 23 Nov 2020, 12:38
by Rava
ncmprhnsbl wrote:
23 Nov 2020, 12:33
it's far easier to :
if you go to <whereever-the-heck-google-keeps-it> grab it directly, put it in the folder you're using as a work directory and the script will find it and use it(and not delete it when it's finished) ..
brilliant idea! Adding a parameter that makes the script only tell the user the download URL - without downloading. :celebrate3:

Porteus v5.0rc1 problems

Posted: 23 Nov 2020, 12:49
by ncmprhnsbl
Rava wrote:
23 Nov 2020, 12:38
brilliant idea! Adding a parameter that makes the script only tell the user the download URL - without downloading.
that's not what i wrote...

Porteus v5.0rc1 problems

Posted: 23 Nov 2020, 12:54
by Rava
ncmprhnsbl wrote:
23 Nov 2020, 12:49
that's not what i wrote...
no but one can dream. :D

Porteus v5.0rc1 problems

Posted: 07 Dec 2020, 00:53
by Rava
XFCE issue, or maybe not?
From a root Thunar I started a terminal, did some setup changes and fired up my changes.sh - inspired by Ed_P's changes.sh:

Code: Select all

#!/bin/sh
# original script by Ed_P, this version by Rava
# V0.1
if [ $UID -ne 0 ]; then
	echo You have to be root.
	exit 1
fi
declare -i X=1
if [ ! "$1"x == ""x ]; then
	X=$1
fi
if [ $X -eq 0 -o $X -lt 0 ]; then
	X=1
	echo " mmin manually set to 1"
fi

echo "Will list all changes in the system going back mmin (${X}) minute(s)"
echo -e "________________________________________________________________________________\n"

find /mnt/live/memory/changes -mmin -$X

echo -e "________________________________________________________________________________\npress enter to exit…"

read
exit 0
to find recent changes for saving the needed ones in rootcopy/ or rootcopy.xzm:

Code: Select all

root@porteus:/# changes.sh 
Will list all changes in the system going back mmin (1) minute(s)
________________________________________________________________________________

/mnt/live/memory/changes/root/.cache/dconf/user
/mnt/live/memory/changes/root/.config/xfce4/terminal
/mnt/live/memory/changes/root/.config/xfce4/terminal/terminalrc
/mnt/live/memory/changes/var/lib/NetworkManager
/mnt/live/memory/changes/var/lib/NetworkManager/timestamps
/mnt/live/memory/changes/var/log/messages
________________________________________________________________________________
press enter to exit…
so what I want to save is obvious /root/.config/xfce4/terminal/terminalrc - but I wondered what's with /root/.cache/dconf/user - the user's dconf database usually sits in ~/.config/dconf/user not in ~/.cache/dconf/user , so I looked further:

Code: Select all

root@porteus:/# alias l
alias l='/bin/ls -oa --color=auto --time-style=long-iso'
root@porteus:/# file  ~/.config/dconf/user  ~/.cache/dconf/user
/root/.config/dconf/user: GVariant Database file, version 0
/root/.cache/dconf/user:  data
root@porteus:/# l  ~/.config/dconf/user  ~/.cache/dconf/user
-rw------- 1 root     2 2020-12-07 01:29 /root/.cache/dconf/user
-rw------- 1 root 10475 2020-04-02 17:36 /root/.config/dconf/user
What is the use of storing a mere 2 bytes in ~/.cache/dconf/user while leaving ~/.config/dconf/user unaltered?

Especially since it seems nothing got stored:

Code: Select all

root@porteus:/# hexdump -C ~/.cache/dconf/user
00000000  00 00                                             |..|
00000002