Porteus 5.0 RC2 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
Blaze
DEV Team
DEV Team
Posts: 3182
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus 5.0 RC2 bug reports

Post#286 by Blaze » 07 Jan 2021, 15:26

joejac, thanks.
Happy to all in 2021 ;)
joejac wrote:
04 Jan 2021, 18:38
Are there any news on the final release of Porteus 5?
Not before release of Slackware 15
Linux 5.10.11-porteus #1 SMP Thu Jan 28 11:33:44 UTC 2021 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
Rava
Contributor
Contributor
Posts: 2944
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 5.0rc2 + 4.0 i586 XFCe
Location: Forests of Germany

Porteus 5.0 RC2 bug reports

Post#287 by Rava » 08 Jan 2021, 07:54

Blaze wrote:
07 Jan 2021, 15:26
Not before release of Slackware 15
To be even more confusing, check your /var/log/Xorg.0.log :

Code: Select all

guest@porteus:~$ grep "Slackware 15.0" /var/log/Xorg.0.log
[    54.709] Build Operating System: Slackware 15.0 Slackware Linux Project
Red herring much?

And no, you are not running Slackware 15.0 yet:

Code: Select all

guest@porteus:~$ cat /etc/slackware-version
Slackware 14.2+
the + indicates you run current.
Cheers!
Yours Rava

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 2954
Joined: 20 Mar 2012, 03:42
Distribution: 5.0rc1-64bit all-DE+more
Location: australia
Contact:

Porteus 5.0 RC2 bug reports

Post#288 by ncmprhnsbl » 09 Jan 2021, 07:16

Rava wrote:
04 Jan 2021, 03:33
System 5.0rc2 with 003-xfce-4.12-20201108.xzm

/opt/porteus-scripts/xpsinfo aka 'Porteus System Info' ends with this:

Code: Select all

/bin/sh: -c: line 1: syntax error: unexpected end of file
Traceback (most recent call last):
  File "/opt/porteus-scripts/xpsinfo", line 360, in <module>
    class XPSInfo(Gtk.Window):
  File "/opt/porteus-scripts/xpsinfo", line 361, in XPSInfo
    system_info = PSInfo()
  File "/opt/porteus-scripts/xpsinfo", line 20, in __init__
    self.init_infos()
  File "/opt/porteus-scripts/xpsinfo", line 255, in init_infos
    fd.write( f.read() )
  File "/usr/lib64/python3.8/codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 6429: invalid start byte
confirmed
for some strange reason /var/log/messages and /var/log/syslog are now encoded in ISO-8859-1 ( instead UTF-8) ... hard to say if that is the real bug here..
work around for now is: xpsinfo:
line 255: with open('/var/log/messages', encoding="ISO-8859-1" ) as f:
and
line 279: with open('/var/log/syslog', encoding="ISO-8859-1" ) as f:
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

fulalas
DEV Team
DEV Team
Posts: 1686
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Porteus 5.0 RC2 bug reports

Post#289 by fulalas » 11 Jan 2021, 08:11

It works for me if I open from application menu -> system -> porteus system info. It seems it requires to be called by psu.

Maybe we should change xpsinfo to detect when it doesn't have super user privileges.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 2954
Joined: 20 Mar 2012, 03:42
Distribution: 5.0rc1-64bit all-DE+more
Location: australia
Contact:

Porteus 5.0 RC2 bug reports

Post#290 by ncmprhnsbl » 12 Jan 2021, 13:12

fulalas wrote:
11 Jan 2021, 08:11
It works for me if I open from application menu -> system -> porteus system info
hmm.. yeah ..whatever was going on there isn't now, for me... for the moment
@Rava (or anyone else who experiences this) . if xpsinfo fails with that error^
please do: (as root)

Code: Select all

# file -b /var/log/*

this is what mine looks like now (with xpsinfo (unmodified) working)

Code: Select all

# file /var/log/*
/var/log/Xorg.0.log:      JSON data
/var/log/btmp:            empty
/var/log/cron:            ASCII text
/var/log/debug:           ASCII text
/var/log/dmesg:           JSON data
/var/log/faillog:         empty
/var/log/lastlog:         empty
/var/log/maillog:         empty
/var/log/messages:        ASCII text
/var/log/nfsd:            directory
/var/log/packages:        symbolic link to ../lib/pkgtools/packages
/var/log/pkgtools:        directory
/var/log/porteus-livedbg: ASCII text
/var/log/samba:           directory
/var/log/scripts:         symbolic link to ../lib/pkgtools/scripts
/var/log/secure:          ASCII text
/var/log/setup:           symbolic link to ../lib/pkgtools/setup
/var/log/slim.log:        ASCII text
/var/log/syslog:          ASCII text
/var/log/wtmp:            data
fulalas wrote:
11 Jan 2021, 08:11
Maybe we should change xpsinfo to detect when it doesn't have super user privileges.
although that's not the issue here, it's on my todo list (and for various other of the new scripts) ;)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Rava
Contributor
Contributor
Posts: 2944
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 5.0rc2 + 4.0 i586 XFCe
Location: Forests of Germany

