Bug 1608711 - Warning about missing "specifying a version"
Summary: Warning about missing "specifying a version"
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-abrt
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1647170
TreeView+ depends on / blocked
 
Reported: 2018-07-26 08:04 UTC by Frank Büttner
Modified: 2019-06-11 11:03 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-11 11:03:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frank Büttner 2018-07-26 08:04:59 UTC
Description of problem:
When call it, an warning will logged in the journal

Version-Release number of selected component (if applicable):
gnome-abrt-0.3.4-8.el7.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. call gnome-abrt


Actual results:
The following warning will logged:
gnome-abrt.desktop[27372]: /usr/bin/gnome-abrt:36: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.

Expected results:
No warning.

Comment 2 Miroslav Suchý 2018-11-07 11:48:52 UTC
Thank you for report.
This will not make into our priorities in RHEL7. I will move it to upstream,
where it can have better visibility and chances to fix.
If it is important for you to fix this directly in RHEL then please escalate this to Red Hat support.

Comment 3 Ben Cotton 2019-02-19 17:11:54 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.

Comment 4 Matej Grabovsky 2019-06-11 08:45:18 UTC
Cannot reproduce in latest version. It seems this has been fixed already.

Comment 5 Matej Grabovsky 2019-06-11 11:03:04 UTC
This was repaired in https://github.com/abrt/gnome-abrt/commit/f5faa11e and released in version 1.2.1.

Closing as fixed.


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