Bug 838586
Summary: | [abrt] libreoffice-core-3.5.4.2-4.fc17: gdk_screen_get_monitor_geometry killed by signal 11 (SIGSEGV) | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Inglis <ainglis> | ||||||||||||
Component: | libreoffice | Assignee: | Caolan McNamara <caolanm> | ||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 17 | CC: | caolanm, dtardon, erack, ltinkl, mstahl, sbergman | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | x86_64 | ||||||||||||||
OS: | Unspecified | ||||||||||||||
Whiteboard: | abrt_hash:e1133e8fd81a128356614f2207f23a46b2fe2cf2 | ||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2012-07-19 23:03:34 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
Adam Inglis
2012-07-09 14:31:14 UTC
Created attachment 597082 [details]
File: maps
Created attachment 597083 [details]
File: dso_list
Created attachment 597084 [details]
File: build_ids
Created attachment 597085 [details]
File: backtrace
Created attachment 597086 [details]
File: core_backtrace
pScreen = getScreenMonitorFromIdx (nScreen, nMonitor);
if (!pScreen)
return Rectangle();
> gdk_screen_get_monitor_geometry (pScreen, nMonitor, &aRect);
doesn't look obviously wrong. Does this happen always ?, or were there specific circumstances or interesting multi-head configuration setup ?
it did happen always, I have upgraded to 3.5.5.3-2.fc17 and it now loads the dialog without any issue great. |