Porteus-v5.0x86_64_bugs 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
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#106 by Rava » 22 Aug 2022, 02:34

roadie wrote:
22 Aug 2022, 02:20
I don't use a changes module either, but I built one
I see, and now you want to expand on it and either manually change some settings or add some new ones that were not present when you first made it.
roadie wrote:
22 Aug 2022, 02:20
with the steps that I posted and all settings were there after rebooting in Always Fresh.
Mind pointing me to where you posted it?
Cheers!
Yours Rava

roadie
Full of knowledge
Full of knowledge
Posts: 400
Joined: 02 Jan 2011, 18:41
Distribution: Porteus 5.0-RC1
Location: In a hayfield

Porteus-v5.0x86_64_bugs reports

Post#107 by roadie » 22 Aug 2022, 04:51

Rava wrote:
22 Aug 2022, 02:34
roadie wrote:
22 Aug 2022, 02:20
I don't use a changes module either, but I built one
I see, and now you want to expand on it and either manually change some settings or add some new ones that were not present when you first made it.

roadie wrote:
22 Aug 2022, 02:20
with the steps that I posted and all settings were there after rebooting in Always Fresh.
Mind pointing me to where you posted it?
No, I built the module to see why xzm2dir wasn't working for kulle and did it using the steps in post #102

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#108 by Rava » 22 Aug 2022, 08:13

roadie wrote:
22 Aug 2022, 04:51
No, I built the module to see why xzm2dir wasn't working for kulle and did it using the steps in post #102
This is post #102… I see no steps :shock: please explain.
kultex wrote:
21 Aug 2022, 16:51
I use my old stick (Sandisk ultra fit 64 GB USB 3.0) since 2016 with ext4 and no issues - before a slim Lexar JumpDrive USB 2.0 and etx4 for 10 years and no issues and now the new Sandisk ultra fit USB 3.2 will hopfully last the same time....... But I will follow your recommandation.......

And maybe it is my stick with USB 3.2, that has this bootproblems - as soon as everything works on the new stick, I will format the old one and try if this problem still exists....
Cheers!
Yours Rava

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus-v5.0x86_64_bugs reports

Post#109 by Ed_P » 22 Aug 2022, 20:59

Unable to write to the Dell's harddrive's NTFS partitions.

Code: Select all

~#  uname -a
Linux porteus.example.net 5.18.8-porteus #1 SMP PREEMPT_DYNAMIC Sat Jul 2 10:05:31 MSK 2022 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux

~#  cat /etc/porteus/*
001-core.xzm:20220723
002-xorg.xzm:20220723
002-xtra.xzm:20220630
003-cinnamon.xzm:20220511
initrd.xz:20220804

~#  ls -l /mnt/live/memory/images
000-kernel.xzm : Jul 2 03:32
001-core.xzm : Jul 23 05:21
002-xorg.xzm : Jul 23 05:24
002-xtra.xzm : Jun 30 03:13
003-cinnamon.xzm : May 11 08:46
011-slapt-get-0.11.6-x86_64-2gv.xzm : Aug 20 07:25
07-printing-x86_64-2022-08-06.xzm : Aug 6 07:54
Dellsound.xzm : May 14 00:20
Dellwifi2.xzm : Jul 30 00:31
firefox-94.0.2-x86_64-en-US.xzm : Nov 24 2021
mychanges.xzm : Aug 21 18:23

~#  cat /proc/cmdline
quiet BOOT_IMAGE=/boot/syslinux/vmlinuz extramod=UUID:C23A-6012/Modules noload=save.dat initrd=/boot/syslinux/initrd.xz

Boot Drv: sda1
Added in 59 minutes 28 seconds:
:%) I was able to access the drive yesterday and update files on it. :hmmm: I've turned the notebook off and rebooted, the problem continues. Guest Properties for the drive show Permissions for guest and root as Create and delete files for Folder Access and blank for File Access.
Ed

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

Porteus-v5.0x86_64_bugs reports

Post#110 by beny » 22 Aug 2022, 22:12

hi Ed_P from the kernel docs:ntfs3
- "No access rules" mount option sets access rights for files/folders to
777 and owner/group to root. This mount option absorbs all other
permissions.

- Permissions change for files/folders will be reported as successful,
but they will remain 777.

- Owner/group change will be reported as successful, but they will stay
as root.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus-v5.0x86_64_bugs reports

Post#111 by Ed_P » 23 Aug 2022, 05:56

