Bug 231256

I am withdrawing the word "RANDOMLY" because I have just noticed that the ZMD is failed to stop when it is sleeping. If it is already awaken or if I make it awake manually before shutting down the system, then there is no red "failed" message at the shutdown screen so no residual problem after next boot.

I checked all the log files of the system, especially zmd-backend.log and zmd-messages.log but there is no message related to "failed" message at shutdown screen. 

On the other hand, the Bug #231253 has the same origin. I mean the results seem different but the source is same. 

Created attachment 111762 [details]
zmd log files

I tried to reproduce the bug and this time, fortunately, had some error messages in the zmd log files. 

As you will note in the log files,

07 Jan 2007 17:05:52 ZMD going to sleep

then,
starting from 07 Jan 2007 17:11:51 ZMD gives some errors outputs because 17:11:51 is time I click "Turn Off Computer" from the KDE.

later, 
07 Jan 2007 22:59:22, I reboot the computer, but some of the repositories are lost forever.

I need to add one point. After the loss of repositories, I add them again. However  it takes too long restarting/refreshing the zmd ( about 7 minutes for my configured repositories ). So I delete the zmd.db file in /var/lib/zmd and then restarting/refresing time reduces dramatically ( about 2 minutes )

I mean after repo's lost, adding them again does not solve the problem completely, but the zmd.db must be cleared.

I can confirm this bug; I had wanted to report it myself today but just found this report.

It certainly is dangerous because also the regular update-repository is lost without any notification. So users live on in a false feeling of security while they actually never receive a security-update.

Thus I take the liberty of changing the severity to 'Critical'. ^_-

P.S.: This also happens on i386-architecture.

I can confirm this bug. I tried 32bit and 64bit architectures. 

Just wanted to report this same bug because I losted sources in zen-updater. I had to delete them and add again in YaST.

How the hell can you leave so horrible a bug left? It is very dangerous for users, because they do not have Update repository in ZMD and they do not get security updates!

Just to add I have this bug also, and have to do 

rug service-add --type=ZYPP url name

To re-add, and this has several times kept me from getting security updates that I reply on. 

I at time find it easier to go into yast, and just checking the update repository for new updates. 

Hopefully this is fixed, and released for 10.2 and not just closed and marked fixed in 10.3

(ZLM) Lets try this on SLE10 SP1. 

Looking at the logs in comment #2 ....
------------------------------------
07 Jan 2007 17:12:23 WARN  NetworkStatus        Network has been disconnected
process 2956: Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application.
  D-Bus not built with -rdynamic so unable to print a backtrace
--------------------------------------
This was an issue prior to SLE10 SP1. ZMD was not handling the dbus restarts properly. Whenever NetworkManager is started, stopped or restarted dbus service also starts, stops or restarts respectively. Dbus restarts were not handled properly in ZMD. Now it has been handled in a better way in zmd of SP1.

Anyway Zenworks is no more part of OpenSuSE.....
Assuming this has been fixed for SLE10 SP1, marking this as resolved. Please re-open it if you can re-produce it on SLE10 SP1

oops... forgot to change the status

*** Bug 250583 has been marked as a duplicate of this bug. ***