Bug 314881

Summary:	Task bar does not display tasks from login with "Only show tasks from the current activity" checked
Product:	[Unmaintained] plasma4	Reporter:	Adam <SIDEPIPEUK>
Component:	widget-taskbar	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED FIXED
Severity:	minor	CC:	hein, kwin-bugs-null, ranger.linux
Priority:	NOR
Version First Reported In:	4.10.4
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	missing apps screenshot

Description Adam 2013-02-11 09:45:42 UTC

On log in, open ( or newly opened ) applications do not show in the task bar with the above setting enabled.... its as if the "current activity" is not set as far as task manager is concerned. ( At least ) changing desktop effects advanced settings fixes it until the next login ( doesn't matter what is changed, I was changing from "Raster" to "Native." )

When the "Only show tasks...." is not checked, it works as expected ( though of course will show tasks form all activities if you use them, which I don't really. ) I only have a single activity called "Twin Screen" - I actually deleted all others. This is using the Kubuntu backports packages for Kubuntu 12.10, but doesn't seem as though it would be specific to those.

Reproducible: Always

Steps to Reproduce:
1. Tick "Only show tasks from the current activity" in Task Manager settings.
2. Log out.
3. Log in.
Actual Results:  
Task Manager shows no open tasks.

Expected Results:  
Task manager shows open tasks.

Comment 1 rangerGR 2013-03-08 12:56:50 UTC

Created attachment 77858 [details]
missing apps screenshot

Comment 2 rangerGR 2013-03-08 12:57:31 UTC

I can confirm this bug.
I use only one activity (never had a second one) but when I check the option "Only show tasks from the current activity" task manager doesn't show any application that was open before last log out. Closing and opening again the application doesn't help, its still hidden. Moreover, 
a) those applications aren't shown with "alt+TAB" so there is no way to focus on them b) even if I uncheck the "Only show tasks from the current activity" the applications are shown in task manager but I am allowed to drag 'n drop e.g. a file from one dolphin window to another because for plasma those applications are from different activities.

See attached screenshot. Only one activity but applications are missing from task manager.

Using KDE 4.10.1 / 4.8.4 on ArchLinux

Comment 3 Aaron J. Seigo 2013-06-15 14:42:56 UTC

Very strange. I have an account with just one activity and this works perfectly. There must be some other setting involved. Do you (the reporters) have nepomuk disabled? 

What is really odd is this:

   "changing desktop effects advanced settings fixes it until the next login"

That implies an interaction with kwin. The taskbar relies on the window having the correct information set on it by the window manager to know what activity that window is on. So it seems that perhaps kwin is not getting / setting this information reliably?

Comment 4 Thomas Lübking 2013-06-15 18:30:20 UTC

since i just have the great opportunity to work with a taskbar (somebody owes me a beer, i'd say), it seems as if this was due to a change btween kactivities and kwin
i guess the libtaskbar code requires "ALL" as hint to be on all activities, while it turned "00000000-0000-0000-0000-000000000000" for 4.10, because it's also the default return value for "current activity" when kactivitymanagerd is not running at all?

(see https://git.reviewboard.kde.org/r/107855/ for reasoning, we lost windows what's actually worse than loosing taskbar entries)

Comment 5 Eike Hein 2013-06-16 12:46:26 UTC

It's correct that 4.11 uses a zero id for "all activities" and 4.10 uses "ALL" (that's why I had two branches of the taskbar QML port, one for 4.10 testers and one  for 4.11, with the respective libtaskmanager behaviors).

Comment 6 Thomas Lübking 2013-06-16 18:24:56 UTC

Ok, - it'll fix implicitly with 4.11 then.

For KWin and libtaskbar 4.10, commit 569f79c60f8fd2b3e655433c2c53f840b4c103e9 (pushed March, 5th) should actually fix this (we transform the NULL UUID to  "ALL" but eg. running KWin 4.11 on libtaskbar 4.10 would fail as well as libtaskbar 4.11 alongside KWin 4.11

I assume the latter case can be considered "developer burden" and the bug be closed? (Can someone validate it works on vanilla 4.10.4?)

Comment 7 rangerGR 2013-12-27 01:06:57 UTC

Yes, bug seems fixed now. Please close the bug