[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 Justin Zobel changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #11 from Justin Zobel --- Thanks for the update. If there are other unrelated issues please report a bug if there is not one existing for it already, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 --- Comment #10 from Ariel Garcia --- I am now running kde connect from the current Debian testing: ii kdeconnect 20.08.3-1amd64 connect smartphones to your KDE Plasma Workspace It does not crash anymore upon connecting to the phone. (I could not transfer files anyways, but that must be some other issue :-( -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 Justin Zobel changed: What|Removed |Added CC||justin.zo...@gmail.com Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #8 from Justin Zobel --- I haven't been able to reproduce this on kdeconnect from git master. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 Ariel Garcia changed: What|Removed |Added Version|unspecified |1.3.3 Platform|Other |Debian testing --- Comment #7 from Ariel Garcia --- I still see this bug in kdeconnect 1.3.3, Debian testing (see backtrace in Bug #402839). Any hint how to "workaround" this at the network level? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 Christoph Feck changed: What|Removed |Added CC||aog20...@gmail.com --- Comment #6 from Christoph Feck --- *** Bug 402839 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 Aleix Pol changed: What|Removed |Added Resolution|BACKTRACE |--- Ever confirmed|0 |1 Status|NEEDSINFO |REOPENED --- Comment #5 from Aleix Pol --- Can you please submit it to phabricator? There we can discuss the patch. To me it feels weird to translate from ipv6 to 4 though, but maybe I just don't understand well the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 --- Comment #4 from Jasmin Buchert --- Created attachment 115008 --> https://bugs.kde.org/attachment.cgi?id=115008=edit Fix segfault with IPv4-mapped IPv6 addresses Works for me(TM) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 Jasmin Buchert changed: What|Removed |Added CC||jbuchert+kdeb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 --- Comment #3 from Tobias C. Berner --- The problem seems to be mapped Ipv4 addresses ":::172.16.0.103". -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 Tobias C. Berner changed: What|Removed |Added CC||tcber...@freebsd.org --- Comment #2 from Tobias C. Berner --- Hi there I have the same issue on FreeBSD. ### BT lldb) run Process 59923 launching Process 59923 launched: '/home/Tobias/devel/kdeconnect-kde/build/bin/kdeconnectd' (x86_64) QNativeSocketEngine::writeDatagram() was called not in QAbstractSocket::BoundState or QAbstractSocket::ConnectedState kdeconnect.core: Fallback (1), try reverse connection (send udp packet) "Connection refused" Process 59923 stopped * thread #1, name = 'kdeconnectd', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) frame #0: 0x00080177db81 libQt5Network.so.5`QSslSocket::connectToHost(this=0x0008133aabf0, hostName=0x7fffb6b8, port=1716, openMode=(i = 3), protocol=AnyIPProtocol) at qsslsocket.cpp:1947 (lldb) bt all error: libkdeconnectcore.so.1 :: Class 'QTimer' has a base class 'QObject' which does not have a complete definition. error: libkdeconnectcore.so.1 :: Try compiling the source file with -fstandalone-debug. * thread #1, name = 'kdeconnectd', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) * frame #0: 0x00080177db81 libQt5Network.so.5`QSslSocket::connectToHost(this=0x0008133aabf0, hostName=0x7fffb6b8, port=1716, openMode=(i = 3), protocol=AnyIPProtocol) at qsslsocket.cpp:1947 frame #1: 0x00080174c0b8 libQt5Network.so.5`QAbstractSocket::connectToHost(this=0x0008133aabf0, address=0x7fffb988, port=1716, openMode=(i = 3)) at qabstractsocket.cpp:1762 frame #2: 0x0008006628ee libkdeconnectcore.so.1`LanLinkProvider::newUdpConnection(this=0x000807f80e80) at lanlinkprovider.cpp:235 frame #3: 0x00080066925e libkdeconnectcore.so.1`QtPrivate::FunctorCall, QtPrivate::List<>, void, void (LanLinkProvider::*)()>::call(f=10 22 66 00 08 00 00 00 00 00 00 00 00 00 00 00, o=0x000807f80e80, arg=0x7fffbe68)(), LanLinkProvider*, void**) at qobjectdefs_impl.h:136 frame #4: 0x0008006691d3 libkdeconnectcore.so.1`void QtPrivate::FunctionPointer::call, void>(f=10 22 66 00 08 00 00 00 00 00 00 00 00 00 00 00, o=0x000807f80e80, arg=0x7fffbe68)(), LanLinkProvider*, void**) at qobjectdefs_impl.h:169 frame #5: 0x0008006690f6 libkdeconnectcore.so.1`QtPrivate::QSlotObject, void>::impl(which=1, this_=0x000802ffdb20, r=0x000807f80e80, a=0x7fffbe68, ret=0x) at qobjectdefs_impl.h:398 frame #6: 0x000804bb7476 libQt5Core.so.5`QtPrivate::QSlotObjectBase::call(this=0x000802ffdb20, r=0x000807f80e80, a=0x7fffbe68) at qobjectdefs_impl.h:378 frame #7: 0x000804bf4955 libQt5Core.so.5`QMetaObject::activate(sender=0x000807f80e98, signalOffset=3, local_signal_index=0, argv=0x) at qobject.cpp:3750 frame #8: 0x000804bf3ffd libQt5Core.so.5`QMetaObject::activate(sender=0x000807f80e98, m=0x0008050dd1f0, local_signal_index=0, argv=0x) at qobject.cpp:3629 frame #9: 0x000804a991c2 libQt5Core.so.5`QIODevice::readyRead(this=0x000807f80e98) at moc_qiodevice.cpp:185 frame #10: 0x0008017498b1 libQt5Network.so.5`QAbstractSocketPrivate::emitReadyRead(this=0x000804777180, channel=0) at qabstractsocket.cpp:1302 frame #11: 0x0008017494a9 libQt5Network.so.5`QAbstractSocketPrivate::canReadNotification(this=0x000804777180) at qabstractsocket.cpp:729 frame #12: 0x00080174f8b6 libQt5Network.so.5`QAbstractSocketPrivate::readNotification(this=0x000804777180) at qabstractsocket_p.h:75 frame #13: 0x000801743948 libQt5Network.so.5`QAbstractSocketEngine::readNotification(this=0x0008133aa5a0) at qabstractsocketengine.cpp:160 frame #14: 0x00080176062a libQt5Network.so.5`QReadNotifier::event(this=0x00081337a9e0, e=0x7fffcd80) at qnativesocketengine.cpp:1274 frame #15: 0x00080317dbef libQt5Widgets.so.5`QApplicationPrivate::notify_helper(this=0x000804777000, receiver=0x00081337a9e0, e=0x7fffcd80) at qapplication.cpp:3732 frame #16: 0x00080317f817 libQt5Widgets.so.5`QApplication::notify(this=0x7fffd1a0, receiver=0x00081337a9e0, e=0x7fffcd80) at qapplication.cpp:3104 frame #17: 0x000804ba287d libQt5Core.so.5`QCoreApplication::notifyInternal2(receiver=0x00081337a9e0, event=0x7fffcd80) at qcoreapplication.cpp:1050 frame #18: 0x000804ba80d8 libQt5Core.so.5`QCoreApplication::sendEvent(receiver=0x00081337a9e0, event=0x7fffcd80) at qcoreapplication.h:234 frame #19: 0x000804c3d7f5 libQt5Core.so.5`socketNotifierSourceDispatch(source=0x000804771b90, (null)=0x, (null)=0x)(void*), void*) at qeventdispatcher_glib.cpp:106 frame
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 Aleix Polchanged: What|Removed |Added CC||aleix...@kde.org Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Aleix Pol --- Can you still reproduce? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 Christoph Feckchanged: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.