Bug 352071 - Error popup when Gwenview starts and my kdeconnect phone is unconnected.(sleeping, locked away etc)
Summary: Error popup when Gwenview starts and my kdeconnect phone is unconnected.(slee...
Status: RESOLVED DUPLICATE of bug 349130
Alias: None
Product: gwenview
Classification: Applications
Component: general (other bugs)
Version First Reported In: Other (add details in bug description)
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-31 18:51 UTC by kkoksvik
Modified: 2017-09-08 21:00 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kkoksvik 2015-08-31 18:51:10 UTC
It looks like Gwenview is expecting/demanding that  my phone should be available at all times.

Gwenview might handle this exeption by changing the icon to indicate that the resorce is unavailable at the moment.



Reproducible: Always

Steps to Reproduce:
1.Pair kdeconnect with phone.
2.Open some file on the phone with Gwenview
3.Turn of Phone.
4.Open a image with Gwenview

Actual Results:  
Error pupup:

Internal Error
Please send a full bug report at http://bugs.kde.org
No such object path '/modules/kdeconnect/devices/dab82ea69749e082/sftp'

Expected Results:  
Greyed/Changed icon(away) the sftp connection to the phone, and silently gone on with buisines.
Comment 1 Alexander Fieroch 2015-11-06 16:52:37 UTC
I think this is the same bug as https://bugs.kde.org/show_bug.cgi?id=349130

But the error dialog always pops up during every start of gwenview in the view-mode. It doesn't matter if the smartphone is unlocked or connected to the system.
Comment 2 Alexander Fieroch 2015-11-30 21:13:26 UTC
I think you can see a bookmark to your smartphone in the folders pane that is not working (anymore). Open dolphin and delete that entry. It worked for me.
Best regards
Comment 3 Nate Graham 2017-09-08 21:00:35 UTC
Yah, despite the differences, the root cause is the same as https://bugs.kde.org/show_bug.cgi?id=349130

*** This bug has been marked as a duplicate of bug 349130 ***