LinuxQuestions.org - New User has X Server Running on Display 0 already

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - New User has X Server Running on Display 0 already (https://www.linuxquestions.org/questions/linux-newbie-8/new-user-has-x-server-running-on-display-0-already-211950/)

New User has X Server Running on Display 0 already

After adding a user, and working with that user for some time now, I now try to log in as that user and I get a 'init 5' formated message:

"There already appears to be an X sever running on display :0. Should I try another display number? if you answer no, I will attempt to start the server on :0 again. (You can change consoles by pressing Ctrl-Alt plus a function key, such as Ctrl-Alt-F7 to go to console 7. X servers usually run on consoles 7 and higher.)
<Yes> <No>"

It does not respond with an Ctrl-Alt function key, but I can use the arrows to choose 'Yes' and 'No'.
with either choice, I can't get past this point with this user now.
I can login as root though.
It appears that I need to redefine what display number is being used when login in as this user. Is there a way to adjust this?

Any help would be wonderful!

Thanks
-Tim

Try booting into command line (init 3)rather than a display manager (init 5) and starting the gui with the command startx after logging in as that user.

Edit /etc/inittab and and change the default to the number that corresponds toFull multiuser mode. Here is the pertinent portion of my file:

Code:

# Default runlevel. The runlevels used by RHS are:

#  0 - halt (Do NOT set initdefault to this)

#  1 - Single user mode

#  2 - Multiuser, without NFS (The same as 3, if you do not have networking)

#  3 - Full multiuser mode

#  4 - unused

#  5 - X11

#  6 - reboot (Do NOT set initdefault to this)

#

id:3:initdefault:

Here's where my newbieness really shows!
I'm not sure how to boot into command line vs the standard login screen.

use kwrite or nano whatever you like go to /etc/inittab and
#Default Runlevel
id:5:initdefault change the 5 to 3 and save

You haven't mentioned your distribution, so I don't know what editors you have at hand.

Open an x terminal and become root, launch your editor from that, open /etc/inittab, change default, and save, then close the x terminal.

Code:

Sat Jul 31 08:06 PM fancy@uilleann ~ $ su -

Password:

Sat Jul 31 08:06 PM root@uilleann ~ # nano /etc/inittab

<some snippage of extraneous stuff>

# Default runlevel. The runlevels used by RHS are:

#  0 - halt (Do NOT set initdefault to this)

#  1 - Single user mode

#  2 - Multiuser, without NFS (The same as 3, if you do not have networking)

#  3 - Full multiuser mode

#  4 - unused

#  5 - X11

#  6 - reboot (Do NOT set initdefault to this)

#

id:3:initdefault:

<more snippage of extraneous stuff>

Now, either re-boot or command (as root)

init 3

Made that adjustment to the inittab file. I then attemped to log in as that user and it wont let me passed the password prompt. Although it doesn't give me an error after typing in the password, it acts as though the authentication has failed. Wierdness.
I wanted to see if this is the case with any additional user on this box, so I've just added a new user and then tryed to log with that.
This X Server/Display 0 problem is acutally happening on all user accounts other than Root. And adjusting the inittab setting to multiusermode doesn't seem to make a difference.

Oh yea, I'm using FC1

i did.

noticed something though in the startup while in init 3.
There is an error in the /etc/security/console.perms stating it's having trouble with the class <v41> can someone send me what the permission definitions are supposed to look like, if not the whole file.

<console> 0600 <v4l> 0600 root

Here is my file:

Code:

# /etc/security/console.perms

#

# This file determines the permissions that will be given to priviledged

# users of the console at login time, and the permissions to which to

# revert when the users log out.



# format is:

#  <class>=list of regexps specifying consoles or globs specifying files

#  file-glob|<class> perm dev-regex|<dev-class> \

#    revert-mode revert-owner[.revert-group]

# the revert-mode, revert-owner, and revert-group are optional, and default

# to 0600, root, and root, respectively.

#

# For more information:

# man 5 console.perms



# file classes -- these are regular expressions

<console>=tty[0-9][0-9]* vc/[0-9][0-9]* :[0-9]\.[0-9] :[0-9]

<xconsole>=:[0-9]\.[0-9] :[0-9]



# device classes -- these are shell-style globs

<floppy>=/dev/fd[0-1]* \

        /dev/floppy/* /mnt/floppy*

<sound>=/dev/dsp* /dev/audio* /dev/midi* \

        /dev/mixer* /dev/sequencer \

        /dev/sound/* /dev/beep

<cdrom>=/dev/cdrom* /dev/cdroms/* /dev/cdwriter* /mnt/cdrom*

<pilot>=/dev/pilot

<jaz>=/mnt/jaz*

<zip>=/mnt/pocketzip* /mnt/zip*

<ls120>=/dev/ls120 /mnt/ls120*

<scanner>=/dev/scanner /dev/usb/scanner*

<rio500>=/dev/usb/rio500

<camera>=/mnt/camera* /dev/usb/dc2xx* /dev/usb/mdc800*

<memstick>=/mnt/memstick*

<flash>=/mnt/flash*

<diskonkey>=/mnt/diskonkey*

<rem_ide>=/mnt/microdrive*

<fb>=/dev/fb /dev/fb[0-9]* \

    /dev/fb/*

<kbd>=/dev/kbd

<joystick>=/dev/js[0-9]*

<v4l>=/dev/video* /dev/radio* /dev/winradio* /dev/vtx* /dev/vbi* \

      /dev/video/*

<gpm>=/dev/gpmctl

<dri>=/dev/nvidia* /dev/3dfx*

<mainboard>=/dev/apm_bios



# permission definitions

<console>  0660 <floppy>    0660 root.floppy

<console>  0600 <sound>      0600 root

<console>  0600 <cdrom>      0660 root.disk

<console>  0600 <pilot>      0660 root.uucp

<console>  0600 <jaz>        0660 root.disk

<console>  0600 <zip>        0660 root.disk

<console>  0600 <ls120>      0660 root.disk

<console>  0600 <scanner>    0600 root

<console>  0600 <camera>    0600 root

<console>  0600 <memstick>  0600 root

<console>  0600 <flash>      0600 root

<console>  0600 <diskonkey>  0660 root.disk

<console>  0600 <rem_ide>    0660 root.disk

<console>  0600 <fb>        0600 root

<console>  0600 <kbd>        0600 root

<console>  0600 <joystick>  0600 root

<console>  0600 <v4l>        0600 root

<console>  0700 <gpm>            0700 root

<console>  0600 <mainboard>  0600 root

<console>  0600 <rio500>    0600 root



<xconsole> 0600 /dev/console 0600 root.root

<xconsole> 0600 <dri>            0600 root

By retyping in these two lines:

<v4l>=/dev/video* /dev/radio* /dev/winradio* /dev/vtx* /dev/vbi* \
/dev/video/*
AND
<console> 0600 <v4l> 0600 root

Everything is now working.

Thanks you your help.

same problem: X server running on display 0 already

I had the same problem after upgrading from Fedora Core 1 to Fedora Core 2. I changed the run level from 5 to 3 and now when I login, I can't type anything. I'm prompted with a login:, but I'm stuck there. I'm also having the following issue, but since I can't type - I can't fix it:

http://www.linuxquestions.org/questions/history/188684

Thanks,

Matt

Re: same problem: X server running on display 0 already

Quote:

Originally posted by mraible
but since I can't type - I can't fix it:

:confused: How did this message get posted then? Did you hire a secretary??:rolleyes:

I entered the question using my PowerBook.

Not using your keyboard at all? I am still very confused.

Can you get this far?

Code:

Fedora Core release 1 (Yarrow)

Kernel 2.4.22-1.2115.nptl on an i686



uilleann login: root

Password:

Last login: Sat Aug  7 16:13:47 on tty1

You have new mail.

Mon Aug 09 05:50 PM root@uilleann ~ #

If so, what happens if you type this:

nano /etc/security/console.perms

Back where I started from

OK, I'm back to a working keyboard - after using my rescue cd to change the value back from 3 to 5. I'll try to revert back to 3 and see what happens. Any idea why changing it to 3 could cause my keyboard not to function? By "not functioning", I mean I get prompted with a login, but nothing happens when I type.

Linux users are as dumb as computers are, they need to be told exactly what you did and the exact result of you doing it. We are very poor at intepreting "I can't type" at any other meaning than "I don't know how to press the keys on the keyboard." :p

How to get good answers with your questions about Linux

You aren't using some oddball keyboard or one with some broken connections then? Nothins shows up when you type?

If so, I would edit your needed files from the rescue environment, then, since the keyboard works from that.