| Summary: | [abrt] texmaker-1:2.0-1.fc13: Poppler::Document::page: Process /usr/bin/texmaker was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | jacques_legras | ||||
| Component: | texmaker | Assignee: | Deji Akingunola <dakingun> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 13 | CC: | dakingun | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:57665062a1819f58cb6292b205623ea0ad376f02 | ||||||
| Fixed In Version: | texmaker-2.3-1.fc13 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-04-23 20:47:42 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
jacques_legras
2011-01-16 15:35:43 UTC
Created attachment 473716 [details]
File: backtrace
Can you please state what you were doing when this crash occurred? Also can you reliably reproduce the crash? texmaker-2.3-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/texmaker-2.3-1.fc13 Package texmaker-2.3-1.fc13: * should fix your issue, * was pushed to the Fedora 13 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing texmaker-2.3-1.fc13' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/texmaker-2.3-1.fc13 then log in and leave karma (feedback). texmaker-2.3-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |