[Bug 239701] New: Yast Xen Manager - Slow start, no busy pointer
https://bugzilla.novell.com/show_bug.cgi?id=239701 Summary: Yast Xen Manager - Slow start, no busy pointer Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: madprogextrodinr@gmail.com QAContact: jsrain@novell.com The yast xen manager takes a long time to load. This isn't the main problem. The busy pointer comes up for about 20 seconds and then goes back to a normal pointer. So you aren't sure if you it died or what. The first fix needs to keep the busy pointer active the entire time that it takes to display the management screen. -- 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=239701 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |cgriffin@novell.com |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=239701 ccoffing@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #1 from ccoffing@novell.com 2007-02-01 20:01 MST ------- This takes a long time to load, because it's connecting to the package database and ensuring that all the xen packages are installed. I think the slowness is actually in libzypp. Going forward, yast2-vm has been split: the yast tool has been streamlined and only checks the configuration, and it is faster now. The VM installation process is a separate tool, which also starts much faster. I don't think this large change won't be backported to 10.2, but it'll be in SLES10 SP1 and 10.3. -- 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=239701 madprogextrodinr@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #2 from madprogextrodinr@gmail.com 2007-02-01 20:13 MST ------- I agree that you shouldn't back port the changes of splitting things up. What I would hope you would add is additional busy pointer calls for each step that you described above so that at least you see that it is processing vs thinking that the click processed for 20 seconds and then failed. I would think forcing the busy pointer would be easy to do, low risk to the code base. -- 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=239701 lbendixs@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lbendixs@novell.com Status|REOPENED |RESOLVED Resolution| |WONTFIX ------- Comment #3 from lbendixs@novell.com 2007-02-07 08:37 MST ------- The new tool mentioned in comment #1 has the problem fixed in it and the old tool which exists in openSuse 10.2 is deprecated and will not be fixed. Sorry for the inconvenience. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com