On 05/11/2010 11:43 AM, John E. Perry wrote:
I just tried my second "zypper up" after switching from "zypper dup" due to the responses to my "Changing zypper command" message of last week.
Oops.
zypper: error while loading shared libraries: libzypp.so.619: cannot open shared object file: No such file or directory
Now, yast won't start (dbus error), zypper won't start.
Thanks, all. Carlos:
Wow. What did you do? :-o
As I said above, I just stopped using "zypper dup" and started using "zypper up". On the second "up", I got that error. The first one appeared to go just fine, so I was pretty happy -- until this :-). ---------------------------------------- Jon:
Something like 'less /root/.bash_history' (as root) might help retrace your steps?
Since I only go to the command line for special reasons (like zypper), I didn't expect to find anything there (the last few lines of 500 :-): zypper dup ifconfig wlan0 ethtool wlan0 ip addr wlan0 ip addr help ip addr show dev wlan0 exit zypper dup zypper up exit zypper up The first zypper dup was from a couple of weeks ago, just before I was experimenting with networking commands after a message on this list made me curious. I don't see anything here that could show a problem? I was reading over the rest of your message, and trying to work up the courage to go through this scary process, when ------------------------------------------------------ Tony's message came up:
A workaround, that worked for this time anyhow, is I created a symbolic link libzypper.so.619 pointing to the current libzypp.so.631.0.4 library,
and it worked fine for me! Apparently I'm not the only one who had this problem? Maybe switching from "dup" to "up" did something similar to what your fellow instructor did? I created the link, ran zypper up (30 packages to upgrade, 1 new, 2 to change arch.), got a couple of errors, ran it again, go no errors. The kupdater icon was still yellow, so I clicked "check now" and it turned red (java security update), and it did its thing and turned green. I started up yast, and it came up, refreshed all the repositories, and waited for a command. I shut it down, since I only use it for installing new packages and system configuration maintenance. So for now, it looks pretty good. Thanks much, all -- particularly Tony, who gave me a successful workaround that was much less scary than Jon's. I suppose sometime soon I'll work up the courage to delete the link and see if my zypper is up to date... jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org