Bug 346779

Summary:	SFTP: crashes when attempting to revisit disconnected device's sd card folder
Product:	[Applications] kdeconnect	Reporter:	Long <yellowdragonwin>
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	kde, nicolas.fella, null
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Error giver by DrKonqi - no debug symbols

Description Long 2015-04-27 11:01:44 UTC

Browsing files remotely through Dolphin file manager. Leaving the file manager open I disconnected my device. Still on the unrefreshed view of the device sd card after it being disconnnected, I refreshed the view to see what would happen, by going to a different folder and going back to the device's sd card folder, after which kde connect crashes. 

Reproducible: Always

Steps to Reproduce:
1. go to device sd card folder
2. disconnect device
3. leave folder then go back

Actual Results:  
kdeconnect crashes along with file manager

Expected Results:  
maybe show an empty folder instead of crashing, I don't know how it should work really

Comment 1 Christoph Feck 2015-05-01 12:44:19 UTC

If this is reproducible, please add the backtrace. For more information, please read https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Comment 2 Unknown 2015-06-07 14:45:36 UTC

Created attachment 93056 [details]
Error giver by DrKonqi - no debug symbols

Despite having the -debuginfo package for openSUSE, DrKonqi cannot create a bigger trace.

Comment 3 Unknown 2015-06-07 14:46:37 UTC

Hello!
I also have this issue and I'm unable to create a better bug trace. DrKonqi keeps telling me, that I lack the debugging symbols, but I've already installed -debuginfo package for kdeconnect. This is what I've got so far:

Application: kdeconnect (kdeconnectd), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4ad2740 (LWP 1974))]

Thread 3 (Thread 0xb1de7b40 (LWP 1981)):
#0  0xffffffff in  ()

Thread 2 (Thread 0xb116eb40 (LWP 2706)):
#0  0xffffffff in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0xffffffff in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0
#2  0xffffffff in  () at /usr/lib/libglib-2.0.so.0
#3  0xffffffff in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#4  0xffffffff in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#5  0xffffffff in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#6  0xffffffff in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#7  0xffffffff in QThread::exec() () at /usr/lib/libQtCore.so.4
#8  0xffffffff in  () at /usr/lib/libQtCore.so.4
#9  0xffffffff in  () at /usr/lib/libQtCore.so.4
#10 0xffffffff in start_thread () at /lib/libpthread.so.0
#11 0xffffffff in clone () at /lib/libc.so.6

Thread 1 (Thread 0xb4ad2740 (LWP 1974)):
#0  0xffffffff in  ()
#1  0x00000000 in  ()

I'm using:

Linux 3.16.7-7-desktop
openSUSE 13.2 (Harlequin) (i586)
KDE 4.14.8

And the following kdeconnect components:

kdeconnect-kde
kdeconnect-kde-debuginfo
kdeconnect-kde-debugsource
kdeconnect-kde-devel
kdeconnect-kde-lang
 
ALL in 0.8-2.4 version.

Android application: 0.8g
Android version: 4.1.2
Kernel: 3.0.31 
Compilation: JZO54K
It's an LG L9.

Because this bug is reproducible, I'll gladly give you a better bug-trace once I have the debug package. Maybe the debug package for openSUSE is lacking something?

Thank you,
Bartosz

Comment 4 Nicolas Fella 2018-09-26 23:45:46 UTC

Closing as outdated