I doubt that this is KDE-specific.

Sorry, but don't do stupid things like install old packages only because someone say it in a forum. Use the package we delivered with 10.3 final.

Please install the actual version and try again. If it happen again: is it a remote session? Is there XDG_SESSION_COOKIE in the environment of the user? Is ConsoleKit running?

Well, I'm sorry that you, Danny Kukawka, can't read English.

The error access happen first, without installation of any third party repositories.

With no posted solution from Novell or OpenSuSE except this track:
http://suseforums.net/index.php?showtopic=39754

Still it did not resolve.

Apparently I'm not the only one, please leave your comfortable palace and look at the other OpenSuSE forums.

Anyway, OpenSuSE 10.3 64bit sucks, big time, compare with OpenSuSE 10.2 64bit.

I'm going back to 32bit.

Solve it if you wish, I don't really care!

I have the same bug with the 32bit version. I installed 10.3 with DVD upgrade from 10.2.

-No remote session

-env | grep XDG
XDG_CONFIG_DIRS=:/etc/xdg
XDG_DATA_DIRS=/usr/local/share:/usr/share:/etc/opt/kde3/share:/opt/gnome/share:/opt/kde3/share

-ConsoleKit is not running, although it should be running according to the runlevel editor in runlevels 2,3,5. 

cat /var/log/boot.msg | grep ConsoleKit results this:
Starting ConsoleKit.<notice>startproc: execve (/usr/sbin/console-kit-daemon) [ /usr/sbin/console-kit-daemon ], [ CONSOLE=/dev/console ROOTFS_FSTYPE=ext3 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317 RUNLEVEL=5 PWD=/ SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-1024x768.cfg PREVLEVEL=N LINES=44 HOME=/ SHLVL=2 splash=silent SPLASH=yes ROOTFS_BLKDEV=/dev/sda7 _=/sbin/startproc DAEMON=/usr/sbin/console-kit-daemon ]

I hope these informations help.

(In reply to comment #3 from Joshua Frasir Chan)
> Well, I'm sorry that you, Danny Kukawka, can't read English.

Dude, what's your problem. If you start to diss me you should leave bugzilla now!

[...] 
> Still it did not resolve.

Why should it? This is not a update this was a downgrade to a really old beta version!

> Apparently I'm not the only one, please leave your comfortable palace and look
> at the other OpenSuSE forums.

Again: If you start to diss me ....

(In reply to comment #5 from Danny Kukawka)
> (In reply to comment #3 from Joshua Frasir Chan)
> > Apparently I'm not the only one, please leave your comfortable palace and look
> > at the other OpenSuSE forums.

Btw. It's not out job to monitor any existing forum in the net. We have mailinglist and as fist place bugzilla for this.

And if you would answer my questions instead of diss me we could fix the bug.

(In reply to comment #4 from Nils Reuter)
> cat /var/log/boot.msg | grep ConsoleKit results this:
> Starting ConsoleKit.<notice>startproc: execve (/usr/sbin/console-kit-daemon) [
> /usr/sbin/console-kit-daemon ], 

Could you attach /var/log/boot.msg?

Created attachment 178875 [details]
/var/log/boot.msg

(In reply to comment #6 from Danny Kukawka)
> (In reply to comment #5 from Danny Kukawka)
> > (In reply to comment #3 from Joshua Frasir Chan)
> > > Apparently I'm not the only one, please leave your comfortable palace and look
> > > at the other OpenSuSE forums.
> 
> Btw. It's not out job to monitor any existing forum in the net. We have
> mailinglist and as fist place bugzilla for this.
> 
> And if you would answer my questions instead of diss me we could fix the bug.
> 

OK, I'm sorry.

I can't provide any info now as I've removed all (2 PCs + 1 Notebook) 64bit OpenSuSE 10.3 installation. The error is causing serious storage issue.

Will install the 64bit version on a test machine and send you the log when available.

For us, at least, it does not happen to any of the 32bit installation (2 PCs).

Good luck.

The same bug hapened with my laptop (CoreDuo) after installing fresh 32bit openSUSE 10.3, but everything just works fine on my desktop (AMD Barton 3200+) with same software setup (default).

revert last flag changes. note to Priority field: "This field describes the importance and order in which a bug should be fixed. This field is utilized by the programmers/engineers to prioritize their work to be done"

Sometimes I have this issue too on my laptop (fresh 32bit install). 

A system reboot usually solves the problem. If not, than I have to do another reboot.

Since someone suggested to switch off parallel service loading to workaround this issue, I suspect that this is a race condition in the boot sequence.
(Yast -> System -> /etc/sysconfig editor -> System -> Boot -> RUN_PARALLEL = no)

syslog contains:
console-kit-daemon[2717]: WARNING: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

May I suggest changing the bug summary to 'ConsoleKit not starting on boot due to possible race condition'.

We currently have several bugs where we think they actually have the same reason (boot sequence). But we're still waiting for responses. If we're right, the outcome would be a D-Bus update, which is somehow, aehm, tricky ;-) So we need to make sure that it's really D-Bus which is at fault.

Please follow the instructions from bug 333735, comment #12 and report whether this helps. Thanks.

*** This bug has been marked as a duplicate of bug 331002 ***