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.
Earlier this morning, at 04:38 UTC, one out of the twenty-two IMAP backends in production stopped serving its mail spool, showing Input/Output errors on its disk. Our Standard Operating Procedure is to examine log files, flush vm caches, stop the virtual machine, and start it back up again. This occurred at 05:48 UTC. The IMAP backend in question did not come back up cleanly.
As we recently announced, we have pursued an opt-in second factor authentication feature on Kolab Now. As described, the implementation is limiting users to the web client, and this requires some reconfiguration of various servers and services.
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.
We are preparing a transition from our current platform underpinning the firstname.lastname@example.org 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.