Porteus 5.0 RC2 bug reports

Post#291 by Rava » 14 Jan 2021, 02:39

ncmprhnsbl wrote:
12 Jan 2021, 13:12
@Rava (or anyone else who experiences this) . if xpsinfo fails with that error^
please do: (as root)

Code: Select all

# file -b /var/log/*
I think you meant

Code: Select all

# file /var/log/*

here the info

Code: Select all

root@porteus:/# file /var/log/*
/var/log/Xorg.0.log:        JSON data
/var/log/btmp:              empty
/var/log/cron:              ASCII text
/var/log/debug:             ASCII text
/var/log/dmesg:             JSON data
/var/log/faillog:           empty
/var/log/lastlog:           data
/var/log/maillog:           empty
/var/log/messages:          Non-ISO extended-ASCII text
/var/log/messages.1.gz:     gzip compressed data, last modified: Mon Jan 11 18:29:34 2021, from Unix, original size modulo 2^32 773525
/var/log/nfsd:              directory
/var/log/openbox-changelog: ASCII text
/var/log/packages:          symbolic link to ../lib/pkgtools/packages
/var/log/pkgtools:          directory
/var/log/porteus-livedbg:   ASCII text
/var/log/samba:             directory
/var/log/scripts:           symbolic link to ../lib/pkgtools/scripts
/var/log/secure:            ASCII text, with very long lines
/var/log/setup:             symbolic link to ../lib/pkgtools/setup
/var/log/syslog:            ASCII text, with very long lines
/var/log/wtmp:              data
/var/log/messages: Non-ISO extended-ASCII text :bad:
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 2944
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 5.0rc2 + 4.0 i586 XFCe
Location: Forests of Germany

Porteus 5.0 RC2 bug reports

Post#292 by Rava » 21 Jan 2021, 11:49

I formatted a 2 GB SDHC to ext2 and copied the boot/ folder and subfolders from the Porteus-XFCE-v5.0rc2-x86_64.iso to make it able to boot Porteus.

So I executed Porteus-installer-for-Linux:

Code: Select all

Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing Porteus Installer  100%  

                             _.====.._
                           ,:._       ~-_
                               '\        ~-_
                                 \        \.
                               ,/           ~-_
                      -..__..-''   PORTEUS   ~~--..__

==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--

Installing Porteus to /dev/mmcblk0p1
WARNING: Make sure this is the right partition before proceeding.

Type 'ok' to continue or press Ctrl+c to exit.
ok
Flushing filesystem buffers...

Installation failed with error code '2'.
Please ask for help on the Porteus forum: www.porteus.org/forum
and provide the information from /mnt/mmcblk0p1/boot/debug.txt

Exiting now...
cat: /mnt/mmcblk0p1/boot/syslinux/lilo.menu: No such file or directory
Indeed there is only a lilo.conf in boot/syslinux/ - and there is also no lilo in boot/syslinux/ .

Here what debug.txt has, I left out the other devices that are not /dev/mmcblk0p1 , and also all the loop's from the modules:

Code: Select all

device: /dev/mmcblk0
partition: /dev/mmcblk0p1
partition number: p1
partition mount point: /mnt/mmcblk0p1
installation path: /mnt/mmcblk0p1/boot
subfolder: 
filesystem: ext2
bootloader: lilo
error code: 2
system: porteus.example.net 5.4.30-porteus x86_64
mount details: /dev/mmcblk0p1 /mnt/mmcblk0p1 ext2 rw,noatime,nodiratime 0 0
[…]
Disk /dev/mmcblk0: 1.84 GiB, 1977614336 bytes, 3862528 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device         Boot Start     End Sectors  Size Id Type
/dev/mmcblk0p1 *      135 3858623 3858489  1.8G 83 Linux
Cheers!
Yours Rava

beny
Full of knowledge
Full of knowledge
Posts: 970
Joined: 02 Jan 2011, 11:33
Location: italy

Porteus 5.0 RC2 bug reports

Post#293 by beny » 22 Jan 2021, 12:25

mount the device in a /mnt directory cd on boot directory and reload the installer.....maybe work if this is the issue

User avatar
Rava
Contributor
Contributor
Posts: 2944
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 5.0rc2 + 4.0 i586 XFCe
Location: Forests of Germany

Porteus 5.0 RC2 bug reports

Post#294 by Rava » 22 Jan 2021, 12:38

beny wrote:
22 Jan 2021, 12:25
mount the device in a /mnt directory cd on boot directory and reload the installer.....maybe work if this is the issue
The device is in a /mnt/ directory - /mnt/mmcblk0p1 .
I could use a USB card-reader, maybe that makes a difference…

