Description of problem: I updated dnssec-trigger, which distributes dnssec-trigger-script. The script is in python and uses libnm Pyhon bindings, which use DBus. Also SELinux prevented an access dbus dir to the Python3.4 Version-Release number of selected component: python3-3.4.1-16.fc21 Additional info: reporter: libreport-2.3.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.18.8-201.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 var_log_messages: [System Logs]:\n-- Logs begin at Fri 2014-05-30 10:03:40 CEST, end at Fri 2015-03-13 15:41:50 CET. -- Truncated backtrace: Thread no. 1 (10 frames) #0 pygobject_register_wrapper at pygobject.c:664 #1 pygobject_constructv at gobjectmodule.c:995 #2 pygobject_init at pygobject.c:1276 #3 type_call at /usr/src/debug/Python-3.4.1/Objects/typeobject.c:869 #4 PyObject_Call at /usr/src/debug/Python-3.4.1/Objects/abstract.c:2067 #5 do_call at /usr/src/debug/Python-3.4.1/Python/ceval.c:4485 #6 call_function at /usr/src/debug/Python-3.4.1/Python/ceval.c:4283 #7 PyEval_EvalFrameEx at /usr/src/debug/Python-3.4.1/Python/ceval.c:2853 #8 PyEval_EvalCodeEx at /usr/src/debug/Python-3.4.1/Python/ceval.c:3607 #9 function_call at /usr/src/debug/Python-3.4.1/Objects/funcobject.c:632
Created attachment 1001418 [details] File: backtrace
Created attachment 1001419 [details] File: cgroup
Created attachment 1001420 [details] File: core_backtrace
Created attachment 1001421 [details] File: dso_list
Created attachment 1001422 [details] File: environ
Created attachment 1001423 [details] File: exploitable
Created attachment 1001424 [details] File: limits
Created attachment 1001425 [details] File: maps
Created attachment 1001426 [details] File: open_fds
Created attachment 1001427 [details] File: proc_pid_status
possible duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1201283 also the SELinux issue https://bugzilla.redhat.com/show_bug.cgi?id=1201813
*** This bug has been marked as a duplicate of bug 1202197 ***