July 2018 - kde - Fedora mailing-lists

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

07 May '25

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

4 3

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

30 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 08 Feb '20

08 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

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

Amarok, Juk & Elisa
by Joe Buckley 04 Nov '18

04 Nov '18

I hope this is appropriate. I'm not a contributor, but I am a long-time KDE (Fedora) user who has an extensive music collection on my lap-top. Since I saw the discussion about dropping Amarok (because of the use of qt4???) I installed and tried to configure juk. My experience is - it's not quite ready for prime time. Once juk is given a directory it creates a "collection" (it's a surprisingly confusing term!). That collection cannot be changed (or at least, the way to change it is lost in the mists of antiquity). Apparently, "collection" is not "directory" or "folder". A folder, once created, cannot be removed without crashing juk. At least, I found a way to create a folder that crashes juk when any attempt to remove from juk is made. Playlists are displayed in no known order. It is certainly not alphabetical. Column order cannot be changed. Changes to the settings (like, removing the comment column) are not retained from session to session. I'm starting to hope that Amarok is kept in the live image. -- */~ Joe Buckley/*

10 23

Kinoite, a KDE version of Fedora Silverblue
by Timothée Ravier 12 Aug '18

12 Aug '18

Hi! This is proof of concept to build a KDE based version of Fedora Silverblue. I called it Kinoite because it had to start with a 'K' and Kinoite is a blue mineral. The resulting desktop only has Firefox and Konsole as main applications installed by default (the minimum for easy Flatpak/Flathub usage). **This has only been tested inside a virtual machine for now, so use at your own risk!** Instructions to try it out on an already installed Fedora Silverblue system: curl -O https://tim.siosm.fr/downloads/siosm_gpg.pub sudo ostree remote add kinoite https://siosm.fr/kinoite/ --gpg-import siosm_gpg.pub sudo ostree admin pin 0 sudo rpm-ostree rebase kinoite:fedora/28/x86_64/kinoite Instructions to build your own: git clone https://pagure.io/fork/siosm/workstation-ostree-config sudo rpm-ostree compose tree --repo=ostree_repo --cachedir=ostree_cache workstation-ostree-config/kinoite.json The changes are available in the following repositories: https://pagure.io/fork/siosm/fedora-comps (master) https://pagure.io/fork/siosm/workstation-ostree-config (f28-kinoite branch) Unfortunately, the current configuration layout makes it hard to switch base packages without duplicating the entire config tree. Thus the Kinoite config is simply a copy of the Silverblue one and is not integrated at all. See also the discussion at: https://discussion.fedoraproject.org/t/kinoite-a-kde-version-of-fedora-silv… Hope you like it!

3 4

Plasma 5.13
by Matthieu Gras 27 Jul '18

27 Jul '18

Upstream released Plasma 5.13.3. Are there any reasons why Plasma is still at 5.13.1 in Rawhide and not even in testing for F28?

6 10

Missing dependencies
by Matthieu Gras 26 Jul '18

26 Jul '18

Hi, it seems that there is a dependency for plasma-workspace which is missing (maybe only on plasma 5.13.3) namely: qqc2-desktop-style Not having this packages causes this bug: https://bugs.kde.org/show_bug.cgi? id=396888 which is a duplicate of https://bugs.kde.org/show_bug.cgi?id=395097

2 1

Re: Again, please announce your so-name bumps!
by Adam Williamson 19 Jul '18

19 Jul '18

On Thu, 2018-07-19 at 09:59 -0700, Adam Williamson wrote: > On Thu, 2018-07-19 at 08:19 +0200, Christian Dersch wrote: > > Hi all, > > > > please announce your so-name bumps *before* you push them. This time LibRaw > > bumped its version, as a result we have broken dependencies and some > > composes like Astronomy spin fail to build… > > > > Problem 1: conflicting requests > > - nothing provides libraw.so.16()(64bit) needed by siril-0.9.9-2.fc29.x86_64 > > Problem 2: conflicting requests > > - nothing provides libraw.so.16()(64bit) needed by > > kstars-1:2.9.6-2.fc29.x86_64 > > Problem 3: conflicting requests > > - nothing provides libraw.so.16()(64bit) needed by > > indi-gphoto-1.7.2-2.fc29.x86_64 > > Problem 4: conflicting requests > > - package gimp-2:2.10.4-1.fc29.1.x86_64 requires > > libgegl-0.4.so.0()(64bit), but none of the providers can be installed > > - package gimp-2:2.10.4-1.fc29.1.x86_64 requires > > libgegl-npd-0.4.so()(64bit), but none of the providers can be > > installed > > - package gimp-2:2.10.4-1.fc29.1.x86_64 requires gegl04(x86-64) >= > > 0.4.4, but none of the providers can be installed > > - nothing provides libraw.so.16()(64bit) needed by gegl04-0.4.4-1.fc29.x86_64 > > > > I'm going to rebuild gimp, indi-gphoto, kstars and siril now. But I'm sure > > there are more broken dependencies. > > Here's the others: BTW, I suspect what may have happened here is the bump was inadvertently introduced by the mass rebuild. It looks like Gwyn committed the bump to 0.19 to dist-git on 2018-06-29 but (presumably intentionally) did not actually *build* it - there is no 0.19 build prior to the 0.19.0-2.fc29 that was done by the mass rebuild. So I think perhaps Gwyn was waiting to be ready to rebuild all the dependencies, but things got pre-empted by the mass rebuild :/ I'm working through the list now. So far it looks like kf5-libkdcraw and krita (which actually appears to have a bundled copy of the same library: https://github.com/KDE/krita/tree/master/plugins/impex/raw/3rdparty/libkdcr… ) need actual code changes to build with 0.19. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Missing dependencies for Plasma 5.13
by Gerald B. Cox 17 Jul '18

17 Jul '18

Last metadata expiration check: 0:07:38 ago on Mon 16 Jul 2018 10:22:48 PM PDT. Dependencies resolved. Problem 1: cannot install the best update candidate for package plasma-desktop-5.12.6-1.fc28.x86_64 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.x86_64 Problem 2: package plasma-workspace-5.13.3-3.fc28.x86_64 requires plasmashell >= 5.13, but none of the providers can be installed - cannot install the best update candidate for package plasma-workspace-5.12.6-1.fc28.x86_64 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.i686 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.x86_64 Problem 3: package plasma-integration-5.13.3-3.fc28.x86_64 requires plasma-workspace >= 5.13, but none of the providers can be installed - package plasma-workspace-5.13.3-3.fc28.i686 requires plasmashell >= 5.13, but none of the providers can be installed - package plasma-workspace-5.13.3-3.fc28.x86_64 requires plasmashell >= 5.13, but none of the providers can be installed - cannot install the best update candidate for package plasma-integration-5.12.6-1.fc28.x86_64 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.i686 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.x86_64 Problem 4: package plasma-lookandfeel-fedora-5.13.3-3.fc28.noarch requires plasma-workspace = 5.13.3-3.fc28, but none of the providers can be installed - package plasma-workspace-5.13.3-3.fc28.i686 requires plasmashell >= 5.13, but none of the providers can be installed - package plasma-workspace-5.13.3-3.fc28.x86_64 requires plasmashell >= 5.13, but none of the providers can be installed - cannot install the best update candidate for package plasma-lookandfeel-fedora-5.12.6-1.fc28.noarch - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.i686 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.x86_64 Problem 5: package sddm-breeze-5.13.3-3.fc28.noarch requires plasma-workspace = 5.13.3-3.fc28, but none of the providers can be installed - package plasma-workspace-5.13.3-3.fc28.i686 requires plasmashell >= 5.13, but none of the providers can be installed - package plasma-workspace-5.13.3-3.fc28.x86_64 requires plasmashell >= 5.13, but none of the providers can be installed - cannot install the best update candidate for package sddm-breeze-5.12.6-1.fc28.noarch - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.i686 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.x86_64 Problem 6: problem with installed package plasma-workspace-5.12.6-1.fc28.x86_64 - package plasma-workspace-5.12.6-1.fc28.x86_64 requires libkworkspace5(x86-64) = 5.12.6-1.fc28, but none of the providers can be installed - cannot install both libkworkspace5-5.13.3-3.fc28.x86_64 and libkworkspace5-5.12.6-1.fc28.x86_64 - cannot install both libkworkspace5-5.12.6-1.fc28.x86_64 and libkworkspace5-5.13.3-3.fc28.x86_64 - package plasma-workspace-5.13.3-3.fc28.x86_64 requires plasmashell >= 5.13, but none of the providers can be installed - cannot install the best update candidate for package libkworkspace5-5.12.6-1.fc28.x86_64 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.i686 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.x86_64 Problem 7: package kde-print-manager-17.12.3-1.fc28.x86_64 requires plasma-workspace, but none of the providers can be installed - package plasma-workspace-5.12.6-1.fc28.x86_64 requires plasma-workspace-common = 5.12.6-1.fc28, but none of the providers can be installed - package plasma-workspace-5.12.6-1.fc28.i686 requires plasma-workspace-common = 5.12.6-1.fc28, but none of the providers can be installed - package plasma-workspace-5.12.4-1.fc28.i686 requires plasma-workspace-common = 5.12.4-1.fc28, but none of the providers can be installed - package plasma-workspace-5.12.4-1.fc28.x86_64 requires plasma-workspace-common = 5.12.4-1.fc28, but none of the providers can be installed - cannot install both plasma-workspace-common-5.13.3-3.fc28.x86_64 and plasma-workspace-common-5.12.6-1.fc28.x86_64 - cannot install both plasma-workspace-common-5.12.6-1.fc28.x86_64 and plasma-workspace-common-5.13.3-3.fc28.x86_64 - cannot install both plasma-workspace-common-5.12.4-1.fc28.x86_64 and plasma-workspace-common-5.13.3-3.fc28.x86_64 - package plasma-workspace-5.13.3-3.fc28.i686 requires plasmashell >= 5.13, but none of the providers can be installed - package plasma-workspace-5.13.3-3.fc28.x86_64 requires plasmashell >= 5.13, but none of the providers can be installed - cannot install the best update candidate for package plasma-workspace-common-5.12.6-1.fc28.x86_64 - cannot install the best update candidate for package kde-print-manager-17.12.3-1.fc28.x86_64 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.i686 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.x86_64 Problem 8: problem with installed package sddm-breeze-5.12.6-1.fc28.noarch - package sddm-breeze-5.12.6-1.fc28.noarch requires plasma-workspace = 5.12.6-1.fc28, but none of the providers can be installed - package plasma-workspace-5.12.6-1.fc28.i686 requires plasma-workspace-common = 5.12.6-1.fc28, but none of the providers can be installed - package plasma-workspace-5.12.6-1.fc28.x86_64 requires plasma-workspace-libs(x86-64) = 5.12.6-1.fc28, but none of the providers can be installed - cannot install both plasma-workspace-common-5.13.3-3.fc28.x86_64 and plasma-workspace-common-5.12.6-1.fc28.x86_64 - cannot install both plasma-workspace-common-5.12.6-1.fc28.x86_64 and plasma-workspace-common-5.13.3-3.fc28.x86_64 - package sddm-breeze-5.13.3-3.fc28.noarch requires plasma-workspace = 5.13.3-3.fc28, but none of the providers can be installed - cannot install both plasma-workspace-libs-5.13.3-3.fc28.x86_64 and plasma-workspace-libs-5.12.6-1.fc28.x86_64 - cannot install both plasma-workspace-libs-5.12.6-1.fc28.x86_64 and plasma-workspace-libs-5.13.3-3.fc28.x86_64 - package plasma-workspace-geolocation-libs-5.13.3-3.fc28.x86_64 requires plasma-workspace-common = 5.13.3-3.fc28, but none of the providers can be installed - package plasma-workspace-5.13.3-3.fc28.i686 requires plasmashell >= 5.13, but none of the providers can be installed - package plasma-workspace-5.13.3-3.fc28.x86_64 requires plasmashell >= 5.13, but none of the providers can be installed - cannot install the best update candidate for package plasma-workspace-libs-5.12.6-1.fc28.x86_64 - cannot install the best update candidate for package plasma-workspace-geolocation-libs-5.12.6-1.fc28.x86_64 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.i686 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.x86_64 Problem 9: package kde-print-manager-libs-17.12.3-1.fc28.x86_64 requires kde-print-manager = 17.12.3-1.fc28, but none of the providers can be installed - package kde-print-manager-17.12.3-1.fc28.i686 requires plasma-workspace, but none of the providers can be installed - package kde-print-manager-17.12.3-1.fc28.x86_64 requires plasma-workspace, but none of the providers can be installed - package plasma-workspace-5.12.6-1.fc28.x86_64 requires plasma-workspace-common = 5.12.6-1.fc28, but none of the providers can be installed - package plasma-workspace-5.12.6-1.fc28.i686 requires plasma-workspace-common = 5.12.6-1.fc28, but none of the providers can be installed - package plasma-workspace-5.12.4-1.fc28.i686 requires plasma-workspace-common = 5.12.4-1.fc28, but none of the providers can be installed - package plasma-workspace-5.12.4-1.fc28.x86_64 requires plasma-workspace-common = 5.12.4-1.fc28, but none of the providers can be installed - cannot install both plasma-workspace-common-5.13.3-3.fc28.x86_64 and plasma-workspace-common-5.12.6-1.fc28.x86_64 - cannot install both plasma-workspace-common-5.12.6-1.fc28.x86_64 and plasma-workspace-common-5.13.3-3.fc28.x86_64 - cannot install both plasma-workspace-common-5.12.4-1.fc28.x86_64 and plasma-workspace-common-5.13.3-3.fc28.x86_64 - package plasma-workspace-geolocation-libs-5.13.3-3.fc28.x86_64 requires plasma-workspace-common = 5.13.3-3.fc28, but none of the providers can be installed - package plasma-workspace-geolocation-5.13.3-3.fc28.x86_64 requires plasma-workspace-geolocation-libs(x86-64) = 5.13.3-3.fc28, but none of the providers can be installed - package plasma-workspace-5.13.3-3.fc28.i686 requires plasmashell >= 5.13, but none of the providers can be installed - package plasma-workspace-5.13.3-3.fc28.x86_64 requires plasmashell >= 5.13, but none of the providers can be installed - cannot install the best update candidate for package plasma-workspace-geolocation-5.12.6-1.fc28.x86_64 - cannot install the best update candidate for package kde-print-manager-libs-17.12.3-1.fc28.x86_64 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.i686 - nothing provides plasma-systemsettings >= 5.13 needed by plasma-desktop-5.13.3-2.fc28.x86_64 ======================================================================================================================================================================================== Package Arch Version Repository Size ======================================================================================================================================================================================== Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): libkworkspace5 x86_64 5.13.3-3.fc28 updates-testing 96 k plasma-workspace-common x86_64 5.12.4-1.fc28 fedora 45 k plasma-workspace-common x86_64 5.13.3-3.fc28 updates-testing 46 k plasma-workspace-libs x86_64 5.13.3-3.fc28 updates-testing 1.5 M Skipping packages with broken dependencies: kde-print-manager i686 17.12.3-1.fc28 fedora 377 k kde-print-manager i686 17.12.3-1.fc28 updates-testing 377 k plasma-desktop i686 5.13.3-2.fc28 updates-testing 6.1 M plasma-desktop x86_64 5.13.3-2.fc28 updates-testing 5.9 M plasma-integration x86_64 5.13.3-3.fc28 updates-testing 153 k plasma-lookandfeel-fedora noarch 5.13.3-3.fc28 updates-testing 11 M plasma-workspace i686 5.12.4-1.fc28 fedora 5.0 M plasma-workspace x86_64 5.12.4-1.fc28 fedora 4.9 M plasma-workspace i686 5.12.6-1.fc28 updates 5.0 M plasma-workspace i686 5.13.3-3.fc28 updates-testing 5.1 M plasma-workspace x86_64 5.13.3-3.fc28 updates-testing 5.0 M plasma-workspace-geolocation x86_64 5.13.3-3.fc28 updates-testing 82 k plasma-workspace-geolocation-libs x86_64 5.13.3-3.fc28 updates-testing 45 k sddm-breeze noarch 5.13.3-3.fc28 updates-testing 397 k Transaction Summary ======================================================================================================================================================================================== Skip 18 Packages Nothing to do.

3 4

Are you able to mount your Android devices in the Dolphin?
by Sudhir Khanger 17 Jul '18

17 Jul '18

Hello, I get the following error when I try to mount my Google Pixel running Android P and another old Android device with an older version of Android. >The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2 does not exist. I wonder if you guys are able to get usb access to your Android devices. I have following mtp packages installed. esmtp-1.2-10.fc28.x86_64 kf5-ksmtp-17.12.3-1.fc28.x86_64 libesmtp-1.0.6-14.fc28.x86_64 kio_mtp-0.75-17.20141221gitc418634.fc28.x86_64 libmtp-1.1.14-3.fc28.x86_64 -- Regards, Sudhir Khanger, sudhirkhanger.com.

10 27

Consider dropping qtlogging.ini *.debug=false override
by Rex Dieter 16 Jul '18

16 Jul '18

Currently, fedora packages provide /usr/share/qt5/qtloggin.ini that includes [Rules] *.debug=false qt.qpa.xcb.xcberror.warning=false Some users have recently commented in https://bugzilla.redhat.com/show_bug.cgi?id=1227295 that we should consider dropping '*.debug=false' It appears a couple of distros (debian, ubuntu) have done so recently in reaction to user feedback, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886437 https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1731646 I'm thinking it may be time for fedora to follow suit. Software has gotten better, kde.org stuff in particular, at supporting categorized logging (with sane defaults) since f22. Thoughts? -- Rex

5 4

Elisa music player
by Syam Krishnan 16 Jul '18

16 Jul '18

Hi, Since there was a discussion about dropping Amarok from the KDE spin since it's still Qt4 based, I looked at alternatives and found Juk and Elisa. It seems that Elisa is more modern of the two. But I wasn't able to find a Fedora package. Any reasons for not packaging Elisa yet (other than the obvious - no takers yet)? Thanks, Syam

6 5

firefox / gtk3 touch controls unavailble on plasma
by Sinan H 15 Jul '18

15 Jul '18

Greetings, I've gotten around on installing plasma on this Thinkpad S1 Yoga. I've found out that (properly configured) firefox doesn't respond to touch anymore, whereas it works as expected under openbox. All touch-friendly kde applications work on both WM/DEs (krita, okular). Replacing kwin by openbox under plasma doesn't fix neither. I've tracked the issue to gtk3 gestures not working at all on plasma: you can check by gtk3-demo --run=gestures # rotate, pinch gestures should draw a color rectangle. Am I missing something ? I haven't found any similar issue or reported bug after tedious googling.

2 3

Frameworks 5.48 in koji issue (F28)
by Colin J Thomson 15 Jul '18

15 Jul '18

Hi, Just updated to test frameworks-5.48, one slight issue was this: Error: Transaction check error: file /usr/lib64/libKF5Activities.so.5 from install of kf5- kactivities-5.48.0-2.fc28.x86_64 conflicts with file from package kf5- kactivities-libs-5.47.0-1.fc28.x86_64 file /usr/lib64/qt5/qml/org/kde/activities/libkactivitiesextensionplugin.so from install of kf5-kactivities-5.48.0-2.fc28.x86_64 conflicts with file from package kf5-kactivities-libs-5.47.0-1.fc28.x86_64 Removing kf5-kactivities-5.47 allowed the update to then go fine, but of course I am left with kf5-kactivities-libs-5.47 and cannot install kf5- kactivities-5.48 Am I right in thinking kf5-kactivities-libs is no more? Colin -- Fedora (Twenty Eight) Registered Linux user number #342953

2 2

Re: Plasma 5.13
by Matthieu Gras 11 Jul '18

11 Jul '18

Thanks, very helpful. I wasn't sure if Plasma 5.13 is eventually going to land in F28 but that seems to be the case.

2 1

Problem sending messages in kmail (smtp)
by José Abílio Matos 11 Jul '18

11 Jul '18

Hi, yesterday I noticed that I am unable to send email messages on kmail using stmp to an outlook server. It worked with no problem until yesterday. This is strange since I never had this problem until yesterday and I can send messages using k9mail (on android) using (seemingly) the same setup. I am using TLS over port 587 and using Login as the authentication method. The error that shows in the logs (using journalctl -xb) is: akonadi_maildispatcher_agent[3382]: org.kde.pim.ksmtp: LoginJob: Couldn't choose an authentication method. Please retry with : ("GSSAPI", "NTLM") This seems consistent with the fact that if I try autodetect the encryption type it says that there is none. Any help? Regards, -- José Abílio

1 1

thinning f29 kde spin: dropping qt4/kde4
by Rex Dieter 09 Jul '18

09 Jul '18

Next step in thinning the f29 kde spin is dropping the last bits that depend on qt4/kde4, namely: amarok (currently replaced by juk). https://pagure.io/fedora-comps/pull-request/287 -- Rex

4 5

Plasma GUI fonts borked
by Patrick O'Callaghan 08 Jul '18

08 Jul '18

I was fooling around with the Settings panel and must have done something I shouldn't, because now the fonts for KDE apps are all wrong. GTK apps are unaffected. I enclose a small screenshot to illustrate. Note that the left-hand side looks fine, while the right- hand side is clearly wrong. The same fuzziness affects the Plasma panel and the Konsole fonts. I've no recollection of touching the font configuration, but I guess anything is possible. How can I restore sanity? poc

2 3

usability "spectacle" compared to "ksnapshot"
by Reindl Harald 07 Jul '18

07 Jul '18

in ksnapshot when you selected a rectangle and after the snapshot said "new screenshot" by default the same rectangle was kept which is great when you produce a step-by-step howto, now you need to select again and again by hand also the delay "on click" makes no sense for a rectangle but disable it makes "window behind the pointer" useless given that it's an optical clone of ksnapshot why didn't the developers care about usability?

2 2

KDE session scripts
by Patrick O'Callaghan 06 Jul '18

06 Jul '18

I found a Python script (I think on Github, but I can't seem to locate the URL or the original author) that saves or restores the desktop location of each open Firefox window*. It does this by calling wmctrl(1) and storing/loading the location as a JSON data structure. The data structure is indexed by the window title, but Firefox changes the title based on the currently active tab in each window. Thus the saved data will depend on which tab happens to be active in each window. The script already works when called manually but I just want to automate the process when I log in or out of KDE. The Save script has to run *after* Plasma starts and all my windows are already created. According to the KDE manual, this seems to rule out Autostart. The Restore script should run just before killing any running windows. It should also work even if I reboot directly from the KDE Leave tab without logging out. Is this possible? poc * It would be trivial to modify the script for other apps.

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde July 2018