Bug 130166

Summary:	YaST asks for root password, but never starts. Must use shell to start.
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Bryce Nesbitt <bryce2>
Component:	YaST2	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Bryce Nesbitt 2005-10-22 19:27:45 UTC

I have just installed SUSE Linux 10.0 from scratch.  Everything is fine, except
YaST won't start from a user account.

Starting YaST from the Gnome root menu asks for the root password.  If I enter
the wrong password it complains.  If I enter the correct password, it says
"please wait, verifying password".  Then box closes, and nothing starts. 
Nothing appears in /var/log/messages.

YaST works fine if I first open a terminal window, su to root, then start
/sbin/yast2.

YaST opens (in user mode) if i use Applications->Run Application.

Comment 1 Bryce Nesbitt 2005-10-22 20:29:52 UTC

Nothing appears in /var/log/YaST either.

Comment 2 Michael Gross 2005-10-24 12:27:46 UTC

This works for me... (YaST asks for the pw, verifies it and starts afterwards -- also after a wrong try).

I'm closing this bug because I don't know how this could be reproduced, hence it will be rather impossible to fix here, sorry.

If you find a way to reproduce it or if you can track down the problem, please reopen it.

Comment 3 Bryce Nesbitt 2005-10-24 16:32:06 UTC

Maybe you could suggest a way to get some debugging output?  It must fail for some reason... where is it logged?  How can I get the console output for a program that is launched from the GNOME panel?

Keep in mind this is a brand-new and fresh SUSE installation.

Comment 4 Michael Gross 2005-10-25 12:40:55 UTC

I Could think of none (method to fetch stdin/stderr), if the process is not connected to any (virtual) console.

What you could do is connecting to the running process with gdb and create debug output here. If you don't know how, you would have to read yourself into it.

As we cannot reproduce this, the only way is to do it yourself. If you manage it, please reopen.