Description of problem: 6_s2: kactivitymanagerd running in Xfce Display Environment. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. clean network install with Plasma, Gnome, Xfce DE installed +updates 2. Create a "junk" user account 3. reboot system 3. gui log into junk with Xfce DE 4. wait an hour 5. click up a terminal su - root journalctl -b | grep kactivitymanagerd
Assigning to XFCE maintainer, because I doubt the KDE maintainers will think this is a bug :-þ There might be more KDE stuff running in XFCE. Using top last time I used XFCE (last night), with nothing else started, except rsync in tty2, I noticed several applications with names that start with a "k".
Keywords: (none) => 6sta2CC: (none) => kde, marja11Assignee: bugsquad => jani.valimaa
(In reply to Marja van Waes from comment #1) > Assigning to XFCE maintainer, because I doubt the KDE maintainers will think > this is a bug :-þ Well, is seems to have shown up with the latest round of kde/plasma updates this week. I just completed a clean network install this morning to verify I did not have something leftover after those updates. > There might be more KDE stuff running in XFCE. Using top last time I used > XFCE (last night), with nothing else started, except rsync in tty2, I > noticed several applications with names that start with a "k". Oh balderdash. Same as you, all sorts of k* running.
Assigning back to bugsquad. As Xfce maintainer I'm not going to decide which KDE/GNOME/Mate/LXQt/LXDE apps should be allowed to start on session startup. It's something that app maintainer and/or upstream should think of plus there're already options to allow/disallow GNOME/KDE services to start on Xfce session startup.
Assignee: jani.valimaa => bugsquad
(In reply to Jani Välimaa from comment #3) > Assigning back to bugsquad. Hehe, I was pretty sure assignment to Xfce was not going to fly. :) As Xfce maintainer I'm not going to decide which > KDE/GNOME/Mate/LXQt/LXDE apps should be allowed to start on session startup. > It's something that app maintainer and/or upstream should think of plus > there're already options to allow/disallow GNOME/KDE services to start on > Xfce session startup. I agree, Default user setting is Gnome stuff, and I have disabled about 98% of the autostart session items. Amount of noise generated by KDE code in logs is ridicules. Out of the box install should only have warn/error enabled.
Assignee: bugsquad => kde
My current workaround is to place kwrite inside of a wrapper script and pkill kactivitymanagerd after launching kwrite.
Status comment: (none) => 6_s2Summary: 6_s2: kactivitymanagerd running in Xfce DE => kwrite starting kactivitymanagerd running in Xfce DESource RPM: kactivitymanagerd-5.8.4-1.mga6.src.rpm => kate-16.12.0-1.mga6.src.rpm
i don't reproduce on todays cauldron. btw with a default xfce + kwrite installed i don't have kactivitymanager installed.
CC: (none) => mageia
(In reply to Nicolas Lécureuil from comment #6) > i don't reproduce on todays cauldron. > btw with a default xfce + kwrite installed i don't have kactivitymanager > installed. Well with kactivitymanager not installed it would be hard to start it. :) Guessing you missed Step 1 in test procedure. :) Just now tried kwrite a and here is a journal snippet. Mar 21 21:02:44 kactivitymanagerd[30938]: Config timer connecting... Mar 21 21:02:45 kactivitymanagerd[30938]: Creating directory: "/home/bittwister/.local/share/kactivitymanagerd/resources/" Mar 21 21:02:45 kactivitymanagerd[30938]: KActivities: Database connection: "kactivities_db_resources_139979994732544_readwrite" Mar 21 21:02:45 kactivitymanagerd[30931]: Cleaning up...
Status comment: 6_s2 => (none)Source RPM: kate-16.12.0-1.mga6.src.rpm => kate-16.12.3-1.mga6.src.rpm
closing bug
Status: NEW => RESOLVEDResolution: (none) => FIXED