Porteus-v3.2rc3 Bug Reports

[tome]

Blaze, are you trying rpm2xzm in Fresh Mode without devel, 7zip, peazip...?

Fujitsu P702 xfce4-x86_64
I can't also use Ctrl+Alt+F-key to switch sessions - many warnings, pictures here: https://www.dropbox.com/sc/axrmjkznsbcb ... gAhtxhDCha
In menu (porteus-button) switch icon and user icon don't work "Failed to execute child process "mugshot" (No such file or directory)"

[brokenman]

@Tome
Please try adding this link for now.
ln -s /lib64/libdb-4.4.so /usr/lib64/libdb-4.8.so

@Blaze
Bleachbit will be removed from xfce4.
The two missing icons (at the bottom) in nemo ... after installing various icon packages I still can't find the correct icon names.

@Ed_P
Not sure why in v3.0 you get a return from guest when calling init. init is in sbin and as such guest should not even know about it.

[burdi01]

@Jack: The engrampa/iso problem is a know one.

Just mount iso file from CLI.

Code: Select all

mkdir  iso
sudo  mount file.iso  iso

So far had no problem with this.

Better to use gvfsd-archive for mount ISO. In CLI it will be

Code: Select all

cd here_directory_where_your_ISO_file
sudo /usr/libexec/gvfsd-archive file=here_name_of_ISO_file

