| Summary: | [abrt] SfxHelp::GetHelpText killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | foxsite | ||||
| Component: | openoffice.org | Assignee: | Caolan McNamara <caolanm> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | caolanm, dtardon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:351c28ae721754d3a949d92a233f08c827d4d50f | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-02-22 08:48:36 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
foxsite
2011-02-13 16:45:03 UTC
Created attachment 478492 [details]
File: backtrace
Odd, looks like a crash in pulling the help tip out for a menu entry, rather than anything to do with printing. Are you able to reproduce this ? Something like this was triggered by bug 204920 long ago, but it can't be the same problem anymore. I don't reproduce the bug, don't know exactly how it happened. maybe when I click on the border of a table to modify it just after printing one other document. I can't reproduce. SfxHelp::GetHelpText is called not only for menus, but for tooltips as well; the easiest way to trigger the call is by moving the mouse over a toolbar item. No crash here, though :( Anyway, I bet this happened at line 528 of sfx2/source/appl/sfxhelp.cxx (i.e., xCont->getByName( aModuleIdentifier )), but it gets much harder to guess the path through configmgr :) We can avoid this particular crash by applying patches from fdo#31716 and fdo#33088, but I'm not sure how much that helps. If the crash was caused by corrupted configuration, it would just happen somewhere else... not reproducible :( |