Bug 694044

Summary: ObConf 2.0.3 gtk warinig
Product: [Fedora] Fedora Reporter: Vytas <vytautas1987>
Component: obconfAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 14CC: mlichvar
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: obconf-2.0.3-6.20091221gitc8ac23.fc15 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-09 04:02:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Vytas 2011-04-06 10:20:23 UTC
Description of problem:
(obconf:3718): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

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

How reproducible:
$ obconf

Steps to Reproduce:
1. $ obconf
  
Actual results:
Gtk-WARNING

Expected results:
nothing

Additional info:
minor

Comment 1 Fedora Update System 2011-05-02 14:33:14 UTC
obconf-2.0.3-6.20091221gitc8ac23.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/obconf-2.0.3-6.20091221gitc8ac23.fc15

Comment 2 Fedora Update System 2011-05-03 04:27:40 UTC
Package obconf-2.0.3-6.20091221gitc8ac23.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing obconf-2.0.3-6.20091221gitc8ac23.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/obconf-2.0.3-6.20091221gitc8ac23.fc15
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2011-05-09 04:02:23 UTC
obconf-2.0.3-6.20091221gitc8ac23.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.