KDE

The next release of the Qt Visual Studio Tools, v2.3.0, will allow debugging of QML applications in Visual Studio. It will be possible to set breakpoints in QML files and step through the execution of QML code. While in break mode, it will be ... [More] possible to watch variables and change their values, as well as evaluate arbitrary expressions. The QML debug session will run concurrently to the C++ debug session, so it will be possible to set breakpoints and watch variables in both C++ and QML during the same debug run of the application. This new debugging feature of the Qt VS Tools integrates with the QML debugging infrastructure, a part of the Qt QML module which provides services for debugging, inspecting, and profiling applications via a TCP port. To extend the Visual Studio debugger with features of the QML debugging infrastructure, a Visual Studio QML debug engine is provided. This debug engine consists, for the most part, of implementations of interfaces from the Active Debugging 7 (AD7) extensibility framework for the Visual Studio debugger. If a Qt project contains any QML resource files, starting a debug session (e.g. by pressing F5), besides launching the native application, now also connects to the QML debugging infrastructure of that application. This can be seen in the Processes window of the Visual Studio debugger: two processes are listed, a native process that corresponds to the actual physical process created for the C++ debugging session, and a QML process, which does not correspond to any physical process that is running on the machine, but rather represents the connection to the QML debugging runtime within the native process. Since both a native process and a QML process are present, it is possible to request breakpoints both in C++ or QML code. The Visual Studio debugger will forward requests to the appropriate debug engine. As usual, a filled circular breakpoint marker in QML code indicates a valid breakpoint; this means that a breakpoint request for that file position has been sent to, and confirmed by the QML runtime. When a breakpoint is hit, Visual Studio will show the current state of the call stack. Unlike other scenarios of debugging applications that use different languages (e.g. .NET + Native debugging), the QML debug engine does not provide true mixed mode debugging. It runs concurrently with the native debug engine and, from the point of view of the Visual Studio debugger, it is not related to the native process. This means that, even though it is possible to debug both C++ and QML in the same debugging session, the stack that is shown when a QML breakpoint is hit will only include QML function calls — the C++ context of those calls will not be available. As in the case of native debugging, while in break mode, it is possible to view and modify the values of local variables, in the context of the currently active call stack frame, as well as create watches for any variable or expression. The Immediate window is also available for evaluation of any expression in the context of the current stack frame. Moving the mouse over a QML expression pops up an instant watch window (or “DataTip”). The value of that expression in the current context is displayed and can also be modified. QML debugging is enabled by default for any Qt QML application. It is possible to disable QML debugging, and revert to native-only debugging, by opening the Qt project settings dialog and setting the “QML Debug” option to “Disable”. In this dialog, it is also possible to change the port that is used by the QML debugging runtime. As mentioned, the QML debugging feature of the Qt VS Tools will be available in the next version, scheduled for release in the Visual Studio Marketplace later this year. A preview version will shortly be available for download on the Qt website; we’ll post a quick update here when it is available. The post QML Debugging in Visual Studio appeared first on Qt Blog. [Less]

The Linux Foundation holds its Open Source Summit + Embedded Linux Conference Europe in Edinburgh, October 22 – 24, 2018 In spite of the clumsy name, this is an event you won’t want to miss! KDAB’s Christoph Sterz will be presenting a talk ... [More] on Tuesday, October 23 • 15:50 – 16:30: Extending the Performance Analysis Toolset  Finding and analyzing performance issues on embedded devices can be a tiresome search. Nowadays, modern sampling and tracing technologies are built into the Linux kernel to address this, in the form of perf and LTTng respectively. Still, the vast amounts of data recorded are difficult to handle on the limited embedded devices themselves. In his talk, Christoph will present Hotspot, an open-source performance analysis tool and how to optimize sophisticated tracepoint analysis as well as outline KDAB’s plans in instrumenting Qt for the LTTng tracing ecosystem. Read more… Open Source Summit + Embedded Linux Conference Europe (OSSEU) is the technical conference for professional open source and the leading conference for developers, architects and other technologists – as well as open source community and industry leaders. 15% Attendee Discount Offer Sign up here and get a 15% discount, by using the following code: SPKSHARE15   The post Extending the Performance Analysis Toolset appeared first on KDAB. [Less]

