Hide Forgot
Version-Release number of selected component: mate-file-manager-1.6.3-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: caja -n crash_function: handle_error executable: /usr/bin/caja kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 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 XPending at Pending.c:55 #8 gdk_check_xpending at gdkevents-x11.c:159 #9 gdk_event_check at gdkevents-x11.c:2378 #10 g_main_context_check at gmain.c:3557 #13 gtk_main at gtkmain.c:1257 Potential duplicate: bug 868472
Created attachment 840006 [details] File: backtrace
Created attachment 840007 [details] File: cgroup
Created attachment 840008 [details] File: core_backtrace
Created attachment 840009 [details] File: dso_list
Created attachment 840010 [details] File: environ
Created attachment 840011 [details] File: limits
Created attachment 840012 [details] File: maps
Created attachment 840013 [details] File: open_fds
Created attachment 840014 [details] File: proc_pid_status
Created attachment 840015 [details] File: var_log_messages
Can you describe a little more detailed what happend? Did this issue occurs frequently ?
I was able to reproduce this bug on fresh install of F20, first login.
Than forward the issue to upstream ;) Reopening a bug whithout given upstream a chance to work on it is useless.
Another user experienced a similar problem: I just moved the cursor over the icons on desktop. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: caja -n crash_function: handle_error executable: /usr/bin/caja kernel: 3.13.2-200.fc20.i686 package: mate-file-manager-1.6.3-1.fc20 reason: caja killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Same as Comment 12, above - first login, no interaction, immediate abort. Closing this as "INSUFFICIENT DATA" is just avoiding the issue. There is enough information: 1) fresh install Fedora 20 2) install Mate Desktop group 3) choose Mate as desktop environment and log in 4) observe error I bet you don't even have to have a fresh install of Fedora 20 - just install the Mate desktop group, create a new user, and log in to Mate as that new user. It would take about two minutes to reproduce this problem. If the response from Fedora QA is "forward the issue to upstream ;)", then why even have a Fedora Bugzilla, or a QA team?
Sorry, Mr. Need Real Name or should i say Mr. Smith, or Mr. Upset ;) You've lost your bet. I installed Mate very often directly from netiso image, using lightdm as DM and i can't reproduce the issue. If a issue is reproduceable than it is the normal way to forward them to upstream for fixing the code. A fedora package maintainer isn't the developer of the software.