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 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.
View 14 Replies View RelatedJust for some testing on a test non-productive machine, how to allow Gnome login by root user on squeeze?
View 8 Replies View RelatedBefore I ask I know what I'm asking is not recommended.
On Lenny It was possible to change the boot login to permit logins as root
I can't find how to do that since I installed Squeeze.
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.
View 11 Replies View RelatedI am trying to login as root but i end up with an error that says: su: Authentication failure
View 10 Replies View RelatedGnome-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.
org.gnome.desktop.session idle-delay
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout
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 .
View 10 Replies View RelatedMy 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.
View 3 Replies View RelatedIs there any way o enable root login for Gnome in Fedora 14 ?
View 6 Replies View RelatedEverything 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.
The systems is CentOS 5.3 with SELinux enforced.
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,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
View 13 Replies View RelatedLast 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
View 6 Replies View RelatedI 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.
View 14 Replies View RelatedI 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.
View 13 Replies View RelatedI 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.
View 1 Replies View RelatedHaving successfully installed SANE and gotten a scan from my ancient Mustek scanner, I thought I had it setup. But that was running in the root terminal window. When I try to run xscanimage from GIMP in my normal user account it doesn't start up. Running xscanimage in a normal terminal it says it can't see any scanners. Yes, I added my user account to the scanner group. What else needs to be done to let a normal non-root user access the scanner?
View 4 Replies View RelatedSince upgrading my Debian/unstable amd64 installation a few days back I can no longer log in as either root or user, whether to SDDM, via the console, or via ssh. When trying with the console, I can see the login message flash briefly on the screen, before the console resets itself.
I can boot into recovery mode, and examine log files. I enabled systemd debug logging and, amid reams of messages, these seem the most pertinent:
Sep 25 02:24:43 cooler systemd[1]: Received SIGCHLD from PID 937 (login).
Sep 25 02:24:43 cooler systemd[1]: Child 937 (login) died (code=killed, status=6/ABRT)
I would like to know how can Debian prompt my user instead of the root account after booting.
View 2 Replies View RelatedI installed Debian 5.0.2 about a year ago, my first encounter with Debian and first serious look at Linux. I never got it right. Some software wouldn't work after installing. This week I decided to just start all over. I installed Debian 5.0.5 on a second disk. I seems to be better. Software that failed before works now!
Problem 1:
I ended up with two possible boot up choices in GRUB, but they both run 5.0.5 w/ Gnome. Why two? How do I know which to keep and how do I get rid of the other?
Problem 2:
Previously, I could boot into a command console by interrupting the normal boot. I don't get that chance now. It goes right to Gnome. I can't boot as root in Gnome. How do I get on as root?
I have a "time-server". It's sending time to different devices through different ports/protocols. The problem is that it has no operator and that makes some extra difficulties.
Now when i try to start it using terminal Code: Select allsudo ./myprogram works fine and
Code: Select all./myprogram doesn't work.
It is so because without sudo i have no access to ports. As a result If i add my program to System->Preferences->Startup Applications it has the same problem. So i need to start it as root, auto-start, right after auto-login to system but without entering password cause nobody will do it.
Also I need to start ntpd but it also asks password sometimes I've tried googles but it offer a few ways with entering password that isn't suitable for me or writing some scripts/changing system files but with no example I'm afraid to break it all. So is there a way to start Myprogram and NTPD as root with no password entering?
My system is Debian 6.0.10 Squeeze, Kernel 2.6.32-5-686
Installed Debian 8.2 a while back, and I've been having issues with getting the machine to suspend correctly. If I try to put it to sleep when logged in to my regular user account the screen just goes black and then the computer hangs. However if I put it to sleep as root everything works fine. I do this by running this command (as root):
Code: Select allsystemctl suspend
What can I do about this? Worked fine on Debian wheezy..
Btw, just found this in the dmesg log. Connected perhaps..?
Code: Select all[Â Â 6.863018] ACPI Warning: SystemIO range 0x00000000000018e0-0x00000000000018ff conflicts with OpRegion 0x00000000000018e0-0x00000000000018ef (\_SB_.PCI0.SBUS.SMBI) (20140424/utaddress-258)
[Â Â 6.863028] ACPI:
If an ACPI driver is available for this device, you should use it instead of the native driver
I think my root drive is 100% full causing strange problems with my video server. What steps can I use to see what's taking up the room on the drive and perhaps identify files that can safely be deleted?
Code: Select allroot@lenny:/# df -h
Filesystem        Size Used Avail Use% Mounted on
/dev/sda2Â Â Â Â Â Â Â Â Â 55GÂ Â 53GÂ Â Â 0 100% /
udev           10M   0  10M  0% /dev
tmpfs          793M 1.1M 792M  1% /run
[code]...
For my dissertation I created a debootstrap install of Lenny. When I boot this system I just can login with root without a password. When I want to ssh this machine with the debootstrap install I can't just login with root. I'm asked for a password which I don't have.
So I created one with passwd root and after that I can connect to the machine with ssh and the given password. But the machine still logs in with without a password.