Created attachment 398024 [details] log from unsucessful startup Description of problem: If I try to start X using startx command, I get only blank screen. Logging as root and trying startx, X works without any problem. Version-Release number of selected component (if applicable): xorg-x11-xinit-1.0.9-14.fc12 How reproducible: always Steps to Reproduce: 1. switch to runlevel without X (init 3) 2. log in as ordinary user 3. startx Actual results: blank screen on VT7; switching back to the console from startx was issued, there are error messages, can't break it, have to issue kill -9 from another console: X.Org X Server 1.7.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: x86-01 2.6.18-164.6.1.el5 Current Operating System: Linux dhcp-lab-151.englab.brq.redhat.com 2.6.31.12-174.2.22.fc12.x86_64 #1 SMP Fri Feb 19 18:55:03 UTC 2010 x86_64 Kernel command line: ro root=UUID=dda2eb47-7289-4cdf-8818-19983ad434fa rhgb quiet SYSFONT=latarcyrheb-sun16 LANG=cs_CZ.UTF-8 KEYTABLE=cz-lat2 Build Date: 16 February 2010 04:33:35AM Build ID: xorg-x11-server 1.7.5-1.fc12 Current version of pixman: 0.16.6 Before reporting problems, check http://bodhi.fedoraproject.org/ to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 5 09:28:18 2010 (==) Using default built-in configuration (30 lines) record: RECORD extension enabled at configure time. record: This extension is known to be broken, disabling extension now.. record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 resize called 1280 1024 The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols > Ignoring extra symbols Errors from xkbcomp are not fatal to the X server No protocol specified waiting for X server to begin accepting connections . No protocol specified .. No protocol specified .. No protocol specified .. No protocol specified .. No protocol specified .. No protocol specified .. No protocol specified .. No protocol specified ..^C No protocol specified .. Expected results: normal X and desktop environment startup Additional info:
Created attachment 398025 [details] log from another machine
COuld I get also output of dmesg (AFTER failure to get X on) and /var/log/messages (ditto), please? Thanks
Makes me wonder whether this is not a duplicate of bug 571639...
sorry, bug 571976 I meant
I've just retried on a qemu virtual system and it repeats the message Invalid MIT-MAGIC-COOKIE-1 key..
Created attachment 402018 [details] dmesg
Created attachment 402020 [details] Xorg.0.log
Created attachment 402022 [details] messages
Created attachment 402049 [details] dmesg, messages, Xorg.0.log tested on a real machine with F13 - console output the same as in the original case
(In reply to comment #0) > Created an attachment (id=398024) [details] > log from unsucessful startup johanka:~$ checkXorgLog 'https://bugzilla.redhat.com/attachment.cgi?id=398024' (WW) Warning, couldn't open module fbdev (EE) Failed to load module "fbdev" (module does not exist, 0) (WW) Falling back to old probe method for vesa johanka:~$ What's the story of your xorg-x11-drv-fbdev? (In reply to comment #7) > Created an attachment (id=402020) [details] > Xorg.0.log johanka:~$ checkXorgLog 'https://bugzilla.redhat.com/attachment.cgi?id=402020' (WW) Falling back to old probe method for cirrus (WW) Falling back to old probe method for vesa (WW) Falling back to old probe method for fbdev (EE) open /dev/fb0: No such file or directory (WW) CIRRUS(0): Unable to estimate virtual size johanka:~$ CIRRUS??? Could we keep testing on one driver, please?
(In reply to comment #10) > What's the story of your xorg-x11-drv-fbdev? # rpm -q xorg-x11-drv-fbdev package xorg-x11-drv-fbdev is not installed # rpm -q --whatrequires xorg-x11-drv-fbdev no package requires xorg-x11-drv-fbdev why should I have it if xorg-x11-drv-intel works just fine? > CIRRUS??? Could we keep testing on one driver, please? well ... I thought the root cause is the same, but ok, I'll be testing just on one machine
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
I had the exact same problem, not able to start from user, able to start in root, same "No protocol specified .. No protocol specified ..", etc. Solved by deleting the .Xauthority in the users home directory.
I also met such problem , and the cause of it is : The X server cannot write to the dir: ~/.kde . When I fixed it and .kde and other related files are writable, the problem "No protocol specified" is fixed.