Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Open Thunar to root broken [solved]

Help for Current Versions of MX
Message
Author
User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2064
Joined: Wed Apr 11, 2018 5:09 pm

Re: Open Thunar to root broken

#21 Post by fehlix » Sat Nov 03, 2018 9:54 am

Mauser wrote:
Sat Nov 03, 2018 9:10 am
ll /usr/bin returns.
Lot's of permissions are wrong, not only su/sudo but passwd etc. All setuid-bit's are missing, lot's of group ownership are wrong. I assume you have played with root-Thunar and copied stuff around, which resets permissions bit and group ownership and by this you have broken your system by yourself. :eek:

To illustrate here a extract of some ownership and permissions as they should be:

Code: Select all

$ ls -al /usr/bin/| grep -v 'root   root'                                                                                                               
insgesamt 598348
-rwsr-sr-x  1 daemon daemon     51464 Dez  8  2016 at
-rwxr-sr-x  1 root   tty        14768 Apr 12  2017 bsd-write
-rwxr-sr-x  1 root   shadow     71856 Mai 17  2017 chage
-rwxr-sr-x  1 root   crontab    40264 Okt  7  2017 crontab
-rwxr-sr-x  1 root   mail       19008 Jan 17  2017 dotlockfile
-rwxr-sr-x  1 root   shadow     22808 Mai 17  2017 expiry
-rwxr-sr-x  3 root   mail       14920 Dez  1  2012 mail-lock
-rwxr-sr-x  3 root   mail       14920 Dez  1  2012 mail-touchlock
-rwxr-sr-x  3 root   mail       14920 Dez  1  2012 mail-unlock
-rwxr-sr-x  1 root   mlocate    39680 Nov 13  2016 mlocate
-rwsr-xr--  1 root   plugdev    49496 Mai 18  2014 pmount
-rwsr-xr--  1 root   plugdev    35896 Mai 18  2014 pumount
-rwxr-sr-x  1 root   ssh       358624 Aug 21 05:14 ssh-agent
-rwxr-sr-x  1 root   tty        31576 Apr  3  2018 wall
fehlix@mx171:~/Desktop/00
$ ls -l /usr/bin/ | grep -E 'wsr|-sr'
-rwsr-sr-x 1 daemon daemon     51464 Dez  8  2016 at
-rwxr-sr-x 1 root   tty        14768 Apr 12  2017 bsd-write
-rwsr-xr-x 1 root   root       51304 Sep  5 19:49 bwrap
-rwxr-sr-x 1 root   shadow     71856 Mai 17  2017 chage
-rwsr-xr-x 1 root   root       50040 Mai 17  2017 chfn
-rwsr-xr-x 1 root   root       40504 Mai 17  2017 chsh
-rwxr-sr-x 1 root   crontab    40264 Okt  7  2017 crontab
-rwxr-sr-x 1 root   mail       19008 Jan 17  2017 dotlockfile
-rwxr-sr-x 1 root   shadow     22808 Mai 17  2017 expiry
-rwsr-xr-x 1 root   root       75792 Mai 17  2017 gpasswd
-rwxr-sr-x 3 root   mail       14920 Dez  1  2012 mail-lock
-rwxr-sr-x 3 root   mail       14920 Dez  1  2012 mail-touchlock
-rwxr-sr-x 3 root   mail       14920 Dez  1  2012 mail-unlock
-rwxr-sr-x 1 root   mlocate    39680 Nov 13  2016 mlocate
-rwsr-xr-x 1 root   root       40312 Mai 17  2017 newgrp
-rwsr-xr-x 1 root   root       34904 Feb 28  2018 nvidia-modprobe
-rwsr-xr-x 1 root   root       59680 Mai 17  2017 passwd
-rwsr-xr-x 1 root   root       23352 Mai 24  2017 pkexec
-rwsr-xr-- 1 root   plugdev    49496 Mai 18  2014 pmount
-rwsr-xr-- 1 root   plugdev    35896 Mai 18  2014 pumount
-rwxr-xr-x 1 root   root       14816 Jan 23  2017 recode-sr-latin
-rwxr-sr-x 1 root   ssh       358624 Aug 21 05:14 ssh-agent
-rwsr-xr-x 1 root   root      140944 Jun  5  2017 sudo
-rwsr-xr-x 1 root   root      114144 Jul 15  2015 udevil
-rwxr-sr-x 1 root   tty        31576 Apr  3  2018 wall
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9639
Joined: Sun Dec 16, 2007 1:17 pm

Re: Open Thunar to root broken

#22 Post by dolphin_oracle » Sat Nov 03, 2018 9:58 am

