Page 9 of 15
Re: Porteus-v3.2rc5 bug reports
Posted: 07 Oct 2016, 07:21
by ncmprhnsbl
Ed_P wrote:Neither of these options produces a working flashplayer plugin for Firefox.
firefox 50.0b4 and flashplayer-plugin-23.0.0.162-x86_64-1.xzm(both via update-<> scripts) are working for me..
Re: Porteus-v3.2rc5 bug reports
Posted: 07 Oct 2016, 10:29
by jssouza
When booting into Porteus from an iso file using from= cheatcode:
Code: Select all
guest@porteus:~$ cat /proc/cmdline
quiet BOOT_IMAGE=/porteus/vmlinuz from=/porteus/Porteus-CINNAMON-v3.2rc5-x86_64.iso
The environment variable $PORTDIR shows incorrect path:
Code: Select all
guest@porteus:~$ echo $PORTDIR
/mnt/isoloop/porteus
guest@porteus:~$ ls $PORTDIR
/bin/ls: cannot access '/mnt/isoloop/porteus': No such file or directory
The actual path is /mnt/live/mnt/isoloop. The file
/var/log/porteus-livedbg also shows wrong paths to the loaded modules.
All credits go to
Ed_P for noticing this here:
http://forum.porteus.org/viewtopic.php? ... =15#p49327
Re: Porteus-v3.2rc5 bug reports
Posted: 07 Oct 2016, 15:16
by Ed_P
ncmprhnsbl wrote:firefox 50.0b4 and flashplayer-plugin-23.0.0.162-x86_64-1.xzm(both via update-<> scripts) are working for me..
Thanks
ncmprhnsb.
I'll give 50.0b4 a try. I'm currently using firefox-48.0b6-x86_64-1.xzm. I've tried various versions of the flashplayer.
Code: Select all
firefox-47.0b9-x86_64-1.xyzm
firefox-48.0b6-x86_64-1.xzm
flashplayer-plugin-11.2.202.635-x86_64-1alien.xyzm
flashplayer-plugin-22.0.0.209-x86_64-1.xyzm
flashplayer-plugin-23.0.0.162-x86_64-1.xyzm
Re: Porteus-v3.2rc5 bug reports
Posted: 07 Oct 2016, 19:38
by Blaze
FURRY_NOVA, modules for both architectures:
Cheers
Re: Porteus-v3.2rc5 bug reports
Posted: 07 Oct 2016, 22:43
by brokenman
We also need:
NetworkManager-pptp
NetworkManager-openvpn
NetworkManager-vpnc
Re: Porteus-v3.2rc5 bug reports
Posted: 07 Oct 2016, 23:04
by brokenman
When booting from an ISO there really is no porteus folder. It is locked up inside the ISO and so there has so far been no need to know where it is. You can't write to it nor read from it.
The ISO file from which porteus booted is shown in /var/log/porteus-livedbg as ISO=/path/to/porteus.iso (v3.2+)
Porteus did in fact boot from /mnt/isoloop. It copied the data into ram and then unmounted this point. Everything is relative to where initrd was when it booted which was /mnt/live.
There are some scripts that check for the string isoloop in porteus-livedbg to know if Porteus booted from an ISO so it can modify behaviour in terms of putting downloaded modules into a non-existent porteus folder.
EDIT:
What I am getting at here is that all scripts that need to know if Porteus booted from an ISO should do the check. If they require access to the loaded modules they should add the /mnt/live prefix to the modules.
Re: Porteus-v3.2rc5 bug reports
Posted: 07 Oct 2016, 23:48
by Ed_P
Ed_P wrote:ncmprhnsbl wrote:firefox 50.0b4 and flashplayer-plugin-23.0.0.162-x86_64-1.xzm(both via update-<> scripts) are working for me..
Thanks
ncmprhnsb.
I'll give 50.0b4 a try. I'm currently using firefox-48.0b6-x86_64-1.xzm. I've tried various versions of the flashplayer.
Code: Select all
firefox-47.0b9-x86_64-1.xyzm
firefox-48.0b6-x86_64-1.xzm
flashplayer-plugin-11.2.202.635-x86_64-1alien.xyzm
flashplayer-plugin-22.0.0.209-x86_64-1.xyzm
flashplayer-plugin-23.0.0.162-x86_64-1.xyzm
-update-
Running 50.0b5 with the same flash problem. (The latest results from update-firefox.) The only addon shown is one for OpenH264 Video Codec
In the /tmp folder the Firefox xzm module has a lock icon and a red X icon on it. What does the
X indicate.
Code: Select all
usr/lib64/firefox-50.0b5/distribution/searchplugins/locale/en-US/ddg.xml
Restoring permissions of /tmp/portff/ff.1696 to chmod 700
Slackware package /tmp/firefox-50.0b5-x86_64-1.txz created.
/tmp/portff
Verifying package firefox-50.0b5-x86_64-1.txz.
Installing package firefox-50.0b5-x86_64-1.txz:
PACKAGE DESCRIPTION:
Executing install script for firefox-50.0b5-x86_64-1.txz.
Package firefox-50.0b5-x86_64-1.txz installed.
Creating /tmp/firefox-50.0b5-x86_64-1.xzm
DONE
root@porteus:/home/guest# ls /tmp/
firefox-50.0b5-x86_64-1.txz firefox-50.0b5-x86_64-1.xzm pulse-PKdhtXMmr18n/
root@porteus:/home/guest#
Code: Select all
guest@porteus:~$ ls /mnt/live/memory/images/f*
/mnt/live/memory/images/firefox-50.0b5-x86_64-1.xzm:
home/ usr/ var/
/mnt/live/memory/images/flashplayer-plugin-23.0.0.162-x86_64-1.xzm:
usr/ var/
guest@porteus:~$
Re: Porteus-v3.2rc5 bug reports
Posted: 08 Oct 2016, 05:32
by ncmprhnsbl
Ed_P wrote:Running 50.0b5 with the same flash problem. (The latest results from update-firefox.) The only addon shown is one for OpenH264 Video Codec
the only thing i can think to suggest is restart firefox.... i've had no problem with any combination of firefox and flash versions...
(note firefox will incorrectly display flash 23* as 11*)
Re: Porteus-v3.2rc5 bug reports
Posted: 08 Oct 2016, 06:44
by Ed_P
Rebooting doesn't even help.
It's too bad the USM apps can't be made to work with 3.2.
BTW If you use a save.dat file and a update-firefox module be sure to have a save.dat of at least 1GB. The default update-firefox Firefox allocates a .5 GB to a cache and saves up to 15 copies of the bookmarks files. My save.dats are usually .5 GB or less. Of course if you remember to change them you should be ok. I did mine as 983040 B and 2.
Re: Porteus-v3.2rc5 bug reports
Posted: 08 Oct 2016, 08:59
by Blaze
brokenman wrote:We also need:
NetworkManager-pptp
NetworkManager-openvpn
NetworkManager-vpnc
I don't have a new versions of these packages or building scripts for Slackware 14.2.
Linux Kernel 4.8.1 is out
https://www.kernel.org/
***
Waiting the final release of Porteus 3.2
Re: Porteus-v3.2rc5 bug reports
Posted: 08 Oct 2016, 13:14
by jssouza
Hi brokenman,
Still on the isoloop. Instead of changing the path itself (/mnt/isoloop to /mnt/live/mnt/isoloop), couldn't the path be given via a symlink?
Code: Select all
ln -s /mnt/live/mnt/isoloop /mnt/isoloop
This way $PORTDIR would be reliable across all booted variants (/mnt/sdxn /mnt/srn and /mnt/isoloop).
I executed update-porteus after creating the symlink and it still correctly exited with the error saying cannot update when booted from ISO.
Maybe other scripts break with this... Pardon my ignorance if I am wrong about the addition of a symlink.
Thanks!
Re: Porteus-v3.2rc5 bug reports
Posted: 08 Oct 2016, 15:37
by FURRY_NOVA
Blaze wrote:FURRY_NOVA, modules for both architectures:
Cheers
You're a life saver, mate, thanks a lot.
It'stable so far, I'll keep note here if any issues.
Edit: Forgot to mention. If anyone has trouble downloading them by link on page. Close the mediafire page, re-open link here and re-download again. Took me few times for it to work and sometimes says couldn't find download link in download manager.
Re: Porteus-v3.2rc5 bug reports
Posted: 08 Oct 2016, 15:46
by Ed_P
jssouza wrote:I executed update-porteus after creating the symlink and it still correctly exited with the error saying cannot update when booted from ISO.
Re: Porteus-v3.2rc5 bug reports
Posted: 08 Oct 2016, 18:29
by Ed_P
ncmprhnsbl wrote:Ed_P wrote:Running 50.0b5 with the same flash problem. (The latest results from update-firefox.) The only addon shown is one for OpenH264 Video Codec
the only thing i can think to suggest is restart firefox.... i've had no problem with any combination of firefox and flash versions...
(note firefox will incorrectly display flash 23* as 11*)
Surprise, surprise.
I've booted into Always Fresh mode and Flash now shows as a plugin. So something in my changes= file is causing the problem.
Re: Porteus-v3.2rc5 bug reports
Posted: 08 Oct 2016, 20:27
by brokenman
Blaze,
https://download.gnome.org/sources/
Still on the isoloop. Instead of changing the path itself (/mnt/isoloop to /mnt/live/mnt/isoloop), couldn't the path be given via a symlink?
Good idea.