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 1787951

Summary: [abrt] marco: INT_cairo_region_num_rectangles(): marco killed by SIGSEGV
Product: [Fedora] Fedora Reporter: John <handyj>
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, rajib
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/6d1e3f4d0a4a36f57611be811e092f1b5221918b
Whiteboard: abrt_hash:8ec5c78e2da44041f64b55e68f043430a91e3b58;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-23 14:06:45 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 John 2020-01-05 20:04:19 UTC 
Description of problem:
I'm not sure how this error happened. It just popped up, not sure how to replicate. 

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

Additional info:
reporter:       libreport-2.11.3
backtrace_rating: 4
cmdline:        marco
crash_function: INT_cairo_region_num_rectangles
executable:     /usr/bin/marco
journald_cursor: s=f9933999e7ef4d689e129f84b2d19219;i=8e03;b=23b276952ac44561ba1c7a1e15e8ed56;m=1ff56c58ed;t=59b5571e75633;x=87d4c3dfc2f78941
kernel:         5.3.16-200.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 INT_cairo_region_num_rectangles at cairo-region.c:451
 #1 cairo_region_to_xserver_region at compositor/compositor-xrender.c:607
 #2 border_size at compositor/compositor-xrender.c:1157
 #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 John 2020-01-05 20:04:21 UTC 
Created attachment 1649997 [details]
File: backtrace
Comment 2 John 2020-01-05 20:04:22 UTC 
Created attachment 1649998 [details]
File: cgroup
Comment 3 John 2020-01-05 20:04:22 UTC 
Created attachment 1649999 [details]
File: core_backtrace
Comment 4 John 2020-01-05 20:04:23 UTC 
Created attachment 1650000 [details]
File: cpuinfo
Comment 5 John 2020-01-05 20:04:25 UTC 
Created attachment 1650001 [details]
File: dso_list
Comment 6 John 2020-01-05 20:04:25 UTC 
Created attachment 1650002 [details]
File: environ
Comment 7 John 2020-01-05 20:04:27 UTC 
Created attachment 1650003 [details]
File: exploitable
Comment 8 John 2020-01-05 20:04:28 UTC 
Created attachment 1650004 [details]
File: limits
Comment 9 John 2020-01-05 20:04:29 UTC 
Created attachment 1650005 [details]
File: maps
Comment 10 John 2020-01-05 20:04:29 UTC 
Created attachment 1650006 [details]
File: mountinfo
Comment 11 John 2020-01-05 20:04:30 UTC 
Created attachment 1650007 [details]
File: open_fds
Comment 12 John 2020-01-05 20:04:31 UTC 
Created attachment 1650008 [details]
File: proc_pid_status
Comment 13 Wolfgang Ulbrich 2020-02-23 14:00:59 UTC 
*** Bug 1792827 has been marked as a duplicate of this bug. ***
Comment 14 Wolfgang Ulbrich 2020-02-23 14:06:45 UTC 
Same report exists in f31.

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