Porteus-v3.2rc5 bug reports

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.
User avatar
ncmprhnsbl
Full of knowledge
Full of knowledge
Posts: 843
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Porteus-v3.2rc5 bug reports

Post#121 by ncmprhnsbl » 07 Oct 2016, 07:21

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..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

jssouza
Samurai
Samurai
Posts: 179
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

Re: Porteus-v3.2rc5 bug reports

Post#122 by jssouza » 07 Oct 2016, 10:29

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: viewtopic.php?f=94&t=6256&start=15#p49327

User avatar
Ed_P
Contributor
Contributor
Posts: 3156
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#123 by Ed_P » 07 Oct 2016, 15:16

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
Ed

User avatar
Blaze
Moderator
Moderator
Posts: 1383
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus 3.2 Cinnamon x86_64
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Re: Porteus-v3.2rc5 bug reports

Post#124 by Blaze » 07 Oct 2016, 19:38

Linux porteus 4.12.7-porteus #1 SMP PREEMPT Sun Aug 13 17:38:30 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

User avatar
brokenman
Site Admin
Site Admin
Posts: 5456
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v3.2rc5 bug reports

Post#125 by brokenman » 07 Oct 2016, 22:43

We also need:

NetworkManager-pptp
NetworkManager-openvpn
NetworkManager-vpnc
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5456
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v3.2rc5 bug reports

Post#126 by brokenman » 07 Oct 2016, 23:04

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.
Last edited by brokenman on 07 Oct 2016, 23:10, edited 2 times in total.
Reason: typo
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3156
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#127 by Ed_P » 07 Oct 2016, 23:48

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:~$ 
Ed

User avatar
ncmprhnsbl
Full of knowledge
Full of knowledge
Posts: 843
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Porteus-v3.2rc5 bug reports

Post#128 by ncmprhnsbl » 08 Oct 2016, 05:32

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*)
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Ed_P
Contributor
Contributor
Posts: 3156
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#129 by Ed_P » 08 Oct 2016, 06:44

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.
Last edited by Ed_P on 08 Oct 2016, 18:35, edited 1 time in total.
Ed

User avatar
Blaze
Moderator
Moderator
Posts: 1383
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus 3.2 Cinnamon x86_64
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Re: Porteus-v3.2rc5 bug reports

Post#130 by Blaze » 08 Oct 2016, 08:59

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
Linux porteus 4.12.7-porteus #1 SMP PREEMPT Sun Aug 13 17:38:30 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

jssouza
Samurai
Samurai
Posts: 179
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

Re: Porteus-v3.2rc5 bug reports

Post#131 by jssouza » 08 Oct 2016, 13:14

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!

User avatar
FURRY_NOVA
Black ninja
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

Post#132 by FURRY_NOVA » 08 Oct 2016, 15:37

You're a life saver, mate, thanks a lot. :beer: 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.
New to Linux but learning. Hoping to help out Porteus community. :)

User avatar
Ed_P
Contributor
Contributor
Posts: 3156
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#133 by Ed_P » 08 Oct 2016, 15:46

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.
:shock:
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3156
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus-v3.2rc5 bug reports

Post#134 by Ed_P » 08 Oct 2016, 18:29

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. :wall:
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5456
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v3.2rc5 bug reports

Post#135 by brokenman » 08 Oct 2016, 20:27

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.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply