Version-Release number of selected component: libreoffice-core-1:6.4.7.2-3.fc32 Additional info: reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1001.slice/user/dbus\x2d:1.2\x2dorg.gnome.Nautilus.slice/dbus-:1.2-org.gnome.Nautilus cmdline: /usr/lib64/libreoffice/program/soffice.bin --impress file:///home/jasmin/Dokumente/AKH/Bewerbung/Pr%C3%A4sentation.odp --splash-pipe=6 crash_function: (anonymous namespace)::signalHandlerFunction executable: /usr/lib64/libreoffice/program/soffice.bin journald_cursor: s=60cfa02ed4544e21817420f67733a0b0;i=1beca;b=cd5f484db26a4d37beff80167457411e;m=584555933f;t=5b8a42957dfbd;x=178cfcd2e134b6b8 kernel: 5.9.15-100.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001
Created attachment 1747750 [details] File: backtrace
Created attachment 1747751 [details] File: core_backtrace
Created attachment 1747752 [details] File: cpuinfo
Created attachment 1747753 [details] File: dso_list
Created attachment 1747754 [details] File: environ
Created attachment 1747755 [details] File: limits
Created attachment 1747756 [details] File: maps
Created attachment 1747757 [details] File: mountinfo
Created attachment 1747758 [details] File: open_fds
Created attachment 1747759 [details] File: proc_pid_status
Created attachment 1747760 [details] File: var_log_messages
pFocusWin must be null at that point
FEDORA-2021-33d29c0f69 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-33d29c0f69
FEDORA-2021-33d29c0f69 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-33d29c0f69` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-33d29c0f69 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-33d29c0f69 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.