TazPuppy 5.0 rc2

[s243a]

@greengeek the best solution was to login as root

Or you can righclick on the folder in pcmanfm and select "open as root".

[mistfire]

hello

For that past several weeks. I attempted to release TazPuppy however there is a big hindrance why I cant release another version and I need some help here to fix the following issue. These issue can be easily recreated on last tazpuppy release and only applicable to common user account not on root account

1. sudo was seems to be broken. If you put a wrong root password when sudo program. It still continue to run program in sudo instead of exit and return error message

2. If you install gksu and invoke command on sudo -A it shows that the requesting program was "Password:" instead of the actual command that requires root permission. And it does not work even if you enter a correct password

3. all programs require sudo password except shutdown, reboot, poweroff, pup_event_frontend_d and some puppy core programs.

I hope that someone here can help me to fix these issue on TazPuppy.

[mistfire]

TazPuppy Beta 31 released:

* Built from recent slitaz release
* Fixed all file and folder permissions
* Fixed sudo problems
* Fixed free memory tray applet
* Ability to handle AppImage, Snap (experimental, requires snap installed), and Flatpak (experimental, requires flatpak installed)

Download: https://drive.google.com/open?id=11EmYE ... Hv_C4AaYcE
MD5 Checksum: c482d39b96f3100282d3393708c0cef4

Build kit: https://drive.google.com/open?id=1YKVI9 ... V5V6g7dr35

[TiredPup]

I have used Slitaz in the past. I have also used previous versions of Tazpup successfully. However I am having a great deal of trouble with this latest version of Tazpup. I am not able to do anything that requires root access. This includes setting up the network or running an app like gparted. Subox will appear and request a root password. I enter root, it returns an error message for wrong password.

I logged out of user Tux and logged into user Root. Root password was accepted for this login. I was able to configure wifi and do an install of Tazpup to my Eeepc 901 this way. I found that Midori browser will run when logged in as Root but will refuse to save downloads throwing up an error message complaining about permission issues.

I find these issues repeated on the Eeepc 901 after booting from hdd install as well. So I booted from usb on my desktop. Got the same thing.

I tried running from console to overcome permission issues as user Tux but no luck.

What am I not understanding?

[s243a]

I have used Slitaz in the past. I have also used previous versions of Tazpup successfully. However I am having a great deal of trouble with this latest version of Tazpup. I am not able to do anything that requires root access. This includes setting up the network or running an app like gparted. Subox will appear and request a root password. I enter root, it returns an error message for wrong password.

I logged out of user Tux and logged into user Root. Root password was accepted for this login. I was able to configure wifi and do an install of Tazpup to my Eeepc 901 this way. I found that Midori browser will run when logged in as Root but will refuse to save downloads throwing up an error message complaining about permission issues.

I find these issues repeated on the Eeepc 901 after booting from hdd install as well. So I booted from usb on my desktop. Got the same thing.

I tried running from console to overcome permission issues as user Tux but no luck.

What am I not understanding?

Perhaps sudo is still broken? Try sudo from the command line or try right clicking a folder and selecting "open as root".

[TiredPup]

Try sudo from the command line

"sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set"

"su: setresgid: Operation not permitted" This was in response to running subox and entering root as password.

try right clicking a folder and selecting "open as root"

Right clicking a folder and selecting "open as root" from the context menu yielded no response.

Perhaps sudo is still broken?

It seems to be the case.

[s243a]

.

Perhaps sudo is still broken?

It seems to be the case.

Until it is fixed are you able to use the "su" command instead?

[TiredPup]

Until it is fixed are you able to use the "su" command instead?

su command yields identical results to subox.

[s243a]

Until it is fixed are you able to use the "su" command instead?

su command yields identical results to subox.

Wild shot in the dark. Try the command:

Code: Select all

busybox su root

on another note. Check the premissions on busybox. I think that it might rquire the suid set. I'm going to have to download the latest iso and try to troubleshoot.

[darry19662018]

Running as root like in other Puppies found a problem with Timezone Configuration - nothing happens so used the script slitaz dialog configs as this worked without incident and changed to NZ timezone.

[mistfire]

Hello

Sorry for late reply. I figured out the problem. It was a file permission issue.

To fix this problem:

1. login as root
2. type the following command on terminal and press enter

Code: Select all

chmod 4755 /usr/bin/sudo
chmod 4755 /bin/busybox
chmod 4755 /bin/su

I will fix also this bug on TazPuppy builder

[TiredPup]

mistfire wrote:

Hello

Sorry for late reply. I figured out the problem. It was a file permission issue.

To fix this problem:

1. login as root
2. type the following command on terminal and press enter

Code:

chmod 4755 /usr/bin/sudo
chmod 4755 /bin/busybox
chmod 4755 /bin/su


I will fix also this bug on TazPuppy builder

I just implemented these steps as described. It has not changed anything. I am still receiving all of the same error messages as previously described.

EDIT:

Success!

I had been doing all of this without a savefile because user Tux did not have sudo permissions to initiate shutdown and reboot. So when I implemented your instructions I skipped a step in the process.

So I repeated the process, then logged out of root, into Tux and shutdown successfully making a savefile in the process. And of course, on reboot I was able to log in as Tux and all is well with the permissions issue.

[mistfire]

@TiredPup what command did you tried to execute that triggers that error? Did logged out on TazPuppy and logged in to root account before you do that procedure?

[TiredPup]

@mistfire

We crossed posts. I updated my last post as you were reading it apparently.

[mistfire]

TazPuppy Beta 32 released

Changes:
* Broken busybox, su, and sudo in user account due to file permissions was fixed

Download: https://drive.google.com/open?id=1I70c0 ... 75MNPzixwv
MD5 Checksum: 82ffc3a48380329947e9bfb95ded8ec5

Build kit: https://drive.google.com/open?id=1rnS68 ... _DC1twijgi

[zagreb999]

i installed latest iso

can not lunch xfce4
can not connect to android phone
mobile hotspot...
can not connect to usb dongle wifi...

thanks

[zagreb999]

with respect

can not automount
hdd partitions with
thunar and pcmanfm

thunar 1.4 is very, very old

can not install network-
manager-gnome
pulseaudio is very old
an it does not work...

[mistfire]

@zagreb999

Does your latest TazPuppy setup has zdrv and fdrv file?

Where did you get the xfce?

Also if you want automount, just install startmount pet package. TazPuppy supports pet packages too

[zagreb999]

Does your latest TazPuppy setup has zdrv and fdrv file?
yes

Where did you get the xfce?
from tazpanel

Also if you want automount, just install startmount pet package. TazPuppy supports pet packages too

where is pet?

please, can you create repository
such as new xfce 4,14.
(your xfce is from last century...)
network manager gnome,,,
office,
master pdf editor
etc

also,
there is problem with wifi

starting wpa supplicant failed

[zagreb999]

how to autologin as
root???
how to disable function of
trash???
how to disable function
"move to trash"?
i have to clean trash 24 h!!!