[opensuse] Worrying behavior at boot, in v11.2/kde4
The system boots, seemingly without any problem. When the process is over (no further HD activity), an attempt to move the mouse cursor from its position at the center of the screen causes the cursor to become invisible. Continuing to move the mouse causes erratic behavior on the screen, as though the "phantom mouse" is activating whatever icon it lights upon. When this v11.2 was first installed, this behavior did not appear (but in previous attempts to install v11.2, it was present in such a degree that I abandoned the installation and tried again from scratch -- at least three times). In the case of the current installation, there was no such problem at first; then after a few days, it was necessary to wait a few seconds and only then to use the mouse; now I have to wait several minutes before daring to move the mouse. It doesn't take a lot of imagination to suppose that it will keep getting worse. If it does as I expect, I will almost certainly give up v11.2 altogether in self defense. The OS is x86_64; the hardware is Pentium4. There is also a v11.1 installation on the machine which does not display the problem behavior. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-06-18 13:49, Stan Goodman wrote:
The system boots, seemingly without any problem. When the process is over (no further HD activity), an attempt to move the mouse cursor from its position at the center of the screen causes the cursor to become invisible. Continuing to move the mouse causes erratic behavior on the screen, as though the "phantom mouse" is activating whatever icon it lights upon.
When this v11.2 was first installed, this behavior did not appear (but in previous attempts to install v11.2, it was present in such a degree that I abandoned the installation and tried again from scratch -- at least three times). In the case of the current installation, there was no such problem at first; then after a few days, it was necessary to wait a few seconds and only then to use the mouse; now I have to wait several minutes before daring to move the mouse. It doesn't take a lot of imagination to suppose that it will keep getting worse. If it does as I expect, I will almost certainly give up v11.2 altogether in self defense.
The OS is x86_64; the hardware is Pentium4. There is also a v11.1 installation on the machine which does not display the problem behavior.
Is it fully updated? I mean the "official" updates. If not, then do. If you can't do it in graphical mode because it is unusable, then use text mode. Are you using any extra repos? If so, say which. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkwbgSMACgkQU92UU+smfQVyuQCdGYfnuLxdKsfvAr1Tvc4Tpb0c dUAAn3vWWbsge+R28JQnErBH/z37m04A =I2bm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 18 June 2010 17:22:27 Carlos E. R. wrote:
On 2010-06-18 13:49, Stan Goodman wrote:
The system boots, seemingly without any problem. When the process is over (no further HD activity), an attempt to move the mouse cursor from its position at the center of the screen causes the cursor to become invisible. Continuing to move the mouse causes erratic behavior on the screen, as though the "phantom mouse" is activating whatever icon it lights upon.
When this v11.2 was first installed, this behavior did not appear (but in previous attempts to install v11.2, it was present in such a degree that I abandoned the installation and tried again from scratch -- at least three times). In the case of the current installation, there was no such problem at first; then after a few days, it was necessary to wait a few seconds and only then to use the mouse; now I have to wait several minutes before daring to move the mouse. It doesn't take a lot of imagination to suppose that it will keep getting worse. If it does as I expect, I will almost certainly give up v11.2 altogether in self defense.
The OS is x86_64; the hardware is Pentium4. There is also a v11.1 installation on the machine which does not display the problem behavior.
Is it fully updated? I mean the "official" updates. If not, then do. If you can't do it in graphical mode because it is unusable, then use text mode.
Are you using any extra repos? If so, say which.
The existing repos are: Updates for openSUSE 11.2-0 cd:/// Debug Non-Oss Oss Source I assume that the system is properly updated -- despite the problem, it eventually boots to a useful state, or I shut down and try again successfully. Just now, it became useful only less than a minute after HD activity ceased. But I now notice that Debug and Source are not enabled; I think that at least the latter should be. But according to Software Manager, the kernel and the sources are matched. 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. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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. -- Regards Rajko, -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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 Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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
participants (4)
-
C -
Carlos E. R. -
Rajko M. -
Stan Goodman