Re-downloaded the Porteus-CINNAMON-v5.0-x86_64.iso and booted it rather than the updated 20220723 files ISO and now the drive is update-able again. :crazy: :%)

Added in 18 minutes :
And now rebooting to the 20220723 updated ISO again the drive is still update-able. :Yahoo!:
But why? :crazy: :%) :unknown: :fool:
Ed

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#112 by Rava » 23 Aug 2022, 07:11

Ed_P wrote:
23 Aug 2022, 06:14
Added in 18 minutes :
And now rebooting to the 20220723 updated ISO again the drive is still update-able. :Yahoo!:
But why? :crazy: :%) :unknown: :fool:
That's the mystery of PCs (and smartphones and tablets), at times they behave in seemingly irrational ways.

Maybe some program you used prior the 1st time changed some system settings, or maybe it was more than one program in the "wrong" order executed to cause it. :shrug:
________________________________________________

Sytem Porteus 5.0 x86_64 XFCE - albeit 4.12 via xfce-4.12-20220218

I have quite some mime typed defined:

Code: Select all

guest@porteus:~/.config$ wc mimeapps.list
  86   87 5953 mimeapps.list
Still, less than 85 since wc also counts the empty lines and the "chapter title lines".

Still, when I open the mime type editor from XFCE via Settings/MIME Type Editor, its list is completely empty.

Why is that? Is there some trick needed first for the MIME Type Editor to learn about the already existing MIME types?
Cheers!
Yours Rava

kultex
Black ninja
Black ninja
Posts: 71
Joined: 30 Dec 2015, 12:11
Distribution: Porteus 4.0 XFCE
Location: Austria

Porteus-v5.0x86_64_bugs reports

Post#113 by kultex » 23 Aug 2022, 10:59

first @Rava
The Sandisk Ultra fit USB3.1 - https://documents.westerndigital.com/co ... sb-3-1.pdf - does not boot from some older laptops (e.g. Acer R3 131T / I bought it 2016). As soon as I have time, I will check, if a bios update will help.....

2 questions - this are no bugs

1) usm is no more on 5.0 - so just checking https://packages.salixos.org/#! - are there some others?

2) the "Create Live USB" utility also disappeared? will it come back?

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#114 by Rava » 23 Aug 2022, 11:52

kultex wrote:
23 Aug 2022, 10:59
The Sandisk Ultra fit USB3.1 - https://documents.westerndigital.com/co ... sb-3-1.pdf - does not boot from some older laptops (e.g. Acer R3 131T / I bought it 2016). As soon as I have time, I will check, if a bios update will help.....
Have you tried looking in other forums?

Also, when it comes to hardware issues, try Knoppix - the Cd version should suffice. Knoppix is among the live systems known for the best hardware compatibility.
Dr. Ing. Knopper created Knoppix so that he can test malfunctioning hardware of his customers, after all.
Cheers!
Yours Rava

donald
Full of knowledge
Full of knowledge
Posts: 2063
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Porteus-v5.0x86_64_bugs reports

Post#115 by donald » 24 Aug 2022, 03:01

Rava wrote:
23 Aug 2022, 07:11
Still, when I open the mime type editor from XFCE via Settings/MIME Type Editor, its list is completely empty.
/usr/share/mime is almost empty...
so I copied over the files we had in 3.2.2 (as a proof of concept) and here it is:
Image
I think you will find out how to add your own -- hint: < enter search engine here> :)

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#116 by Rava » 24 Aug 2022, 04:34

I see, the issue was my user's mime file vs the global mime file in etc...
So, copy mine from ~./config/ into /usr/share/mime/
donald wrote:
24 Aug 2022, 03:01
/usr/share/mime is almost empty...
so I copied over the files we had in 3.2.2
will try and report later.
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#117 by Rava » 25 Aug 2022, 23:51

^
Not tested so far.
____________________________________________________

Sadly, trying to put my system into suspend it utterly crashed once again.

System Porteus 5.0x86-64, XFCE, kernel 5.4.30 - needed cause it is the newest kernel I managed to compile 010-nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm for.

When that happens, REISUB is not helping, the system state is in some kind of undefined limbo.
What I see is: longer time nothing happens - the screen turns black but by the grey it displays the monitor is still switched on trying to display just black, then a text appears in a split second - too quick to read - and then the monitor switches off, but the PC still runs. And runs, and keeps running in limbo.

