Description of problem: i just tried to start owncloud client (not directly, using XFCE's Application Autostart feature) same happens if i try to start owncloud client directly app craeshes not allways, and not only on startup - sometimes it crashes after few minutes or may be hours after startup Version-Release number of selected component: owncloud-client-2.2.0-4.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/owncloud crash_function: QVector<QDBusCustomTypeInfo>::size executable: /usr/bin/owncloud global_pid: 1478 kernel: 4.4.9-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QVector<QDBusCustomTypeInfo>::size at ../../src/corelib/tools/qvector.h:83 #1 QDBusMetaType::typeToSignature at qdbusmetatype.cpp:437 #2 qDBusParametersForMethod at qdbusmisc.cpp:179 #4 QDBusConnectionPrivate::findSlot at qdbusintegrator.cpp:1291 #5 QDBusConnectionPrivate::prepareHook at qdbusintegrator.cpp:1306 #6 QDBusConnectionPrivate::disconnectRelay at qdbusintegrator.cpp:2395 #7 QDBusAbstractInterfacePrivate::finishDisconnectNotify at qdbusabstractinterface.cpp:661 #8 QObject::event at kernel/qobject.cpp:1256 #9 doNotify at kernel/qcoreapplication.cpp:1090 #10 QCoreApplication::notify at kernel/qcoreapplication.cpp:1076
Created attachment 1163892 [details] File: backtrace
Created attachment 1163893 [details] File: cgroup
Created attachment 1163894 [details] File: core_backtrace
Created attachment 1163895 [details] File: dso_list
Created attachment 1163896 [details] File: environ
Created attachment 1163897 [details] File: exploitable
Created attachment 1163898 [details] File: limits
Created attachment 1163899 [details] File: maps
Created attachment 1163900 [details] File: mountinfo
Created attachment 1163901 [details] File: namespaces
Created attachment 1163902 [details] File: open_fds
Created attachment 1163903 [details] File: proc_pid_status
Created attachment 1163904 [details] File: var_log_messages
Please do not mark bugreports as private, since it will prevent exchanging useful infos with upstream developers
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.