Bug 23103 - Non-functional Search and Replace and Build Output buttons in kate (fixed upstream)
Summary: Non-functional Search and Replace and Build Output buttons in kate (fixed ups...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-01 01:05 CEST by Support at DBCobol
Modified: 2020-08-16 23:50 CEST (History)
6 users (show)

See Also:
Source RPM: kate-17.12.2-1.mga6.i586
CVE:
Status comment:


Attachments

Description Support at DBCobol 2018-06-01 01:05:17 CEST
Description of problem:

Following the Mageia 6 updates of 2018-05-13, kate 17.12.2 stopped working as flawlessly as before. Two bug reports were posted, copied below, and a response was received, also copied below. The maintainer noted that the flaws were a temporary regression, now fixed. See https://bugs.kde.org/show_bug.cgi?id=394254

The current version seems to be 17.12.3 (Ubuntu). The bugs will disappear with the version upgrade.

Bug 1:
Search in Files and Build bring up the corresponding plugin panels and work well, but clicking on the Search and Replace and Build Output buttons does nothing. They should remove (minimize) the respective panel. ESC does remove both the panels but subsequent clicks on the persistent buttons serve only to change their color.

Bug 2:
When both Symbol List and Document plugins are selected together the (first chosen?) button works once only the first time and the other just changes color. 

Response from maintainer:
This is fixed - this regression was only temporary in the KMultiTabBar, but
never released. Maybe Mageia released an updated version which has this
regression. Please update.
Support at DBCobol 2018-06-01 01:06:45 CEST

CC: (none) => support

Marja Van Waes 2018-06-01 19:44:01 CEST

Assignee: bugsquad => kde
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=394254
Summary: Non-functional Search and Replace and Build Output buttons in kate => Non-functional Search and Replace and Build Output buttons in kate (fixed upstream)

Comment 1 Nicolas Lécureuil 2018-06-02 01:23:10 CEST
yes, I plan to update to 17.12.3 in a near future.

CC: (none) => mageia

Comment 2 Guillermo Hazebrouck 2018-06-11 15:22:32 CEST
(In reply to Nicolas Lécureuil from comment #1)
> yes, I plan to update to 17.12.3 in a near future.

Kate 17.12.2 package is causing serious trouble in Mageia 6. I have submitted a new bug today, but now I see the problem was already know. Please, consider removing this package, even if the fix is not ready yet. Installing it will damage the system.

CC: (none) => gahazebrouck

Marja Van Waes 2018-06-11 22:20:22 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=23167

Comment 3 Deri James 2018-08-20 22:02:29 CEST
The problem appears fixed in cauldron (v18.04.1) but it affects v17.12.2, it would be nice if this could be fixed before the 6.1 isos are released. The bug means that almost all kate plugins are unusable because their tab buttons do not work.

CC: (none) => deri

Comment 4 Paweł Susicki 2018-10-13 21:42:20 CEST
still waiting for v17.12.3 ...

CC: (none) => spam

Comment 5 Aurelien Oudelet 2020-08-16 20:49:43 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

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

Comment 6 Support at DBCobol 2020-08-16 23:50:28 CEST
This bug disappeared long ago, before Mageia 7, but nobody bothered to note the fact. Myself included, sorry!.

Note You need to log in before you can comment on or make changes to this bug.