Description of problem: I first logged in without network connectivity. After connecting to the network a login window popped up. I right clicked the tray icon and selected quit. Version-Release number of selected component: nextcloud-client-2.5.3-1.fc30 Additional info: reporter: libreport-2.10.1 backtrace_rating: 3 cmdline: /usr/bin/nextcloud executable: /usr/bin/nextcloud journald_cursor: s=2e996a7a0d0941e99d298991832763ef;i=9d0;b=fc256eaee24745de86b0b32075d8d1fc;m=4a55ab8;t=591d8f9aa1237;x=2b570cf7849cbd82 kernel: 5.2.11-200.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #1 QMetaObject::cast at kernel/qmetaobject.cpp:374 #3 qobject_cast<QWidgetWindow*> at ../../include/QtCore/../../src/corelib/kernel/qobject.h:499 #4 QApplicationPrivate::isWindowBlocked at kernel/qapplication.cpp:2446 #5 QXcbWindow::relayFocusToModalWindow at ../../../../include/QtGui/5.12.4/QtGui/private/../../../../../src/gui/kernel/qguiapplication_p.h:196 #6 QXcbWindow::doFocusOut at qxcbwindow.cpp:876 #7 QXcbWindow::destroy at qxcbwindow.cpp:554 #8 QXcbWindow::~QXcbWindow at qxcbwindow.cpp:537 #9 QXcbGlxWindow::~QXcbGlxWindow at qxcbglxwindow.cpp:53 #11 QWindowPrivate::destroy at kernel/qwindow.cpp:1914
Created attachment 1612157 [details] File: backtrace
Created attachment 1612158 [details] File: cgroup
Created attachment 1612159 [details] File: core_backtrace
Created attachment 1612160 [details] File: cpuinfo
Created attachment 1612161 [details] File: dso_list
Created attachment 1612162 [details] File: environ
Created attachment 1612163 [details] File: exploitable
Created attachment 1612164 [details] File: limits
Created attachment 1612165 [details] File: maps
Created attachment 1612166 [details] File: mountinfo
Created attachment 1612167 [details] File: open_fds
Created attachment 1612168 [details] File: proc_pid_status
Created attachment 1612169 [details] File: var_log_messages
Clicked too fast, should not have been private. How do I make it public?
I have made the bug public.
Could you please test https://bodhi.fedoraproject.org/updates/FEDORA-2019-f8936457e9 and leave karma feedback? Thank you
FEDORA-2019-6ad9cf7edc has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-6ad9cf7edc
FEDORA-2019-282b17f3a1 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-282b17f3a1
FEDORA-2019-4e4292468f has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-4e4292468f
nextcloud-client-2.6.1-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-4e4292468f
nextcloud-client-2.6.1-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-282b17f3a1
nextcloud-client-2.6.1-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-6ad9cf7edc
nextcloud-client-2.6.1-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
nextcloud-client-2.6.1-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
nextcloud-client-2.6.1-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.