Bug 1045720

Summary: [abrt] mate-file-manager: handle_error(): caja killed by SIGTRAP
Product: [Fedora] Fedora Reporter: 赵凯 <zhaokaihit>
Component: mate-file-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: 7cw5y4hf, comcast.really.sucks, dan.mashal, fedora, plroskin, rdieter, stefano, vdanen, Wilhelm.Buchmueller
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9ecc1e6cfa49e523d740702ab106f0ae1dad14a1
Whiteboard: abrt_hash:c4b60b75bcdfbe47c7261839ea875de658947453
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-23 21:46:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description 赵凯 2013-12-21 13:12:24 UTC 
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
Comment 1 赵凯 2013-12-21 13:12:33 UTC 
Created attachment 840006 [details]
File: backtrace
Comment 2 赵凯 2013-12-21 13:12:35 UTC 
Created attachment 840007 [details]
File: cgroup
Comment 3 赵凯 2013-12-21 13:12:39 UTC 
Created attachment 840008 [details]
File: core_backtrace
Comment 4 赵凯 2013-12-21 13:12:42 UTC 
Created attachment 840009 [details]
File: dso_list
Comment 5 赵凯 2013-12-21 13:12:44 UTC 
Created attachment 840010 [details]
File: environ
Comment 6 赵凯 2013-12-21 13:12:51 UTC 
Created attachment 840011 [details]
File: limits
Comment 7 赵凯 2013-12-21 13:12:53 UTC 
Created attachment 840012 [details]
File: maps
Comment 8 赵凯 2013-12-21 13:12:56 UTC 
Created attachment 840013 [details]
File: open_fds
Comment 9 赵凯 2013-12-21 13:12:58 UTC 
Created attachment 840014 [details]
File: proc_pid_status
Comment 10 赵凯 2013-12-21 13:13:00 UTC 
Created attachment 840015 [details]
File: var_log_messages
Comment 11 Wolfgang Ulbrich 2013-12-29 09:36:07 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 12 Dan Mashal 2014-02-12 22:45:46 UTC 
I was able to reproduce this bug on fresh install of F20, first login.
Comment 13 Wolfgang Ulbrich 2014-02-15 13:48:11 UTC 
Than forward the issue to upstream ;)
Reopening a bug whithout given upstream a chance to work on it is useless.
Comment 14 Pavel Roskin 2014-02-15 15:53:16 UTC 
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
Comment 15 Need Real Name 2014-06-01 04:53:29 UTC 
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?
Comment 16 Wolfgang Ulbrich 2014-06-01 07:03:02 UTC 
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.