X11/xdm issue on login

English Install/Boot/Login
1

Hi,

I started to have an odd issue when I boot up 13.1 it gets to just before the login screen(not actually getting there) and hangs. If I switch to different tty and login as root and do

service xdm start

I get another tty with fully working graphical interface. When I check with

systemctl status xdm.service

It reports back that xdm is inactive and error With Loading LSB: Display manager (Or something to that effect)

I checked the kdm log and got the following

.
.
.
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
klauncher(1654) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(1648)/kdecore (KTimeZone): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: “Not connected to D-Bus server”

kdmgreet(1648)/kdecore (KTimeZone): No time zone information obtained from ktimezoned

and in Xorg log grepping for (EE)

90.310] Current Operating System: Linux 3.11.10-29-desktop #1 SMP PREEMPT Thu Mar 5 16:24:00 UTC 2015 (338c513) x86_64
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
90.430] Initializing built-in extension MIT-SCREEN-SAVER
90.587] (EE) AIGLX error: dlopen of /usr/lib64/dri/i965_dri.so failed (/usr/lib64/dri/i965_dri.so: cannot open shared object file: No such file or directory)
90.588] (EE) AIGLX: reverting to software rendering
90.588] (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
90.588] (EE) GLX: could not load software renderer
90.885] (EE) evdev: TPPS/2 IBM TrackPoint: ioctl EVIOCGBIT for bitmask in EvdevOpenMTDev failed: Inappropriate ioctl for device
90.885] (EE) TPPS/2 IBM TrackPoint: Couldn't open mtdev device
90.895] (EE) PreInit returned 2 for "TPPS/2 IBM TrackPoint"

Any ideas why xdm doesn’t start properly on bootup?

2

Better use:

systemctl start xdm.service

I checked the kdm log and got the following

That’s normal and doesn’t indicate any problem.

and in Xorg log grepping for (EE)

Well, your system installation seems to be broken:

 90.587] (EE) AIGLX error: dlopen of /usr/lib64/dri/i965_dri.so failed (/usr/lib64/dri/i965_dri.so: cannot open shared object file: No such file or directory)
 90.588] (EE) AIGLX: reverting to software rendering
 90.588] (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
 90.588] (EE) GLX: could not load software renderer

Reinstall Mesa.

sudo zypper in -f Mesa
3

Do you have NVIDIA GPU or is the machine an optimus notebook and have you been experimenting with NVIDIA drivers???

4

It’s thinkpad X230 with intel graphics

5

Done that, still hangs at regular boot but if I manually start xdm from different terminal it works fine.

I did recently disabled X11 repo I had linked from the build service. Now I have some packages hanging from regular openSUSE repo and some really new from X11 I disabled. Is there a way to switch them easily from one to another?

6

When you manually start it later, does the Xorg log then also contain those errors?
Or are they gone now completely?

Can you please post the exact output of “systemctl status xdm” (run as root) right after boot when it failed to start?

I did recently disabled X11 repo I had linked from the build service. Now I have some packages hanging from regular openSUSE repo and some really new from X11 I disabled. Is there a way to switch them easily from one to another?

Well, you could run “zypper dup”, but that can be problematic if you have a lot of additional repos.

7

I needed a working system so I ended up updating the ssystem to 13.2. The login now works, but the whole boot process is really slow! I mean 2-3 minutes to get to login screen.

Which makes me think that there is a lingering setup issue still on the system?

8

Run “systemd-analyze blame” and “systemd-analyze critical-chain” to find out what is taking so long.

9

Result from systemd-analyze critical-chain

graphical.target @1min 58.031s
└─multi-user.target @1min 58.031s
  └─vboxdrv.service @1min 57.152s +879ms
    └─remote-fs.target @1min 57.150s
      └─remote-fs-pre.target @1min 57.139s
        └─nfs.service @1min 56.767s +372ms
          └─network-online.target @1min 56.766s
            └─network.target @1min 56.766s
              └─NetworkManager.service @1min 31.434s +25.319s
                └─SuSEfirewall2_init.service @1min 31.328s +105ms
                  └─basic.target @1min 31.252s
                    └─timers.target @1min 31.252s
                      └─systemd-tmpfiles-clean.timer @1min 31.252s
                        └─sysinit.target @1min 31.251s
                          └─sys-fs-fuse-connections.mount @1min 31.339s +1ms
                            └─systemd-modules-load.service @814ms +98ms
                              └─systemd-readahead-replay.service @680ms +126ms
                                └─system.slice
                                  └─-.slice

Result form systemd-analyze blame

         
          25.319s NetworkManager.service
          7.991s systemd-cryptsetup@cr_ata\x2dST500LM000\x2d1EJ162_W37227QR\x2dpart2.service
          2.221s cups.service
          1.799s systemd-udev-settle.service
          1.222s postfix.service
           879ms vboxdrv.service
           523ms lvm2-activation-early.service
           462ms dev-mqueue.mount
           461ms sys-kernel-debug.mount
           376ms SuSEfirewall2.service
           372ms nfs.service
           371ms systemd-tmpfiles-setup-dev.service
           366ms systemd-fsck-root.service
           363ms lvm2-activation.service
           352ms postgresql.service
           351ms systemd-fsck@dev-system-home.service
           341ms dev-hugepages.mount
           308ms systemd-udev-trigger.service
           308ms boot.mount
           289ms display-manager.service
           277ms apparmor.service
           212ms dev-system-swap.swap
           178ms systemd-tmpfiles-setup.service
           165ms systemd-fsck@dev-disk-by\x2did-ata\x2dST320LT007\x2d9ZV142_W0Q9D5NR\x2dpart1.service
           157ms vboxadd.service
           150ms systemd-readahead-collect.service
           148ms udisks2.service
           133ms systemd-journald.service
           126ms systemd-readahead-replay.service
           124ms systemd-udev-root-symlink.service
           105ms SuSEfirewall2_init.service
            98ms systemd-modules-load.service
10

Doesn’t look bad.
The longest is NetworkManager which takes 25 seconds.

Does your system boot faster if you switch to wicked in YaST->Network Devices->Network Settings->Global Options?

Also, try to disable nfs.service. Maybe a network share mount delays the boot (although that should probably show up in the systemd-analyze output, I’m not sure).