Computer hangs "OK" Reach Target Graphical Interface".

English Install/Boot/Login
1

Hi OpenSuse Community

This morning shortly after the automatic updating of various softwares, the display on my opensuse 13.2 machine crashed (desktop turn black). I restarted the computer but graphical display never shos up. At some point a bunch of lines shows up (instead of the opensuse welcome screen) and things get stuck at “OK” Reach Target Graphical Interface". i tried to restart in safemode but result is the same.
If I presse alt F1 I can login via commad line. All my data is there. It just seems that X does not start.
And it failed when I tried to start it manually with the command startX. It complains about no space to write some temp files and then it says Fatal servor error. unaable to connect to X server. connection refused But none of my partitions are full

Reading from posts, this problem seemed to have occured for other users, but due to my poor computer background, I can not make sense out of those posts. I tried a few simple suggestions but nothing worked.

Can someone help me PLEASE.

If you guide me I can give you of course more information. But remember that I am a biologist …:wink:

Thanks in advance

2

Ok, so Xorg (the graphical system) fails to start.
If it happens also in safemode, it’s likely not a problem with your graphics driver installation.

But it might still be useful to know what graphics card you are using. And whether you installed a proprietary driver or not.

If I presse alt F1 I can login via commad line. All my data is there. It just seems that X does not start.
And it failed when I tried to start it manually with the command startX. It complains about no space to write some temp files and then it says Fatal servor error. unaable to connect to X server. connection refused But none of my partitions are full

Did you login as user?
In a default installation, this doesn’t work because of insufficient privileges.

Try to login as root and try to run “startx” then as a test.
Does it start?
If not, can you please post the messages you get?

OTOH, it might be easier to just post the files /var/log/Xorg.0.log and/or /var/log/Xorg.0.log.old.
They should tell why Xorg is failing to start.
It might be cumbersome to do so in text mode, so you could also boot from a LiveCD and/or a different OS if installed.
This would also at least rule out hardware issues, like a broken graphics card e.g.

Reading from posts, this problem seemed to have occured for other users, but due to my poor computer background, I can not make sense out of those posts. I tried a few simple suggestions but nothing worked.

Well, similar problems (or rather the same symptoms) occured for other users. But there can be many different reasons for this to happen. So trying some random suggestions is not going to work obviously.

Can someone help me PLEASE.

I’ll try… :wink:

Btw, do you have internet access in text mode?
If so, try to run “sudo zypper up”. Just continuing the interrupted update might already fix things for you…

PS: there was a GNOME update this morning, so I gather that you use GNOME, and it’s likely that that’s broken now (because of the incomplete update installation).
Try to set a different displaymanager in /etc/sysconfig/displaymanager by modifying the line with DISPLAYMANAGER accordingly (just open the file in a text editor), xdm should be installed by default.
Do you get a login screen then when you reboot?

DISPLAYMANAGER="xdm"
3

Thanks Wolfi for offering to help. This might be boring for you as I am really limited when it comes to facing a computer without graphical interface

Ok how can I get this info ?

I tried both a user and superuser. Same result with more or less same error message (complains about no space to write some temp files and then it says Fatal servor error. unaable to connect to X server. connection refused). I need to figure out a way to get the error message (right now I am using the machine next to my computer and looking at the screen).

Will do when I find how to do that …

The only thing I have handy is the USB stick on which I have the installation media. Would that work ? I tried to boot from this usb stick and point to rescue but it got me nowehre

How can I tell ?
I tried sudo zypper up: it returns

sudo:unable to write to /var/lib/sudo/ts/david: no space left on device. Again this does not seem right. And I know my root partition is not full /dev/sda3 which is mounted on / is 34% used

No I am using KDE. DisplayManager is set on kdm. I tried to change it using vi but even if i use sudo It complains it can overwritte.
As another piece of info when I login it tells me
login: write lastlog failed: no space left on device

isn it weird ?

thanks a lot!!!

4

Did you log in as root?if you logged in as root you do not need sudo

5

Well at least I am learning things here.Espetially how to surive with out graphical interface

Btw, do you have internet access in text mode?

I can mount a harddrive on another linux machine. SO I have some network capability.

Try to login as root and try to run “startx” then as a test.
Does it start?
If not, can you please post the messages you get?

Does not start and here is the error message

/usr/bin/startx: line 227: cannot create temp file for here-document: No space left on device
xauth:  error in locking authority file /root/.Xauthority
/usr/bin/startx: line 244: cannot create temp file for here-document: No space left on device
xauth:  error in locking authority file /root/.Xauthority
/usr/bin/startx: line 244: cannot create temp file for here-document: No space left on device

