LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 02-26-2008, 06:47 AM   #1
Ken Russell
LQ Newbie
 
Registered: Jan 2006
Location: Worcester, U.K.
Distribution: Ubuntu
Posts: 18

Rep: Reputation: 0
X not starting - probably after installing updates


I installed some updates a few days ago from Mandriva.

I'm running 2008.0.

After reboot, KDE is hanging, and I think its because X is failing to start.

I can get a command prompt and all hardware seems to be working ok.

X starts, but just "freezes" at a blue screen.

I can view the system logs, and i "seem" to be getting a message about the X-server dying unexpectedly. I say seem, because this might be me killing the hung KDe startup.

Is there a better or more detailed log of X startup ? Or can anyone else provide me with a better troubleshooting method ?

I'm a bit stuck without a working machine, 'cos my command line skills are limited (and very rusty !).

As ever i'll ensure the solution is posted here if anyone else ever has the same problem.

Ken
 
Old 02-26-2008, 07:33 AM   #2
b0uncer
Guru
 
Registered: Aug 2003
Distribution: CentOS, OS X
Posts: 5,131

Rep: Reputation: Disabled
Brobably the best place to look for what happened when you tried to start X is at the logfile:
Code:
less /var/log/Xorg.0.log
Hopefully that gives some new information.

It might depend on what you upgraded, so try to remember which packages you installed - video drivers, perhaps, or a kernel upgrade? Are you using some proprietary drivers (like ATI's fglrx or nVidia's equivalent drivers)? If you are, you might have to reinstall them, then reconfigure your X.

You may also want to review that the configuration file of X is ok:
Code:
less /etc/X11/xorg.conf
If you need to make changes, log in as root (in the console), then use vim, nano, pico, joe or any of your favourite editors to edit the file. You could basically use one of the semi-automatic X-configuration "programs" (scripts usually), but they mainly just overwrite the whole configuration and ask you loads of questions, and therefore it's often easier to just directly edit the config file if you know what to change.

Well, see the logfile if it helped to locate the exact problem.

You could also try to start X with xterm only, so you saw if it was the desktop environment (probably not) that causes the trouble, or X itself (it's configuration usually):
Code:
mv ~/.xinitrc{,.bak}
echo xterm > ~/.xinitrc
startx
mv ~/.xinitrc{.bak,}
The above basically renames your .xinitrc file (which is in your home directory) to .xinitrc.bak (so we don't lose any data that might be there), then creates a new .xinitrc file that has only "xterm" in it (so when X starts, it just runs xterm and when it ends, closes X), then startx tries to start X (.xinitrc is read, and if X starts, xterm is launched). If it works, just type 'exit' at the xterm prompt and you're back at command line - and know that X is not the problem, but something in your desktop environment (I doubt this). If it doesn't start, then you'll just run the last command putting the original (renamed) .xinitrc back to it's place and think of something else.
 
Old 02-26-2008, 04:12 PM   #3
Ken Russell
LQ Newbie
 
Registered: Jan 2006
Location: Worcester, U.K.
Distribution: Ubuntu
Posts: 18

Original Poster
Rep: Reputation: 0
getting there....startx works !!

thank you b0uncer. I'm getting somewhere now.

Here is what happened...i kind of followed your suggestions.....

The X log file wasn't much use..its very long, no clear errors that i could see.

the config file for X looked ok (not that i'd be sure...but it looked alright)

I looked at your suggestion for .xinitrc but cannot find that file in my hoem directory.

so i took the bull by the horns and just typed startx at the command prompt.

Lo and behold i have a working KDE.

typing kde at the command prompt still hangs it.

So my conclusion is that X IS working and KDE is in some way ill.

any thoughts anyone on how to look at hoe KDe starts up ???

Thanks for the help so far !!!!

Ken
 
Old 04-22-2008, 06:59 AM   #4
Ken Russell
LQ Newbie
 
Registered: Jan 2006
Location: Worcester, U.K.
Distribution: Ubuntu
Posts: 18

Original Poster
Rep: Reputation: 0
upgraded so close this thread

Well I have upgraded to spring and still have the problem.

As far as i am concerned this is now a closed issue. I can work around it.
 
  


Reply

Tags
kde, kde35, mandriva2008


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Fedora Core 6 won't start after updates installed - Starting udev: Disabling IRQ #16 Martin01234 Linux - Newbie 3 01-11-2008 06:24 PM
Installing updates Hamlets Ubuntu 2 06-29-2006 04:08 PM
why after installing updates using up2date boxerboy Fedora 6 08-02-2005 05:18 PM
Installing Updates from a cd (fedora 1) FocusedWolf Linux - General 2 02-20-2004 11:10 PM
Installing openSSH updates on RH 7.2 tawsie Linux - Newbie 1 09-19-2003 10:42 AM


All times are GMT -5. The time now is 12:29 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration