Porteus 5.0 RC2 bug reports

[rchase]

...
also the changes=EXIT or changes-ro cheatcode might be of some interest.

I deleted the /changes folder of my Porteus 5.0rc2 (with new kernel) test installation and booted with:

Code: Select all

APPEND from=UUID:"3d99f0ce-54f5-48b9-bc1d-5926d0e45f3e"/testPorteus changes=EXIT:UUID:"3d99f0ce-54f5-48b9-bc1d-5926d0e45f3e"/testPorteus/porteus utc timezone=America/Denver login=root

. As before, Porteus booted up with the xfce-blue wallpaper, Adwaita-dark theme, and Elementary icons selected and no network access. All I'm trying to do is to use the new release with persistence.

[otan]

Palemoon

Code: Select all

guest@porteus:~$ slackyd -c slackyd.conf -d palemoon  

Checking palemoon-28.12.0-x86_64-enGB: done.

Found 2 missing dependencies:
libgtk-x11-2.0.so.0 required by:
 --> Package: palemoon-28.12.0-x86_64-enGB (/opt/palemoon/browser/components/libbrowsercomps.so)
 --> Package: palemoon-28.12.0-x86_64-enGB (/opt/palemoon/libxul.so)
 --> Package: palemoon-28.12.0-x86_64-enGB (/opt/palemoon/updater)
libgdk-x11-2.0.so.0 required by:
 --> Package: palemoon-28.12.0-x86_64-enGB (/opt/palemoon/browser/components/libbrowsercomps.so)
 --> Package: palemoon-28.12.0-x86_64-enGB (/opt/palemoon/libxul.so)
 --> Package: palemoon-28.12.0-x86_64-enGB (/opt/palemoon/updater)

Searching libgtk-x11-2.0.so.0: found 1 package.
Searching libgdk-x11-2.0.so.0: found 1 package.

Download gtk+2-2.24.32-x86_64-3.txz [from slackware] ? [y/N] y

Downloading gtk+2-2.24.32-x86_64-3.txz. [ok]
* Verify md5 checksum: ok.

Fix

Code: Select all

root@porteus:/home/guest# txz2xzm /tmp/gtk+2-2.24.32-x86_64-3.txz
Verifying package gtk+2-2.24.32-x86_64-3.txz.
Installing package gtk+2-2.24.32-x86_64-3.txz:
PACKAGE DESCRIPTION:
# gtk+2 (multi-platform GUI toolkit)
#
# This is GTK+, a multi-platform toolkit for creating graphical user
# interfaces. Offering a complete set of widgets, GTK+ is suitable for
# projects ranging from small one-off projects to complete application
# suites.
#
Executing install script for gtk+2-2.24.32-x86_64-3.txz.
Package gtk+2-2.24.32-x86_64-3.txz installed.
Creating /tmp/gtk+2-2.24.32-x86_64-3.xzm

root@porteus:/home/guest# activate /tmp/gtk+2-2.24.32-x86_64-3.xzm
Updating shared library links:  /sbin/ldconfig
Updating GTK immodules: /usr/bin/update-gtk-immodules

[fulalas]

@otan, not all DEs come with GTK2 (only Openbox and Xfce), so that's acceptable. Also, our browser downloader tool doesn't solve dependencies as it's very simple by design. Thanks for reporting anyway

[roadie]

@ rchase
The radio button "Save sessions for future logins" should save open windows
so they do re-appear after a reboot.
Those sessions are stored in ~/.cache/sessions/ and have nothing to do with changes
you make to the system.

also the changes=EXIT or changes-ro cheatcode might be of some interest.

I'd like an answer to my several questions -- with respect to how Porteus makes changes, why is the /changes folder written at boot? It must incorporate changes made by the loading of packages as well as changes I make to my desktop, else why does networking fail the instant I attempt to use persistence, having done nothing else? I've verified that I have network access under Porteus 5.0rc2 with or without using the new kernel; how do I proceed to configure my desktop and make changes persistent? The "change-ro" cheatcode is of zero relevance, so far as I can see; networking breaks because I am trying to save changes -- I'm not repeatedly breaking Porteus doing something else and need to hold off committing changes!

Porteus doesn't write to the changes folder at boot. There's nothing to write at boot as nothing has been done to create changes. If networking fails when you try to use persistence that indicates that there's something wrong with previous changes that are in the folder. If you see an empty changes folder after booting in Always Fresh, that's because it's part of the files in the ISO, it's not created at boot.

The method you're using for saving changes to a partition is fine. It will save everything that changes when it changes, it needs no input from the user. But, it will save all changes, good or bad, it has no way of determining which is which.

You mentioned that you were able to boot and get network access, I'd suggest you do that, in Always Fresh mode, get things the way you want them. Then delete any change folders that may be in place, and copy the changes folder in /mnt/live/memory to the partition you want to save on. If that doesn't work, then I have no idea what's happening.

I downloaded rc2, set up the command line for changes and it works fine here. It works as it always has.

[donald]

5.0rc2 -- Porteus-installer-for-Linux.com failed with error code 3
so I took the one from 5.0rc1 - this worked, partly.
Booting the drive (usb thumbdrive ext2) showed a "vesamenu.c32 is not
a..." (don't remember) error.
so I also copied this file from rc1 -- bingo, now it boots.

[ The host PC runs a 32 bit porteus and I didn't copy
the EFI folder onto the usb thumbdrive because it is a BIOS PC ]
That should be fine because it always was.

