Bug 862108
Summary: | [abrt] nepomuk-core-4.9.1-1.fc17: QObject::~QObject: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adrian Anghel <adianghel> | ||||||||||||||||
Component: | nepomuk-core | Assignee: | Jaroslav Reznik <jreznik> | ||||||||||||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||
Priority: | unspecified | ||||||||||||||||||
Version: | 17 | CC: | jreznik, kevin, ltinkl, rdieter, rnovacek, than | ||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||
Target Release: | --- | ||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||
Whiteboard: | abrt_hash:7525e063be31234f975053d57d6b2ebd1ef0f77c | ||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||
Last Closed: | 2012-10-02 00:11:04 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
Adrian Anghel
2012-10-01 22:20:41 UTC
Created attachment 620036 [details]
File: backtrace
Created attachment 620037 [details]
File: open_fds
Created attachment 620038 [details]
File: environ
Created attachment 620039 [details]
File: build_ids
Created attachment 620040 [details]
File: cgroup
Created attachment 620041 [details]
File: maps
Created attachment 620042 [details]
File: limits
Sorry, but there is really no way we can fix the bug with this "backtrace". It is most likely a duplicate of bug #860025 and/or bug #861517 (which have more useful backtraces), but there's no way to tell for sure. |