Description of problem: Problem caused by running everpad, which was installed from their git repo. It appears that on the gnome tray icon in the lower right of the screen is the source of the problem, or at least clicking on the icon is. Version-Release number of selected component: python-2.7.3-7.2.fc17 Additional info: backtrace_rating: 4 cmdline: /bin/python /usr/bin/everpad crash_function: operator new executable: /usr/bin/python2.7 kernel: 3.7.9-101.fc17.x86_64 remote_result: NOTFOUND uid: 1000 var_log_messages: Feb 26 14:13:56 davisa-clone abrt[9415]: Saved core dump of pid 9406 (/usr/bin/python2.7) to /var/spool/abrt/ccpp-2013-02-26-14:13:55-9406 (1173667840 bytes) Truncated backtrace: Thread no. 1 (9 frames) #3 operator new at ../../../../libstdc++-v3/libsupc++/new_op.cc:52 #4 allocate at /usr/include/c++/4.7.0/ext/new_allocator.h:94 #5 _M_get_node at /usr/include/c++/4.7.0/bits/stl_tree.h:369 #6 _M_create_node at /usr/include/c++/4.7.0/bits/stl_tree.h:379 #7 _M_clone_node at /usr/include/c++/4.7.0/bits/stl_tree.h:427 #8 std::_Rb_tree<SbkObject*, SbkObject*, std::_Identity<SbkObject*>, std::less<SbkObject*>, std::allocator<SbkObject*> >::_M_copy at /usr/include/c++/4.7.0/bits/stl_tree.h:1044 #10 _Rb_tree at /usr/include/c++/4.7.0/bits/stl_tree.h:634 #11 set at /usr/include/c++/4.7.0/bits/stl_set.h:195 #12 Shiboken::Object::invalidate at /usr/src/debug/shiboken-1.1.0/libshiboken/basewrapper.cpp:875
Created attachment 703112 [details] File: backtrace
Created attachment 703113 [details] File: cgroup
Created attachment 703114 [details] File: core_backtrace
Created attachment 703115 [details] File: dso_list
Created attachment 703116 [details] File: environ
Created attachment 703117 [details] File: limits
Created attachment 703118 [details] File: maps
Created attachment 703119 [details] File: open_fds
Created attachment 703120 [details] File: proc_pid_status
Created attachment 703121 [details] File: smolt_data
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.