KDM error when log in

English Applications
1

Hello,
I am experiencing a small problem. Anytime I try to log in after a reboot I get an error “an important problem has occurred and log in is not possible”.
and then I try again and it works. the log says that dbus is not working but it is !

dbus                      0:off  1:off  2:on   3:on   4:off  5:on   6:off

Any ideas ?

Thanks

/var/log/messages

X.Org X Server 1.10.4
Release Date: 2011-08-19
X Protocol Version 11, Revision 0
Build Operating System: openSUSE SUSE LINUX
Current Operating System: Linux computer01 3.1.2-1.4-desktop #1 SMP PREEMPT Mon Mar 19 12:38:11 CET 2012 x86_64
Kernel command line: root=/dev/disk/by-id/scsi-35000cca0055cd44c-part2 resume=/dev/disk/by-id/scsi-35000cca0055cd44c-part1 splash=silent quiet nomodeset
Build Date: 10 November 2011  03:34:36PM
 
Current version of pixman: 0.24.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 26 10:40:19 2012
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
klauncher(6772) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(6768)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server" 

kdmgreet(6768)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
2

Looks like something is wrong with your KDE install, or with the X-server. Please post output of


zypper lr -d

and


ls -l /etc/X11
3

zypper lr -d

# | Alias                                    | Name                                     | Enabled | Refresh | Priority | Type   | URI                                                                             | Service
--+------------------------------------------+------------------------------------------+---------+---------+----------+--------+---------------------------------------------------------------------------------+--------
1 | Mises-à -jour-pour-openSUSE-12.1-12.1-1.4 | Mises à jour pour openSUSE 12.1 12.1-1.4 | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/12.1/                                       |        
2 | VLC                                      | VLC                                      | Yes     | Yes     |   99     | rpm-md | http://download.videolan.org/pub/vlc/SuSE/12.1                                  |        
3 | google-chrome                            | google-chrome                            | Yes     | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                             |        
4 | openSUSE-12.1-12.1-1.4                   | openSUSE-12.1-12.1-1.4                   | Yes     | No      |   99     | yast2  | cd:///?devices=/dev/disk/by-id/ata-HL-DT-ST_DVD+_-RW_GH50N_K1YACE32536,/dev/sr0 |        
5 | repo-debug                               | openSUSE-12.1-Debug                      | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/debug/distribution/12.1/repo/oss/                  |        
6 | repo-debug-update                        | openSUSE-12.1-Update-Debug               | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/debug/update/12.1/                                 |        
7 | repo-non-oss                             | openSUSE-12.1-Non-Oss                    | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.1/repo/non-oss/                    |        
8 | repo-oss                                 | openSUSE-12.1-Oss                        | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.1/repo/oss/                        |        
9 | repo-source                              | openSUSE-12.1-Source                     | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/source/distribution/12.1/repo/oss/

ls -l /etc/X11


ls -l /etc/X11
total 64
-rw-r--r-- 1 root root 1353 Apr 12  2003 Xmodmap
-rw-r--r-- 1 root root 1049 Jun 20  2001 Xmodmap.remote
-rw-r--r-- 1 root root 4017 Apr 22  2009 Xresources
drwxr-xr-x 2 root root 4096 Mar 16 12:22 fs
drwxr-xr-x 2 root root 4096 Mar 16 12:22 lbxproxy
drwxr-xr-x 2 root root 4096 Mar 16 12:22 proxymngr
-rw-r--r-- 1 root root  954 Oct 29 23:29 qtrc
drwxr-xr-x 4 root root 4096 Mar 16 12:22 rstart
drwxr-xr-x 2 root root 4096 Mar 16 12:22 xdm
-rw-r--r-- 1 root root 5708 Oct 22 21:29 xim
drwxr-xr-x 2 root root 4096 Nov 10 18:14 xim.d
drwxr-xr-x 3 root root 4096 Mar 16 12:22 xinit
-rw-r--r-- 1 root root 1336 Mar 19 13:04 xorg.conf
drwxr-xr-x 2 root root 4096 Mar 16 12:10 xorg.conf.d
-rw-r--r-- 1 root root  849 Mar 16 11:45 xorg.conf.install
4

As it seems to be an openSUSE 12.1 system (we know not because the OP told us in the first line of his thread, but as a by-product of his repos listing >:(), could this be a systemd effect? Loging in while the system is not completely booted?

5

The thing is I cannot prevent user from logging in and there is no way to know if the system has completely started. As soon as the logon screen appears users will think it’s booted. So Is Is the only way to deal with it to warn them or could I make dbus start before ?

Thanks

6

I agree with what you say. But I only offered a possible cause. As long as we are not sure that it is the cause, we can ahrdly talk about a solution (or on how terrible it is).

Thus, my suggestion was (apart from comment from others that may say to me: that is a lousy suggestion), to test this by e.g.

  • boot, then wait for about one minute (or until the disk light stops flivckering showing still boot activity) and then doing a first login to see what it does.
  • booting sysvinit instaed of systemd and then of course login like a mad man as soon as the login screen is there.

When systemd is proven to be the culprit, you could decide to use sysvinit permanently (until systemd does better in a future openSUSE) and may be file a bug report (id there isn’t not allready one).

7

boot, then wait for about one minute (or until the disk light stops flivckering showing still boot activity) and then doing a first login to see what it does.

I am going to try this to know how long takes the system to be ready.

booting sysvinit instaed of systemd and then of course login like a mad man as soon as the login screen is there.

I am already using sysvinit instead of systemd-sysvinit. systemd-sysvinit was provoking some problems with automount.

Thanks

8

When you are allready using sysvinit, my suggestion is a dead alley.