SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Rebooting 3 times cured the problem (temporarily, at least). Restarting X (with a ctrl-alt-backspace) doesn't seem to have an effect.
This has happened a couple of times now, and an arbitrary number of reboots removes the error.
As I said before, I'm new to openSUSE and am relativley ignorant of what's going on. Could any more experienced users shed some light on what may be causing this error and what I can do to fix it (other than rebooting)?
The FAQ's at opensuse-community.org have the recommendation to remove Zen Management in nearly all their how to's. This substitutes the OpenSuSE Updater applet for the Zen Updater and lets you just use YaST Software Management to get your updates and install new software, and Online Update for your Novell system patches.
I've taken to unchecking the Zen Management pattern when installing OpenSuSE as that thing, even with its latest bug fixes, is incredibly slow and doesn't allow as much control over non-automatic resolving of dependencies. YaST will allow you to adjust things until all is resolved whereas the Zen installer would just error on it and fail to carry out the installs if it couldn't resolve stuff automatically.
So head on over there and read some of their guides. You'll see what to do to get rid of Zen and to install some nice multimedia stuff.
To update all your software, besides the Novell updates that OpenSuSE Updater checks for, in YaST Software Management change the dropdown to packages, scroll down to zzz_all, then on the right pane right click one of the onces checked and choose All in this list - Update all with newer versions available. That'll get you what Zen Updater used to get you, with the exception of the Novell Patches that you access through Online Update instead of Software Management.
Then you scroll through the list to make sure you want the updates that have that update icon. Whatever you don't want, you just click the icon until it changes to the blue "keep" checkmark. Then you click the dependency check and if all's okay click Accept and your software will be downloaded and updated.
Once you remove Zen, this problem you're having likely won't occur anymore.
I have the same error with Yast on occassion and haven't figured out what triggers it. I'll look in the Zen thing but in the meantime if I reboot it seems to clear itself. It's annoying but hasn't slowed me down much. I still think Suse 10.2 is a great distro.
Good luck, (and if you find what's causing remember to update this thread with your findings)
If you are using opensuseupdater (the KDE updater instead of zen-updater), when it refreshes it accesses the RPM database, so you will be unable to use software management. This happens more often when I boot the PC, for example.
Hi. I'm having the same problem. I'm by no means at all new to Linux, however, I am fairly new to SuSE. I've been running SuSE since I purchased the 10.0 retail, right when it came out (well, I believe I may have done some kind of trail first-or read something. Either way I knew I fell in love with it quickly).
This is one of the two things I hate about SuSE... It's reliance on rpm's. RPM's make upgrading extremely painful in comparison to .debs. RPM's also use CPIO instead of tar. And then, naturally, problems like this!
Anyways, my guess is that somewhere theres a temp file saying that the rpm database is in use, when it's not. Anybody have any suggestions? I can't install or uninstall anything at the moment..
On 10.1 you can disable ZMD and simply either use Smart or the openSUSE Software Management module (which doesn't use ZMD). On 10.2, you can completely remove ZMD and use the openSUSE Software Management pattern. For more information on both of these, see Package Sources.
So what is the problem with ZMD? Well, ZMD was originally Novell's enterprise software management, which was then pushed onto openSUSE. It caused many problems there, including running away with your CPU, failing to install packages, and taking an increasingly long time to execute basic instructions. As a consequence, we do not recommend that you use it on openSUSE.
"A ZYpp transaction is already in progress"
If you get this error at any time, make sure that all programs that might be using the package management system have been closed down. This includes Zypper, Smart, and most YaST processes. If you are sure that none of these are running, then one of them might be misbehaving. To kill the offending process, execute:
su -c "kill -9 $(lsof -t /usr/lib/libzypp*)"
According to this second paragraph, that is our problem. The code they, however, say to execute did not work for me. I used ksysguard as root and manually killed the processes zmd, zypper, zen, or anything related. All good now! Now, off to remove ZEN....