LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-07-2019, 12:04 PM   #1
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware
Posts: 1,122
Blog Entries: 3

Rep: Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048
Evince opening as root


I opened Evince just now to see it's running as root [my theme puts a red line at the top of a program to show this].

Code:
lysander@psychopig-xxxiv:~$ ps -elf|grep root
4 S root         1     0  0  80   0 -  1093 -      Jan04 ?        00:00:01 init [3]
1 S root         2     0  0  80   0 -     0 -      Jan04 ?        00:00:00 [kthreadd]
1 S root         3     2  0  80   0 -     0 -      Jan04 ?        00:00:01 [ksoftirqd/0]
1 S root         5     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kworker/0:0H]
1 S root         7     2  0  80   0 -     0 -      Jan04 ?        00:02:04 [rcu_sched]
1 S root         8     2  0  80   0 -     0 -      Jan04 ?        00:00:00 [rcu_bh]
1 S root         9     2  0 -40   - -     0 -      Jan04 ?        00:00:00 [migration/0]
1 S root        10     2  0 -40   - -     0 -      Jan04 ?        00:00:00 [migration/1]
1 S root        11     2  0  80   0 -     0 -      Jan04 ?        00:00:01 [ksoftirqd/1]
1 S root        13     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kworker/1:0H]
1 S root        14     2  0 -40   - -     0 -      Jan04 ?        00:00:00 [migration/2]
1 S root        15     2  0  80   0 -     0 -      Jan04 ?        00:00:01 [ksoftirqd/2]
1 S root        17     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kworker/2:0H]
1 S root        18     2  0 -40   - -     0 -      Jan04 ?        00:00:00 [migration/3]
1 S root        19     2  0  80   0 -     0 -      Jan04 ?        00:00:01 [ksoftirqd/3]
1 S root        21     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kworker/3:0H]
5 S root        22     2  0  80   0 -     0 -      Jan04 ?        00:00:00 [kdevtmpfs]
1 S root        23     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [netns]
1 S root        24     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [perf]
1 S root        25     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [writeback]
1 S root        26     2  0  99  19 -     0 -      Jan04 ?        00:00:19 [khugepaged]
1 S root        27     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [crypto]
1 S root        28     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kintegrityd]
1 S root        29     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root        30     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kblockd]
1 S root        31     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [ata_sff]
1 S root        32     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [md]
1 S root        33     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [devfreq_wq]
1 S root        38     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [rpciod]
1 S root        57     2  0  80   0 -     0 -      Jan04 ?        00:00:02 [kswapd0]
1 S root        58     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [vmstat]
1 S root        59     2  0  80   0 -     0 -      Jan04 ?        00:00:00 [fsnotify_mark]
1 S root        60     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [nfsiod]
1 S root       126     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kthrotld]
1 S root       128     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       129     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       130     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       131     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       132     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       133     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       134     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       135     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       136     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       137     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       138     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       139     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       140     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       141     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       142     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       143     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       144     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       145     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       146     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       147     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       148     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       149     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       150     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       151     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       152     2  0  80   0 -     0 -      Jan04 ?        00:00:00 [scsi_eh_0]
1 S root       153     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [scsi_tmf_0]
1 S root       154     2  0  80   0 -     0 -      Jan04 ?        00:00:00 [scsi_eh_1]
1 S root       155     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [scsi_tmf_1]
1 S root       158     2  0  80   0 -     0 -      Jan04 ?        00:00:00 [scsi_eh_2]
1 S root       159     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [scsi_tmf_2]
1 S root       160     2  0  80   0 -     0 -      Jan04 ?        00:00:00 [scsi_eh_3]
1 S root       161     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [scsi_tmf_3]
1 S root       164     2  0  80   0 -     0 -      Jan04 ?        00:00:00 [scsi_eh_4]
1 S root       165     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [scsi_tmf_4]
1 S root       166     2  0  80   0 -     0 -      Jan04 ?        00:00:00 [scsi_eh_5]
1 S root       167     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [scsi_tmf_5]
1 S root       174     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       175     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       176     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       177     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       182     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [raid5wq]
1 S root       186     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [deferwq]
1 S root       227     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kworker/1:1H]
1 S root       229     2  0  60 -20 -     0 -      Jan04 ?        00:00:02 [kworker/0:1H]
1 S root       236     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kworker/3:1H]
1 S root       238     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kworker/2:1H]
1 S root       287     2  0  80   0 -     0 -      Jan04 ?        00:00:00 [jbd2/sdc1-8]
1 S root       288     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [ext4-rsv-conver]
1 S root       305     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       306     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       307     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       308     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       309     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       310     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       311     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
1 S root       312     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [bioset]
5 S root       637     1  0  80   0 -  9035 -      Jan04 ?        00:00:00 /sbin/udevd --daemon
1 S root       679     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kpsmoused]
1 S root       686     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kvm-irqfd-clean]
1 S root       687     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [kfd_process_wq]
1 S root       689     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [ttm_swap]
1 S root       758     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [radeon-crtc]
1 S root       759     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [radeon-crtc]
1 S root       760     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [radeon-crtc]
1 S root       761     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [radeon-crtc]
1 S root       762     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [radeon-crtc]
1 S root       763     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [radeon-crtc]
1 S root       863     2  0  80   0 -     0 -      Jan04 ?        00:00:07 [jbd2/sdc3-8]
1 S root       864     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [ext4-rsv-conver]
5 S root       875     1  0  80   0 -  5942 -      Jan04 ?        00:00:00 /usr/sbin/cgmanager --daemon
1 S root       907     1  0  80   0 -  1626 -      Jan04 ?        00:00:00 /usr/sbin/syslogd
5 S root       911     1  0  80   0 -  1094 -      Jan04 ?        00:00:00 /usr/sbin/klogd -c 3 -x
5 S root      1123     1  0  80   0 -  1622 -      Jan04 ?        00:00:00 /usr/sbin/inetd
1 S root      1128     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [ipv6_addrconf]
5 S root      1129     1  0  80   0 -  7175 -      Jan04 ?        00:00:00 /usr/sbin/sshd
1 S root      1140     1  0  80   0 -  1098 -      Jan04 ?        00:00:03 /usr/sbin/acpid
5 S root      1154     1  0  80   0 - 104717 -     Jan04 ?        00:00:00 /usr/sbin/console-kit-daemon
1 S root      1156     1  0  80   0 - 49094 -      Jan04 ?        00:01:05 /usr/bin/python -O /usr/share/wicd/daemon/wicd-daemon.py
1 S root      1165     1  0  80   0 -  3207 -      Jan04 ?        00:00:00 /usr/sbin/crond -l notice
5 S root      1186     1  0  80   0 -  1889 -      Jan04 ?        00:00:02 /usr/sbin/gpm -m /dev/mouse -t imps2
0 S root      1190  1156  0  80   0 - 28118 -      Jan04 ?        00:00:21 /usr/bin/python -O /usr/share/wicd/daemon/monitor.py
4 S root      1359     1  0  80   0 -  3209 -      Jan04 tty2     00:00:00 /sbin/agetty 38400 tty2 linux
4 S root      1360     1  0  80   0 -  3209 -      Jan04 tty3     00:00:00 /sbin/agetty 38400 tty3 linux
4 S root      1361     1  0  80   0 -  3209 -      Jan04 tty4     00:00:00 /sbin/agetty 38400 tty4 linux
4 S root      1362     1  0  80   0 -  3209 -      Jan04 tty5     00:00:00 /sbin/agetty 38400 tty5 linux
4 S root      1363     1  0  80   0 -  3209 -      Jan04 tty6     00:00:00 /sbin/agetty 38400 tty6 linux
1 S root      1390     2  0  60 -20 -     0 -      Jan04 ?        00:00:00 [cfg80211]
4 S root      1448  1447  2  80   0 - 133275 -     Jan04 tty7     01:27:04 /usr/libexec/Xorg :0 -auth /home/lysander/.serverauth.1431
4 S root      1491     1  0  80   0 - 55462 -      Jan04 ?        00:00:00 /usr/libexec/upowerd
4 S root      1684     1  0  80   0 - 107164 -     Jan04 ?        00:00:39 /usr/lib/udisks2/udisksd --no-debug
5 S root      2632     1  0  80   0 -  1672 -      11:20 ?        00:00:00 /sbin/dhcpcd --noipv4ll eth0
1 S root     12084     2  0  80   0 -     0 -      16:24 ?        00:00:01 [kworker/u8:2]
1 S root     12130     2  0  80   0 -     0 -      16:26 ?        00:00:02 [kworker/0:0]
1 S root     12494     2  0  80   0 -     0 -      16:41 ?        00:00:00 [kworker/3:2]
1 S root     12557     2  0  80   0 -     0 -      16:42 ?        00:00:00 [kworker/1:1]
1 S root     12903     2  0  80   0 -     0 -      16:48 ?        00:00:00 [kworker/2:2]
1 S root     13380     2  0  80   0 -     0 -      16:54 ?        00:00:00 [kworker/1:0]
1 S root     13406     2  0  80   0 -     0 -      16:54 ?        00:00:00 [kworker/3:1]
1 S root     13410     2  0  80   0 -     0 -      16:54 ?        00:00:00 [kworker/2:0]
1 S root     13476     2  0  80   0 -     0 -      16:55 ?        00:00:00 [kworker/u8:0]
1 S root     13624     2  0  80   0 -     0 -      16:56 ?        00:00:00 [kworker/0:2]
1 S root     13800     2  0  80   0 -     0 -      16:59 ?        00:00:00 [kworker/1:2]
1 S root     13900     2  0  80   0 -     0 -      17:01 ?        00:00:00 [kworker/u8:1]
1 S root     13915     2  0  80   0 -     0 -      17:01 ?        00:00:00 [kworker/0:1]
0 S lysander 14012 14008  0  80   0 -  2918 pipe_w 17:03 pts/1    00:00:00 grep root
Code:
lysander@psychopig-xxxiv:~$ whereis evince
evince: /usr/bin/evince /usr/lib64/evince /usr/include/evince /usr/share/evince /usr/man/man1/evince.1.gz
I've no idea why this is happening. What's the best way to reset it so it's only opened by my user?
 
