Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1794344

Summary: [abrt] marco: meta_frame_get_frame_bounds(): marco killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Peter Draganov <pdraganov>
Component: marcoAssignee: Wolfgang Ulbrich <fedora>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8dbf6d4d1a5e84fc21122562678de13c03955864
Whiteboard: abrt_hash:549dac6dc0b160d1819b7f5da3c6922e12a7ee81;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-23 13:16:37 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 Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Peter Draganov 2020-01-23 10:51:55 UTC
Description of problem:
LibreOffice hung and I selected Force Quit

Version-Release number of selected component:
marco-1.22.4-1.fc30

Additional info:
reporter:       libreport-2.11.3
backtrace_rating: 3
cmdline:        marco
crash_function: meta_frame_get_frame_bounds
executable:     /usr/bin/marco
journald_cursor: s=68bedf09efe1467d98d171816123614f;i=549fc;b=9823f57aae314436894b9d05b055c9ff;m=8b93bd4790;t=59ccc4310bdff;x=329447a730964c96
kernel:         5.4.10-100.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 meta_frame_get_frame_bounds at core/frame.c:411
 #1 meta_window_get_frame_bounds at core/window.c:8866
 #2 border_size at compositor/compositor-xrender.c:1154
 #3 paint_windows at compositor/compositor-xrender.c:1420
 #4 paint_all at compositor/compositor-xrender.c:1593
 #5 repair_screen at compositor/compositor-xrender.c:1620
 #6 xrender_present_complete at compositor/compositor-xrender.c:2719
 #7 process_generic at compositor/compositor-xrender.c:2743
 #8 xrender_process_event at compositor/compositor-xrender.c:3113
 #9 event_callback at core/display.c:2614

Comment 1 Peter Draganov 2020-01-23 10:51:59 UTC
Created attachment 1654810 [details]
File: backtrace

Comment 2 Peter Draganov 2020-01-23 10:52:01 UTC
Created attachment 1654811 [details]
File: cgroup

Comment 3 Peter Draganov 2020-01-23 10:52:03 UTC
Created attachment 1654812 [details]
File: core_backtrace

Comment 4 Peter Draganov 2020-01-23 10:52:04 UTC
Created attachment 1654813 [details]
File: cpuinfo

Comment 5 Peter Draganov 2020-01-23 10:52:06 UTC
Created attachment 1654814 [details]
File: dso_list

Comment 6 Peter Draganov 2020-01-23 10:52:07 UTC
Created attachment 1654815 [details]
File: environ

Comment 7 Peter Draganov 2020-01-23 10:52:08 UTC
Created attachment 1654816 [details]
File: exploitable

Comment 8 Peter Draganov 2020-01-23 10:52:10 UTC
Created attachment 1654817 [details]
File: limits

Comment 9 Peter Draganov 2020-01-23 10:52:13 UTC
Created attachment 1654818 [details]
File: maps

Comment 10 Peter Draganov 2020-01-23 10:52:14 UTC
Created attachment 1654819 [details]
File: mountinfo

Comment 11 Peter Draganov 2020-01-23 10:52:15 UTC
Created attachment 1654820 [details]
File: open_fds

Comment 12 Peter Draganov 2020-01-23 10:52:17 UTC
Created attachment 1654821 [details]
File: proc_pid_status

Comment 13 Wolfgang Ulbrich 2020-02-23 13:16:37 UTC

*** This bug has been marked as a duplicate of bug 1793524 ***