[rchase]

@ rchase
The radio button "Save sessions for future logins" should save open windows
so they do re-appear after a reboot.
...

P.S. You're right about the radio button correlating with the state of opened windows on the desktop (so I shouldn't call it "non-functional"), but since when I boot with "changes=" (or "changes=EXIT:") I have no networking and since the situation persists when I eliminate "changes=", I know that Porteus wrote something in /changes prior to shutdown that disabled networking. I just verified this by booting into Porteus 5.0rc2 with no /changes folder but the "changes=" cheatcode set, then immediately rebooting without it; I had no networking before or after.

[rchase]

...
also the changes=EXIT or changes-ro cheatcode might be of some interest.

I deleted the /changes folder of my Porteus 5.0rc2 (with new kernel) test installation and booted with:

Code: Select all

APPEND from=UUID:"3d99f0ce-54f5-48b9-bc1d-5926d0e45f3e"/testPorteus changes=EXIT:UUID:"3d99f0ce-54f5-48b9-bc1d-5926d0e45f3e"/testPorteus/porteus utc timezone=America/Denver login=root

. As before, Porteus booted up with the xfce-blue wallpaper, Adwaita-dark theme, and Elementary icons selected and no network access. All I'm trying to do is to use the new release with persistence.

roadie, I just finished pointing out that Porteus writes the /changes folder to the installation medium when it's not there even in "Always Fresh" mode -- when the "changes=" cheatcode is used, the folder is populated at boot despite the fact that more changes will have to be written at shutdown -- are you trying to dispute this? I've described how I established this. "... delete any change folders that may be in place, and copy the changes folder in /mnt/live/memory to the partition you want to save on ..." -- isn't this exactly what the Porteus Save Session dialog does? It's great that Porteus 5.0rc2 works on your machine -- when I try to enable persistence, networking immediately fails on mine.

[rchase]

I was mistaken -- when I booted in "Always Fresh", Porteus used data from my main installation (running Porteus 5.0rc1); I've never had network access using rc2.

[roadie]

I just booted Porteus in Always Fresh mode......there was no changes directory before I booted.......there was no changes directory after I booted. I had previously removed the empty changes folder that is placed along with the other folders when Porteus is installed. Not trying to dispute anything, just sayin it doesn't do it on my machine.

Yes, if the cheatcode "changes=/dev/XXXXX is used, then a changes folder is created if one is not already present......but this is not the case when booting Always Fresh........Always Fresh mode means no changes of any kind are loaded, no modules, no rootcopy, no changes folder, only the base is loaded. It's the only way to track down problems.

I again suggest booting Always Fresh from the menu with nothing appended.......just from the menu, don't TAB and change the command line. Then run the previous commands......lspci -k.....dmesg.....lsmod.....if there are no kernel modules loaded then lsmod will show that.

If no kernel modules are loaded, then there's a mismatch with the kernel modules and vmlinuz.

[ncmprhnsbl]

5.0rc2 -- Porteus-installer-for-Linux.com failed with error code 3

when we looked at fixing the installer (wasn't working for newer kernels, might have actually been ok for the 5.4 series), we didn't think of the install 64bit via a 32bit host scenario.. which is why the old version would work: it's entirely 32bit. since the new one has both 32 and 64bit syslinux binaries, i guess the script is detecting the target and trying run the 64bit binary which would fail... ..maybe.. anyway, thanks, we'll need to look at this one a little harder..

[ncmprhnsbl]

/usr/bin/rpm2xzm: line 100: gtkdialog.py: command not found

thanks, missing the full path, fixed in the scripts git repo

[donald]

5.0rc2 XFCE

CPU-Graph plugin:
right-click > move, don't work
left-click > opens Task-manager

Application button:
right-click > properties > icon not shown
click on icon button > select an icon window > no icons shown until
selected (once) and window closed.

Desktop Settings:
Menus > Desktop Menu > uncheck "include applications menu on desktop right click"
has no effect.

Porteus settins center > security > firewall > firewall manager:
does it work? - all options seems to have the same settings!
( iptables -L -v )

[ncmprhnsbl]

not all DEs come with GTK2 (only Openbox and Xfce), so that's acceptable.

lxde too? i do plan to add a gtk2 bundle for DEs that don't have it to the bundles collection, and add a section to the palemoon script to check for it's presence and maybe offer to fetch it, if absent..

[ncmprhnsbl]

Porteus settins center > security > firewall > firewall manager:
does it work? - all options seems to have the same settings!
( iptables -L -v )

yep, no, it's one of the 'works in progress' .. it's works in the sense that the firewall can be turned on/off, but only the 'normal' level, not the strict & blockall..
also, in /etc/rc.d/rc.Firewall i commented line 48: "#$IPTABLES -P OUTPUT DROP ## this breaks ping... should it?" to allow ping, sftp to work..
any input on what 'sensible' firewall rules should be, is welcome..

[fulalas]

@donald:
1- it moves on my machine. Have you tried in Always Fresh?
2- this is just the default setting. You can change the associated command in the plugin properties -> advanced tab
3- this is a known little issue that is probably upstream's fault (i.e. nothing related to Porteus). Since it doesn't affect normal use, I wouldn't mind if I were you
4- it works for me. You should try in AF. This option only enables/disables an entry in the context menu when right click on the desktop.
5- this one ncm has answered

@ncm, yes, LXDE as well! Gosh, so many DEs that sometimes I get confused