http://bugzilla.novell.com/show_bug.cgi?id=595432 http://bugzilla.novell.com/show_bug.cgi?id=595432#c0 Summary: knetworkmanager's rc-file not updated because its date is more current than /etc/sysconfig/network/config Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers@suse.de ReportedBy: sven.burmeister@gmx.net QAContact: qa@suse.de Found By: --- Blocker: --- 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 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.