Bug 432442 - y2controlcenter-gnome opens with an error message
Summary: y2controlcenter-gnome opens with an error message
Status: RESOLVED DUPLICATE of bug 428963
: 427578 431287 432963 (view as bug list)
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Factory
Hardware: Other Other
: P1 - Urgent : Normal (vote)
Target Milestone: ---
Assignee: Hans Petter Jansson
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-06 03:39 UTC by Alberto Passalacqua
Modified: 2008-10-07 13:57 UTC (History)
4 users (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
y2controlcenter-gnome load error (211.15 KB, image/png)
2008-10-06 03:40 UTC, Alberto Passalacqua
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alberto Passalacqua 2008-10-06 03:39:56 UTC
When opening Yast-gtk control center, the following message is displayed:

"An error occurred when loading or saving configuration information for y2controlcenter-gnome. ..." (See screenshot for the complete error message.

With kind regards,
Alberto
Comment 1 Alberto Passalacqua 2008-10-06 03:40:40 UTC
Created attachment 243536 [details]
y2controlcenter-gnome load error

Screenshot of the load error
Comment 2 JP Rosevear 2008-10-06 13:40:38 UTC
I think probably this is an issue with env vars/gnomesu possibly cookies.
Comment 3 JP Rosevear 2008-10-06 14:03:56 UTC
*** Bug 431287 has been marked as a duplicate of this bug. ***
Comment 4 Forgotten User h13THG8RK1 2008-10-06 14:10:28 UTC
Likely it boils down to bug 428963. All those yast files (/usr/share/applications/YaST2/) use gnomesu...
Comment 5 JP Rosevear 2008-10-07 11:00:56 UTC
*** Bug 432963 has been marked as a duplicate of this bug. ***
Comment 6 JP Rosevear 2008-10-07 13:36:12 UTC
*** Bug 427578 has been marked as a duplicate of this bug. ***
Comment 7 Michael Meeks 2008-10-07 13:57:08 UTC

*** This bug has been marked as a duplicate of bug 428963 ***