Created attachment 1865821 [details] journal Description of problem: Do a default installation with Fedora-Workstation-Live-x86_64-36_Beta-1.1.iso, boot into the newly installed system,found there is a crash,though no abrt warning message pop up. Version-Release number of selected component (if applicable): xdg-desktop-portal-1.12.1-2.fc36.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Proposed as a Blocker for 36-final by Fedora user lnie using the blocker tracking app because: This is a violation of the criteria: There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop.
Is this the same crash as https://bugzilla.redhat.com/show_bug.cgi?id=2054594 ? Can you try and get a full backtrace from abrt or coredumpctl? Thanks!
Discussed during the 2022-03-14 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Final)" was made as this doesn't seem to violate the criterion (there has to be a graphical notification of the crash for that), plus others do not seem to be able to reproduce it. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-14/f36-blocker-review.2022-03-14-16.01.txt
(In reply to Adam Williamson from comment #3) > Is this the same crash as > https://bugzilla.redhat.com/show_bug.cgi?id=2054594 ? Can you try and get a > full backtrace from abrt or coredumpctl? Thanks! Not sure how I missed this comment,they seems like the same bug, tough this crash will happen every time I login the newly installed system,while that crash is happened when I'm trying to setup a google/microsoft online account.
Didn't see this crash anymore on the system installed with Fedora-Workstation-Live-x86_64-36_Beta-1.4.iso
(In reply to Adam Williamson from comment #3) > Is this the same crash as > https://bugzilla.redhat.com/show_bug.cgi?id=2054594 ? Can you try and get a > full backtrace from abrt or coredumpctl? Thanks! I think so, yes, which makes this a duplicate of bug 2036518 I do see this possibly unrelated xdg-desktop-portal crash, but let's ignore that for a moment: Stack trace of thread 1452: #0 0x00007f3cb0a51e5a fuse_mount_fusermount.cold (libfuse.so.2 + 0x9e5a) #1 0x00007f3cb0a664cd fuse_mount_compat25 (libfuse.so.2 + 0x1e4cd) #2 0x00007f3cb0a6899b fuse_mount_common (libfuse.so.2 + 0x2099b) #3 0x000055d712aff995 on_name_acquired (xdg-document-portal + 0x19995) #4 0x00007f3cb0d2f8b4 do_call.lto_priv.0 (libgio-2.0.so.0 + 0x10a8b4) #5 0x00007f3cb0d2fad8 on_name_lost_or_acquired (libgio-2.0.so.0 + 0x10aad8) #6 0x00007f3cb0d29fef emit_signal_instance_in_idle_cb (libgio-2.0.so.0 + 0x104fef) #7 0x00007f3cb0adb4ab g_idle_dispatch (libglib-2.0.so.0 + 0x514ab) #8 0x00007f3cb0adefaf g_main_context_dispatch (libglib-2.0.so.0 + 0x54faf) #9 0x00007f3cb0b34228 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xaa228) #10 0x00007f3cb0ade6cf g_main_loop_run (libglib-2.0.so.0 + 0x546cf) #11 0x000055d712af701e main (xdg-document-portal + 0x1101e) #12 0x00007f3cb0853590 __libc_start_call_main (libc.so.6 + 0x2d590) #13 0x00007f3cb0853649 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2d649) #14 0x000055d712af72c5 _start (xdg-document-portal + 0x112c5)
*** This bug has been marked as a duplicate of bug 2036518 ***