Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 85095 - control-center not checking for runing GConfd
Summary: control-center not checking for runing GConfd
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: control-center
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jonathan Blandford
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-02-25 17:40 UTC by Andy Shevchenko
Modified: 2013-04-02 04:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-25 20:03:14 UTC


Attachments (Terms of Use)
screen shot with warning window (deleted)
2003-02-25 17:43 UTC, Andy Shevchenko
no flags Details

Description Andy Shevchenko 2003-02-25 17:40:35 UTC
Description of problem:
I try to start control-center under KDE session, but control-center
outputs the warning. (See attached screen shot)


Version-Release number of selected component (if applicable):
KDE-3.1
control-center from rawhide stream

[root@andriy man8]# rpm -q control-center
control-center-2.2.0.1-8

How reproducible:
just start gnome-control-center from KDE konsole tool


Expected results:
Automated running of GConf daemon

Comment 1 Andy Shevchenko 2003-02-25 17:43:59 UTC
Created attachment 90357 [details]
screen shot with warning window

Comment 2 Jonathan Blandford 2003-02-25 20:03:14 UTC
hrm.  I'm not sure how well the GNOME control-center will run under KDE.  It is
really GNOME specific and won't actually modify anything.  It probably should
have a better warning dialog, though.

Filed upstream as:
http://bugzilla.gnome.org/show_bug.cgi?id=107060


Note You need to log in before you can comment on or make changes to this bug.