Bug 323819 - Windows with imported KWin rules for acitivities aren't visible
Summary: Windows with imported KWin rules for acitivities aren't visible
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kwin
Classification: Plasma
Component: activities (show other bugs)
Version: 4.11.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-21 06:26 UTC by meyerm
Modified: 2018-10-10 12:18 UTC (History)
2 users (show)

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


Attachments
An exported rule that doesn't work (205 bytes, application/octet-stream)
2013-10-03 15:41 UTC, Avihay
Details

Note You need to log in before you can comment on or make changes to this bug.
Description meyerm 2013-08-21 06:26:28 UTC
After upgrading to KDE 4.11.0 some program windows were not visible anymore even though the programs were started correctly. I had KWin rules defined that made Kontact, Kopete and Clementine visible on all activities. After deactivating this Activity rule and reactivating it, the windows showed up as expected.

Exporting and re-importing the rules doesn't help. Neitherwill playing around with other settings of the rule (like Desktop etc). You don't have to delete the whole rule. Just deactivating, and after applying the rule reactivating, the Activity setting is enough.
Comment 1 Thomas Lübking 2013-08-21 09:28:21 UTC
That's because of a change from "ALL" to "00000000-0000-0000-0000-000000000000" for "ALL" activities.

A kconfupdate script should have taken care of that (and is confirmed to work correctly), but apparently wasn't run (since you're the second person encountering this)
Comment 2 Avihay 2013-10-03 15:41:46 UTC
Created attachment 82642 [details]
An exported rule that doesn't work

Hope this helps in some way
Comment 3 Thomas Lübking 2013-10-03 16:12:27 UTC
Yes, the "ALL" statement there is the problem - it's become invalid.

It's no surprise that rules that have been exported with "ALL" now fail on re-import, but the present rules should have been updated with the kconf update. We'd rather need to understand why it didn't run after the version update...
Comment 4 Alexander Mentyu 2018-04-04 14:05:58 UTC
Is this bug can be safely closed?
Comment 5 David Edmundson 2018-10-10 12:18:11 UTC
Yeah, it sucks that we had an ID change, but it's too late to migrate stuff now.