Bug 562452

Summary:	KNetworkManager does not start
Product:	[Fedora] Fedora	Reporter:	Armands Liepins <armandsl>
Component:	kde-plasma-networkmanagement	Assignee:	Ben Boeckel <fedora>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12	CC:	extras-orphan, fedora, kevin, ltinkl, mmcgrath, rdieter, roland.wolters, smparrish
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-02-06 21:13:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Armands Liepins 2010-02-06 20:03:35 UTC

Description of problem:
KNetworkManager does not start. It shows message box with "Another NetorkManager client is already running. Use KNetworkManeger in future?" and two buttons "Start automatically" and "Don't start automatically". If "Start automatically" is pressed, then on the next login this same message box appears. I had kde-plasma-networkmanagement and NetworkManager-gnome installed some time ago, but now them are uninstalled.

Version-Release number of selected component (if applicable):
knetworkmanager-0.9-0.3.20090930svn.fc12.2.i686

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
NetworkManager-0.7.997-2.git20091214.fc12.i686

Comment 1 Armands Liepins 2010-02-06 20:46:11 UTC

This was due to wrong context of /tmp/.X11-unix, doing restorecon /tmp/.X11-unix fixed the problem.

Comment 2 Armands Liepins 2010-02-06 20:50:51 UTC

But one question remains: why this message box?

Comment 3 Kevin Kofler 2010-02-06 21:13:36 UTC

(FYI, knetworkmanager is built from the kde-plasma-networkmanagement SRPM, as they're shipped together in one directory in upstream SVN. The knetworkmanager SRPM doesn't exist anymore, so reports against knetworkmanager go basically nowhere.)

*** This bug has been marked as a duplicate of bug 499183 ***