Old 01-07-2019, 12:08 PM   #2
average_user
Member
 
Registered: Dec 2010
Location: Warsaw, Poland
Distribution: Slackware
Posts: 323

Rep: Reputation: 124Reputation: 124
I can't see evince process in this list. Anyway, check what's the parent process of evince
Code:
grep PPid /proc/<EVINCE_PID>/status
And show output of:
Code:
ls -l $(command -v evince)

Last edited by average_user; 01-07-2019 at 12:09 PM.
 
Old 01-07-2019, 12:41 PM   #3
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware
Posts: 1,122

Original Poster
Blog Entries: 3

Rep: Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048
Quote:
Originally Posted by average_user View Post
I can't see evince process in this list. Anyway, check what's the parent process of evince
Code:
grep PPid /proc/<EVINCE_PID>/status
And show output of:
Code:
ls -l $(command -v evince)
It gives this:

Code:
lysander@psychopig-xxxiv:~$ pidof evince
15044
lysander@psychopig-xxxiv:~$ grep PPid /proc/15044/status
PPid:	3689
3689 is PCManFM.

Code:
lysander@psychopig-xxxiv:~$ ls -l $(command -v evince)
-rwxr-xr-x 1 root root 426816 Jul 31 19:30 /usr/bin/evince
 
Old 01-07-2019, 01:01 PM   #4
average_user
Member
 
