How to fix the problem of "Cannot open display"?

[Dominik Reichardt]

Am 06.10.2009 um 16:42 schrieb Peng Yu:

>>>> So the instructions the port prints out are wrong? Is there a way  
>>>> to
>>>> correct them? It sounds like you're saying you need "sudo" to have
>>>> access to write the changes to the plist, but I remember from prior
>>>> discussions that this would cause the launchagent to be running  
>>>> as root,
>>>> when in fact we want the launchagent running as the current user.
>>
>> You are right, LaunchAgents/org.freedesktop.dbus-session.plist is  
>> meant
>> to be run by the current user, not root.
>>
>> And yes, the instructions look kind of wrong. launchctl load -w  
>> without
>> sudo does not work because it requires write access to the file.  
>> But if
>> -w is not used, the Disabled key will not be removed and it cannot be
>> loaded automatically at system startup time...
>>
>>> The bottom line is that the startupitem code needs some love. At  
>>> present
>>> it really can't handle anything beyond launchdaemons that will be
>>> started by root.
>>
>> dbus does not use the startupitem.* code for
>> org.freedesktop.dbus-sesstion.plist as it installs multiple plist  
>> files
>> which startupitem.* cannot handle.
>
> I don't understand what would be the solution to my problem. Could
> somebody let me know the detailed steps what I should do?

I would like to know that, too. It seems to me that dbus is not  
running correctly on SL and therefore KDE stuff is not running since  
kdeinit fails...

Dom