https://bugzilla.novell.com/show_bug.cgi?id=464680 User bluedzins@wp.pl added comment https://bugzilla.novell.com/show_bug.cgi?id=464680#c2 Maciej Pilichowski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|bluedzins@wp.pl | --- Comment #2 from Maciej Pilichowski 2009-02-13 08:46:11 MST --- No, but this is general problem, not that "in my case..." -- it is related to principles of SM design, how it handles "dangling" locks. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=464680 User lslezak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464680#c3 Ladislav Slezak changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |bluedzins@wp.pl --- Comment #3 from Ladislav Slezak 2009-02-23 02:30:01 MST --- The locks are handled quite well in the package manager - file /var/run/zypp.pid contains PID of the process which has the lock. If the process is not running the lock is automatically removed, so you should never need to manually remove the lock if SM has crashed. Please, attach yast logs, there is more information about the lock (why it could not have been obtained). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=464680 User lslezak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464680#c5 Ladislav Slezak changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |bluedzins@wp.pl --- Comment #5 from Ladislav Slezak 2009-02-23 07:42:56 MST --- Um, the logs do not contain any failed attempt, all attempts to obtain the lock were successful. Maybe the old logs were removed from the system (yast keeps 10 previous log files by default). Please, try to reproduce and attach the logs again. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=464680 User lslezak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464680#c7 Ladislav Slezak changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #7 from Ladislav Slezak 2009-03-02 06:46:42 MST --- The log contains these messages from the failed SM start: 2009-02-27 19:59:28 <5> linux-dqhf(6873) [zypp] Exception.cc(log):133 Close this application before trying again. 2009-02-27 19:59:28 <5> linux-dqhf(6873) [zypp] Exception.cc(log):133 PkgFunctions.cc(zypp_ptr):103 RETHROW: ZYppFactory.cc(getZYpp):366: System management is locked by the application with pid 2863 (/usr/lib/YaS T2/bin/y2base). 2009-02-27 19:59:28 <5> linux-dqhf(6873) [zypp] Exception.cc(log):133 Close this application before trying again. 2009-02-27 19:59:28 <3> linux-dqhf(6873) [Pkg] PkgFunctions.cc(Connect):165 Error in Connect: FactoryException: System management is locked by the application with pid 2863 (/usr/lib/YaST2/bin/y2base). Close this application before trying again. Process 2863 is still running and prints messages 2009-02-27 20:02:21 <1> linux-dqhf(2863) [satsolver] PoolImpl.cc(logSat):81 installing old packages 2009-02-27 20:02:21 <1> linux-dqhf(2863) [satsolver] PoolImpl.cc(logSat):81 resolving job rules to the log. So there is no "dangling" lock, there is another Yast instance running and Yast behaves correctly regarding to the locks. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=464680 User lslezak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464680#c9 Ladislav Slezak changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID --- Comment #9 from Ladislav Slezak 2009-03-02 07:54:21 MST --- Sorry, there is no crash, another Yast _is_ still running. See the log or check the list of running processes (Ctrl+Esc in KDE). Process 2863 is solving package dependencies in a loop (that's another bug), while another Yast instance is started which of course fails because another yast is already running. You have to close (kill) the "frozen" Yast (reported in bug 480553), which has process ID 2863, before starting Yast again. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=464680 User lslezak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464680#c11 --- Comment #11 from Ladislav Slezak 2009-03-02 09:58:58 MST --- Oh, OK, I got it. I thought that Yast crashed completely and another idea was that it's running (completely). I didn't think about half-running Yast. Anyway, the popup tells it clearly what to do in such case - close the application which name and PID is displayed in the popup. You can close it using X button or by a process manager (if there is no window). The only way how to "fix" it is to explicitly kill the process. But that's too dangerous IMO, the process might be a running update, killing it in the middle of the update process may result in a broken (unusable) system. The _user_ should decide what to do, any "magic" is not desired in such potentially dangerous situation. -- 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.