Gedda.info

Rodney Gedda's piece of the Web

November 25, 2018
by Rodney Gedda
2 Comments

More usability options

Nate is now approaching one year of usability & productivity. Awesome stuff!

A couple of things I noticed recently relate to notifications.

  • Discover, the KDE front-end to Flatpak, among other things, does not have a notification icon and the naming is inconsistent:

Discover’s missing icon and inconsistent naming

If I were to offer a recommendation I’d say have the right-click entries as “Open Discover“, “See Updates” and “Configure Discover“. Keep the Discover name consistent throughout the app and config.

  • Another relates to KDE Connect, an awesome app for integrating Android with the Linux desktop.

Duplicate SMS notifications from KDE Connect

More duplicate SMS notifications from KDE Connect.

When you receive an SMS it will display as KDE notification, but the problem is three or so duplicates show up. Once is enough.

  • Lastly, LibreOffice’s icons appear twice in the standard Plasma panel. Other KDE and non-KDE apps, like Firefox, display and underscore under their panel icon after being started. For some reason LibreOffice spawns a new one, which takes up real estate.

LibreOffice’s second panel icon (far left and second one is far right).

October 29, 2018
by Rodney Gedda
0 comments

Nasty Nouveau problem

I had a problem with X.org using way too much shared memory with the Nouveau driver.

High memory use – X.org with Nouveau

 

 

 

 

 

 

The shared memory was taking up all the physical memory and swap space making the system unusable.

Switching to the proprietary driver (or switching to the Intel card) seems to have resolved the issue.

 

August 31, 2018
by Rodney Gedda
0 comments

Is secure boot becoming mandatory?

The gift that keeps on… is now making it difficult for me to install Linux on it.

Back in the good old days you used to be able to install a boot loader to the MBR of the first hard drive and away you go. Apparently this doesn’t work anymore. I installed KaOS on it and while it seemed to install fine the darn thing won’t boot.

Want to add an EFI source? Now it seems you have to enable secure boot to add a “trusted” source. Any every USB key is trusted, right?

Grr… I’ll figure something out.

July 31, 2018
by Rodney Gedda
0 comments

Delta Chat bridges chat and email

Delta Chat in action.

I found this great little app on the F-Droid store that allows you to bring some sanity to chat.

Delta Chat is essentially an email client that form-factors the text to be a chat message. People can chat as they would using any other chat app with all messages sent to an inbox as well. You can “chat email” anyone.

There is no central server (just your email server) and messages can be encrypted.

June 30, 2018
by Rodney Gedda
0 comments

Vivid pic

I took this great photo of a light dinosaur at Sydney’s recent Vivid festival. A lucky touch indeed.

Illuminated dinosaur at Vivid.

Illuminated dinosaur at Vivid.

I’ve worked with photographers all my career, but I’m still very much an amateur. And here’s one from a rooftop bar…

A vivid rooftop…

 

 

 

 

 

 

 

 

 

 

 

May 31, 2018
by Rodney Gedda
0 comments

Korora’s on ice

I have one system with the Fedora-based Korora installed on it. This month the maintainers decided to take a break from developing the distro.

This leaves me in a bit of a pickle as I need to reinstall something else. At this stage I’m thinking of KaOS as it seems to have everything I need.

It’s a shame about Korora. The core maintainers are Australian and there is certainly space in the market for a distro like it.

Perhaps they were taking on too much by supporting five desktop environments? I recommend just picking one desktop and running with it. There is still a lot of integration work to be done between the desktop, apps and system. And doing that for multiple desktops is no mean feat.

April 30, 2018
by Rodney Gedda
0 comments

New Ubuntu release, old PC donated

I scratched together a working desktop from old components lying around the house. With the release of Kubuntu 18.04 she’s as good as new.

Old PC

Well, the USB Wi-Fi dongle and the keyboard and mouse are new, but everything else is pre-loved.

I donated it to the local homeless shelter today where I trust it will be put to good use.

My office is less cluttered and someone will experience Linux for the first (probably) time. Okay, we’re not counting Android.

I encourage others to do the same – much more rewarding than selling old tech online for a grand total of $20!

 

March 31, 2018
by Rodney Gedda
0 comments

USB headset usability

Hot on the heels of my last post about USB key usability I have another one to share, this time about headsets.

Nate Graham’s usability series is going full steam ahead and we have a lot to look forward to in upcoming releases.

For now let’s focus USB headsets. I use a USB headset for Skype and Linphone calls and KDE has good support for this peripheral device. In fact, the KDE team was thinking well ahead of its time when years ago it provisioned for a number of use cases with audio devices. An audio stream can be directed to a type of audio device WHEN it was most appropriate (or, to meet a use case). For example, a “communication” use case can priorotise a headet over the computer’s loud speakers. Conversely, a system notification can be directed to use the computer’s speakers instead of a headset.

The Phonon AV framework abstracts the devices from the applications so audio or video can be added to any app, such as a file manager, without having to code it from scratch.

KDE multimedia (Phonon) system settings.

The only challenge for a polished end-user experience is third-party applications must take advantage of this flexibility, and KDE must respond accordingly. Take USB headsets. When you plug one in ,you get:

Plug in USB headset -> No device notification -> No backend change -> The user has to manually promote the headset to be the preferred device for audio playback

No notification when a USB headset is plugged in

Quick question: If one plugs in a USB headset is it not a reasonable assumption the person actually wants to use it?

So we have two possible scenarios to improve usability:

  1. Plug in a USB headset and the system sets that as the default (not unreasonable),
  2. Or, plug in the USB headset and the notification system ASKS the user to select that device as the default for audio playback and capture or not (most refined option). This is similar to how the notification system asks the user how to respond when a USB key is inserted.

At present the user is left to her or his own devices (yes pun) to manually select the headset for audio playback and “recording” (should this be changed to “input”?).

Once you set the default audio playback and recording device to the USB headset VoIP apps work fine.