Version-Release number of selected component: xdg-desktop-portal-gtk-1.7.0-1.fc32 Additional info: reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/xdg-desktop-portal-gtk.service cmdline: /usr/libexec/xdg-desktop-portal-gtk crash_function: g_hash_table_lookup_node executable: /usr/libexec/xdg-desktop-portal-gtk journald_cursor: s=e8ec058f595347379a13ecdf0cbbdaf0;i=3e0d;b=87295c779b8e4606a3760117c642fa7b;m=222bfe67a;t=5a1ad722f1d69;x=f3d4583e2ba8201d kernel: 5.6.0-0.rc7.git0.2.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1770603
Created attachment 1674020 [details] File: backtrace
Created attachment 1674021 [details] File: core_backtrace
Created attachment 1674022 [details] File: cpuinfo
Created attachment 1674023 [details] File: dso_list
Created attachment 1674024 [details] File: environ
Created attachment 1674025 [details] File: exploitable
Created attachment 1674026 [details] File: limits
Created attachment 1674027 [details] File: maps
Created attachment 1674028 [details] File: mountinfo
Created attachment 1674029 [details] File: open_fds
Created attachment 1674030 [details] File: proc_pid_status
Similar problem has been detected: audio stopped working after returning from sleep, relog fixed it and after relog got this bug report reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/xdg-desktop-portal-gtk.service cmdline: /usr/libexec/xdg-desktop-portal-gtk crash_function: g_hash_table_lookup_node executable: /usr/libexec/xdg-desktop-portal-gtk journald_cursor: s=e8ec058f595347379a13ecdf0cbbdaf0;i=26f22;b=ed32436ca6294242865230d948edcc12;m=45035d6ae;t=5a1d7cc29ebe0;x=5eefa9c74a8d05b2 kernel: 5.6.0-0.rc7.git0.2.fc32.x86_64 package: xdg-desktop-portal-gtk-1.7.0-1.fc32 reason: xdg-desktop-portal-gtk killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: While sharing the screen with Chrome the system got hang up and it looked like the display was cycling through three buffers in a loop reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/xdg-desktop-portal-gtk.service cmdline: /usr/libexec/xdg-desktop-portal-gtk crash_function: g_hash_table_lookup_node executable: /usr/libexec/xdg-desktop-portal-gtk journald_cursor: s=7f481a274eac48c48fd73ad1079e13b7;i=29981;b=545561cfbecd4e9e814d792478662aff;m=75f8b50461;t=5ba39b328cb8b;x=b7c16995ec275a1d kernel: 5.11.0-0.rc2.114.fc34.x86_64 package: xdg-desktop-portal-gtk-1.8.0-1.fc32 reason: xdg-desktop-portal-gtk killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000 xsession_errors:
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.