After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 589639 - Network Manager cannot access system wide connection settings
Network Manager cannot access system wide connection settings
Status: RESOLVED INCOMPLETE
Product: NetworkManager
Classification: Platform
Component: general
0.7.x
Other All
: Normal major
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2009-07-24 19:04 UTC by Hadmut Danisch
Modified: 2010-04-10 19:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
ruby script I use for testing (1.23 KB, text/plain)
2009-07-24 19:06 UTC, Hadmut Danisch
Details

Description Hadmut Danisch 2009-07-24 19:04:35 UTC
Please describe the problem:
Hi, 

I am using Network Manager on several machines with Ubuntu 9.04. 

On some (not all) of these machines a certain problem occurs: When setting a connection to system wide availability, a file is generated in /etc/NetworkManager/system-connections as expected, but then neither Network Manager nor nm-connection-editor can see this connection. 

Even when querying dbus for network connection settings with a small ruby script it does not find those connections. On the machines where it works it lists the existing connections, while on the machines where it does not work it gets an empty list from dbus. 

Unfortunately there is no point to start with for debugging. Docs don't tell where to start debugging, source code comments are as good as not existing and the software structure is complex. No way to see why the nm-system-settings daemon does find the connections on some of my machines and doesn't on others. 


Steps to reproduce:
1. no idea how to reproduce, not even removing and reinstalling the software helps
2. 
3. 


Actual results:


Expected results:


Does this happen every time?
On the machines where it does not work, it never works. 

Other information:
Comment 1 Hadmut Danisch 2009-07-24 19:06:46 UTC
Created attachment 139173 [details]
ruby script I use for testing

on some machines it lists the know connections, on others it doesn't (empty list of connections although they exist in /etc/NetworkManager/system-connections)
Comment 2 Dan Williams 2009-10-16 02:21:38 UTC
Any chance you can attach one of the files that fails to be found?  Does it get found if you 'killall -TERM nm-system-settings' ?
Comment 3 Tobias Mueller 2010-04-10 19:59:00 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!