KDE4 desktop crash in 12.1 after "playing" with mesa lib

:shame:My system is 12.1, official KDE4, systemd booted.

Yesterday, to install a new program I had to install a new version of mesa library from Xorg repository who itself updated several Xorg packages. After that the system restarted with a blank screen. Rebooting in failsafe mode I was able to get a console, deleted the Xorg repository (only the official repositories were left) and made a zypper dup, so I recovered the official packages. Now I can boot in normal mode (not failsafe needed) but I only get a console, from which I can start start programs or even IceWM desktop (typing it) but not KDE4. I have tried to set KDE4 or even IceWM as the default window manager in the login screen without success, I always get a console window.

Some help to login in KDE4 another time?

thanks in advance.

Have you tested a new user login?

You might tell us about your graphics device?

Yes I have tried with a new user with the same result: After login I get a small text window. If I start IceWM I get at least the full monitor size.

The graphics device is a Intel i915 with Kernel controler drm. I think the driver was Intel but now I don’t remember where to check it.

I think I doesn’t matter but this is a netbook that has been working OK for a year, the problem is that I screwed something (it’s the better way to learn) but I need some further steps to unscrew it again.

What happens if you login on the console and do

rckdm restart

The output is: “redirecting to systemctl
Failed to issue method call: Unit rcxdm.service failed to load: No such file or directory. See system logs and ‘systemctl status rcxdm.service’ for details.”

and, what does that say?
Also, immediately after the X server crashes/refuses to load, do

tail -20 /var/log/Xorg.0.log 

First, thanks for your help and sorry for my ignorance, I am just an user, I don’t have advanced skills. I would like to learn all this stuff a little bit in the better way, that is struggling with it but if at some point you think it’s not worth going on there is always the option of installing 12.1. The pity is that 12.3 is so close…

I didn’t realize ‘systemctl status rcxdm.service’ was a console command. The output is:
“Loaded: error (Reason: No such file or directory)
Active: inactive (dead)”

Just in case I tried the command ‘systemctl start rcxdm.service’ with the error:
“Failed to issue method call: Unit rcxdm.service failed to load. No such file or directory…”

system logs: I don’t know what to see. YAST has no entry for that (I think it had in the past) and googling I have seen they are in /var/log but I 'm lost there. The logical one kdm.log says messages go to the daemon .* syslog facility. Some help here?

“tail -20 /var/log/Xorg.0.log” : The output is:
423.922] (–) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
423.923] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
423.923] (II) No input driver/identifier specified (ignoring)
423.925] (II) config/udev: Adding input device PC Speaker (/dev/input/event7)
423.925] (II) No input driver/identifier specified (ignoring)
423.931] (II) config/udev: Adding input device Acer WMI hotkeys (/dev/input/event9)
423.931] () Acer WMI hotkeys: Applying InputClass “evdev keyboard catchall”
423.931] (
) Acer WMI hotkeys: Applying InputClass “evdev keyboard catchall”
423.931] () Acer WMI hotkeys: Applying InputClass “LocalKeyboard”
423.931] (II) Using input driver ‘evdev’ for ‘Acer WMI hotkeys’
423.931] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
423.932] (
) Acer WMI hotkeys: always reports core events
423.932] () Acer WMI hotkeys: Device: “/dev/input/event9”
423.932] (–) Acer WMI hotkeys: Found keys
423.932] (II) Acer WMI hotkeys: Configuring as keyboard
423.932] (
) Option “config_info” “udev:/sys/devices/virtual/input/input9/event9”
423.932] (II) XINPUT: Adding extended input device “Acer WMI hotkeys” (type: KEYBOARD)
423.932] () Option “xkb_rules” “evdev”
423.932] (
) Option “xkb_model” “evdev”
423.932] (**) Option “xkb_layout” “es”

Try

systemctl status xdm.service

