Bug 1656579 - [abrt] xfdesktop: _cairo_mempool_init(): xfdesktop killed by SIGABRT
Summary: [abrt] xfdesktop: _cairo_mempool_init(): xfdesktop killed by SIGABRT
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xfdesktop
Version: 29
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:fb7c6a2bc2fbdbe32c469990b17...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-05 18:43 UTC by Scott Cohen
Modified: 2019-06-18 03:45 UTC (History)
2 users (show)

Fixed In Version: xfdesktop-4.13.4-1.fc30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-18 00:55:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (62.00 KB, text/plain)
2018-12-05 18:43 UTC, Scott Cohen
no flags Details
File: cgroup (341 bytes, text/plain)
2018-12-05 18:43 UTC, Scott Cohen
no flags Details
File: core_backtrace (25.25 KB, text/plain)
2018-12-05 18:43 UTC, Scott Cohen
no flags Details
File: cpuinfo (1.25 KB, text/plain)
2018-12-05 18:43 UTC, Scott Cohen
no flags Details
File: dso_list (8.32 KB, text/plain)
2018-12-05 18:43 UTC, Scott Cohen
no flags Details
File: environ (4.10 KB, text/plain)
2018-12-05 18:43 UTC, Scott Cohen
no flags Details
File: limits (1.29 KB, text/plain)
2018-12-05 18:43 UTC, Scott Cohen
no flags Details
File: maps (50.65 KB, text/plain)
2018-12-05 18:43 UTC, Scott Cohen
no flags Details
File: mountinfo (3.99 KB, text/plain)
2018-12-05 18:43 UTC, Scott Cohen
no flags Details
File: open_fds (1.13 KB, text/plain)
2018-12-05 18:43 UTC, Scott Cohen
no flags Details
File: proc_pid_status (1.34 KB, text/plain)
2018-12-05 18:43 UTC, Scott Cohen
no flags Details

Description Scott Cohen 2018-12-05 18:43:07 UTC
Version-Release number of selected component:
xfdesktop-4.13.2-20.fc29

Additional info:
reporter:       libreport-2.9.6
backtrace_rating: 4
cmdline:        xfdesktop --display :0.0 --sm-client-id 2a49acab3-495b-4afa-a738-d371bfb2f94b
crash_function: _cairo_mempool_init
executable:     /usr/bin/xfdesktop
journald_cursor: s=2682d9519b3c4e818e5621611d2cad7c;i=3c523;b=23b95394d5024303947f143c976b151e;m=166264fa418;t=57c38461072bf;x=baf9d9a31cb6f255
kernel:         4.18.18-300.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 Scott Cohen 2018-12-05 18:43:11 UTC
Created attachment 1511865 [details]
File: backtrace

Comment 2 Scott Cohen 2018-12-05 18:43:12 UTC
Created attachment 1511866 [details]
File: cgroup

Comment 3 Scott Cohen 2018-12-05 18:43:13 UTC
Created attachment 1511867 [details]
File: core_backtrace

Comment 4 Scott Cohen 2018-12-05 18:43:14 UTC
Created attachment 1511868 [details]
File: cpuinfo

Comment 5 Scott Cohen 2018-12-05 18:43:14 UTC
Created attachment 1511869 [details]
File: dso_list

Comment 6 Scott Cohen 2018-12-05 18:43:15 UTC
Created attachment 1511870 [details]
File: environ

Comment 7 Scott Cohen 2018-12-05 18:43:16 UTC
Created attachment 1511871 [details]
File: limits

Comment 8 Scott Cohen 2018-12-05 18:43:17 UTC
Created attachment 1511872 [details]
File: maps

Comment 9 Scott Cohen 2018-12-05 18:43:18 UTC
Created attachment 1511873 [details]
File: mountinfo

Comment 10 Scott Cohen 2018-12-05 18:43:18 UTC
Created attachment 1511874 [details]
File: open_fds

Comment 11 Scott Cohen 2018-12-05 18:43:19 UTC
Created attachment 1511875 [details]
File: proc_pid_status

Comment 12 Scott Cohen 2018-12-25 05:03:41 UTC
This bug was detected at 8:28 PM PST 11/24/2018 and bug 1650586 was detected at 8:33 AM PST 11/24/2018. I just thought this close to 12 hours difference in detection was interesting.

Comment 13 Scott Cohen 2019-01-09 00:28:58 UTC
Similar problem has been detected:

I logged in via xscreensaver a couple minutes before this and there was a lot of swapping going on. Other than that, I don't know what caused this.

reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        xfdesktop --display :0.0 --sm-client-id 240f7b40e-8779-43ac-b3be-fb414928b633
crash_function: _cairo_mempool_init
executable:     /usr/bin/xfdesktop
journald_cursor: s=4fc33c98ac2f432e895d7159936df6f7;i=bbc6;b=ed7d45e6519145199be6cdcc67d71074;m=a898ef4dd8;t=57efb69414d90;x=4d252cedc749e8c9
kernel:         4.19.10-300.fc29.x86_64
package:        xfdesktop-4.13.2-20.fc29
reason:         xfdesktop killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Scott Cohen 2019-02-04 00:13:34 UTC
Similar problem has been detected:

