Projects/KDE on Solaris/OpenSolaris/Status
Parent: KDE on OpenSolaris
When installing one of the latest development builds of KDE4 on OpenSolaris (2009.06), there's a number of changes to do to make the use of the desktop more convenient. Some of the suggested changes are below.
This page also lists some yet unresolved and highly visible problems with no workaround.
See also the list of known bugs.
Is disabled in a fresh installation. Execute
gnome-appearance-properties and select some better option in Fonts.
Seems to be fixed in 4.3.90 and b130.
nwam-manager is spawned multiple times
Was tracked as 205529. KDE4 session is started with multiple instances of nwam-manager. As a result, systray has multiple nwam-manager icons.
There's an easy workaround, add the following to ~/.kde/share/config/ksmserverrc to [General] section:
More details in 205529.
Akonadi seems misconfigured
After login an akonadi error window is shown. You can get rid of the errors by calling
kwriteconfig --file kres-migratorrc --group Migration --key Enabled --type bool false
although a patch would be better.
Missing Reboot and Shutdown
Broken screen lock
Tracked as 184465. xlock can be used as a workaround. It could also be convenient to undefine the Ctrl+Alt+L shortcut and use
System Settings -> Input Actions to redefine this shortcut to xlock.
To disable default shortcut:
System Settings -> Global Keyboard Shortcuts -> Run Command Interface -> "Lock Session" (remove the shortcut)
To enable Ctrl+Alt+L as Input Action to spawn xlock:
System Settings -> Input Actions right-click the left pane -> New -> Global Shortcut -> Command/URL Trigger -> define shortcut Action -> Command/URL -> xlock
Colission with SUNWvboxguest
When built and/or executed in a VirtualBox instance, there's a collision with the SUNWvboxguest package (VirtualBox guest additions). While building, this results in following sort of build error in FOSSqt:
Undefined first referenced
symbol in file
When using succesfully built packages in VirtualBox the KDE session startup fails.
This needs to be resolved in the build system. This is reported as http://www.virtualbox.org/ticket/6030