kde January 2019

kde@lists.fedoraproject.org

14 participants
15 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

KDE Telepathy Bonjour account: This IM Account cannot be created - a Telepathy Connection Manager named 'salut' is missing or it cannot handle protocol 'local-xmpp'. Please try installing salut with your package manager.
by Dennis Schridde 10 Jun '19

10 Jun '19

Hi! I was trying to setup a Bonjour (local XMPP) account in KDE Plasma System Settings for KDE Telepathy. In `System Settings > Online Accounts > Create`, I clicked "Bonjour" in the list on the right. This action was answered with an error dialogue box: "This IM Account cannot be created - a Telepathy Connection Manager named 'salut' is missing or it cannot handle protocol 'local-xmpp'. Please try installing salut with your package manager." However, `telepathy-salut` is already installed on my machine. Does anyone have an idea how to debug this, or where I would find the actual error message that led to this? I am using Fedora 27 KDE, with telepathy-salut currently being at version 0.8.1 (release 12.fc27), telepathy-mission control at version 5.16.4 (epoch 1, release 4.fc27) and ktp-accounts-kcm at version 17.12.1(release 1.fc27). Best regards, Dennis

6 9

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

27 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

KDE rebuild for RHEL8
by Troy Dawson 09 May '19

09 May '19

I know that RHEL8 isn't out yet, but I'd like to run KDE on my RHEL8 Beta. Even if it's just the basic KDE desktop. I'm fine building it myself, but I'm having a hard time figuring out the rebuild flow. If I (or anyone) were to rebuild KDE for RHEL8, where do I start? and then what's next? There are base QT5 packages in RHEL8 beta. Do you think I would need to rebuild QT5? Or just start with RHEL8's QT5 packages. Thanks Troy

9 29

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

kate - turn off "Highlight Selected Text"
by Troy Dawson 25 Feb '19

25 Feb '19

I'm really liking the kate that comes with kde5, except for one thing. It comes with "Highlight Selected Text"[1] turned on by default. It looks like with kde4, this was a plugin that you could turn on and off, but with kde5, it's builtin, and as far as I can tell, you can't turn it off. Does anyone know how to turn this off? This looks like something I might want once in a while, but having it on constantly totally throws me off, because the highlighing is very bright. Troy [1] - https://kate-editor.org/2010/11/14/highlight-selected-text/

2 1

Finding orphaned KDE packages in Fedora
by Kai Bojens 25 Jan '19

25 Jan '19

Is there an easy way, maybe even a list of orphaned KDE packages in Fedora? The overwiew of all orphaned packages in Fedora is a little bit overwhelming and seems to have no search for SIG packages …

2 5

Re: Spins keepalive deadline approaching
by Ben Cotton 24 Jan '19

24 Jan '19

I wasn't sure which individuals to tag into the KDE ticket[1] for the message below, so I'm sending it to the list at large. [1] https://pagure.io/fedora-project-schedule/issue/100 On Wed, Jan 23, 2019 at 3:06 PM Ben Cotton <bcotton(a)redhat.com> wrote: > > FESco previously approved a requirement that Spin/Labs owners send a > keepalive request in order to keep building the spin or lab. I have > opened Pagure issues[1] for all Spins and Labs listed on the wiki[2]. > > If you are the owner of one of those spins and labs, please reply in > the appropriate ticket by30 January 2019 to indicate the spin should > continue to be produced. If there is a spin or lab that does not have > an open ticket, please create one[3]. > > The reasoning for this is to not ship spins that are not actively > maintained. Future improvements to the release process that will allow > for teams to self-publish solutions will eventually remove the need > for these keepalives. > > [1] https://pagure.io/fedora-project-schedule/issues > [2] https://fedoraproject.org/wiki/Releases/30/Spins > [3] https://pagure.io/fedora-project-schedule/new_issue > > -- > Ben Cotton > Fedora Program Manager > TZ=America/Indiana/Indianapolis -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis

2 1

Qt Creator - 'undeclared' error for Qt4 projects
by Syam Krishnan 20 Jan '19

20 Jan '19

Hi I am trying a Qt4 project on Qt Creator on Fedora 29. I get 'undeclared' errors by the IDE (not the compiler) for pretty much all library functions/types - both Qt and non-Qt. But compilation and execution work just fine. Only the IDE shows these errors. Screenshot here: https://pasteboard.co/HXhWMJZ.png Any idea on what is wrong? Thanks, Syam

1 0

Profile corrupt
by Klaus Kolle 18 Jan '19

18 Jan '19

