QV version 240425 pre-alpha uploaded

[BarryK]

Update devx :

Try the following steps te reproduce it.
- pkg on desktop
- PKGget
- Find: devx / GO / search all repositories
- select devx-240423
- Install

Message : you declined to install this package : devx-240423

then it stops.

It is not a big problem (for me), just reporting it.

Hmmm, strange.
The only different thing I did was select "pet-void" radiobutton, then "utility" radiobutton, then clicked on the devx package, and install worked.

It seems that PKGget has a problem if don't go to the "pet-void" repo where the pkg is.

I have used the search box to find Void packages and that has worked. But then, "void-current" is the default repo.

OK, figured it out. Changes for QV in /usr/local/petget/installpreview.sh caused the breakage.

There have been lots of fixes since the 23rd, better to bring out a new release of QV, rather than just post fixed script here.

[BarryK]

QV 240423 - installed with qv-installer using fatdog64
______________________________
-recorded audio
_______________
-I was able to set up samba server to transfer files with my chromebook
However easyshare app gave an error message when I clicked 'Apply'
testparm.log had strange message but services did launch which is why the share was made with my chromebook

Code: Select all

Load smb config files from GЏzU
Error loading services.

Screenshot-samba.png

I have only done a basic test with samba, which worked.
Booted EasyOS Pyro-series on my old Compaq PC and exported a folder via samba.
In QV was able to mount the folder and transfer files, no error messages.

[ghoen]

Ok. I will wait before I continue trying.

[BarryK]

QV 240425 release:

https://bkhome.org/news/202404/qv-versi ... eased.html

[ghoen]

Ok. I will wait before I continue trying.

Problem solved in QV version 240425.

[don570]

I noticed that older pet packages don't install properly
My baconrecorder didn't show in menu and older wine app didn't install code in /opt

When I made pets in qv they installed perfectly.

For instance here is wine pet...
viewtopic.php?t=11358
________________________________________________________

[nnriyer]

Sir, We need proper installer for qv etc. It should be easy to install without manual intervention

[Caramel]

QV 240425 release:

https://bkhome.org/news/202404/qv-versi ... eased.html

Just installed.
After first creation of a snapshot, the information on desktop has changed, but the number is 3 instead 2 (btrfs subvolume list / confirm 2 subvolumes was created) and the date is a day in advance.
After second snapshot, the number is 4 (increased by 1) and the date has not changed (still a day in advance)

[Caramel]

Return of the problem with Pam and flatpak Anydesk (see viewtopic.php?t=10439 for the problem in EasyVoid)

Pam prevents the launch of the flatpak Anydesk with the error message :

The logged in user differs from the (non-root) user this process runs as

It does not like the "run-as-client" trick

For test, I moved many files installed by the pakages pam, pam-libs and rebooted. Then Anydesk started.

For the deactivation to take effect, a reboot is necessary. So it's difficult to know which files moved are enough to prevent pam

EDIT: the move of the 6 .so files libpam libpamc lipam_misc in /usr/lib is enough to block pam
EDIT2: the move of the 2 .so files libpam in /usr/lib is enough to block pam

EDIT3: Ultimately the move of the symlink libpam.so.0 is sufficient for blocking pam

[BarryK]

QV 240425 release:

https://bkhome.org/news/202404/qv-versi ... eased.html

Just installed.
After first creation of a snapshot, the information on desktop has changed, but the number is 3 instead 2 (btrfs subvolume list / confirm 2 subvolumes was created) and the date is a day in advance.
After second snapshot, the number is 4 (increased by 1) and the date has not changed (still a day in advance)

Yes, at first bootup. snapshot 2 is created, as a backup of pristine conditions.
You can see it in /mnt/${WKG_DEV}/quantumvis/snapshot-record

The date is only yymmdd
Regarding being a day in advance, I attempted to obtain the accurate date in the initrd. This code in 'init' script:

Code: Select all