(EE) 
Fatal server error:
(EE) Could not create lock file in /tmp/.tX0-lock
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
(EE) 
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
-------------------------------------------------------------------------------------------
xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason?
If so either use a display manager (strongly recommended) or adjust /etc/permissions.local and run "chkstat --system --set" afterwards
xauth:  error in locking authority file /root/.Xauthority

OTOH, it might be easier to just post the files /var/log/Xorg.0.log and/or /var/log/Xorg.0.log.old.
They should tell why Xorg is failing to start.

This log is too long to report here. I can not figure out how to put it in inside a little window. So this is just the beggining

417.697]
X.Org X Server 1.16.1
Release Date: 2014-09-21
417.698] X Protocol Version 11, Revision 0
417.698] Build Operating System: openSUSE SUSE LINUX
417.698] Current Operating System: Linux RobbeLabWorkStation1.inmed.univ-mrs.fr 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) x86_64
417.698] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.7-7-desktop root=UUID=b0b549f2-6a2c-48d6-9a2a-b4c814775d6a ro resume=/dev/disk/by-uuid/0c0cd14f-d88d-4b1c-94f1-812a13c9f228 splash=silent quiet showopts
417.698] Build Date: 04 March 2015 01:16:46PM
417.698]
417.698] Current version of pixman: 0.32.6
417.698] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
417.698] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
417.698] (==) Log file: “/var/log/Xorg.0.log”, Time: Mon Apr 20 14:02:15 2015
417.699] (==) Using config directory: “/etc/X11/xorg.conf.d”
417.699] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
417.699] (==) No Layout section. Using the first Screen section.
417.699] (==) No screen section available. Using defaults.
417.699] () |–>Screen “Default Screen Section” (0)
417.699] (**) | |–>Monitor “<default monitor>”
417.699] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
417.699] (==) Automatically adding devices
417.699] (==) Automatically enabling devices
417.699] (==) Automatically adding GPU devices
417.706] (WW) The directory “/usr/share/fonts/misc/sgi” does not exist.
417.706] Entry deleted from font path.
417.707] (==) FontPath set to:
/usr/share/fonts/misc:unscaled,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/ghostscript/,
/usr/share/fonts/cyrillic:unscaled,
/usr/share/fonts/truetype/,
built-ins
417.707] (==) ModulePath set to “/usr/lib64/xorg/modules”
417.707] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
417.707] (II) Loader magic: 0x80ec60
417.707] (II) Module ABI versions:
417.707] X.Org ANSI C Emulation: 0.4
417.707] X.Org Video Driver: 18.0
417.707] X.Org XInput driver : 21.0
417.707] X.Org Server Extension : 8.0
417.707] (II) xfree86: Adding drm device (/dev/dri/card0)
417.720] (–) PCI:*(0:5:0:0) 1002:674a:103c:0122 rev 0, Mem @ 0xd0000000/268435456, 0xefd20000/131072, I/O @ 0x0000a000/256, BIOS @ 0x???/131072
417.720] (II) LoadModule: “glx”
417.736] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
417.775] (II) Module glx: vendor=“X.Org Foundation”
417.775] compiled for 1.16.1, module version = 1.0.0
417.775] ABI class: X.Org Server Extension, version 8.0
417.775] (==) AIGLX enabled
417.775] (==) Matched fglrx as autoconfigured driver 0
417.775] (==) Matched ati as autoconfigured driver 1
417.775] (==) Matched fglrx as autoconfigured driver 2
417.775] (==) Matched ati as autoconfigured driver 3
417.775] (==) Matched modesetting as autoconfigured driver 4
417.775] (==) Matched fbdev as autoconfigured driver 5
417.775] (==) Matched vesa as autoconfigured driver 6
417.775] (==) Assigned the driver to the xf86ConfigLayout
417.776] (II) LoadModule: “fglrx”
417.777] (WW) Warning, couldn’t open module fglrx
417.777] (II) UnloadModule: “fglrx”
417.777] (II) Unloading fglrx
417.777] (EE) Failed to load module “fglrx” (module does not exist, 0)
417.777] (II) LoadModule: “ati”
417.777] (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so
417.777] (II) Module ati: vendor=“X.Org Foundation”
417.777] compiled for 1.16.1, module version = 7.4.0
417.777] Module class: X.Org Video Driver
417.777] ABI class: X.Org Video Driver, version 18.0
417.777] (II) LoadModule: “radeon”
417.778] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
417.784] (II) Module radeon: vendor=“X.Org Foundation”
417.784] compiled for 1.16.1, module version = 7.4.0
417.784] Module class: X.Org Video Driver
417.784] ABI class: X.Org Video Driver, version 18.0
417.784] (II) LoadModule: “modesetting”
417.784] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
417.785] (II) Module modesetting: vendor=“X.Org Foundation”
417.785] compiled for 1.16.1, module version = 0.9.0
417.785] Module class: X.Org Video Driver
417.785] ABI class: X.Org Video Driver, version 18.0
417.785] (II) LoadModule: “fbdev”
417.785] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
417.786] (II) Module fbdev: vendor=“X.Org Foundation”
417.786] compiled for 1.16.1, module version = 0.4.4
417.786] Module class: X.Org Video Driver
417.786] ABI class: X.Org Video Driver, version 18.0
417.786] (II) LoadModule: “vesa”
417.786] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
417.786] (II) Module vesa: vendor=“X.Org Foundation”
417.786] compiled for 1.16.1, module version = 2.3.3
417.786] Module class: X.Org Video Driver
417.786] ABI class: X.Org Video Driver, version 18.0
417.786] (II) RADEON: Driver for ATI Radeon chipsets:

