-
Notifications
You must be signed in to change notification settings - Fork 664
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Qt4] [RedHat] [Linux] Crash on QNetworkReplyImplPrivate::resumeNotificationHandling #3960
Comments
@Germano0 Any info? |
@guruz I just pinged the bugreporter. Let's wait for a reply |
@guruz our packages for Fedora 22 compile against Qt5: https://build.opensuse.org/package/live_build_log/isv:ownCloud:desktop/owncloud-client/Fedora_22/x86_64 |
@Germano0 Does it work with those packages? |
@guruz What do you mean exactly? |
@Germano0 We think this is a Qt4 problem. |
@guruz I am still waiting for a reply from the Fedora bugreporter |
Another user experienced the problem. I asked him to show me the installed qt libs. Hereunder his reply: Yes, but I remember now that I have done a "dnf upgrade" during this session, so this may be inaccurate: $ rpm -qa qt* | sort dnf update log (may contain old qt lib versions https://bugzilla.redhat.com/attachment.cgi?id=1091089 ) |
@Germano0 This does not help. It's fine for a system to have both qt4 and qt5 installed. |
@Germano0 Does this still occur with your Qt5 based Fedora package? |
Hi @guruz , I just asked to the person who filled the Fedora bugreport. Soon I wil receive a feedback |
On Fedora bugzilla the bug is marked as fixed due missing feedback from bugreport creator. I assume it as fixed even here |
Upstream bugreport of https://bugzilla.redhat.com/show_bug.cgi?id=1272729
Version-Release number of selected component:
owncloud-client-2.0.1-1.fc22
Additional info:
reporter: libreport-2.6.2
backtrace_rating: 4
cmdline: /usr/bin/owncloud
crash_function: QNetworkReplyImplPrivate::resumeNotificationHandling
executable: /usr/bin/owncloud
global_pid: 5443
kernel: 4.1.10-200.fc22.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 QNetworkReplyImplPrivate::resumeNotificationHandling at access/qnetworkreplyimpl.cpp:444
#1 QNetworkReplyImplPrivate::finished at access/qnetworkreplyimpl.cpp:796
#2 QNetworkAccessBackend::finished at access/qnetworkaccessbackend.cpp:324
#3 QNetworkAccessHttpBackend::replyFinished at access/qnetworkaccesshttpbackend.cpp:754
#4 QNetworkAccessHttpBackend::qt_static_metacall at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:95
#5 QObject::event at kernel/qobject.cpp:1222
#6 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:4565
#7 QApplication::notify at kernel/qapplication.cpp:4351
#8 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:953
#9 sendEvent at kernel/qcoreapplication.h:231
you can find more logs in the mentioned bugzilla URL
The text was updated successfully, but these errors were encountered: