Description of problem: I don't know what the problem even is/was. I just installed Fedora 32. I rebooted several times since I was trying to set up my fstab. And the 'Oops' message appeared. The only potentially useful information I could provide is that I created an encrypted partition with btrfs file system and tried to make the 2 of its subvolumes mounted via crypttab and fstab at /home/me and /tmp. I succeded eventually but had problems with permissions for my home directory (the mounted one). Whether this was related to the problem being reported I don't know. I haven't seen any noticeable issues. Version-Release number of selected component: libreport-gtk-2.12.0-3.fc32 Additional info: reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/dbus\x2d:1.2\x2dorg.freedesktop.problems.applet.slice/dbus-:1.2-org.freedesktop.problems.applet cmdline: report-gtk -- /var/spool/abrt/ccpp-2020-09-28-22:02:14.358673-2011 crash_function: g_type_check_instance_cast executable: /usr/bin/report-gtk journald_cursor: s=e228a20022cc410e8c8b02a682d02885;i=3e07;b=dc0856be3f17474fbf3642d49525c725;m=16d0e3c7;t=5b064619ab403;x=3d63731362012959 kernel: 5.6.6-300.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 g_type_check_instance_cast at ../gobject/gtype.c:4053 #1 show_error_as_msgbox at wizard.c:365 #2 log_handler at logging.c:146 #3 log_wrapper at logging.c:172 #4 internal_aug_error_msg at configuration_files.c:135 #5 libreport_save_conf_file at configuration_files.c:479 Potential duplicate: bug 1515048
Created attachment 1717324 [details] File: backtrace
Created attachment 1717325 [details] File: core_backtrace
Created attachment 1717326 [details] File: cpuinfo
Created attachment 1717327 [details] File: dso_list
Created attachment 1717328 [details] File: environ
Created attachment 1717329 [details] File: exploitable
Created attachment 1717330 [details] File: limits
Created attachment 1717331 [details] File: maps
Created attachment 1717332 [details] File: mountinfo
Created attachment 1717333 [details] File: open_fds
Created attachment 1717334 [details] File: proc_pid_status
A patch has been proposed upstream: https://github.com/abrt/libreport/pull/675
FEDORA-2020-ae55f49266 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ae55f49266
FEDORA-2020-efe7a7d732 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-efe7a7d732
FEDORA-2020-efe7a7d732 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-efe7a7d732` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-efe7a7d732 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-c39a7b655b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c39a7b655b
FEDORA-2020-c39a7b655b has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c39a7b655b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c39a7b655b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I installed update https://bodhi.fedoraproject.org/updates/FEDORA-2020-c39a7b655b . I would like not to leave a response on bodhi.fedoraproject, since I ain't qualified enough to even understand what the problem was and be 100% if it's gone. But I think that the update's worked well, since I used to have errors reported in the Problem Reporting window. But since I installed the update they are all gone.
FEDORA-2020-c39a7b655b has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.