[SOLVED] X suddenly stopped working

spoovy · 11-18-2010, 05:33 AM

Booting up this morning, no problem. But I accidentally let my laptop go into suspend mode, which doesn't work, so I had to force a restart (Suspend mode on my laptop won't allow me to wake it up again).

Now, on rebooting, X doesn't work. I usually boot to RL3 then use startx. Now it just flashes the screen then gives me this error -

Code:

(EE) Error compiling keymap (server-0)
(EE) XKB: Couldn't compile keymap
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.

Fatal server error:
Failed to activate core devices.

Please consult the The X.Org Foundation support 
at http://wiki.x.org
for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

..and from Xorg.0.log -

Code:

(II) intel(0): Initializing HW Cursor
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(==) intel(0): DPMS enabled
(==) intel(0): Intel XvMC decoder enabled
(II) intel(0): Set up textured video
(II) intel(0): Set up overlay video
(II) intel(0): [XvMC] i965_xvmc driver initialized.
(II) intel(0): direct rendering: DRI2 Enabled
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_make_current_read
(II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i965_dri.so
(II) GLX: Initialized DRI2 GL provider for screen 0
(II) intel(0): Setting screen physical size to 338 x 211
(EE) Error compiling keymap (server-0)
(EE) XKB: Couldn't compile keymap
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.

Fatal server error:
Failed to activate core devices.

Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

If I su - to root and then do "init 4", I get to xdm, and I can log in. X then starts, but with no sound, wrong keymaps, launchers not working; all sorts of things wrong.

If I startx as root I get a normal desktop. I have tried copying root's xinitrc to /home/spoovy, but makes no difference.

Seems like a permissions thing, but what? I can't think of anything I changed that might've broken it.

What on earth is going on here?

Thanks in advance

Spoov

spoovy · 11-18-2010, 07:50 AM

This problem (or a very similar one it would appear) has cropped up before -

http://www.linuxquestions.org/questi...errors-833887/

It was suggested there that the questioner supply the following info, so I am doing so here -

Code:

root@poppy:/home/spoovy# egrep 'WW|EE' /var/log/Xorg.0.log
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) The directory "/usr/share/fonts/local" does not exist.
(WW) The directory "/usr/share/fonts/CID" does not exist.
(WW) The directory "/usr/share/fonts/local" does not exist.
(WW) The directory "/usr/share/fonts/CID" does not exist.
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
(II) Loading extension MIT-SCREEN-SAVER

spoovy · 11-18-2010, 08:38 AM

My mistake, sorry all. Problem was that the / dir was full.

live n learn..

Natasha-LQ · 12-13-2011, 02:57 PM

Spoovy wrote, "Problem was that the / dir was full."

Thanks, mate, for posting this! I had the same problem with X refusing to start (on Fedora 14) and it was due to the same problem: a 100% full root.

Even long-time Linux users learn stuff every day.

RW84 · 05-07-2013, 11:13 AM

Could you elaborate on what you meant by the directory was full? Which directory and how did you clear it? Thanks a lot!

Ahau · 05-08-2013, 02:34 PM

The "root" directory, aka "/", meaning the partition on which the core filesystem was installed. Xorg needs to write data to the drive when it starts up; since the drive was completely full, it failed. This could be remedied by deleting files out of the /tmp directory, assuming /tmp is on the same partition as the root filesystem.

NickBorneo · 08-29-2013, 04:10 AM

can someone teach me step by step how to delete files out of the /tmp directory? I am newbie to this software and i hope someone can help me with this. Thanks

perbh · 08-29-2013, 07:49 PM

If you are using Slackware, you can solve the problem permanently ...

Code:

# > /etc/rc.d/rc.local_shutdown
# chmod a+rx /etc/rc.d/rc.local_shutdown
# cat <<EOT >/etc/rc.d/rc.local_shutdown
#!/bin/sh
echo ":: cleaning up /tmp ..."
/usr/bin/find -mindepth 1 -maxdepth 1 -print0 | /usr/bin/xargs -r0 /bin/rm -rf
EOT
#

and then reboot ...

NickBorneo · 08-29-2013, 08:05 PM

I'm using ubuntu server.

zrdc28 · 08-29-2013, 10:54 PM

cd /tmp when you are inside /tmp "rm file1" "rm file2" etc. minus the quotes.

leifnel · 02-24-2019, 04:28 PM

Quote:

Originally Posted by perbh

If you are using Slackware, you can solve the problem permanently ...

Code:

# > /etc/rc.d/rc.local_shutdown
# chmod a+rx /etc/rc.d/rc.local_shutdown
# cat <<EOT >/etc/rc.d/rc.local_shutdown
#!/bin/sh
echo ":: cleaning up /tmp ..."
/usr/bin/find -mindepth 1 -maxdepth 1 -print0 | /usr/bin/xargs -r0 /bin/rm -rf
EOT
#

and then reboot ...

I know this is a late reply, but this doesn't specify that the find should start in /tmp.

You might end up deleting your entire disk :-(

volkerdi · 02-24-2019, 04:33 PM

Quote:

Originally Posted by leifnel

I know this is a late reply, but this doesn't specify that the find should start in /tmp.

You might end up deleting your entire disk :-(

Well... this is a valid reason to necropost if I've ever seen one.

enorbet · 02-24-2019, 04:35 PM

Easy Solution - Buy a larger drive and clone your old one while making each partition substantially larger These days even 200GB is tiny and cheap. In fact a quick search had the top hit for a WD Blue 7200rpm 1TB SATA Brand New full size hdd from Amazon for 50bux USD.

leifnel · 02-24-2019, 06:12 PM

Quote:

Originally Posted by enorbet

Easy Solution - Buy a larger drive and clone your old one while making each partition substantially larger These days even 200GB is tiny and cheap. In fact a quick search had the top hit for a WD Blue 7200rpm 1TB SATA Brand New full size hdd from Amazon for 50bux USD.

Welcome to the crypt.

When the disk runs full, You might start by investigating why. It could for instance be a log cleanup failure, in which the problem will just reappear later.