Software management is locked

hi i m trying to install software, but when i open “install software”, the following message displayed.

Accessing Package Management Failed
*System management is locked by the application with pid 6104(/usr/sbin/packagekitd).
Close this application before trying again.

Would you like to abort or try again?

Abort Retry*

and one more thing
how to open “*.ymp” file, earlier when i downloaded this type of file, it automatically get opened with install software, but its not happening now.

SOS!!!

Hi
That happens at times if the updater applet is running a check. You can
either disable it (should be via a right-click) temporarily. Or disable
completely and ensure you do regular manual checks for updates.


Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.27.39-0.3-default
up 4 days 9:41, 3 users, load average: 0.03, 0.08, 0.02
GPU GeForce 8600 GTS Silent - CUDA Driver Version: 190.18

As far as the package manager, it is probably the update applet locking the process. Kill it and try again. Not sure why .ymp settings would change. Right click on the .ymp file and select properties. Then click the wrench icon and make sure “YaST Meta Package Handler” is at the top of the list. The software installer doesn’t give a lot of error info, so the update applet might also be the culprit here. I killed the update applet from starting at boot. Before, I had to go to the system, monitor and manually hunt down the processes and kill them to use the package manager. There needs to be a bug reported on this to have the updater killed when package management is called.

67GTA wrote:
> There needs to be a bug reported on this to have the updater
> killed when package management is called.

killing the updater in the midst of an update is a sure way to have
problems…up to an including a completely unstable, and unable to
boot system…


palladium

killing the updater in the midst of an update is a sure way to have
problems…up to an including a completely unstable, and unable to
boot system…

I agree. The point I was alluding to was the fact that if the updater is auto started at boot, you can almost never open the package manager because packagekitd is locking the process 99.9% of the time. Obviously, it should not be killed if an update is in progress.

Thanks all
it helps a lot

well my experience is that running the updater from boot will have it
check once at boot up, and then not again for some hours…that way
it is not constantly locked…i do not know the default setup for the
updater, but i don’t believe it is running often enough to lock up the
package manager constantly maybe a couple of times a day, by default…

ymmv


palladium