On Thu, 16 Dec 2010 01:29:43 +0530, Stan Goodman wrote:

No. the new repo is install ed with: http://download.opensuse.org/repositories/KDE/Distro/Factory/openSUSE_11.3 kde45>. What is optional is installation of another repo, which is called "Extra", the purpose of which is not explained.

what i suspected: you tried to upgrade to KDE 4.5.85, also known as KDE 4.6 beta2. when that article was posted, that was where KDE 4.5 lived; now it doesn't anymore. and this still could have worked out ok, but you did "zypper dup" with all your repos enabled. in that case, zypper doesn't really know what you want to upgrade to which version, and i have no idea what the solver process came up with. IMO, what you should do now is do "zypper dup" with only the standard repos enabled (oss, non-oss), then add the packman (and any other repos you need) and upgrade their packages. then add the real KDE 4.5.4 repo to yast: http://download.opensuse.org/repositories/KDE:/Release:/45/openSUSE_11.3/ [assuming you're on openSUSE 11.3; too lazy to look up the whole thread now.] then run "zypper dup" or switch all packages to the KDE 4.5 repo via yast. (i find the latter safer, since it's easier to see and edit potential problems than with zypper output.) ----------- zypper dup -r ----------- -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 16 Dec 2010 03:23:07 +0530, Stan Goodman wrote:

Believe it or not, I find that sequence confusing, and I want not to introduce more confusion to what already exists. Would you mind please to lay that out in detailed form?