Since REISUB would not work, I had to do a hard reset (via pressing the ON button > 10 seconds) to switch the PC off.

After that all internal ext? partitions had to be checked, and I had to umount the extHD8_4 ext3 partition (mounted via /dev/sdb4) manually and check it manually, but this time major damage was done to the file system. fsck told me it's not a valid ext2/3/4 system:

Code: Select all

root@porteus:~# e2fsck -b 8193 /dev/sdb4
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb4

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

/dev/sdb4 contains a ext3 file system labelled 'extHD8_4'
        last mounted on /mnt/sdb4 on Fri Aug 26 02:50:02 2022
Why does it display "ext3 file system labelled 'extHD8_4'" but cannot fsck it?

Code: Select all

root@porteus:~# e2fsck -b 32768 /dev/sdb4
e2fsck 1.46.5 (30-Dec-2021)
extHD8_4 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
[...]
Fix<y>? yes
Free blocks count wrong for group #1 (9813, counted=9942).
Fix<y>? yes
Free blocks count wrong for group #2 (11048, counted=11128).
Fix<y>? yes
Free blocks count wrong for group #3 (9793, counted=7721).
Fix<y>? yes
Free blocks count wrong for group #4 (8748, counted=6420).
Fix<y>? yes
Free blocks count wrong for group #5 (8022, counted=7948).
Fix<y>? yes
Free blocks count wrong for group #6 (6676, counted=7270).
Fix<y>? yes
Free blocks count wrong for group #7 (2181, counted=5986).
Fix<y>? yes
Free blocks count wrong for group #8 (6013, counted=12352).
Fix<y>? yes
Free blocks count wrong for group #9 (8722, counted=9654).
Fix<y>? yes
Free blocks count wrong for group #14 (12802, counted=8501).
Fix<y>? yes
Free blocks count wrong for group #15 (21547, counted=9004).
Fix<y>? yes
Free blocks count wrong for group #16 (8692, counted=7908).
Fix<y>?
[...]
Free inodes count wrong for group #3427 (8192, counted=6030).
Fix<y>? yes
Directories count wrong for group #3427 (0, counted=195).
Fix<y>? yes
Free inodes count wrong for group #3428 (8192, counted=6031).
Fix<y>? yes
Directories count wrong for group #3428 (0, counted=76).
Fix<y>? yes
Free inodes count wrong for group #3429 (8192, counted=5948).
Fix<y>? yes
Directories count wrong for group #3429 (0, counted=13).
Fix<y>? yes
[...]
Free inodes count wrong for group #3668 (8192, counted=7182).
Fix<y>? yes
Directories count wrong for group #3668 (0, counted=210).
Fix<y>? yes
Free inodes count wrong for group #3683 (7635, counted=7644).
Fix<y>? yes
Directories count wrong for group #3683 (213, counted=209).
Fix<y>? yes
Free inodes count wrong for group #3692 (8056, counted=8045).
Fix<y>? yes
Free inodes count wrong (30134300, counted=30138671).
Fix<y>? yes
extHD8_4: ***** FILE SYSTEM WAS MODIFIED *****
extHD8_4: 409297/30547968 files (56.4% non-contiguous), 72631851/122168916 blocks
Hopefully no data loss occurred. :(

Code: Select all

root@porteus:~# e2fsck /dev/sdb4
e2fsck 1.46.5 (30-Dec-2021)
extHD8_4: clean, 409297/30547968 files, 72631851/122168916 blocks
root@porteus:~# mount /dev/sdb4
root@porteus:~# ls /mnt/sdb4
Porteus_modules  backup-rm.sh            boot               sound
backup           backup-webm.sh          extHD8_4           tmp
backup-avi.sh    backup.sh               extHD8_4.fsck.txt  video
backup-mp3.sh    backup.viewnior.weiter  intHDD1_2.rebuild  welt
backup-mp4.sh    backup2                 kamera
backup-mpg.sh    bin                     lost+found
Root filesystem on extHD8_3 looks okay.

The reason seems to be the lack of usable memory.
This PC "only" has 4GB of RAM, and via SWAP I have this added:

Code: Select all

root@porteus:/Lsfind# type sx
sx is a function
sx () 
{ 
    echo $(date +%d.%m.%Y\ %H:%M:%S) ____________________________________________________________;
    { 
        read firstLine;
        echo "$firstLine";
        while read f t s u p; do
            let "s2 = $s / 1024";
            let "u2 = $u / 1024";
            printf '%-40s%-16s%-8s%-8s%-8s\n' $f $t $s2 $u2 $p;
        done
    } < /proc/swaps
}
root@porteus:/Lsfind# sx
26.08.2022 01:28:32 ____________________________________________________________
Filename				Type		Size	Used	Priority
/dev/sda6               partition   4607    0       -2
/dev/zram0              partition   774     0       100
Is there a way the system warning me when swap via partition and zram0 has too much use that all that not fits into the physical RAM, ow whatever reason there is for the PC to crash when SWAP is too much in use instead of utterly crashing and risking data / partition corruption coming with each such crash?

Also, even when Port crashes, why is it so utterly destructive that not even REISUB works?
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#118 by Rava » 26 Aug 2022, 03:41

It crashed again, this time I activated my /var/log/messages logging tia tee…

This time REISUB did work, but still all but the boot partition have been unclean:
Image

But at least extHD8 did not suffer again:

Code: Select all

guest@porteus:~$ su -
Password: 
root@porteus:~# mypasswd
mypasswd V0.1
root@porteus:~# umount /dev/sdb4
root@porteus:~# fsck /dev/sdb4
fsck from util-linux 2.37.4
e2fsck 1.46.5 (30-Dec-2021)
Superblock last mount time is in the future.
	(by less than a day, probably due to the hardware clock being incorrectly set)
extHD8_4: clean, 409297/30547968 files, 72631851/122168916 blocks
root@porteus:~# mount /dev/sdb4
Here the last lines from /var/log/messages

Code: Select all

Aug 26 04:47:30 porteus NetworkManager[1567]: <info>  [1661482050.8776] device (eth0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Aug 26 04:47:30 porteus NetworkManager[1567]: <info>  [1661482050.9152] manager: NetworkManager state is now ASLEEP
Aug 26 04:47:30 porteus elogind-daemon[1179]: Suspending system...
Aug 26 04:47:30 porteus kernel: PM: suspend entry (deep)
Aug 26 04:47:30 porteus kernel: Filesystems sync: 0.035 seconds
Aug 26 04:47:51 porteus kernel: Freezing user space processes ... 
Aug 26 04:47:51 porteus kernel: tee             D    0  2649   2643 0x00004004
Aug 26 04:47:51 porteus kernel: OOM killer enabled.
Aug 26 04:47:51 porteus kernel: Restarting tasks ... done.
Aug 26 04:47:51 porteus kernel: video LNXVIDEO:01: Restoring backlight state
Aug 26 04:47:51 porteus kernel: PM: suspend exit
Aug 26 04:47:51 porteus kernel: PM: suspend entry (s2idle)
Aug 26 04:47:51 porteus acpid: client 1873[0:100] has disconnected
Aug 26 04:47:51 porteus last message buffered 1 times
Aug 26 04:47:51 porteus acpid: client connected from 1873[0:100]
Aug 26 04:47:51 porteus acpid: 1 client rule loaded
Aug 26 04:47:51 porteus kernel: Filesystems sync: 0.345 seconds
Aug 26 04:47:52 porteus acpid: client connected from 1873[0:100]
Aug 26 04:47:52 porteus acpid: 1 client rule loaded
I presume "OOM killer enabled." is when REISUB got executed.
The "tee D 0 2649 2643 0x00004004" must be from my /var/log/messages logging it via tee
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#119 by Rava » 26 Aug 2022, 18:01

About the crashes in post #118 Porteus-v5.0x86_64_bugs reports (Post by Rava #89352) - and
#119 Porteus-v5.0x86_64_bugs reports (Post by Rava #89357)

Most probably this is due to the florence virtual keyboard. When I deactivated the 3 modules I had no suspend issues.

deactivating florence while running XFCE even gave an kernel error in /var/log/messages . :)
Cheers!
Yours Rava

kultex
Black ninja
Black ninja
Posts: 71
Joined: 30 Dec 2015, 12:11
Distribution: Porteus 4.0 XFCE
Location: Austria

Porteus-v5.0x86_64_bugs reports

Post#120 by kultex » 28 Aug 2022, 20:00

I have troubles to set the correct time - I can set the time in the Porteus Settings Center - to the correct time - this works, but its gon after reboot always 2 h late

Whatever I try - cheatcode, xfce plugin, Porteus settings Center - nothing is working, also ntpdate does not change the time???????

Post Reply