[Bug 216615] New: yast2 sw_single: takes very long to reconize that another instance of "yast2 single" is already running
https://bugzilla.novell.com/show_bug.cgi?id=216615 Summary: yast2 sw_single: takes very long to reconize that another instance of "yast2 single" is already running Product: openSUSE 10.2 Version: Alpha 5 Platform: All OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dmayr@novell.com QAContact: jsrain@novell.com If there's already an instance of "yast2 sw_single" / "yast2 -i" running, a second instance of the Yast software-module needs very long (about 2 minutes here at my machine) to recognize that fact. In the meantime Yast shows only the "initializing..."-message, before it brings up the following message: "Another process is accessing the package database. Package management cannot be used now." To avoid annoyance, this message could be popping up immediately or maybe any sort of locking should be done. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216615 cthiel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |yast2-maintainers@suse.de |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216615 sh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lslezak@novell.com AssignedTo|yast2-maintainers@suse.de |kkaempf@novell.com Severity|Minor |Normal Component|YaST2 |libzypp QAContact|jsrain@novell.com |kkaempf@novell.com ------- Comment #1 from sh@novell.com 2006-11-06 05:46 MST ------- AFAIK what you see is the effect of a lock, but I fully agree that it shouldn't take that long for that lock to be recognized. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216615 ma@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|schubi@novell.com |lslezak@novell.com ------- Comment #2 from ma@novell.com 2006-11-06 07:30 MST ------- zypp lock returns immediately, but Pkg::Connect (pkg-bindings; PkgModuleFunctions.cc) does up to 10 attemps with 5 seconds sleep between two attemps. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216615 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #3 from lslezak@novell.com 2006-11-09 02:13 MST ------- Fixed in yast2-pkg-bindings-2.13.105 - there are 5 attempts with 3 second sleep now, so the timeout is 15 seconds. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216615 mvidner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@novell.com Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #4 from mvidner@novell.com 2006-11-09 02:57 MST ------- I have already thought about this. If we had Pkg::ConnectShort (with a short timeout, like 5 seconds), then PackageLock::Connect could pop up a "waiting" window that would loop for the whole minute with a possibility to abort. Feel free to set this improvement to Later. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216615 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=216615#c6 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|LATER | --- Comment #6 from Stephan Kulow <coolo@novell.com> 2008-06-25 03:19:16 MDT --- mass reopening all 10.2 LATER+REMIND bugs. -- 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=216615 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=216615#c7 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #7 from Stephan Kulow <coolo@novell.com> 2008-06-25 03:23:28 MDT --- close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on it. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com