fehlix wrote:
Sat Nov 03, 2018 9:54 am
Mauser wrote:
Sat Nov 03, 2018 9:10 am
ll /usr/bin returns.
Lot's of permissions are wrong, not only su/sudo but passwd etc. All setuid-bit's are missing, lot's of group ownership are wrong. I assume you have played with root-Thunar and copied stuff around, which resets permissions bit and group ownership and by this you have broken your system by yourself. :eek:

To illustrate here a extract of some ownership and permissions as they should be:

Code: Select all

$ ls -al /usr/bin/| grep -v 'root   root'                                                                                                               
insgesamt 598348
-rwsr-sr-x  1 daemon daemon     51464 Dez  8  2016 at
-rwxr-sr-x  1 root   tty        14768 Apr 12  2017 bsd-write
-rwxr-sr-x  1 root   shadow     71856 Mai 17  2017 chage
-rwxr-sr-x  1 root   crontab    40264 Okt  7  2017 crontab
-rwxr-sr-x  1 root   mail       19008 Jan 17  2017 dotlockfile
-rwxr-sr-x  1 root   shadow     22808 Mai 17  2017 expiry
-rwxr-sr-x  3 root   mail       14920 Dez  1  2012 mail-lock
-rwxr-sr-x  3 root   mail       14920 Dez  1  2012 mail-touchlock
-rwxr-sr-x  3 root   mail       14920 Dez  1  2012 mail-unlock
-rwxr-sr-x  1 root   mlocate    39680 Nov 13  2016 mlocate
-rwsr-xr--  1 root   plugdev    49496 Mai 18  2014 pmount
-rwsr-xr--  1 root   plugdev    35896 Mai 18  2014 pumount
-rwxr-sr-x  1 root   ssh       358624 Aug 21 05:14 ssh-agent
-rwxr-sr-x  1 root   tty        31576 Apr  3  2018 wall
fehlix@mx171:~/Desktop/00
$ ls -l /usr/bin/ | grep -E 'wsr|-sr'
-rwsr-sr-x 1 daemon daemon     51464 Dez  8  2016 at
-rwxr-sr-x 1 root   tty        14768 Apr 12  2017 bsd-write
-rwsr-xr-x 1 root   root       51304 Sep  5 19:49 bwrap
-rwxr-sr-x 1 root   shadow     71856 Mai 17  2017 chage
-rwsr-xr-x 1 root   root       50040 Mai 17  2017 chfn
-rwsr-xr-x 1 root   root       40504 Mai 17  2017 chsh
-rwxr-sr-x 1 root   crontab    40264 Okt  7  2017 crontab
-rwxr-sr-x 1 root   mail       19008 Jan 17  2017 dotlockfile
-rwxr-sr-x 1 root   shadow     22808 Mai 17  2017 expiry
-rwsr-xr-x 1 root   root       75792 Mai 17  2017 gpasswd
-rwxr-sr-x 3 root   mail       14920 Dez  1  2012 mail-lock
-rwxr-sr-x 3 root   mail       14920 Dez  1  2012 mail-touchlock
-rwxr-sr-x 3 root   mail       14920 Dez  1  2012 mail-unlock
-rwxr-sr-x 1 root   mlocate    39680 Nov 13  2016 mlocate
-rwsr-xr-x 1 root   root       40312 Mai 17  2017 newgrp
-rwsr-xr-x 1 root   root       34904 Feb 28  2018 nvidia-modprobe
-rwsr-xr-x 1 root   root       59680 Mai 17  2017 passwd
-rwsr-xr-x 1 root   root       23352 Mai 24  2017 pkexec
-rwsr-xr-- 1 root   plugdev    49496 Mai 18  2014 pmount
-rwsr-xr-- 1 root   plugdev    35896 Mai 18  2014 pumount
-rwxr-xr-x 1 root   root       14816 Jan 23  2017 recode-sr-latin
-rwxr-sr-x 1 root   ssh       358624 Aug 21 05:14 ssh-agent
-rwsr-xr-x 1 root   root      140944 Jun  5  2017 sudo
-rwsr-xr-x 1 root   root      114144 Jul 15  2015 udevil
-rwxr-sr-x 1 root   tty        31576 Apr  3  2018 wall
:puppy:
I really think that the "change ownership to root" thunar right-click action got used inadvertently. the action produces the results provided by Mauser's info.

so yes, he likely did it to himself. the question is...is it too easy to do? that's a question for dev team to hash out.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
Mauser
Forum Regular
Forum Regular
Posts: 711
Joined: Mon Jun 27, 2016 7:32 pm

Re: Open Thunar to root broken

#23 Post by Mauser » Sat Nov 03, 2018 10:05 am

