Bug 230673

I have already experienced ZMD very long time with Suse Linux 10 and 10.1, however I see that zmd has big problems with opensuse 10.2. I am not sure to list them all here or open bug reports for each of them. Anyway as a starting point I will list them here from minor to most critical ones.

1) After a successful update with zen-updater, the update notification sign in the KDE panel still notifies, although there is no update. Then I need to restart the zmd to clear this dummy notification.

2) When one/some of the repositories are unreachable, there is no notification on the KDE panel.

3) When I add a repository using zen it is NOT automatically added into Yast's package management as installation source. I need to add it again separately using Yast itself.

4) The problem which is the one as already explained in my previous report.

5) When shutting down the system, RANDOMLY zmd can not be shutdown by the system. I see the red failed message on the shutdown screen. Then after next-boot zen-updater says that ZMD is not working, although it is working. I try stoping or restrating the zmd, but it fails. I need to reboot to make the zmd-related things work again.

6) Similarly as problem 5, when RANDOMLY zmd fails to be stopped during shutdown, then after next-boot, some of the repositories are lost in the zen-updater configuration. Restaring the zmd, zen-updater and rebooting does not work, I manually need to add the lost repositories again.

7) Similarly as problem 5 & 6, after suspend/resume operation, zen-updater says that either ZMD is not working ( so I reboot the machine ) or some of the repositories are lost ( so I add them again )

8) After a normal boot or when refreshing, zmd tries to find the services and refreshes the files, that's ok. But, during these operation zmd eats all the CPU power of my machine and almost does not let another application work. So, trying  to do some work during the zmd restarting/refreshing is fooling. My 1.8 GHz Turion 64 with 1 GByte RAM and 128 MByte ATI collapses.


When I compare these 8 problems of ZMD with the ZMD in SL10.1, only problem 2 is common !?

I attach the necessary log files.

Created attachment 111192 [details]
zmd log files

Please, split up the bug report, use 'Copy to New' button.

Thanks!

ok think this belongs here 

i cant install a rpm file thats held on local disk 

yast says database is locked and in use by another program 
updater says canot find the rpm reposatory for the rpm that it has localy

never had this problem prior to zmd , this is a real pain , if it fails then theres no way to install a rpm fix , but zmd will update online now at least 

but after trying to install a rpm localy via yast it locks up the whole update system , i have to manualy unlock the database each time and it still locks back up the next time i try 

the only way left to install anything that is not distributed as a suse official rpm is to search all the rpm reposotories for the file you want and if its not there your stuffed , thats how it is at the moment 
well a bit better than 10.1 where i still canot get it to update or install anything thats not on the origianl dvd , other than downloading the source ,and compileing it on the machine 

back a few years ago there used to be the term rpm hell but that was not as bad as the current situation , i have 3 machines here  2 running suse 10.2 and one still on 10.1  online update works fine on one , and needs a restart after each on the other or it tries telling me that all updates have not been installed after updating one file 

it seems that having 3 diferent programs doing package managment will never work together as there will always be some conflict , one of them has to go 
users canot be expected to have to spend hours trying to install software that would just install if it was not for the borked packagemanagment 

i do think one solution that would help if there is any chance of it is the following 

on the install , add an option that will let you chouse what packagmanagment system you want   ie   yast only ,  or full zmd ,yast and rug  stateing that   the full zmd,yast and rug  is still alpha/beta software and may give problems 
cause its definatly not final if it is it reflects badly on the linux developers that produce good stable software that works without problems 

 

Heyyy, ZMD needs urgent attention !!! I split up this bug into 8; not even a single resolution yet. I keep it work on my machine for testing and seeing the resolved issues of my bugs reported and expect an opportunity for setting some bugs' resolution to FIXED. I hardly bear to ZMD-family applications and started to thinking shifting to Yast Fronted or Smart... I wish a "fatality" package management application from opensuse because this is, most probably, the unique main concern within the distro.

Please, be patient. We are focusing on improving the lower levels of the software management first.

Comment # 6

Since there are 8 separate bug for this one, marking this one as resolved.
Because now we are looking at those 8 bugs individually and some of them have been fixed as part of SLE10 SP1 release(JFYI Zenworks is no more part of OpenSUSE), but when I go to mark them as resolved bugzilla does not allow me to do so because of the dependency tree.