opening YAST utilities causes the pointer_to_become_a_busy_one and
stays there for 7-10 seconds - AFTER, the initial checks w/ the progress
bars (-starting the software manager- window if using “package manager”,
or -initializing user & group information- window if using “User and
Group Management.”)
My box is quite fast - quad 2.4 w/ 4gb ram. No matter if I had
previously opened a YAST util, the time it takes from when I first click
the utility to the time the busy cursor disappears is still around 7-10
seconds. The application appears to have been loaded completely, but
that darn busy cursor is still there.
I know the utilities can be used with the busy cursor, but I’d like to
know why it takes so long for it to go away.
Interesting -> This behavior only occurs when the utility is run from
the Yast Control Center
running
Code:
/sbin/yast2 sw_single
in a terminal as root causes the utility to popup quick, and no busy
pointer. But starting up YAST, and then Software Management causes the
busy cursor to stay for about 10 seconds.
No terminal output.
Is this a bug?
Also want to mention that this behavior occurs on ALL YAST programs
I’ve tried.
>
> The YAST Control Center opens instantly BUT…
>
> opening YAST utilities causes the pointer_to_become_a_busy_one and
> stays there for 7-10 seconds - AFTER, the initial checks w/ the
> progress bars (-starting the software manager- window if using
> “package manager”, or -initializing user & group information- window
> if using “User and Group Management.”)
>
> My box is quite fast - quad 2.4 w/ 4gb ram. No matter if I had
> previously opened a YAST util, the time it takes from when I first
> click the utility to the time the busy cursor disappears is still
> around 7-10 seconds. The application appears to have been loaded
> completely, but that darn busy cursor is still there.
>
> I know the utilities can be used with the busy cursor, but I’d like to
> know why it takes so long for it to go away.
>
>
>
> Anyone else experiencing this? Any solutions?
>
>
Have a look in /home/<user-name>/.kde4/share/config/klaunchrc
Good reply, I also found you can change those settings in Configure
Desktop>Desktop>Launch Feedback from the main menu. It gives a good help
article on what its all about too.
Also, the proposed solutions don’t actually solve the problem I’m
having - they’re hacks & something should be done about this. Can anyone
else confirm they’re experiencing the same behavior?
Also, the proposed solutions don’t actually solve the problem I’m
having - they’re hacks & something should be done about this. Can
anyone else confirm they’re experiencing the same behavior?
They are not hacks these are alterations that have been around for years and are included in the desktop settings precisely for that reason.
Then, simply - why does the busy cursor remain so long when accessing it
from YAST but not when I access the application from the terminal?
baskitcaise;1917495 Wrote:
> acompw wrote:
>
> >
> > I’m running GNOME
>
> Ah you should have said in first post
>
> Sorry don`t do Gnome.
Also, the proposed solutions don’t actually solve the problem I’m
having - they’re hacks & something should be done about this. Can
anyone else confirm they’re experiencing the same behavior?
They are not hacks these are alterations that have been around for
> years and are included in the desktop settings precisely for that
> reason.
>
> HTH
>
> –
> Mark…
>
> Nil illegitimi carborundum
