[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-10-19 Thread Albert Vaca
https://bugs.kde.org/show_bug.cgi?id=388991

Albert Vaca  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #45 from Albert Vaca  ---
1.2 is an old version, this problem is fixed in the current version 1.3.2.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-10-19 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=388991

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||alf...@gmail.com

--- Comment #44 from Kai Uwe Broulik  ---
*** Bug 400010 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-08-22 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #43 from David Mattatall  ---
Just bumping this. Still crashes and detaches.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-08-22 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=388991

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
   Severity|critical|crash

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-08-16 Thread daniel roi
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #42 from daniel roi  ---
Nevermind, it seems the segfault I reported above only happened once, I can't
reproduce it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-08-13 Thread daniel roi
https://bugs.kde.org/show_bug.cgi?id=388991

daniel roi  changed:

   What|Removed |Added

 CC||saart...@libero.it

--- Comment #41 from daniel roi  ---
On a freshly installed Arch Linux wth kdeconnect 1.3.1-1 I see this in my logs:

[ 2124.044491] kdeconnectd[6908]: segfault at 8 ip 7f3b7c892fbf sp
7ffc9fa641d0 error 4 in libQt5XcbQpa.so.5.11.1[7f3b7c88b000+d4000]
[ 2532.915715] kdeconnectd[7661]: segfault at 8 ip 7f28b4c0bfbf sp
7ffe8d171400 error 4 in libQt5XcbQpa.so.5.11.1[7f28b4c04000+d4000]
[ 2685.638765] kdeconnectd[8090]: segfault at 8 ip 7fe03721bfbf sp
7ffd002331d0 error 4 in libQt5XcbQpa.so.5.11.1[7fe037214000+d4000]
[ 2738.130807] kdeconnectd[8449]: segfault at 8 ip 7ffb40b7ffbf sp
7ffcc1bae8d0 error 4 in libQt5XcbQpa.so.5.11.1[7ffb40b78000+d4000]
[ 2817.73] kdeconnectd[8732]: segfault at 8 ip 7f81a2c1ffbf sp
7ffcbcb08830 error 4 in libQt5XcbQpa.so.5.11.1[7f81a2c18000+d4000]
[ 3087.642255] kdeconnectd[9392]: segfault at 8 ip 7f78b00ddfbf sp
7ffe586d45a0 error 4 in libQt5XcbQpa.so.5.11.1[7f78b00d6000+d4000]
[ 3409.277672] kdeconnectd[10123]: segfault at 8 ip 7fe77ccfefbf sp
7fff680def70 error 4 in libQt5XcbQpa.so.5.11.1[7fe77ccf7000+d4000]
[ 3441.648155] kdeconnectd[10389]: segfault at 8 ip 7fa04c6affbf sp
7ffd4577ee80 error 4 in libQt5XcbQpa.so.5.11.1[7fa04c6a8000+d4000]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-04-26 Thread Benjamin Xiao
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #40 from Benjamin Xiao  ---
I am not the original bug reporter, but I've been getting the exact same crash
as he is. After updating to KDE Connect 1.3 (from the Fedora testing repos),
the crash no longer seems to happen! Also it seems to have fixed the issue
where I have to keep my phone awake to get notifications.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-04-25 Thread Benjamin Xiao
https://bugs.kde.org/show_bug.cgi?id=388991

Benjamin Xiao  changed:

   What|Removed |Added

 CC||ben.r.x...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-29 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #39 from Christoph Feck  ---
https://cgit.kde.org/kdeconnect-kde.git/commit/?id=6495e8dc538610fb679df0f1522243103a3a1789
could have fixed it, but it was committed after the kdeconnect 1.2.1 release.
If you can test kdeconnect master branch, please confirm.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-06 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #38 from David Mattatall  ---
I mean, The bug is not mine, I just filed it. I have no idea where this should
go or how to request it be reassigned.

I'm just saying my whole issue has always been that when I get a slack
notification on my phone kdeconnect crashes.

Anyone out there?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-04 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=388991

Albert Astals Cid  changed:

   What|Removed |Added

 CC|aa...@kde.org   |

--- Comment #37 from Albert Astals Cid  ---
Ok, so the bug is yours

Find someone else that is not me to help you fix it and debug it, i'm only
interested in the kio side since it's the only part i have some expertise, so
removing myself from this bug, if someone has a valgrind trace involving KIO
open a new bug then.

You may also want to find someone else to move it out of the frameworks-kio
since this bug that belongs to you may be in the wrong product.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-04 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #36 from David Mattatall  ---
This was my ticket initially and has always been about this notifications bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-04 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #35 from Albert Astals Cid  ---
David, your backtrace is different from the one Lukasz shows, yours is about
the notifications code

==9724== Invalid read of size 8
==9724==at 0x53DBD0C: KNotification::setTitle(QString const&) (in
/usr/lib64/libKF5Notifications.so.5.43.0)
==9724==by 0x265F8886: Notification::createKNotification(bool,
NetworkPackage const&) (notification.cpp:94)
==9724==by 0x265FEC78:
NotificationsDbusInterface::processPackage(NetworkPackage const&)
(notificationsdbusinterface.cpp:96)
==9724==by 0x265F9C0A: NotificationsPlugin::receivePackage(NetworkPackage
const&) (notificationsplugin.cpp:59)
==9724==by 0x4E733B7: Device::privateReceivedPackage(NetworkPackage const&)
(device.cpp:345)
==9724==by 0x6BDED4D: QMetaObject::activate(QObject*, int, int, void**) (in
/usr/lib64/libQt5Core.so.5.9.4)
==9724==by 0x4E79D74: DeviceLink::receivedPackage(NetworkPackage const&)
(moc_devicelink.cpp:209)
==9724==by 0x4E56659: LanDeviceLink::dataReceived() (landevicelink.cpp:133)
==9724==by 0x6BDED4D: QMetaObject::activate(QObject*, int, int, void**) (in
/usr/lib64/libQt5Core.so.5.9.4)
==9724==by 0x4E5B6D5: SocketLineReader::dataReceived()
(socketlinereader.cpp:51)
==9724==by 0x6BDED4D: QMetaObject::activate(QObject*, int, int, void**) (in
/usr/lib64/libQt5Core.so.5.9.4)
==9724==by 0x78E8C1E: ??? (in /usr/lib64/libQt5Network.so.5.9.4)
==9724==  Address 0x27af00a0 is 16 bytes inside a block of size 24 free'd
==9724==at 0x4C2C63B: operator delete(void*) (vg_replace_malloc.c:576)
==9724==by 0x6BDF9D7: QObject::event(QEvent*) (in
/usr/lib64/libQt5Core.so.5.9.4)
==9724==by 0x5BD7D6B: QApplicationPrivate::notify_helper(QObject*, QEvent*)
(in /usr/lib64/libQt5Widgets.so.5.9.4)
==9724==by 0x5BDF5F8: QApplication::notify(QObject*, QEvent*) (in
/usr/lib64/libQt5Widgets.so.5.9.4)
==9724==by 0x6BB5E59: QCoreApplication::notifyInternal2(QObject*, QEvent*)
(in /usr/lib64/libQt5Core.so.5.9.4)
==9724==by 0x6BB8ACC: QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (in /usr/lib64/libQt5Core.so.5.9.4)
==9724==by 0x6C06822: ??? (in /usr/lib64/libQt5Core.so.5.9.4)
==9724==by 0xCD64516: g_main_context_dispatch (in
/usr/lib64/libglib-2.0.so.0.5200.3)
==9724==by 0xCD6477F: ??? (in /usr/lib64/libglib-2.0.so.0.5200.3)
==9724==by 0xCD6482B: g_main_context_iteration (in
/usr/lib64/libglib-2.0.so.0.5200.3)
==9724==by 0x6C0660E:
QEventDispatcherGlib::processEvents(QFlags) (in
/usr/lib64/libQt5Core.so.5.9.4)
==9724==by 0x6BB4B89:
QEventLoop::exec(QFlags) (in
/usr/lib64/libQt5Core.so.5.9.4)
==9724==  Block was alloc'd at
==9724==at 0x4C2B57F: operator new(unsigned long) (vg_replace_malloc.c:334)
==9724==by 0x265F8DDF: Notification::createKNotification(bool,
NetworkPackage const&) (notification.cpp:86)
==9724==by 0x265F91FD: Notification::Notification(NetworkPackage const&,
QObject*) (notification.cpp:53)
==9724==by 0x265FF4D0:
NotificationsDbusInterface::processPackage(NetworkPackage const&)
(notificationsdbusinterface.cpp:84)
==9724==by 0x265F9C0A: NotificationsPlugin::receivePackage(NetworkPackage
const&) (notificationsplugin.cpp:59)
==9724==by 0x4E733B7: Device::privateReceivedPackage(NetworkPackage const&)
(device.cpp:345)
==9724==by 0x6BDED4D: QMetaObject::activate(QObject*, int, int, void**) (in
/usr/lib64/libQt5Core.so.5.9.4)
==9724==by 0x4E79D74: DeviceLink::receivedPackage(NetworkPackage const&)
(moc_devicelink.cpp:209)
==9724==by 0x4E56659: LanDeviceLink::dataReceived() (landevicelink.cpp:133)
==9724==by 0x6BDED4D: QMetaObject::activate(QObject*, int, int, void**) (in
/usr/lib64/libQt5Core.so.5.9.4)
==9724==by 0x4E5B6D5: SocketLineReader::dataReceived()
(socketlinereader.cpp:51)
==9724==by 0x6BDED4D: QMetaObject::activate(QObject*, int, int, void**) (in
/usr/lib64/libQt5Core.so.5.9.4)

I suggest you open a new bug so we can track the kio related one here.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-04 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #34 from David Mattatall  ---
Created attachment 84
  --> https://bugs.kde.org/attachment.cgi?id=84&action=edit
valgrind terminal output for crash

Here's the valgrind terminal output

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-04 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #33 from Albert Astals Cid  ---
(In reply to David Mattatall from comment #32)
> Here's my valgrind output.
> 
> It's absolutely massive, I hope it's useful.
> https://we.tl/2rAd4UrD49

That's not the output of valgrind to the terminal.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-03 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #32 from David Mattatall  ---
Here's my valgrind output.

It's absolutely massive, I hope it's useful.
https://we.tl/2rAd4UrD49

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-03 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #31 from David Mattatall  ---
Here's my valgrind output.

It's absolutely massive, I hope it's useful.
https://we.tl/2rAd4UrD49

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-03 Thread H L Prasad
https://bugs.kde.org/show_bug.cgi?id=388991

H L Prasad  changed:

   What|Removed |Added

 CC||hlpr...@gmail.com

--- Comment #30 from H L Prasad  ---
I am also facing the same issue. I'm using KDE Neon User Edition with
kdeconnect version 1.2.1-0neon+16.04+xenial+build31, on laptop, and kdeconnect
app v1.7.1 on Android. I observed that if I disable 'Receive Notifications' on
KDEConnect android, then this crash of kdeconnectd does not happen on my
laptop.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-03 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #29 from Albert Astals Cid  ---
go to a terminal, make sure you have valgrind installed and then run

killall kdeconnectd; valgrind /usr/lib/kdeconnectd

and try to make it crash, attach the output of valgrind

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-01 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #28 from David Mattatall  ---
Hi Albert,

Provide instruction and I'd be happy to test

Cheers,
David A. Mattatall | 778-323-7857

On 03/01/2018 02:41 PM, Albert Astals Cid wrote:
> https://bugs.kde.org/show_bug.cgi?id=388991
>
> --- Comment #27 from Albert Astals Cid  ---
> (In reply to Lukasz from comment #24)
>> It's happening to me as well:
> Lukasz can you reproduce this easily? Do you know how to run kdeconnect under
> valgrind? I'd help me quite a bit having the valgrind trace to understand
> what's going on.
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-01 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #27 from Albert Astals Cid  ---
(In reply to Lukasz from comment #24)
> It's happening to me as well:

Lukasz can you reproduce this easily? Do you know how to run kdeconnect under
valgrind? I'd help me quite a bit having the valgrind trace to understand
what's going on.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-01 Thread Lukasz
https://bugs.kde.org/show_bug.cgi?id=388991

Lukasz  changed:

   What|Removed |Added

Version|unspecified |5.43.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-01 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=388991

Christoph Feck  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|VERIFIED|UNCONFIRMED

--- Comment #26 from Christoph Feck  ---
Reopening based on recent comments. Please set the KF5 frameworks version
number.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-01 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #25 from David Mattatall  ---
Just to update,


I'm up to 1.2.1-r1 and it is still constantly crashing in the same manner

Cheers,
David A. Mattatall | 778-323-7857

On 03/01/2018 05:33 AM, Lukasz wrote:
> https://bugs.kde.org/show_bug.cgi?id=388991
>
> Lukasz  changed:
>
>What|Removed |Added
> 
>  CC||dolo...@outlook.com
>  Status|RESOLVED|VERIFIED
>
> --- Comment #24 from Lukasz  ---
> It's happening to me as well:
>
> Thread 4 (Thread 0x7f0ce82a5700 (LWP 678)):
> #0  0x7f0d0130997b in poll () from /usr/lib/libc.so.6
> #1  0x7f0cfb503ff3 in ?? () from /usr/lib/libglib-2.0.so.0
> #2  0x7f0cfb50410e in g_main_context_iteration () from
> /usr/lib/libglib-2.0.so.0
> #3  0x7f0d01c552f1 in
> QEventDispatcherGlib::processEvents(QFlags) ()
>from /usr/lib/libQt5Core.so.5
> #4  0x7f0d01bf73db in
> QEventLoop::exec(QFlags) () from
> /usr/lib/libQt5Core.so.5
> #5  0x7f0d01a067ae in QThread::exec() () from /usr/lib/libQt5Core.so.5
> #6  0x7f0d00668416 in ?? () from /usr/lib/libQt5DBus.so.5
> #7  0x7f0d01a0bb4d in ?? () from /usr/lib/libQt5Core.so.5
> #8  0x7f0cfd4d908c in start_thread () from /usr/lib/libpthread.so.0
> #9  0x7f0d01313e7f in clone () from /usr/lib/libc.so.6
>
> Thread 3 (Thread 0x7f0cf1118700 (LWP 660)):
> #0  0x7f0d0130997b in poll () from /usr/lib/libc.so.6
> #1  0x7f0cf9e508e0 in ?? () from /usr/lib/libxcb.so.1
> #2  0x7f0cf9e52679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
> #3  0x7f0cf3cb482a in ?? () from /usr/lib/libQt5XcbQpa.so.5
> #4  0x7f0d01a0bb4d in ?? () from /usr/lib/libQt5Core.so.5
> #5  0x7f0cfd4d908c in start_thread () from /usr/lib/libpthread.so.0
> #6  0x7f0d01313e7f in clone () from /usr/lib/libc.so.6
>
> Thread 2 (Thread 0x7f0ce7aa4700 (LWP 681)):
> #0  0x7f0d0130997b in poll () from /usr/lib/libc.so.6
> #1  0x7f0cfb503ff3 in ?? () from /usr/lib/libglib-2.0.so.0
> #2  0x7f0cfb50410e in g_main_context_iteration () from
> /usr/lib/libglib-2.0.so.0
> #3  0x7f0d01c552f1 in
> QEventDispatcherGlib::processEvents(QFlags) ()
>from /usr/lib/libQt5Core.so.5
> #4  0x7f0d01bf73db in
> QEventLoop::exec(QFlags) () from
> /usr/lib/libQt5Core.so.5
> #5  0x7f0d01a067ae in QThread::exec() () from /usr/lib/libQt5Core.so.5
> #6  0x7f0d01a0bb4d in ?? () from /usr/lib/libQt5Core.so.5
> #7  0x7f0cfd4d908c in start_thread () from /usr/lib/libpthread.so.0
> #8  0x7f0d01313e7f in clone () from /usr/lib/libc.so.6
>
> Thread 1 (Thread 0x7f0d03ecd500 (LWP 647)):
> #0  0x7f0d001291c2 in KIO::TransferJob::sendAsyncData
> (this=this@entry=0x564d1342c990, dataForSlave=...)
> at
> /home/dlh/abs/packages/kio/repos/extra-x86_64/src/kio-5.43.0/src/core/transferjob.cpp:189
> #1  0x7f0d00129924 in KIO::TransferJobPrivate::slotIODeviceClosed
> (this=0x564d13397380)
> at
> /home/dlh/abs/packages/kio/repos/extra-x86_64/src/kio-5.43.0/src/core/transferjob.cpp:457
> #2  0x7f0d0012a0c9 in KIO::TransferJob::qt_static_metacall (_o= out>, _c=, _id=, 
> _a=)
> at
> /home/dlh/abs/packages/kio/repos/extra-x86_64/src/build/src/core/KF5KIOCore_autogen/include/moc_transferjob.cpp:171
> #3  0x7f0d01c296c6 in QMetaObject::activate(QObject*, int, int, void**) ()
> from /usr/lib/libQt5Core.so.5
> #4  0x7f0d00fad06e in ?? () from /usr/lib/libQt5Network.so.5
> #5  0x7f0d01c296c6 in QMetaObject::activate(QObject*, int, int, void**) ()
> from /usr/lib/libQt5Core.so.5
> #6  0x7f0d00f791c1 in QAbstractSocket::disconnectFromHost() () from
> /usr/lib/libQt5Network.so.5
> #7  0x7f0d00f7a5e6 in QAbstractSocket::~QAbstractSocket() () from
> /usr/lib/libQt5Network.so.5
> #8  0x7f0d00f7e36a in QTcpSocket::~QTcpSocket() () from
> /usr/lib/libQt5Network.so.5
> #9  0x7f0d00fa31fd in QSslSocket::~QSslSocket() () from
> /usr/lib/libQt5Network.so.5
> #10 0x7f0d00fa322a in QSslSocket::~QSslSocket() () from
> /usr/lib/libQt5Network.so.5
> #11 0x7f0d03ae5df9 in QtSharedPointer::ExternalRefCountData::destroy
> (this=0x564d133f15f0)
> at /usr/include/qt/QtCore/qsharedpointer_impl.h:157
> #12 QSharedPointer::deref (dd=0x564d133f15f0) at
> /usr/include/qt/QtCore/qsharedpointer_impl.h:461
> #13 QSharedPointer::deref (this=0x564d1335dd78) at
> /usr/include/qt/QtCore/qsharedpointer_impl.h:456
> #14 QSharedPointer::~QSharedPointer (this=0x564d1335dd78,
> __in_chrg=)
> at /usr/include/qt/QtCore/qsharedpointer_impl.h:313
> #15 FileTransferJob::~FileTransferJob (this=0x564d1335dd60,
> __in_chrg=)
> at
> /home/dlh/abs/community/kdeconnect/trunk/src/build/core/kdeconnectcore_autogen/EWIEGA46WW/../../../../kdeconnect-kde-v1.2.1/core/filetransferjob.h:41
> #16 FileTransferJob::~FileTransferJob (this=0x564d1335dd60,
> __in_chrg=)
> at
> /

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-03-01 Thread Lukasz
https://bugs.kde.org/show_bug.cgi?id=388991

