Description of problem: the application failed to start on fedora rawhide Version-Release number of selected component: openbox-3.6.1-17.fc34 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1003.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-028587bc-9d71-4615-838d-85aee81ea034.scope cmdline: openbox crash_function: __libc_connect executable: /usr/bin/openbox journald_cursor: s=c85bd028d0a04acc95e7eb2d5a2b6875;i=175cd;b=f33603ce2b08462b8478f04c137b04a0;m=38ae1a5b7;t=5c56c39faeefa;x=1dcb1249328098f9 kernel: 5.13.0-0.rc6.20210617git70585216fe77.48.fc35.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1003 Truncated backtrace: Thread no. 1 (8 frames) #0 __libc_connect at ../sysdeps/unix/sysv/linux/connect.c:26 #1 _xcb_open_abstract at /usr/src/debug/libxcb-1.13.1-7.fc34.x86_64/src/xcb_util.c:479 #2 _xcb_open at /usr/src/debug/libxcb-1.13.1-7.fc34.x86_64/src/xcb_util.c:291 #3 xcb_connect_to_display_with_auth_info at /usr/src/debug/libxcb-1.13.1-7.fc34.x86_64/src/xcb_util.c:515 #4 xcb_connect at /usr/src/debug/libxcb-1.13.1-7.fc34.x86_64/src/xcb_util.c:489 #5 _XConnectXCB at /usr/src/debug/libX11-1.7.2-1.fc35.x86_64/src/xcb_disp.c:78 #6 XOpenDisplay at /usr/src/debug/libX11-1.7.2-1.fc35.x86_64/src/OpenDis.c:129 #7 obt_display_open at obt/display.c:64
Created attachment 1799467 [details] File: backtrace
Created attachment 1799468 [details] File: core_backtrace
Created attachment 1799469 [details] File: cpuinfo
Created attachment 1799470 [details] File: dso_list
Created attachment 1799471 [details] File: environ
Created attachment 1799472 [details] File: limits
Created attachment 1799473 [details] File: maps
Created attachment 1799474 [details] File: mountinfo
Created attachment 1799475 [details] File: open_fds
Created attachment 1799476 [details] File: proc_pid_status
SIGABRT coming from the connect() system call is very odd. How was openbox started? Can you reproduce this problem?
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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.