Bug 562452 - KNetworkManager does not start
Summary: KNetworkManager does not start
Keywords:
Status: CLOSED DUPLICATE of bug 499183
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-plasma-networkmanagement
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ben Boeckel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-06 20:03 UTC by Armands Liepins
Modified: 2010-02-06 21:13 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-06 21:13:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.