xterm is not working on RHEL 7.2

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












xterm is throwing below error on RHEL 7.2:



$ xterm &


[1] 21638
Warning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm: Xt error: Can't open display: %s
[1]+ Exit 1 xterm
[/RHEL/Packages]


$ rpm -qa | grep -i xterm
xterm-295-3.el7.x86_64


what I am missing here?







share|improve this question






















  • rpm -V xterm says?
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 13:51










  • @Ignacio: nothing
    – dcds
    Nov 6 '17 at 14:57










  • try to remove it and install it again
    – Arpit Agarwal
    Nov 6 '17 at 15:11










  • try to remove it and install it again
    – Arpit Agarwal
    Nov 6 '17 at 15:11














up vote
0
down vote

favorite












xterm is throwing below error on RHEL 7.2:



$ xterm &


[1] 21638
Warning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm: Xt error: Can't open display: %s
[1]+ Exit 1 xterm
[/RHEL/Packages]


$ rpm -qa | grep -i xterm
xterm-295-3.el7.x86_64


what I am missing here?







share|improve this question






















  • rpm -V xterm says?
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 13:51










  • @Ignacio: nothing
    – dcds
    Nov 6 '17 at 14:57










  • try to remove it and install it again
    – Arpit Agarwal
    Nov 6 '17 at 15:11










  • try to remove it and install it again
    – Arpit Agarwal
    Nov 6 '17 at 15:11












up vote
0
down vote

favorite









up vote
0
down vote

favorite











xterm is throwing below error on RHEL 7.2:



$ xterm &


[1] 21638
Warning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm: Xt error: Can't open display: %s
[1]+ Exit 1 xterm
[/RHEL/Packages]


$ rpm -qa | grep -i xterm
xterm-295-3.el7.x86_64


what I am missing here?







share|improve this question














xterm is throwing below error on RHEL 7.2:



$ xterm &


[1] 21638
Warning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm: Xt error: Can't open display: %s
[1]+ Exit 1 xterm
[/RHEL/Packages]


$ rpm -qa | grep -i xterm
xterm-295-3.el7.x86_64


what I am missing here?









share|improve this question













share|improve this question




share|improve this question








edited Nov 6 '17 at 14:54









Jeff Schaller

32k849109




32k849109










asked Nov 6 '17 at 13:48









dcds

982414




982414











  • rpm -V xterm says?
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 13:51










  • @Ignacio: nothing
    – dcds
    Nov 6 '17 at 14:57










  • try to remove it and install it again
    – Arpit Agarwal
    Nov 6 '17 at 15:11










  • try to remove it and install it again
    – Arpit Agarwal
    Nov 6 '17 at 15:11
















  • rpm -V xterm says?
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 13:51










  • @Ignacio: nothing
    – dcds
    Nov 6 '17 at 14:57










  • try to remove it and install it again
    – Arpit Agarwal
    Nov 6 '17 at 15:11










  • try to remove it and install it again
    – Arpit Agarwal
    Nov 6 '17 at 15:11















rpm -V xterm says?
– Ignacio Vazquez-Abrams
Nov 6 '17 at 13:51




rpm -V xterm says?
– Ignacio Vazquez-Abrams
Nov 6 '17 at 13:51












@Ignacio: nothing
– dcds
Nov 6 '17 at 14:57




@Ignacio: nothing
– dcds
Nov 6 '17 at 14:57












try to remove it and install it again
– Arpit Agarwal
Nov 6 '17 at 15:11




try to remove it and install it again
– Arpit Agarwal
Nov 6 '17 at 15:11












try to remove it and install it again
– Arpit Agarwal
Nov 6 '17 at 15:11




try to remove it and install it again
– Arpit Agarwal
Nov 6 '17 at 15:11










1 Answer
1






active

oldest

votes

















up vote
0
down vote













short: don't run the application as root



long:



The message tells you what's wrong. The usual way to get this message is by logging in (as your normal, non-privileged user) and using su or sudo to switch to the root user.



The message (and check) was added in 1997 (it appeared first as a patch to XFree86 at the end of June as a followup to discussion in May, and two weeks later in X11R6.3).



Before then, root could connect to your X session and run any program that you (as root) chose. Unfortunately, many of the programs that were likely to be used weren't secure. (This is still the state for almost all of the desktop applications).



