Bug 418434

Summary:	Stopping an activity containing a Falkon window closes all Falkon windows
Product:	[Applications] Falkon	Reporter:	Andreas Kilgus <kde>
Component:	general	Assignee:	David Rosca <nowrep>
Status:	REPORTED ---
Severity:	normal	CC:	jurajoravec
Priority:	NOR
Version First Reported In:	3.1.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Andreas Kilgus 2020-03-03 14:33:30 UTC

STEPS TO REPRODUCE
1. Open a Falkon window in your current activity
2. Start/Launch another activity and open a Falkon window there
3. Stop/Pause the activity launched in step 2

OBSERVED RESULT

All Falkon windows are closed, no falkon process is left running.

EXPECTED RESULT

The Falkon window belonging to the stopped activity is the only one being closed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.18.2
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1

Comment 1 Juraj 2020-03-03 17:00:25 UTC

Hello,

What I can thing about is that when you stop some activity it kills the process?
Since multiple Falkon windows does NOT mean that falkon runs multiple processes.

Comment 2 Andreas Kilgus 2020-03-03 18:42:03 UTC

(In reply to Juraj from comment #1)

> What I can thing about is that when you stop some activity it kills the
> process?

Yes, this might be the cause of the behaviour observed.

> Since multiple Falkon windows does NOT mean that falkon runs multiple
> processes.

Maybe "one process for each activity" is required to support activities. I had a look at Falkon's session management (I hope this is the correct name, in german it reads "Sitzungsverwaltung") but sessions can not serve as a workaround as it is not possible to use several sessions simultaneously.

Unfortunately I do not know any browser that supports activities at the moment (https://bugs.kde.org/show_bug.cgi?id=396291, https://bugs.kde.org/show_bug.cgi?id=388333, https://bugs.kde.org/show_bug.cgi?id=384097). With 19 activities partly simultaneously used in changing combinations I am stuck at konqueror 17.04. AFAICS Falkon is the only KDE browser actively worked on, so my hopes for activity support have to go that way.

Comment 3 Juraj 2020-03-04 07:23:14 UTC

> Maybe "one process for each activity" is required to support activities.
This would mess up current settings and so on if you use same profile for all oft hem.

A bit crazy workaround I can think of is using different profiles for each activity, in such case there would be new process created.

> falkon -r -p <my-cute-little-profile>

Comment 4 Andreas Kilgus 2020-03-04 23:04:03 UTC

(In reply to Juraj from comment #3)
> > Maybe "one process for each activity" is required to support activities.
> This would mess up current settings and so on if you use same profile for
> all oft hem.

Well, just for comparison: 23 konqueror processes running on my machine in 4 activities just now - no mess of settings.

But that's the wrong discussion anyway (at least with me as counterpart). I consider it a bug that the nowadays main/default browser of KDE applications does not support activities. The way how this lacking can be changed is beyond my scope/expertise.

> A bit crazy workaround I can think of is using different profiles for each
> activity, in such case there would be new process created.
> 
> > falkon -r -p <my-cute-little-profile>

That's the way activityfox works (well, more or less) for chromium and firefox. One profile/activity. But s. https://bugs.kde.org/show_bug.cgi?id=396291#c2 - this has several flaws.
And does not work for Falkon: Start activity, execute "falkon -r -p test" (BTW: I don't like the idea of having to repeat all my configuration work for every new profile from scratch), stop activity, start activity - the restored Falkon window belongs to the default profile, not to "test".