Bug 160250
Summary: | allmost no application are starting giving the error Xlib: connection to ":0.0" refused by server Xlib: No protocol specified | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ilja Kogan <news> |
Component: | system-config-securitylevel | Assignee: | Chris Lumens <clumens> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | bitrain, gajownik, knutjbj, tim.lauridsen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-12-20 19:16:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ilja Kogan
2005-06-13 20:33:06 UTC
*** Bug 160251 has been marked as a duplicate of this bug. *** Sorry for the doublepost ... I have found out something interesting: When I reboot everything works fine as long as I don't start # system-config-securitylevel Xlib: connection to ":0.0" refused by server Xlib: No protocol specified Afterwards again most of the applications are giving the same error. Sounds like it might be an issue with system-config-securitylevel itself. Reassigning... maybe a general python bug ? http://forums.fedoraforum.org/showthread.php?t=59407 I get when I try to start system-config-secerity as normal user and give root password. Traceback (most recent call last): File "/usr/share/system-config-securitylevel/system-config-securitylevel.py", line 18, in ? app.stand_alone() File "/usr/share/system-config-securitylevel/securitylevel.py", line 453, in stand_alone self.readFile() File "/usr/share/system-config-securitylevel/securitylevel.py", line 353, in readFile I can open yumex as noraml user but not as root with su. Xlib: connection to ":0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key Traceback (most recent call last): File "yumex.py", line 23, in ? File "yumWrapper.py", line 26, in ? File "/usr/lib/python2.4/site-packages/PIL/__init__.py", line 37, in ? RuntimeError: could not open display [root@knutjorgen knutjbj]# system-config-securitylevel Xlib: connection to ":0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key protoname = socket.getservbyport(int(service), protocol) socket.error: port/proto not found The message about port/proto not found is going out in an update here within a day or two. Look for the announcement on the mailing list and try again to see if that also fixes this problem. You can't run yumex just with su. You have to either go through the desktop's authorization mechanism or mess with xauth. hmm: # xhost + access control disabled, clients can connect from any host # system-config-securityleve Now it works like a charm. Let's wait until the next reboot, wether I'll have to make it everytime I start system-config-services this might interest you guys : http://www.fedoraforum.org/forum/showpost.php?p=282367&postcount=2 The traceback is fixed by an FC4 update I just pushed out. Curious if there's something more going on here with this bug, though. I get this when I try to run system-config-network when I su'd. When I didn't su, the enter your password windows comes and everything works. [root@localhost ~]# system-config-network Xlib: connection to ":0.0" refused by server Xlib: No protocol specified ERROR: Unable to initialize graphical environment. Most likely cause of failure is that the tool was not run using a graphical environment. Please either start your graphical user interface or set your DISPLAY variable. I am seeing the same issue with no X application working before doing the xhost + Even xauth does not appear to authenticate the app with the correct cookie. There may be an issue with xauth as well. Running an app from the Application menu as root works fine. I made an update to system-config-securitylevel-1.5.8.1-1 , but it's still there... Hey all! new to fedora, and I noticed that while the $> xhost + did me no good whatsover, this problem only happened when I was root, even if I $> su - to keep my environment. However doing this fixes the problem: (note this IS a HACK!, this still should be fixed) (some output from env is printed) HOME=/root LOGNAME=root LESSOPEN=|/usr/bin/lesspipe.sh %s DISPLAY=:0.0 G_BROKEN_FILENAMES=1 _=/bin/env [root@localhost ~]# export HOME=/home/username [root@localhost root]# export USER=username [root@localhost root]# synaptic Voila! I guessing this is a configuration mistake somewhere in the default install. Most likely someone decided it would be more secure if people couldn't run X programs as root from the terminal? (even though gksu lets me launch X apps as root anyways...) So looks like a misunderstanding on fc4 crew's part. Especially since some X apps (e.g. synaptic) need to be run as root to be useful.... *** This bug has been marked as a duplicate of 175783 *** |