Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to load Compiz on my Fedora 15 desktop. When I finished installing the compiz packages, I restarted. However, it started in text terminal mode and the gui didn't load automatically.

I executed following commands externally to load my gui (in root mode):

cd /etc/dconf/db
exec gdm

Though that is working perfectly, I want to load the GUI automatically.

share|improve this question
Did you check what runlevel (fedoraproject.org/wiki/Systemd#How_do_I_change_the_runlevel.3F) you were booting into? Not familiar with upstart on Fedora, but I believe chkconfig can still be used to add/remove services from runlevels. – symcbean Apr 3 '12 at 11:41
up vote 0 down vote accepted

Fedora 15 uses systemd. First make sure you're running the 'graphical' target by making sure that /etc/systemd/system/default.target is a symlink to /lib/systemd/system/graphical.target, which is the equivalent of runlevel 5 (and not multi-user.target, which is the equivalent of runlevel 3).

Next, make sure that the 'prefdm' service is running. Check the output of systemctl status prefdm.service. it should show that it's loaded and active. If you weren't at the graphical target, it probably won't be.

Now, if you already had it in the graphical target, it's possible that X isn't starting due to some error. Check the log files in /var/log/gdm, look at the files with the timestamp of the last time you booted, to see if maybe something was broken.

share|improve this answer
thanks. my systmed got set to runlevel 3, thats why, this is happening – White Dwarf Apr 12 '12 at 7:10
not sure why installing compiz would do that. is there something else you might have done to change the default runlevel (or target, in systemd parlance). – jsbillings Apr 12 '12 at 22:22

You should check to make sure what run-level you are in after boot, and if gdm is being started for the run-level. You can do this manually by checking the symlinks in your /etc/rc*.d directories, where * is the number of the run-level.

First check to make sure you have a gdm init script, and run it to verify that it properly starts gdm:

$ ls -l /etc/init.d/ | grep gdm    
$ sudo /etc/init.d/gdm start

If that works, then you can check the symlinks in the runlevel that you are in you can get you current runlevel with the 'runlevel' command. Then check for the correct symlink

$ runlevel
$ ls -al /etc/rc3.d/ | grep gdm

If it's not there, create the symlink:

$ cd /etc/rc3.d/
$ sudo ln -s /etc/init.d/gdm 

After rebooting, this start start the gdm init script. Make sure you are using the correct init script filename. I am using 'gdm' because I assume thats what it's called, but I could be wrong.

share|improve this answer
Fedora doesn't start gdm via an initscript. Heck, it practically doesn't even have initscripts anymore. – Ignacio Vazquez-Abrams Apr 3 '12 at 15:43
Ah, I guess I'm an old-timer now :P – Nick Jennings Apr 3 '12 at 15:44
F15 uses systemd. – jmtd Apr 3 '12 at 15:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.