EasyOS Scarthgap-series version 6.5.1

[Caramel]

Same problems. I had to go back to 6.5 with the option 4 at boot.

The first error message was (approximately) :
Making the filesystem usable cp : cannot overwrite non_directory /mnt/.easy_ro/easy_sfs/var/run
ln: failed to create symlink link /var/run file exists

My hypothesis : it's related to the existence of a symlink /run in the session folder at the time of upgrade. (The symlink would come from dolphin when it has mounted partition)

@ Caramel @ BarryK

Dear Barry, dear Caramel. I'm glad that someone reported the same situation. It could be of course related to Dolphin, hence my whole family is having the problem. I was thinking about using option 5, for reverting back to the latest snapshot of the previous version of the system. Does this imply any data and / or settings loss? Or does this simply revert back to the latest saved session of the previous version, retaining all data and settings? Please let me know as soon as possible.

Thank you very much in advance.

(Edit : Please note the number may be different for someone else , see the end of message viewtopic.php?p=137859#p137859)
I don't know for option 5.
If you use option 4 (and if you have updated from 6.5) you will revert back to the snapshot created at the upgrade to 6.5 .
Easy 6.5 was released the 3rd december. The content of /files is not lost

PS : After return to Easy 6.5, I removed the symbolic link /run in the /mnt/wkg/.session, then used Easy Version Control (in the menu, files section) to restaure Easy 6.5.1

[Federico]

I don't know for option 5.
If you use option 4 (and if you have updated from 6.5) you will revert back to the snapshot created at the upgrade to 6.5 .
Easy 6.5 was released the 3rd december. The content of /files is not lost

PS : After return to Easy 6.5, I removed the symbolic link /run in the /mnt/wkg/.session, then used Easy Version Control (in the menu, files section) to restaure Easy 6.5.1

Dear Caramel, I don't question your expertise - and I never did - but option 4 on my system is described as: Zurücksetzen auf ursprünglichen Erststart, which translated means: reset to the original first start. Which sounds pretty scary to me. Maybe the numbering of the options is different due to the locale?
I'm going to list all the options which I can read on screen:

1) Nichts tun, zurück zur Passworteingabe gehen --> Do nothing, go back to password entry
2) Bootup nur zur Kommandozeile, kein X --> Boot only to command prompt, no X
3) Zurück zur letzten gespeicherten Sitzung --> Go back to last saved session
4) Zurücksetzen auf ursprünglichen Erststart --> reset to the original first start
5) Rollback zur vorherigen Version --> Rollback to previous version
6) Dateisystemprüfung der Arbeitspartition --> Filesystem check of the working partition

On my system there is really a lot of customization work. I need a way to keep it. I do never use the system close to its original state. If it has basically already gone lost and there's no way to recover it, I prefer having at least some psicological preparation for that. Maybe we can fix it somehow, without having to do this reset?
If not, unfortunately I don't have time this weekend to redo all my settings from start.

[BarryK]

Updated to v 6.5.1 and I unfortunately have to report serious problems. Video went from a full HD resolution to just 800x600 pixel, no matter how do I set it on xorgwizard, so that the desktop is unusable. Furtherly there is totally no input: no mouse and no keyboard. I can't even do CTRL+ALT+F2 to exit the X server! The only thing I can do is to keep pressed the power button to power off the system abruptedly. At the limine boot screen, I can't solve the issue by choosing the fix broken video option (it does not matter which driver and resolution I choose: it always reverts back automatically to 800x600), but if I press the e key to edit the boot configuration, I can manually type the resolution and set it to 1920x1080; in this case, the video gets fixed but still absolutely no input. If too much time elapses, the screen turns off and I can't get it back on since there is no input. Also, the network applet has a red X on it and there is no audio applet on the system tray.
Since it looks like I've been the only one to report all of this until now, this must also be somehow related to the german locale (or to non-english locales in general).
Please help!

Same problems. I had to go back to 6.5 with the option 4 at boot.

The first error message was (approximately) :
Making the filesystem usable cp : cannot overwrite non_directory /mnt/.easy_ro/easy_sfs/var/run
ln: failed to create symlink link /var/run file exists

My hypothesis : it's related to the existence of a symlink /run in the session folder at the time of upgrade. (The symlink would come from dolphin when it has mounted partition)

I was afraid that fixing the Kodi flatpak might have bad repercussions!

/run is no longer a symlink, and /var/run is now a symlink to /run. This is, apparently, how it is in most distributions, and what flatpak expects. Flatpak is too dumb to work with /run and /var/run both being symlinks to /temp/run

/etc/rc.d/rc.sysinit has this code:

Code: Select all

if [ -d /run ];then #20221026 hack fix.
 if [ ! -h /run ];then
  rm -rf /run
 else
  rm -f /run
 fi
fi
#ln -snf /tmp/run /run #20220510 could have done ln -snf /tmp/var/run /run  20221102 20241211 no.
#20241211 populate...
cp -a /mnt/.easy_ro/easy_sfs/var/run /run