The Linux Foundation holds its Open Source Summit + Embedded Linux Conference Europe in Edinburgh, October 22 – 24, 2018 In spite of the clumsy name, this is an event you won’t want to miss! KDAB’s Chris Sterz will be presenting a talk on Tuesday ... [More] , October 23 • 15:50 – 16:30: Extending the Performance Analysis Toolset  Finding and analyzing performance issues on embedded devices can be a tiresome search. Nowadays, modern sampling and tracing technologies are built into the Linux kernel to address this, in the form of perf and LTTng respectively. Still, the vast amounts of data recorded are difficult to handle on the limited embedded devices themselves. In his talk, Chris will present Hotspot, an open-source performance analysis tool and how to optimize sophisticated tracepoint analysis as well as outline KDAB’s plans in instrumenting Qt for the LTTng tracing ecosystem. Read more… Open Source Summit + Embedded Linux Conference Europe (OSSEU) is the technical conference for professional open source and the leading conference for developers, architects and other technologists – as well as open source community and industry leaders. 15% Attendee Discount Offer Sign up here and get a 15% discount, by using the following code: SPKSHARE15   The post Extending the Performance Analysis Toolset appeared first on KDAB. [Less]

Here’s a little tip how to get DrKonqi, the KDE crash handler to work in applications that use QtWebEngine. If your application uses QtWebEngine, you probably noticed that DrKonqi doesn’t pop up when the program crashes. This is because QtWebEngine ... [More] installs its own crash handler, overriding the one DrKonqi has set up. The workaround is quite simple but is not trivial to find because all of it is undocumented (and not everyone wants to dig into Chromium code…). The trick is to add --disable-in-process-stack-traces to QTWEBENGINE_CHROMIUM_FLAGS environment variable before initializing QtWebEngine: const auto chromiumFlags = qgetenv("QTWEBENGINE_CHROMIUM_FLAGS"); if (!chromiumFlags.contains("disable-in-process-stack-traces")) { qputenv("QTWEBENGINE_CHROMIUM_FLAGS", chromiumFlags + " --disable-in-process-stack-traces"); } ... auto view = new QtWebEngineView(this); ... Here’s a full example of how we fixed this in Kontact [Less]

