Language Selection

English French German Italian Portuguese Spanish

With the latest Kubuntu 15.10 (Wily)

Filed under
Just talk

I love the KDE desktop—I really do. However… here are some grumbles.

1. If you're looking to configure wacom drivers using the KDE systemsettings Input icon, forget it. This functionality is missing from the (upgraded) KDE tools. If you do click the Input icon in systemsettings, you will find that your graphics tablet is configured as a joystick. So, you'll have to use the Command Line Interface xsetwacom utility program available in the xserver-xorg-input-wacom package. The xsetwacom utility is difficult to master.

2. If you use multiple desktops, under KDE4, you could use different wallpapers, and widgets for each desktop. Since I have a 3-monitor display, this was invaluable for tracking my applications and widgets, and setting-up a smooth workflow. This is gone from the new KDE Plasma5 and is not likely to be reproduced in the future (it's “too difficult”).

3. In the file manager Dolphin, you used to be able to right-click on a file, and click “Extract here” – which is a feature I've used probably a thousand-times over the years to expand files from the file manager into the proper folder. A nifty and useful utility in a file-manager (and not all that hard to implement). Well, it's gone.

So how do I feel about the “upgrade” from KDE 4 to the new KDE Applications15-Frameworks5-Plasma5? I guess it's better than switching from KDE3 to KDE4, but it's still aggravating. Yes, I know, it will take time before it's all polished-up (but, some things, like item #2 above, aren't likely to be fixed).

More in Tux Machines

Security Leftovers

  • Security updates for Thursday
  • Security Tips for Installing Linux on Your SysAdmin Workstation
    Once you’ve chosen a Linux distro that meets all the security guidelines set out in our last article, you’ll need to install the distro on your workstation.
  • Fedora 26 crypto policy Test Day today (2017-03-30)!
  • Open-source developers targeted in sophisticated malware attack
    For the past few months, developers who publish their code on GitHub have been targeted in an attack campaign that uses a little-known but potent cyberespionage malware. The attacks started in January and consisted of malicious emails specifically crafted to attract the attention of developers, such as requests for help with development projects and offers of payment for custom programming jobs. The emails had .gz attachments that contained Word documents with malicious macro code attached. If allowed to execute, the macro code executed a PowerShell script that reached out to a remote server and downloaded a malware program known as Dimnie.
  • A scramble at Cisco exposes uncomfortable truths about U.S. cyber defense
    When WikiLeaks founder Julian Assange disclosed earlier this month that his anti-secrecy group had obtained CIA tools for hacking into technology products made by U.S. companies, security engineers at Cisco Systems (CSCO.O) swung into action. The Wikileaks documents described how the Central Intelligence Agency had learned more than a year ago how to exploit flaws in Cisco's widely used Internet switches, which direct electronic traffic, to enable eavesdropping. Senior Cisco managers immediately reassigned staff from other projects to figure out how the CIA hacking tricks worked, so they could help customers patch their systems and prevent criminal hackers or spies from using the same methods, three employees told Reuters on condition of anonymity.
  • NTPsec: a Secure, Hardened NTP Implementation
    Network time synchronization—aligning your computer's clock to the same Universal Coordinated Time (UTC) that everyone else is using—is both necessary and a hard problem. Many internet protocols rely on being able to exchange UTC timestamps accurate to small tolerances, but the clock crystal in your computer drifts (its frequency varies by temperature), so it needs occasional adjustments. That's where life gets complicated. Sure, you can get another computer to tell you what time it thinks it is, but if you don't know how long that packet took to get to you, the report isn't very useful. On top of that, its clock might be broken—or lying. To get anywhere, you need to exchange packets with several computers that allow you to compare your notion of UTC with theirs, estimate network delays, apply statistical cluster analysis to the resulting inputs to get a plausible approximation of real UTC, and then adjust your local clock to it. Generally speaking, you can get sustained accuracy to on the close order of 10 milliseconds this way, although asymmetrical routing delays can make it much worse if you're in a bad neighborhood of the internet.
  • Zelda Coatings
    I assume that every permutation of scams will eventually be tried; it is interesting that the initial ones preyed on people's avarice and dishonesty: "I will transfer millions to your bank account, then you share with me" - with subsequent scams appealing to another demographic: "I want to donate a large sum to your religious charity" - to perhaps capture a more virtuous but still credulous lot. Where will it end ?

Tizen and Android

Linux and Linux Foundation

Mesa and Intel Graphics