Lukasz  changed:

   What|Removed |Added

 CC||dolo...@outlook.com
 Status|RESOLVED|VERIFIED

--- Comment #24 from Lukasz  ---
It's happening to me as well:

Thread 4 (Thread 0x7f0ce82a5700 (LWP 678)):
#0  0x7f0d0130997b in poll () from /usr/lib/libc.so.6
#1  0x7f0cfb503ff3 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f0cfb50410e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f0d01c552f1 in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/libQt5Core.so.5
#4  0x7f0d01bf73db in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f0d01a067ae in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f0d00668416 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f0d01a0bb4d in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f0cfd4d908c in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f0d01313e7f in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f0cf1118700 (LWP 660)):
#0  0x7f0d0130997b in poll () from /usr/lib/libc.so.6
#1  0x7f0cf9e508e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f0cf9e52679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f0cf3cb482a in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f0d01a0bb4d in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f0cfd4d908c in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f0d01313e7f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f0ce7aa4700 (LWP 681)):
#0  0x7f0d0130997b in poll () from /usr/lib/libc.so.6
#1  0x7f0cfb503ff3 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f0cfb50410e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f0d01c552f1 in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/libQt5Core.so.5
#4  0x7f0d01bf73db in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f0d01a067ae in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f0d01a0bb4d in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7f0cfd4d908c in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f0d01313e7f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f0d03ecd500 (LWP 647)):
#0  0x7f0d001291c2 in KIO::TransferJob::sendAsyncData
(this=this@entry=0x564d1342c990, dataForSlave=...)
at
/home/dlh/abs/packages/kio/repos/extra-x86_64/src/kio-5.43.0/src/core/transferjob.cpp:189
#1  0x7f0d00129924 in KIO::TransferJobPrivate::slotIODeviceClosed
(this=0x564d13397380)
at
/home/dlh/abs/packages/kio/repos/extra-x86_64/src/kio-5.43.0/src/core/transferjob.cpp:457
#2  0x7f0d0012a0c9 in KIO::TransferJob::qt_static_metacall (_o=, _c=, _id=, 
_a=)
at
/home/dlh/abs/packages/kio/repos/extra-x86_64/src/build/src/core/KF5KIOCore_autogen/include/moc_transferjob.cpp:171
#3  0x7f0d01c296c6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f0d00fad06e in ?? () from /usr/lib/libQt5Network.so.5
#5  0x7f0d01c296c6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#6  0x7f0d00f791c1 in QAbstractSocket::disconnectFromHost() () from
/usr/lib/libQt5Network.so.5
#7  0x7f0d00f7a5e6 in QAbstractSocket::~QAbstractSocket() () from
/usr/lib/libQt5Network.so.5
#8  0x7f0d00f7e36a in QTcpSocket::~QTcpSocket() () from
/usr/lib/libQt5Network.so.5
#9  0x7f0d00fa31fd in QSslSocket::~QSslSocket() () from
/usr/lib/libQt5Network.so.5
#10 0x7f0d00fa322a in QSslSocket::~QSslSocket() () from
/usr/lib/libQt5Network.so.5
#11 0x7f0d03ae5df9 in QtSharedPointer::ExternalRefCountData::destroy
(this=0x564d133f15f0)
at /usr/include/qt/QtCore/qsharedpointer_impl.h:157
#12 QSharedPointer::deref (dd=0x564d133f15f0) at
/usr/include/qt/QtCore/qsharedpointer_impl.h:461
#13 QSharedPointer::deref (this=0x564d1335dd78) at
/usr/include/qt/QtCore/qsharedpointer_impl.h:456
#14 QSharedPointer::~QSharedPointer (this=0x564d1335dd78,
__in_chrg=)
at /usr/include/qt/QtCore/qsharedpointer_impl.h:313
#15 FileTransferJob::~FileTransferJob (this=0x564d1335dd60,
__in_chrg=)
at
/home/dlh/abs/community/kdeconnect/trunk/src/build/core/kdeconnectcore_autogen/EWIEGA46WW/../../../../kdeconnect-kde-v1.2.1/core/filetransferjob.h:41
#16 FileTransferJob::~FileTransferJob (this=0x564d1335dd60,
__in_chrg=)
at
/home/dlh/abs/community/kdeconnect/trunk/src/build/core/kdeconnectcore_autogen/EWIEGA46WW/../../../../kdeconnect-kde-v1.2.1/core/filetransferjob.h:41
#17 0x7f0d01c2a131 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#18 0x7f0d02976fec in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#19 0x7f0d0297e9c6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#20 0x000

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-20 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #23 from David Mattatall  ---
I resolved that crash on load (sendAsyncData) by clearing out the config
directory. So I cannot replicate it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-20 Thread Albert Vaca
https://bugs.kde.org/show_bug.cgi?id=388991

