"your last session only lasted less than 10 seconds"
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"your last session only lasted less than 10 seconds"
New to Suse and Linux.
I get the error in Suse 10:
Your last session only lasted for less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of diskspace. Try logging in with one of the failsafe sessions to see if you can fix this problem.
If I click on "View Details (~/x-session errors file)" I see nothing. What did I do wrong? How would I repair it?
This is the second time I've installed Suse and got the same message. I'm using an 80 gig drive and surely I have plenty of space. What gives? I have my wireless working and performed the updates.
I have another PC that I installed Suse 10 on and I get the same thing. I have logged in as root in Gnome a few times and on the other PC I get the same message logging in as root, on this PC I get it during autologin when booting as my user name.
I posted in the hardware area as to how to get a link to or some step-by-steps to install another hard drive that I have data on that I wish to access. The drive was on an XP machine. Installing it showed no such drive until I poked around and got it showing. I cant do anything (move, copy/paste) with the files on it. Im looking for a step-by step to install a drive too, so help would be appreciated very much.
Don't ever login as root in X.
Try fixing this automaticly first.
Boot with SuSE CD/DVD=>installation=>repair installed system=>automatic repair
Also login FIRST in KDE, then if you want Gnome, logout and enter Gnome and save it as default session.
And again NO X for root.
Can you tell me what exactly happens when I do? Simply saying "never" is easy and if I shouldn't then for now I won't.
If I inderstand you, youre saying the GUI is never, ever designed to be entered as root, correct? I mean Never?
Is there any situation where you Would log in as root? And if so what causes Gnome to have erros like it does?
Can I have Gnome and KDE installed at the same time or is it either one or the other? How would I change desktops if so?
Will giving myself (user) root priveliges in itself cause the root login in Gnome to get the errors I'm experiencing?
I wanted to simply add a NTFS formatted drive with MP3's and stuff already on it and have access to the file system and have it show And be able to read and write to it, then add another populated drive and do the same. I got in deep and being new, tried to figure out things using the GUI w/o having to type alot in terminal. I suppose this is just a dream for now.
Thanks for the suggestion. Can booting to the cd really repair things that easy? And what about the fact that I have done the online updates?
If using X as root you mess up permissions, links and lot of other stuff. A lot to write..
As for your NTFS drive, use Konsole in KDE
$su
password
#linux~> mc
Use Midnight Commander to navigate and operate
About KDE in SuSE. It's just default DE. Like Gnome in Ubuntu.
I accidentally deleted whole /tmp directory today and I had been experiencing same that problem.
Quote:
"Your session only lasted less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of disk space. Try logging in with one of the failsafe sessions to see if you can fix this problem."
Anyway I was happy enough, because I could log in as root to try and fix this problem. So I created /tmp and then issued chmod 1777 /tmp and problem was sold.
I don't recommend you to do this or anything but this is in short what I've done...
...like root
Code:
rm -rf /tmp
mkdir /tmp
chmod 1777 /tmp
That is, if you suspect solution to your problem is in /tmp directory.
-- Joseph
Last edited by tuesdays-child; 03-22-2006 at 09:02 AM.
I tried doing same way when that 10 second error has occured and now i am not getting my windows os on the list when booting. and the problem of 10 seconds is stll there.
Is my windows xp still there..?
I have installed SUSE linux enterpise desktop 10 on windowsxp ..dual boot.
Please help out in recovering these two OS
THANKS
Quote:
Originally Posted by SlackerLX
Don't ever login as root in X.
Try fixing this automaticly first.
Boot with SuSE CD/DVD=>installation=>repair installed system=>automatic repair
Also login FIRST in KDE, then if you want Gnome, logout and enter Gnome and save it as default session.
And again NO X for root.
There are several reasons of X session crashes. Some of these are:
- When SuSE gets up, so normally after X fails, press Ctrl + Alt + 2 keys. You'll see a text based login screen. After you loged in, check the presence of your home directory (like /home/iamnew2linux, you can parse it by typing more /etc/passwd). You (iamnew2linux) must be owner of this directory. Not root. If not type chown -R iamnew2linux /home/iamnew2linux.
- The second reason may be about your XF86Config file. If your X configuration is not compatible with your hardware you can not use X session. As you guess you have to rebuild XF86Config. You can easily do that by using sax2 tool. This tool tries to build the best XF86Config file for your hardware. If sax2 does not give response you can interrupt it by pressing Ctrl+Alt+Backspace keys. If sax2 gives no error, you cab manually restart X session by using rcxdm restart command. It would be better backing up the original XF86Config file at any location ( cp /etc/X11/XF86Config /tmp )
You can findout some tips by cat /var/log/messages (you must make su - before previewing messages file)
Strongly probable your windows xp is still there. You must do some grub configuration to reach it agin.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.