I just installed Fedora 12 on a laptop. I changed the default shell on the root account to /bin/tcsh and changed the runlevel to 3 and then rebooted. Now I can't login into the root account: it returns me immediately to the login prompt and I can't see any error message (the screen is cleared).Why is this happening?Can I boot into some sort of safe mode so I can undo my changes to the /etc/inittab and /etc/passwd file?I tried booting with a Live CD with the intention of mounting the filesystem and making the changes, but the new filesystem is a LVM and it won't let me mount it (or I don't know how to mount a Logical Volume).
My OpenSUSE 11.2 is working fine as samba server, no problems, but I have a problem with KDM.My default init runlevel is set to 5 and every time I try to login at KDM (KDE4), the monitor goes black and returns to the login screen.If I hit Ctrl+Alt+F1 to go to console and start /usr/sbin/console-kit-daemon manually, press Ctrl+Alt+F7 to return to KDM login, everything is fine.What do I have to do to fix this issue?
Every account every option I try. when I login, it just cycles back to the login screen. I have attempted to do a repair install, but to no avail. it happens when I try to boot normally or if I boot into failsafe.
The graphical login screen is loaded just fine. Though very shortly after (a moment after the loading screen could be seen) it crashes back to the graphical login. And that happens no matter what wm I'm trying - gnome, kde3, kde4, e16, e17, even twm.
It happened after the logout after a zypper up yesterday morning. Looking through the list of what packages were upgraded (two machines, both last zypper up'ed last Sunday, checked on the second one after the problem with the first one), the only packages which might be responsible are kwin or qt4.
The graphics card seems to be fine (NVidia 9600), as it happens whether or not I use nv or the propietary driver. Also tried reinstalling it from the repo as well as using the binary blob from NVidia. Has been tested on Windows and games are running fine there, so it shouldn't be the card.
What is strange, is that when calling upon sax2 -r from runlevel three, the initial screen loads nicely, but sax2 crashes back to the cli once one presses 'Change Configuration'. No error messages are being printed.
Any pointers on how I can narrow down the cause (and get it fixed)?
On a Debian 5.0.8 I have a problem with OpenSSH server (sshd): when connecting to it from another host there is always a 10 seconds delay before sshd gives login prompt to the client. After the connection is established the communication goes on without any interruption. This long delay started to happen a few months ago and sshd_config was not changed at that time.
Here is a short description of the conversation between the putty client (on MS Windows) and sshd: - putty client starts connection to sshd - 10 s delay - sshd returns "login as:" - user types username in putty window - sshd returns "password:" - user types password in putty window - sshd returns MotD and shell prompt
Here is a short description of the conversation between the OpenSSH client (on a Debian 6) and sshd: - client does "ssh user@host.foo.bar" - 10 s delay - sshd returns "Password:" - user types password - sshd returns MotD and shell prompt
I tried connecting from: - local host - NO DELAY - a host on the same subnet - delay exists - a host on another subnet - delay exists
I've found the following suggestions but to no avail (of course I restarted sshd after changing its configuration): - on server put "UseDNS no" at the end of /etc/ssh/sshd_config - in /etc/hosts on the server define mappings between IP addresses and host names for the ssh clients - on client use "GSSAPIAuthentication no" in /etc/ssh/ssh_config
i am having a boot problem with opensuse.i installed a theme named suse-elegant under personal settings(configure desktop)-system administration-login screen.
i had also added vbox users(i ticked vboxusers) under yast-security and users-user and group management-edit-details to make virtual box work.
i want to check that installed theme so i restarted my laptop.after the restart opensuse taking too long time to boot
note:the login theme also not working.
after the boot i restored defaults in login screen themes.it is also not working.
i don't know which cause this problem(vboxusers or login theme).i am also seeing a root user has been added in my login area.i tried opensuse failsafe also.
I have installed VirtualBox and setup a Windows Vista host, initially with a .vdi of 10gb. That filled up quickly, so I added another 20gb secondary partition, after first trying to allocate a .vdi to a SCSI controller. Configured the drive in Windows (Computer Management), and all seemed ok. I shutdown VB, and rebooted my Linux host (openSuse 11.3). Now I keep bouncing back to the login screen, and can't login to Linux KDE, but can login to a console.I do have the following info:
I did see a message before, that I don't see anymore, that said it could not start NFS services due to missing entry in fstab. Another I'm seeing now is it couldn't start the avahi-daemon, no space left on device. This is odd, since I have a 200GB drive, with half of it left, only max 30GB set to VB. Here's my df -k output:
/dev/sda6 Use% is 100% devtmpfs Use% is 1% tmpfs Use% is 1% /dev/sda7 Use% is 46%
So root "/" is mounted on /dev/sda6, which looks like it could be a problem, but why would this suddenly be a problem after working with VirtualBox? Could this be a matter of just freeing up space on /dev/sda6? Like the /tmp folder that's under "/"?
I was expecting a gnome window login prompt after installation was done. Instead I am getting a command line login prompt.Am I right expecting a X-Windows login prompt?I login successfully, but I am dropped into a shell (bash) instead of a gnome desktop.
The hardware I am installing on: Intel Core 2 Duo 2 GB Ram 137 GB HD Radeon X1300/X1550 Series Monitor - Dell E156FP (max res 1024x768 60 Hz)
Whenever I logoff my workstation, I log back on and my desktop doesn't come back. Only the mouse pointer and the wallpaper show up. The panel and the shortcuts don't show. I have to power off using the power button, then power back on to fix.
Main reason I am using openSUSE currently is because my Windows system's went bad. I haven't been able to easily restore and will probably have to do clean windows install. I want to make sure my entire openSuse system (application/OS setting/etc) backup so I can easily restore of it fast. Since this type of back takes awhile, I would preferably like do this while I am still logged into SUSE. I am where to disk cloning thing like clonezilla, but looks like I would need turn of my system entirely to get this done.
Currently my SUSE root and home are in a partition with another NTFS partition on my hard drive. I really don't want to use 'dd' to clone the entire hard disk. I would much rather store of required partitions in other locations. Hopefully, there is easy to get this done without too much of effort and time.
My FC12 laptop won't boot. During the attempted boot, after blue/white progress bars finish displaying on the bottom of screen, nothing more seems to happen. The screen isn't totally blank in that I seem to have a text cursor and keyboard input is displayed. But, no prompt, no login prompt, X isn't running, etc. If I hit ESCduring boot, it displays the boot messages and the boot sequence stops after "Starting atd". I'm not sure if it's related, but I had previously experimented with creating a new xorg.conf file by running "Xorg -configure' and was testing the new file with "X -?? /etc/x11/xorg.conf.new" (I forget what the -?? option was). I assumed that this would not overwrite the /etc/x11/xorg.conf file and that if I ran into problems, that the original xorg.conf would be in place. how I can get this miserable thing to boot?
I installed Ubuntu 10.10 on my 32gb flash drive. Just one large partition for the OS and about a gig for swap. Worked fine. Booted to USB on two computers and a laptop at home. Fine. Figured I'd try it on a work pc for the sake of testing a random computer. Well I stick the drive in, boot up, select usb from the boot menu and bam Ubuntu starts loading. I look away, it's cool ubuntu's loading. Well I turn back and it's a black screen. It's "<username>@whatever login:" or something close.
I use the username and password I created during installation and what I used to login to the computer like fifty million times while booted into Ubuntu. Well, invalid login. The first time I installed this OS on this drive I updated it through the update manager and rebooted. Next thing I know I type in my username and password, hit enter, and bam black screen, some stuff, then im asked to login again. Now after this next iteration I am faced with yet another faulty login screen. What is up with this OS?
I have just did an upgrade from 9.04 to 9.10. I am planning to go to 10.04 . After the upgrade everything was ok but I noticed the GRUB was still legacy. So I updated my GRUB to GRUB2. Now when I boot, after entering my logon-id and password, it just brings me back to the login-id screen (to logon on). Any indication of what is wrong and how I should fix this ?
I have no encryptions. [added comments] Currently reading thread about login loop bug with 9.10 Followed instructions about possible missing pre-release update but even if it did do updates, I am still login screen looping. Doing additional researches until someone answers with the fix. did : CTRL + ALT + F1 switch to one virtual console sudo service gdm stop
When I try to login with my username, the one I created when I installed the OS, it seems to try to login but almost immediately kicks back to the login screen. No authentication error it just seems to just logout? The only change I made since last successful login was to add ". .alias" to the .profile file - the only entries in the .alias file are comments and "alias" commands. I have one other username but it is not in the sudo's list of users so I can not change anything in the master login.
been using 11.2 with KDE on a Sony laptop since 11.2 was released always ran perfect suddenly I can't login, I get to the login screen type in password it begins to load my desktop, then fails and dumps me back to the login screen I can login as root, all my stuff is there (under /home/me) I tried changing my password, no luck I went to run level 3 and there I can login just fine seems to be something with my KDE profile any ideas where I might find some error messages telling me what's going on?
this seemed to happen when I was running "blender" and making the machine do some heavy number crunching, it actually locked up.
when I get into the login page, I can only see the background and the login box in the middle of the page just turns whole white and keeps flashing. no response for any clicks. I was force to ctrl+alt+F1 to switch to init 1 to do my work. But I still want to use my graphical desktop either KDE or Gnome is ok. I am using gnome.
I want, when I boot up, to load and log-in automatically a default user. I get a login in screen with the option to login as root, I do not want this. How do disable the option to login to X as root and just load as me/default user?
Status: openSUSE 11.3; Fujitsu Tablet ST4110.I've managed to install successfully openSUSE 11.3 on my old Fujitsu Tablet 11.3. nomodeset needs to be used at GRUB boot. Now, at the login, when I click Others, and prompted to type a username, when I clicked on the virtual keyboard at the bottom right corner of my screen, the I-beam icon looses focus from the entry box, and each character pressed on the virtual keyboard does not appear on the entry box. When I try to click on the entry box, focus cannot be returned to the entry (ie. the I-beam icon does not flash at the entry box).
when i login to openSUSE a window named login keyring appears and it asks me root password. it happens everytime when i login. how to fix this problem?
I just upgraded from 10.04 to 10.10 this morning and after the upgrade I can't log in via GDM. If I log in it seems to work and the screen goes black, but then it goes right back to the login screen.I can't figure out what is throwing the signal, but the interesting thing is that if I stop GDM and log in on the console, I can run startx and my session runs fine (I'm typing this message from firefox). Any ideas on how to determine what is throwing the signal? I tried poking around in /var/log but I can't find anything that seems relevant.
I've been running openSUSE 11.2 within a VM using VirtualBox 3.1.2 with Vista x64 as the host OS for quite some time now with good results. Yesterday I went to reboot the VM and VBox made some comment about 3D not working and needing to install the VBox guest additions (which were already installed). After rebooting and seeing the openSUSE splash screen, I now get a solid purplish display with no activity. I've tried running "sax2 -r", re-installing guest additions, running the repair CD, and other things but this problem has not gone away. Aside from reloading the OS, does anyone have ideas on how I might fix this?
I request assistance to fix the following annoying problem: In SuSE 11.2, GNOME, the taskbar and menus are not available after boot up. Consequently I do not have access to applications which I urgently need for some work I am doing.
Lately I had to reboot a couple of times (by way of terminal window) in the hope that it comes up. Now, however, the taskbar/menues do not come up any more.
I just installed a test Natty VirtualBox server from the "mini" iso. After doing that the normal boot always ends with a blank screen and cannot login. The recovery boot option does work normally. After much digging around and various tests I found that the "splash quiet" boot options cause this issue.
I removed them from the /etc/defaults/grub file and ran update-grub. Next boot the login screen came up after as normal. It seems when the splash flashes that purple screen with the Ubuntu 11.04 message it is breaking something and does not get back out of some graphics mode.
This is in a VirtualBox window and I noticed that vesa framebuffers seem to be used by default in grub now. I never had this issue in previous releases and I'm just wondering if others have seen this and if there is a better fix than disabling splash. I don't mind having it disabled as this is a server install anyway and I'm fine with seeing debug messages during boot. If other have seen this then perhaps it needs to be logged as a bug?