• 1
xguest doesn't have permissions to talk to NM, and NM at this point doesn't auto-connect to any network (or if it did, the xguest user might need to change that). So, while it will start firefox, it can't connect anywhere because NM hasn't brought up a network interface.

Re: NetworkManager

(Anonymous)
NetworkManager shouldn't have to talk to any of the xguest user processes.
If for some reason it really can't set up a network connection without communicating with processes owned by the user logged in to the console, there are alternative ways to handle network management.

Re: NetworkManager

This is by design. I didn't want a kiosk user to be able to change the network settings on the machine. You can customize policy to allow this, though.

require {
type xguest_t;
}

#============= xguest_t ==============
networkmanager_dbus_chat(xguest_t)

This will allow the xguest user to run nm-applet to communicate with the NetworkManager. You would need to use sabayon to read nm-applet as a application on startup also.

With Kiosk you can create profiles that are attached to users or groups of users. A profile can define any KDE setting, but usually includes the contents of the desktop, panel, and K Menus, as well as the choice of wallpaper, default fonts, and widget style.

Here you go: —- ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ ssid=”tangent” key_mgmt=WPA-PSK psk=”network key goes here” priority=2 } network={ ssid=”adlnet” bssid=xx:xx:xx:xx:xx:xx key_mgmt=WPA-PSK psk=”network key goes here” } —- Btw, if you have DHCP set up, it could very long to obtain IP address or it could even never get it (request timeout), however network interface should be brought up (you can see ethX up, but with no IP assigned).

  • 1
?

Log in