Description of problem: Estaba usando el escritorio Enlightenment E17 en mi pc con Fedora 20 y al salir de E17 y entrar a Mate inmediatamente me aparecio el mensaje de error. Saludos Version-Release number of selected component: caja-1.8.1-5.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: caja crash_function: handle_error executable: /usr/bin/caja kernel: 3.15.10-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 handle_error at xcb_io.c:213 #5 handle_response at xcb_io.c:325 #6 _XEventsQueued at xcb_io.c:364 #7 XEventsQueued at Pending.c:43 #8 _cairo_xlib_shm_info_cleanup at cairo-xlib-surface-shm.c:481 #9 _cairo_xlib_shm_info_create at cairo-xlib-surface-shm.c:640 #10 _cairo_xlib_shm_surface_create at cairo-xlib-surface-shm.c:829 #11 _cairo_xlib_surface_create_shm__image at cairo-xlib-surface-shm.c:1169 #12 _cairo_xlib_surface_draw_image at cairo-xlib-surface.c:1144 #13 surface_source at cairo-xlib-source.c:1019 Potential duplicate: bug 1076931
Created attachment 933552 [details] File: backtrace
Created attachment 933553 [details] File: cgroup
Created attachment 933554 [details] File: core_backtrace
Created attachment 933555 [details] File: dso_list
Created attachment 933556 [details] File: environ
Created attachment 933557 [details] File: limits
Created attachment 933558 [details] File: maps
Created attachment 933559 [details] File: open_fds
Created attachment 933560 [details] File: proc_pid_status
Created attachment 933561 [details] File: var_log_messages
Another user experienced a similar problem: Error message popped up right after first login in a brand new install. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: caja crash_function: handle_error executable: /usr/bin/caja kernel: 3.15.10-201.fc20.x86_64 package: caja-1.8.1-5.fc20 reason: caja killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Dear reporter, why do you think everbody would speak spanish? Can you describe a little more detailed what happend? Did this issue occurs frequently ?
I have a wallpaper script called every few minutes by crontab which contains: gsettings set org.mate.background picture-filename /home/nice/Pictures/OldWallpaper/1.jpg DISPLAY=:0.0 feh --bg-scale "$(find /home/nice/Pictures/OldWallpaper/|grep jpg|shuf -n1)" This seems to run for a while but then I get an error: (process:3582): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=e38bc4f395321e04bd2630c14b2b8580 --binary-syntax --close-stderr': Child process exited with code 1 and abrt then tells me about a crash in caja. I can't make it crash every time but I get this crash a few times over an hour.
dconf (systemd) is bit weird, sometimes it set permission to root for /run/user/1000/dconf There are a lot of reports about this. You should check permissions after crash of this directory. I think your script is a stress test for dconf ;) I sugest to use walpapoz.
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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.