The X library making the check does this after seeing that it's the root user and then removing environment variables (such as DISPLAY) which might tempt you into falling into that morass of unsecured applications.



Some systems allow the root user to log into a desktop session; for those most immediately-accessible applications have been selected to keep things relatively safe. Some don't do that.



Now... in Red Hat 7, xterm is not installed set-uid or set-gid. set-uid to root was used 20 years ago to open the BSD-style pseudo-terminals, and set-gid was used to update utmp. Both of those went away quite a while ago. You can see that by doing



ls -l /usr/bin/xterm


If there's a set-uid or root user permission to be found, the place to start looking is at the shell from which you're running xterm.






share|improve this answer






















  • The $ indicates that it's being run as a normal user, versus # for root.
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 23:14










  • He could have chmod'd the program. Just as likely, running with a prompt set to '$'. Take your pick.
    – Thomas Dickey
    Nov 6 '17 at 23:15










  • Right, but rpm -V xterm returned nothing, which means that they haven't been tampered with.
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 23:16










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f402832%2fxterm-is-not-working-on-rhel-7-2%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













short: don't run the application as root



long:



The message tells you what's wrong. The usual way to get this message is by logging in (as your normal, non-privileged user) and using su or sudo to switch to the root user.



The message (and check) was added in 1997 (it appeared first as a patch to XFree86 at the end of June as a followup to discussion in May, and two weeks later in X11R6.3).



Before then, root could connect to your X session and run any program that you (as root) chose. Unfortunately, many of the programs that were likely to be used weren't secure. (This is still the state for almost all of the desktop applications).



The X library making the check does this after seeing that it's the root user and then removing environment variables (such as DISPLAY) which might tempt you into falling into that morass of unsecured applications.



Some systems allow the root user to log into a desktop session; for those most immediately-accessible applications have been selected to keep things relatively safe. Some don't do that.



Now... in Red Hat 7, xterm is not installed set-uid or set-gid. set-uid to root was used 20 years ago to open the BSD-style pseudo-terminals, and set-gid was used to update utmp. Both of those went away quite a while ago. You can see that by doing



ls -l /usr/bin/xterm


If there's a set-uid or root user permission to be found, the place to start looking is at the shell from which you're running xterm.






share|improve this answer






















  • The $ indicates that it's being run as a normal user, versus # for root.
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 23:14










  • He could have chmod'd the program. Just as likely, running with a prompt set to '$'. Take your pick.
    – Thomas Dickey
    Nov 6 '17 at 23:15










  • Right, but rpm -V xterm returned nothing, which means that they haven't been tampered with.
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 23:16














up vote
0
down vote













short: don't run the application as root



long:



The message tells you what's wrong. The usual way to get this message is by logging in (as your normal, non-privileged user) and using su or sudo to switch to the root user.



The message (and check) was added in 1997 (it appeared first as a patch to XFree86 at the end of June as a followup to discussion in May, and two weeks later in X11R6.3).



Before then, root could connect to your X session and run any program that you (as root) chose. Unfortunately, many of the programs that were likely to be used weren't secure. (This is still the state for almost all of the desktop applications).



The X library making the check does this after seeing that it's the root user and then removing environment variables (such as DISPLAY) which might tempt you into falling into that morass of unsecured applications.



Some systems allow the root user to log into a desktop session; for those most immediately-accessible applications have been selected to keep things relatively safe. Some don't do that.



Now... in Red Hat 7, xterm is not installed set-uid or set-gid. set-uid to root was used 20 years ago to open the BSD-style pseudo-terminals, and set-gid was used to update utmp. Both of those went away quite a while ago. You can see that by doing



ls -l /usr/bin/xterm


If there's a set-uid or root user permission to be found, the place to start looking is at the shell from which you're running xterm.






share|improve this answer






















  • The $ indicates that it's being run as a normal user, versus # for root.
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 23:14










  • He could have chmod'd the program. Just as likely, running with a prompt set to '$'. Take your pick.
    – Thomas Dickey
    Nov 6 '17 at 23:15










  • Right, but rpm -V xterm returned nothing, which means that they haven't been tampered with.
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 23:16












