[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-mac
Subject:    [KDE/Mac] Re: trouble with snow leopard
From:       Jonas_Bähr <jonas.baehr () web ! de>
Date:       2010-12-31 16:15:24
Message-ID: C466D940-2518-410B-9224-3B5AF9896E85 () web ! de
[Download RAW message or body]

Hi,

Am 31.12.2010 um 00:48 schrieb Ben Brodie:

> Hello,
>
> I am trying to run KDE applications natively in mac os x. I  have  
> snow leopard. I have installed KDE4 through macports, and ran
>
>    # Don't forget that dbus needs to be started as the local
>    # user (not with sudo) before any KDE programs will launch
>    # To start it run the following command:
>    # launchctl load /Library/LaunchAgents/org.freedesktop.dbus- 
> session.plist
>    ##########################################################
>
>    ######################################################
>    #  Programs will not start until you run the command #
>    #  'sudo chown -R $USER ~/Library/Preferences/KDE'   #
>    #  replacing $USER with your username, followed by   #
>    #  'open /Applications/Macports/KDE4/kdeinit4.app'   #
>    #  in a Terminal.                                    #
>    ######################################################
>
> as instructed. When I go to the macports kde folder and double click  
> any application, they pop up in the dock, but there are no windows  
> associated with them.
>
> Note that I have reinstalled the KDE4 multiple times and ran 'update  
> outdated' as well.
>
> Most notably in Terminal:
> "ben-brodies-macbook:~ Ben$ launchctl load /Library/LaunchAgents/ 
> org.freedesktop.dbus-session.plist
> nothing found to load"

This looks like a dbus problem. It seems that the message you posed  
above from the kde ports isn't in sync with the latest dbus port [1]  
which installs the startup item in a different place. I suggest to  
file a bug report against macports kde port group.

[1] http://trac.macports.org/browser/trunk/dports/devel/dbus/Portfile

> Whats going on? Does KDE4 work on snow leopard?

Try to start a kde application in the terminal. Then you should see  
some output which may direct you to the source of the problem.

bye,
Jonas

> Thanks a lot,
> Ben
>
>
>
>
>
> -- 
> Benjamin L. Brodie
> Institute for Artificial Intelligence
> University of Georgia
> 518-334-3279
> blbrodie@gmail.com
>
> _______________________________________________
> kde-mac@kde.org
> List Information: https://mail.kde.org/mailman/listinfo/kde-mac
> KDE/Mac Information: http://techbase.kde.org/index.php?title=Projects/KDE_on_Mac_OS_X

_______________________________________________
kde-mac@kde.org
List Information: https://mail.kde.org/mailman/listinfo/kde-mac
KDE/Mac Information: http://techbase.kde.org/index.php?title=Projects/KDE_on_Mac_OS_X
[prev in list] [next in list] [prev in thread] [next in thread]