Version-Release number of selected component: python3-3.4.2-4.fc22 Additional info: reporter: libreport-2.4.0 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/libexec/dnssec-trigger-script --setup crash_function: pygobject_register_wrapper executable: /usr/bin/python3.4 kernel: 3.19.0-1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 pygobject_register_wrapper at /usr/lib64/python3.4/site-packages/gi/_gi.cpython-34m.so #1 pygobject_constructv at /usr/lib64/python3.4/site-packages/gi/_gi.cpython-34m.so #2 pygobject_init at /usr/lib64/python3.4/site-packages/gi/_gi.cpython-34m.so #3 type_call at /lib64/libpython3.4m.so.1.0 #4 PyObject_Call at /lib64/libpython3.4m.so.1.0 #5 PyEval_EvalFrameEx at /lib64/libpython3.4m.so.1.0 #6 PyEval_EvalCodeEx at /lib64/libpython3.4m.so.1.0 #7 function_call at /lib64/libpython3.4m.so.1.0 #8 PyObject_Call at /lib64/libpython3.4m.so.1.0 #9 method_call at /lib64/libpython3.4m.so.1.0 Potential duplicate: bug 1201830
Created attachment 1002090 [details] File: backtrace
Created attachment 1002091 [details] File: cgroup
Created attachment 1002092 [details] File: core_backtrace
Created attachment 1002093 [details] File: dso_list
Created attachment 1002094 [details] File: environ
Created attachment 1002095 [details] File: limits
Created attachment 1002096 [details] File: maps
Created attachment 1002097 [details] File: open_fds
Created attachment 1002098 [details] File: proc_pid_status
Created attachment 1002099 [details] File: var_log_messages
This seems to be a problem in pygobject3, not in Python. Reassigning.
Hi. This bug is effectively preventing dnssec-trigger dispatcher script from getting DHCP-provided DNS resolvers from NetworkManager using libnm Python bindings. I can reproduce it every time I boot up Fedora 22 with dnssec-trigger enabled.
*** Bug 1226533 has been marked as a duplicate of this bug. ***
*** Bug 1201830 has been marked as a duplicate of this bug. ***
Also on F21 - reproducible every time I connect to a DHCP-enabled network.
Removing the blocking bug, since this seems to be not happening any more, after the SELinux policy update. Also there is no response from the assignee.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I have since upgraded to F23 and I'm not seeing it there.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.