then we'll have to start with what you have now. i didn't see you posting the output of "zypper lr -d" earlier in this thread. (forgive me if i'm wrong and you did...). that would clear any misunderstanding in this regard. and i'd like to know what you did after enabling the KDE repo, which zypper command(s) that was. from what you describe it seems obvious that you got different KDE versions, at least in part, on your system, and that doesn't work. this can usually be rectified by "zypper dup" with and from the correct repositories. -- phani -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 12/22/2010 03:39 PM, Stan Goodman pecked at the keyboard and wrote:

On Thursday 16 December 2010 00:05:13 phanisvara das wrote:

...

On Thu, 16 Dec 2010 03:23:07 +0530, Stan Goodman

I have to apologize for disappearing during the week that has passed since your note. It was unavoidable, for medical reasons, so that I did not have the time to concentrate on tis problem. I am back now, and hope we can continue.

Welcome back, hope all is well.

...

wrote:

...

Believe it or not, I find that sequence confusing, and I want not to introduce more confusion to what already exists. Would you mind please to lay that out in detailed form?

then we'll have to start with what you have now. i didn't see you posting the output of "zypper lr -d" earlier in this thread. (forgive me if i'm wrong and you did...). that would clear any misunderstanding in this regard.

and i'd like to know what you did after enabling the KDE repo, which zypper command(s) that was.

That is unclear. I think I've described everything that I did. If you want me to repeat, I will do so, but I don't think there is anything else to add in that respect.

Since zypper is a command line program what did you type at the command line when you ran zypper? Was it zypper up or zypper dup?

...

from what you describe it seems obvious that you got different KDE versions, at least in part, on your system, and that doesn't work. this can usually be rectified by "zypper dup" with and from the correct repositories.

-- phani

Your suggestion in your note of 16 December was as copied below, with my further questions: *****

...

IMO, what you should do now is do "zypper dup" with only the standard repos enabled (oss, non-oss), then add the packman (and any other repos you need) and upgrade their packages. then add the real KDE 4.5.4 repo to yast:

Would you please make the "zypper dup" instruction more explicit by including its argument?

There is no further argument, dup is the argument to zypper!

The remainder of your paragraph above isn't clear to me, because I don't understand what more is to be done after the "zypper dup" (nor do I know what to expect as the result of the "zypper dup"). Is this about d/l KDE packages for KDE4.5? Does that have to done individually for each KDE package? But if it is about KDE packages, why the reference to packman?

If you have the proper repos added with the proper priorities zypper dup is all that is needed to upgrade KDE to 4.5. Again, what is the result of zypper lr -d? If you don't supply the info requested how can you expect us to help you?

...

http://download.opensuse.org/repositories/KDE:/Release:/45/openSUSE_11.3 /

[assuming you're on openSUSE 11.3; too lazy to look up the whole thread now.]

I am on 11.3.

...

then run "zypper dup" or switch all packages to the KDE 4.5 repo via yast. (i find the latter safer, since it's easier to see and edit potential problems than with zypper output.)

I am flummoxed by this paragraph, because the earlier paragraphs above have had mr run "zypper dup......", then do the download, and here again we are talking about "zypper dup" and switching packages.

It means to use either YaST--> software manager--> RPM groups click on zzz All (on the left at the bottom of the list), then at the top click on Package, All in This List, Update if newer version available *_or_* at the command line use zypper dup to upgrade KDE to 4.5. You need to use zypper dup because a change in vendor (repo) is required. zypper up will not change to another vendor.

*****

There is yet another part of this problem that hasn't been mentioned yet. As I described in my original query, the system at present is altogether unusable, so I would not be able to perform any of the suggested actions using the GUI. I assume (hope) that run level 3 would enable me to work; I know how to move from run level 5 to 3 in a normally operating system, but I do not know, and haven't been able to find, how to boot directly to text based interface when the system is still configured for level 5.

When at the boot prompt type a 3and hit enter. That will boot to runlevel 3 (text mode). -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 23 Dec 2010 02:59:45 +0530, Ken Schneider - openSUSE

On Wednesday 22 December 2010 23:41:40 phanisvara das wrote: list3@bout-tyme.net> wrote:

...

...

Would you please make the "zypper dup" instruction more explicit by including its argument?

There is no further argument, dup is the argument to zypper!

ahem, i disagree. i almost always limit zypper dup with the "r" or "--from" argument. i think it's the only way to make sure zypper understands exactly what i want it to do. otherwise, with more than the standard repos enabled, you might get surprising results.

Not to argue, but I think the argument of a function is the part that is the object of the function, i.e., in terms of Linux commands, the part that comes AFTER the switches and options. But I think my question was superflous. After studying the thread more carefully through my bleary eyes, I see that the command was given as: zypper dup -r , so that the argument is the URI of the repo. It's late now, after midnight. I'll write a better note with questions tomorrow. BTW, Ken's note (apparently in response to mine) never arrived here. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 22 December 2010 23:29:45 Ken Schneider - openSUSE wrote:

On 12/22/2010 03:39 PM, Stan Goodman pecked at the keyboard and wrote:

...

On Thursday 16 December 2010 00:05:13 phanisvara das wrote:

...

On Thu, 16 Dec 2010 03:23:07 +0530, Stan Goodman

I have to apologize for disappearing during the week that has passed since your note. It was unavoidable, for medical reasons, so that I did not have the time to concentrate on tis problem. I am back now, and hope we can continue.

Welcome back, hope all is well.

...

...

wrote:

...

Believe it or not, I find that sequence confusing, and I want not to introduce more confusion to what already exists. Would you mind please to lay that out in detailed form?

then we'll have to start with what you have now. i didn't see you posting the output of "zypper lr -d" earlier in this thread. (forgive me if i'm wrong and you did...). that would clear any misunderstanding in this regard.

and i'd like to know what you did after enabling the KDE repo, which zypper command(s) that was.

That is unclear. I think I've described everything that I did. If you want me to repeat, I will do so, but I don't think there is anything else to add in that respect.

Since zypper is a command line program what did you type at the command line when you ran zypper? Was it zypper up or zypper dup?

Neither. The page I was using called for zypper <asdreopo> -f, where http://download.opensuse.org/repositories/KDE/Distro/Factory/openSUSE_11.3 kde45.

...

...

from what you describe it seems obvious that you got different KDE versions, at least in part, on your system, and that doesn't work. this can usually be rectified by "zypper dup" with and from the correct repositories.

-- phani

Your suggestion in your note of 16 December was as copied below, with my further questions: *****

...

IMO, what you should do now is do "zypper dup" with only the standard repos enabled (oss, non-oss), then add the packman (and any other repos you need) and upgrade their packages. then add the real KDE 4.5.4 repo to yast:

Would you please make the "zypper dup" instruction more explicit by including its argument?

There is no further argument, dup is the argument to zypper!

...

The remainder of your paragraph above isn't clear to me, because I don't understand what more is to be done after the "zypper dup" (nor do I know what to expect as the result of the "zypper dup"). Is this about d/l KDE packages for KDE4.5? Does that have to done individually for each KDE package? But if it is about KDE packages, why the reference to packman?

If you have the proper repos added with the proper priorities zypper dup is all that is needed to upgrade KDE to 4.5.

Again, what is the result of zypper lr -d? If you don't supply the info requested how can you expect us to help you?

...

...

http://download.opensuse.org/repositories/KDE:/Release:/45/openSUSE_ 11.3 /

[assuming you're on openSUSE 11.3; too lazy to look up the whole thread now.]

I am on 11.3.

...

then run "zypper dup" or switch all packages to the KDE 4.5 repo via yast. (i find the latter safer, since it's easier to see and edit potential problems than with zypper output.)

I am flummoxed by this paragraph, because the earlier paragraphs above have had mr run "zypper dup......", then do the download, and here again we are talking about "zypper dup" and switching packages.

It means to use either YaST--> software manager--> RPM groups click on zzz All (on the left at the bottom of the list), then at the top click on Package, All in This List, Update if newer version available *_or_* at the command line use zypper dup to upgrade KDE to 4.5. You need to use zypper dup because a change in vendor (repo) is required. zypper up will not change to another vendor.

...

*****

There is yet another part of this problem that hasn't been mentioned yet. As I described in my original query, the system at present is altogether unusable, so I would not be able to perform any of the suggested actions using the GUI. I assume (hope) that run level 3 would enable me to work; I know how to move from run level 5 to 3 in a normally operating system, but I do not know, and haven't been able to find, how to boot directly to text based interface when the system is still configured for level 5.

When at the boot prompt type a 3and hit enter. That will boot to runlevel 3 (text mode).

-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 12/23/2010 03:24 AM, phanisvara das pecked at the keyboard and wrote:

On Thu, 23 Dec 2010 12:16:40 +0530, Stan Goodman wrote:

...

...

Since zypper is a command line program what did you type at the command line when you ran zypper? Was it zypper up or zypper dup? Neither. The page I was using called for zypper <asdreopo> -f, where http://download.opensuse.org/repositories/KDE/Distro/Factory/openSUSE_11.3

kde45.

that information was correct at the time the article was written: KDE 4.5.x was in KDE/Distro/Factory then. by now, factory contains KDE 4.6 beta2. apart from that, switching to a newer release of KDE requires to run 'zypper dup' after adding the repo; otherwise packages won't be switched over to the new repo.

'zypper up' updates packages when new ones are available in the repo they originally were installed from; 'zypper dup' switches packages to the repo that contains the newer packages. if several repos are enabled, it's always advisable to specify which repo to use for the 'distribution update' -- either by disabling all other repos for the update, or by specifying the repo with 'zypper dup --from '. otherwise it's pretty unpredictable what zypper will do when it finds the same packages in several repos.

if i remember correctly, the situation now is that your system got messed up by combining packages from incompatible repos. the safest and most straight-forward way to fix this would be a new install, keeping your /home partition intact. but if you installed many programs in addition to the standard installation, that may result in a lot of work, and trying to rescue the existing system may be desirable.

Before doing a new install first try to recover by removing the errant repo. You can do this with zypper rr: zypper rr -h removerepo (rr) [options] (zypper lr will give you this) Remove repository specified by alias, number or URI. Command options: --loose-auth Ignore user authentication data in the URI. --loose-query Ignore query string in the URI. Once the repo(s) are removed: zypper ref zypper dup should fix the problem with the messed up KDE. I have used this in the past many times after installing the newest KDE and finding that KDE was so bad I couldn't login. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 23 Dec 2010 19:05:34 +0530, Ken Schneider - openSUSE

On Thursday 23 December 2010 15:43:16 phanisvara das wrote: list3@bout-tyme.net> wrote:

...

Once the repo(s) are removed: zypper ref zypper dup

yes, but all additional repos should be removed for this, not only the 'errant' ones. if you have per ex. packman, videolan, and some others enabled, zypper dup would be likely to create havoc (again).

as i wrote earlier: only the standard repos should be enabled for this: OSS, non-OSS, and update. after that you'll get a system with KDE 4.4, which isn't what the original poster wants. so then he can add the desired KDE repo, and do zypper dup, limiting the update to that repo.

I'm ready now to try to reconstruct KDE4.4 as it was before the time trap I fell into. I'm in run level 3, have extracted the list of existing repos with zypper lr -d, and want now to disable (rather than delete) all of them save the rhree basic ones. I have browsed man zypper for a way to do that, but have found none. Is there a way? If not, I will delete them. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 28 December 2010 11:25:28 Stan Goodman wrote:

I'm ready now to try to reconstruct KDE4.4 as it was before the time trap I fell into. I'm in run level 3, have extracted the list of existing repos with zypper lr -d, and want now to disable (rather than delete) all of them save the rhree basic ones. I have browsed man zypper for a way to do that, but have found none. Is there a way? If not, I will delete them.

man zypper shows me zypper modifyrepo --disable should do what you want (the same search command works in man pages that works in vim -- i searched on 'disable' first, then started over searching for 'modifyrepo') mr is shorthand for modifyrepo, -d for --disable sc -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 28 December 2010 20:48:31 phanisvara das wrote:

On Tue, 28 Dec 2010 22:55:28 +0530, Stan Goodman wrote:

...

I'm ready now to try to reconstruct KDE4.4 as it was before the time trap I fell into. I'm in run level 3, have extracted the list of existing repos with zypper lr -d, and want now to disable (rather than delete) all of them save the rhree basic ones. I have browsed man zypper for a way to do that, but have found none. Is there a way? If not, I will delete them.

------------ zypper mr -d ------------

We are past that stage now, and zypper dup has been chugging away for over an hour, doing its thing. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 28 December 2010 22:08:58 phanisvara das wrote:

On Wed, 29 Dec 2010 01:19:07 +0530, Stan Goodman wrote:

...

...

------------ zypper mr -d ------------

We are past that stage now, and zypper dup has been chugging away for over an hour, doing its thing.

yes, i didn't see the other posts saying the same thing before i posted this one. sounds good, and good luck!

That's what I thought too. The reinstallation is finished now, after an hour and a half plus, and I was told that some programs haven't been restarted because they depended on files that have been deleted. I was advised to run zypper -ps. That produced a file of nearly 30KB, containing a list of what appear to be library files; I was able to save this file, but not to copy it to another machine through NFS, so I can't exhibit it here. What am I to make of this? Is this normal in the circumstances? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 28 December 2010 23:13:01 Patrick Shanahan wrote:

* Stan Goodman [12-28-10 15:58]:

lots of *mis*understanding here.

...

That's what I thought too. The reinstallation is finished now, after an hour and a half plus, and I was told that some programs haven't been restarted because they depended on files that have been deleted. I was advised to run zypper -ps.

the command is "zypper ps" and it is to show programs that *need* to be restarted because the files they depend on where deleted and/or replaced. Dropping to runlevel 3 should clear *most* of them. The others need to be "kill -HUP <process-id>" or failing that, "kill -9 <process-id>". Then return to runlevel 5.

I was already at run level 3. In the meanwhile, I rebooted to level 5, and found a desktop that looks normal except for the absence of a panel and the immobility of the mouse cursor. Now, having seen your message, I booted to level 3, ran zypper ps again, and found the happy news that there are no files that depended on deleted files, so all has now been cleaned.

or, you could restart your system.

Then I rebooted to level 5 again, which is where it is now. The desktop is incomplete, missing the Desktop Folder window, but the panel is present. The chameleon is still there, as is the progress gauge under it, which seems to be fully extended. The mouse cursor, after several boots, is still frozen.

...

That produced a file of nearly 30KB, containing a list of what appear to be library files; I was able to save this file, but not to copy it to another machine through NFS, so I can't exhibit it here.

-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 29 December 2010 01:16:47 Patrick Shanahan wrote:

* Stan Goodman [12-28-10 17:47]:

...

I was already at run level 3. In the meanwhile, I rebooted to level 5,

as confused as you seem to be, it is time to get terms straightened out; you didn't "reboot" to runlevel 5, rebooting is restarting your computer, you "changed/init" to runlevel 5.

No, in fact I rebooted, taking a timeout to empty my bladder and make a cup of tea for the next time. Confusion is one thing, jumping to conclusions is quite another. And making an issue of trivia is different entirely.

...

and found a desktop that looks normal except for the absence of a panel and the immobility of the mouse cursor.

panel probably not there because the "layout" is not set to ?? or your ~/.kde4 exists as you ?previously? had it.

Apparently not. Read further.

...

Now, having seen your message, I booted to level 3, ran zypper ps again, and found the happy news that there are no files that depended on deleted files, so all has now been cleaned.

Then I rebooted to level 5 again,

no.

Why "no"?

...

which is where it is now.

The desktop is incomplete, missing the Desktop Folder window, but the panel is present.

??, this is a configuration setting.

I interpret as meaning that the boot process is not yet complete, and has got stuck. The reason I think this is that the progress gauge, although close to its maximum length, has not been dismissed. This seems reasonable to me.

...

The chameleon is still there, as is the progress gauge under it, which seems to be fully extended. The mouse cursor, after several boots, is still frozen.

sounds like X is lockedup/crashed.

-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 28 December 2010 23:14:17 phanisvara das wrote:

On Wed, 29 Dec 2010 02:25:11 +0530, Stan Goodman wrote:

...

On Tuesday 28 December 2010 22:08:58 phanisvara das wrote:

...

On Wed, 29 Dec 2010 01:19:07 +0530, Stan Goodman

wrote:

...

...

...

------------ zypper mr -d ------------

We are past that stage now, and zypper dup has been chugging away for over an hour, doing its thing.

yes, i didn't see the other posts saying the same thing before i posted this one. sounds good, and good luck!

That's what I thought too. The reinstallation is finished now, after an hour and a half plus, and I was told that some programs haven't been restarted because they depended on files that have been deleted. I was advised to run zypper -ps.

That produced a file of nearly 30KB, containing a list of what appear to be library files; I was able to save this file, but not to copy it to another machine through NFS, so I can't exhibit it here.

What am I to make of this? Is this normal in the circumstances?

"zypper ps" shows you processes that use files that have been deleted during the upgrade. that's normal; files get deleted and replaced by different versions, being switched to another repo. the programs using them won't crash immediately because these files still exist in some temporary fashion.

you can run "zypper ve" (verify), to make sure that all dependencies are fulfilled. that should show nothing; "zypper ps" showing a lot of libraries being used by running processes is normal at this stage. you'll have to log out of KDE, and back in to see if everything works as it should. (i think there should be nothing in the update requiring a full reboot; wouldn't hurt to do it anyway i guess...)

I have not been able to find hints about how to approach the apparent failure of the reinstallation, and I can add only the following few observations to what I have already reported: 1) After running zypper ps, the report was that there were no unstarted packages. Running zypper ve reported that there are no unresolved dependencies. 2) Booting the system to runlevel 5 doesn't end exactly as I reported earlier. I observed that there is near the end an interval of a few seconds when the mouse cursor is not frozen, but seems to behave normally, then freezes and jumps to the center of the screen and freezes. The progress gauge does not reach the end position and stop, but freezes a little sooner than it did the first time. The Desktop Folder and Panel never come up as they did the first time. 3) FWIW, the startup log reports that the following actions failed: Starting VirtualBox kernel modules Starting Postfix Starting rng-tools If any of this suggests a diagnostic approach to anyone, I'd like to know what.it is, because I have nothing. In the absence of any other suggestion, I think I have to abandon the installation and install 11.3 elsewhere on the HD, then try to fetch data to it from this one. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 30 Dec 2010 04:08:49 +0530, Ken Schneider - openSUSE wrote:

Did you try removing the .kde4 and .kde directories before logging on. Yes you will lose any setup you have but you are going to lose that anyway with a fresh install. Go to runlevel 3 and login as your user and mv .kde4 .kde4.old && mv .kde .kde.old Go back to runlevel 5 and try to login again.

yes, of course! i didn't think of this (just got up), but that's one of the first things to do when KDE seems messed up. resets all your KDE settings to their defaults. specially in your case, where different versions of KDE have been writing settings & config. files, this might very well help. if it does work afterwards, you can still try to rescue contacts, emails, and even settings, one by one, from the previous (renamed) KDE folders and include them in the new ones. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 30 Dec 2010 03:55:27 +0530, Stan Goodman wrote:

On Tuesday 28 December 2010 23:14:17 phanisvara das wrote:

...

On Wed, 29 Dec 2010 02:25:11 +0530, Stan Goodman wrote:

...

On Tuesday 28 December 2010 22:08:58 phanisvara das wrote:

...

On Wed, 29 Dec 2010 01:19:07 +0530, Stan Goodman

wrote:

...

...

...

------------ zypper mr -d ------------

We are past that stage now, and zypper dup has been chugging away for over an hour, doing its thing.

yes, i didn't see the other posts saying the same thing before i posted this one. sounds good, and good luck!

That's what I thought too. The reinstallation is finished now, after an hour and a half plus, and I was told that some programs haven't been restarted because they depended on files that have been deleted. I was advised to run zypper -ps.

That produced a file of nearly 30KB, containing a list of what appear to be library files; I was able to save this file, but not to copy it to another machine through NFS, so I can't exhibit it here.

What am I to make of this? Is this normal in the circumstances?

"zypper ps" shows you processes that use files that have been deleted during the upgrade. that's normal; files get deleted and replaced by different versions, being switched to another repo. the programs using them won't crash immediately because these files still exist in some temporary fashion.

you can run "zypper ve" (verify), to make sure that all dependencies are fulfilled. that should show nothing; "zypper ps" showing a lot of libraries being used by running processes is normal at this stage. you'll have to log out of KDE, and back in to see if everything works as it should. (i think there should be nothing in the update requiring a full reboot; wouldn't hurt to do it anyway i guess...)

I have not been able to find hints about how to approach the apparent failure of the reinstallation, and I can add only the following few observations to what I have already reported:

1) After running zypper ps, the report was that there were no unstarted packages. Running zypper ve reported that there are no unresolved dependencies.

2) Booting the system to runlevel 5 doesn't end exactly as I reported earlier. I observed that there is near the end an interval of a few seconds when the mouse cursor is not frozen, but seems to behave normally, then freezes and jumps to the center of the screen and freezes. The progress gauge does not reach the end position and stop, but freezes a little sooner than it did the first time. The Desktop Folder and Panel never come up as they did the first time.

3) FWIW, the startup log reports that the following actions failed: Starting VirtualBox kernel modules Starting Postfix Starting rng-tools

