Bug 15603

Summary:	Mate daemon starting as collateral effect.
Product:	Mageia	Reporter:	Renato Dali <mkare>
Component:	RPM Packages	Assignee:	Atilla ÖNTAŞ <tarakbumba>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	tarakbumba
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	mate-settings-daemon	CVE:
Status comment:

Description Renato Dali 2015-04-01 05:31:01 CEST

Mate daemon starting as collateral effect (seems a movie title, heh?)

This is part C of previously opened bug 15595 , filed in separate as asked.

Steps:

1. Get Mageia 5 with Xfce and KDE installed.
2. Install Mate.

Then log into KDE, call "mate-appearance-properties" (with the intention to change the appearance of certain apps); regardless of the result, a new daemon is kept running: mate-settings-daemon.

Short ouput:
============================================================
[zz@localhost ~]$ mate-appearance-properties 
[zz@localhost ~]$ ps -ef | grep mate
zz       26077     1  1 15:12 ?        00:00:00 /usr/libexec/mate-settings-daemon
zz       26126 18995  0 15:12 pts/1    00:00:00 grep --color mate
[zz@localhost ~]$
============================================================

I know there's a KDE module to adjust gtk apps appearance, but I was specifically testing interaction between desktops and found that.

I don't even know whether that daemon could cause problems (but it seems probable) or even if it is inadvisable to run mate-appearance-properties inside KDE; I know some people use lxappearance with that same purpose (at least in Xfce IIRC) -- I don't know if that should be avoided, too.

Thanks.

Comment 1 Atilla ÖNTAŞ 2015-04-01 08:20:44 CEST

That is the normal behaviour. mate-appearance-properties needs to mate-settings-daemon to run. As a daemon, when it's started it will stay running. Same applies to KDE. Try to run a KDE specific application, like kwrite or dolphin in MATE Desktop from commandline. You can see that a lot of KDE stuff starts along with these applications. So, this issue should be invalid.

CC: (none) => tarakbumba
Assignee: bugsquad => tarakbumba
Source RPM: (none) => mate-settings-daemon

Comment 2 Renato Dali 2015-04-01 14:47:48 CEST

Thanks for the clarification. I agree that such behaviour can labeled as "normal", in the sense that it it what usually happens. Also, your example of KDE is also very Ã  propos.

That notwithstanding, I hope one day applications will be aware of the context they're started in and don't go starting things on their own but instead use the available infrastructure -- ok, that may be too much to expect.

Otherwise, I suppose using an application out of its DE is bound to bring problems as daemons start changing the behaviour of DEs alien to them.

As for this bug being invalid, yes, that's the corollary of the current situation, but I'd like if a "CLOSED/INFUTURERELEASE" category existed...

Thanks, Atilla.

Comment 3 Renato Dali 2015-04-02 17:39:36 CEST

That means that I'm thanking Attila -- not that I'm signing as Attila. English is so much fun... :-(

Comment 4 Atilla ÖNTAŞ 2015-04-04 21:04:14 CEST

Ok. Since we do not have "infuturerelease" tag unfortunately closing this bug report as invalid.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 5 Renato Dali 2015-04-05 04:03:07 CEST

Ok.