I am unable to login to kde after upgrade to fc14 from fc13 as user , the splash screen works for seconds and returns back to login screen, but I am able to do as root
I also managed to login to KDE (failsafe session)
and also I am able to login as normal user to gnome desktop
Code:
# cat /etc/init/tty.conf
# This service maintains a getty on the sepcified device.
stop on runlevel [016]
respawn
instance $TTY
exec /sbin/mingetty $TTY
exec /sbin/mingetty --autologin user tty1
when i use this conf I'm auto logged back in again , and cant't execute any command
commenting pre-last line has no effect.
How to enable autologin on desired tty for certain user?
I just installed FC13 on my laptop. I cannot upgrade from FF 3.6.7 to 3.6.8.
View 3 Replies View RelatedTook an FC12 system to FC13 via 'preupgrade'There was a REALLY old version of gimp-print-cups in RPM, and the installer announced "a fatal error occurred". However, everything else seemed to download properly and I allowed the upgrader to reboot the system.
a) grub boots the kernel, then the kernel can't find root and panics. It does this because it can't root file system with root=UUID= kernel option. If I manually tweek the grub line to use root=/dev/sdx, kernel finds its root and boots up to the next problem.
b) GUI environment not launched. Init scripts die on "error loading modules.dep". Sure enough - one is not there. Ran "depmod" to generate it ,and rebooted. System reboots into GUI, where I login to find the next problem.
c) Evolution won't start. Reason turns out the evolution-data-server from FC12 is still present. Did a check on just how many other FC12 RPM's are present: 1100. Yeah - over 1000. About 850 of the FC12 RPM's also had FC13 replacements installed. Did an "rpm -e" on these. Also had to do some remove action on mkinitrd, nash, plymouth-scripts-0.8.0, and parted-1.9.0 as there are replacements for these utilities under different package names. That cleaned up the system some, to present me with the next problem.
d) yum package repository still linked into FC12. Removed fedora-release-12-2.noarch and then I could "yum install" evolution and a few other packages properly.
I've done one other FC12->FC13 upgrade today, and that went flawlessly. So, I think in general the upgrade works fine. It just looks like if preupgrade finds anything amiss, it doesn't take care of a lot of things and generally leaves you with an unbootable mess to clean up.
Having just installed fc13 and downloaded the KDE package I attempted to log out as user and back in as root, but I keep getting a message about the wrong password. This is odd as the same password works in terminal if I try to become a SuperUser. I have tried turning off SELinux to no avail. I cannot log in from cold as root,only as user.
View 1 Replies View RelatedI managed to successfully upgrade FC11 to FC13. While doing the post upgrade steps, I made a HUGE mistake. After identifying the unsupported packages, I used "yum remove package1 package2" command to remove the obsoleted ones without realizing the yum was also removing many FC13 packages! Here are the cmd sequence used:
# package-cleanup --orphans
...
# yum remove compat-db45-4.5.20-5.fc10.i386 flash-plugin-10.0.32.18-release.i386 gnome-spell-1.0.8-5.fc9.i386 ifd-egate-0.05-21.i586
[code]....
I simply typed Yes and left unattended for a few minutes after yum prompted there were # of packages to be removed as I blindly believed it would do the job. After returning to the computer, I found many installed icons were disappearing, the wireless suddenly turned off etc. I killed the yum process right away but it was too late.
-Is there anything I could do to undo the yum remove process?
-How to safely remove supported packages?
I have just upgraded my FC12 installation to FC13. The initial boot failed (just blank screen). Second time I received 'selinux targeted policy relabel is required'. I let that run, but still the boot did not suceed.
I then went in to verbose boot and saw that the boot would hang at libvirtd. So I disabled libvirtd for anything above run level 1. Next boot failed at atd, disabled atd. Next boot failed at 'monthly Smolt checkin'.
At that point and booted in to single user mode and dissabled SELinux, thinking that was the cause of all the problems. That did not help.
The update process has also removed my previous kernels, so I can't test a different kernel
I've recently upgraded my hardware. Now, the system boots perfectly fine, but I can't login to the tty as root or any other user. Infact yes, I can login, but as soon as it shows Last Login, it exits and then I'm back to a login prompt. I've successfully booted into single user mode, and changed all the passwords, but still it fails. X doesn't start, although I think it's due to the old xorg.conf having the wrong driver.
View 9 Replies View RelatedLast nights upgrade of java-1.6.0-openjdk-1.6.0.0-43.1.8.2.fc13.i686 and java-1.6.0-openjdk-plugin-1.6.0.0-43.1.8.2.fc13.i686 prevent the loading of Ameritrades Command Center.Downgrading to version 1.6.0.0-37 fixes the problem. I'll post the bugzilla number as soon as I get the chance to file it.
View 3 Replies View Relatedyesterday I updated my fedora 13 to fedora 14 (on laptop) and today i cannot log in on user. It just go blank for a sec and is back to login.
At text console (alt+ctr+f2/f3) i enter my username and pass it give this for a sec and resets (clean) console
username: Name
password:
last used: [date]
login: no shell permission denied
i used unetbootin (fedora 14 netinstall to update) and later i updated 1,5G before reboot (did update that fix, forgot its name tho :s)
I would most likely reinstall everything, but i have some work at laptop and as death-line is near, i would prefer to fix it if possible.
edited:
i have installed F13 on unused space, is there a way for me to access and fix it? or at least get some files from there?
Recently I upgraded my kernel to 2.6.34.6-47.fc13.x86_64 and then also did an update to 2.6.34.6-47.fc13.x86_64. Both of these kernels I do not get a login dialogue box. I still have the one kernel that works and it is 2.6.33.8-149.fc13.x86_64. The system I am on has a Radeon graphics card, but I don't think the graphics card is the issue since I get the login screen's background, but not the login screen itself. <Later> After messing around with this for a while I came to the conclusion that livna-config-display was messing with the xorg.conf file. Removed it and things seem to be working fine now.
View 1 Replies View Relatedgot my upgraded fedora 14 partition to boot, but I find out that I had to reinstall my nvidia driver, no big deal. seemed to go ok, but now when I go applications->system tools -> terminal I get the "starting terminal" thing on the bar, and then nothing. Can't figure out whats up.
View 4 Replies View RelatedUbuntu 8.10 does not ask for a password to login. I have only one user set up. I have set the user password from System > Administration > Users & Groups. Still does not ask for password > logs in straight away.
View 2 Replies View RelatedI upgraded from FC11 to FC13 last night. The desktop has not been stable since. It will run for anything from 5 to 30 minutes before it locks up. Interesting, if I am already ssh'd in, I can perform commands, but a new SSH will hang, and if I try to SU to root in an already logged in ssh, it hangs.
However, I did finally manage to get the messages that were logged to /var/log/messages at the time of the desktop freeze.
Here are the messages. The first 3 about high speed usb may or may not be relevant. The freeze appeared to happen around the 4th message in the log below.
Code:
Sep 2 13:16:57 starbug kernel: usb 2-4.2: reset high speed USB device using ehci_hcd and address 6
Sep 2 13:26:38 starbug kernel: usb 2-4.2: reset high speed USB device using ehci_hcd and address 6
Sep 2 13:31:20 starbug kernel: usb 2-4.2: reset high speed USB device using ehci_hcd and address 6
Sep 2 13:38:03 starbug kernel: INFO: task jbd2/dm-0-8:558 blocked for more than 120 seconds.
[Code].....
I was having a job in /etc/event.d. It was working fine upto FC12. With upgrade to Fedora 13, it stopped working . Searching the internet, It looks like /etc/event.d is obsolete and I need to use /etc/init. Also the filename has to have a '.conf' extension. So I have renamed my job as /etc/init/svscan.conf.However, it fails to start automatically on reboot . It works if I manually issue the command % sudo /sbin/initctl emit qmailstartBut fails to start automatically on reboot. Is there anything wrong in my script below ? Let me know if I have missed out anything?
% cat /etc/init/svscan.conf
# svscan - runlevel compatibility
# WARNING: This file was auto-generated. Do not edit!
[code]....
I have a problem with LVM. My installation of Fedora 13 is on 2 SATA hard disks, which are set as /dev/sda and /dev/sdb. On sda there are two partitions (boot and a physical part of the volume group) and on sdb is only one partition (other physical part of the volume group). Both physical parts of the volume group are used for one volume group and the VG is splittet into multiple logical groups. The system works and all seems to be ok. But I saw a strange thing on last reboot:
The device /dev/sda was not recognized during the boot sequence, instead the system has build a device /dev/md126p1 with the same geometry and partitions and it has the same disk id as sda.
The volume group is also ok, the system boots into the desktop environment, but the system-config-lvm says that /dev/sda is not initialized and the volume group consists of sdb and md126p1. fdisk -l knows three devices (sda, sdb and md126p1). I think, that is the reason for my problems with preupgrade, which stops after the reboot with a LVM problem (root not found). Can I correct that without data loss?
Here is my problem:
I need to enable the statistic module in iptables.
I had Fedora 13 32 bits, iptables-1.4.7-2 and kernel 2.6.18
But kernel 2.6.18 does not support statistic module.
So, I upgraded from Fedora 13 to Fedora 14.
Now I have Fedora release 14 (Laughlin) and Kernel 2.6.18
I did this to upgrade: url
Also, I did this too.
# yum update kernel
No Packages marked for Update
How can I ugrade to newer kernel?
Previously I have a hard disk running OpenSUSE partitioned as follows:
Code:
/dev/sda1 = swap
/dev/sda2 = /
/dev/sda3 = /home
I redid the default partitioning scheme that Fedora tries to use (no LVM crap). Basically told it to make the above layout and to format swap and slash, but NOT to format /home because I want that data. I had it go ahead and install grub on the MBR of this HD as well. The install seems to have went ok and it rebooted. That is when the first problem comes up. I never see grub. I just get a black screen then a bar at the bottom that progressively turns blue, which I assume is Fedora loading.
This is all well and good, then it gets to the login screen (GDM) and I try to log in as root and it tells me "can't authenticate user" hangs for a bit, then goes back to the log in box. I try to get a virtual console (Ctrl+Alt+F#) and nothing. So I guess I have 3 problems in order of significance:
- Why no grub?
- Why no virtual console?
- Why root can't log in?
Normally I would edit kernel option line at the grub prompt to boot into single user mode and fix the problem, but can't. I was able to use the "rescue mode" on the Fedora DVD to accomplish this, but have not had a chance to figure things out any further. I don't think having a /home created by another OS would prevent root from logging in since root "home dir" is /root.
Fresh install of Fedora 11 x86_64, ext4 file system, Intel Quad, 1 Tb disk
Went through install, defined mike as user with password
reboot, get graphic login (init 5); cannot login as mike OR AS ROOT!! (unable to authenticate)
use live cd, reset inittab to start at level 3
reboot, get user prompt on terminal at level 3
enter mike and password, system wait a minute or more, returns to login prompt (obviously timing out --- dbus problem???)
enter root and password, get in, issue startx
open terminal window, and issue "su mike" command, ten minutes later, finally get terminal with mike as user.
Use ctrl-alt-F2 to get a terminal, type mike, and password, no joy; login as root and type "su mike". Go back to Gnome screen at F7, so I can continue to type this , and check back at F2 periodically to see if "su mike" ever takes. After three minutes, still no joy. After five minutes, it worked. whoami shows "mike"
If I'm getting good at anything with Fedora, it would be making mistakes. I have Fedora 12 installed and it was running fine until I attempted to set the path in bashrc and cshrc for jdk. Now I am unable to login using the only user account I created at install. When I enter my password the login screens goes blank then my mouse pointer appears with the circling dashed loading symbol for a few secs and then brings me back to the login screen asking for my password again.
View 4 Replies View RelatedI upgraded a working Fedora 9 installation to Fedora 10 using the installation DVD. Sound works for root but not for other users. All of the pulse audio RPMs are installed. This appears to be a permission issue as it works for root. My user is a member of the 3 pulse Groups.
View 1 Replies View RelatedI have a problem to login with the root user from gui (I use Gnome). The root password is ok. Is there a way for me to logon with the user root in gnome?
View 1 Replies View RelatedAbout a week ago I used preupgrade to make the transition F14 -> F15 on a x86_64 workstation.
The system has been fully updated ever since, but I'm still not able to login either with KDE or Gnome. With KDE, the login process freezes before completion, whereas with Gnome I get the "wallpaper" behaviour reported here: [URL]
Funny though, I can login in the KDE failsafe session.
I could find no other thread reporting this problem and am at a loss on how to start diagnosing the problem. If anyone out there has any suggestion, I'd welcome it...
what's the difference between a "regular" KDE session and the failsafe one? They both look & feel the same to me...
I have a windows 7 ultimate host machine, installed oracle virtual box on it. Made a iso image to boot fr fedora. All this is fine when the installation is complete, it asks for reboot. Reboot done. Then I went to terminal. Did a SU - root to get into the root. Then I did a firstboot command to enter information. I created a user for myself and at the end rebooted the virtual box.
When it starts up, it does not show my user. It just shows "Automatic Login" and it logs in as Live System User. Even if I try to switch user then it gave me a authentication failure when I enter the credentials of the user which I created. If I try to create users manually using system administration, the user is lost after reboot. I have tried all possible steps...as instructed on the net.
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[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 upgraded to fedora 10 using yum but i have a problem, the installation went fine and after rebooting i got a login screen. I typed in my user name and password and after a second it returns to the login screen. Im sure the username and password are correct. If i type in another password i get an error message. So how can i log in?
This is what i did to upgrade to Fc10:
Code:
Then i got an upgrade wizzard and selected Fedora 10 and than reboot.
In the grub menu only one kernel is present which is the Fc10 so couldn't use the old one.
I've tried to edit the kernel with single for single user that works gives me a command line but im just not experienced enough to figure out how i can use the command line to login.
My system is Dell 4300S with 1.4 GHz Pentium processor, recently upgraded to 1 GB RAM,120 GB WDC1200JB hard drive Sony DRU-720A DVD/RW drive, ATT plugandshare wireless adapter with Atheros AR5001X chip, ATI Rage 128 Pro Ultra TF video card, and Actiontec V90, and 56KFlex modem (Agere System Venus). I attempted to use preupgrade to upgrade from Fedora 12 to 14 using wireless connection. It seems, that upgrade finished successfully, except I am not unable to get to a GDM login. I updated SElinux to selinux-policy-3.9.7-10 and selinux-policy-targeted-3.9.7-10, and touch /.autorelabel overnight, I was able to login using GDM once. And that is all. After I boot, after Ctrl+Alt+F4, I can login to terminal.
[Code].....
Code:
$ su -c 'yum install wine'
this forum won't let me put all the text in Transaction Check Error: package openldap-2.4.21-6.fc13.x86_64 (which is newer than openldap-2.4.21-4.fc13.i686) is already installed package nss-softokn-freebl-3.12.4-19.fc13.x86_64 (which is newer than nss-softokn-freebl-3.12.4-17.fc13.i686) is already installed
I was using Fedora 11 for the past few months. It was working fine. I upgraded yesterday to Fedora 12 and now every time I boot up, the fedora logo screen comes up, the "f" is filled up and after that the screen goes hazy. I was expecting the login screen but nothing comes - the system freezes sort of.
View 1 Replies View RelatedI have a mivvy l310 netbook. Before I had FC12 on it and I couldn't upgrade (not enough space on /boot, tried all commands and it didn't worked) to FC13. So I said I would do a fresh install for FC13. I used live CD FC 13 iso to make the usb drive (16gb) bootable.It boots, all goes ok, untill the installation is in progress of copying files to my HDD (at this point my HDD is empty, since it was formated). At about half of the progress bar of copying the installation files to HDD it stops with: ""There was an error installing the live image to your hard drive. This could be due to bad media. Please verify your installation media."" I can't go further and install it. I tried making the usb drive on FC13 (finished successfully, on another laptop with liveusb creator) and also on SUSE and it behaves the same.
I also tried second method (described in a thread around here, it worked for me in the past for FC11), by just making the usb drive bootable, using commands in the terminal (here my FC13 kernel, on another laptop crashes, for some commands) and when I try to install I get only: "missing operating system, sleeping forever". For this method, it does not boot at all, so I guess the usb drive is not properly setup. I don't know what else to try. I tried normal dvd iso, live cd, tried making the usb using commands, using live cd, with commands on suse, on FC13 etc...
LE: I found in messages log that I have: zlib_inflate error fc13
LE LE: what's more weird is that I downloaded the same live image of FC13 and burned it on a CD and managed to install it on my other laptop and it worked.
Later update: I tried now with the DVD iso for FC13 and now I get: operating system not found