F22 / KDE5

Tue Sep 15 14:20:15 UTC 2015

For anything not yet supporting status notifiers, you can use something like wmsystemtray (I do).

-- Rex

________________________________________
From: kde-bounces at lists.fedoraproject.org <kde-bounces at lists.fedoraproject.org> on behalf of Reindl Harald <h.reindl at thelounge.net>
Sent: Tuesday, September 15, 2015 9:18 AM
To: kde at lists.fedoraproject.org
Subject: Re: F22 / KDE5

Am 15.09.2015 um 15:51 schrieb Emilio Recio:
> Sorry, I agree with all that, but have to add the missing system tray!

systray was part of my initial posting

* it don't work for applications which where used
   with Exec=ksystraycmd while the UI still offers
   it and does nothing else than add it to the command
* it don't work with "alltray", klick on Thundebird, Eclipse
   or "rdesktop" and the windows disappears and never
   comes back
* no idea if the developers only work with short tasks but
   i know nobody which is closing his mailprogram and IDE
   all day long to start it again while the space in the
   windowbar is not endlessly

BTW:

i guess the 30 seconds waiting at login are caused by *repeatly* try to
start "upower" and "networkmanager" - both are not needed on a
workstation behind a UPS with static network configuration

"upower" in fact is masked because the machine of my co-developer a few
weeks ago startet to power of the monitor directly after login into KDE
and since "upower" is gone that don't happen - i know that this is a bug
somewhere but it's not worth to dig around remote in case of services
with no business in the current setup

Sep 15 16:08:38 rh.thelounge.net sddm-helper[7444]:
pam_unix(sddm:session): session opened for user harry by (uid=0)
Sep 15 16:08:39 rh.thelounge.net org.kde.kded5[7471]: Qt: Session
management error: networkIdsList argument is NULL
Sep 15 16:08:39 rh.thelounge.net dbus[882]: [system] Activating via
systemd: service name='org.freedesktop.UPower' unit='upower.service'
Sep 15 16:08:39 rh.thelounge.net dbus[882]: [system] Activation via
systemd failed for unit 'upower.service': Unit upower.service is masked.
Sep 15 16:08:39 rh.thelounge.net polkitd[1194]: Registered
Authentication Agent for unix-session:132 (system bus name :1.397
[/usr/libexec/kf5/polkit-kde-authentication-agent-1], object path
/org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activating via
systemd: service name='org.freedesktop.UPower' unit='upower.service'
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activation via
systemd failed for unit 'upower.service': Unit upower.service is masked.
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activating via
systemd: service name='org.freedesktop.UPower' unit='upower.service'
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activation via
systemd failed for unit 'upower.service': Unit upower.service is masked.
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activating via
systemd: service name='org.freedesktop.UPower' unit='upower.service'
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activation via
systemd failed for unit 'upower.service': Unit upower.service is masked.
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activating via
systemd: service name='org.freedesktop.UPower' unit='upower.service'
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activation via
systemd failed for unit 'upower.service': Unit upower.service is masked.
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activating via
systemd: service name='org.freedesktop.NetworkManager'
unit='dbus-org.freedesktop.NetworkManager.service'
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activation via
systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service':
Unit NetworkManager.service is masked.
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activating via
systemd: service name='org.freedesktop.NetworkManager'
unit='dbus-org.freedesktop.NetworkManager.service'
Sep 15 16:08:40 rh.thelounge.net dbus[882]: [system] Activation via
systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service':
Unit NetworkManager.service is masked.
Sep 15 16:08:40 rh.thelounge.net org.a11y.Bus[7471]: GLib-GIO-Message:
Using the 'memory' GSettings backend.  Your settings will not be saved
or shared with other applications.
Sep 15 16:08:41 rh.thelounge.net dbus[882]: [system] Activating via
systemd: service name='org.freedesktop.UPower' unit='upower.service'
Sep 15 16:08:41 rh.thelounge.net dbus[882]: [system] Activation via
systemd failed for unit 'upower.service': Unit upower.service is masked.
Sep 15 16:08:41 rh.thelounge.net dbus[882]: [system] Activating via
systemd: service name='org.freedesktop.UPower' unit='upower.service'
Sep 15 16:08:41 rh.thelounge.net dbus[882]: [system] Activation via
systemd failed for unit 'upower.service': Unit upower.service is masked.
Sep 15 16:08:41 rh.thelounge.net systemd-logind[844]: Removed session 131.
Sep 15 16:09:05 rh.thelounge.net dbus[882]: [system] Activating via
systemd: service name='org.freedesktop.UPower' unit='upower.service'
Sep 15 16:09:05 rh.thelounge.net dbus[882]: [system] Activation via
systemd failed for unit 'upower.service': Unit upower.service is masked.
Sep 15 16:09:05 rh.thelounge.net dbus[882]: [system] Activating via
systemd: service name='org.freedesktop.UPower' unit='upower.service'
Sep 15 16:09:05 rh.thelounge.net dbus[882]: [system] Activation via
systemd failed for unit 'upower.service': Unit upower.service is masked.

> On 09/14/15 18:56, Patrick O'Callaghan wrote:
>> On Tue, 2015-09-15 at 00:19 +0300, Eli Wapniarski wrote:
>>> On Monday 14 September 2015 20:17:33 Reindl Harald wrote:
>>>> so, upgraded to F22
>>>>
>>>> honestly, before these fools of kde-developers start to think about
>>>> KDE6
>>>> they better go out and drinling some beers for 5-1^0 years and no
>>>> progress at all - if it ain#t broken don't fix it - seriously
>>>>
>>>> and before the next time Fedora decides to switch to KDE6 or
>>>> whatever
>>>> major release wait until the currently used one is really out of
>>>> support
>>>>
>>>> AND THEN PEOPLE WONDER WHY LINUX DESKTOPS HAVE NO BIG MARKET-SHARE,
>>>> FRANKLY WITH THE EXPIERIENCE KDE3 -> KDE4 / KDE4_> KDE5 I WOULD BE
>>>> A
>>>> FOOL TO RECOMMEND TO ANY NON-DEVLOPER SWITCH TO IT
>>>
>>>
>>> OK...
>>>
>>> Now that we have heard more than enough complaints.... How do we
>>> revert back?
>>>
>>> This is a serious question. I have yet to hear anyone compliment KDE5
>>> in anyway shape or form.
>>
>> Maybe because people mostly post when they have something to complain
>> about. Off the top of my head, my only problems with KDE5 are:
>>
>> 1) SDDM doesn't support gnome-keyring, so I have to use KDM
>> 2) Session Restore still doesn't work properly
>> 3) I get Plasma crashes pretty much every time I logout, but not
>> otherwise, and no freezes (touch wood)
>>
>> Everything else seems to work for me. I'm using the Nvidia driver, if
>> it matters.