kde September 2016

kde@lists.fedoraproject.org

33 participants
30 discussions

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

F25 runs wayland by default
by Neal Becker 14 Apr '17

14 Apr '17

I see that F25 will run wayland by default instead of Xorg. Will kde run on wayland?

12 19

Device notifier produces "malformed url" error since last update
by CS DBA 12 Oct '16

12 Oct '16

All; Since the last update if I plug in a device and click the "Open with File Manager" I get a "Malformed url" error. I can mount the device manually at the command line. Thoughts? Thanks in advance

4 4

plasma-5.8.0 avilable in copr
by Rex Dieter 08 Oct '16

08 Oct '16

For those of you who want a quick sneak-peak at plasma-5.8.0, builds are avilable in copr, https://copr.fedorainfracloud.org/coprs/g/kdesig/plasma-5-unstable/ Feedback is welcome and encouraged. I've only done one quick upgrade test (on f24 box), and restarted my session. Nothing exploded. :) Doing official updates may have to wait a bit, as Fedora 25 is currently in beta freeze. -- Rex

10 19

dbus-update-activation-environment not working
by Fredy Neeser 30 Sep '16

30 Sep '16

Hello list My ~/.xsession-errors begins with startkde: Starting up... dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments This is on Fedora 24 with dbus-1.11.4-1.fc24.x86_64 plasma-workspace-5.7.5-2.fc24.x86_64 qt5-qtbase-5.6.1-3.fc24.x86_64 It seems like DBus Activation is not working for some apps -- see the related discussion here: [1] https://blog.martin-graesslin.com/blog/2014/06/dbus-activation-for-apps-in-… DBus Activation for apps in prefix [2] https://mail.kde.org/pipermail/plasma-devel/2015-October/045349.html Review Request 125768: Use dbus-update-activation-environment [3] https://github.com/NixOS/nixpkgs/issues/17943 dbus-update-activation-environment is broken As suggested by [3], I can reproduce the above error by running the following command: $ dbus-update-activation-environment --systemd --all dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments [3] also suggests a patch which seems to fix the issue for KDE5 / NixOS. Does anyone else experience this error? Which are the consequences? B.t.w., I don't get the usual KDE debug messages in ~/.xsession-errors, but I'm not sure if this is related in any way to the DBus Activation problem. Thanks Fredy Neeser IBM Zurich Research Laboratory CH-8803 Rueschlikon, Switzerland

1 0

Fedora 24 KDE screen resolution issue
by CS DBA 29 Sep '16

29 Sep '16

Hi All; I just received a new Lenovo X1 4th Generation laptop today. It has an Intel HD Graphics 520 card. I have a 3rd gen x1 as well running Fedora 24 with an Intel Graphics 5500 card. I've now installed Fedora 24 on the new (4th Generation) X1. If I go to System Settings --> Display and Monitor The old X1 with the 5500 card shows me a resolution of 1368x768 which is what I want. However the new X1 (the 520 card) running Fedora 24 (both are running the KDE spin) does not show 1368x768, nor does it show any resolutions that will work on the wide screen except the max resolution of 2560x1440. I can get a 1368x768 resolution via xrandr like this: xrandr --newmode "1368x768_60.00" 85.25 1368 1440 1576 1784 768 771 781 798 -hsync +vsync xrandr --addmode eDP-1 1368x768_60.00 xrandr --output eDP-1 --mode 1368x768_60.00 How can I get the System Settings --> Display and Monitor to reckognize / show the 1368x768 resolution? Thanks in advance

3 7

Apper should not override the widget style
by Kevin Kofler 29 Sep '16

29 Sep '16

Hi, Apper currently ships with a downstream hack (apper-0.9.2-style.patch) that makes it refuse to use the systemwide Qt widget style. This was done to workaround a harmless, purely cosmetic glitch (bug #1209017). But it causes a much worse cosmetic glitch: the application looks just completely off. Just compare the big progress bar on a stock Fedora 24 installation (where Oxygen is not available, and thus Cleanlooks is used) with a Breeze progress bar. It just looks completely wrong. Please see the discussion at: https://bugzilla.redhat.com/show_bug.cgi?id=1380097 I was asked to bring this to the mailing list, so I am doing that hereby. IMHO, native KDE applications must not be disguising themselves as GTK+ applications when running under Plasma. Kevin Kofler

2 1

F24, KDE Plasma 5.7.5: Menu and desktop widgets react to mouse events with seconds of delay
by Fredy Neeser 29 Sep '16

29 Sep '16

Hi list, Two days ago, I upgraded from F22 to F24. The dnf upgrade succeeded and applications seem to work, but there's a new, serious desktop usability problem: I'm using a dual-screen setup (LVDS + external monitor), where I usually set Primary dIsplay = external monitor. Moreover, I place the KDE Panel also on the external monitor. When I do that and try to navigate through the Application Menu (launcher with cascading popup menus) or when I click / move over a desktop widget, the following happens: - After a mouse left click on the KDE menu icon (left hand side of KDE Panel), the menu pops up only after a delay of >= 1 second - When the mouse pointer is moved to another item in a popup menu, the focus visibly jumps from item to item, and a delay of at least 1 second is added on every intermediate item. - When I click / move over a desktop widget, the desktop reacts with a delay of >= 1 second The delay problem consistently disappears when I set Primary display = Laptop Screen, even though the KDE Panel remains on the external monitor. It's strange that the KDE Panel does not move to the Primary display -- I'm likely seeing the following bug https://bugzilla.redhat.com/show_bug.cgi?id=1322724 Bug 1322724 - Plasma panel not on primary screen in F24 as well. Also, the delay problem typically reappears when I go back to Primary dIsplay = external monitor. Only in two out of perhaps a dozen logout-login cycles, I observed that the delay problem was gone, despite the fact that I had Primary dIsplay = external monitor. This may indicate some kind of race condition. Since this was an upgrade, I also tried the following, but the delay problem behaved the same: - Remove the contents of ~/.cache - Temporarily remove ~/.config, ~/.local and ~/.kde and login to KDE - Login to KDE as another user Version-release numbers: kscreen-5.7.5-1.fc24.x86_64 kwin-5.7.5-1.fc24.x86_64 plasma-desktop-5.7.5-1.fc24.x86_64 plasma-systemsettings-5.7.5-1.fc24.x86_64 plasma-workspace-5.7.5-2.fc24.x86_64 plasma-workspace-libs-5.7.5-2.fc24.x86_64 qt5-qtbase-5.6.1-3.fc24.x86_64 Any idea which component should be blamed or how to debug this problem? I wish some KDE debug messages could be seen in ~/.xsession-errors (I enabled the debug messages using kdebugsettings), but I don't see any of the familiar messages - maybe something is broken with the KDE debug messages as well. Thanks Fredy Neeser IBM Zurich Research Laboratory CH-8803 Rueschlikon, Switzerland

2 2

windows go behind panel
by CS DBA 28 Sep '16

28 Sep '16

Hi All; I'm running Fedora 24 KDE spin, when I full screen an app the window goes behind the panel If I check Panel Options --> Panel Settings --> More Settings I have "Always Visible highlighted Thanks in advance for any advice

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde September 2016