Thanks for the reply Anders, I looked at the log and unfortunately nothing 
obvious jumped out at me.  I'm not sure of the etiquette of this list for 
posting log files so I've posted the log at the below link.  

This is the output of a tail -f command as I started yast from the command line 
and attempted to start the Software Management module.If anyone can see 
something out of place in this I'd appreciate the help.

http://www.coalliance.org/~tdonnelly/yast_log.txt

Tim Donnelly 
Systems/Network Administrator 
Colorado Alliance of Research Libraries 
(303)759-3399 x106 

On Wed Mar 7 12:38 , Anders Johansson sent:

On Wednesday 07 March 2007 20:29, Tim Donnelly wrote:
> I'm running the 64 bit version of Open SuSE 10.1. Often (nearly always)
> when I try to go into the Software Management module in YaST I get nothing.
> By nothing I mean, I click the icon, the "thinking" cursor appears and
> stays up for a few seconds then reverts back to the normal arrow cursor. 
> And that's it. Rebooting the server generally allows me to use the module
> for some period of time, then the behavior starts again.
>
> Running a ps -ef | grep yast command produces the following output:
>
> [EMAIL PROTECTED]:~> ps -ef | grep yast
> root 30311 30206 0 12:23 ? 00:00:00 kdesu -u root -c
> /sbin/yast2 root 30312 30311 0 12:23 ? 00:00:00 /bin/bash
> /sbin/yast2 root 30352 1 0 12:23 ? 00:00:00 /bin/bash
> /sbin/yast2 sw_single 1000 30530 30501 0 12:29 pts/4 00:00:00 grep
> yast
>
> I have tried running yast2 from the command line and get the same thing,
> namely nothing.
>
> The rest of the YaST modules seem to work fine, its only the Software
> Management one that is borked.
>
> Any help would be greatly appreciated.

The log file is /var/log/YaST2/y2log and it should contain a trace of what 
yast is up to, and hopefully some clues as to why it's failing

-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to