Description of problem:
I opened an old working directory with a new version of eclipse.
During the update process this warning about a crash of eclipse-pydev came up, but the instalation seems to have comleted successfully.
Version-Release number of selected component:
cmdline: /usr/bin/python2.7 -u /usr/lib64/eclipse/dropins/pydev-core/eclipse/plugins/org.python.pydev_18.104.22.168505131500/pysrc/pycompletionserver.py 55154
runlevel: N 5
Thread no. 1 (10 frames)
#0 init_libpycomps at /usr/src/debug/libcomps-e11ff1b16f901139ee4e9d6ccc9219982ceaebd5/libcomps/src/python/src/pycomps.c:1038
#1 _PyImport_LoadDynamicModule at /usr/src/debug/Python-2.7.10/Python/importdl.c:53
#2 load_module at /usr/src/debug/Python-2.7.10/Python/import.c:1919
#3 import_submodule at /usr/src/debug/Python-2.7.10/Python/import.c:2704
#4 load_next at /usr/src/debug/Python-2.7.10/Python/import.c:2519
#5 import_module_level at /usr/src/debug/Python-2.7.10/Python/import.c:2228
#6 PyImport_ImportModuleLevel at /usr/src/debug/Python-2.7.10/Python/import.c:2292
#7 builtin___import__ at /usr/src/debug/Python-2.7.10/Python/bltinmodule.c:49
#8 PyObject_Call at /usr/src/debug/Python-2.7.10/Objects/abstract.c:2529
#9 PyEval_CallObjectWithKeywords at /usr/src/debug/Python-2.7.10/Python/ceval.c:3981
Potential duplicate: bug 1107994
Created attachment 1054068 [details]
Created attachment 1054069 [details]
Created attachment 1054070 [details]
Created attachment 1054071 [details]
Created attachment 1054072 [details]
Created attachment 1054073 [details]
Created attachment 1054074 [details]
Created attachment 1054075 [details]
Created attachment 1054076 [details]
Created attachment 1054077 [details]
Created attachment 1054078 [details]
Created attachment 1054079 [details]
Is this reproducable?
It would really help us if you could attach some sample workspace that exhibits the problem.
I tried to create a couple of example workspaces with older versions of eclipse which I expected to have the same behavior, but have not been able to recreate the problem. Next time I will try with a fresh fedora install.
So you can not reproduce it now?
No, it won't crash on my test machine.
I have since upgraded all my systems to Fedora 23, so maybe just close the bug.
Closing the bug as per previous comment.
*** Bug 1288639 has been marked as a duplicate of this bug. ***