###set date and time###
#see TZ set early in script.
#20240320 settimeofday() error, see: https://bkhome.org/news/202402/hwclock-fail-in-easyvoid-603.html
# getting this error in initrd. now have static hwclock with old musl
# ...it does not accept -l requires --localtime
CLKflg=1
if [ -e /sys/class/rtc/rtc0 ];then
 #20240424 get timezone...
 if [ -e /tempmnt/${QV}/etc/localtime ];then
  NEWTZ="$(readlink /tempmnt/${QV}/etc/localtime)" #ex: /usr/share/zoneinfo/Etc/GMT-8
  mkdir -p ${NEWTZ%/*}
  cp -a ${NEWTZ} ${NEWTZ%/*}/
  cp -a /tempmnt/${QV}/etc/localtime /etc/
  unset TZ #otherwise it will override /etc/localtime
  export TZ
 fi
 if [ -s /tempmnt/${QV}/etc/clock ];then
. /tempmnt/${QV}/etc/clock #has HWCLOCKTIME=localtime or utc
  case "$HWCLOCKTIME" in
   localtime) hwclock -s --localtime -f /dev/rtc0; CLKflg=$? ;;
   utc)       hwclock -s -u -f /dev/rtc0; CLKflg=$? ;;
  esac
 else #first bootup, assume hw clock is localtime...
  hwclock -s -l -f /dev/rtc0
 fi
fi
if [ $CLKflg -ne 0 ];then
 if [ -s /tempmnt/${QV}/var/local/shutdown_date_saved ];then
  date -s "$(cat /tempmnt/${QV}/var/local/shutdown_date_saved)" > /dev/null
 fi
fi
#rpi does not have a hardware clock, set it to something sane at 1st bootup...
YEAR=$(date +%Y) #ex: 1970
if [ $YEAR -lt 2020 ];then
 #set date same as init file...
 fDATE="$(stat -c %y /init | cut -f 1,2 -d ':')"
 DATE="$(date -s "$fDATE")"
else
 DATE="$(date)"
fi
export DATE #ex: Tue Mar  3 07:09:34 +08 2020

At first bootup, assumes hw clock is local time.
Subsequent bootups, reads /etc/localtime symlink in the @qv folder and copies it, as well as what it points to, into the initrd.
Then, it is hoped, the date will be set correctly.

But maybe the code has a problem, if you are getting a day ahead.

[BarryK]

Return of the problem with Pam and flatpak Anydesk (see viewtopic.php?t=10439 for the problem in EasyVoid)

Pam prevents the launch of the flatpak Anydesk with the error message :

The logged in user differs from the (non-root) user this process runs as

It does not like the "run-as-client" trick

For test, I moved many files installed by the pakages pam, pam-libs and rebooted. Then Anydesk started.

For the deactivation to take effect, a reboot is necessary. So it's difficult to know which files moved are enough to prevent pam

EDIT: the move of the 6 .so files libpam libpamc lipam_misc in /usr/lib is enough to block pam
EDIT2: the move of the 2 .so files libpam in /usr/lib is enough to block pam

EDIT3: Ultimately the move of the symlink libpam.so.0 is sufficient for blocking pam

OK, I'll go back to how it was before. This was the change:

https://github.com/bkauler/woof-quantum ... 752a797033

I will revert it.

[Caramel]

Just installed.
After first creation of a snapshot, the information on desktop has changed, but the number is 3 instead 2 (btrfs subvolume list / confirm 2 subvolumes was created) and the date is a day in advance.

The date is only yymmdd
Regarding being a day in advance, I attempted to obtain the accurate date in the initrd. This code in 'init' script:

Code: Select all

###set date and time###
#see TZ set early in script.
#20240320 settimeofday() error, see: https://bkhome.org/news/202402/hwclock-fail-in-easyvoid-603.html
# getting this error in initrd. now have static hwclock with old musl
# ...it does not accept -l requires --localtime
CLKflg=1
if [ -e /sys/class/rtc/rtc0 ];then
 #20240424 get timezone...
 if [ -e /tempmnt/${QV}/etc/localtime ];then
  NEWTZ="$(readlink /tempmnt/${QV}/etc/localtime)" #ex: /usr/share/zoneinfo/Etc/GMT-8
  mkdir -p ${NEWTZ%/*}
  cp -a ${NEWTZ} ${NEWTZ%/*}/
  cp -a /tempmnt/${QV}/etc/localtime /etc/
  unset TZ #otherwise it will override /etc/localtime
  export TZ
 fi
 if [ -s /tempmnt/${QV}/etc/clock ];then
. /tempmnt/${QV}/etc/clock #has HWCLOCKTIME=localtime or utc
  case "$HWCLOCKTIME" in
   localtime) hwclock -s --localtime -f /dev/rtc0; CLKflg=$? ;;
   utc)       hwclock -s -u -f /dev/rtc0; CLKflg=$? ;;
  esac
 else #first bootup, assume hw clock is localtime...
  hwclock -s -l -f /dev/rtc0
 fi
fi
if [ $CLKflg -ne 0 ];then
 if [ -s /tempmnt/${QV}/var/local/shutdown_date_saved ];then
  date -s "$(cat /tempmnt/${QV}/var/local/shutdown_date_saved)" > /dev/null
 fi
fi
#rpi does not have a hardware clock, set it to something sane at 1st bootup...
YEAR=$(date +%Y) #ex: 1970
if [ $YEAR -lt 2020 ];then
 #set date same as init file...
 fDATE="$(stat -c %y /init | cut -f 1,2 -d ':')"
 DATE="$(date -s "$fDATE")"
else
 DATE="$(date)"
fi
export DATE #ex: Tue Mar  3 07:09:34 +08 2020

At first bootup, assumes hw clock is local time.
Subsequent bootups, reads /etc/localtime symlink in the @qv folder and copies it, as well as what it points to, into the initrd.
Then, it is hoped, the date will be set correctly.

But maybe the code has a problem, if you are getting a day ahead.

I'm having trouble understanding the code.

Previously the variable TZ is initialized by export TZ='XXX-23'
In the code shown here TZ seems not changed.

I do not really understand the lines:

unset TZ #otherwise it will override /etc/localtime
export TZ

[gcav]

Is this working?

At first run, I get prompted for a password but afterwards I see a message that working folders cannot be encrypted and password will be root's passwd.

gc...

[williwaw]

At first bootup, assumes hw clock is local time.
Subsequent bootups, reads /etc/localtime symlink in the @qv folder and copies it, as well as what it points to, into the initrd.
Then, it is hoped, the date will be set correctly.

But maybe the code has a problem, if you are getting a day ahead.

when quicksetup > "hardwareclock set to UTC" box is ticked, I have the day ahead dating, but it is just a note in snapshot-record so not obvious. the time and date in the taskbar is OK

when changing desktop backgrounds the snapshot version message seems to scale different

[TerryH]

Is this working?

At first run, I get prompted for a password but afterwards I see a message that working folders cannot be encrypted and password will be root's passwd.

gc...

Entering a password at that prompt is intended to have 2 purposes, the encryption function doesn't work with btrfs. The other purpose sets the root password, so that function still works.

[BarryK]

I do not really understand the lines:

unset TZ #otherwise it will override /etc/localtime
export TZ

Earlier in the code, TZ was exported.
I thought that if TZ is unset, it would have to be exported again, as unset.

[BarryK]

Sorry, I might be a bit slow to respond to QV bug reports for a few days.
I'm finally giving EasyOS Kirkstone some TLC. A complete recompile with updated packages.

[don570]

I reinstalled qv again in the same partition to check SAMBA

I was able to get a samba server to run but
there is definitely something wrong with Easy share app.

Here is my install method

-install fresh qv
-booted and set samba daemon with first set up
-ran easy share app and clicked 'Apply' button
-warning message that services aren't running
-chromebook doesn't list the server
-I went to /etc and ran

Code: Select all

rc.samba start

Checked in terminal that samba is running
-checked my chromebook that sever is now running properly.

[BarryK]

I reinstalled qv again in the same partition to check SAMBA

I was able to get a samba server to run but
there is definitely something wrong with Easy share app.

Here is my install method

-install fresh qv
-booted and set samba daemon with first set up
-ran easy share app and clicked 'Apply' button
-warning message that services aren't running
-chromebook doesn't list the server
-I went to /etc and ran

Code: Select all

rc.samba start

Checked in terminal that samba is running
-checked my chromebook that sever is now running properly.

Why didn't you start samba from within EasyShare?
That does more things than just run "/etc/init.d/rc.samba start"

[gcav]

Is this working?

At first run, I get prompted for a password but afterwards I see a message that working folders cannot be encrypted and password will be root's passwd.

gc...

Entering a password at that prompt is intended to have 2 purposes, the encryption function doesn't work with btrfs. The other purpose sets the root password, so that function still works.

Aww.. shucks...
I see that BTRFS does not have native encryption, only with LUKS and the sorts..

I will play with having F2FS on QV...

gc

[BarryK]

Is this working?

At first run, I get prompted for a password but afterwards I see a message that working folders cannot be encrypted and password will be root's passwd.

gc...

Entering a password at that prompt is intended to have 2 purposes, the encryption function doesn't work with btrfs. The other purpose sets the root password, so that function still works.

Aww.. shucks...
I see that BTRFS does not have native encryption, only with LUKS and the sorts..

I will play with having F2FS on QV...

gc

The btrfs developers were working on fscrypt, same that ext4 and f2fs have. But the kernel patches caused a crash.
Also, the developers have put it on the back-burner. Hopefully, they will get enthused enough sometime to keep working on it.
I gather, from reading their mail-list, that fscrypt is very complicated to implement in btrfs.

f2fs won't work on QV, as the whole thing is built around the snapshot feature of btrfs. f2fs is a copy-on-write f.s., but snapshots were never implemented.

[don570]

I did fresh install of qv to test samba . Here are my notes...

-a fresh install of QV
qv-240423-amd64.img
-bootup
-Firewall is automatically setup
-In the first setup app I set the samba deamon to always run at bottup
-clicked yes for keyboard changes
-there is message that the firewall is running
-I check tray and I see that ethernet wired connection is active
-I launch EasyShare app and there is message that firewall is starting
(this is third message that a firewall is starting. A lot of firewall messages???)
-I choose Samba option and then click 'Samba setup' button (see image)

Screenshot (1).png (25.36 KiB) Viewed 102 times

-
I see green Samba icon.(see image)

Screenshot(3).png (71.54 KiB) Viewed 102 times

I right click on it to read instructions.
Instructions say that if green then samba is running.
-I assume samba is running and click 'Apply' button
-I get error message that samba isn't running

-So I go to /etc/init.d folder and run

Code: Select all

./rc.samba start

I check with my chromebook that a samba server is available
__________________________________________________

Note that with other versions of puppy linux I have seen
a red samba icon used by EasyShare app.
___________________________________________