fehlix wrote:
Sat Nov 03, 2018 9:54 am
Mauser wrote:
Sat Nov 03, 2018 9:10 am
ll /usr/bin returns.
Lot's of permissions are wrong, not only su/sudo but passwd etc. All setuid-bit's are missing, lot's of group ownership are wrong. I assume you have played with root-Thunar and copied stuff around, which resets permissions bit and group ownership and by this you have broken your system by yourself. :eek:

To illustrate here a extract of some ownership and permissions as they should be:

Code: Select all

$ ls -al /usr/bin/| grep -v 'root   root'                                                                                                               
insgesamt 598348
-rwsr-sr-x  1 daemon daemon     51464 Dez  8  2016 at
-rwxr-sr-x  1 root   tty        14768 Apr 12  2017 bsd-write
-rwxr-sr-x  1 root   shadow     71856 Mai 17  2017 chage
-rwxr-sr-x  1 root   crontab    40264 Okt  7  2017 crontab
-rwxr-sr-x  1 root   mail       19008 Jan 17  2017 dotlockfile
-rwxr-sr-x  1 root   shadow     22808 Mai 17  2017 expiry
-rwxr-sr-x  3 root   mail       14920 Dez  1  2012 mail-lock
-rwxr-sr-x  3 root   mail       14920 Dez  1  2012 mail-touchlock
-rwxr-sr-x  3 root   mail       14920 Dez  1  2012 mail-unlock
-rwxr-sr-x  1 root   mlocate    39680 Nov 13  2016 mlocate
-rwsr-xr--  1 root   plugdev    49496 Mai 18  2014 pmount
-rwsr-xr--  1 root   plugdev    35896 Mai 18  2014 pumount
-rwxr-sr-x  1 root   ssh       358624 Aug 21 05:14 ssh-agent
-rwxr-sr-x  1 root   tty        31576 Apr  3  2018 wall
fehlix@mx171:~/Desktop/00
$ ls -l /usr/bin/ | grep -E 'wsr|-sr'
-rwsr-sr-x 1 daemon daemon     51464 Dez  8  2016 at
-rwxr-sr-x 1 root   tty        14768 Apr 12  2017 bsd-write
-rwsr-xr-x 1 root   root       51304 Sep  5 19:49 bwrap
-rwxr-sr-x 1 root   shadow     71856 Mai 17  2017 chage
-rwsr-xr-x 1 root   root       50040 Mai 17  2017 chfn
-rwsr-xr-x 1 root   root       40504 Mai 17  2017 chsh
-rwxr-sr-x 1 root   crontab    40264 Okt  7  2017 crontab
-rwxr-sr-x 1 root   mail       19008 Jan 17  2017 dotlockfile
-rwxr-sr-x 1 root   shadow     22808 Mai 17  2017 expiry
-rwsr-xr-x 1 root   root       75792 Mai 17  2017 gpasswd
-rwxr-sr-x 3 root   mail       14920 Dez  1  2012 mail-lock
-rwxr-sr-x 3 root   mail       14920 Dez  1  2012 mail-touchlock
-rwxr-sr-x 3 root   mail       14920 Dez  1  2012 mail-unlock
-rwxr-sr-x 1 root   mlocate    39680 Nov 13  2016 mlocate
-rwsr-xr-x 1 root   root       40312 Mai 17  2017 newgrp
-rwsr-xr-x 1 root   root       34904 Feb 28  2018 nvidia-modprobe
-rwsr-xr-x 1 root   root       59680 Mai 17  2017 passwd
-rwsr-xr-x 1 root   root       23352 Mai 24  2017 pkexec
-rwsr-xr-- 1 root   plugdev    49496 Mai 18  2014 pmount
-rwsr-xr-- 1 root   plugdev    35896 Mai 18  2014 pumount
-rwxr-xr-x 1 root   root       14816 Jan 23  2017 recode-sr-latin
-rwxr-sr-x 1 root   ssh       358624 Aug 21 05:14 ssh-agent
-rwsr-xr-x 1 root   root      140944 Jun  5  2017 sudo
-rwsr-xr-x 1 root   root      114144 Jul 15  2015 udevil
-rwxr-sr-x 1 root   tty        31576 Apr  3  2018 wall
:puppy:
No, because Thunar wouldn't let me do anything. Thunar run amuck when I asked it to open as root and it didn't. How do I fix it without reinstalling MX Linux?

User avatar
Mauser
Forum Regular
Forum Regular
Posts: 711
Joined: Mon Jun 27, 2016 7:32 pm

Re: Open Thunar to root broken

#24 Post by Mauser » Sat Nov 03, 2018 10:13 am

I am going to file a bug report on Xfce.org on this because Thunar should do exactly what I tell it to and not cross connection causing this problem. It should have a confirmation box. I also should be able to change it back to what it was.

