Urgent(ish) Contract KDE Developer availability?

Bernard Gray bernard_gray at debortoli.com.au
Mon Mar 30 06:23:04 BST 2020


Hi all,
My name is Bernie, I work for an Australian Winemaking company and we
have been KDE Users for many years now
(https://dot.kde.org/2014/02/18/kde-software-down-under)

I apologise if this is the wrong platform to pose the question, but I
wasn't sure where else would suit -

In short, due to COVID-19 we have rapidly had to transition our
workforce to remote functions, and we're doing this by running a
(actually, multiple) terminal server setup with xrdp.
In the course of this migration, we have uncovered a number of bugs in
multi-user KDE that are having a fairly significant impact on the
functionality of this setup.

We'd like to contract one or more people to spend some time patching
these issues (and potentially a few other issues which are impacting
less heavily for now) - if you are able to, willing to, or especially
are in need of some contract work due to loss of income from COVID-19,
please get in touch.

The major bugs, in order of priority:

1. Bug 418906 - UDI (Unique Device Identifier) provided by solid is
not actually unique, entry gets overwritten
 - https://bugs.kde.org/show_bug.cgi?id=418906
This one is our current hardest hitter - every subsequent user that
logs in overwrites the previous user's specific network mount point
references in solid, and all the device shortcuts in the left pane of
dolphin break for all other users. It is possible to workaround by
navigating to specific folders, but this is causing a significant
amount of extra support on an already lean and hard worked department
and resolving this would be huge.

2. Bug 347772 - kscreenlocker_greet using 100% cpu on plasma 5
 - https://bugs.kde.org/show_bug.cgi?id=347772
This is longstanding, but it hits us on a per user basis. Once a few
users have logged in, timed out and the screensaver started up, 10-15%
cpu * user adds up very quickly and the machine gradually maxes out
each core. I've had to workaround this by disabling the screensaver
altogether on the terminal server.

Thanks for your time - once again, apologies if this was an
inappropriate place to post, please direct me to a more suitable
platform if so.

Regards,
Bernard Gray




More information about the kde-core-devel mailing list