Bug 1369044 - calling threads_init is no longer needed
Summary: calling threads_init is no longer needed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: tuned
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-22 11:33 UTC by Tomasz Kłoczko
Modified: 2017-12-25 07:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-25 07:13:05 UTC
Type: Bug


Attachments (Terms of Use)

Description Tomasz Kłoczko 2016-08-22 11:33:02 UTC
Description of problem:

After today updates looking across system logs looking for errors and warnings I found:

Aug 22 07:06:10 domek tuned: /usr/lib/python2.7/site-packages/tuned/exports/dbus_exporter.py:27: PyGIDeprecationWarning: Since version 3.11, calling threads_init is no longer needed. See: https://wiki.gnome.org/PyGObject/Threading
Aug 22 07:06:10 domek tuned:  gobject.threads_init()
Aug 22 07:06:10 domek tuned: /usr/lib/python2.7/site-packages/tuned/exports/dbus_exporter.py:45: PyGIDeprecationWarning: GObject.MainLoop is deprecated; use GLib.MainLoop instead
Aug 22 07:06:10 domek tuned:  self._main_loop = gobject.MainLoop()
Aug 22 07:06:10 domek systemd: Started Dynamic System Tuning Daemon.


$ rpm -qf /usr/lib/python2.7/site-packages/tuned/exports/dbus_exporter.py
tuned-2.7.1-1.fc26.noarch

Comment 1 Jaroslav Škarvada 2016-08-23 13:44:39 UTC
Thanks for the report, fixed by the following upstream commit:
https://git.fedorahosted.org/cgit/tuned.git/commit/?id=bbfc2c6e54eee89c92296f47a48892df02b2ca0d

Comment 2 Fedora End Of Life 2017-02-28 10:08:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 3 Tomasz Kłoczko 2017-12-25 07:13:05 UTC
Closing.
I no longer see this issue.


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