https://bugzilla.novell.com/show_bug.cgi?id=272829 Summary: Open Suse Updater - Corruption in application and error responses Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: scocoo@tpg.com.au QAContact: jsrain@novell.com Open Suse Update Application was fully functional without errors The only change to the environment was activating the Automatic Online Update application in Yast at a later point in time. After a 24 hour period expired the applet changed to a triangle with exclamation mark - see attached. Initial error response whilst hovering over alert was Error The updater could not access the packet manager engine. This usually happens when you have another application (like Yast) using it at the same time. Please close other application. The Yast configured automatic update was de-activated. The applet was closed and then re-opened into system tray with same outcome. The applet was then closed and system rebooted. *Applet remained on alert. The applet was opened and add/remove update source was opened with initial error response run is not in path Followed by the usual display of installation source and optional advanced configuration details which were greyed out. The applet was accessed and the "configure applet" was opened. A change was made from default to Novell Zenworks and oked. Applet then changed to normal functionality. The applet was accessed and the "configure applet" was re-opened and set to "default" *An unfortunate event then took place, the previous update source was non responsive and indicated update source was down and or possible corruption in DNS resolution of site. (Update source selected by automated registration was in Russia and functioned perfectly at first.) I opened Yast and opened installation sources. Error response was received indicating update source was not responsive and asked if I wanted to remove update source. I deliberately chose NO and closed the application, however the source was removed. The applet appeared to be functioning without errors now and a new source I opened Yast to auto register a new update source and a mirror in Australia was chosen. *Update functionality was not restored and applet issued no error responses, however when accessing the add/delete installation source was accessed instead of the usual green configuration screen Yast opened the Yast Catalogues and other open suse configuration details were not accessible. I understand this is an enormous sequence of events, some of which * are not logically understood. However it is theorised the it is possible to faithfully reproduce the corruption by activating the Yast Automatic Online Update - time initiated application whilst the open suse online update application has its own time initiated update schedule in place. Attached is Yast log files and image of open suse update application icon. Every care has been taken to state the sequence of events clearly and consistently - whether or not some * of the process has anything to do with the initial and presumable re-producible of corruption is severely questionable. Please advise if any further log files are required IF this cannot be re-produced in a test environment. -- 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, or are watching someone who is.