417.793] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
417.793] (II) FBDEV: driver for framebuffer: fbdev
417.793] (II) VESA: driver for VESA chipsets: vesa
417.793] (++) using VT number 8

…

417.856] (II) [KMS] Kernel modesetting enabled.
417.856] (WW) Falling back to old probe method for modesetting
417.856] (WW) Falling back to old probe method for fbdev
417.856] (II) Loading sub module “fbdevhw”
417.856] (II) LoadModule: “fbdevhw”
417.856] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
417.858] (II) Module fbdevhw: vendor=“X.Org Foundation”
417.858] compiled for 1.16.1, module version = 0.0.2
417.858] ABI class: X.Org Video Driver, version 18.0
417.858] (WW) Falling back to old probe method for vesa
417.858] (II) RADEON(0): Creating default Display subsection in Screen section
“Default Screen Section” for depth/fbbpp 24/32
417.858] (==) RADEON(0): Depth 24, (–) framebuffer bpp 32
417.858] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
417.858] (==) RADEON(0): Default visual is TrueColor
417.858] (==) RADEON(0): RGB weight 888
417.858] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
417.858] (–) RADEON(0): Chipset: “TURKS” (ChipID = 0x674a)
417.858] (II) Loading sub module “dri2”
417.858] (II) LoadModule: “dri2”
417.858] (II) Module “dri2” already built-in
417.858] (II) Loading sub module “exa”
417.858] (II) LoadModule: “exa”
417.859] (II) Loading /usr/lib64/xorg/modules/libexa.so
417.860] (II) Module exa: vendor=“X.Org Foundation”
417.860] compiled for 1.16.1, module version = 2.6.0
417.860] ABI class: X.Org Video Driver, version 18.0

6

are you referring to sudo zypper ?

no I did not log in as root. And Of course I if login as root and typed zypper I have the same output

7

Looks like you may be out of space.

While logged as root

df to see how much space you have left

try removing tmp files to free space

rm -R /tmp/.

this will clear the directory remember that as root you are god be very sure you type stuff right. removing things as root can remove all things if you are not careful always use the full path and don’t assume that you can use relative paths. As root rm will happily remove all things on your machine if you tell it to.

type reboot to reboot
see if that fixes things. You also may want to consider how much space you have allocated to the OS also may consider turning off snapper if you have less then 40 gig assigned to root partition

8 

/usr/bin/startx: line 227: cannot create temp file for here-document: *** No space left on device ***

Please, paste here the output of ‘df -h’

9

Would be good to see some absolute number (i.e. the free space in kilobytes or megabytes or gigabytes) instead of just the relative value (of percent of what?).

Please post the output of the command line calls

df

and

free
10

As general information snapper uses space on the partition but the normal Linux utilities don’t see that usages so may show a lot of free space but snapper has used it

11

Thanks for trying to help.

df -h

