Bug 14006 - Konversation isn't added to the Lxqt menu when installed
Summary: Konversation isn't added to the Lxqt menu when installed
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Florian Hubold
QA Contact:
URL:
Whiteboard: 5alpha2
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-28 20:07 CEST by Carolyn Rowse
Modified: 2014-10-26 15:52 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
screenshot LXQT with konversation (54.20 KB, image/png)
2014-08-29 11:13 CEST, Florian Hubold 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Carolyn Rowse 2014-08-28 20:07:29 CEST 
Description of problem:
I'm running an alpha 2 installation made from the dual ISO and using Lqxt which I added afterwards.  I installed Konversation but it isn't showing on the applications menu.  I can however run it from the terminal.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Carolyn Rowse 2014-08-28 20:07:43 CEST

Whiteboard: (none) => 5alpha2

David Walser 2014-08-29 00:37:26 CEST

Assignee: bugsquad => doktor5000

Comment 1 Florian Hubold 2014-08-29 11:13:30 CEST 
Created attachment 5381 [details]
screenshot LXQT with konversation

Sorry, cannot reproduce, see attachment.

CC: (none) => doktor5000

Comment 2 Florian Hubold 2014-08-29 11:14:39 CEST 
What lxqt package did you install? task-lxqt-minimal or task-lxqt ?
FWIW, did you logout/login since the installation?
Comment 3 Florian Hubold 2014-10-26 15:52:59 CET 
Cannot reproduce. Installed task-lxqt-0.8, then within the session installed konversation. Directly after it was installed, it appeared in the menu at Internet -> Konversation.

Reopen if it reoccurs, and please add detailed steps to reproduce please.

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