Version-Release number of selected component: abrt-2.2.1-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/abrt-action-notify -d /var/tmp/abrt/ccpp-2014-05-09-13:41:42-2483 crash_function: update_refs dso_list: executable: /usr/bin/python2.7 exploitable: kernel: 3.14.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 var_log_messages: Truncated backtrace: Thread no. 1 (10 frames) #0 update_refs at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:400 #1 collect at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:998 #2 collect_generations at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:1124 #3 _PyObject_GC_Malloc at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:1585 #4 _PyObject_GC_NewVar at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:1605 #5 PyTuple_New at /usr/src/debug/Python-2.7.5/Objects/tupleobject.c:106 #6 PyTuple_Pack at /usr/src/debug/Python-2.7.5/Objects/tupleobject.c:210 #7 PyType_Ready at /usr/src/debug/Python-2.7.5/Objects/typeobject.c:4025 #8 dbus_py_init_string_types at ../../_dbus_bindings/string.c:345 #9 init_dbus_bindings at ../../_dbus_bindings/module.c:272 Potential duplicate: bug 735662
Created attachment 913339 [details] File: backtrace
Created attachment 913340 [details] File: cgroup
Created attachment 913341 [details] File: core_backtrace
Created attachment 913342 [details] File: environ
Created attachment 913343 [details] File: limits
Created attachment 913344 [details] File: maps
Created attachment 913345 [details] File: open_fds
Created attachment 913346 [details] File: proc_pid_status
Hello, thank you for taking the time report this crash. The crash looks like a bug in Python itself and it appears that your Python isn't healthy (these reports bug #1114575 and bug #1114577 look like a bug in Python too). Did you report more Python crashes recently?
This morning my machine reported a large number of crash logs - about 15 of them. I have never had so many at once before. I reported them all at once. I do not know when they occurred - it may have been over the last week or more. I did not see these as they occurred - it may have been in the background. For what it is worth, I do a `yum update' every morning, and shut down fully every night. My machine is fairly vanilla GNOME F20, but I have installed Xfce as well and that is the desktop I use. I am happy to provide any more info if I can.
OK, if /var/tmp/abrt/ccpp-2014-05-09-13:41:42-2483 directory still exists, please run the following command as root user and report the results here (we will see whether the crash is reproducible): $ /usr/bin/python /usr/bin/abrt-action-notify -d /var/tmp/abrt/ccpp-2014-05-09-13:41:42-2483
The directory is still there. When I ran the command, the Problem Reporting tool appeared again. It won't log a new fault, though; it says: --- Running report_uReport --- A bug was already filed about this problem: Bugzilla: URL=https://bugzilla.redhat.com/show_bug.cgi?id=1114577
(In reply to Liam Proven from comment #12) > The directory is still there. When I ran the command, the Problem Reporting > tool appeared again. Yes, that is expected behaviour. The command emitted a DBus signal which the Problem Reporting tool is listening for. > It won't log a new fault, though; it says: > > --- Running report_uReport --- > A bug was already filed about this problem: > Bugzilla: URL=https://bugzilla.redhat.com/show_bug.cgi?id=1114577 This is also expected behaviour. ABRT won't let you create a new Bugzilla ticket for the crash because you have already created one. Neither you nor I can reproduce the crash. So, if you don't mind, I would close this bug report as WORKSFORME.
Sure, no problem. If it happens again, should I avoid reporting it again?
(In reply to Liam Proven from comment #14) > Sure, no problem. If it happens again, should I avoid reporting it again? No, please report any further crash you experience. But anyway, I believe that this particular crash won't happen again (it was probably caused by a rare constellation of circumstances).