Bug 2224240

Summary: [abrt] picom: map_win_start(): picom killed by SIGABRT
Product: [Fedora] Fedora Reporter: Ingo Weiss <iweiss>
Component: picomAssignee: Artem <ego.cordatus>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: ego.cordatus, iweiss
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/64352c13525da324abd4bb75af99537f33e6135
Whiteboard: abrt_hash:dc20edf6607a5e1d84d41db63b9666027b4808ae;VARIANT_ID=;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-28 13:33:27 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: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: dso_list
none
File: backtrace none

Description Ingo Weiss 2023-07-20 08:57:23 UTC 
Version-Release number of selected component:
picom-10.2-2.fc38

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         picom killed by SIGABRT
journald_cursor: s=367b75e4fadc40d1b00f77dda0e02609;i=b35e0d;b=12dfb78706584522a70ef77031b5ffaf;m=9f2b193f22;t=600d06fbb43cc;x=7436d258e49917af
executable:     /usr/bin/picom
cmdline:        picom -CGb --config /home/iweiss/desktopconfig/picom.test.conf
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
rootdir:        /
uid:            1000
kernel:         6.3.8-200.fc38.x86_64
package:        picom-10.2-2.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: map_win_start

Truncated backtrace:
Thread no. 1 (9 frames)
 #6 map_win_start at ../src/win.c:2479
 #7 win_process_update_flags at ../src/win.c:474
 #8 refresh_windows at ../src/picom.c:1385
 #9 handle_pending_updates at ../src/picom.c:1433
 #10 draw_callback_impl.isra.0 at ../src/picom.c:1460
 #11 draw_callback at ../src/picom.c:1550
 #12 ev_invoke_pending at /usr/src/debug/libev-4.33-7.fc38.x86_64/ev.c:3770
 #13 ev_run at /usr/src/debug/libev-4.33-7.fc38.x86_64/ev.c:4190
 #15 session_run at ../src/picom.c:2465
Comment 1 Ingo Weiss 2023-07-20 08:57:27 UTC 
Created attachment 1976673 [details]
File: proc_pid_status
Comment 2 Ingo Weiss 2023-07-20 08:57:29 UTC 
Created attachment 1976674 [details]
File: maps
Comment 3 Ingo Weiss 2023-07-20 08:57:31 UTC 
Created attachment 1976675 [details]
File: limits
Comment 4 Ingo Weiss 2023-07-20 08:57:32 UTC 
Created attachment 1976676 [details]
File: environ
Comment 5 Ingo Weiss 2023-07-20 08:57:34 UTC 
Created attachment 1976677 [details]
File: open_fds
Comment 6 Ingo Weiss 2023-07-20 08:57:36 UTC 
Created attachment 1976678 [details]
File: mountinfo
Comment 7 Ingo Weiss 2023-07-20 08:57:37 UTC 
Created attachment 1976679 [details]
File: os_info
Comment 8 Ingo Weiss 2023-07-20 08:57:39 UTC 
Created attachment 1976680 [details]
File: cpuinfo
Comment 9 Ingo Weiss 2023-07-20 08:57:41 UTC 
Created attachment 1976681 [details]
File: core_backtrace
Comment 10 Ingo Weiss 2023-07-20 08:57:42 UTC 
Created attachment 1976682 [details]
File: dso_list
Comment 11 Ingo Weiss 2023-07-20 08:57:44 UTC 
Created attachment 1976683 [details]
File: backtrace
Comment 12 Aoife Moloney 2024-05-28 13:33:27 UTC 
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.