Bug 1283474

Summary:	network manager applet won't start after star-tup even it should
Product:	[Fedora] Fedora	Reporter:	spochybo
Component:	plasma-systemsettings	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	22	CC:	dcbw, jgrulich, jklimes, lkundrak, ltinkl, me, rdieter, than
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-24 14:18:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description spochybo 2015-11-19 04:43:49 UTC

With my Fedora22 that has KDE5, I am using the awesome window-manager. Since the updates on November 14th (update of systemsettings5 was part of it) I am encountering several problems, that seem to be connected to the loading of my systemsettings at the system-startup. The failure to load network manager applet is just one of them.

Further I cannot launch KDE applications like kshutdown or konsole, nor can I alter the startup/shutdown services (saying that KDED cannot be contacted), which results in not loading may Power Management profile.

Comment 1 Jirka Klimes 2015-11-24 08:44:55 UTC

You are probably talking about KDE graphical frontend (plasma-nm), because nm-applet is not run in KDE by default.

https://wiki.archlinux.org/index.php/NetworkManager#Graphical_front-ends

Comment 2 spochybo 2015-11-24 09:02:07 UTC

(In reply to Jirka Klimes from comment #1)
> You are probably talking about KDE graphical frontend (plasma-nm), because
> nm-applet is not run in KDE by default.
> 
> https://wiki.archlinux.org/index.php/NetworkManager#Graphical_front-ends

I am talking about nm-applet. I had it set to run at startup. However, this is not a problem anymore, and it seems to have been solved with a recent update (sometime last week). My systemsettings for the startup and shutdown services are now accessible and I do not get an error regarding KDED.

Anyway, I do not think that this was a problem with the applet in itself, but rather it had to do with the loading of the startup/shutdown settings at the beginning of a session. The problem is solved now.

Thanks, Sona

Comment 3 Rex Dieter 2015-11-24 14:18:42 UTC

Fwiw, plasma5 only recently (re)gained support for classic xembed-based systemtray icons

Closing per "problem is solved now"