EDIT: and please, post output between CODE tags (the # in the editor)


   MyPC:>systemctl status xdm.servicexdm.service - LSB: X Display Manager

      Loaded: loaded (/etc/init.d/xdm)
      Active: active (running) since Mon, 18 Feb 2013 14:34:02 +0100; 1min 10s ago
     Process: 794 ExecStart=/etc/init.d/xdm start (code=exited, status=0/SUCCESS)
      CGroup: name=systemd:/system/xdm.service
          ├ 821 /usr/bin/kdm
          └ 892 /usr/bin/Xorg -br :0 vt7 -nolisten tcp -auth /var/...

from a console. login to your user account, and post output of

cat /etc/sysconfig/displaymanager

and

su -c 'tail -40 /var/log/messages'

Output of cat /etc/sysconfig/displaymanager:

## Path:    Desktop/Display manager
## Description:    settings to generate a proper displaymanager config
## Type:    string(kdm,kdm3,kdm4,xdm,gdm,wdm,entrance,console)
## Default:    ""
#
# Here you can set the default Display manager (kdm/xdm/gdm/wdm/entrance/console).
# all changes in this file require a restart of the displaymanager
#
DISPLAYMANAGER="kdm"

## Type:    yesno
## Default:    no
#
# Allow remote access (XDMCP) to your display manager (xdm/kdm/gdm). Please note
# that a modified kdm or xdm configuration, e.g. by KDE control center
# will not be changed. For gdm, values will be updated after change.
# XDMCP service should run only on trusted networks and you have to disable
# firewall for interfaces, where you want to provide this service.
#
DISPLAYMANAGER_REMOTE_ACCESS="no"

## Type:    yesno
## Default:    no
#
# Allow remote access of the user root to your display manager. Note
# that root can never login if DISPLAYMANAGER_SHUTDOWN is "auto" and
# System/Security/Permissions/PERMISSION_SECURITY is "paranoid"
#
DISPLAYMANAGER_ROOT_LOGIN_REMOTE="no"

## Type:    yesno
## Default:    yes
#
# Let the displaymanager start a local Xserver.
# Set to "no" for remote-access only.
# Set to "no" on architectures without any Xserver (e.g. s390/s390x).
#
DISPLAYMANAGER_STARTS_XSERVER="yes"

## Type:        yesno
## Default:     no
#
# TCP port 6000 of Xserver. When set to "no" (default) Xserver is
# started with "-nolisten tcp". Only set this to "yes" if you really
# need to. Remote X service should run only on trusted networks and
# you have to disable firewall for interfaces, where you want to
# provide this service. Use ssh X11 port forwarding whenever possible.
#
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN="no"

## Type:    string
## Default:
#
# Define the user whom should get logged in without request. If string
# is empty, display standard login dialog.
#
DISPLAYMANAGER_AUTOLOGIN=""

## Type:        yesno
## Default:     no
#
# Allow all users to login without password, but ask for the user, if
# DISPLAYMANAGER_AUTOLOGIN is empty.
#
DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no"

## Type:        yesno
## Default:     no
#
# Display a combobox for Active Directory domains.
#
DISPLAYMANAGER_AD_INTEGRATION="no"

## Type:    list(root,all,none,auto)
## Default: auto
#
# Determine who will be able to shutdown or reboot the system in kdm.  Valid
# values are: "root" (only root can shutdown), "all" (everybody can shutdown),
# "none" (nobody can shutdown from displaymanager), "auto" (follow
# System/Security/Permissions/PERMISSION_SECURITY to decide: "easy local" is
# equal to "all", everything else is equal to "root").  gdm respects the
# PolicyKit settings for ConsoleKit. Shutdown configuration can be done via
# the polkit-default-privs mechanism.
#
DISPLAYMANAGER_SHUTDOWN="auto"
## Path:        Desktop/Display manager
## Type:        string(Xorg)
## Default:     "Xorg"
#
DISPLAYMANAGER_XSERVER="Xorg"
## Path:    Desktop/Display manager
## Description: settings to generate a proper displaymanager config
## Config:      kdm3
## Type:    string
## Default: 
#
# space separated list of users for which icons should be shown in KDM
# if empty, then take system defaults
#
KDM_USERS=""

## Type:    string
## Default: 
#
# Special greeting words in kdm
#
KDM_GREETSTRING=""

## Type:        string
## Default: 
#
# Defines extra Server Arguments given to the kdm display manager when
# starting a local display. Useful to override e.g. the -dpi setting.
# 
DISPLAYMANAGER_KDM_LOCALARGS=""

## Type:        string
## Default:     SUSE
#
# Define the theme to be used by kdm. If empty, the traditional login
# window is used (which lacks some features)
# 
DISPLAYMANAGER_KDM_THEME="SUSE"

## Type:    yesno
## Default:    yes
#
# Allow local access of the user root to your display manager. Note
# that root can never login if DISPLAYMANAGER_SHUTDOWN is "auto" and
# System/Security/Permissions/PERMISSION_SECURITY is "paranoid".
# This settings currently works only with KDM.
#
DISPLAYMANAGER_ROOT_LOGIN_LOCAL="yes"


Output of su -c ‘tail -40 /var/log/messages’:

Feb 18 15:08:02 majo dbus-daemon[783]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda
Feb 18 15:08:02 majo dbus-daemon[783]: helper(pid  1497): launched job udisks-helper-ata-smart-collect on /dev/sda
Feb 18 15:08:02 majo dbus-daemon[783]: helper(pid  1497): completed with exit code 2
Feb 18 15:35:00 majo kernel:  3679.565179] usb 1-1: new high speed USB device number 4 using ehci_hcd
Feb 18 15:35:00 majo kernel:  3679.681920] usb 1-1: New USB device found, idVendor=058f, idProduct=6387
Feb 18 15:35:00 majo kernel:  3679.681934] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 18 15:35:00 majo kernel:  3679.681945] usb 1-1: Product: Mass Storage
Feb 18 15:35:00 majo kernel:  3679.681953] usb 1-1: Manufacturer: Generic
Feb 18 15:35:00 majo kernel:  3679.681961] usb 1-1: SerialNumber: 2CCF0F24A7087624C91F
Feb 18 15:35:00 majo kernel:  3679.684223] scsi5 : usb-storage 1-1:1.0
Feb 18 15:35:00 majo dbus-daemon[783]: **** scsi_host ADDING /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host5/scsi_host/host5
Feb 18 15:35:00 majo dbus-daemon[783]: **** scsi_host IGNORING ADD /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host5/scsi_host/host5
Feb 18 15:35:01 majo kernel:  3680.685262] scsi 5:0:0:0: Direct-Access     Generic  Flash Disk       8.07 PQ: 0 ANSI: 2
Feb 18 15:35:01 majo kernel:  3680.686380] sd 5:0:0:0: Attached scsi generic sg1 type 0
Feb 18 15:35:01 majo kernel:  3680.687982] sd 5:0:0:0: [sdb] 4108288 512-byte logical blocks: (2.10 GB/1.95 GiB)
Feb 18 15:35:01 majo kernel:  3680.688728] sd 5:0:0:0: [sdb] Write Protect is off
Feb 18 15:35:01 majo kernel:  3680.688749] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
Feb 18 15:35:01 majo kernel:  3680.689340] sd 5:0:0:0: [sdb] No Caching mode page present
Feb 18 15:35:01 majo kernel:  3680.689356] sd 5:0:0:0: [sdb] Assuming drive cache: write through
Feb 18 15:35:01 majo kernel:  3680.692588] sd 5:0:0:0: [sdb] No Caching mode page present
Feb 18 15:35:01 majo kernel:  3680.692599] sd 5:0:0:0: [sdb] Assuming drive cache: write through
Feb 18 15:35:01 majo kernel:  3680.782260]  sdb: sdb1
Feb 18 15:35:01 majo kernel:  3680.784822] sd 5:0:0:0: [sdb] No Caching mode page present
Feb 18 15:35:01 majo kernel:  3680.784830] sd 5:0:0:0: [sdb] Assuming drive cache: write through
Feb 18 15:35:01 majo kernel:  3680.784839] sd 5:0:0:0: [sdb] Attached SCSI removable disk
Feb 18 15:35:01 majo dbus-daemon[783]: **** ADDING /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdb
Feb 18 15:35:01 majo dbus-daemon[783]: **** UPDATING /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdb
Feb 18 15:35:01 majo dbus-daemon[783]: **** ADDED /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdb
Feb 18 15:35:01 majo dbus-daemon[783]: **** EMITTING ADDED for /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdb
Feb 18 15:35:02 majo dbus-daemon[783]: **** ADDING /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb1
Feb 18 15:35:02 majo dbus-daemon[783]: **** UPDATING /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb1
Feb 18 15:35:02 majo dbus-daemon[783]: **** ADDED /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb1
Feb 18 15:35:02 majo dbus-daemon[783]: **** EMITTING ADDED for /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb1
Feb 18 15:37:18 majo su: (to root) majo on /dev/pts/0
Feb 18 15:37:50 majo su: (to root) majo on /dev/pts/0
Feb 18 15:38:02 majo dbus-daemon[783]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda
Feb 18 15:38:02 majo dbus-daemon[783]: helper(pid  1588): launched job udisks-helper-ata-smart-collect on /dev/sda
Feb 18 15:38:02 majo dbus-daemon[783]: helper(pid  1588): completed with exit code 0
Feb 18 15:38:02 majo dbus-daemon[783]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda
Feb 18 15:38:28 majo su: (to root) majo on /dev/pts/0


:XFinally I gave up and reinstalled the system, this time with 12.2.

:)Thank you for your help anyway.