Albert Vaca  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #22 from Albert Vaca  ---
There are two different stack traces on this issue. I'm not sure if the other
crash, on sendAsyncData, has actually been fixed (it might) but I'm gonna mark
it as resolved for now. Feel free to reopen if the sendAsyncData crash can be
reproduced.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-20 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #21 from David Mattatall  ---
Great so is this to be set to resolved?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-20 Thread Albert Vaca
https://bugs.kde.org/show_bug.cgi?id=388991

Albert Vaca  changed:

   What|Removed |Added

 CC||albertv...@gmail.com

--- Comment #20 from Albert Vaca  ---
(In reply to Kai Uwe Broulik from comment #17)
> I can see why the notification thing crashes, it stores KNotification as a
> raw pointer but that class will self-delete when closed. That doesn't
> explain the sendAsyncData one, though

The notification crash was fixed in 895a9206ffafd4b9725f567fd069fd655f200139

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-18 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #19 from David Mattatall  ---
Created attachment 109961
  --> https://bugs.kde.org/attachment.cgi?id=109961&action=edit
Crashlog for kdeconnect 1 18 2018

Crashlog for 1 18 2018 for kdeconnect 1.2.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-17 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #18 from David Mattatall  ---
Let me know what further information you need.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-17 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #17 from Kai Uwe Broulik  ---
I can see why the notification thing crashes, it stores KNotification as a raw
pointer but that class will self-delete when closed. That doesn't explain the
sendAsyncData one, though

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-17 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #16 from David Mattatall  ---
This seems to have some percentage to crash when I get an alert on runscope on
my phone and I think it's sending that alert to my desktop.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-17 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #15 from David Mattatall  ---
Interesting. Maybe more than one thing is at play. Here's a new one:

(04:08:25) david@gothbox:/etc/portage $ gdb /usr/lib64/libexec/kdeconnectd
GNU gdb (Gentoo 7.12.1 vanilla) 7.12.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib64/libexec/kdeconnectd...Reading symbols from
/usr/lib/debug//usr/lib64/libexec/kdeconnectd.debug...done.
done.
(gdb) run
Starting program: /usr/lib64/libexec/kdeconnectd 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffdfb8d700 (LWP 15499)]
[New Thread 0x7fffd7d74700 (LWP 15500)]
kdeconnect.core: KdeConnect daemon starting
[New Thread 0x7fffd7573700 (LWP 15501)]
kdeconnect.core: onStart
kdeconnect.core: KdeConnect daemon started
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: Starting client ssl (but I'm the server TCP socket)
kdeconnect.core: Socket succesfully stablished an SSL connection
kdeconnect.core: It is a known device "OnePlus"
kdeconnect.core: Not loading plugin "kdeconnect_remotecommands" because device
doesn't support it
kdeconnect.core: Not loading plugin "kdeconnect_mprisremote" because device
doesn't support it
kdeconnect.core: Not loading plugin "kdeconnect_lockdevice" because device
doesn't support it
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeconnect.plugin.mpris: MPRIS service "org.mpris.MediaPlayer2.clementine" just
came online
kdeconnect.plugin.mpris: Mpris addPlayer "org.mpris.MediaPlayer2.clementine" ->
"Clementine"
kdeconnect.plugin.sftp: add to dolphin
kdeconnect.plugin.sftp: Created device: "OnePlus"
discarding unsupported package "kdeconnect.runcommand.request" for "OnePlus"
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/a77729036df82d1daa9d9085253369f9") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/a77729036df82d1daa9d9085253369f9") size: 6821
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/a77729036df82d1daa9d9085253369f9") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/a77729036df82d1daa9d9085253369f9") size: 6821
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/12e673432d351e0c508edf910094ee9d") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/12e673432d351e0c508edf910094ee9d") size: 9411
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/b63a275187c6c51784fb27abf1e15bb7") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/b63a275187c6c51784fb27abf1e15bb7") size: 2563
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/a77729036df82d1daa9d9085253369f9") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/a77729036df82d1daa9d9085253369f9") size: 6821
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/a77729036df82d1daa9d9085253369f9") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/a77729036df82d1daa9d9085253369f9") size: 6821
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/12e673432d351e0c508edf910094ee9d") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/12e673432d351e0c508edf910094ee9d") size: 9411
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/b63a275187c6c51784fb27abf1e15bb7") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/b63a275187c6c51784fb27abf1e15bb7") size: 2563
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
kdeconnect.core: Socket succesfully stablished an SSL connection
kdeconnect.core: It is a known device "OnePlus"
kdeconnect.plugin.notification: Not found noti by internal Id: 
"0|com.google.android.gm|7|null|10061"
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/654db74a4a34b95672cc883fdbfe4293") lacks a scheme.
S

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-17 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #14 from Kai Uwe Broulik  ---
Well, now it looks like it crashed in KNotification::setPixmap whereas before
it would crash in KIO::TransferJob::sendAsyncData, can you perhaps try again?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-17 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #13 from David Mattatall  ---
Unstripped, here ya go

