Debian Configuration :: Can't Login As Root On Gnome / Resolve This?
Mar 9, 2011
I have squeeze with gnome. Various apps let me log in as root when needed to but if I logout as a user and try to login as root it won't let me (won't authenticate password). I had this problem before and reinstalled Debian and definitely checked for it to allow me to do this and it worked for a while after new install. Apparently some update overrode my preferences. This is a major defect and may force me to abandon Debian. I don't use root often but I don't have any use for a operating system that won't let me use it. Anyone know how to correct this. I am not interested in using a terminal on a regular basis or ever for that matter.
We have setup Squeeze a Test machine , just for some tests, without network, Internet etc. and we need to allow root login in Gnome. We've changed /etc/gdm3/daemon.conf:[security] AllowRoot=truebut still doesn't work.
I just installed Debian 6 on a server and when the server powers up, it shows me all the accounts I created in order for me to choose and login under an account, except for the root account. At the colo where the server is going, they need the root account at the login screen.
Gnome-disk-utility doesn't show filesystem type, mount point, filesystem label, size¦ of my / filesystem.
I am running Debian Squeeze using lvm2. I have two HDDs and each has one primary partition, which are used as PVs. Having two VGs, each VG has it's own PV.
There are some LVs and all of them except the LV holding the swap space are formatted with XFS. Now gnome-disk-utility shows everything about my /home LV, another LV containing a whole Ubuntu installation,¦ only the / LV (and Swap LV, but I don't know what it is supposed to show there) is/are missing nearly all information.
Otherwise the system is running perfectly well and the Debian / LV is shown normally in Ubuntu's disk-utlity, as well as all other LVs.
fdisk
Physical volume
Volume group
Volume group
lvdisplay
Logical volume
Logical volume
Logical volume
Logical volume
Logical volume
DebianCopy is a copy of my Debian installation (different fs label and UUID). DebianII (again different UUID and label) is a copy too, but there I tried out newer (testing) versions of udisks/lvm2/udev and right after the upgrade it showd everything as it should with the additional advantage of the newer udisks-version showing my VGs, but after a reboot it showed the same behaviour as before or even worse, because the information about other LVs was missing too.
In the end I even modified the fstab. Originally it contained the /dev/mapper/vgbay... entries and I replaced them with LABEL=... and finally with UUID=..., but it didn't make any difference either.
Today I upgraded my system to the Nvidia driver 340.93 and 4.2.0-1 kernel on Debian Stretch.
While I wait for the gnome login screen to pop up I get the "Oh no something has gone wrong" message.
When I log in from another terminal and execute startx , gnome initiates and starts although settings like my resolution and other xserver settings are not loaded.
From the journalctl I believe the error is located in the following section:
Code: Select allOct 06 14:23:17 DEBIAN-PC org.a11y.atspi.Registry[1692]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Oct 06 14:23:17 DEBIAN-PC gnome-session[1680]: X Error of failed request:Â BadValue (integer parameter out of range for operation) Oct 06 14:23:17 DEBIAN-PC gnome-session[1680]: Major opcode of failed request:Â 154 (GLX)
[Code] ....
I reinstalled the xorg-xserver and the nvidia drivers and I get the same behavior.
Looking for some info in order to reconfigure the gnome-session to work?
I'm trying to prevent GDM/Gnome from turning the screen off prior to login. It's current behavior, under 3.14, slowly fades the screen out and then enters DPMS mode after 10 minutes.I have zeroed out the following dconf settings, under both root and user, but the default behavior persists.
I have installed Fedora 10 on VmWare. I created another user besides root. I am able to login to that user using GNome login and i can switch to root using "su" command and perform the additional tasks.
Now, for one lab assignment, i need to login as root using GUI. But whenever i am trying to do, I am unable to do that. Is there some additional things that i have to do to login as root from GUI?
How to enable Root login...i cant copy or move something on the HDD...I have administrator rights and password for root but i cant change permissions for the HDD without login on root and root login are not allowed .
My laptop has the latest/greatest ubuntu (Linux linuxskip 2.6.32-22-generic #33-Ubuntu). I run kdm as my graphical login, but I am unable to locate the kdm-config files as mentioned in prior posts here.
So I recently upgraded from Debian 5 to Debian 6 and now for some reason I cant SSH into my server FROM my server. All of the following fail with the same error:
[URL]
They all come back with: ssh: Could not resolve hostname 127.0.0.1: Name or service not known. I never actually tried this before upgrading so I'm not sure if its caused by the upgrade, but I would like to get this fixed. Also, ping with all of the above hostnames fails as well. I can SSH in from other computers and I can SSH out from the server. For whatever reason, I cant SSH from the server to the server though.
Everything was fine yesterday, but today, the situation is the following:
When I try to login as root, using Gnome, after I enter username and password, it can do three things:
1- It brings me back to the GUI login screen again
2- Brings me to the prompt login screen (black)
3- It lets me in but I have no top or bottom navigation bars. (Sorry, cannot remember the actual names...) Sometimes I have access to a console screen, which allows me to reboot, and sometimes not, in which case I have to do a cold reboot. Not good.
The last attempt I made, I used the KDE interface and everything was fine.
I really don't understand what happened between yesterday and today, nobody but me uses this system at home and remote logins for root are disabled.
Previously, I issued a wakeonlan command to my sleeping debian (wheezy stable) server from (a mac) within my home network and then ssh in no problem. Worked like a charm. I could put it to sleep again and wake it up etc. Perfecto.
However, for some reasonI can now only ssh in once the server is rebooted (by physically switching it off then on again). If I put it to sleep then wake it, it does wake up --- however, ssh cannot then resolve the hostname:
--- >> ssh -vX bob@cerberus.local OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 debug1: Reading configuration data /Users/bob/.ssh/config debug1: Reading configuration data /etc/ssh_config debug1: /etc/ssh_config line 20: Applying options for * debug1: /etc/ssh_config line 102: Applying options for * ssh: Could not resolve hostname cerberus.local: nodename nor servname provided, or not known
I've installed newest Debian (Squeeze) and then on fresh system made instalation of VirtualBox OSE as it is written on http://wiki.debian.org/VirtualBox. I've also created virtual machine, however when I try to run it I got error message:
RTR3Init failed with rc=-1912(rc=-1912) Please install the virtual-ose-dkms package and execute 'modprobe vboxdrv' as root
I edited fstab to automatically mount my windows data partition on boot, but I screwed it up by not specifying the file system type, however that is not the problem, I was able to fix that easily. The problem was that when it failed to mount the partition, Debian automatically entered root and I guess that is to be expected in order for me to fix it, but I never configured a root password and it just gave me full root access without asking any password, not even my user password. I though that was strange so I set the root password and sure thing it asked me for the root password this time without automatically logging into root....
I then tried to lock the root account to see if it will ask me for a password or not, it did but of course I wasn't able to login as root because it was locked now and I was left with no way to access the system. I had to fix fstab from a live cd so that I can login normally as the user....
I didn't know what to search for or if that is the expected behavior if you don't set root password during installation, but it just seemed a bit strange to automatically enter root when you specifically disable root login during installation...
I've installed F12 twice now. After completing the installation and getting all the updates via YumEx, my network trouble begin after a reboot. I am not able to login as root under gnome so I can't see the services panel.
Tried to reinstall 'NetworkManager' after the fact but of course I have no network connections so I may have made the problem worse. I hate to reinstall and repeat the same troubles over again as it consumes a lot of time. I don't know where to begin.
I have three Debian systems running, along with several XP laptops, PS3 and two DirecTV systems. I use two of the three Debian systems as media servers, and the third is an older system mostly for playing around with. My home network is running fine with the following nuisance. The two newer Debian (Lenny) systems are <barney> and <mitzi>, the older is named <oscar>, running Debian Sarge 3.1. From either locally or remote login to <barney> and <mitzi> I can ssh into either of the other two systems, however when logged into <oscar> I cannot ssh by name to either of the other systems. e.g. ssh: mitzi: Temporary failure in name resolution..However, from <oscar> I can ping outside my network (e.g. ping www.google.com) with no problems.I can also ssh to the other systems via IP address, just not by name.
I've compared the /etc/ssh/ssh_config, /etc/resolv.conf, /etc/ssh/sshd_config and other files between the two systems and not seeing anything peculiar. arp, route, etc., don't show different behavior between the systems either.
I've just installed Debian Squeeze from a live CD. When I open a web browser (be it iceweasel or epiphany) and try to go to google.com, it tells me it can't resolve the host name. [Edit: They do, however, allow me to go anywhere on debian.org, minus the search feature] I also get the same error when I try to go to my website running on a local server. However, when I type the server's IP address (192.168.0.10), it goes to the website fine. Basically, any program I run that needs to resolve a host name returns an error, with the exception of the host command:
I've tried changing my DNS server IP from 192.168.0.1 (my router, configured to provide DNS) to 192.168.1.254 (my internet modem, also configured to provide DNS). That didn't help any. Then I changed my DNS server IP to the same one used by the modem, and now everything works.
I've tried googling my way out of the issue, and I've found where someone had the same issue as I've got and fixed it by adding "blacklist ipv6" to their /etc/modprobe.d/blacklist.conf file, but that didn't work for me.
So, recap: Why does resolving domain names fail for certain applications (except the "host" program) when the DNS server IP is that of my router or modem (which works fine for all of my other computers), but suddenly works when I point the computer straight to my ISP's DNS servers, and how can I permanently fix the problem?
i,m using Fedora11 since some time.... to day i hav updated my system but after updation, im unable to login my system through Gnome, but i can login by KDE as usual. now there is another problem i can,t login system throgh root account although i can access root account through terminal
Any attempt to load a webpage gives a Cannot Resolve Hostname error. i can ping [URL], but cannot load the page. However, the page will load by typing its IP address [URL] I have been trying to figure this out for days. cat /etc/resolv.conf nameserver 192.168.1.254
I just installed Debian with the latest testing iso, and I'm having problems connecting to the web via browser. I can ping hostnames (i.e. google.com, debian.org, etc.) from the terminal and it resolves just fine, but if I try to load a page from Iceweasel or Epiphany it says the page won't load because it can't resolve the hostname. Can someone tell me what I'm missing?the detail that I'm running amd64. I've checked iptables and found no entries, and for good measure I flushed it to be certain. I also checked resolv.conf but that looked normal, just a nameserver entry pointing to my home router. I'm new to Debian, but have used Linux for years, and I'm genuinely stumped. I'm sure the solution will smack me in the head for its simplicity, but nonetheless I need at least a shove in the right direction.
Last night I started my computer and loaded my CentOS 5.2 partition (Windows 7 on the other partition). I was able to login to my account, but was given a gnome error that the panel buttons (i.e. weather, cpu monitor etc) could not be loaded. I then went to restart the computer (probably not the smartest thing to do) and was given some file errors upon shutdown that were related to /dev/VolGroup00/LogVol00. After restart I was taken to a shell and ran fsck manually. It seemed to find a lot of bad blocks, so I repaired the /dev/VolGroup00 system and restarted. At this point CentOS seemed to boot normally, but upon loading of the login screen I get the error: Configuration not correct The configuration file contains an invalid command line for the login dialog, so running the default command. Please fix your configuration.
I cannot even log in as root. I get the error /usr/bin/gnome-session: error while loading shared libraries: libgnome-desktop-2.so.2: cannot open shared objects file: no such file or directory. I then went to a shell and ran: sudo yum install libgnome-desktop-2.so.2, but the package was already installed and up to date, so there was nothing to do. I am therefore stuck at this login screen with pull-down menus and tabs where I can change the configuration, add/remove users etc. So, my question is this: How do I restore my user profile so I can login....and if anyone has some insight, what caused this to happen in the first place? I should also mention, this all happened after plugging the computer into a new internet connection. No clue if that's even relevant.
is there a way to auto login as root? login in window preferences won't allow me to select rootPS before anyone starts on the me bad, I'm a programmer using it on a closed embedded system, and need to link to others software, and need to be root
I can login as root into GUI (X, openbox). But, I found some persons said that with debian one cannot login as root to desktop (GUI). viewtopic.php?f=30&t=68228#p387712 viewtopic.php?f=30&t=68228#p387737
I installed debian squeeze with linux and initrd.gz for i386 using internet. At the tasksel, I uncheck all the entries. After finishing the installation, I rebooted and installed xorg, iceweasel, iceweasel-l10n-ja, menu, menu-l10n, alsa, openbox, obconf, scim-anthy, pcmanfm, leafpad, sux, and so on. I know that root login to GUI is not so secure and should not be done.
I want to login as root in GUI just like login as normal user, how this can be achieved. i tried giving root and its password but failed. i dont want to go from terminal. just want to know how this can be done.
I can't get in as root. User is no problem but when I su or login for root I get "setgid". I also have a corrupt ssh key which is preventing sshd from starting. This seemed to happen all at once.
I run a minecraft server on my debian/gnome desktop and I need access to the files in the root folder and to the mysql folder but i cant log as root. i tried installing sudo and it didnt work. i know the su and su - but I want to change the files manually.
