You are not logged in.
[~] ps auxc |grep 'X'
root 17687 4.8 2.5 37544 26196 tty7 SLs+ 13:54 0:16 X
root 17689 0.0 2.5 37544 26196 tty7 SL+ 13:54 0:00 X
No matter if I start gnome/openbox/twm by startx/gdm I have two X working, I don't know where the second one is, ctrl+alt+f8 doesnt show anything. Is this normal, or have I done something wrong?
My xorg.conf: http://rafb.net/p/2ZyYV143.html
[~] Xorg -version
X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: UNKNOWN
Current Operating System: Linux airship 2.6.20-ck #1 SMP PREEMPT Sat Apr 21 15:02:32 IST 2007 i686
Build Date: 08 April 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Sorry for my english, i'm still learning.
Offline
I do not know if this is "normal" but I do not think is something you have done wrong. Both seem to have been started by root.
My guess is that some process you run my start the second.
R
Offline
this has been happening to me as well since fglrx 8.36 (my comp has a firegl v5250, this does not occur when using the vesa driver). i meant to post here about this to ask if others were experiencing the same thing but forgot to. anyway i've just been using a script that i have run after x starts to kill the second x process
Offline
Yes, it's something connected with fglrx, switching to opensource driver soloved problem, but is there posibility to make it work right with fglrx?
Offline
I can also confirm this, I'm on fglrx 8.36.5 too.
Offline
bugs.archlinux.org
Offline
Is it useful to file bugs for a closed source driver? Are the arch developers able to fix stuff like this or are we dependent from ati developers?
Offline
I was experiencing this as well and couldn't figure it out. X was also constantly utilizing 5-15% of my cpu. I installed the open source ati driver and it fixed both issues. This was also apparently preventing cpufreq from scaling my cpu. Thanks for the heads up!
Last edited by dejitarob (2007-05-09 15:44:49)
We do not want a world in which the guarantee that we will not die of starvation is bought by accepting the risk of dying of boredom. -Raoul Vaneigem / Students for a Human Society
Offline
Any news in this issue?
Offline
I just noticed I have two X processes also, running the latest catalyst drivers (7.11-2).
Did anyone ever file a bug report?
Offline
I've still got that same issue too, killing the useless-"doing nothing" X process makes it defunct. Maybe a bug report would be appropriate. I haven't yet found the time to file one though.
Last edited by Ramses de Norre (2007-12-16 17:35:38)
Offline
just pointing out that I, too, also have to X's running.
And i'm using fglrx driver.
Offline
yes same here, hard to say when this phenomena started.
Offline
I went ahead and filed a bug report.
http://bugs.archlinux.org/task/8960
If anyone has more information to add I would put it there.
Offline
It seems to be fixed with the latest catalyst (7.12-2) here.
Offline
I have the same problem here with catalyst 8.1...???
It does not seem to be fixed.
Offline
it came back it seems with 8.1
Offline
This is really anoying! Is this a arch specific problem or a catalyst problem ?
I did a bugreport as it seemed there was none... http://bugs.archlinux.org/task/9354
Please vote for it if you have the same problem, so it get fixed soon.
Last edited by May-C (2008-01-27 10:30:55)
Offline
This is really anoying! Is this a arch specific problem or a catalyst problem ?
I did a bugreport as it seemed there was none... http://bugs.archlinux.org/task/9354
Please vote for it if you have the same problem, so it get fixed soon.
If you'd read the thread you'd have seen that someone told us he made a bugreport four posts above yours... In that report it is stated that the problem is with the closed source driver, so you should direct your complaints towards ATI/AMD.
Offline
Ups sorry was not aware of that... I did even vote for the bug.
Last edited by May-C (2008-01-27 12:03:35)
Offline