Welcome to an especially humongous week in KDE’s Usability & Productivity initiative! I typically assemble these reports incrementally over the course of the week, as fixes trickle in. But this week, I had to spend almost 4 hours yesterday ... [More] getting it ready after an enormous flood of incredible work on Friday and Saturday. And there was a time at around 6 PM when patches for Baloo started pouring in faster than my capacity to review them (expect more on Baloo next week). KDE Contributors were truly on a roll! Check out the veritable flood of improvement throughout KDE’s software stack over the past few days: New Features Gwenview can now be configured to zoom in and out of images just by scrolling, no need to use a modifier key first (Chris Suran, KDE Applications 18.12.0) Text annotations in Okular can now be drawn in any color. The toolbar button even shows the color; how cool is that!? (Dileep Sankhla and Tobias Deiminger, KDE Applications 18.12.0): Konsole now fully supports emoji characters (Mariusz Glebocki, KDE Applications 18.12.0) Bugfixes The most common way that the Baloo file indexing system could crash has now been fixed (Stefan Brüns, KDE Frameworks 5.51) Discover can once again be used to turn repos and PPAs on and off on the Settings page (Aleix Pol Gonzalez, KDE Plasma 5.14.0) Discover no longer lets you try to browse apps from Snap or distro repos on the Settings page when it won’t work (Aleix Pol Gonzalez, KDE Plasma 5.14.0) Fixed a place where Discover could crash when installing Snap apps (Aleix Pol Gnzales, KDE Plasma 5.14.0) The Global Menu now works with Flatpak’ed KDE apps again (Jan Grulich, soon) KRunner no longer shows duplicate bookmarks from Firefox (Stefan Brüns, KDE Plasma 5.15.0): When using a Folder View widget in a panel, its file list can once again be navigated using the keyboard (Eike Hein, KDE Plasma 5.12.8) Fixed a variety of other keyboard navigation issues with Folder View widgets on panels (Thomas Surrel, KDE Plasma 5.15.0) Fixed keyboard navigation for the Konsole Profiles widget (Thomas Surrel, KDE Plasma 5.15.0) When using GNOME apps, the corner resize cursors are now correctly used from the Breeze theme, if it’s active (Nicolas Fella, KDE Plasma 5.15.0) Fixed a bug that could cause removable media to still appear in the Device Notifier and Places panel after being removed (Stefan Brüns, KDE Frameworks 5.51) Dolphin can once again automatically install Samba packages if necessary the first time you tell it to share a folder (Rik Mills, KDE Applications 18.08.2) In Dolphin, it’s no longer possible to accidentally start renaming a file or folder after dragging it (Andreas, Krutzler, KDE Applications 18.08.2) KCalc now behaves properly when you repeat the same calculation using the = button or the Enter key (Maximilian Schiller, KDE Applications 18.12.0) UI Polish & Improvement It’s now more obvious in Discover how to manage distro repositories, and those repositories are now shown with more clarity in Ubuntu-based distros (Aleix Pol Gonzalez, KDE Plasma 5.14.0): Discover’s Update Notifier widget now displays a “Restart” button if a restart is recommended after applying all updates but the user hasn’t actually restarted yet (Aleix Pol Gonzalez, KDE Plasma 5.15.0) The Kickoff Application Launcher’s search field now looks like a search field, which fixes various bugs (me: Nate Graham, KDE Plasma 5.15.0): Plasma is now a little bit (100ms) faster to start up (David Edmundson, KDE Plasma 5.15.0) The term “Shut Down” is now consistently used in the user interface for actions, replacing the grammatically incorrect term “Shutdown” (me: Nate Graham, KDE Plasma 5.15.0) By default (i.e. for new installs), the Places panel now displays a better icon for the Network place (me: Nate Graham, KDE Frameworks 5.51): Disks no longer receive an emblem when mounted; now they only get one when they have some unusual status–unmounted, encrypted, etc. This results in greater ability to distinguish the icon used for the disk, particularly at small sizes; see the following pictures for examples! (me: Nate Graham, KDE Frameworks 5.51) We got a new icon for hard drives, which results in a hugely improved appearance in the Places Panel (Noah Davis, KDE Frameworks 5.51): The “Edit…” context menu item for Places panel entries now uses the correct icon (Thomas Surrel, KDE Frameworks 5.51 and Applications 18.12.0): When viewing the Properties dialog for the root volume, the volume’s hardware disk is now listed (Thumas Surrel, KDE Frameworks 5.51) What exciting time to be alive, huh? All of this stuff is available for free, and improves at lightning speed, often in direct response to user feedback. And guess what? Next week, your name could be in this list! Just check out https://community.kde.org/Get_Involved, and find out how you can help be a part of something that really matters. You don’t have to already be a programmer. I wasn’t when I got started. Try it, you’ll like it! We don’t bite! If my efforts to perform, guide, and document this work seem useful and you’d like to see more of them, then consider becoming a patron on Patreon, LiberaPay, or PayPal. Also consider making a donation to the KDE e.V. foundation. [Less]

LabPlot has already quite a good feature set that allows to create 2D Cartesian plots with a lot of editing possibilities and with a good variety of different data sources supported. Analysis functionality is also getting more and more extended and ... [More] matured with every release. Based on the overall good foundation it’s time now to take care also of other plot types and visualization techniques. As part of the next release 2.6 we’re going to ship the histogram. This feature was originally developed by Anu Mittal who contributed to LabPlot during Google Summer of Code 2016. We finally managed to finalize this code, to extend and to prepare it for the release: Also for this type of the data visualization, modifications of the appearance are couple of mouse clicks away. The plots below show couple of histograms for the same data set:                         Cumulative histograms are supported, too. The next plots compare the ordinary and the cumulative histograms for the same data:       Similar for the two possible orientations of the histogram – vertical and horizontal:       Plotting of two and more histograms in the same plot is also possible where some nice looking results can be achieved by varying the opacity of the histogram fillings: Selection of the number of bins for the histogram is an art of its own. LabPlot implements couple of common techniques to set the number of bins such as the square-root rule, Rice and Sturges rules, etc. Furthermore, the number of bins or their widths can also be specified explicitly by the user. With this, LabPlot 2.6 will cover many different visualization techniques for histograms. More advanced features like logarithmic binning, average shifted histograms, histograms with error bars etc. will be implemented in the next releases. [Less]

