Description of problem: 1. I booted up my computer and logged in 2. I almost immediately logged back out again 3. Then I immediately logged back in again This ABRT notification popped up right after logging in in step 3, but nextcloud-client is and was working perfectly fine regardless. Version-Release number of selected component: nextcloud-client-3.3.6-1.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-com.nextcloudgmbh.Nextcloud cmdline: /usr/bin/nextcloud --background crash_function: qt_message_fatal executable: /usr/bin/nextcloud journald_cursor: s=1829ce260b824b3497b9384bc4359aed;i=4e469;b=2823557b1bcb47d48611ccf3b27db5a3;m=682a758;t=5d9efcbd113ee;x=8e2bedc32269322c kernel: 5.16.12-200.fc35.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 qt_message_fatal at global/qlogging.cpp:1914 #5 QMessageLogger::fatal at global/qlogging.cpp:893 #6 init_platform at kernel/qguiapplication.cpp:1254 #7 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1474 #8 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1491 #9 QCoreApplicationPrivate::init at kernel/qcoreapplication.cpp:835 #10 QGuiApplicationPrivate::init at kernel/qguiapplication.cpp:1520 #11 QApplicationPrivate::init at kernel/qapplication.cpp:513 #12 QApplication::QApplication at kernel/qapplication.cpp:501 #13 SharedTools::QtSingleApplication::QtSingleApplication at /usr/src/debug/nextcloud-client-3.3.6-1.fc35.x86_64/src/3rdparty/qtsingleapplication/qtsingleapplication.cpp:56
Created attachment 1865445 [details] File: backtrace
Created attachment 1865446 [details] File: core_backtrace
Created attachment 1865447 [details] File: cpuinfo
Created attachment 1865448 [details] File: dso_list
Created attachment 1865449 [details] File: environ
Created attachment 1865450 [details] File: limits
Created attachment 1865451 [details] File: maps
Created attachment 1865452 [details] File: mountinfo
Created attachment 1865453 [details] File: open_fds
Created attachment 1865454 [details] File: proc_pid_status
Created attachment 1865455 [details] File: var_log_messages
FEDORA-2022-e70dc539df has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e70dc539df
FEDORA-2022-e70dc539df has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-e70dc539df` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e70dc539df See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
FEDORA-2022-e70dc539df has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.