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 1792827

Summary: [abrt] marco: INT_cairo_region_num_rectangles(): marco killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Rajib Chakrabartty <rajib>
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/a508b6c26e6bf0d4ad885753cc5c1bac86c1a0f7
Whiteboard: abrt_hash:8ec5c78e2da44041f64b55e68f043430a91e3b58;VARIANT_ID=matecompiz;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-23 14:00:59 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 Rajib Chakrabartty 2020-01-20 05:21:54 UTC
Description of problem:
Reported by Fedora system during bootup.

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=65c17680ba87417cab8b1402a2db7af8;i=9966c;b=378032929da54753ad690c9a1d0df3e2;m=30dad16a73;t=59c8b284f00db;x=428648293adbd1f8
kernel:         5.4.10-100.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (8 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 repair_display at compositor/compositor-xrender.c:1662
 #7 compositor_idle_cb at compositor/compositor-xrender.c:1672

Potential duplicate: bug 1792624

Comment 1 Rajib Chakrabartty 2020-01-20 05:21:59 UTC
Created attachment 1653810 [details]
File: backtrace

Comment 2 Rajib Chakrabartty 2020-01-20 05:22:00 UTC
Created attachment 1653811 [details]
File: cgroup

Comment 3 Rajib Chakrabartty 2020-01-20 05:22:02 UTC
Created attachment 1653812 [details]
File: core_backtrace

Comment 4 Rajib Chakrabartty 2020-01-20 05:22:04 UTC
Created attachment 1653813 [details]
File: cpuinfo

Comment 5 Rajib Chakrabartty 2020-01-20 05:22:06 UTC
Created attachment 1653814 [details]
File: dso_list

Comment 6 Rajib Chakrabartty 2020-01-20 05:22:08 UTC
Created attachment 1653815 [details]
File: environ

Comment 7 Rajib Chakrabartty 2020-01-20 05:22:10 UTC
Created attachment 1653816 [details]
File: exploitable

Comment 8 Rajib Chakrabartty 2020-01-20 05:22:12 UTC
Created attachment 1653817 [details]
File: limits

Comment 9 Rajib Chakrabartty 2020-01-20 05:22:14 UTC
Created attachment 1653818 [details]
File: maps

Comment 10 Rajib Chakrabartty 2020-01-20 05:22:16 UTC
Created attachment 1653819 [details]
File: mountinfo

Comment 11 Rajib Chakrabartty 2020-01-20 05:22:18 UTC
Created attachment 1653820 [details]
File: open_fds

Comment 12 Rajib Chakrabartty 2020-01-20 05:22:19 UTC
Created attachment 1653821 [details]
File: proc_pid_status

Comment 13 Wolfgang Ulbrich 2020-02-23 14:00:59 UTC

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