...and I see what is wrong!
/run exists, but is a broken symlink, so the [ -d /run ] test fails, and /run does not get deleted.
OK, I can fix that.

Interesting that updating 6.5 to 6.5.1 worked for me, so I didn't pick up on that problem.

EDIT:
It looks like uncomment line 240 will fix it:

Code: Select all

mkdir /tmp/run  #20241211 remove. 20241214 keep.

If you have updated to 6.5.1, rollback to 6.5. NO, see my next post.
I will release 6.5.1.1 very soon.

[Caramel]

I don't know for option 5.
If you use option 4 (and if you have updated from 6.5) you will revert back to the snapshot created at the upgrade to 6.5 .
Easy 6.5 was released the 3rd december. The content of /files is not lost

PS : After return to Easy 6.5, I removed the symbolic link /run in the /mnt/wkg/.session, then used Easy Version Control (in the menu, files section) to restaure Easy 6.5.1

Dear Caramel, I don't question your expertise - and I never did - but option 4 on my system is described as: Zurücksetzen auf ursprünglichen Erststart, which translated means: reset to the original first start. Which sounds pretty scary to me. Maybe the numbering of the options is different due to the locale?
I'm going to list all the options which I can read on screen:

1) Nichts tun, zurück zur Passworteingabe gehen --> Do nothing, go back to password entry
2) Bootup nur zur Kommandozeile, kein X --> Boot only to command prompt, no X
3) Zurück zur letzten gespeicherten Sitzung --> Go back to last saved session
4) Zurücksetzen auf ursprünglichen Erststart --> reset to the original first start
5) Rollback zur vorherigen Version --> Rollback to previous version
6) Dateisystemprüfung der Arbeitspartition --> Filesystem check of the working partition

On my system there is really a lot of customization work. I need a way to keep it. I do never use the system close to its original state. If it has basically already gone lost and there's no way to recover it, I prefer having at least some psicological preparation for that. Maybe we can fix it somehow, without having to do this reset?
If not, unfortunately I don't have time this weekend to redo all my settings from start.

This is the code in init (in initrd) :

Code: Select all

menu_func() {
 CNTm=1
 if [ "$1" != "nopw" ];then #20220626
  echo "QUIT ${CNTm} ${S020:-Do nothing, go back to enter password}" > /menulist
  CNTm=$(($CNTm+1))
 fi
 if [ "$LOCKkeep" == "1" ];then
  echo "LOCKREM ${CNTm} ${S021:-Remove lockdown, restore normal bootup}" >> /menulist
  CNTm=$(($CNTm+1))
 fi
 echo "NOX ${CNTm} ${S022:-Bootup to commandline only, no X}" >> /menulist
 CNTm=$(($CNTm+1))
 echo "RBSAVED ${CNTm} ${S023:-Rollback to last saved session}" >> /menulist
 CNTm=$(($CNTm+1))
 echo "RBPRISTINE ${CNTm} ${S024:-Rollback to pristine first-boot}" >> /menulist
 CNTm=$(($CNTm+1))
 echo "RBPREVVER ${CNTm} ${S451:-Rollback to previous version}" >> /menulist
 CNTm=$(($CNTm+1))
 echo "FSCHECK ${CNTm} ${S025:-Filesystem check of working-partition}" >> /menulist
 CNTm=$(($CNTm+1))

The option to roolback to previous version is the penultimate like in german menu as you said. (Edit 5th changed by penultimate)

In my menu (in french) there is only 5 options. I need to understand why.

EDIT: In fact there is 7 options but the first two are not always displayed.
The menu is not the same for everyone and especially the numbers do not correspond to the same options for everyone.

[BarryK]

A further note about the broken update 6.5 to 6.5.1.

If it has broken your update, boot up another distro, and go to /mnt/${WKG_DEV}/${WKG_DIR}.session of the afflicted EasyOS, and delete /run and /var/run

Then bootup and it should be fixed, as long as your attempts to fix it earlier have not introduced a new problem.

[Federico]

A further note about the above problem.

If it has broken your update, boot up another distro, and go to /mnt/${WKG_DEV}/${WKG_DIR}.session of the afflicted EasyOS, and delete /run and /var/run

Then bootup and it should be fixed, as long as your attempts to fix it earlier have not introduced a new problem.

@BarryK

Dear Barry, I will try this immediately. I'm glad to have waited for your answer and not having already made the reset.
I'll report back in short.

Thans so much!

[Federico]

A further note about the broken update 6.5 to 6.5.1.

If it has broken your update, boot up another distro, and go to /mnt/${WKG_DEV}/${WKG_DIR}.session of the afflicted EasyOS, and delete /run and /var/run

Then bootup and it should be fixed, as long as your attempts to fix it earlier have not introduced a new problem.

Dear Barry, it is fixed! God bless you!!!!

Easy Version Control shows version 6.5.1.

[Federico]

So, now using the recovered system. I would still like to clearly understand if this failure was solely related to the presence of the KDE apps or not. Or if the KDE apps have nothing to do with what happened at all. In this latter case, why didn't anyone else report a similar situation?