Created attachment 1861173 [details] journal Description of problem: Do a default installation with Fedora-Workstation-Live-x86_64-36-20220214.n.1.iso,boot into the newly installed system,gnome-initial-setup just quit if you try to set up a google/microsoft online account(screencast1),you have to reboot the system and skip that step ,you can setup it successfully later,but you will see a pop crash warning(screencast2) then. 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: If an initial setup utility is run or intended to be run after the first boot of the installed system, then it must start successfully and each page or panel of the initial setup utility should withstand a basic functionality test
Was not able to reproduce with Workstation Live 20220218.n.0 compose[0] in a VM. [0] - https://kojipkgs.fedoraproject.org/compose/branched/Fedora-36-20220218.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-36-20220218.n.0.iso
Checked with Fedora-Workstation-Live-x86_64-36-20220218.n.0.iso,I can setup an online account successfully during g-i-s now,but I still see the crash(screencast2) when I try to setup a google/microsoft online account after g-i-s. Seems violate the criteria: All applications that can be launched using the standard graphical mechanism after a default installation of Fedora Workstation on the x86_64 architecture must start successfully and withstand a basic functionality test.
I do not know whether this is somehow connected, but I experienced issues with creating a Google account as well on freshly installed Fedora 36. I am not experiencing crashes, but when I choose my email, put it down and hit Continue, I am receiving an error message about the browser not being "safe enough" and that I should use an updated version of the browser. Repeating the process for several times resulted in the account being finally added.
Testing with the Workstation Live 20220222.n.1 compose[0] I can confirm I see an abrt message when adding a Microsoft account through gnome-control-panel (not during GIS). The account appears to be added successfully however. I had no issues with Google or Nextcloud. [0] - https://kojipkgs.fedoraproject.org/compose/branched/Fedora-36-20220222.n.1/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-36-20220222.n.1.iso
Discussed during the 2022-02-28 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Final)" was made as we agreed this would be a blocker issue if it were clearly reproducible, but so far other testers have not been able to reproduce it. We can reconsider this decision if we are able to pin the issue down more precisely and it still seems concerning. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-28/f36-blocker-review.2022-02-28-17.00.txt
Looking at the attached screencasts, this doesn't seem related to xdg-desktop-portal at all. I better bet is gnome-online-accounts.
(In reply to Debarshi Ray from comment #10) > Looking at the attached screencasts, this doesn't seem related to > xdg-desktop-portal at all. I better bet is gnome-online-accounts. Ok, I was wrong. The attached journal entries are full of this xdg-desktop-portal crash: Stack trace of thread 3102: #0 0x00007f34209e6dc9 map_pid_if_needed (xdg-desktop-portal + 0x31dc9) #1 0x00007f34209ecc6e handle_make_thread_realtime_with_pid (xdg-desktop-portal + 0x37c6e) #2 0x00007f3420233746 ffi_call_unix64 (libffi.so.8 + 0x7746) #3 0x00007f34202304d2 ffi_call_int.lto_priv.0 (libffi.so.8 + 0x44d2) #4 0x00007f3420645a43 g_cclosure_marshal_generic (libgobject-2.0.so.0 + 0x19a43) #5 0x00007f342063fd30 g_closure_invoke (libgobject-2.0.so.0 + 0x13d30) #6 0x00007f3420669f65 signal_emit_unlocked_R.isra.0 (libgobject-2.0.so.0 + 0x3df65) #7 0x00007f3420a1622b _xdp_realtime_skeleton_handle_method_call (xdg-desktop-portal + 0x6122b) #8 0x00007f34207ab89b dispatch_in_thread_func (libgio-2.0.so.0 + 0x12389b) #9 0x00007f34207398e3 g_task_thread_pool_thread (libgio-2.0.so.0 + 0xb18e3) #10 0x00007f3420571d22 g_thread_pool_thread_proxy.lto_priv.0 (libglib-2.0.so.0 + 0x81d22) #11 0x00007f342056f322 g_thread_proxy (libglib-2.0.so.0 + 0x7f322) #12 0x00007f342035d0b7 start_thread (libc.so.6 + 0x910b7) #13 0x00007f34203e2800 __clone3 (libc.so.6 + 0x116800) I see that you had xdg-desktop-portal-1.12.1-2.fc36.x86_64 when you experienced this problem, and the above crash is fixed in xdg-desktop-portal-1.12.3-1.fc36.x86_64. So, I think this is a duplicate of bug 2036518.
*** This bug has been marked as a duplicate of bug 2036518 ***