Update on the Kube flatpak nvidia driver issue

After some investigation into the nvidia driver issue, the flatpak has now been rebuilt based on the org.freedesktop.Platform runtime.
A limitation of flatpak currently keeps flatpak from making the appropriate driver available from any other runtime.

As a nice side-effect the overall size of the flatpak has been reduced by removing some unnecessary parts.

If you have already installed Kube, please follow the following instructions to update to the latest version (in all other cases, install it now):

Update to the latest version (please note this will also automatically install the new runtime and driver extensions):

flatpak -y --user update com.kolabnow.kube

To remove the no longer relevant platform, run the following commands:

flatpak --user uninstall org.kolab.Sdk
flatpak --user uninstall org.kolab.Platform

To check if the relevant driver was installed you can use the following command:

flatpak --gl-drivers

If you have an nvidia card, this should give you a line similar to (depending on your nvidia driver):

nvidia-384-90

To run kube, use:

flatpak run com.kolabnow.kube

Please let us know in the comments if this resolves the issue for you, thanks!

For more info about Kube, please head over to About Kube.

Kube flatpak not working with nvidia drivers

It was recently pointed out that the Kube flatpak for Kolab Now does not work with nvidia drivers, leaving you with error messages like this:

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Unrecognized OpenGL version
Unrecognized OpenGL version

As it turns out this is a problem with the extension system of flatpak that is used to provide the appropriate graphics driver to the application inside the container. It’s not quite clear what the best solution to the problem will be, but we’re working on it.

For more info about Kube, please head over to About Kube.

Pushing Support to our Enterprise Customer Support Platform

We are preparing a transition from our current platform underpinning the support@kolabnow.com email address — based on OTRS — to a more up-to-date, feature-rich environment based on Phabricator.

For various reasons, we much anticipate this change. Not in the least we’ll have real-time notifications about new tickets, and user responses, and a few chat rooms — it’ll allow us to sort our workload better.

Continue Reading “Pushing Support to our Enterprise Customer Support Platform”

Journey to the Center of Kube: Sink

Kube is a client that allows you to work offline, so you can work no matter whether your train just entered a tunnel, you’re on board of a plane or you’re just too lazy to get up and ask for the free wifi password. One implication of this is that we have to deal with fair amounts of data.

Email tends to accumulate quickly, and it’s not uncommon to have mail folders that have somewhere between 40’000 and 200’000 emails in them, so we have to figure out a way to deal with that. At the core of Kube we therefore have Sink; the data-access and synchronization system.

Continue Reading “Journey to the Center of Kube: Sink”

Experimenting with TOTP Two Factor Authentication

We’re currently experimenting with an implementation of TOTP-based 2 factor authentication, allowing our customers to use a second factor.

Until now, Kolab Now required its users to supply a username and a password. This is considered only a single factor, since the username is your email address and thus known to third parties.

Continue Reading “Experimenting with TOTP Two Factor Authentication”