| Summary: | [abrt] iok-2.1.3-4.fc20: g_bit_lock: Process /usr/bin/iok was killed by signal 11 (SIGSEGV) | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | lnie <lnie> | ||||||||||||||||||||||||
| Component: | iok | Assignee: | Parag Nemade <pnemade> | ||||||||||||||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||
| Version: | 20 | CC: | i18n-bugs, lnie, pnemade | ||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/c70ddab5e90724093d369edda1968db8a0f0d006 | ||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:b8237f62ef57c9292073a1c0e2e37a7b32cc2510 | ||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||
| Clone Of: | |||||||||||||||||||||||||||
| : | 1049974 (view as bug list) | Environment: | |||||||||||||||||||||||||
| Last Closed: | 2014-01-14 06:09:09 UTC | Type: | --- | ||||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||
|
Description
lnie
2013-12-11 04:23:45 UTC
Created attachment 835108 [details]
File: backtrace
Created attachment 835109 [details]
File: cgroup
Created attachment 835110 [details]
File: core_backtrace
Created attachment 835111 [details]
File: dso_list
Created attachment 835112 [details]
File: environ
Created attachment 835113 [details]
File: exploitable
Created attachment 835114 [details]
File: limits
Created attachment 835115 [details]
File: maps
Created attachment 835116 [details]
File: open_fds
Created attachment 835117 [details]
File: proc_pid_status
Created attachment 835118 [details]
File: var_log_messages
so how can I reproduce this? (In reply to Parag from comment #12) > so how can I reproduce this? Just install the same version iok ,then run iok command on a terminal.:) unable to reproduce on newly installed F20 Final TC5. I installed iok and able to run in fine. That's weird ,the tested system installed on the VM is also F20 Final TC5 Gnome. er,you tested it on VM too? yes I have f20 Final TC5 VM installed on Monday. It's really weird then,maybe the only difference is that I have installed several other packages.I think I should figure out that iok crashed every time I run iok command on a terminal I tested it on fresh installed x86_64 systems just now, saw this bug on both Gnome and KDE system,yours is x86_64 system too?If so, then I really have no idea why iok refuse to work on my systems Okay. I will try again with fresh installation. I have x86_64 machine to test in VM. (In reply to Parag from comment #19) > Okay. I will try again with fresh installation. I have x86_64 machine to > test in VM. If you tested it with x86_64 machine,then you need not test it again. I tested it on fresh installed system(#comment18) because you said in #comment14 that you tested in newly installed system,while as I said in #comment17,my tested system has some other packages installed. Thanks but to make sure myself again that this bug is not reproducible I installed F20 Final TC5 DVD installation freshly in VM. This is x86_64 installation. Then I installed iok as the first package on this system and just started it from gnome-terminal as "iok" and used its functionality and found no crash. I still consider this as a not bug for me. |