firefox 50.0b4 and flashplayer-plugin-23.0.0.162-x86_64-1.xzm(both via update-<> scripts) are working for me..Ed_P wrote:Neither of these options produces a working flashplayer plugin for Firefox.
Porteus-v3.2rc5 bug reports
- ncmprhnsbl
- DEV Team
- Posts: 3938
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Re: Porteus-v3.2rc5 bug reports
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
Re: Porteus-v3.2rc5 bug reports
When booting into Porteus from an iso file using from= cheatcode:
The environment variable $PORTDIR shows incorrect path:
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
Code: Select all
guest@porteus:~$ cat /proc/cmdline
quiet BOOT_IMAGE=/porteus/vmlinuz from=/porteus/Porteus-CINNAMON-v3.2rc5-x86_64.iso
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
All credits go to Ed_P for noticing this here: http://forum.porteus.org/viewtopic.php? ... =15#p49327
- Ed_P
- Contributor
- Posts: 8369
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Porteus-v3.2rc5 bug reports
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.ncmprhnsbl wrote:firefox 50.0b4 and flashplayer-plugin-23.0.0.162-x86_64-1.xzm(both via update-<> scripts) are working for me..
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
Ed
- Blaze
- DEV Team
- Posts: 3885
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
- Contact:
Re: Porteus-v3.2rc5 bug reports
FURRY_NOVA, modules for both architectures:
Cheers
Cheers
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: Porteus-v3.2rc5 bug reports
We also need:
NetworkManager-pptp
NetworkManager-openvpn
NetworkManager-vpnc
NetworkManager-pptp
NetworkManager-openvpn
NetworkManager-vpnc
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: Porteus-v3.2rc5 bug reports
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.
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.
Last edited by brokenman on 07 Oct 2016, 23:10, edited 2 times in total.
Reason: typo
Reason: typo
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
- Ed_P
- Contributor
- Posts: 8369
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Porteus-v3.2rc5 bug reports
-update-Ed_P wrote: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.ncmprhnsbl wrote:firefox 50.0b4 and flashplayer-plugin-23.0.0.162-x86_64-1.xzm(both via update-<> scripts) are working for me..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
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:~$
Ed
- ncmprhnsbl
- DEV Team
- Posts: 3938
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Re: Porteus-v3.2rc5 bug reports
the only thing i can think to suggest is restart firefox.... i've had no problem with any combination of firefox and flash versions...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
(note firefox will incorrectly display flash 23* as 11*)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
- Ed_P
- Contributor
- Posts: 8369
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Porteus-v3.2rc5 bug reports
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.
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.
Last edited by Ed_P on 08 Oct 2016, 18:35, edited 1 time in total.
Ed
- Blaze
- DEV Team
- Posts: 3885
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
- Contact:
Re: Porteus-v3.2rc5 bug reports
I don't have a new versions of these packages or building scripts for Slackware 14.2.brokenman wrote:We also need:
NetworkManager-pptp
NetworkManager-openvpn
NetworkManager-vpnc
Linux Kernel 4.8.1 is out
https://www.kernel.org/
***
Waiting the final release of Porteus 3.2
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
Re: Porteus-v3.2rc5 bug reports
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?
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!
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
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!
- FURRY_NOVA
- Black ninja
- Posts: 84
- Joined: 11 Aug 2016, 17:26
- Distribution: Porteus XFCE v3.2 i586
- Location: United Kingdom
Re: Porteus-v3.2rc5 bug reports
You're a life saver, mate, thanks a lot. It'stable so far, I'll keep note here if any issues.Blaze wrote:FURRY_NOVA, modules for both architectures:
Cheers
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.
New to Linux but learning. Hoping to help out Porteus community.
- Ed_P
- Contributor
- Posts: 8369
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Porteus-v3.2rc5 bug reports
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.
Ed
- Ed_P
- Contributor
- Posts: 8369
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Porteus-v3.2rc5 bug reports
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.ncmprhnsbl wrote:the only thing i can think to suggest is restart firefox.... i've had no problem with any combination of firefox and flash versions...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
(note firefox will incorrectly display flash 23* as 11*)
Ed
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: Porteus-v3.2rc5 bug reports
Blaze,
https://download.gnome.org/sources/
https://download.gnome.org/sources/
Good idea.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?
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.