Bug 16363

Summary:	Cannot add new plugin to Kate Python Plugin
Product:	Mageia	Reporter:	Vladimir Stepanoff <vs>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia, marja11, vs
Version:	5
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Vladimir Stepanoff 2015-07-13 01:29:40 CEST

Kate->Settings->Configure Kate->Python Plugins used to provide a Pate Manager/Documentation panel. It doesn't now, so new plugins cannot not be added.

Also, starting Kate from a root console indicated several missing required components related to plugins, jedi, kde-develop, etc. I didn't log the names but added what was required, except fot jedi which is not available in the repositories. The, selecting a python plugin for inclusion crashed Kate. I didn't keep the log expecting to be able to reproduce the crash. However, after rebooting Mageia, Kate no longer crashes but ignores the selected plugin.

Vladimir Stepanoff 2015-07-13 01:30:48 CEST

CC: (none) => vs

Comment 1 Vladimir Stepanoff 2015-07-13 16:16:21 CEST

This occurred immediately after upgrading from Mageia 4 online, using mgaonline. 

My new plugins had worked perfectly before upgrade and the earlier method was used in trying to install them. They were placed in /usr/share/apps/kate/pate. I note that none of the provided plugins are executable.

The problem(s) is/are reproducible, but I obviously can't reload Mageia from scratch.

David Walser 2015-07-30 17:22:52 CEST

CC: (none) => mageia
Assignee: bugsquad => lmenut

Luc Menut 2016-08-25 16:47:37 CEST

Assignee: lmenut => kde

Comment 2 Marja Van Waes 2018-04-28 19:03:24 CEST

Hi Vladimir,

Thank you for having taken the needed time to report this issue!

We regret if this issue didn't get fixed in Mageia 5.

Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

I assume this bug doesn't exist in Mageia 6 or later, because KDE and its tools are entirely different there.

Closing as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED
CC: (none) => marja11