Bug 129165 - Yast is very slow ...
Summary: Yast is very slow ...
Status: RESOLVED INVALID
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Alpha 1
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-18 20:30 UTC by atha v.
Modified: 2005-10-29 15:09 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description atha v. 2005-10-18 20:30:27 UTC 
you have heart that often times i bet ... 
 
But I want to ask, if this is the fault of the "qt-engine" better qt-liberys? 
 
maybe this is an Idea, what you can do, to speed it up ... (this is only my 
thougt: can it be, that Gnome - without QT - is little bit faster?) 
 
so far ... 
 
DJ B.
Comment 1 Martin Lasarsch 2005-10-19 09:51:52 UTC 
sorry, but this is not really a valid bug. It's not slow on my system, this is very subjective. Every system without libs (which are not already in the system) is faster i guess. You can be sure that we try to make it as fast as possible.

unless you say: "when i do in yast this...that..whatever it takes xx seconds" i will close the bug.

please reopen if you think parts of it are slow and you can meassure it.

thanks
Comment 2 atha v. 2005-10-28 20:52:37 UTC 
Oh shit!!!

Sorry the most important thing i've forgotten:

I mean the Yast package Module!

I think It's calling System update. and it takes over 2  or sometimes 5 Minutes!!!

In the past I added 5 repositories, now there are only two.

But no changes!

I've an Athlon 64 3000+ (Maybe it is interesting) and 512 MB RAM

hope you read this

greez DJ B.
Comment 3 atha v. 2005-10-28 20:54:05 UTC 
look above...
Comment 4 Michael Gross 2005-10-29 15:09:49 UTC 
Don't reopen this bug again.