Version-Release number of selected component: gimp-2.8.10-4.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gimp-2.8 /home/godfrey/multipageproject/image-0003.pnm crash_function: elf_get_dynamic_info executable: /usr/bin/gimp-2.8 kernel: 3.12.10-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 elf_get_dynamic_info at get-dynamic-info.h:44 #1 _dl_map_object_from_fd at dl-load.c:1432 #2 _dl_map_object at dl-load.c:2382 #3 dl_open_worker at dl-open.c:224 #4 _dl_catch_error at dl-error.c:177 #5 _dl_open at dl-open.c:650 #6 dlopen_doit at dlopen.c:66 #7 _dl_catch_error at dl-error.c:177 #8 _dlerror_run at dlerror.c:163 #9 __dlopen at dlopen.c:87
Created attachment 923511 [details] File: backtrace
Created attachment 923512 [details] File: cgroup
Created attachment 923513 [details] File: core_backtrace
Created attachment 923514 [details] File: dso_list
Created attachment 923515 [details] File: environ
Created attachment 923516 [details] File: exploitable
Created attachment 923517 [details] File: limits
Created attachment 923518 [details] File: maps
Created attachment 923519 [details] File: open_fds
Created attachment 923520 [details] File: proc_pid_status
Created attachment 923521 [details] File: var_log_messages
Hmm. This crash is rather odd, as it happens in: ... #11 g_module_open (file_name=0x7fae2c298020 "/usr/lib64/gegl-0.2/jp2-load.so", flags=flags@entry=0) -> #9 0x00007fae22b1b0c1 in __dlopen (file=file@entry=0x7fae2c297ad0 "/usr/lib64/gegl-0.2/jp2-load.so", mode=mode@entry=258) ... This "simple" dlopen() call is not something I'd expect to be able to crash, unless some bug in _init()/_fini() functions were involved (but apparently isn't). What did you do when the crash happened? Can you reproduce it?
It happens when I wanted to start GIMP. I have since removed Fedora from my machine and using Ubuntu. I had numerous issues with Fedora 20 with other softwares as well and the file system got corrupted.
Without any way to reproduce the bug, I'll close it as there's no way for me to debug it. You should check whether your hardware is okay though -- I don't see these issues you describe, neither with GIMP nor other programs or the file system and I use and have used F-20 on several systems (bare metal and virtual machines).