Bug 287451 - Stopping an activity doesn't kill the applications running on it
Summary: Stopping an activity doesn't kill the applications running on it
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: activities (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-24 10:49 UTC by Andrea Scarpino
Modified: 2011-11-24 15:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrea Scarpino 2011-11-24 10:49:31 UTC
Version:           unspecified (using Devel) 
OS:                Linux

Hi,
I don't know if this is a bug or a new KDE 4.8 change.

In KDE <= 4.7.3, when I stop an activity the applications which are running on it are killed and when I start the activity the applications are executed again. This was really *useful* and I guess this's activities' goal.
Unfortunately, this do not more happen with KDE 4.8 (current git).

Reproducible: Always

Steps to Reproduce:
- Open kwrite in an activity
- Stop that activity
- reboot
- Start the same activity

Actual Results:  
kwrite doesn't start

Expected Results:  
kwrite start

KDE 4.7.80
Comment 1 Aaron J. Seigo 2011-11-24 14:56:21 UTC
so i just tested and at first i was able to reproduce.

however, i then restarted both kwin and kactivitimanager and it started
working.

can you try:

kquitapp kactivitymanagerd
kactivitymanagerd

then see if it works.. if it doesn't, then next try:

kwin --replace &

and see if it works. my current theory is that one of the two is having issues
with the dbus calls they are trying to make.
Comment 2 Andrea Scarpino 2011-11-24 14:59:28 UTC
(In reply to comment #1)
> so i just tested and at first i was able to reproduce.
> 
> however, i then restarted both kwin and kactivitimanager and it started
> working.
> 
> can you try:
> 
> kquitapp kactivitymanagerd
> kactivitymanagerd
Yeah, restarting kactivitymanagerd made them working as in 4.7 again!
Comment 3 Aaron J. Seigo 2011-11-24 15:11:33 UTC
aha.. ok.. when you log in next, can you comment here again noting whether it works or not? 

i'm guessing that it's an on-log-in issue. one i may have fixed today in response to this bug report, but i'm not 100% sure. 

as it seems you are building from source, if it does still fail for you on log-in, can you update the kactivities repository and then see if that works better on log in? thanks.
Comment 4 Andrea Scarpino 2011-11-24 15:38:49 UTC
I just tried with the latest kactivities git and everything is working.
I'll send a mail to Dirk to ask if this fix can be included in 4.8beta1.