Everyone is hard at work, and what will become Krita 4.2 is taking shape already. Today we’re presenting a preview of Krita 4.2. It’s not complete yet, and there ARE bugs. More than in the stable release (we’ll be doing a 4.1.4 after all next week to ... [More] clear up some more bugs…), and some might make you lose work. Support Krita! Join the 2018 Fundraiser! But experiment with it, test it, check it out! There are lots of new things in there, and we’d love your feedback! There are also quite a few things we’re right now working on, that aren’t in this preview, but will be in 4.2. And we’ll talk about, too! What’s in there already Masks and Selections. We’ve done a lot of work on improving working with masks and selections. Some of that work has already landed in Krita 4.1.3, but there’s more to come. Ranging from making it easier to paint selections masks, to a new way of moving and transforming selections, to performance improvements all round. The “select opaque” function has received new options. Gamut masks. A much-demanded new feature, gamut masks mask out part of the color selector. A technique described by James Gurney, this helps you to use color in a harmonious way. You can create new masks and edit existing masks right inside Krita. The masks now work with both the artistic and the advanced color selector. Rotating masks over the color selector is possible as well! Improved performance. We’re always working to make Krita perform better, and there will always be room for improvement. This preview contains Andrey Kamakin’s Google Summer of Code work on the very core of Krita: the tile engine. That is, the bits where all your layer’s pixels are handled. There’s still some fixing to do here, so be warned that if you paint with really big brushes, you may experience crashes. At the same time, this preview also contains more of Ivan Yossi’s Summer of Code work: the creation of brush masks now uses your CPU’s vectorization instructions, and that also increates performance! Dmitry also worked hard on improving the performance of the Layer Styles feature: especially for the Stroke Layer Style. The rendering became more correct at the same time. And fill layers have become much faster, too! Keep up to date! Only on Linux for now, since we’re still working on setting up the necessary libraries for encryption on Windows and macOS. The welcome screen can now show the latest news about Krita. It’s off by default, since to bring you the news we have to connect to the Krita website. Colored Assistants. It’s now possible to give your painting assistants individual colors, and that color is saved and restored when you save and load your .kra project file. Activate transform tool on pasting. When pasting something in Krita a new layer is created. Most of the time you’ll want to move the pasted layer around or transform it. There’s now a setting in the preferences dialog that, when checked, will make Krita automatically select the transform tool. Improved move tool: undo and redo with the move tool was always a bit wonky… Now it works as expected. Not a big thing, but it should help with everyone’s workflow. A smoother UI: 4.2 will have lots of small fixes to improve your workflow. That ranges from making it possible to resize the thumbnails in the layer docker to improved interaction with color palettes to making it possible to translate plugins written in Python. There are also new blending modes, with more coming, and the G’Mic plugin has been updated to the latest version. Lots of bug fixes. We’re already at nearly 200 bug fixes for 4.2, and that number will only increase. What we’re working on But we’re not done yet! We intend to release Krita 4.2 this year, in December, but we haven’t gone into feature freeze. This is a little taste of what may still be coming from 4.2! This isn’t in the preview yet, but here are a couple of things that our UX expert, Scott, is working on. First, the brush editor is being redesigned. As you can see from the video, it’s being condensed, and that’s because we also want to make it possible to dock it as a panel in one of the dock areas of Krita, or have it floating free, possibly on another monitor. Then, the text tool‘s UI is being revamped. While Dmitry is working on making the text tool more reliable, Scott is working on making it nicer to use: Michael’s Summer of Code work hasn’t been merged yet, but we fully intend to do that before the release. This will improve the stability of working with color palettes and make it possible to save palettes in your .kra Krita project file. Another area where work is going is resource management. That is, loading, working with, tagging, saving and sharing things like brush presets, brush tips, gradients or patterns. This is a big project, but when done Krita will start faster, use less memory and a lot of little niggles and bugs with handling resources will be gone. Downloads Have fun with the 4.2 preview! Download Windows 64 bits Windows: krita-x64-4.2.0-preview-setup.exe Portable 64 bits Windows: krita-x64-4.2.0-preview.zip Debug symbols. (Unpack in the Krita installation folder) 32 bits Windows: krita-x86-4.2.0-preview-setup.exe Portable 32 bits Windows: krita-x86-4.2.0-preview.zip Debug symbols. (Unpack in the Krita installation folder) Linux 64 bits Linux: krita-4.2.0-preview-x86_64.appimage 64 bits Linux G’Mic-Qt plugin appimage. (If, for some reason, Firefox thinks it needs to load this as text: to download, right-click on the link.) OSX OSX disk image: krita-4.2.0-preview.dmg Note: the touch docker, gmic-qt and python plugins are not available on OSX. Source code Source code: krita-4.2.0-preview.tar.gz md5sum For all downloads: md5sum.txt [Less]

