puavo-org / puavo-os Goto Github PK

To ensure OpenVPN manages to open a tunnel even when the host is unable to maintain a valid wall clock time (e.g. due to empty batteries).

Booting an unregistered device ends up to Lightdm login screen instead of device registration.

CSR sent by the client generates the following error at the CA server:

OpenSSL::X509::RequestError (nested asn1 error):
app/models/certificate.rb:12:in `initialize'
app/models/certificate.rb:12:in `new'
app/models/certificate.rb:12:in `sign_certificate'
app/controllers/certificates_controller.rb:68:in `block in create'
app/controllers/certificates_controller.rb:67:in `create'

And hence it fails to create and return a signed certificate.

If libssl1.0.0 is downgraded to 1.0.1e-2+deb7u20, registration works as expected.

The priority use for autopilot in production systems is to test the system functionality with smoketest to make sure that on network booting devices

• pxe boot works normally
• login works normally

Autopilot is launched from the bootserver and it creates a new virtual device, boots it with pxe and logs in. After login it reports about successful login, logs out and removes the created device and test user.

Autopilot can also be used for stress testing system or hardware.

This is probably due to changed desktop-file names /usr/share/applications/org.gnome.Nautilus.desktop

In some cases, according to strace -p, /usr/bin/xinit seems to sleep forever after forking a child (child becomes defunct) and hence blocks /usr/lib/puavo-ltsp-client/xinitrc which is used as a display setup script for lightdm.

This bug was noticed on a relatively slow machine, Shuttle SFM27 (Intel Atom).

The daemon should

• lock the database file
• reply to parameter queries via DBus
• be spawned by systemd or on-demand

On fatclients, there are redundant (and potentially harmful) services running, such as nslcd and avahi-daemon.

There are two instances of puavo-remote-assistance-applet running in user sesssions (two icons in the bar).

Previously we have used LightDM with Unity Greeter but as it is not available at Debian we might have to consider alternatives.

Current features at the login screen include:

• ui element (currently at the panel) with options to 1. allow remote access, 2. clock, 3. shutdown (reboot, poweroff, suspend), 4. open virtual keyboard (needed for touch screen and virtual whiteboards), 5. choose network connection (wifi/ethernet), 6. view battery status (on laptops), choose keyboard layout (finnish, russian, dvorak, arabic...)
• possibility to enter your username and password by typing
• on personal devices/laptops possibility to select username from a list of people who have previously used the computer (owner of the computer as a default)
• possibility to log in as a guest (this can be set on and off)
• information about: device type, device hostname, system version

Login screen is an UI element that typically everyone see during the day. Therefore it should be considered that:

• It would look aesthetically good
• Would be a good place for sharing mutual information

Possible alternatives include

• Lightdm with a different greeter (Webkit, razor-qt, kdm, gtk..)
• GDM3
• Packaging Unity greeter for Debian

It should be hidden by default, most of the users do not need it. Optionally, a configuration parameter to show/hide it could be introduced to support VPN users.

In Ubuntu-images, it was started by Upstart. Now it need to be converted to systemd service unit.

Display settings made via Puavo xrandr settings or Gnome display settings tool doesn't work.

NetworkManager competes with puavo-wlanap for wireless interfaces.

It seems that there isn't any real need for bundling facter, Debian's own version should be used.

[ 3446.098039] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[ 3446.098171] rt2800usb 2-1.1:1.0: firmware: failed to load rt2870.bin (-2)

Add opensource Ubuntu font http://font.ubuntu.com/

Currently, configuration database is only accessible by root and only for a one caller at a time. However, it should be possible to make multiple parameter queries simultaneously and also by desktop session users.

From an application programmer's point of view, everything should be hidden behind existing configuration interfaces (libpuavoconf, puavo/conf -Ruby module and puavo-conf command).

hostapd outputs the following error message:

iapp_init - bind[UDP]: Address already in use
iapp_deinit - setsockopt[UDP,IP_DEL_MEMBERSHIP]: Cannot assign requested address
IEEE 802.11F (IAPP) initialization failed.

The second login succeeds if waited for 20secs after the first login.

gedit, calculator, screenshot, file-roller and cheese are missing from the menu.

It does not configure IPv4 automatically.

This happens at least on unregistered hosts. Boot sequence ends up to just getty, no darkdm is started.

Install and run rngd at least on accesspoints.

If basic rates are not configured, hostapd's default value should be used.

Display setting view just displays 'Could not get screen information'.

lightdm pam stack exits with the following error:

/usr/lib/puavo-ltsp-client/pam/open-session failed: exit code 98

This is because puavo-rest-client fails.