Description of problem: used batch processing on CR2 images Version-Release number of selected component: rawtherapee-4.0.11-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: rawtherapee crash_function: gdk_x_error executable: /usr/bin/rawtherapee kernel: 3.14.3-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 gdk_x_error at /lib64/libgdk-x11-2.0.so.0 #3 _XError at /lib64/libX11.so.6 #4 handle_error at /lib64/libX11.so.6 #5 handle_response at /lib64/libX11.so.6 #6 _XEventsQueued at /lib64/libX11.so.6 #7 XFlush at /lib64/libX11.so.6 #8 gdk_window_process_all_updates at /lib64/libgdk-x11-2.0.so.0 #9 gdk_window_update_idle at /lib64/libgdk-x11-2.0.so.0 #10 gdk_threads_dispatch at /lib64/libgdk-x11-2.0.so.0 #12 g_main_context_iterate.isra at /lib64/libglib-2.0.so.0
Created attachment 908039 [details] File: backtrace
Created attachment 908040 [details] File: cgroup
Created attachment 908041 [details] File: core_backtrace
Created attachment 908042 [details] File: dso_list
Created attachment 908043 [details] File: environ
Created attachment 908044 [details] File: limits
Created attachment 908045 [details] File: maps
Created attachment 908046 [details] File: open_fds
Created attachment 908047 [details] File: proc_pid_status
Created attachment 908048 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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.
This *may* be fixed by Rawtherapee 4.2, but I didn't want to push out a package for that since that update loses configuration information. If you're hitting this problem, please upgrade to Fedora 22. Thanks!