Bug 1383277 - Feature request - GTK+3 version when available upstream soon please
Summary: Feature request - GTK+3 version when available upstream soon please
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: mintmenu
Version: 25
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Wolfgang Ulbrich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-10 10:47 UTC by Mike Simms
Modified: 2016-10-11 22:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-11 22:22:44 UTC
Type: Bug

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

Description Mike Simms 2016-10-10 10:47:44 UTC 
Description of problem:The version of mintmenu in the repositories is not compatible with GTK+3. Please update with the GTK+3 version as and when it becomes available upstream.


Version-Release number of selected component (if applicable):5.6.5-4.fc24


How reproducible:consistently


Steps to Reproduce:
1.install mintmenu as shown in F25 repositories via dnf, yumex-dnf, yum-deprecated or yumex
2.try adding to a panel


Actual results:nothing happens as it won't load


Expected results:added to panel and loaded


Additional info:I'm aware that you are restricted by what is available upstream. Clem did state it should be ready for MATE 1.16 when I asked him via github earlier in the year though https://github.com/linuxmint/mintmenu/issues/133

Still on their todo list: https://github.com/linuxmint/mintmenu/issues/161
Comment 1 Wolfgang Ulbrich 2016-10-11 12:50:07 UTC 
See https://bugzilla.redhat.com/show_bug.cgi?id=1383680
Mate-menu from Ubuntu-Mate will become the replacement for mintmenu in f25.
Scratch build for testing:
http://koji.fedoraproject.org/koji/taskinfo?taskID=16048260
Comment 2 Mike Simms 2016-10-11 22:22:44 UTC 
thanks that's perfect, I'll close this then
Note You need to log in before you can comment on or make changes to this bug.