On Saturday 19 June 2010 12:45:44 C wrote:
On Sat, Jun 19, 2010 at 09:38, Stan Goodman wrote:
On Saturday 19 June 2010 01:02:46 Rajko M. wrote:
On Friday 18 June 2010 15:09:24 Stan Goodman wrote:
Fore completeness: shortly after initial installation, there was a time when it went on an extensive update that lasted at least twenty minutes before it stalled (according to the progress gauge, it was about half through), Since it never resumed updating, I eventually shut down. I expected that it would return later to what had not been updated, but there has never been a time when I saw enough updating activity to acccount for the missing half.
It happened to me that larger packages and slower server made update long lasting process, but I never stop installation before it bails out by itself. Interrupting installation is receipt for repeated installation to bring all in order.
Hi, Rajko...
I didn't stop installation. Please read again the first sentence of my paragraph above. The installation was complete, and the system have been rebooted at least once. Only then did the very long automatic update process start, involving many packages,
Stan, I think Rajko meant he never stopped an update in the middle of the update... this could very well be the whole source of your problems... a partial update.. you get some components running at one version and possible dependencies at other incompatible versions. I would REALLY recommend that you finish the update as Carlos suggested.
C.
I ran YaST update. As soon as it started, its screen disappeared. I don't know if that is the expected behavior or if it crashed, or if it did anything before vanishing. There was very little, if any, activity through the router to indicate updating. Personally, I would be in favor of more user feedback from YaST software operations. So I ran zypper, per Carlos's other suggestion, in order to get some sort of report, which turned out to be "Nothing to do", which is reassuring. Two reboots of v11.2 have passed since, without the problem I reported, so the tentative assumption is that the YaST update did correct a mismatch. Thank you Carlos. This has not affected the no-sound problem presented in another thread. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org