(00:32:58) david@gothbox:~ $ gdb /usr/lib64/libexec/kdeconnectd
GNU gdb (Gentoo 7.12.1 vanilla) 7.12.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib64/libexec/kdeconnectd...(no debugging symbols
found)...done.
(gdb) run
Starting program: /usr/lib64/libexec/kdeconnectd 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffdfb8d700 (LWP 1895)]
[New Thread 0x7fffd7d74700 (LWP 1896)]
kdeconnect.core: KdeConnect daemon starting
[New Thread 0x7fffd7573700 (LWP 1897)]
kdeconnect.core: onStart
kdeconnect.core: KdeConnect daemon started
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
kdeconnect.core: Socket succesfully stablished an SSL connection
kdeconnect.core: It is a known device "OnePlus"
kdeconnect.plugin.sftp: add to dolphin
kdeconnect.plugin.sftp: Created device: "OnePlus"
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeconnect.plugin.mpris: MPRIS service "org.mpris.MediaPlayer2.clementine" just
came online
kdeconnect.plugin.mpris: Mpris addPlayer "org.mpris.MediaPlayer2.clementine" ->
"Clementine"
kdeconnect.core: Socket succesfully stablished an SSL connection
kdeconnect.core: It is a known device "OnePlus"
QCoreApplication::postEvent: Unexpected null receiver
kdeconnect.plugin.notification: Destroying NotificationsPlugin
kdeconnect.core: Sending onNetworkChange to  1  LinkProviders
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: Starting client ssl (but I'm the server TCP socket)
kdeconnect.core: Socket succesfully stablished an SSL connection
kdeconnect.core: It is a known device "OnePlus"
kdeconnect.core: Not loading plugin "kdeconnect_lockdevice" because device
doesn't support it
kdeconnect.core: Not loading plugin "kdeconnect_remotecommands" because device
doesn't support it
kdeconnect.core: Not loading plugin "kdeconnect_mprisremote" because device
doesn't support it
kdeconnect.plugin.mpris: MPRIS service "org.mpris.MediaPlayer2.clementine" just
came online
kdeconnect.plugin.mpris: Mpris addPlayer "org.mpris.MediaPlayer2.clementine" ->
"Clementine"
kdeconnect.plugin.sftp: add to dolphin
kdeconnect.plugin.sftp: Created device: "OnePlus"
kdeconnect.plugin.battery: Deleting stale BatteryDbusInterface for "OnePlus"
discarding unsupported package "kdeconnect.runcommand.request" for "OnePlus"
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/d7bcce8479ae57c082101e2c15d06087") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/d7bcce8479ae57c082101e2c15d06087") size: 11936
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/837b8138b8af0354f9d3efde1245542d") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/837b8138b8af0354f9d3efde1245542d") size: 16496
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/aca6c32eea236538b6cf35e36ebad5cc") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/aca6c32eea236538b6cf35e36ebad5cc") size: 14008
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/5c496b9e490e39dcba66770882421936") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/5c496b9e490e39dcba66770882421936") size: 5484
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/d7bcce8479ae57c082101e2c15d06087") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/d7bcce8479ae57c082101e2c15d06087") size: 11936
kdeconnect.core: Destination QUrl
QUrl("/tmp/kdeconnect/837b8138b8af0354f9d3efde1245542d") lacks a scheme.
Setting its scheme to 'file'.
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("/tmp/kdeconnect/837b8138b8af0354f9d3efde1245542d") size: 16496
kdeconnect.core: Dest

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-16 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #12 from Albert Astals Cid  ---
Yes please, it would be great if you could rebuild the kio package with debug
symbols

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-15 Thread David Mattatall
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #11 from David Mattatall  ---
Hi it's a 100% reproducible.

Just give me the steps and I'd be happy to follow (I can even build with
symbols if you need me too). I think gentoo allows that with a flag.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-15 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=388991

--- Comment #10 from Albert Astals Cid  ---
David how reproducible is this for you?

Any chance you could get us a crash with more debug information?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

2018-01-15 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=388991

Kai Uwe Broulik  changed:

   What|Removed |Added

Product|kdeconnect  |frameworks-kio
Version|1.2 |unspecified
 CC||aa...@kde.org,
   ||kdelibs-b...@kde.org
   Assignee|albertv...@gmail.com|fa...@kde.org
  Component|plasmoid|general

--- Comment #9 from Kai Uwe Broulik  ---
Looks like a cras in KIO, re-assigning. There were some chnages to the
TransferJob recently, I think.

-- 
You are receiving this mail because:
You are watching all bug changes.