Everyone is hard at work, and what will become Krita 4.2 is taking shape already. Today we’re presenting a preview of Krita 4.2. It’s not complete yet, and there ARE bugs. More than in the stable release (we’ll be doing a 4.1.4 after all next week to ... [More] clear up some more bugs…), and some might make you lose work. Support Krita! Join the 2018 Fundraiser! But experiment with it, test it, check it out! There are lots of new things in there, and we’d love your feedback! There are also quite a few things we’re right now working on, that aren’t in this preview, but will be in 4.2. And we’ll talk about, too! What’s in there already Masks and Selections. We’ve done a lot of work on improving working with masks and selections. Some of that work has already landed in Krita 4.1.3, but there’s more to come. Ranging from making it easier to paint selections masks, to a new way of moving and transforming selections, to performance improvements all round. The “select opaque” function has received new options. Gamut masks. A much-demanded new feature, gamut masks mask out part of the color selector. A technique described by James Gurney, this helps you to use color in a harmonious way. You can create new masks and edit existing masks right inside Krita. The masks now work with both the artistic and the advanced color selector. Rotating masks over the color selector is possible as well! Improved performance. We’re always working to make Krita perform better, and there will always be room for improvement. This preview contains Andrey Kamakin’s Google Summer of Code work on the very core of Krita: the tile engine. That is, the bits where all your layer’s pixels are handled. There’s still some fixing to do here, so be warned that if you paint with really big brushes, you may experience crashes. At the same time, this preview also contains more of Ivan Yossi’s Summer of Code work: the creation of brush masks now uses your CPU’s vectorization instructions, and that also increates performance! Dmitry also worked hard on improving the performance of the Layer Styles feature: especially for the Stroke Layer Style. The rendering became more correct at the same time. And fill layers have become much faster, too! Keep up to date! Only on Linux for now, since we’re still working on setting up the necessary libraries for encryption on Windows and macOS. The welcome screen can now show the latest news about Krita. It’s off by default, since to bring you the news we have to connect to the Krita website. Colored Assistants. It’s now possible to give your painting assistants individual colors, and that color is saved and restored when you save and load your .kra project file. Activate transform tool on pasting. When pasting something in Krita a new layer is created. Most of the time you’ll want to move the pasted layer around or transform it. There’s now a setting in the preferences dialog that, when checked, will make Krita automatically select the transform tool. Improved move tool: undo and redo with the move tool was always a bit wonky… Now it works as expected. Not a big thing, but it should help with everyone’s workflow. A smoother UI: 4.2 will have lots of small fixes to improve your workflow. That ranges from making it possible to resize the thumbnails in the layer docker to improved interaction with color palettes to making it possible to translate plugins written in Python. There are also new blending modes, with more coming, and the G’Mic plugin has been updated to the latest version. Lots of bug fixes. We’re already at nearly 200 bug fixes for 4.2, and that number will only increase. What we’re working on But we’re not done yet! We intend to release Krita 4.2 this year, in December, but we haven’t gone into feature freeze. This is a little taste of what may still be coming from 4.2! This isn’t in the preview yet, but here are a couple of things that our UX expert, Scott, is working on. First, the brush editor is being redesigned. As you can see from the video, it’s being condensed, and that’s because we also want to make it possible to dock it as a panel in one of the dock areas of Krita, or have it floating free, possibly on another monitor. Then, the text tool‘s UI is being revamped. While Dmitry is working on making the text tool more reliable, Scott is working on making it nicer to use: Michael’s Summer of Code work hasn’t been merged yet, but we fully intend to do that before the release. This will improve the stability of working with color palettes and make it possible to save palettes in your .kra Krita project file. Another area where work is going is resource management. That is, loading, working with, tagging, saving and sharing things like brush presets, brush tips, gradients or patterns. This is a big project, but when done Krita will start faster, use less memory and a lot of little niggles and bugs with handling resources will be gone. Downloads Have fun with the 4.2 preview! Download Windows 64 bits Windows: krita-x64-4.2.0-preview-setup.exe Portable 64 bits Windows: krita-x64-4.2.0-preview.zip Debug symbols. (Unpack in the Krita installation folder) 32 bits Windows: krita-x86-4.2.0-preview-setup.exe Portable 32 bits Windows: krita-x86-4.2.0-preview.zip Debug symbols. (Unpack in the Krita installation folder) Linux 64 bits Linux: krita-4.2.0-preview-x86_64.appimage 64 bits Linux G’Mic-Qt plugin appimage. (If, for some reason, Firefox thinks it needs to load this as text: to download, right-click on the link.) OSX OSX disk image: krita-4.2.0-preview.dmg Note: the touch docker, gmic-qt and python plugins are not available on OSX. Source code Source code: krita-4.2.0-preview.tar.gz md5sum For all downloads: md5sum.txt [Less]