Registered: Dec 2010
Location: Warsaw, Poland
Distribution: Slackware
Posts: 323

Rep: Reputation: 124Reputation: 124
Are you sure that evince is running as root though? As as I said there is no evince process in the list you posted.

It's possible that evince's parent process PCManFM is running as root.
 
Old 01-07-2019, 01:32 PM   #5
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware
Posts: 1,122

Original Poster
Blog Entries: 3

Rep: Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048
Quote:
Originally Posted by average_user View Post
Are you sure that evince is running as root though?
No, I'm not, I'm purely going by the window bar.

If I switch to root and open Evince, it appears with the normal window bar. I'm wondering if the theme has just mixed the two up.
 
Old 01-07-2019, 01:47 PM   #6
average_user
Member
 
Registered: Dec 2010
Location: Warsaw, Poland
Distribution: Slackware
Posts: 323

Rep: Reputation: 124Reputation: 124
OK, so to make sure find PID of evince process first:
Code:
$ ps aux | grep '[e]vince'
ja       29917  7.3  0.5 597784 41428 pts/21   Sl+  19:45   0:00 evince
and then check what's user id for the given PID, for example:
Code:
$ ps -o uid 29917
  UID
 1000
If evince is running as root uid should be 0.
 
1 members found this post helpful.
Old 01-07-2019, 04:08 PM   #7
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware
Posts: 1,122