My current profile / login on Fedora KDE 29 is corrupted in some parts. I was thinking of deleting either the .kde or the .config folders (or rather rename them) in order to let the KDE and programs reinitialise ther settings. I don't want to delete the whole profile (home directory), because there are a lot of other things that I would like to preserve. My intentions are to move part of the settings back from the backups for those programs and KDE parts that are not corrupted. Amongst other problems I see is that LibreOffice doesn't like Danish letters in file or pathnames. But if I start it from commandline with an empty env (env -i pgmname) it works well. Another thing I see is that my computer does not respect the settings for locking the screen when away for the set period of time and it doesn't go to sleep some time later. And there is some other problems as well, but that would be a long list. The profile has been living for quite some years now, so it is probably the constant upgrading that may have corrupted it. Which of the two folders should I rename first - .kde or .config? OR maybe a totally different. Thanks |< -- Med venlig hilsen Klaus Kolle Teknikumingeniør, B.Sc.EE., e-mail : klaus(a)kolle.dk Master of IT www : www.kolle.dk Kollundvej 5 Telephone : +4586829682 / +4522216044 DK-8600 Silkeborg, Denmark "Leave me alone, I know what I'm doing!" Kimi Räikönen, Abu Dhabi F1 race 2012. Planlægning er tanker om noget man agter at gøre en gang i fremtiden, hvis omstændighederne tillader det. Klaus Kolle 2006 Perfection is achieved not when nothing more to add, but when there is nothing more left to take away. Antoine de Saint-Exupery

2 2

Updates - A difference of opinion
by Ed Greshko 16 Jan '19

16 Jan '19

Yesterday I enabled updates-testing and updated. This update included kernel-4.19.15-300. Today, dnf and pkcon tell me there are no packages to update. However, dnfdragora-updater is telling me there are 5 updates available in the kernel-4.19.14-300 series. None of the "refresh" options of dnfdragora clears it out. So, where is it getting the idea that a lower version of the kernel needs to be install? -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme

2 4

Different approach to KDE and XFCE desktop testing?
by Lukas Ruzicka 08 Jan '19

08 Jan '19

Hello KDE and XFCE teams, I am writing to you on behalf of the Fedora QA team, because you are the stakeholders of release-blocking desktop environments in Fedora. We believe that there is need to revisit and review some of the approaches we have in desktop testing. I hope that I can clarify in the text. *How do we test desktop applications?* Currently, there are three desktop environments, which block the Fedora releases: GNOME, KDE, and XFCE (on ARM). Among others, there is a test case called “Desktop Menus” [ https://fedoraproject.org/wiki/QA:Testcase_desktop_menus ] which is used for all three desktop environments. *What is the purpose of the Desktop Menus test case?* The purpose of the “Desktop Menus” test case is to test that applications listed in the menu do generally work. That means that each application in the default system menu must launch without crashing and withstand basic usage. [2] *What problems can arise when trying to follow the test case?* This approach leaves a lot of space for variability, because the terms are not clearly given, especially when talking about “basic functionality” of the desktop applications. In the past, there have been some disputes during Blocker Review meetings, or during Go/No go meetings whether basic functionality is broken or not. It's usually up to group judgement to decide what is a basic functionality and what it beyond that, which means as testers we need to err on the side of doing more testing rather than less. Testing the “Desktop Menus” test case is one of the most time consuming test case we currently have. In GNOME, there are currently about 40 applications in the default menu and all need to be started and their basic functionality tested. In KDE, the number of applications is even higher, and some application types (like web browsers) are even present as several different applications. The scope of this test case also covers testing the subcomponents in the Control Center (or a similar equivalent) and, usually, such subcomponents are numerous. Testing XFCE on ARM is also rather time consuming, because the ARM devices we can use for testing are very slow and there are some application that make little sense on an ARM motherboard (e.g. a CD writing software). Thus, doing a thorough Desktop Menus test case requires a rather longish time frame and we lose time we could devote to different problems. Besides that, the test case is also very boring, so it usually gets tested by Fedora QA members only, with few inputs from the community. So, before the Beta and Final release we are able to do such tests a couple of times, but the overall coverage is not big. *What could we do about it?* At Fedora QA, we have been trying to come up with some ideas to make the situation a little better than it is now. The goal is that the important areas get enough attention and testing they deserve, and we avoid shipping broken and under-tested software. See the ideas below and please tell us if you could adopt all/some of them, or if you have different suggestions to improve the current state, we'd love to hear them too. - The list of pre-installed applications could be pruned of those which don't make much sense for that particular purpose (e.g. CD writing software on ARM, or perhaps on any system nowadays). - Pre-installed applications could be deduplicated where possible (e.g. not having several web browsers pre-installed by default). - We could define a list of "important" applications that would be tested thoroughly and the basic functionality criterion would apply just to them. That would tell QA where to focus. (This would obviously contain applications like system settings, file browser, text editor, browser, terminal emulator, etc. But e.g. a screenshot utility would probably not fall into the list. Also, in case of duplicated apps, only one of those could be marked as "important", and the others would* not). The rest of the applications would be just best effort in terms of QA, and wouldn't block the release. - Last but not least, you could help us more with release validation before relevant milestones (Beta, Final) :-) If there's anything that should be improved on our part (communication, instructions, etc), we'd love to hear that. Please, let me know what you think about the ideas proposed above. Do you have any other ideas that could help us improve the quality (with the same amount of testing force)? Best regards, -- Lukáš Růžička FEDORA QE, RHCE Red Hat <https://www.redhat.com> Purkyňova 115 612 45 Brno - Královo Pole lruzicka(a)redhat.com TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

1 0

Fedora 29 KDE Plasma Discover finds no more updates after Update to Kde-Framwork 5.53
by Mag. Gerald Sterrer 07 Jan '19

07 Jan '19

It seems that Plasma Discover does not find no more updates after updating to KDE-Framework 5.53. What can be done and what are the reasons for this? Thank you Gerald

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde January 2019