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.
Having installed Debian 7 on an old machine from a Liinux Format Magazine DVD I was unable to log in as a specific user. I can login as root and use useradd etc but when I logout of root I still cannot login as a user and nor will the machine accept my root password. I have to shutdown and reboot to get back into root. I'm using O'Reilly's Linux Pocket Guide from 2004 for the commands. Could it be that things have changed?
I have a network set up that has been working for around a year with no problems but has now developed a login problem. The system was set up with a main server with all users on it and another PC located elsewhere that people could log onto using there personal login and password that then gained access to the account on the main server. This remote PC has now got the problem. When you try to log onto an account it comes up with the message "your session has lasted less than 10 seconds. If you have not logged out yourself this could mean there is a installation problem or that you are out of disk space."
Error message says that no profile for the user can be found and it couldnt create per-user gnome configuration directory. I can log on as root onto the remote PC as it is obviously a local account but all the account on the main server are not accessible. From the root account I can see that the connection to the server is OK and I can actually log into the accounts on the server using the failsafe session so the physical network is OK.
I never built or designed this set up and to be honest I normally work with windows so its all a bit strange to me. Both PC's run Centos 5. I have checked the messages log and there doesnt seem to be any indication of a problem. Just that it stopped connecting from the remote PC. The accounts are all active on the main server itself and have no problems being accessed.
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.
Since 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: Received SIGCHLD from PID 937 (login). Sep 25 02:24:43 cooler systemd: Child 937 (login) died (code=killed, status=6/ABRT)
Debian 8/Cinnamon fresh install. /home is being shared with two other OS's, Mint and openSUSE. At the login screen I enter my user name and password and the screen blacks for 1-2 seconds and comes back asking for user name and password. I can login as root. As root I can launch the Group & Users GUI and attempt to set the user's password, and pressing the 'change' button does nothing obvious.
I can set the user's password in a terminal, which reports success. I tried to switch users and login with the changed password and I get the same failure. If I try to login with the original password I get an incorrect password error, suggesting that the password is being processed properly and the problem is elsewhere.
On previous installs with Mate and the default desktop (Gnome) I didn't have this problem. So, the questions are: Is it Cinnamon? Is it an unlucky chance bad install? Config files are typically in /home, which is being shared with Mate and KDE, is this the problem?
on my netbook I've tried to make possible for my user to shutdown without needing a password. battery could run low when I'm not in front of it. Editing sudoers has allowed my user to shutdown the system, but Gnome still prompts me for the root password whenever root is logged in too. That's usually the case, because to avoid entering the root password multiple times whenever I need elevated privileges and not wanting to cache the root password, I keep a Root Terminal always open.
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.
Suddenly Debian started rejecting my user pw and I have to login as root. Perhaps this is a coincidence, but this started when I re-booted after adding Russian keyboard layout in etc/default/keyboard. The Russian keyboard added successfully.
Being logged in as root, renewed the pw of my user account (actually assigned the same as wes previously), got confirmation the the pw has been changed. Reloaded. Yet it keeps complaining that the pw is wrong.
I'm using Debian Jessie Cinnamon right now. I've got 1 user account on my machine--fred--as well as root, of course. "fred" is an administrator, and many times that is enough for root priviledges, for example, I can install packages via apt or dpkg. However, I cannot access "Users and Groups", or install packages via GDebi, with my password. For that, I have to have the root password.
I know that it is possible to let the admin account handle everything and not even need root--for example, Mint and (I believe) Ubuntu do it this way. I don't know how, though.
Code: Select allgroups fred fred : fred cdrom floppy sudo audio dip video plugdev netdev lpadmin scanner bluetooth
I did disable the root account by Code: Select allsudo passwd -l root to see if it would make any change. Nothing different happened except that I now can't use GDebi or access "Users and Groups" since the root account and therefore password is inactivated. Not a big deal to get it back, though.
I have lost my password for my root and for my user account.
Code: Select alluser@debian:~$ su Password: su: Authentication failure user@debian:~$ su Password: su: Authentication failure user@debian:~$ su
I have just installed a gust debian 8 on debian 8 host in virtualbox, and when i wonted too login as su/root on the host there where no login possible, is there a way to regain the root password for the host?
I have a very strange problem.ometimes, yes sometimes not all the time, I get a Destination Host Unreachable when I ping a computer on my network. If I switch to root using su I can ping that same computer. Here is a screen shot:
joseph@laptop:~$ ping 192.168.1.14 PING 192.168.1.14 (192.168.1.14) 56(84) bytes of data. From 192.168.1.9 icmp_seq=2 Destination Host Unreachable
I upgraded a Guruplug Display machine running Lenny to Squeeze. It's running Linux on a MicroSD device, running an ARM-cpu.
# uname -a Linux gplugD 2.6.29 #1 Wed Feb 16 17:59:04 IST 2011 armv5tejl GNU/Linux yeri@gplugD ~ $ cat /etc/debian_version 6.0.1
However, after rebooting, every non root user was unable to access anything related to the net.This means, DHCP failed to auto start, ntp is giving errors, etc
# ntpq -p localhost: timed out, nothing received ***Request timed out
Mar 27 06:07:44 localhost ntpd: ./../lib/isc/unix/ifiter_ioctl.c:348: unexpected error: Mar 27 06:07:44 localhost ntpd: making interface scan socket: Permission denied Mar 27 06:07:44 localhost ntpd: Too many errors.† Shutting up.
gplugD ~ # ping 220.127.116.11 -c 1 PING 18.104.22.168 (22.214.171.124) 56(84) bytes of data. 64 bytes from 126.96.36.199: icmp_req=1 ttl=58 time=42.1 ms
I've got to purge GNOME from Jessie old netbook of my mom at least think so. It just run out of free space on 8Gb SSD. After upgrade GNOME is not accessible. System is stuck on logon 'GDM' screen without possibility to login for any user including 'root'. Here [URL] .... are given instructions on how to purge GNOME from installed system and install 'xfce' instead. Is this the right way to do it? And do I have to reboot netbook into 'Recovery mode' for it? URL warns about possible system crash during changeover. That is highly unwanted!here [URL] ....
After fossicking around I can not find anything around that I can invoke in a terminal to configure settings in network-manager. The applet(?) on the task bar doesn't ask for a login, so options are grey/grayed out. The "program" in the applications menu is similarly grey/grayed out.
If it was a once off, then I suspect that it would be simple as login as root to start X, but I have a series of config files to edited each time of their initial use. also, there is the ongoing problem of vpn target switching.
woops; wheezy with xfce4 and everything is uptodate.
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.
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.
I am using debian squeeze server with asterisk 1.6 installed and configured.my problem is non root users need to access the server using ssh and restart asterisk server after making changes in asterisk configuration files.As of now i am giving root username/password for this process (i know it is not at all a good idea) .now how can i create a username and configure it which can only access and modify asterisk configuration files and restart asterisk server without any other privileges.
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: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Oct 06 14:23:17 DEBIAN-PC gnome-session: X Error of failed request:¬† BadValue (integer parameter out of range for operation) Oct 06 14:23:17 DEBIAN-PC gnome-session: Major opcode of failed request:¬† 154 (GLX)
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 just installed linux mandriva 2009. i set password for root and created a user account. when i try to login as root, after logging out as user, it does not allow me and gives the error "root logins are not allowed". even it does not show the root account. if i try to go to root from konsole terminal using su root, it allows to enter as a root but when i try to start the GUI with startx it gives error.not sure what to do and why i can't see my account in GUI mode
I am afraid to ask with so many things changing around in each new release.Where would one add a custom script to execute when logging and shutting down in into a user profile like /home/test or /root ?would this be rc.local?