up vote
0
down vote










up vote
0
down vote









short: don't run the application as root



long:



The message tells you what's wrong. The usual way to get this message is by logging in (as your normal, non-privileged user) and using su or sudo to switch to the root user.



The message (and check) was added in 1997 (it appeared first as a patch to XFree86 at the end of June as a followup to discussion in May, and two weeks later in X11R6.3).



Before then, root could connect to your X session and run any program that you (as root) chose. Unfortunately, many of the programs that were likely to be used weren't secure. (This is still the state for almost all of the desktop applications).



The X library making the check does this after seeing that it's the root user and then removing environment variables (such as DISPLAY) which might tempt you into falling into that morass of unsecured applications.



Some systems allow the root user to log into a desktop session; for those most immediately-accessible applications have been selected to keep things relatively safe. Some don't do that.



Now... in Red Hat 7, xterm is not installed set-uid or set-gid. set-uid to root was used 20 years ago to open the BSD-style pseudo-terminals, and set-gid was used to update utmp. Both of those went away quite a while ago. You can see that by doing



ls -l /usr/bin/xterm


If there's a set-uid or root user permission to be found, the place to start looking is at the shell from which you're running xterm.






share|improve this answer














short: don't run the application as root



long:



The message tells you what's wrong. The usual way to get this message is by logging in (as your normal, non-privileged user) and using su or sudo to switch to the root user.



The message (and check) was added in 1997 (it appeared first as a patch to XFree86 at the end of June as a followup to discussion in May, and two weeks later in X11R6.3).



Before then, root could connect to your X session and run any program that you (as root) chose. Unfortunately, many of the programs that were likely to be used weren't secure. (This is still the state for almost all of the desktop applications).



The X library making the check does this after seeing that it's the root user and then removing environment variables (such as DISPLAY) which might tempt you into falling into that morass of unsecured applications.



Some systems allow the root user to log into a desktop session; for those most immediately-accessible applications have been selected to keep things relatively safe. Some don't do that.



Now... in Red Hat 7, xterm is not installed set-uid or set-gid. set-uid to root was used 20 years ago to open the BSD-style pseudo-terminals, and set-gid was used to update utmp. Both of those went away quite a while ago. You can see that by doing



ls -l /usr/bin/xterm


If there's a set-uid or root user permission to be found, the place to start looking is at the shell from which you're running xterm.







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 6 '17 at 23:30

























answered Nov 6 '17 at 23:12









Thomas Dickey

49.7k585155




49.7k585155











  • The $ indicates that it's being run as a normal user, versus # for root.
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 23:14










  • He could have chmod'd the program. Just as likely, running with a prompt set to '$'. Take your pick.
    – Thomas Dickey
    Nov 6 '17 at 23:15










  • Right, but rpm -V xterm returned nothing, which means that they haven't been tampered with.
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 23:16
















  • The $ indicates that it's being run as a normal user, versus # for root.
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 23:14










  • He could have chmod'd the program. Just as likely, running with a prompt set to '$'. Take your pick.
    – Thomas Dickey
    Nov 6 '17 at 23:15










  • Right, but rpm -V xterm returned nothing, which means that they haven't been tampered with.
    – Ignacio Vazquez-Abrams
    Nov 6 '17 at 23:16















The $ indicates that it's being run as a normal user, versus # for root.
– Ignacio Vazquez-Abrams
Nov 6 '17 at 23:14




The $ indicates that it's being run as a normal user, versus # for root.
– Ignacio Vazquez-Abrams
Nov 6 '17 at 23:14












He could have chmod'd the program. Just as likely, running with a prompt set to '$'. Take your pick.
– Thomas Dickey
Nov 6 '17 at 23:15




He could have chmod'd the program. Just as likely, running with a prompt set to '$'. Take your pick.
– Thomas Dickey
Nov 6 '17 at 23:15












Right, but rpm -V xterm returned nothing, which means that they haven't been tampered with.
– Ignacio Vazquez-Abrams
Nov 6 '17 at 23:16




Right, but rpm -V xterm returned nothing, which means that they haven't been tampered with.
– Ignacio Vazquez-Abrams
Nov 6 '17 at 23:16

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f402832%2fxterm-is-not-working-on-rhel-7-2%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?