unable login via GUI but can login via Putty (command line)
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
unable login via GUI but can login via Putty (command line)
Hi all,
I am able to login via putty to a fedora 10 workstation.
But when i try to login via physical screen connected to workstation, it just gives me a blank screen and i cant see any options to enter username and passwd. How do i get the physical GUI to work.
Code:
[vct@console-0124 ~]$ who -r
run-level 5 2011-06-03 11:25
below is the ps -ef output for X
Does the numlock light work on the keyboard? Is the monitor plugged in? I know they're simple questions, but, they are the only things I can think of for a completely blank screen at the computer itself...
When you first boot up, edit the command line from the grub menu and add 3 to the end.
Then when you have logged in (command line) issue the command "startx".
If there is an issue with the gui it will show up then. Repeat the error here.
I changed /etc/inittab to 3 and rebooted the workstation and startx gives the following output and stays there forever.
Code:
[root@console-0124 ~]# startx
xauth: creating new authority file /root/.serverauth.4064
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-164.2.1.el5 x86_64
Current Operating System: Linux console-0124.local 2.6.27.41-170.2.117.fc10.x86_64 #1 SMP Thu Dec 10 10:36:29 EST 2009 x86_64
Build Date: 23 November 2009 05:30:50PM
Build ID: xorg-x11-server 1.5.3-18.fc10
Before reporting problems, check http://wiki.x.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: Mon Jun 6 13:10:13 2011
(==) Using config file: "/etc/X11/xorg.conf"
imsettings information
==========================
Is DBus enabled: yes
Is imsettings enabled: yes
Is GTK+ supported: no
Is Qt supported: no
DESKTOP_SESSION:
DISABLE_IMSETTINGS:
IMSETTINGS_DISABLE_DESKTOP_CHECK:
DBUS_SESSION_BUS_ADDRESS: unix:abstract=/tmp/dbus-SnuIadpHpE,guid=2e7ae73f76d3426060f2ff944ded09f8
GTK_IM_MODULE: gtk-im-context-simple
QT_IM_MODULE:
XMODIFIERS: @im=imsettings
IMSETTINGS_MODULE: none
Started none
** Message: another SSH agent is running at: /tmp/ssh-chpYQe4292/agent.4292
Window manager warning: Failed to read saved session file /root/.config/metacity/sessions/10528eea413d64ecb9130738021763842500000042920022.ms: Failed to open file '/root/.config/metacity/sessions/10528eea413d64ecb9130738021763842500000042920022.ms': No such file or directory
Acceleration key: disabled
XSETTINGS manager support is explicitly disabled.
06/06/2011 01:10:19 PM Autoprobing TCP port
06/06/2011 01:10:19 PM Autoprobing selected port 5900
06/06/2011 01:10:19 PM Advertising authentication type: 'No Authentication' (1)
06/06/2011 01:10:19 PM Advertising security type: 'No Authentication' (1)
** (gnome-power-manager:4365): WARNING **: This machine is not identified as a laptop.system.formfactor is desktop.
W: main.c: This program is not intended to be run as root (unless --system is specified).
Failed to play sound: Not available
Traceback (most recent call last):
File "/usr/bin/sealert", line 108, in <module>
from setroubleshoot.analyze import *
File "/usr/lib/python2.5/site-packages/setroubleshoot/analyze.py", line 43, in <module>
from setroubleshoot.avc_audit import *
File "/usr/lib/python2.5/site-packages/setroubleshoot/avc_audit.py", line 54, in <module>
my_context = AvcContext(selinux.getcon()[1])
OSError: [Errno 22] Invalid argument
(gnome-settings-daemon:4340): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
^C** Message: Got disconnected from the session message bus; retrying to reconnect every 10 seconds
waiting for X server to shut down gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
** ERROR **: couldn't get D-Bus connection: Failed to connect to socket /tmp/dbus-SnuIadpHpE: Connection refused
aborting...
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-SnuIadpHpE: Connection refused)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-SnuIadpHpE: Connection refused)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-SnuIadpHpE: Connection refused)
The application 'gnome-settings-daemon' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
I have another workstation identical to the one where i am having trouble in logging into GUI. (both have same OS fedora core 10)
I am posting few commands from both to see if that helps
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.