One of the most frustrating user experiences is when you get an error message that you can’t do anything about, or even worse, that you don’t even understand.
While it’s very well possible that the error message is entirely justified, wouldn’t it be great if the system didn’t just tell you that something is wrong, but also what you can do about it? Error messages can be even more infuriating if they block you from doing your work even if they are not directly related, thus interrupting your workflow unnecessarily. Wouldn’t you rather have a notification that something does not work as it should, while otherwise letting you go about what you wanted to do, instead of just popping up a blocking popup that you have to click away before you can do anything else?
If you ever wanted to try Kube a great way to do so is with a Kolab Now account. You will not only reap the benefits of using an secure, Switzerland hosted Open Source service, but you will also help sustain the development of Kube.
Kube now sports a sign-up link, allowing you to sign up directly from the setup page, which will result in a Kube Kolab Now account.
The Kube Kolab Now account is special in that its feature set will follow the Kube feature set, and so will its price. So if you sign up now, for a more limited feature set, you not only benefit from a reduced price but also receive free upgrades in the future as we’re adding new features to Kube! You can still take advantage from the web interface from the beginning though, if you want to complement Kube with that.
Even if you are not sure if you want to take out a subscription, the 30 day trial allows you to test the service and get a full refund if you’re not satisfied.
While working on our flatpak build infrastructure I noticed that the flatpak is much larger than it should be. After quickly digging into the flatpak one of the culprits was quickly found; a bunch of unnecessary files such as include files were left.
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.
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.