Not long ago I purchased a Dell XPS 13 with the HiDPI touchscreen. It was one of the Project Sputnik “Developer Edition” laptops loaded with Ubuntu from the factory; nice and clean. This was my first foray into using a HiDPI screen in Linux. From my ... [More] research before purchasing, it sounded like a mixed bag of functionality. I fired up a bunch of apps, tested them out and dutifully submitted a bunch of bug reports regarding scaling issues to a number of projects. From there, once ushered into the development side of KDE, I decided to start helping out with fixing some of the issues I saw with KDE/Qt apps. It appears there are still very few users and even fewer developers with a HiDPI screen who run 2x scaling, so I notice things others don’t. Most of it revolves around window sizes upon loading, interface button and label sizes, and icon pixelation. Minor stuff, but annoying. The latter of which, is actually really easy to fix in Qt apps. It’s one line: QGuiApplication::setAttribute(Qt::AA_UseHighDpiPixmaps); Enter that into main.cpp of the program and you’re set! Even myself, a rather entry-level programmer can perform that task and submit a patch. So that’s what I did for several applications. Look carefully at the before/after pixelation of the icons here in KTorrent: Some more examples and links to Phabricator, please ignore any change of icon colors, that is a different issue that has been recently resolved: KTorrent K3b KMenu Editor I have a few more in my list, such as the AppMenu button you can add to KWin. Anyone want to tackle that? But anyway, lots of progress is being made! These sorts of fixes, along with ones like display of scaled icons from intended folder, 2x icons in Breeze, enhanced scaling abilities in Wayland, and implementation of HiDpiScaling in some older apps are being committed constantly. Running the latest Plasma release, there are very few HiDPI issues left, and a good portion of them can be blamed on X. You could help do easy tasks like this too! Visit KDE’s Get Involved page for more information, or contact me! [Less]

What is Flatpak? Flatpak is a new way of distributing applications.  Each application runs in its own isolated environment called sandbox with all its dependencies being provided as part of the Flatpak and with no access to other programs. This way ... [More] every user runs the exact same application in the exact same environment no matter what Linux distribution they use.  The applications inside the sandbox are also limited to what system resources they can access, which provides greater security.   Kontact Stable on Flathub The latest stable version of Kontact is now available on Flathub, the official app store for Flatpaks. So even if your distribution does not ship the latest version of KDE Applications or Kontact you can now easily install it from the Kontact Flatpak without having to worry about breaking your system. How to get it? Follow this setup guide on Flathub to install Flatpak and to set up the Flathub repository. Then you can install Kontact Flatpak from Discover or you can install it manually from terminal: flatpak install flathub org.kde.kontact You should see Kontact icon in your installed apps, or you can run it manually from terminal again: flatpak run org.kde.kontact Your feedback is welcomed, taming the entire Kontact to run inside of a tiny sandbox wasn’t an easy task and we may have missed something. You can report issues in the Kontact Flathub repository, reach us on the KDE PIM mailing list or via IRC on the #kontact channel on Freenode.   Kontact Nightly We also have nightly builds of the Kontact development branch. You can use the development Kontact Flatpak to see if your bug has been fixed, to help us with testing Kontact and to provide early feedback on new features before they are released. The nightly Kontact Flatpak runs completely isolated from the stable Flatpak as well as from system-wide installation, which means that your data and configuration are completely safe. We hope that offering this easy and safe way of running the latest development builds of Kontact to a wide audience we will receive more feedback and early testing, leading to better and more polished releases in the future. To install the nightly build you first need to add the kdeapps-testing Flatpak repository: flatpak remote-add --if-not-exists kdeapps-testing --from https://distribute.kde.org/flatpak-apps-testing/kdeapps.flatpakrepo And install Kontact Nightly: flatpak install kdeapps-testing org.kde.kontact//master. To run the nightly version, use flatpak run org.kde.kontact//master You can read a more detailed guide to Flatpak on our community wiki. Remember to run flatpak update from time to time to always get the latest version.   Help us make Kontact even better! Take a look at some of the junior jobs that we have! They are simple, mostly programming tasks that don’t require any deep knowledge or understanding of Kontact, so anyone can work on them. Feel free to pick any task from the list and reach out to us! We’ll be happy to guide you and answer all your questions. Read more here… [Less]