Porteus-v5.0rc3 x86_64 bug reports
-
- Shogun
- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
Porteus-v5.0rc3 x86_64 bug reports
I use only Blueman gui.
On click, main window opens,
search for Bluetooth devices,
lists
I select my phone
Phone identifies as BlueZ5.59
pair
once connected and paired, files can be shared between phone and PC.
It works for me.
I don.t have any audio bluetooth devices.
On click, main window opens,
search for Bluetooth devices,
lists
I select my phone
Phone identifies as BlueZ5.59
pair
once connected and paired, files can be shared between phone and PC.
It works for me.
I don.t have any audio bluetooth devices.
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit
- Blaze
- DEV Team
- Posts: 3885
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
- Contact:
Porteus-v5.0rc3 x86_64 bug reports
Anybody can check as root command?
Filesystem check does not start.
Bug report from this post Вопросы про porteus (Пост glestwid #83685)
Code: Select all
fsck -A
Filesystem check does not start.
Bug report from this post Вопросы про porteus (Пост glestwid #83685)
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
Porteus-v5.0rc3 x86_64 bug reports
root@porteus:/home/guest# fsck -A
fsck from util-linux 2.37
root@porteus:/home/guest#
fsck from util-linux 2.37
root@porteus:/home/guest#
- ncmprhnsbl
- DEV Team
- Posts: 3941
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Porteus-v5.0rc3 x86_64 bug reports
so.. from man fsck:
ie. specifying a partition, looks like it works properly..
i'm led to believe, that fsck should used only on unmounted partitions or mounted read only partitions...
my guess is that fsck has some problem with our fstab ...because eg.:-A Walk through the /etc/fstab file and try to check all filesystems in one run. This option is typically used from the /etc/rc system initialization file, instead of multiple commands for checking a single filesystem. .. ..
Code: Select all
root@porteus:/home/guest# fsck /dev/sda7
fsck from util-linux 2.37.1
e2fsck 1.46.3 (27-Jul-2021)
/dev/sda7: clean, 11/12804096 files, 851531/51200000 blocks
i'm led to believe, that fsck should used only on unmounted partitions or mounted read only partitions...
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
Porteus-v5.0rc3 x86_64 bug reports
i have rebuild the core when is ready i can confirm if work or not
- Ed_P
- Contributor
- Posts: 8374
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus-v5.0rc3 x86_64 bug reports
It definently is present and works!
I think I see it run occasionally when booting with my changes=EXIT cheatcode and it checks the save.dat file.
Code: Select all
guest@porteus:~$ su
Password:
root@porteus:/home/guest# fsck -A
fsck from util-linux 2.37.1
root@porteus:/home/guest#
root@porteus:/home/guest# fsck
fsck from util-linux 2.37.1
root@porteus:/home/guest# fsck /dev/sda1
fsck from util-linux 2.37.1
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
[123?q]? 3
There is no label in boot sector, but there is volume label 'ESP' stored in root directory
1) Copy volume label from root directory to boot sector
2) Remove volume label from root directory
[12?q]?
Ed
Porteus-v5.0rc3 x86_64 bug reports
Code: Select all
root@porteus:/home/guest# fsck -A
fsck from util-linux 2.37.1
e2fsck 1.46.2 (28-Feb-2021)
/dev/sdc1 is mounted.
e2fsck: Cannot continue, aborting.
we have to change the last number on fstab to 1 but when you unmount the hard disk fsck reset to start so this is a loop
/dev/sde1 /mnt/sde1 ext4 users,noatime,nodiratime,suid,dev,exec,async,comment=x-gvfs-show 0 0
/dev/sdd1 /mnt/sdd1 ext4 users,noatime,nodiratime,suid,dev,exec,async,comment=x-gvfs-show 0 0
/dev/sda1 /mnt/sda1 ext4 users,noatime,nodiratime,suid,dev,exec,async,comment=x-gvfs-show 0 0
/dev/sdf1 /mnt/sdf1 ext4 users,noatime,nodiratime,suid,dev,exec,async,comment=x-gvfs-show 0 0
root@porteus:/home/guest# fsck /dev/sdb1
fsck from util-linux 2.37.1
e2fsck 1.46.2 (28-Feb-2021)
/dev/sdb1: clean, 1579206/19499760 files, 14619819/78142464 blocks
root@porteus:/home/guest#
- Blaze
- DEV Team
- Posts: 3885
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
- Contact:
Porteus-v5.0rc3 x86_64 bug reports
It is obvious.
seems too.
beny, how you got right output from command
Code: Select all
fsck -A
Thanks.
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
Porteus-v5.0rc3 x86_64 bug reports
hi blaze for fsck there are 0 for not to check 1 for control and 2 for all but you can change as root the fstab:
dev/sde1 /mnt/sde1 ext4 users,noatime,nodiratime,suid,dev,exec,async,comment=x-gvfs-show 0 0 (1) or (2) the loop is like a slackbuild modified into the sbo-git directory the change are erased from the script,so fstab change return to 0
dev/sde1 /mnt/sde1 ext4 users,noatime,nodiratime,suid,dev,exec,async,comment=x-gvfs-show 0 0 (1) or (2) the loop is like a slackbuild modified into the sbo-git directory the change are erased from the script,so fstab change return to 0
Porteus-v5.0rc3 x86_64 bug reports
On RC3 kde I'm getting the same issue with save session and context module scripts like folder to module: folder not writeable. Yes it is.
ccccc wrote: ↑19 Jul 2021, 15:35xfce rc3 x64 edition, created with yumi [legacy boot] (i have multiple distros on usb stick), i cannot save current custom settings into module, on rc1 it is working ok without any other hack.
porteus settings center, save your currrent porteus session, save to module
Error messages:
I cannot even select random folder on usb stick or /tmp folder, which are 100% writable!
I am logged as root of course, default option on usb boot for porteus launch mode (ie Graphics mode)
from porteus.cfg
LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL /multiboot/Porteus-XFCE-v5.0rc3-x86_64/boot/syslinux/vmlinuz
INITRD /multiboot/Porteus-XFCE-v5.0rc3-x86_64/boot/syslinux/initrd.xz
APPEND from=/multiboot/Porteus-XFCE-v5.0rc3-x86_64
TEXT HELP
Run Porteus the best way we can.
Try to autoconfigure graphics
card and use the maximum
allowed resolution
ENDTEXT
One more thing, in "choose destination folder" (1st pic), in rc1 it shows correct path (/multiboot/Porteus-XFCE-v5.0rc1-x86_64)
Porteus-v5.0rc3 x86_64 bug reports
I don't have a laptop to test, sorry. Have you tried this? https://unix.stackexchange.com/question ... xbacklight
Porteus-v5.0rc3 x86_64 bug reports
@jroovy, I found a solution: https://slackware.pkgs.org/current/alie ... n.tgz.html
- Ed_P
- Contributor
- Posts: 8374
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus-v5.0rc3 x86_64 bug reports
I use the changes=EXIT cheatcode. My 256MB save.dat file recently, and unexpectedly, became full when I shutdown. 1MB of free space. When I rebooted, with the changes=EXIT cheatcode, I used the Porteus Savefile Manager and expanded the file to 320MB, same name, same location, NTFS partition, I shutdown and rebooted and got this error window.
/tmp/chg_errlog
I checked the size of the file and Nemo shows it as 335.5MB so the expansion worked.
Added in 8 hours 28 minutes 54 seconds:
Update
Added in 12 minutes 14 seconds:
Windows 10 has no problem with the drive.
Code: Select all
Changes are not saved
More information here: /tmp/chg_errlog
/tmp/chg_errlog
Code: Select all
The changes location is not writable. This maybe because the changes path is located on a read-only filesystem.
I checked the size of the file and Nemo shows it as 335.5MB so the expansion worked.
Added in 8 hours 28 minutes 54 seconds:
Update
Code: Select all
guest@porteus:~/Savedat$ mloop /mnt/sda6/porteus5.0/changes/50rc3save.dat
Please enter root's password below
Password:
using /dev/loop11
Please wait while I gather some info ....
NTFS signature is missing.
Failed to mount '/dev/loop12': Invalid argument
The device '/dev/loop12' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
#################################
Your data file has been mounted at:
/mnt/loop
You can unmount it by typing uloop
Here is a list of the files:
guest@porteus:~/Savedat$ ls -l /mnt/loop/
total 0
guest@porteus:~/Savedat$ df -BM --output=size,used,avail,pcent /mnt/loop
1M-blocks Used Avail Use%
2282M 97M 2185M 5%
guest@porteus:~/Savedat$
Windows 10 has no problem with the drive.
Code: Select all
Microsoft Windows [Version 10.0.19043.1165]
(c) Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>chkdsk D:
The type of the file system is NTFS.
Volume label is Data.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
120832 file records processed.
File verification completed.
Phase duration (File record verification): 1.23 seconds.
55 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.31 milliseconds.
Stage 2: Examining file name linkage ...
3192 reparse records processed.
129272 index entries processed.
Index verification completed.
Phase duration (Index verification): 1.54 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 25.85 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 1.03 milliseconds.
3192 reparse records processed.
Phase duration (Reparse point and Object ID verification): 13.63 milliseconds.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 4.33 milliseconds.
4221 data files processed.
Phase duration (Data attribute verification): 4.44 milliseconds.
CHKDSK is verifying Usn Journal...
36230768 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 154.53 milliseconds.
Windows has scanned the file system and found no problems.
No further action is required.
262143996 KB total disk space.
139580848 KB in 59333 files.
17404 KB in 4222 indexes.
0 KB in bad sectors.
231036 KB in use by the system.
65536 KB occupied by the log file.
122314708 KB available on disk.
4096 bytes in each allocation unit.
65535999 total allocation units on disk.
30578677 allocation units available on disk.
Total duration: 2.98 seconds (2985 ms).
C:\WINDOWS\system32>
C:\WINDOWS\system32>dir D:\"porteus5.0"\changes\50*
Volume in drive D is Data
Volume Serial Number is 28E9-74E9
Directory of d:\porteus5.0\changes
08/21/2021 02:26 PM 335,544,320 50rc3save.dat
1 File(s) 335,544,320 bytes
0 Dir(s) 131,808,985,088 bytes free
C:\WINDOWS\system32>
Ed
- babam
- Warlord
- Posts: 528
- Joined: 16 Nov 2016, 10:30
- Distribution: Porteus 5.0rc3 Xfce K6.1.1
- Location: Rainy city
Porteus-v5.0rc3 x86_64 bug reports
@Ed_P,
Code: Select all
# fdisk -l 50rc3save.dat
Last edited by babam on 22 Aug 2021, 15:11, edited 1 time in total.
Sorry, my English is bad.
- Ed_P
- Contributor
- Posts: 8374
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus-v5.0rc3 x86_64 bug reports
Thank you babam.
The X file on top is the original problem file, the bottom one a new one I created that doesn't have any problems at this point.
Code: Select all
root@porteus:/mnt/sda6/porteus5.0/changes# fdisk -l 50rc3saveX.dat
Disk 50rc3saveX.dat: 320 MiB, 335544320 bytes, 655360 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
root@porteus:/mnt/sda6/porteus5.0/changes# fdisk -l 50rc3save.dat
Disk 50rc3save.dat: 512 MiB, 536870912 bytes, 1048576 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
root@porteus:/mnt/sda6/porteus5.0/changes#
Ed