Bug 595432 - knetworkmanager's rc-file not updated because its date is more current than /etc/sysconfig/network/config
Summary: knetworkmanager's rc-file not updated because its date is more current than /...
Status: RESOLVED WONTFIX
: 561095 (view as bug list)
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: KDE4 Applications (show other bugs)
Version: RC 2
Hardware: Other Other
: P2 - High : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-09 19:38 UTC by Forgotten User --EoyBps8f
Modified: 2012-01-17 10:56 UTC (History)
1 user (show)

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

Attachments
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 --EoyBps8f 2010-04-09 19:38:42 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8

If one changes from traditional to networkmanager in yast knetworkmanager should get started as well, which does not always happen. Thus the user starts it manually and connects to a network which updates the rc file because of the "LastUsed" field.

knetworkmanager.default.sh is run at kde login and checks whether networkmanagementrc is older than /etc/sysconfig/network/config. I guess this is meant to prevent it overwriting manual changes, yet because the rc got updated with the "LastUsed" after the user changed the network settings via YaST, it will not change the "Autostart" to "yes".

The easiest solution would be to not care about the date of the rc-file. The reasoning for this would simply be that there are more people that switch to NetworkManager because they want to use knetworkmanagemer than users that switch to NetworkManager but do not want to use it.

Reproducible: Always
Comment 1 Forgotten User --EoyBps8f 2011-12-08 18:51:37 UTC 
*** Bug 561095 has been marked as a duplicate of this bug. ***
Comment 2 Forgotten User --EoyBps8f 2012-01-17 10:56:14 UTC 
Too old.