But anyway, when lilo should be the bootloader, then I would need a lilo as well for installation, or not?
Is secretly one of the *c32 files lilo in disguise?

I try the USB card-reader approach and report back.

Added in 13 minutes 24 seconds:
Neato, it worked, now Porteus-installer-for-Linux not tried lilo but extlinux.

Code: Select all

Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing Porteus Installer  100%  

                             _.====.._
                           ,:._       ~-_
                               '\        ~-_
                                 \        \.
                               ,/           ~-_
                      -..__..-''   PORTEUS   ~~--..__

==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--

Installing Porteus to /dev/sdd1
WARNING: Make sure this is the right partition before proceeding.

Type 'ok' to continue or press Ctrl+c to exit.
ok
Flushing filesystem buffers...

Using extlinux bootloader.

Installation finished successfully.
You may reboot your PC now and start using Porteus.
Please check the /boot/docs folder for additional information about
the installation process, Porteus requirements and booting parameters.
In case of making tweaks to the bootloader config,
please edit: /mnt/sdd1/boot/syslinux/porteus.cfg file.

Press Enter to exit.
Cheers!
Yours Rava

beny
Full of knowledge
Full of knowledge
Posts: 970
Joined: 02 Jan 2011, 11:33
Location: italy

Porteus 5.0 RC2 bug reports

Post#295 by beny » 22 Jan 2021, 12:54

good to know... mmc isn't multimedia card? not secure digital

User avatar
Rava
Contributor
Contributor
Posts: 2944
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 5.0rc2 + 4.0 i586 XFCe
Location: Forests of Germany

Porteus 5.0 RC2 bug reports

Post#296 by Rava » 22 Jan 2021, 12:59

beny wrote:
22 Jan 2021, 12:54
good to know... mmc isn't multimedia card? not secure digital
Could be a slot for both, you definitely can insert and mount a secure digital card in it - as seen in what debug.txt above reports.

When I next boot I use the SD card - not via the USB card-reader - the idea was to use the unused SD card slot and keep the USB ports for USB devices - and report here if booting via SD card slot works, or if the SD card can only boot via USB card-reader.
Cheers!
Yours Rava

beny
Full of knowledge
Full of knowledge
Posts: 970
Joined: 02 Jan 2011, 11:33
Location: italy

Porteus 5.0 RC2 bug reports

Post#297 by beny » 22 Jan 2021, 13:07

in my desktop system i can't boot the card via usb3, i have an ugreen device that have a ssd plug and two usb 3 and also a sd card reader and this device boot in all system also in my notebook work,in the past if you have a multireader card device you can't boot from it.

User avatar
Rava
Contributor
Contributor
Posts: 2944
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 5.0rc2 + 4.0 i586 XFCe
Location: Forests of Germany

Porteus 5.0 RC2 bug reports

Post#298 by Rava » 22 Jan 2021, 13:26

beny wrote:
22 Jan 2021, 13:07
if you have a multireader card device you can't boot from it.
I thought my BIOS "choose device to boot from screen" showed me the card reader if one is inserted during boot…



Do not tempt me to boot right now. :D
ImageImage
Cheers!
Yours Rava

nanZor
Shogun
Shogun
Posts: 226
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.0 RC2 LXDE
Location: Los Angeles

Porteus 5.0 RC2 bug reports

Post#299 by nanZor » 16 Mar 2021, 09:15

E2FSCK out of date warning:

Running 5.0rc2 with LXDE. I use the internal mmcblk device formatted with ext to store my changes. Works great, however the system did come up with a hint to use the FSCK bootcode next time to make sure all the filesystems are consistent. But I got this warning:

Code: Select all

MMCBLK0P2 has unsupported feature:   METADATA_CSUM
Get a new version of e2fsck !
So not really a bug, but it appears that the e2fsck as supplied in RC2 doesn't dig my mmcblk device for doing normal fsck's..
Last edited by nanZor on 19 Mar 2021, 08:16, edited 2 times in total.
That's a UNIX book - cool. -Garth

nanZor
Shogun
Shogun
Posts: 226
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.0 RC2 LXDE
Location: Los Angeles

Porteus 5.0 RC2 bug reports

Post#300 by nanZor » 16 Mar 2021, 09:20

Init ID "x1" respawning too fast

Noticed that on occasion, the one of my systems will halt at

Code: Select all

Init ID "x1" respawning too fast.  Disabled for 5 minutes.
After 5 minutes it will just respawn too fast again in an infinite loop.

One fix for that when it happens is to CTRL-D out of it, log in again, and manually startx

And on occasion, when instructed to reboot, the system seems to just halt, and not reboot. Might be a timing issue with one of my cheap machines ...

Not show-stoppers, just something that I've seen once in a blue moon.
That's a UNIX book - cool. -Garth

Post Reply