Bug 252663 - KDE should not modify GNOME Startup program settings
Summary: KDE should not modify GNOME Startup program settings
Status: RESOLVED DUPLICATE of bug 170817
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.5
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-28 17:28 UTC by Gireesh
Modified: 2010-09-28 17:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gireesh 2010-09-28 17:28:17 UTC
Version:           4.5 (using KDE 4.5.0) 
OS:                Linux

KDE control center has a section to select startup programs. When both gnome and kde are installed, kde automatically starts the programs from gnome startup also. This leads to redundant programs for same function (gnome-screensaver and Kde screensaver, Gnome-power-manager and kde power plasmoid etc). 

If I disable the duplicate gnome programs within KDE, it ALSO disables them from starting in gnome. This is not ideal. KDE as a desktop should not modify the settings of the other desktop.

Reproducible: Didn't try

Steps to Reproduce:
1. Install both KDE and GNOME
2. Login to GNOME and See the startup programs
3. Logoff GNOME and Login to KDE
4. Some GNOME startup programs are started
5. Go to KDE control center --> startup and disable GNOME related programs.
6. Logoff KDE and go to GNOME and check.

Actual Results:  
If I disable the duplicate gnome startup programs within KDE, it ALSO disables them from starting in gnome. This is not ideal. KDE as a desktop should not modify the settings of the other desktop.

Expected Results:  
KDE as a desktop should not modify the settings of the other desktop.

I can't confirm this but I don't remember this used to be the case before 4.4?
Comment 1 Gireesh 2010-09-28 17:29:31 UTC
I'm sorry I forgot to update "Reproducability" column. I was able to reproduce it 4 out 4 times.
Comment 2 Christoph Feck 2010-09-28 17:32:06 UTC

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