On Sun, 31 Jul 2005 16:37:02 -0500 JB wrote:

Today for the first time I tried to use the runlevel editor in YaST on my 9.3 system, but when it started it got to about 'cron' and then just sat there and did nothing more. Everything below 'cron' remained with the question marks. I even let it sit for an hour and a half and still nothing happened, it just sat there with the little clock next to the cursor. Anyone else had this problem? Any 'fix' anyone knows of? I'm updated with YOU since yesterday by the way.

I had a similar problem with the YaST 'Software Install' window on my 9.3 system -- that window just sat there unresponsive, no matter what I did with the keyboard or mouse. [Though in my case the cursor was without the little clock.] Turned out a dialog window had been opened, which did not have focus, but was hidden BEHIND the 'Software Install' window I was looking at. [The 'Software Install' window became responsive again once I had discovered the dialog window, and clicked on its 'OK' button.] I think it's some kind of a bug if dialog windows open BEHIND the things they affect. mikus

Op maandag 1 augustus 2005 03:56, schreef Mikus Grinbergs:

I had a similar problem with the YaST 'Software Install' window on my 9.3 system -- that window just sat there unresponsive, no matter what I did with the keyboard or mouse.  [Though in my case the cursor was without the little clock.]

Turned out a dialog window had been opened, which did not have focus, but was hidden BEHIND the 'Software Install' window I was looking at.  [The 'Software Install' window became responsive again once I had discovered the dialog window, and clicked on its 'OK' button.]

I think it's some kind of a bug if dialog windows open BEHIND the things they affect.

In case you use kde it is a feature. The window that you're working keeps focus and is not disturbed by a window that is popping up. You can configure this is in kcontrol, and give pop up more priority e.g. -- Richard Bos Without a home the journey is endless

On Tue, 2 Aug 2005 03:35 am, Richard Bos wrote:

...

that window just sat there unresponsive, no matter what I did with the keyboard or mouse. [Though in my case the cursor was without the little clock.]

Turned out a dialog window had been opened, which did not have focus, but was hidden BEHIND the 'Software Install' window I was looking at. [The 'Software Install' window became responsive again once I had discovered the dialog window, and clicked on its 'OK' button.]

I think it's some kind of a bug if dialog windows open BEHIND the things they affect.

In case you use kde it is a feature. The window that you're working keeps focus and is not disturbed by a window that is popping up. You can configure this is in kcontrol, and give pop up more priority e.g.

Fire up Control Center, go to Desktop - Window Behaviour and look on the Advanced tab. Focus stealing prevention is set to Low by default, (which drives me nuts). But if you set it any higher than Normal you will see this kind of behaviour. When it happens, it's worth Centre-clicking the titlebar of the blocked window to send it to the back, to see if something is trapped behind it. michaelj PS: How do those non-X users survive without being able to centre-click through a stack of windows? Especially without 12 desktops to work on. Poor things. -- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166 No matter how much you pay for software, you always get less than you hoped. Unless you pay nothing, then you get more.