If any of this suggests a diagnostic approach to anyone, I'd like to know what.it is, because I have nothing. In the absence of any other suggestion, I think I have to abandon the installation and install 11.3 elsewhere on the HD, then try to fetch data to it from this one.

i'm sorry, but i'm running out of ideas; i don't understand what's going on. perhaps somebody else can give you better advice, but at this point i'd probably go for a new install and then, as you wrote, rescue your data from the old one. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, 24 Dec 2010 02:01:06 +0530, Stan Goodman wrote:

I've asked how I can have the system boot to run level 3, which hopefully would enable me to manipulate and use repos, because I know only how to switch levels when the existing level is functional.

it was mentioned in this thread (forgot by whom): when grub gives you the choice which version to boot, add a "3" to the boot options (using the same one you always use). you'll have to press <enter> after typing '3', of course. that boots into init 3. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 12/23/2010 4:31 PM, Stan Goodman wrote:

...

...

it was mentioned in this thread (forgot by whom): Then I overlooked it, for which I apologize.

http://www.cyberciti.biz/tips/linux-changing-run-levels.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 12/24/2010 03:54 AM, Stan Goodman pecked at the keyboard and wrote:

On Thursday 23 December 2010 23:46:17 Michael S. Dunsaavage wrote:

...

On 12/23/2010 4:31 PM, Stan Goodman wrote:

