https://bugzilla.novell.com/show_bug.cgi?id=169799#c19
--- Comment #19 from Stephen Shaw 2007-08-01 16:20:55 MST ---
Someone mentioned that I might not have explained myself well enough. To me
this seems a critical/blocker bug.
The idea is that once you have yast2 open and select a module (ie. dns server
or dhcp server) that it locks the rpm db. In order for the rpm db to be
released you have to close the module AND close yast2. So for example if you
wanted to update your dns server and add a couple packages right after without
closes yast2 you would not be able to. You would have to close out the dns
server module (which is fine), close yast2, open yast2, and then open software
management.
As a user this would bug me a lot. I imagine that the average user would be
bugged by it as well. As Axel mentioned, this is a usability issue. And a
good reason not to use yast for administrative actions.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.