Updates Messing With Kinternet And Tor

I just did a fresh install of openSUSE 10.3. I did a kernel update, installed madwifi and nvidia drivers. So far everything is good to go. I install and setup kinternet to get me internet on boot even if if I'm not logged on KDE. I install and setup tor and privoxy to start on boot. I also setup NTP client to sync my clock on boot. I have this all setup to work on boot. So far everything worked with out any problems.

Notice I say "worked" as in past tense. >:-|

I don't like to use yast if I can help it. It's sloowww! I install Smart and add the SUSE Update repo to get the rest of the SUSE patches as well as Packman to fix the broken stuff. I decide to do a full update of everything. Normally this doesn't give me any problems except for this time. After all that I did reboot just because. I hit escape on the suse logo to watch everything to make sure there's no errors. The only error was that the network failed. As if it's having problems connecting or getting a IP assigned from the routers DNS server. This error didn't happen until I installed the rest of the suse updates. Before, the only update I installed was the kernel.

I can get a internet connection if I log on KDE and left click once on the kinternet icon next to the clock to "reset" it to get online. My question is, what patch or update did I install that fsked it all up. What ever it is also affected Tor. I had Tor setup to start on bootup and now it's funky to, I end up having to restart tor or I can't get programs like xchat or firefox to connect to it.

What every was updated or changed is affecting both Tor and keeping me from getting a proper internet connection on a fresh boot. What I'm looking for is a list of packages that might have been changed that's related to the network aspects of suse. I'm not all that familiar with the ins and outs of suse. So I would appreciated if someone can help me narrow down this issue.

After an hour of reboots and process of elimination I've manage to localize the package responsible. It's the [sysconfig] package. I ended up downgrading the package to the default from the openSUSE 10.3 DVD. Here's more information on the package.

Working version - 0.70.2-4 x86_64 from DVD (I'm running this version as of now until the patch can be fixed)
Non Working version - 0.70.2-4.5 x86_64 from Main Update Repository

sysconfig - The sysconfig scheme

This package provides the SuSE system configuration scheme.

I'll be contacting the authors to see if they can help remedy the situation.

That's what you get if you do heavy updates with package manager such smart. I does really bad job with dependency checking (does it at all?). Yast would probably told you that there is something wrong and all this might have never happened :D

That's what you get if you do heavy updates with package manager such smart. I does really bad job with dependency checking (does it at all?). Yast would probably told you that there is something wrong and all this might have never happened
[/b]

Actually, it has nothing to do with that. The issue is with the sysconfig RPM or specifically the update from the official suse update repo. So it has nothing to do with what package manager I used.