Linux Lite 7.0 RC1 Released

[Şerban S.]

Yeah, Lite Tweaks is a weird one, hard to debug. Staring from a terminal gives no clues.
Thank you Șerban

Installed on ASUS X200MA = OK.

Takes long (some 50 minutes), but when running, it definitely runs faster than LL 6.4 / 6.6.
I found that accidentally. When I migrate my /home, this keeps my Chrome open-tabs list.
So when I opened Chrome, I had about 20 documents opened. On a machine like this, this is just insane! Yet, it worked!
The RAM load, said I still had some 300 MB of RAM free, out of 1,8 GB. I was running also DoubleCommander, gnome-system-monitor, Pluma. I guess that was all. Maybe the Terminal too.
SWAP use, was some 350 MB out of 4096 MB.

The Lite Tweaks thing:

I scavenged a little through my machine.
What I found is the source of the error

Code:

/usr/bin/lite-tweaks-super: line 1089: ((: PERCENTAGE = 100 \* 2 / 1 : syntax error: invalid arithmetic operator (error token is "\* 2 / 1 ")

I opened up the "lite-tweaks-super", which is a shell script.
Unfortunately, my programming skills are way below understanding the full code, or even parts of it. Yet...

Can you explain how this works?

Code:

while read  line
  do
    $line     # Execute functions one by one
    if [ $? = 1 ]; then
      zenity --info --title=" $_LT" --text="Error:\n${line}" 2>/dev/null
    fi
  let i++
  (( PERCENTAGE = 100 \* ${i} / ${TOTAL_LINES} ))
    echo "$PERCENTAGE"
    if [ "$PERCENTAGE" == "100" ]; then
      echo "#Done"
      sleep 1
    fi
done| zenity --progress --width="320" --window-icon="$_RUN_ICON" --pulsate --no-cancel --title="  $_LT" --auto-kill --auto-close 2>/dev/null

Namely:

Code:

  (( PERCENTAGE = 100 \* ${i} / ${TOTAL_LINES} ))

(( PERCENTAGE = 100 \* ${i} / ${TOTAL_LINES} ))

The snippet is supposed to return the value to increase the ProgressBar with PERCENTAGE.
I have a hard time understanding the RED character in the line:
What exactly does the integer division (\) with the *?
Wasn't this supposed to be... ?

Code:

  (( PERCENTAGE = 100 \ ${i} / ${TOTAL_LINES} ))

Just asking... Anyway, as I said, my programming skills are at a very low level.

Running Lite Tweaks

Bad luck!

This is what I got:

Code:

sudo lite-tweaks
ls: cannot access '/root/.local/share/Trash/files/': No such file or directory

---
Checked: "Log Archives", "Package Cache".
Click Begin: Crush.


What exactly means [ '/root/.local/share/Trash/files/': No such file or directory] ?
I wanted to check the availability of the /root/.local/share/.
I could access it.
"Trash" is missing, indeed, but the process is marked as Root so:
I could create the "Trash". So, what is the problem?
As I see it, chaining a large number of scripts, requires each time reissuing sudo whatever-script, because when exiting, previous-script releases the privileged process and another process is started, with the current-user ($USER I guess) privileges. While this works at install time, because $USER = $SUPER, at session level, the $USER is different than $SUPER. So it is the $HOME, for this matter.

Now, if I understood it right, then the sequence is (should be) this:

Code:

BeginButton_OnClick
ask-for-$SUPER-password

On the other hand, if the first line of code is:

Code:

BeginButton_OnClick

mkdir /root/.local/share/Trash/files/
ask-for-$SUPER-password

then the result is:

Code:

mkdir /root/.local/share/Trash/files/
mkdir: cannot create directory ‘/root/.local/share/Trash/files/’: Permission denied

This might trigger an ErrorMSG number that exits the BeginButton_OnClick code, and the whole procedure lite-tweaks.

Here it is the test result:

Code:

sudo mkdir /root/.local/share/Trash/files/
[sudo] password for serban:
serban ~

The dir is obviously empty, but it's there!

What is really weird is this:

Code:

tmp/ltlogs.log: Permission denied

How come that?
I could create and save the file as $USER (serban, in my case).
As I understand, any process derived from the $USER, has the same rights as the $USER.
So, is there any other $USER than $USER = $SUPER = serban?
And if so, how is it possible?
If this is still possible, I see only one solution: some browser-side script hijacked into the system.
Or at least, created an open door to take some control of parts of the system.
If so, I'm already out. That's way beyond my knowledge and understanding.
I use encryption for my connection, but my level of skills in this branch, well, it's symbolic, to say it lightly...