Bug 135897

Summary:	"additional info" missing in yast /etc/sysconfig Editor
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	k. t. <cooling.crystals>
Component:	YaST2	Assignee:	Ladislav Slezák <lslezak>
Status:	RESOLVED INVALID	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	SUSEwatcher YAST /etc/sysconfig editor y2log /etc/sysconfig/suseconfig logged in as root logged in as root logged in as root me using yast logged in as root this is duplicate picture ignore it please I'm sorry me using yast

Description k. t. 2005-11-29 17:18:30 UTC

"additional info" is missing in yast /etc/sysconfig Editor
I made a switch to Gnome by doing clean reinstall. Yast did not had this problem with KDE.
Also I got this weird message in SUSEWatcher:

yast2-packagemanager.rpmdb.configfiles
During the last package installation, some changed configuration
files were detected. Find the log files for the install process in
/var/log/YaST2/. Check whether your configuration files are still
up to date.

- that doesn't tell me much - what and how ? If I remember correctly then this happened after openoffice recommended update.

Comment 1 k. t. 2005-11-29 17:20:47 UTC

Created attachment 59017 [details]
SUSEwatcher

Comment 2 k. t. 2005-11-29 17:21:38 UTC

Created attachment 59018 [details]
YAST /etc/sysconfig editor

Comment 3 Martin Lasarsch 2005-11-30 11:14:45 UTC

please attach y2log. assigned to the maintainer.

Comment 4 Ladislav Slezák 2005-11-30 11:38:13 UTC

Please attach also /etc/sysconfig/file

Comment 5 k. t. 2005-11-30 14:47:58 UTC

Created attachment 59214 [details]
y2log

Comment 6 k. t. 2005-11-30 14:53:42 UTC

Created attachment 59220 [details]
/etc/sysconfig/suseconfig

Comment 7 k. t. 2005-11-30 15:14:35 UTC

This is interesting. I logged is as "root" and everything seems normal, I guess this has to do something with language (estonian) I have choosen first time I logged in. Then I logged in as root I did not change default language settings.

Comment 8 k. t. 2005-11-30 15:16:13 UTC

Created attachment 59232 [details]
logged in as root

Comment 9 k. t. 2005-11-30 15:16:57 UTC

Created attachment 59235 [details]
logged in as root

Comment 10 k. t. 2005-11-30 15:17:59 UTC

Created attachment 59236 [details]
logged in as root

Comment 11 k. t. 2005-11-30 15:18:49 UTC

Created attachment 59237 [details]
me using yast

Comment 12 k. t. 2005-11-30 15:21:36 UTC

Created attachment 59240 [details]
logged in as root

Comment 13 k. t. 2005-11-30 15:22:35 UTC

Created attachment 59243 [details]
this is duplicate picture
ignore it please
I'm sorry

Comment 14 k. t. 2005-11-30 15:24:33 UTC

oops I made a mistake with attachment 59237 [details] - should be "me using yast" not "logged in as root" - sorry !

Comment 15 k. t. 2005-11-30 15:28:11 UTC

Created attachment 59249 [details]
me using yast

Comment 16 k. t. 2005-11-30 15:29:50 UTC

again!
please ignore attachment 59243 [details] - it is done "then logged in as root" !
sorry!

Comment 17 k. t. 2005-12-03 11:15:13 UTC

Problem seems to disappear if I log out and log in with "default" language.
But problem comes back as soon as I log out and log in with "estonian" language.


About that message - yast2-packagemanager.rpmdb.configfiles
During the last package installation, some changed configuration
files were detected. Find the log files for the install process in
/var/log/YaST2/. Check whether your configuration files are still
up to date. - it doesn't explain what I have to do or I'm afraid I don't understand what "Check whether your configuration files are still
up to date" really means. Should I ignore it ?

Comment 18 k. t. 2006-02-06 09:11:45 UTC

I just realized how bad this bug report is with all these useless screenshots 'then logged in as root' and that 'yast2-packagemanager.rpmdb' is completely different thing and not related to this bug...
So please delete this bug completely and let's start over. 
I'm embarrassed. 
Sorry.