[FreeNX-kNX] FreeNX on Suse 10.1

[walter harms]

hi serge,
thx for the hints.

did you try to start fvwm2 also or kde/gnome only ?

re,
  wh

Serge Weinstock wrote:
> Serge Weinstock wrote:
>> Hi,
>>
>> I'm trying to use FreeNX on a Suse 10.1 box and I've run into several
>> problems.
>>
>> * The first one was that I wasn't able to get any sound. I solved that
>> by making my account a member of the group audio.
>>
>> * The second one was a recurring warning message about the power save
>> daemon not running and about dbus problems.  I solved that by using the
>> default X client script for logging in.
>>
>> * The third and still unsolved problem is that I'm unable to mount
>> devices like the DVD drive or a USB key through KDE or Gnome UI. When I
>> try, I get the following cryptic error message:
>>  'A security policy in place prevents this sender from sending this
>> message to this recipient, see message bus configuration file (rejected
>> message had interface "org.freedesktop.Hal.Device.Volume" member "Mount"
>> error name "(unset)" destination "org.freedesktop.hal"'
>>
>> This happens only when I use my normal login. If I logged as root, I
>> don't get any problem.
>>
>> Any idea on what is going wrong ?
>>
>> Thanks in advance,
>>
>> Serge
>>
> 
> I have finally solved all my problems!
> As it can be useful to others, here is my recipe:
> 
> * If you want remote users to have access the audio devices,  make them 
> members of the audio group. This is very useful for people like me who 
> use their computer as a jukebox and want to be able to access it remotely.
> 
> * The commands for launching KDE or GNOME are no more "startkde" and 
> "gnome-session". A lot of applications now use dbus (message bus daemon) 
> as a system wide mean for applications to talk to each others. So a 
> specific dbus daemon must be launched for your session and a global 
> environment variable must be set in order for applications to know to 
> which dbus  daemon to talk to.
> This can be done  by replacing  the  following lines  in  
> /etc/nxserver/node.conf :
> COMMAND_START_KDE='/usr/bin/dbus-launch --sh-syntax --exit-with-session 
> /opt/kde3/bin/startkde'
> COMMAND_START_GNOME='/usr/bin/dbus-launch --sh-syntax 
> --exit-with-session /opt/gnome/bin/gnome-session'
>  
> * if you want your remote users to have access to removable medias like 
> CDs or USB keys, you must first get dbus working as  explained above, 
> secondly configure  HAL to allow  these users to  access remotely the 
> devices.
> 
> For that:
> + add a group "powerusers" and make the desired users members of this group
> + edit /etc/dbus-1/system.d/hal.conf and add the lines:
>   <policy group="1000">
>     <allow 
> send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/>
>     <allow send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>
>     <allow send_interface="org.freedesktop.Hal.Device.Volume"/>
>     <allow send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
>  </policy>
> 
> just before the final </busconfig>
> replace 1000 by the ID of the powerusers group.
> + reboot the system
> 
> And it works!
> 
> Serge
> 
> 
> 
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/ 
> 
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
> 
> 
>