Bug 16063 - kate would not run after installation
Summary: kate would not run after installation
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-31 23:34 CEST by roger herz-fischler
Modified: 2016-09-18 20:47 CEST (History)
1 user (show)

See Also:
Source RPM: kate
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description roger herz-fischler 2015-05-31 23:34:47 CEST 
Description of problem:
kate would not run after installation.
An error message was produced on the screen:
"A KDE text-editor component could not be found"




Version-Release number of selected component (if applicable):
4.14.3



How reproducible:

Steps to Reproduce:
1. use software management
2. install kate
3.  try to run


Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2015-05-31 23:49:42 CEST 
Looks like a missing requires. Can you attach the output of rpm -qa --last ?

Assignee: bugsquad => mageia
Source RPM: (none) => kate
Whiteboard: (none) => MGA5TOO

Comment 2 David Walser 2015-06-01 13:29:00 CEST 
Strange, kate requires ktexteditor and libktexteditor4.

CC: (none) => lmenut

Samuel Verschelde 2016-08-25 16:24:23 CEST

Assignee: mageia => kde

Luc Menut 2016-08-25 16:42:29 CEST

CC: lmenut => (none)

Comment 3 Nicolas Lécureuil 2016-09-18 17:02:32 CEST 
is this bug still valid for you ? 
I can't reproduce on a fresh install.

CC: (none) => mageia

Comment 4 roger herz-fischler 2016-09-18 19:06:25 CEST 
No, kate installed correctly on another (my working) computer.

I am beginning to think that it is either me or the newer computer which I use to test
Comment 5 Nicolas Lécureuil 2016-09-18 20:47:32 CEST 
closing.

Please reopen if the pb reappear.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.