Bug 492261 - xterm works as root, not as a normal user
Summary: xterm works as root, not as a normal user
Keywords:
Status: CLOSED DUPLICATE of bug 491813
Alias: None
Product: Fedora
Classification: Fedora
Component: xterm
Version: 10
Hardware: i686
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-26 08:55 UTC by Natxo Asenjo
Modified: 2009-03-31 13:38 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-03-31 13:38:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
attachment with results of $ strace -o xterm.log xterm (59.85 KB, application/octet-stream)
2009-03-26 08:55 UTC, Natxo Asenjo
no flags Details

Description Natxo Asenjo 2009-03-26 08:55:16 UTC
Created attachment 336764 [details]
attachment with results of  $ strace -o xterm.log xterm

Description of problem: cannot start xterm as normal user; as root there is no problem.


Version-Release number of selected component (if applicable):
X.Org 6.8.99.903(242)

How reproducible: in a gnome desktop use Alt-F2 to run application, enter xterm and press enter. Nothing happens. Open a gnome-terminal, type xterm [enter], nothing happens. 

In a gnome-terminal, su to root (su - , enter root password), type xterm, you get a xterm. 

Selinux is in permissive mode (does not change a thing from targeted mode)
Steps to Reproduce:
1. open gnome-terminal
2. su - to root
3. type xterm, then it works; under a normal user it does not work
  
Actual results:
xterm is borked for a normal user. I cannot use the citrix client because of this, I need to elevate privileges to be able to run programs that in fedora 9 run perfectly fine with the users privileges.

Expected results:
I expect xterm to work as a normal user.

Additional info:
attachment with results of strace -o xterm.log xterm

Comment 1 Miroslav Lichvar 2009-03-31 13:38:36 UTC

*** This bug has been marked as a duplicate of bug 491813 ***


Note You need to log in before you can comment on or make changes to this bug.