Re: [opensuse] Upgrading KDE 4.4 > 4.5 -- was: Graduated from "Absent trash icon" to disaster
On Fri, Feb 4, 2011 at 23:56, Stan Goodman wrote:
10 Import any GPG keys when asked.
This is a new thing. It will give me keys, and I only need to d/l them? What is it that needs to be encrypted?
If you've added any additional supported repositories to YaST/zypper in the past several openSUSE releases (eg Community repos), you will have had to import the GPG keys. YaST handles the import process... you only need to click Yes to accept them, or No if you don't trust them. It's pretty safe to trust the keys in this case.
The install should complete without any issues (assuming you're still starting from a clean 11.3 install),. I've tested the steps above this evening on a clean 11.3 install, upgrading the default KDE4.4.4 to KDE 4.6.0 and there were no issues.
Clean now? It was installed on new partitions; there have been automatic updates from the default repos. I've installed a few KDE apps. I guess it's relatively clean.
I'd still call that "clean". An upgrade starts to get messy if you've added lots of extra repos, upgraded several times, added 3rdparty RPMs etc.
I have yet to use activities.
Take a look at these two blog entries: http://hanschen.org/2011/02/04/activities-a-change-in-workflow/ http://yuenhoe.co.cc/blog/2011/01/the-rise-of-plasma-activities-and-what-it-... Activities may not be for everyone (just like multiple desktops are not for everyone) but as the concept matures, they are becoming much more useful. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 05 February 2011 01:08:02 C wrote:
On Fri, Feb 4, 2011 at 23:56, Stan Goodman wrote:
10 Import any GPG keys when asked.
This is a new thing. It will give me keys, and I only need to d/l them? What is it that needs to be encrypted?
If you've added any additional supported repositories to YaST/zypper in the past several openSUSE releases (eg Community repos), you will have had to import the GPG keys. YaST handles the import process... you only need to click Yes to accept them, or No if you don't trust them. It's pretty safe to trust the keys in this case.
I haven't added repos, so there shouldn't be keys. There are no "past releases", because I always install the OS on a clean partition.
The install should complete without any issues (assuming you're still starting from a clean 11.3 install),. I've tested the steps above this evening on a clean 11.3 install, upgrading the default KDE4.4.4 to KDE 4.6.0 and there were no issues.
Clean now? It was installed on new partitions; there have been automatic updates from the default repos. I've installed a few KDE apps. I guess it's relatively clean.
I'd still call that "clean". An upgrade starts to get messy if you've added lots of extra repos, upgraded several times, added 3rdparty RPMs etc.
I have yet to use activities.
I just haven't got around it them (or a lot of other things).
Take a look at these two blog entries: http://hanschen.org/2011/02/04/activities-a-change-in-workflow/ http://yuenhoe.co.cc/blog/2011/01/the-rise-of-plasma-activities-and-wha t-it-can-do-for-you/
Activities may not be for everyone (just like multiple desktops are not for everyone) but as the concept matures, they are becoming much more useful.
I have been using multiple desktops all along (since v10.3), and they have made it much easier to keep several things going at one time (and amazed my Windows friends as well). If I understand correctly, it will take activities to make it possible for me to assign a different wallpaper image to each desktop (as I had with KDE3), and that would be the most likely motive for me to adopt activities, at least initially. -----[Time out for glancing at the two blogs and bookmarking them to read -----later in the day.] But I can see from the glancing that activities have may have become more useful than they were. I'll read these thoroughly. Thanks.
C.
-- 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, 05 Feb 2011 17:01:48 +0530, Stan Goodman <stan.goodman@hashkedim.com> wrote:
If I understand correctly, it will take activities to make it possible for me to assign a different wallpaper image to each desktop (as I had with KDE3), and that would be the most likely motive for me to adopt activities, at least initially.
nope, you can assign different desktop backgrounds and widgets already in KDE 4.4: systemsettings -> workspace behavior -> virtual desktops it's just one checkbox that allows you to have different stuff on each desktop. BUT i found this much more unstable under KDE 4.4 than under 4.5/6. earlier my desktop arrangements often got messed up w/o any obvious reason, so that i resorted to backing up all plasma-related files & directories in order to be able to restore them, not if, but when disaster struck. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 05 February 2011 16:12:34 phanisvara das wrote:
On Sat, 05 Feb 2011 17:01:48 +0530, Stan Goodman <stan.goodman@hashkedim.com> wrote:
If I understand correctly, it will take activities to make it possible for me to assign a different wallpaper image to each desktop (as I had with KDE3), and that would be the most likely motive for me to adopt activities, at least initially.
nope, you can assign different desktop backgrounds and widgets already in KDE 4.4:
systemsettings -> workspace behavior -> virtual desktops
it's just one checkbox that allows you to have different stuff on each desktop. BUT i found this much more unstable under KDE 4.4 than under 4.5/6. earlier my desktop arrangements often got messed up w/o any obvious reason, so that i resorted to backing up all plasma-related files & directories in order to be able to restore them, not if, but when disaster struck.
Glad to here this, and relieved to learn that disasters strike other people too! One has just struck me now. There is no chance that I caused it. Before preparing to upgrade to KDE4.6, I found that the system wanted to install essential patches. I debated whether to accept this or to pass on it and upgrade KDE first. I took what turns out to be the wrong choice, and accepted the patches. When the smoke cleared away an hour or so later, I was asked to reboot, which I did. The boot never finished, but froze while the chameleon screen was still up, with the mouse cursor stuck in the center and the keyboard dead. I reset, and the new reboot ended with a black screen, but with all else frozen as before. I would like, if possible, to avoid reinstalling v11.3 from scratch; if somebody has a better idea, please mention it. Sometimes I would like things to work as advertised. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/02/05 19:31 (GMT+0200) Stan Goodman composed:
Before preparing to upgrade to KDE4.6, I found that the system wanted to install essential patches. I debated whether to accept this or to pass on it and upgrade KDE first. I took what turns out to be the wrong choice, and accepted the patches.
When the smoke cleared away an hour or so later, I was asked to reboot, which I did. The boot never finished, but froze while the chameleon screen was still up, with the mouse cursor stuck in the center and the keyboard dead. I reset, and the new reboot ended with a black screen, but with all else frozen as before. I would like, if possible, to avoid reinstalling v11.3 from scratch; if somebody has a better idea, please mention it.
Type a <space> 3 when the Grub menu comes up, then press <Return>. That should get you into text mode with full networking. Login as root on tty2 and open mc. Login as root on tty3 and do 'zypper up' and see if it finds anything to do. If it does, let it proceed, then either try rebooting normally, or switch to tty2, navigate to /etc/zypp/repos.d/, where you'll want to configure a file for using the 4.6 repo. One way to do that is if you have a 4.5.5 already configured, just edit it using mc's internal editor to change title, name, and applicable URL. First make a copy for backup [highlight old file; shift-F3; end; BS: removes "o" from name of original filename, creating new file with .rep as ending] Once that's done, goto tty2 and do zypper ref. If no errors, do zypper dup. If while all this is going on you need internet access, you can right inside mc via its built in FTP, such as fetching an RPM or getting a repo URL correct in your mind. After zypper dup is done, try rebooting normally. Look at man zypper for the -r command if you want only to upgrade from a particular repo, such as your new 4.6. -- "How much better to get wisdom than gold, to choose understanding rather than silver." Proverbs 16:16 NKJV 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
On Sat, 05 Feb 2011 23:24:46 +0530, Felix Miata <mrmazda@earthlink.net> wrote:
Type a <space> 3 when the Grub menu comes up, then press <Return>. That should get you into text mode with full networking. Login as root on tty2 and open mc. Login as root on tty3 and do 'zypper up' and see if it finds anything to do. If it does, let it proceed, then either try rebooting normally, or switch to tty2, navigate to /etc/zypp/repos.d/, where you'll want to configure a file for using the 4.6 repo. One way to do that is if you have a 4.5.5 already configured, just edit it using mc's internal editor to change title, name, and applicable URL. First make a copy for backup [highlight old file; shift-F3; end; BS: removes "o" from name of original filename, creating new file with .rep as ending] Once that's done, goto tty2 and do zypper ref. If no errors, do zypper dup. If while all this is going on you need internet access, you can right inside mc via its built in FTP, such as fetching an RPM or getting a repo URL correct in your mind. After zypper dup is done, try rebooting normally. Look at man zypper for the -r command if you want only to upgrade from a particular repo, such as your new 4.6.
this should work, but why do it the difficult way if he can use the zypper command to do all that for him? -- "zypper lr" gives a list of repositories, enabled and otherwise; -- "zypper rr <repo no|repo alias|repo URL>" removes a repo that he doesn't want to use anymore; -- "zypper ar -f <repo URL> <repo alias>" adds a new repo, with auto-refresh enabled; -- "zypper ref" refreshes all repos that have auto-refresh enabled; -- "zypper dup -r <repo alias|repo no|repo URL>" does the upgrade from the specified repo, while allowing packages from other repos to be pulled in if necessary; why should he do all that with a text editor / MC? IMO that's much more error prone, unless one knows _exactly_ what has to be done. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/02/05 14:03 (GMT-0500) phanisvara das composed:
why should he do all that with a text editor / MC? IMO that's much more error prone, unless one knows _exactly_ what has to be done.
1-avoids typing long strings by using copy/paste methodology in text-only mode 2-avoids needing to remember repo nicks 3-backup facilitation 4-avoids needing to remember all those zypper syntax's 5-reduces need for awful man page 6-secondarily, demonstrating one powerful tool goes a long way in fixing a broken system -- "How much better to get wisdom than gold, to choose understanding rather than silver." Proverbs 16:16 NKJV 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
On Saturday 05 February 2011 19:54:46 Felix Miata wrote:
On 2011/02/05 19:31 (GMT+0200) Stan Goodman composed:
Before preparing to upgrade to KDE4.6, I found that the system wanted to install essential patches. I debated whether to accept this or to pass on it and upgrade KDE first. I took what turns out to be the wrong choice, and accepted the patches.
When the smoke cleared away an hour or so later, I was asked to reboot, which I did. The boot never finished, but froze while the chameleon screen was still up, with the mouse cursor stuck in the center and the keyboard dead. I reset, and the new reboot ended with a black screen, but with all else frozen as before. I would like, if possible, to avoid reinstalling v11.3 from scratch; if somebody has a better idea, please mention it.
Type a <space> 3 when the Grub menu comes up, then press <Return>. That should get you into text mode with full networking. Login as root on tty2 and open mc. Login as root on tty3 and do 'zypper up' and see if it finds anything to do. If it does, let it proceed, then either try rebooting normally, or switch to tty2, navigate to /etc/zypp/repos.d/, where you'll want to configure a file for using the 4.6 repo. One way to do that is if you have a 4.5.5 already configured, just edit it using mc's internal editor to change title, name, and applicable URL. First make a copy for backup [highlight old file; shift-F3; end; BS: removes "o" from name of original filename, creating new file with .rep as ending] Once that's done, goto tty2 and do zypper ref. If no errors, do zypper dup. If while all this is going on you need internet access, you can right inside mc via its built in FTP, such as fetching an RPM or getting a repo URL correct in your mind. After zypper dup is done, try rebooting normally. Look at man zypper for the -r command if you want only to upgrade from a particular repo, such as your new 4.6.
Felix... After the <space> 3 to get into text mode, the system returned to the chameleon screen, moved the progress gauge a bit, and froze for about five minutes. After several minutes more, I happened to glance at it again, and found it had entered actually entered text mode -- this timing does not look like previous times when I have entered runmode 3. At the bottom of the logging sequence appear the following lines: ----- Starting Firewall Initialization (phase 2 of 2) Master Resource Control: runlevel 3 has been <--sic Failed services in runlevel 3: Skipped services in runlevel 3: Welcome to openSUSE 11.3 "Teal" - Kernel 2.6.34.7-0.7-desktop (tty1). poblano2 login: WARNING: Number of errors: 0, skipped probes:57 ----- Does that last line modify your suggested procedure? I am now logged into tty1; I will search how to switch to another tty, but if you want to give a hint, that would be helpful. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/02/05 21:44 (GMT+0200) Stan Goodman composed:
After the<space> 3 to get into text mode, the system returned to the chameleon screen, moved the progress gauge a bit, and froze for about five
Get 'quiet' off the line where you type the 3 and change 'splash=silent' to 'splash=verbose' and you'll boot without the graphics, instead getting all available boot messages, which will scroll by faster than they can be read. If you want it like that always, make those changes in /boot/grub/menu.lst and /etc/sysconfig/bootloader on the "DEFAULT_APPEND=" line. ...
Starting Firewall Initialization (phase 2 of 2) Master Resource Control: runlevel 3 has been<--sic Failed services in runlevel 3: Skipped services in runlevel 3:
Welcome to openSUSE 11.3 "Teal" - Kernel 2.6.34.7-0.7-desktop (tty1). poblano2 login: WARNING: Number of errors: 0, skipped probes:57 -----
Does that last line modify your suggested procedure?
no
I am now logged into tty1; I will search how to switch to another tty, but if you want to give a hint, that would be helpful.
Remember, Linux by default is multi-user. This sequence is switching from one "user" to another, even though you're using the same keyboard and display. Ctrl-Alt-F4 Ctrl-Alt-F3 Ctrl-Alt-F2 Ctrl-Alt-F5 Ctrl-Alt-F6 Alt-F7 gets you back to X if X is running Ctrl- is only _necessary_ if you want to get to a tty from X, not to switch from one tty to another. By logging in on multiple ttys at once you have the same effect as multiple windows in X, such as a man page in one, a cmdline running zypper in another, a text editor in another, tailing /var/log/messages in another, top in another, the swiss army knife (MC) in another, etc. -- "How much better to get wisdom than gold, to choose understanding rather than silver." Proverbs 16:16 NKJV 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
On Saturday 05 February 2011 22:25:07 Felix Miata wrote:
On 2011/02/05 21:44 (GMT+0200) Stan Goodman composed:
After the<space> 3 to get into text mode, the system returned to the chameleon screen, moved the progress gauge a bit, and froze for about five
Get 'quiet' off the line where you type the 3 and change 'splash=silent' to 'splash=verbose' and you'll boot without the graphics, instead getting all available boot messages, which will scroll by faster than they can be read.
If you want it like that always, make those changes in /boot/grub/menu.lst and /etc/sysconfig/bootloader on the "DEFAULT_APPEND=" line.
I have made the changes in the two files (replaced 'silent' with 'verbose' and deleted 'quiet'), and rebooted to runlevel 3. At the bottom of display is exactly the same report as before, including 0 errors, but now only 1 skipped probe. But further up there is a report of: ----- Error while executing: Command 'ip route replace to 192.168.1.1/24 via 192.168.1.1 dev eth0' returned: RTNETLINKS answers: Invalid argument Configuration line: 192.168.1.1 192.168.1.1 255.255.255.0 eth0 eth0 ----- which looks like it fixed an error. I'm not sure what the error was, because I was able to access websites through this installation.
Starting Firewall Initialization (phase 2 of 2) Master Resource Control: runlevel 3 has been<--sic Failed services in runlevel 3: Skipped services in runlevel 3:
Welcome to openSUSE 11.3 "Teal" - Kernel 2.6.34.7-0.7-desktop (tty1). poblano2 login: WARNING: Number of errors: 0, skipped probes:57 -----
Does that last line modify your suggested procedure?
no
I am now logged into tty1; I will search how to switch to another tty, but if you want to give a hint, that would be helpful.
Now I need to turn in, because it is late enough that mistakes are virtually unavoidable. I will take up the suggested procedure tomorrow, after I do my weekly grocery run.
Remember, Linux by default is multi-user. This sequence is switching from one "user" to another, even though you're using the same keyboard and display.
Ctrl-Alt-F4 Ctrl-Alt-F3 Ctrl-Alt-F2 Ctrl-Alt-F5 Ctrl-Alt-F6
Ach! I knew that, and it slipped my mind.
Alt-F7 gets you back to X if X is running
Ctrl- is only _necessary_ if you want to get to a tty from X, not to switch from one tty to another.
By logging in on multiple ttys at once you have the same effect as multiple windows in X, such as a man page in one, a cmdline running zypper in another, a text editor in another, tailing /var/log/messages in another, top in another, the swiss army knife (MC) in another, etc.
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 06 February 2011 01:40:20 Stan Goodman wrote:
On Saturday 05 February 2011 22:25:07 Felix Miata wrote:
On 2011/02/05 21:44 (GMT+0200) Stan Goodman composed:
After the<space> 3 to get into text mode, the system returned to the chameleon screen, moved the progress gauge a bit, and froze for about five
Get 'quiet' off the line where you type the 3 and change 'splash=silent' to 'splash=verbose' and you'll boot without the graphics, instead getting all available boot messages, which will scroll by faster than they can be read.
If you want it like that always, make those changes in /boot/grub/menu.lst and /etc/sysconfig/bootloader on the "DEFAULT_APPEND=" line.
I have made the changes in the two files (replaced 'silent' with 'verbose' and deleted 'quiet'), and rebooted to runlevel 3. At the bottom of display is exactly the same report as before, including 0 errors, but now only 1 skipped probe.
But further up there is a report of:
----- Error while executing: Command 'ip route replace to 192.168.1.1/24 via 192.168.1.1 dev eth0' returned: RTNETLINKS answers: Invalid argument Configuration line: 192.168.1.1 192.168.1.1 255.255.255.0 eth0 eth0 ----- which looks like it fixed an error. I'm not sure what the error was, because I was able to access websites through this installation.
Starting Firewall Initialization (phase 2 of 2) Master Resource Control: runlevel 3 has been<--sic Failed services in runlevel 3: Skipped services in runlevel 3:
Welcome to openSUSE 11.3 "Teal" - Kernel 2.6.34.7-0.7-desktop (tty1). poblano2 login: WARNING: Number of errors: 0, skipped probes:57 -----
Now I have booted the system to runlevel 3 again, and I observe several facts that eluded me when I was drowsy last night, or that I failed to interpret properly. I think I see now what has happened and why. When I booted last night, I saw that, even in runlevel 3, the boot process froze at a point; the log stopped scrolling. While I was writing about that on the laptop, I happened to glance at the "stalled" desktop screen, and noticed that it had started again and run to completion, but I didn't inspect adequately what was on the screen. Having repeated this exercise now, I see that the last line before the freeze is: Starting NFS clent services:sm-notify ldmapdStarting kernel based NFS server: lpmapd mountd statd nfsd sm-notify which seems clearly to show that something in NFS has stuck in its throat. So I put the laptop into Suspect, which caused the desktop's boot process to restart at once and run to completion. That reminded me that, a while before I accepted the hour-long automatic upgrade, I had installed an NFS client in the desktop to communicate with the laptop, and had partially installed also an NFS server (I didn't finish that chore because I didn't have the time just then, and it has to be done on the CLI because The Powers That Be, in their great wisdom, have removed that facility from YaST). I haven't continued with the suggestions of Felix, because I am pretty sure that all will be welll if I kill the NFS client (and maybe the sever) in the desktop machine. How can I do that most easily, without losing whatever has already been done there? Aside from the above, I note some other remarks at the end of the log: 1) "Mount CIFS File Systems unused" 2) "Starting RNG daemon No hardware support availablee skipped" -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Stan Goodman <stan.goodman@hashkedim.com> [02-06-11 10:25]: ....
That reminded me that, a while before I accepted the hour-long automatic upgrade, I had installed an NFS client in the desktop to communicate with the laptop, and had partially installed also an NFS server (I didn't finish that chore because I didn't have the time just then, and it has to be done on the CLI because The Powers That Be, in their great wisdom, have removed that facility from YaST).
The Powers That Be, in their great wistom, have included yast2-nfs-server/common/client in the distro, but it is not installed in a basic system and not suggested. Those needing such devices are expected to install them themselves by their chosen method. A *simple* search is all that is needed to locate the software. http://software.opensuse.org/search http://download.opensuse.org/distribution/11.3/repo/oss/suse/noarch/yast2-nf... http://download.opensuse.org/distribution/11.3/repo/oss/suse/noarch/yast2-nf... http://download.opensuse.org/distribution/11.3/repo/oss/suse/noarch/yast2-nf... -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Feb 6, 2011 at 17:00, Patrick Shanahan wrote:
The Powers That Be, in their great wistom, have included yast2-nfs-server/common/client in the distro, but it is not installed in a basic system and not suggested. Those needing such devices are expected to install them themselves by their chosen method. A *simple* search is all that is needed to locate the software.
http://software.opensuse.org/search
http://download.opensuse.org/distribution/11.3/repo/oss/suse/noarch/yast2-nf... http://download.opensuse.org/distribution/11.3/repo/oss/suse/noarch/yast2-nf... http://download.opensuse.org/distribution/11.3/repo/oss/suse/noarch/yast2-nf...
There are actually a few useful YaST extras that can be installed from the repositories - extras that are not included in a default install. Worth doing a search on "yast" in our software manager just to see what's available for install. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 06 February 2011 18:00:15 Patrick Shanahan wrote:
* Stan Goodman <stan.goodman@hashkedim.com> [02-06-11 10:25]: ....
That reminded me that, a while before I accepted the hour-long automatic upgrade, I had installed an NFS client in the desktop to communicate with the laptop, and had partially installed also an NFS server (I didn't finish that chore because I didn't have the time just then, and it has to be done on the CLI because The Powers That Be, in their great wisdom, have removed that facility from YaST).
The Powers That Be, in their great wistom, have included yast2-nfs-server/common/client in the distro, but it is not installed in a basic system and not suggested. Those needing such devices are expected to install them themselves by their chosen method. A *simple* search is all that is needed to locate the software.
Thank you, Patrick. I already have pages on how to do this. As you say, the search for the information was not difficult.
http://software.opensuse.org/search
http://download.opensuse.org/distribution/11.3/repo/oss/suse/noarch/yas t2-nfs-client-2.19.3-1.4.noarch.rpm http://download.opensuse.org/distribution/11.3/repo/oss/suse/noarch/ya st2-nfs-common-2.18.1-5.2.noarch.rpm http://download.opensuse.org/distribution/11.3/repo/oss/suse/noarch/ya st2-nfs-server-2.18.1-5.2.noarch.rpm
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Stan Goodman <stan.goodman@hashkedim.com> [02-06-11 11:29]:
On Sunday 06 February 2011 18:00:15 Patrick Shanahan wrote:
* Stan Goodman <stan.goodman@hashkedim.com> [02-06-11 10:25]: ....
That reminded me that, a while before I accepted the hour-long automatic upgrade, I had installed an NFS client in the desktop to communicate with the laptop, and had partially installed also an NFS server (I didn't finish that chore because I didn't have the time just then, and it has to be done on the CLI because The Powers That Be, in their great wisdom, have removed that facility from YaST).
The Powers That Be, in their great wistom, have included yast2-nfs-server/common/client in the distro, but it is not installed in a basic system and not suggested. Those needing such devices are expected to install them themselves by their chosen method. A *simple* search is all that is needed to locate the software.
Thank you, Patrick. I already have pages on how to do this. As you say, the search for the information was not difficult.
then what point was the comment, mud-slinging, or just verbiage? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 06 February 2011 18:39:01 Patrick Shanahan wrote:
* Stan Goodman <stan.goodman@hashkedim.com> [02-06-11 11:29]:
On Sunday 06 February 2011 18:00:15 Patrick Shanahan wrote:
* Stan Goodman <stan.goodman@hashkedim.com> [02-06-11 10:25]: ....
That reminded me that, a while before I accepted the hour-long automatic upgrade, I had installed an NFS client in the desktop to communicate with the laptop, and had partially installed also an NFS server (I didn't finish that chore because I didn't have the time just then, and it has to be done on the CLI because The Powers That Be, in their great wisdom, have removed that facility from YaST).
The Powers That Be, in their great wistom, have included yast2-nfs-server/common/client in the distro, but it is not installed in a basic system and not suggested. Those needing such devices are expected to install them themselves by their chosen method. A *simple* search is all that is needed to locate the software.
Thank you, Patrick. I already have pages on how to do this. As you say, the search for the information was not difficult.
In fact, before I had the disaster with II.3, I had a server on each of the two computers that make up my LAN.
then what point was the comment, mud-slinging, or just verbiage?
The sentence, which is anyway parenthetical, is self explanatory, if one reads it. It was about why the client is completely installed, but the server only partly so. There is nothing in it asking for assistance in installing an NFS server. But I can reveal to you, if you like, what was in my mind when I wrote that sentence. I was, and am, still confused about the asymmetry of including the client, but not the server, in YaST by default; in previous releases, both were in by default. If there is a client in a LAN, there must also be a server, and the logic of the decision of why suddenly to cut one out is unclear. It's possible that there are networks in which there is only one server, with a multitude of clients; that may be the case in large companies, and even of departments of such companies. But if openSuSE (as distinct from the $$$ product) is expected to be used also by smaller organizations and individuals, there really is no obvious reason for putting one in YaST and the other someplace on the Web. That's why v11.2 has both by default. I hope that is sufficient clarification. But I don't want to talk about it anymore. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 05 February 2011 19:54:46 Felix Miata wrote:
On 2011/02/05 19:31 (GMT+0200) Stan Goodman composed:
Before preparing to upgrade to KDE4.6, I found that the system wanted to install essential patches. I debated whether to accept this or to pass on it and upgrade KDE first. I took what turns out to be the wrong choice, and accepted the patches.
When the smoke cleared away an hour or so later, I was asked to reboot, which I did. The boot never finished, but froze while the chameleon screen was still up, with the mouse cursor stuck in the center and the keyboard dead. I reset, and the new reboot ended with a black screen, but with all else frozen as before. I would like, if possible, to avoid reinstalling v11.3 from scratch; if somebody has a better idea, please mention it.
Since opensuse v10.0, I have never had real trouble from KDE installations, and I do not see any light at the end of the tunnel with this one.
Type a <space> 3 when the Grub menu comes up, then press <Return>. That should get you into text mode with full networking. Login as root on tty2 and open mc. Login as root on tty3 and do 'zypper up' and see if it finds anything to do. If it does, let it proceed, then either try rebooting normally,
What zypper found to do was to d/l the java 1.6.0 runtime, the correspoinding browser plugin, and pullin-msttf-fonts, and I let it do so. It's hard to believe that these have anything to do with the inability of KDE to run. So I rebooted on principle and took the chance of updating the system to KDE v4.6 as described by "C" in this thread. The method is exactly as described below, and is uncomplicated. I don't think the system is capable of downloading, because of some of the lines I have been able to see in the last part of the boot log (I have reported them in previous messages). Some of those lines seem irrelevant to the current problem. For example, there is a remark that there is no hardware support for RNG, aa random number generator. I don't know if there should be hardware surpport or not, but there is also a red warning that there are no rng-tools, which makes it seem abnormal. But it isn't clear that lack of a random number generator would shut down KDE. The following seems more disturbing, and also more relevant to the possibility of downloading upgrades: ***** Error while executing: Command 'ip route replace to 192.168.1.1/24 via 192.168.1.1 dev eth0' returned: RTNETLINK answers:Invalid argument Configuration line: 192.168.1.1 192.168.1.1 255.255.255.0 eth0 ***** (192.168.1.1 is the gateway, the router.) So this seems to be referring to the routing configuration, but I don't know what it wants, or where to fix it with what. Can someone help clarify this?
or switch to tty2, navigate to /etc/zypp/repos.d/, where you'll want to configure a file for using the 4.6 repo. One way to do that is if you have a 4.5.5 already configured, just edit it using mc's internal editor to change title, name, and applicable URL. First make a copy for backup [highlight old file; shift-F3; end; BS: removes "o" from name of original filename, creating new file with .rep as ending] Once that's done, goto tty2 and do zypper ref. If no errors, do zypper dup. If while all this is going on you need internet access, you can right inside mc via its built in FTP, such as fetching an RPM or getting a repo URL correct in your mind. After zypper dup is done, try rebooting normally. Look at man zypper for the -r command if you want only to upgrade from a particular repo, such as your new 4.6.
I am very open to suggestions about getting KDE up and running, after which I think the KDE 4.6 upgrade would happen automatically. If someone sees the missing light at the end of the trouble, I would be very grateful. If not, I'll scratch this installation, and do it all over again in the hope that whatever happened won't happen again. -- 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, 05 Feb 2011 23:01:00 +0530, Stan Goodman <stan.goodman@hashkedim.com> wrote:
On Saturday 05 February 2011 16:12:34 phanisvara das wrote:
On Sat, 05 Feb 2011 17:01:48 +0530, Stan Goodman <stan.goodman@hashkedim.com> wrote:
If I understand correctly, it will take activities to make it possible for me to assign a different wallpaper image to each desktop (as I had with KDE3), and that would be the most likely motive for me to adopt activities, at least initially.
nope, you can assign different desktop backgrounds and widgets already in KDE 4.4:
systemsettings -> workspace behavior -> virtual desktops
it's just one checkbox that allows you to have different stuff on each desktop. BUT i found this much more unstable under KDE 4.4 than under 4.5/6. earlier my desktop arrangements often got messed up w/o any obvious reason, so that i resorted to backing up all plasma-related files & directories in order to be able to restore them, not if, but when disaster struck.
Glad to here this, and relieved to learn that disasters strike other people too! One has just struck me now. There is no chance that I caused it.
Before preparing to upgrade to KDE4.6, I found that the system wanted to install essential patches. I debated whether to accept this or to pass on it and upgrade KDE first. I took what turns out to be the wrong choice, and accepted the patches.
When the smoke cleared away an hour or so later, I was asked to reboot, which I did. The boot never finished, but froze while the chameleon screen was still up, with the mouse cursor stuck in the center and the keyboard dead. I reset, and the new reboot ended with a black screen, but with all else frozen as before. I would like, if possible, to avoid reinstalling v11.3 from scratch; if somebody has a better idea, please mention it.
Sometimes I would like things to work as advertised.
argh!@#$@#$@ -- again! to me this sounds as if either you got some repos mixed up again, or you're hit by the evil video driver bug that causes problems with some newer drivers, mostly on 32bit machines. can you please remind me: what video driver are you using? is your machine 32bit or 64bit? and then, again, the output of "zypper lr -d" ... (sounds familiar, doesn't it?) -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 05 February 2011 21:07:29 phanisvara das wrote:
On Sat, 05 Feb 2011 23:01:00 +0530, Stan Goodman <stan.goodman@hashkedim.com> wrote:
On Saturday 05 February 2011 16:12:34 phanisvara das wrote:
On Sat, 05 Feb 2011 17:01:48 +0530, Stan Goodman
<stan.goodman@hashkedim.com> wrote:
If I understand correctly, it will take activities to make it possible for me to assign a different wallpaper image to each desktop (as I had with KDE3), and that would be the most likely motive for me to adopt activities, at least initially.
nope, you can assign different desktop backgrounds and widgets already in KDE 4.4:
systemsettings -> workspace behavior -> virtual desktops
it's just one checkbox that allows you to have different stuff on each desktop. BUT i found this much more unstable under KDE 4.4 than under 4.5/6. earlier my desktop arrangements often got messed up w/o any obvious reason, so that i resorted to backing up all plasma-related files & directories in order to be able to restore them, not if, but when disaster struck.
Glad to here this, and relieved to learn that disasters strike other people too! One has just struck me now. There is no chance that I caused it.
Before preparing to upgrade to KDE4.6, I found that the system wanted to install essential patches. I debated whether to accept this or to pass on it and upgrade KDE first. I took what turns out to be the wrong choice, and accepted the patches.
When the smoke cleared away an hour or so later, I was asked to reboot, which I did. The boot never finished, but froze while the chameleon screen was still up, with the mouse cursor stuck in the center and the keyboard dead. I reset, and the new reboot ended with a black screen, but with all else frozen as before. I would like, if possible, to avoid reinstalling v11.3 from scratch; if somebody has a better idea, please mention it.
Sometimes I would like things to work as advertised.
argh!@#$@#$@ -- again! to me this sounds as if either you got some repos mixed up again, or you're hit by the evil video driver bug that causes problems with some newer drivers, mostly on 32bit machines.
NO! I had not done anything whatever toward the upgrade. As I said, I had not even prepared to upgrade, when this offer of essential updates came in. In particular, I had not even brought up the web page that contains the URLs of the 4.6 repos, so I certainly had not entered any new repos. This is the large update that always comes soon after one installs a new release of oS, and is bound to be a BIG one when the release is not new (IOW, the DVD is already old, so there are lots of things to be connected this late in the game, so it took about an hour. I contributed nothing to this particular screwup.
can you please remind me: what video driver are you using? is your machine 32bit or 64bit?
The machine and the installation are 64bit. The display chip is Intel 82915G.
and then, again, the output of "zypper lr -d" ... (sounds familiar, doesn't it?)
The (hand copied) repos are: 1) Updates http://download.opensuse.org/update/113/ 2) cd is not present 3) repo-debug http://download.opensuse.org/debug/distribution/repo/oss/ 4) repo-non-oss http://download.opensuse.org/debug/distribution/repo/non- oss/ 5) repo-oss http://download.opensuse.org//debug/distribution/oss/ 6) repo-source http://download.opensuse.org/update/source/distribution/11.3/repo/oss/ 3 and 6 are not enabled. 2 is not refreshed. All are at priority 99. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
C -
Felix Miata -
Patrick Shanahan -
phanisvara das -
Stan Goodman