$# startx X org will start, and immediately close within 1-2 seconds. There are no errors or warnings even on the console after it closes. My setup: Xorg 7.0 built from source for Gentoo/ARM/PXA 270 Xscale processor. Using a custom driver for the Intel 2700G graphics chip I ran a strace -e all -o loggy startx and here is my result: http://pastebin.com/620728 my xorg.conf file: http://pastebin.com/620843 Any pointers would be extremely useful. Thanks muchly!
verify that the server starts on its own, by running X -verbose :0 from the command line. If this stays up, your problem is in an app running after the server starts; otherwise it's an X server bug. Please reopen this bug once you do, preferably attaching the X log from failed server start.
Raphael, have you been able to reproduce ajax's steps?
Created attachment 5214 [details] strace -e all -o output X -verbose :0 output
(In reply to comment #2) > Raphael, have you been able to reproduce ajax's steps? Attached the output... I get a Segfault running the command ajax reccomends. How to re-open?
Created attachment 5215 [details] my xorg.conf file here my xorg.conf file as well. hope this helps :)
Looking at your xorg.conf your currently using fbdev which usually is a bad idea. What graphics card are you using?
(In reply to comment #6) > Looking at your xorg.conf your currently using fbdev which usually is a bad idea. > What graphics card are you using? an Intel 2700G I'm using a proprietary driver from them. Perhaps I should move back to trying vesa/vga?
Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status. Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.