Bug 537907 - Networkmanager does not use netconfig to update resolv.conf anymore
Summary: Networkmanager does not use netconfig to update resolv.conf anymore
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Network (show other bugs)
Version: Factory
Hardware: x86 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Tambet Ingo
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-09 21:46 UTC by Forgotten User ZhJd0F0L3x
Modified: 2016-04-15 09:51 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
NetworkManager console log (7.96 KB, text/plain)
2009-09-09 21:46 UTC, Forgotten User ZhJd0F0L3x 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User ZhJd0F0L3x 2009-09-09 21:46:02 UTC 
Created attachment 317498 [details]
NetworkManager console log

I have this problem since today, when I switched to an i586 machine. An x86_64 machine with the same package version does not have this problem.

The problem is, that I always get the following:

NetworkManager: <info>  Activation (cable) successful, device activated.
NetworkManager: <info>  Activation (cable) Stage 5 of 5 (IP Configure Commit) complete.
ATTENTION: You have modified /etc/resolv.conf.  Leaving it untouched...
You can find my version in /etc/resolv.conf.netconfig ...


reading the code, I guess that NetworkManager always thinks that run_netconfig has failed, thus updates resolv.conf on its own, and then, when netconfig finally wants to update resolv.conf, NM already has changed it and thus netconfig refuses to do so.

I'll attach a log from running NM with "--no-daemon" which will also show some 
GLib-GObject-CRITICAL around this time, which might be related.

Hope this helps ;)
Comment 1 Tambet Ingo 2009-10-05 08:59:50 UTC 
Thanks. Fixed.
Comment 2 Bernhard Wiedemann 2016-04-15 09:51:21 UTC 
This is an autogenerated message for OBS integration:
This bug (537907) was mentioned in
https://build.opensuse.org/request/show/42233 11.3 / NetworkManager