...

...

...

it was mentioned in this thread (forgot by whom):

Then I overlooked it, for which I apologize.

http://www.cyberciti.biz/tips/linux-changing-run-levels.html

No, that is not what I asked about. The URL you have provided is for changing the run level in a system that is already operating, or for setting the run level for the subsequent boot of a system that is now operating. In contrast, my system is currently not operating and not operable; my question was how to assure that it will boot to level 3, although its default is level 5.

But thanks.

Type a 3 at the boot prompt and hit enter. And you can use Ctrl-Alt-F1 (or F2 or F3 or F5) to get to a text screen if at run level 5 and type init 3 for run level 3. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Friday 24 December 2010 16:10:35 Felix Miata wrote:

On 2010/12/24 10:54 (GMT+0200) Stan Goodman composed:

...

my question was how to assure that it will boot to level 3, although its default is level 5.

Put the runlevel number you wish to start in on the Grub kernel line, in this case, a 3. All my menu.lst stanzas include a number, which reminds me which runlevel I'll be starting in, and to specify another first if that isn't what I want on the upcoming boot.

AhA!! A _GRUB_ command line! Nobody has mentioned that until now The implication has been that there is somewhere in the normal boot screens a place to enter the number of the desired run level, and I have been puzzling over that for the better part of the day. Now all is clear. But now the machine doesn't start at all, and I won't be able to address that until Sunday. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 2010/12/24 19:43 (GMT+0200) Mark Goldstein composed:

Stan Goodman wrote:

...

Felix Miata wrote:

...

...

On 2010/12/24 10:54 (GMT+0200) Stan Goodman composed:

...

...

...

my question was how to assure that it will boot to level 3, although its default is level 5.

...

...

Put the runlevel number you wish to start in on the Grub kernel line, in this case, a 3. All my menu.lst stanzas include a number, which reminds me which runlevel I'll be starting in, and to specify another first if that isn't what I want on the upcoming boot.

...

AhA!! A _GRUB_ command line! Nobody has mentioned that until now The implication has been that there is somewhere in the normal boot screens a place to enter the number of the desired run level, and I have been puzzling over that for the better part of the day. Now all is clear.

You normally have a line for "boot options" in the boot screen. These are the parameters you want to pass to the kernel. In particular, you can type the desired run level there.

It has the same effect as adding these options at the end of "kernel" line in grub menu stanza

To be clear, whatever you do on the boot options line on Grub's boot screen amounts to editing the kernel line of the selected stanza in menu.lst, but just for the upcoming boot. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org