@Bogomips: As it is so convenient to open an ISO in Caja (the mate "nautilus", which then calls engrampa (the mate "file-roller"), which then calls 7z (the [un]zipper) I regard mounting the ISO from the CLI as a workaround in this case.

@Blaze: What is the advantage of using gvfsd-archive over Bogomips' mount?

@All: But you are missing my point. Engrampa/7z is not to blame (though 7z might be somewhat more lenient here): big ISOs produced by mkisofs have problems, the same big ISOs produced by genisoimage or xorriso are ok.
How to repack such an ISO is described in https://drive.google.com/file/d/0B0gP2v ... sp=sharing. Have a look at the mkgriso script therein. “Your changes” are to untar this tar to the root of the cdrom and amend the “VER” in the script.

[Blaze]

tome, with devel.

burdi01, gvfsd-archive is easily to mounts ISO files into the left sidebar of the file manager (Thunar, etc)

The two missing icons (at the bottom) in nemo ... after installing various icon packages I still can't find the correct icon names.

I think you are forgot about nemo-data package. I converted nemo-data (2.2.4-2) (probably there is a newer version) to xzm module nemo-data_2.2.4-2_all.xzm

I tested it and all icons are present - look at this screenshot

Code: Select all

/usr/share/icons/hicolor/scalable/actions/location-symbolic.svg
/usr/share/icons/hicolor/scalable/actions/sidebar-hide-symbolic.svg
/usr/share/icons/hicolor/scalable/actions/sidebar-places-symbolic.svg
/usr/share/icons/hicolor/scalable/actions/sidebar-show-symbolic.svg
/usr/share/icons/hicolor/scalable/actions/sidebar-tree-symbolic.svg
/usr/share/icons/hicolor/scalable/actions/view-compact-symbolic.svg

Xfce x86_64 RC3

Code: Select all

root@porteus:~# firefox
Vector smash protection is enabled.

(plugin-container:1595): Gtk-WARNING **: /usr/lib64/gtk-2.0/2.10.0/engines/libadwaita.so: cannot open shared object file: No such file or directory

(plugin-container:1595): Gtk-WARNING **: /usr/lib64/gtk-2.0/2.10.0/engines/libadwaita.so: cannot open shared object file: No such file or directory
Vector smash protection is enabled.
root@porteus:~#

[rchase]

Porteus-v3.2rc3 x86 XFCE does not recognize the Linux installation script as such and opens Mousepad instead of executing it -- how can I install Porteus to a partition on a hard drive?

[Ed_P]

@Ed_P
Not sure why in v3.0 you get a return from guest when calling init. init is in sbin and as such guest should not even know about it.

Must have been a fanthom tweak. Probably a bash script named init that guest can access.

[Jack]

Mate rc3 x86_64

I try to open a ISO file with Engrampa 1.14.0 and I got a error and the error was "An error occurred while loading the archive." Can some verify that?

I install this old file "p7zip-9.20.1-x86_64-1_slack.txz" and converted it to "p7zip-9.20.1-x86_64-1_slack.xzm" and it fixed the ISO problem I had. It might be wrong way to fix it but it works for me.

[scdbackup]

Hi,

as developer of xorriso i have to nitpick that it is not the
size of the ISO but the existence of empty files which makes
mkisofs output indigestible for 7z.

mkisofs uses block address 4294967280 (aka 0xfffffff0 aka -16)
for files which are no directories and contain no data bytes.
7z checks sanity of block addresses versus ISO size.

Have a nice day

Thomas

[francois]

Sorry for being absent in the testing of this rc3. Will there be a rc4? Would it be of any help for me to test rc3 at this point?

[Ed_P]

Would it be of any help for me to test rc3 at this point?

I would think so. You might find something new or confirm someone else's findings.

[brokenman]

I think you are forgot about nemo-data package.
Not forgot. I didn't even know if existed. It is not in the Cinnamon Slack Builds. Thanks for doing the extra work. I will include this extra package.

Porteus-v3.2rc3 x86 XFCE does not recognize the Linux installation script as such and opens Mousepad instead of executing it
Thanks. Will check out the mimetypes.

how can I install Porteus to a partition on a hard drive?
The same way as installing on a USB device except you DON'T want to run the Porteus-installer script. This will wipe the boot record and only porteus will boot. If you already have a bootloader in place just tweak the config file to add Porteus.

Must have been a fanthom tweak. Probably a bash script named init that guest can access.
I can find no such script in v3.1. I will add it to the next release. It at least gives a sane message.

I install this old file "p7zip-9.20.1-x86_64-1_slack.txz" and converted it to "p7zip-9.20.1-x86_64-1_slack.xzm"
Thanks Jack. We have version 15.14.1 installed. Seems like a huge downgrade but I will check out if it breaks anything else.

as developer of xorriso i have to nitpick that it is not the size of the ISO but the existence of empty files which makes mkisofs output indigestible for 7z.
Thanks for stopping by, and thanks for the detailed info. Not nit picky at all. In fact this helps to understand a lot more.

Hi Francois. I think there will be an rc4 since I have made some quite substantial changes since rc3. At rc4 the base will be frozen and only bugfixes considered.

Thanks to all.

[rchase]

Porteus-v3.2rc3 x86 XFCE does not recognize the Linux installation script as such and opens Mousepad instead of executing it
Thanks. Will check out the mimetypes.

how can I install Porteus to a partition on a hard drive?
The same way as installing on a USB device except you DON'T want to run the Porteus-installer script. This will wipe the boot record and only porteus will boot. If you already have a bootloader in place just tweak the config file to add Porteus.

I am referring to the script to install Porteus' boot code to a partition (i.e. /boot/Porteus-installer-for-Linux.com), not the one included in the installer program to install it to the MBR -- I can't execute the script to install the boot code to a partition. When I try to run it from a working Porteus, it brings up the Application Finder.

[francois]

@brokenman:
Any idea for the time schedule for the release of rc4?

[burdi01]

I install this old file "p7zip-9.20.1-x86_64-1_slack.txz" and converted it to "p7zip-9.20.1-x86_64-1_slack.xzm"
In https://github.com/mate-desktop/engrampa/issues/128 I reported that 7z 15.09 beta and 15.14.1 show the problem, but 7z 9.04 and 9.20 do not.
From https://sourceforge.net/p/p7zip/bugs/180/ I derive that a fix *may* be forthcoming.

as developer of xorriso i have to nitpick that it is not the size of the ISO but the existence of empty files which makes mkisofs output indigestible for 7z.
I made sure / verified this info is mentioned in the two topics as mentioned above.

[scdbackup]

Hi,

for bystanders we should mention that we discussed the issue of mkisofs-versus-7z in
http://www.linuxquestions.org/questions ... ?p=5552474

About https://sourceforge.net/p/p7zip/bugs/180/ :
Somehow i cannot log in by my sourceforge password (it is supposed
to still work with xorriso uploads). So i cannot express my scruples
about Igor Pavlov's idea of using GPT info instead of ISO 9660 info.
In an isohybrid ISO, the ISO 9660 aspect is still the main show.
MBR, GPT, APM are all add-ons with the sole purpose to direct boot
firmware to boot loader start programs. Lies and deceptions are allowed
if only they lead to sucessful booting.

As i stated on linuxquestions, both programs, mkisofs and 7z lean out
of the train window. Both should not. "E pericoloso sporgersi".

7z could simply ignore the block addresses of all files which have a
byte count of 0. At least that's what mkisofs expects and Linux mount does.

Have a nice day

Thomas