Bug 1105885
| Summary: | [abrt] mate-file-manager: memset(): caja killed by SIGSEGV | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tristan Santore <tristan.santore> | ||||||||||||||||||||||||
| Component: | mate-file-manager | Assignee: | Dan Mashal <dan.mashal> | ||||||||||||||||||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||
| Version: | 20 | CC: | dan.mashal, raveit65.sun, rdieter, stefano | ||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/6ae4d87f9c4b320cae9b7809f6f290c98570c898 | ||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:7d1297e24fb7f6b017e4c4252ea224a9cca8af7f | ||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||
| Last Closed: | 2014-10-04 14:47:29 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
Tristan Santore
2014-06-08 17:09:47 UTC
Created attachment 903297 [details]
File: backtrace
Created attachment 903298 [details]
File: cgroup
Created attachment 903299 [details]
File: core_backtrace
Created attachment 903300 [details]
File: dso_list
Created attachment 903301 [details]
File: environ
Created attachment 903302 [details]
File: exploitable
Created attachment 903303 [details]
File: limits
Created attachment 903304 [details]
File: maps
Created attachment 903305 [details]
File: open_fds
Created attachment 903306 [details]
File: proc_pid_status
Created attachment 903307 [details]
File: var_log_messages
Can you describe a little more detailed what happend? Did this issue occurs frequently ? Does Caja just crash a lot without reason ? Yes! Which is probably why there are quite a few bugzillas on this. The full back traces should be able to identify the issue, so I am not quite sure what you are asking me, or indeed asking me for. Can you be more specific what you require exactly ? Regards, Tristan (In reply to Tristan Santore from comment #13) > Does Caja just crash a lot without reason ? Yes! Which is probably why there > are quite a few bugzillas on this. > > The full back traces should be able to identify the issue, so I am not quite > sure what you are asking me, or indeed asking me for. Whoow, great theoratical words from someone who only click the button for open a bug report. > > Can you be more specific what you require exactly ? > > Regards, > > Tristan Sorry, without detailed 'step to reproduce' or a short description what you did if the issue ocours i have no chance to forward the issue to upstream. PS: what is so difficult to understand with that question? Can you describe a little more detailed what happend? Did this issue occurs frequently ? I cannot tell you what I did, as I did nothing really, apart from clicking on windows, usually the shell, browser, etc.., which of course has nothing to do with Caja. Caja crashes, is restarted. Maybe this is a heisenbug, because I have reported a few of these, which gives various reasons, most of which were reported by others. I also ticked the, "I do not know what caused this problem", tick box. Maybe the Abrt guys need to amke this more clear in the bugs posted. Might be a good feature request for clarification. Further, looking at the backtrace, it appears it segfaulted, because it was trying to jump to a non-existent memory location. So, I am not sure what else I can put here. I would just file this bug, I am sure upstream can take the attachments and figure this out. The Fedora retracer obviously could process the core dump to get the full backtrace, so that is all that should matter. Further, please do no patronise me or other Fedora Contributors. It is not just clicking one button to report bugs, so if you start to patronise people, they will no longer bother filing bugs. Especially when they have to download the debug headers, which takes loads of discspace, takes time, and if you have a slow connection can take forever! So, one has to be a bit more appreciative that people are helping us out here, even if it seems not so helpful at first. You cannot expect people to report more than a full backtrace, and upstream should be ok with that! Thank you for looking into this and being the apckage co-maintainer for mate. Regards, Tristan Sorry, without 'steps to reproduce' your bug report is useless. Because without that hints nobody else than you can reproduce this issue. Saidly, that you can't provide more informations as an automatic generated backtrace. On my Systems this issue never occours , so i'm not able to provide 'steps to reproduce' for you. For me this is not enough information to fix the issue, in my spare rare time. If you don't agree with me, and i know you don't agree with me, feel free to open a report directly at upstream. https://github.com/mate-desktop/caja Maybe those guys can help you if you only provide a backtrace. regards |