I installed FreeBSD 9.0 amd64 and KDE4.8.4 on my USB, I have no problem rebooting from there... However, If I am logging as regular user, I can't start KDE4. I got message saying that can not run dbus, can you run qdbus. I have no problem if I am logging as root. Any clue?

Maybe dbus setted up only for root?

P.S. Qdbus is Qt dbus version. KDE uses Qt as interface theme.

Thx, it might be stupid question... how to set up dbus for regular user ?

Maybe this help for dbus setup.
http://www.linuxfromscratch.org/blfs/vi ... /dbus.html

D-Bus should not need any special setup.

Can you make sure that your user is able to read+write their home directory?
Also, if you start a fail safe session (should just have xterm) does running "dbus-launch" give any indication as to the cause of the problem (any error message, etc)?

If I remove ~/.xinitrc, the user can use standard xorg, with 3 x-term with no problem, and also read-write home directory. Right now, I am using gnome with the same user name, and has no problem with it. But I prefer KDE. BTW what do you mean fail - safe?

Usually (at least on openSUSE) a type of session called "Failsafe" is available in the Display Manager which does nothing more than launch a XTerm as the users session (instead of a full blown DE). This is quite handy for diagnosing faults such as this one.

Under GNOME, do you see a "dbus-daemon" process running under your user?

Honestly... I am new in gnome... this is my first gnome... so how to check dbus in gnome ?
Edit ... if u means from ps

Code: Select all

[irfan@irfan-pc ~]$ ps -auxw | grep dbus
messagebus  1204   0.0  0.1  14448   2656  ??  Is    5:41PM  0:00.15 /usr/local/bin/dbus-daemon --system
irfan       1493   0.0  0.1  14448   2512  ??  Ss    5:41PM  0:00.12 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-addres
irfan       1492   0.0  0.1  30252   2232  v0  I     5:41PM  0:00.00 dbus-launch --exit-with-session gnome-session
irfan       1770   0.0  0.0  16432   1120   2  RL+   5:59PM  0:00.00 grep dbus


It appears that dbus-daemon is being successfully executed under GNOME.
Have you been able try running "dbus-launch" in a single XTerm yet?

under gnome roxterm

Code: Select all

[irfan@irfan-pc ~]$ dbus-launch
DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-3SSibjifY5,guid=b95ab001fb2d9c054f4aacd400000dfc
DBUS_SESSION_BUS_PID=67150
[irfan@irfan-pc ~]$


during FreeBSD startup

Code: Select all

Additional ABI support: linux.
Clearing /tmp (X related).
Updating motd:.
Starting fusefs.
fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.19
Starting dbus.
re0: link state changed to UP
Starting hald.
Configuring syscons: blanktime.
Performing sanity check on apache22 configuration:
Syntax OK
Starting apache22.
Starting sshd.
Starting cron.
Starting background file system checks in 60 seconds.


The dbus-daemon instance started as part of the system boot is not relevant in this instance, as it is the system bus, while we are interested in the session bus.

The output from under GNOME looks normal and is what is expected.

If it helps, startkde uses the following invocation to run dbus-launch:

Code: Select all

dbus-launch --sh-syntax --exit-with-session

You need to run this outside of other desktop environments (including GNOME) however to get a more general idea if this is something KDE is doing wrong, or if it is something else.

OK, straight from the prompt (including reboot) without any window manager using the same username :

Code: Select all

DBUS_SESSION_BUS_ADDRESS='unix:path=/tmp/dbus-XEqR9FbTlI,guid=3d1c61e1016ce62f259ecd0500000086';
export DBUS_SESSION_BUS_ADDRESS;
DBUS_SESSION_BUS_PID=1429;


That looks normal as far as I can tell.
What does running "startkde" from the failsafe XTerm do? It should cause KDE to begin to startup.

OK... from KDM, I chosed KDE fail safe... and got the same message... hang after the 1st icon (the HD icon) showed up. BTW I just realized KDM could launch gnome as well....

I suspected that would occur. Yes, it is possible for KDM to start GNOME, and GDM should also be able to start KDE.

With regards to startkde - did you try running it from a xterm only session?
It may give more detailed output on the terminal as to why this is failing to startup.