Frank-Michael Fischer wrote:
So: I am well trained in taking comments like yours.
can't you beleive most users have _not_ the problem you have?
I have a default kde install, and had some kind of bugs, but
_not_ the one you have.
Did you have a look at your systems load for the first 10 to 30 minutes
after booting? And this with the default sw setup? It would be more
constructive to give us (or bugzilla) some real numbers showing that
your default sw installation setup does not have the bug.
please, the people that _don't_ have the bug don't have to
report. don't change the rules...
And I found the real problem: it's the way libzypp is architected and
implemented. Now what?
you may be wrong, don't you? do you know the inerts of libzipp?
what I try to make you understant is that if _you_ have
_several_ non working install, this may be because you
always make a kind of install that gives the problem.
this don't mean you do anything wrong, only something that
not any people do. identifying this could be of great help
like the rug test you where asked to do.
and all this helps fixing the bug.
and by the way the starting of the 10.1 is specially fast on
my two years old machine... and I just discovered beagle was
running.. I even don't know what it is :-)
to follow this mail, I tryed beagle. clic on the icon, ask
for "yast" in the search box. Beagle said the daemon was not
started, I clic to start and answers come is nearly no time.
I will try the "lanch on start and see is this slows the