I just moved my mouse and logged into xscreensaver. I also found that my multi-monitor display settings had been reset to default positions as viewed from xfce4-display-settings.

reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        xfdesktop --display :0.0 --sm-client-id 294659ae1-e268-44b2-beeb-b797419385c9
crash_function: _cairo_mempool_init
executable:     /usr/bin/xfdesktop
journald_cursor: s=5cee89a16fe74a1d9b20ea325ac2e5fe;i=2630e;b=d7811a910f4245afb64fe2136cc23b50;m=1685517478;t=58105fc6a8537;x=91144d5fd90022b8
kernel:         4.20.4-200.fc29.x86_64
package:        xfdesktop-4.13.2-20.fc29
reason:         xfdesktop killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Scott Cohen 2019-02-10 20:46:02 UTC
Similar problem has been detected:

This happened after I turned on my primary monitor. I have two monitors, one that shouldn't be primary and what that should. I turned on the non primary one first and then turned on the one that should be primary. A black screen happened and then my multi-moniter configuration reset so my primary display went to the left of my non primary display when it should go to the right. I'm not sure if the moniter that I turned on which was supposed to be primary was actually enabled as primary when I turned it on because at this point, I don't know whether primary monitor settings are being reset before or after turning both monitors on.

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        xfdesktop --display :0.0 --sm-client-id 294659ae1-e268-44b2-beeb-b797419385c9
crash_function: _cairo_mempool_init
executable:     /usr/bin/xfdesktop
journald_cursor: s=5cee89a16fe74a1d9b20ea325ac2e5fe;i=3372f;b=9538143a78724ab4928672b2c8a1fcd6;m=12512156cf;t=581901b6a34f3;x=2500f6d940e3583e
kernel:         4.20.6-200.fc29.x86_64
package:        xfdesktop-4.13.2-20.fc29
reason:         xfdesktop killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 16 Scott Cohen 2019-02-11 16:34:26 UTC
Similar problem has been detected:

This occurred after I turned on both of my monitors, but I'm not sure if I logged in via xscreensaver when this happened.

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        xfdesktop --display :0.0 --sm-client-id 294659ae1-e268-44b2-beeb-b797419385c9
crash_function: _cairo_mempool_init
executable:     /usr/bin/xfdesktop
journald_cursor: s=5cee89a16fe74a1d9b20ea325ac2e5fe;i=358cd;b=e34a212238ca432394adc826935e6c18;m=7f5d9ccbe;t=581a06cdc5f30;x=b10b812b58b48ca9
kernel:         4.20.6-200.fc29.x86_64
package:        xfdesktop-4.13.2-20.fc29
reason:         xfdesktop killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 17 Scott Cohen 2019-02-20 16:57:56 UTC
Similar problem has been detected:

My screen was off due to xscreensaver, I switched to a different input on my primary monitor and then switched back to my primary input. I then logged in and found that my multi-moniter display settings had changed and mirroring the resolution on all my monitors was defaulting to my non primary display, but not resizing the image accordingly and was leaving a black border around where the resolution of my non primary screen could have fit on the primary. I then saw in xfce4-display-settings that "Mirror displays" had a dash in it. When I went to check the box and then unchecked it, my multi-monitor configuration reset to default positions.  

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        xfdesktop --display :0.0 --sm-client-id 294659ae1-e268-44b2-beeb-b797419385c9
crash_function: _cairo_mempool_init
executable:     /usr/bin/xfdesktop
journald_cursor: s=dddf5dc168fd4890a7e50216558b4952;i=6b13;b=6e7266f9def14ce2a5f9a465d832de08;m=8e112bd5e9;t=582561aff2ce7;x=c163258e0c0d8cb
kernel:         4.20.6-200.fc29.x86_64
package:        xfdesktop-4.13.2-20.fc29
reason:         xfdesktop killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 18 Scott Cohen 2019-03-04 22:13:17 UTC
Similar problem has been detected:

A couple minutes after I had logged in via xscreensaver and had changed my two monitor configuration back to the way it was via xfce4-display-settings as it had reset and was moving and interacting with windows. I need to make clear that the error occurred a couple minutes or so after I changed the display configuration back to the way it should be. 

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        xfdesktop --display :0.0 --sm-client-id 294659ae1-e268-44b2-beeb-b797419385c9
crash_function: _cairo_mempool_init
executable:     /usr/bin/xfdesktop
journald_cursor: s=4b8cb791631c4c979cec674a11d6819a;i=81b1;b=f10067df16884df39cf0f778bd2e68ef;m=c88a9f0c9;t=5834b89f29340;x=f8aed0472aedfc59
kernel:         4.20.13-200.fc29.x86_64
package:        xfdesktop-4.13.2-20.fc29
reason:         xfdesktop killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 19 Fedora Update System 2019-05-18 13:51:06 UTC
xfdesktop-4.13.4-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-40d6024781

Comment 20 Fedora Update System 2019-05-19 00:51:21 UTC
xfdesktop-4.13.4-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-40d6024781

Comment 21 Fedora Update System 2019-06-18 00:55:02 UTC
xfdesktop-4.13.4-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 22 Fedora Update System 2019-06-18 03:45:55 UTC
xfdesktop-4.13.4-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.