[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 306680] Regression in libkactivities: caching disrupts communication between KWin and kactivity
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2012-12-16 13:30:24
Message-ID: bug-306680-17878-aBinWhtdCn () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=306680

--- Comment #10 from Thomas Lübking <thomas.luebking@gmail.com> ---
FTR:
with kdelibs 4.10, kactivities master and kwin master i do still observe issues

1. activities but the default one are stopped and cannot be started (using dbus
directly!) - no matter what (i tried to investigate on preserving window
attachment across sessions)

2. we still get an undeduplicated list for at least the openactivities (at
least for activities added after the re-login / kwin restart), see bug #310850

Assigning windows to running activities works, but if you got 
Default
dummy
dummy

and "dummy #2" is actually "dummy #1", assigning a window to Default and dummy
(#1) will oc. also asign it to dummy (#2) thus "ALL" activities.

From what i can say this bug essentially is very apparent and i could at bes
workaround issue (2) but not (1) and that might actually be the more severe one
(right now, i've got kwrite/sm.cpp on dummy & dummy2 (yeah, actual dummy2, not
dummy #2 ;-) and no way to access it (unless i would of course know how to
manipulate xproperties directly ;-)

Good part is that the session crossing attachment actually sees to work (bug
body =)

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]