KDE tries to be as much customizable as possible: All freedom to the user! This leads to an extended configuration that might be confusing to new users. Additionally, modules from different sources are aggregated in a way that not necessarily fits the mental representation of users. For instance, the distinction between ‘workspace appearance’ and ‘window appearance’ is not common in other desktop environments.
‘May the fork be with you’ is a term we often hear in the free software community as it’s extremely easy to take the code and fork it to scratch your etch. What’s really difficult (and that’s something really counts) is to actually come together, collaborate and merge code-base to create something which helps more people, which is not just about scratching your own itch, but to do something which benefits more and more people.
Remember Playkot's Supercity? Game artist Paul Geraskin liked has just started a crowdfunding campaign to support working on a new indie game, inspired by Howard Lovecraft: Road to Providence. As with Supercity, Road to Providence will be created with open source tools: Krita, Blender, and jMonkeyEngine.
The 14.04 release of Unity unfortunately shipped with a few security vulnerabilities in the newly introduced screenlocker. As we will also ship a reworked screenlocker in Plasma Next I started to do another code audit, add more unit tests and try to make the code easier to understand and maintain. Furthermore I think it’s a good reason to explain how screenlockers work in general on X11 (and why it is easy to introduce security vulnerabilities) and the screenlocker in Plasma Next in particular. To make one thing clear: this post is not meant to shame Ubuntu for the issues. Some of these whoopies would have been possible in Plasma, too, and that’s the reason why I looked at the code again in more detail. On the other hand I think that our screenlocker in Plasma Next could be a solution for Unity’s use cases and I would appreciate if Ubuntu would adpot our solution.
For quite a while now the KDE team has been severely understaffed. We maintain
a lot of packages, with many different kinds of bugs, but we don’t have enough
people to do all the work that needs to be done. We have tools that help us
automate the update to new upstream releases, but that’s just the tip of the
iceberg of our work and so we are writing to invite more people to get
involved in the team and help us get KDE software in Debian into better shape.
Firefox has extra features that Konqueror doesn't have and the add-ons might be a deal breaker for some people. The page rendering worked perfectly on every site I tried and to be honest I use it everyday so if it didn't work I wouldn't use it.
Konqueror would be fine for most circumstances but there was at least one example of a page not rendering properly. This could be the reason that openSUSE ships with multiple browsers.
Have you used Konqueror? What have been your experiences?
Packages for the release of KDE's document suite Calligra 2.8.1 are available for Kubuntu 12.04 LTS and 13.10. You can get it from the Kubuntu Backports PPA (alongside KDE SC 4.13). They are also in our development release.
Bugs in the packaging should be reported to kubuntu-ppa on Launchpad. Bugs in the software to KDE.
To update, use the Software Repository Guide to add the following repository to your software sources list.
Jani Heikkinen of Digia has announced the RC candidate packages for Qt 5.3 via the Qt Project web server. These packages will become the official Qt 5.3 release candidates should no serious issues be uncovered in the next few days. It was shared that the goal is to put out this release candidate on Friday, 2 May.