On 30th March 2006 Ian wrote:
Hi all, I am running SuSE 10.0 OSS, Kernel 2.6.13-15.8-default, KDE 3.4 on a Dell 4300 P4 512MB 40GB system, as a desktop system, not a server. (All YOU updates are installed when available) I have a problem viewing 'System Log' via Yast. Clicking on the 'View System Log' icon produces the normal window, but then the whole system grinds to a halt, with all the available memory being used up, including the Swap memory. I hate having to rudely shutdown via the power button, but end up having no choice but to do so. All other Yast modules work correctly, including 'View Start-up Log'. I can only access the 'System Log' using an editor, such as Kate. Nothing related to this shows up in the Log when viewed so I have no idea where to check for the problem. Until today, there has not been any problem viewing the log. What could cause Yast System Log Viewer to run away with all the available memory? I can find nothing on 'Google' resembling these symptoms.
Regards Ian
As a follow up to this problem, I found that previously I had done a YOU update to update Cairo and XML::libXML Perl Module. Suspecting something fishy, yesterday (1st April) I downgraded these back to the originals, (via 'System Update', which informed me that I had a dependency problem with XML::libXML, which unfortunately I did not make a note of), and tonight I made a very brave decision to try to see the 'System Log' via Yast. Lo and Behold, no problem!!!??? Go figure!! Could any of the wise ones please tell me what on earth is going on with either of these packages because now SUSEWatcher informs me that these same updates are available, and I have no wish to make my system that unstable again. Or am I being a little hasty in blaming these packages? If YOU advises me that these patches are available, why does it miss dependencies when downloading and installing them? I remain baffled. Also could someone point me to the thread that explained how to make a 'Protected' flag stick in SUSEWatcher, just until this situation is resolved? Regards Ian