Original Poster
Blog Entries: 3

Rep: Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048
Quote:
Originally Posted by average_user View Post
OK, so to make sure find PID of evince process first:
Code:
$ ps aux | grep '[e]vince'
ja       29917  7.3  0.5 597784 41428 pts/21   Sl+  19:45   0:00 evince
and then check what's user id for the given PID, for example:
Code:
$ ps -o uid 29917
  UID
 1000
If evince is running as root uid should be 0.
OK so we're getting somewhere.

Code:
lysander@psychopig-xxxiv:~$ ps aux | grep '[e]vince'
lysander 18316  5.4  1.0 831020 52872 tty1     Sl   21:07   0:01 evince
lysander@psychopig-xxxiv:~$ ps -o uid 18316 
  UID
 1000
lysander@psychopig-xxxiv:~$
So maybe the theme just mixed up the title bars?
 
Old 01-07-2019, 04:22 PM   #8
ehartman
Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 312

Rep: Reputation: 139Reputation: 139
Quote:
Originally Posted by Lysander666 View Post
So maybe the theme just mixed up the title bars?
Sounds like it.

BTW: a "normal", non-provileged user can only run a program "as root" when that program (executable file) is:
a) owned by root
b) has the setuid bit set.

Like this
Code:
-rwsr-xr-x 1 root root   90156 2013-08-08 04:16:04 /bin/mount
   ^   the "x" is shown as an "s" for the user
The mount command needs root rights to do "user mode" mounts.
The /bin/su command (of course) is another example.

I don't think your evince program has that bit set although as you compiled it as root make DID have the privilege TO set it.
 
1 members found this post helpful.
Old 01-08-2019, 05:26 AM   #9
average_user
Member
 
Registered: Dec 2010
Location: Warsaw, Poland
Distribution: Slackware
Posts: 323

Rep: Reputation: 124Reputation: 124
@Lysander666, could you post contents of your theme config? I wonder if evince or your window manager distinguishes user id and real user id.
 
1 members found this post helpful.
Old 01-08-2019, 06:01 AM   #10
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware
Posts: 1,122

Original Poster
Blog Entries: 3

Rep: Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048
Thanks to both of you - very interesting, ehartman. average_user, I can't post the contents, they seem to be too long for posting.

The theme is this one:

https://www.deviantart.com/killhello...2015-569072551

