| Summary: | launcherPosition, launcherActivities are broken in libtaskmanager | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Michail Vourlakos <mvourlakos> |
| Component: | Task Manager and Icons-Only Task Manager widgets | Assignee: | Eike Hein <hein> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.11.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Would you mind adding your comment and the result of any further investigations to https://bugs.kde.org/show_bug.cgi?id=385594? The bug will be fixed faster if we centralize information there. Thanks! of course, no prob |
These two functions from TasksModel are broken, what is happening is the following. Plasma possibly added new functionality in 5.11 for which a task's launcher url is changed in something more generic. For systemsettings that would be, applications:systemsettings.desktop . I found that this is happening for launchers and windows in 5.11, I dont know for startups. Because of this launcherPosition and launcherActivities return -1 and null accordingly. For cases that instead of the above the desktop url is used e.g. file:///usr/share/applications/systemsettings.desktop then the functions I think they worked correctly. I used the following code on the click event of a task in Latte in order to check the behavior. console.log("POS :::: "+ tasksModel.launcherPosition(LauncherUrlWithoutIcon) + " - " + tasksModel.launcherPosition(LauncherUrl) + " - " + tasksModel.launcherActivities(LauncherUrl)); at all cases of launchers and windows the results where "POS :::: -1 - -1 -"