Filesystem Size Used Avail Use% Mounted on
/dev/sda3 50G 17G 34G 34% /
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 11M 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/sda3 50G 17G 34G 34% /var/spool
/dev/sda3 50G 17G 34G 34% /var/opt
/dev/sda3 50G 17G 34G 34% /var/log
/dev/sda3 50G 17G 34G 34% /var/tmp
/dev/sda3 50G 17G 34G 34% /.snapshots
/dev/sda3 50G 17G 34G 34% /var/lib/pgsql
/dev/sda3 50G 17G 34G 34% /var/lib/named
/dev/sda3 50G 17G 34G 34% /var/lib/mailman
/dev/sda3 50G 17G 34G 34% /var/crash
/dev/sda3 50G 17G 34G 34% /usr/local
/dev/sda3 50G 17G 34G 34% /tmp
/dev/sda3 50G 17G 34G 34% /srv
/dev/sda3 50G 17G 34G 34% /opt
/dev/sda3 50G 17G 34G 34% /boot/grub2/x86_64-efi
/dev/sda3 50G 17G 34G 34% /boot/grub2/i386-pc
/dev/sda4 37G 30G 4.8G 87% /home
/dev/sda1 203M 4.9M 198M 3% /boot/efi
/dev/sdc1 2.7T 805G 1.8T 31% /harddrive2
/dev/sdb1 2.7T 1.6T 1.1T 61% /harddrive1

and free

         total       used       free     shared    buffers     cached

Mem: 32938496 564856 32373640 10728 3476 225760
-/+ buffers/cache: 335620 32602876
Swap: 33551356 0 33551356

12

So your main problem seems to be that there’s no space left on your / partition, even though df tells otherwise. This is an “issue” with btrfs, snapshots can take a lot of space which is not shown as used by other tools.

Ok, as it happened during an update, you could remove the downloaded packages to gain space:

rm -r /var/cache/zypp

(when logged in as root)

And/or try to delete some snapshots. Run “yast snapper” as root to do so, this should work even in your situation.

Hope that helps.

13

If that is the case, this


btrfs filesystem show /dev/sda3

can tell us the real available free space on /dev/sda3.

14 
rm -r /var/cache/zypp

(when logged in as root)
[/QUOTE]

Done. I also did rm -R /tmp/. as suggested by another good soul …

And/or try to delete some snapshots. Run “yast snapper” as root to do so, this should work even in your situation.
Hope that helps.

yast snapper gave me an error.

Anyway I rebooted and it does not seem to work any better.
One more piece of info. Before stopping on the OK reaching target graphical interface, the computer hangs for a long time. If I press Alt F10 I can see this on the screen :
a lot error messages like :

chmod(/tmp/var/) failed. No space left on device
chmod(/tmp/) failed. No space left on device
chmod(/var/log/journal) failed. No space left on device
chmod(/tmp/.X11-unix) failed. No space left on device

Shall I delete these folder. Also when I login as user it still complains about space while I already deleted some files.

Can I delete var/log/snapper.log or zypper.log that are about 6MB each.

Thanks for helping ? I am loosing a day of work now and wondering if I sould not reinstall everything …but I have a lot of soft to installl

15

Try


btrfs filesystem show /dev/sda3
16

This is the output :

Label: none uuid: b0b549f2-6a2c-48d6-9a2a-b4c814775d6a
Total devices 1 FS bytes used 16.48GiB
devid 1 size 50.00GiB used 50.00GiB path /dev/sda3

Btrfs v3.16.2+20141003

not sure I understand it …

17

And what error?

You should at least be able to delete snapshots with snapper directly.
To list all snapshots:

snapper list

To delete snapshots:

snapper delete ###

where “###” should be replaced with the number of the snapshot.

You might also have to “rebalance” the filesystem, although I never had to do that in my cases when / was full…

btrfs fi balance start / -dusage=5

See also: SUSE Documentation

Shall I delete these folder. Also when I login as user it still complains about space while I already deleted some files.

You can, but I doubt it would help.
Those folders are just part of your / filesystem.

Can I delete var/log/snapper.log or zypper.log that are about 6MB each.

Yes. But again, it won’t help probably, if deleting /var/cache/zypp didn’t help.

18 
snapper list

Will print a list of currently stored snapshots.

You can delete them with snapper delete <number>.

Delete the 2 or 3 oldest and see if the situation improves.

19

rotfl! yeah!!!

Guys you save my day (or at least half of it).

I deleted the last three snapshot (includinng the zypper of this morning) and rebooted and my desktop is back !!!

thank you thank you thank you. What shall I do to avoid this happens again ?

20

So you deleted the newest 3 and not the oldest :wink:

You can configure snapper: man snapper-configs.
Just keep a low number of snapshots and set TIMELINE_CREATE to no in the proper configuration file (usually for the root filesystem it’s /etc/snapper/configs/root).