Bug 17155 - 6_s1: Unable to launch Edit Applications from plasma/kde task bar
Summary: 6_s1: Unable to launch Edit Applications from plasma/kde task bar
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: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 17523
  Show dependency tree / graph
 
Reported: 2015-11-15 15:33 CET by Bit Twister
Modified: 2016-07-30 22:52 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

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

Description Bit Twister 2015-11-15 15:33:13 CET 
Description of problem:

 Unable to launch Edit Applications  from plasma/kde task bar

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


How reproducible:


Steps to Reproduce:
1. Right click kde icon in task bar.
2. Click Applications
3. Click A launcher based on cascading popup menus
4. click Switch
5. Right click Edit Applications



Reproducible: 

Steps to Reproduce:
Marja Van Waes 2015-11-15 19:37:28 CET

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

Rémi Verschelde 2016-01-19 11:00:20 CET

Blocks: (none) => 17523

Bit Twister 2016-07-06 21:44:50 CEST

Summary: mga6: Unable to launch Edit Applications from plasma/kde task bar => 6_s1: Unable to launch Edit Applications from plasma/kde task bar

Comment 1 Nicolas Lécureuil 2016-07-17 00:35:18 CEST 
is this bug still valid under Plasma 5.7.1 ?
Comment 2 Bit Twister 2016-07-17 02:24:25 CEST 
(In reply to Nicolas Lécureuil from comment #1)
> is this bug still valid under Plasma 5.7.1 ?

Yes and using breeze desktop.
Comment 3 Ulrich Beckmann 2016-07-28 12:08:42 CEST 
It is also valid using Application Launcher.
Plasma version is 5.7.2-1.mga6.

CC: (none) => bequimao.de

Comment 4 Bit Twister 2016-07-30 22:52:59 CEST 
Guessing kde-rootactions-servicemenu must have fixed the problem.

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