User avatar
asqwerth
Forum Veteran
Forum Veteran
Posts: 3471
Joined: Sun May 27, 2007 5:37 am

Re: Open Thunar to root broken

#25 Post by asqwerth » Sat Nov 03, 2018 10:16 am

Mauser wrote:
Sat Nov 03, 2018 10:05 am
No, because Thunar wouldn't let me do anything. Thunar run amuck when I asked it to open as root and it didn't....
If you accidentally chose the wrong right click option to change ownership to root instead of open Root Thunar, it would appear to you as if nothing happened, but in actual fact, ownership of that folder would have been changed.

Depending which folder you had pointed to to change ownership, the next attempt to use Thunar would then lead to all the problems, because assuming the folder should have been usable and owned by you as user, would now be owned by root so you can no longer access it as a normal user.

If this happened a few other times in the past, where, say, your first attempt to open as root clicked on "change ownership" instead, causing you to think nothing had happened, you could have accumulated quite a few wrongly owned folders/files.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9639
Joined: Sun Dec 16, 2007 1:17 pm

Re: Open Thunar to root broken

#26 Post by dolphin_oracle » Sat Nov 03, 2018 10:19 am

yeah, I think all that drive action you heard was the permissions being changed.

those actions are not thunar defaults. we've added them.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2064
Joined: Wed Apr 11, 2018 5:09 pm

Re: Open Thunar to root broken

#27 Post by fehlix » Sat Nov 03, 2018 10:19 am

Mauser wrote:
Sat Nov 03, 2018 10:05 am
No, because Thunar wouldn't let me do anything. Thunar run amuck when I asked it to open as root and it didn't. How do I fix it without reinstalling MX Linux?
Without knowing what else in your system is wrong, it might best to reinstall.
My strong advice: Stay away from Root esp the Thunar actions with root (change ownership and root-Thunar. As you can bork you system so easily. This actions are meant for experts only. Best remove thos from Thunar.
The only "bug" I see, is that the warning within root-Thunar is far to small and shall by much bigger :eek: !
As normal user you don't need any of those root-actions. Nearly all customizations can be done within the home directory itself, e.g icon set, new desktop-icons etc.
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
richb
Administrator
Posts: 17239
Joined: Wed Jul 12, 2006 2:17 pm

Re: Open Thunar to root broken

#28 Post by richb » Sat Nov 03, 2018 10:22 am

There are two right menu entries that pertain, Open as root and Ownership to root. Ownership to root causes the mayhem that ensued for you. Open as root will open thunar as root nicely with no ill effects unless one subsequently does something untoward in the root thunar.

It no doubt will be a subject for the dev team to attempt to make this distinction more clear and as failsafe as possible. Perhaps eliminate the ownership to root option. I am not sure why anyone would want to do that.

EDIT: I would like to see open as root remain. I use that frequently to tweak a root config file without having to log out and back in as the root user. It can also be accomplished via the terminal but not as convenient for primarily GUI users.
Forum Rules
Guide - How to Ask for Help

Rich
SSD Production: MX 17.1
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB, 350 GB HD

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2064
Joined: Wed Apr 11, 2018 5:09 pm

Re: Open Thunar to root broken

#29 Post by fehlix » Sat Nov 03, 2018 10:23 am

Mauser wrote:
Sat Nov 03, 2018 10:13 am
I am going to file a bug report on Xfce.org on this because Thunar should do exactly what I tell it to and not cross connection causing this problem. It should have a confirmation box. I also should be able to change it back to what it was.
That's not a failure of Thunar, but made by yourself (without knowing!) :p
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Mauser
Forum Regular
Forum Regular
Posts: 711
Joined: Mon Jun 27, 2016 7:32 pm

Re: Open Thunar to root broken

#30 Post by Mauser » Sat Nov 03, 2018 10:25 am

fehlix wrote:
Sat Nov 03, 2018 10:19 am
Mauser wrote:
Sat Nov 03, 2018 10:05 am
No, because Thunar wouldn't let me do anything. Thunar run amuck when I asked it to open as root and it didn't. How do I fix it without reinstalling MX Linux?
Without knowing what else in your system is wrong, it might best to reinstall.
My strong advice: Stay away from Root esp the Thunar actions with root (change ownership and root-Thunar. As you can bork you system so easily. This actions are meant for experts only. Best remove thos from Thunar.
The only "bug" I see, is that the warning within root-Thunar is far to small and shall by much bigger :eek: !
As normal user you don't need any of those root-actions. Nearly all customizations can be done within the home directory itself, e.g icon set, new desktop-icons etc.
:puppy:
I was adding icons. I still should be able to change it back to what it was. Looks like I will have to re-install MX Linux.

Post Reply

Return to “MX Help”