https://bugzilla.novell.com/show_bug.cgi?id=388773 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=388773#c1 Stefan Hundhammer <sh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mvidner@novell.com --- Comment #1 from Stefan Hundhammer <sh@novell.com> 2008-05-09 09:26:23 MST --- This is only a very rough assessment what probably happened here: You updated a lot of packages. You did not have SuSEfirewall2 installed at that time, so there was no need to update SuSEfirewall2, too. Then you started the YaST2 time module and decided to synchronize your system time via NTP. But since (at least, so I assume) yast2-firewall and SuSEfirewalll2 were not installed at that time yet, and xntp, using a network protocol, requires a firewall port to be opened, additional packages had to be installed - yast2-firewall (which has the YaST2 infrastructure to open or close firewall ports), SuSEfirewall2 (required by yast2-firewall) and some packages they depend upon. Since you had just updated your system, the most recent versions of those packages had to be retrieved from the network. Why it also updated sane-backends-autoconfig, mozilla-xulrunner190, perl-doc, ispell etc. I don't know. This might be a very unfortunate combination of dependencies. The most important question here is if there is a reasonable way for that time module to determine if a firewall is running at all, and thus if it makes sense to install yast2-firewall and its dependencies (SuSEfirewall2). In your specific case, this hurt. There may be more users who get this problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.