It has gtk2 and gtk3 in there. I am not sure which is used when using Evince. It may be gtk3 - if so, the relevant title bar is in the folder called "assets" and is "background-dark-ssd.png" [normal windows are "background-dark.png".

EDIT: I've just looked at the graphic properly in the Deviant Art image. Seems that the one with the red bar over it is the normal theme. Seeing as the theme mostly uses gtk2 on my system [which utilises any window style of my choice], I got confused. By the looks of things, the theme is working as intended. I'm sorry for wasting anyone's time but I did learn something in the process!

Last edited by Lysander666; 01-08-2019 at 06:03 AM.
 
Old 01-08-2019, 07:24 AM   #11
ehartman
Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 312

Rep: Reputation: 139Reputation: 139
Quote:
Originally Posted by Lysander666 View Post
I can't post the contents,
But can you post
Code:
ls -l `which evince`
to see what its attributes are?
 
Old 01-08-2019, 07:57 AM   #12
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware
Posts: 1,122

Original Poster
Blog Entries: 3

Rep: Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048Reputation: 1048
Quote:
Originally Posted by ehartman View Post
But can you post
Code:
ls -l `which evince`
to see what its attributes are?
This gives a similar results to that a few posts above [I reinstalled Evince yesterday, by the way, to see if it would make any difference].

Code:
lysander@psychopig-xxxiv:~$ ls -l `which evince`
-rwxr-xr-x 1 root root 426816 Jan  7 21:48 /usr/bin/evince
lysander@psychopig-xxxiv:~$
 
Old 01-08-2019, 09:20 AM   #13
ehartman
Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 312

Rep: Reputation: 139Reputation: 139
Quote:
Originally Posted by Lysander666 View Post
Code:
lysander@psychopig-xxxiv:~$ ls -l `which evince`
-rwxr-xr-x 1 root root 426816 Jan  7 21:48 /usr/bin/evince
So when NOT run as user "root" it will NOT run as root because it doesn't have setuid right. Any program, run by a userID > 0, will run with that userID independent of what the owner of the executable is. Only WITH setuid it will run as that owner ID.
So another proof that your theme (or your interpretation OF it) is the problem:
evince is definitively not running as root.
 
1 members found this post helpful.
Old 01-08-2019, 09:26 AM   #14
cynwulf
Senior Member
 
Registered: Apr 2005
Posts: 2,204
Blog Entries: 5

Rep: Reputation: 1274Reputation: 1274Reputation: 1274Reputation: 1274Reputation: 1274Reputation: 1274Reputation: 1274Reputation: 1274Reputation: 1274
Quote:
Originally Posted by ehartman View Post
BTW: a "normal", non-provileged user can only run a program "as root" when that program (executable file) is:
a) owned by root
b) has the setuid bit set.
Which is for example how (insecure) setuid Xorg is set to run:

Quote:
Originally Posted by Lysander666 View Post
Code:
4 S root      1448  1447  2  80   0 - 133275 -     Jan04 tty7     01:27:04 /usr/libexec/Xorg :0 -auth /home/lysander/.serverauth.1431
 
1 members found this post helpful.
Old 01-08-2019, 09:41 AM   #15
ehartman
Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 312

Rep: Reputation: 139Reputation: 139
Quote:
Originally Posted by cynwulf View Post
Which is for example how (insecure) setuid Xorg is set to run:
It has to be, otherwise a command like "startx" wouldn't work.
When started through a dm (Display Manager) it will be started as root anyway, so doesn't need the setuid, but when started by a non-privileged user it has to be able to grab video, keyboard, mouse etc. devices exclusively for it, so that it can react to events (like a keypress or a mouse movement). Even a simple mouse manager like gpm has to run as root.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
"launch" link in Evince doc reader opening new Nautilus windows atmartin50 Linux - Software 5 08-14-2007 01:39 AM
Evince - Gtk-CRITICAL errors snl Linux - Software 0 07-19-2006 05:11 AM
embedding evince wi th mozplugger in firefox Valhalla Linux - Software 1 12-17-2005 06:43 PM
evince doesn't print PDF files correctly polemon Linux - Software 0 11-22-2005 05:16 PM
Comment on Evince satimis Linux - Software 2 09-03-2005 05:22 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:43 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration