kde January 2018

kde@lists.fedoraproject.org

29 participants
23 discussions

How to set default session type to Plasma for sddm
by Roderick Johnstone 29 Oct '21

29 Oct '21

Hi How do I set the default session type for sddm to offer to be Plasma? I'm currently getting Gnome Classic? This is F22. Thanks Roderick Johnstone

7 13

nntp (aka, usenet) client in kde?
by Gene Smith 07 Feb '20

07 Feb '20

I currently use t-bird with an nntp account pointing to gmane to read this list and sereral others. Does kde have an nntp client program of any sort? I don't see it as a possible new account type in kmail. Also, search with kpackagekit yields nothing with "usenet" or "nntp" that is kde specific. -gene

10 10

time to orphan/retire unmaintained uncommon kde4 language bindings?
by Rex Dieter 28 May '19

28 May '19

Looking over some broken deps reports, I came across some old packages: kdebindings smokeqt smokekde qyoto (csharp/mono) kimono (csharp/mono) ruby-qt ruby-korundum perl-Qt Of these, the only one that's not a pure leaf package is perl-Qt (debconf- kde depends on it). any comment or objection to considering orphaning most (all minus smokeqt/perl-Qt) or all of these ? -- Rex

3 2

Emacs key binding in KDE Plasma 5?
by Sherman Grunewagen 21 May '19

21 May '19

Just moved from Fedora 21 to F25. Under F21 I had a file ~/.gtkrc-2.0 which contained gtk-key-theme-name = "Emacs" This enabled basic Emacs cursor motion keyboard commands in text input boxes throughout KDE, Firefox, &c. (Outside of input boxes, KDE shortcuts ruled.) How can I get this same behaviour for Plasma 5 w/in F25? From reading around, I've created ~/.config/gtk-3.0/settings.ini and inserted [Settings] gtk-key-theme-name = Emacs in this empty file. This has given the desired result in Firefox and Thunderbird, but not w/in arbitrary text boxes in KDE (e.g. Alt-F2). The ~/.gtkrc-2.0 file is still intact, by the way. It seems to have no effect. Any ideas? -Sherman

3 2

SDDM Themes not working
by Gerald B. Cox 06 Mar '19

06 Mar '19

I find that I now cannot select themes - and I'm getting either a solid white or blue background when SDDM starts. When I tried to test, this is what I received: sddm-greeter --theme /usr/share/sddm/themes/01-fedora-breeze [11:43:09.032] (II) GREETER: High-DPI autoscaling not Enabled [11:43:09.108] (EE) GREETER: Socket error: "QLocalSocket::connectToServer: Invalid name" [11:43:09.109] (EE) GREETER: Cannot connect to the daemon - is it running? [11:43:09.317] (II) GREETER: Loading file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml... [11:43:09.317] (WW) GREETER: file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml: No such file or directory [11:43:09.317] (WW) GREETER: file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml: No such file or directory [11:43:09.317] (WW) GREETER: Fallback to embedded theme Wanted to see if there was a quick fix or if this is known before I create a bug report. I didn't see anything on bugzilla, but might have missed it. Thanks!

3 10

F26: Problem with '/usr/lib64/qt5/plugins/kf5/parts/kjavaappletviewer.so'
by John Pilkington 01 Feb '18

01 Feb '18

I just tried to preview a .class file from projectx in F26 konqueror with this result. Attempts to use other tools also fail, and el7 has a similar problem. Google finds related complaints from Windows 10. Apparently the class I hoped to examine isn't there - but that's another story. Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/parts/kjavaappletviewer.so' John P

1 1

digikam 5.8.0-2 with mysql
by Chris Rouch 31 Jan '18

31 Jan '18

I just updated to the latest digikam on fedora 27. It tries to do a database migration on startup, which fails. I assumed this was because I was using a mysql server. I raised a bug this morning, and have already had an update and a fix, which is to change dbconfig.xml to the one in the bug report below. This worked for me. Looking at the date on the rpm it was built just before this file was updated upstream, so hopefully the next release will have it included. Regards, Chris https://bugs.kde.org/show_bug.cgi?id=389677

2 2

[Talking Points] KDE SIG
by Alberto Rodriguez Sanchez 28 Jan '18

28 Jan '18

Hi KDE Team, I'm Alberto from the marketing team, Talking points are key highlights of the new release. They should be compelling, but they will not necessarily be comprehensive. There are different types of talking points for different types of people: general desktop users/everyone, developers, and sysadmins. For the Fedora 28 cycle, we will also have talking points to address some of the Spins. They are meant to provide a short, effective answer to the question, "What cool stuff is in the latest release of Fedora?" Each cycle, the Marketing team compiles a short list of approximately three talking points for each of these audiences for the upcoming release. So, What is new from the KDE Team?? P.D: We already have this little list: 1.- Qt 5.10.x 2.- Plasma-5.12.x, 3.- Wayland support will be included (not default) 4.- Plasma-discover support for flatpak If you have a talking point that you feel meets the criteria found on the talking points SOP page at https://fedoraproject.org/wiki/Talking_points_SOP, Regards -- Alberto Rodriguez Sanchez <hotgalan(a)gmail.com>

1 0

Qt 5.9.4 for f27 feedback
by Rex Dieter 27 Jan '18

27 Jan '18

Next big(ish) update that's worth bringing extra attention, is Qt 5.9.4 stable LTS release builds for fedora 27, https://bodhi.fedoraproject.org/updates/FEDORA-2018-3c21305b93 I queue'd it for updates-testing just now. One caveat is that there is one rebuild missing in this initial batch, ugene, awaiting feedback from it's maintainer on how best to handle that one, https://bugzilla.redhat.com/show_bug.cgi?id=1538704 Any bugs, please file and block this tracker, https://bugzilla.redhat.com/show_bug.cgi?id=qt594_f27 If nothing blows up, will then start work on f26 builds as well. -- Rex

1 0

F27: open kcachegrind-files from folderview
by Reindl Harald 23 Jan '18

23 Jan '18

when i call something like "cachegrind.out.corecms_cached" from Konqueror all is fine, doing the same roma folderview on the desktop it opens fine *but after* you close kcachegrind you get a error message like in the attachment saying "KDEinit could not start /usr/bin/kcachegrind" why is there any difference at all and how in the world comes the desktop to the crazy idea that it was not able to open something you just closed after you are done?

2 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde January 2018