07-17-2004
Starting second X session
I've installed Fedora Core 2 on a machine on my home network. X Windows (GNOME) is set up and works correctly, when I log in from the console.
However, when using Cygwin X from a different machine and trying to start an X session using startx it gives me the following error
Quote:
[root@fedora root]# startx
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at
http://wiki.X.Org
for help.
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
giving up.
xinit: unable to connect to X server
xinit: No such process (errno 3): unexpected signal 2.
That makes sense I guess because the fedora server already has an X session running at the console. I need to know how to create another X session for myself at a different computer.
I poked around about and found that the command
exec gnome-session helps somewhat in that an X session does get started, but many error messages pop up on the screen starting with:
Quote:
There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work correctly.
The Settings Daemon restarted too many times.
The last error message was:
Child process did not give an error message, unknown failure occurred
GNOME will still try to restart the Settings Daemon next time you log in.
Help would be appreciated.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi there.
How do I make the DB connection see the parameter variables passed to the unix script ? The code snippet below isn't working properly.
sqlplus << EOF
user1@db1/pass1
BEGIN
PACKAGE1.perform_updates($1,$2,$3);
END;
EOF
Thanks in advance,
Abrahao. (2 Replies)
Discussion started by: 435 Gavea
2 Replies
2. Shell Programming and Scripting
Hi,
Apologies if anyone has read my recent post on the same subject in the Linux forum, just thought actually the solution might more likely come from scripting.
Essentially, I am trying to restrict access to directories based on the user's name AND their location on a session-by-session... (3 Replies)
Discussion started by: en7smb
3 Replies
3. Solaris
I am not able to login in gnome session and java session in Sun solaris 9& 10 respectively through xmanager as a nis user, I am able to login in common desktop , but gnome session its not allowing , when I have given login credentials, its coming back to login screen, what shoul I do to allow nis... (0 Replies)
Discussion started by: durgaprasadr13
0 Replies
4. Shell Programming and Scripting
Hi
I want to do something that might sound strange.
I have a code that in written in C and is executed at startup (it's a custom process). It occasionally calls some bash scripts.
The process doesn't have any terminal associated with it.
One thing I don't know how to do is to start a... (5 Replies)
Discussion started by: alirezan
5 Replies
5. HP-UX
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies
6. Solaris
When i start a CDE session on Solaris 9 it starts the Gnome desktop for like five minutes with nothing on the screen except the background then it enters the CDE environment
and when I enter (new session) Gnome environment it takes 5 to 10 minutes then the session starts
so I wounder why it... (8 Replies)
Discussion started by: darkman
8 Replies
7. Shell Programming and Scripting
Besides 'who am i' and 'tty' what commands could be used to determine if a session is interactive as compared to a web process or cron process. Any command should work with the common unix variants. (3 Replies)
Discussion started by: jgt
3 Replies
8. Solaris
what is the difference between desktop session and console session in solaris
as i am wondering we use option -text for the former and -nowin for the later (1 Reply)
Discussion started by: kishanreddy
1 Replies
9. UNIX for Dummies Questions & Answers
e.g.
File name: File.txt
cat File.txt
Result:
#INBOUND_QUEUE=FAQ1
INBOUND_QUEUE=FAQ2
I want to get the value for one which is not commented out.
Thanks, (3 Replies)
Discussion started by: Tanu
3 Replies
STARTX(1) General Commands Manual STARTX(1)
NAME
startx - initialize an X session
SYNOPSIS
startx [ [ client ] options ... ] [ -- [ server ] [ display ] options ... ]
DESCRIPTION
The startx script is a front end to xinit(1) that provides a somewhat nicer user interface for running a single session of the X Window
System. It is often run with no arguments.
Arguments immediately following the startx command are used to start a client in the same manner as xinit(1). The special argument '--'
marks the end of client arguments and the beginning of server options. It may be convenient to specify server options with startx to
change on a per-session basis the default color depth, the server's notion of the number of dots-per-inch the display device presents, or
take advantage of a different server layout, as permitted by the Xorg(1) server and specified in the xorg.conf(5) configuration. Some
examples of specifying server arguments follow; consult the manual page for your X server to determine which arguments are legal.
startx -- -depth 16
startx -- -dpi 100
startx -- -layout Multihead
To determine the client to run, startx first looks for a file called .xinitrc in the user's home directory. If that is not found, it uses
the file xinitrc in the xinit library directory. If command line client options are given, they override this behavior and revert to the
xinit(1) behavior. To determine the server to run, startx first looks for a file called .xserverrc in the user's home directory. If that
is not found, it uses the file xserverrc in the xinit library directory. If command line server options are given, they override this
behavior and revert to the xinit(1) behavior. Users rarely need to provide a .xserverrc file. See the xinit(1) manual page for more
details on the arguments.
The system-wide xinitrc and xserverrc files are found in the /etc/X11/xinit directory.
ENVIRONMENT VARIABLES
DISPLAY This variable gets set to the name of the display to which clients should connect. Note that this gets set, not
read.
XAUTHORITY This variable, if not already defined, gets set to $(HOME)/.Xauthority. This is to prevent the X server, if not
given the -auth argument, from automatically setting up insecure host-based authentication for the local host.
See the Xserver(1) and Xsecurity(7) manual pages for more information on X client/server authentication.
FILES
$(HOME)/.xinitrc Client to run. Typically a shell script which runs many programs in the background.
$(HOME)/.xserverrc Server to run. The default is X.
/etc/X11/xinit/xinitrc Client to run if the user has no .xinitrc file.
/etc/X11/xinit/xserverrc Server to run if the user has no .xserverrc file.
SEE ALSO
xinit(1), X(7), Xserver(1), Xorg(1), xorg.conf(5)
X Version 11 xinit 1.3.2 STARTX(1)