Bug 1111285 - Building yad with --with-gtk=gtk3 breaks buttons
Summary: Building yad with --with-gtk=gtk3 breaks buttons
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: yad
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Elder Marco
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-19 15:48 UTC by Mace Moneta
Modified: 2014-06-22 18:39 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-22 18:39:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
fix missing buttons (821 bytes, patch)
2014-06-21 18:48 UTC, Elder Marco
no flags Details | Diff

Description Mace Moneta 2014-06-19 15:48:11 UTC
Description of problem:

When the configure step of the spec file contains the --with-gtk=gtk3 option, yad buttons no longer appear. Removing the option will build a functioning yad.

Version-Release number of selected component (if applicable):
yad-0.26.1-1.fc21

How reproducible:
Always

Steps to Reproduce:
1.yad --title "something" --button "Modify" --button "Exit"
2.
3.

Actual results:
Dialog with no buttons

Expected results:
Dialog with buttons

Additional info:

Comment 1 Elder Marco 2014-06-21 18:48:56 UTC
Created attachment 911062 [details]
fix missing buttons

Hi Mace,

Thanks for the bug report. The patch attached should fix the issue. I've done a test package with the patch applied. Works fine here. Can you test? You can download it here: 

http://koji.fedoraproject.org/koji/taskinfo?taskID=7064797

Please don't wait too long with downloading, as it is a test build the buildsystem will remove it in a couple of days.

Please let me know if this fixes your issue.

Comment 2 Mace Moneta 2014-06-21 18:52:39 UTC
Yes, that build corrects the problem for me. Thanks!

Comment 3 Elder Marco 2014-06-21 19:03:20 UTC
OK.

I will send the patch to upstream and submit a new update for rawhide.


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