http://bugzilla.suse.com/show_bug.cgi?id=876184 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers@suse.de |lslezak@suse.com Flags|needinfo?(contracts@lobikfi | |lip.eu) | --- Comment #6 from Lukas Ocilka --- Ladislav, packager reports an error if access to zypp is locked: --- cut --- Accessing the Software Management Failed System management is locked by the application with pid 31286 (/usr/lib/YaST2/bin/y2base). Close this application before trying again. --- cut --- The message comes from Pkg.LastError https://github.com/yast/yast-yast2/blob/8a742d3d35f5f0a597267a1fef0e3c67778d... It just shows the process, but we can get more from the system: ps --pid 31286 -o command returns COMMAND /usr/lib/YaST2/bin/y2base scanner ncurses IMO this would be good enough to tell the user which process they need to terminate (BTW, some newline might help). The bug also talks about some advanced artificial intelligence where SW Mgmt would advice user that is't not wise to start before Yast Scanner is closed, etc. but this is IMO beyond logical possibilities as we 1. never know whether Scanner or any other Yast module WILL need package lock, and if it already has the lock, we report it 2. not only Yast but also, e.g., zypper or apper use libzypp and thus could create package locks -- You are receiving this mail because: You are on the CC list for the bug.