Bug 352568 - Clicking in the "browser" icon open an empty dolphin window
Summary: Clicking in the "browser" icon open an empty dolphin window
Status: RESOLVED DUPLICATE of bug 341175
Alias: None
Product: kdeconnect
Classification: Applications
Component: plasmoid (show other bugs)
Version: 0.8
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-11 14:26 UTC by Valerio De Angelis
Modified: 2015-11-12 01:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Shell examination of the situation (714 bytes, text/plain)
2015-10-26 15:14 UTC, PeGa!
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Valerio De Angelis 2015-09-11 14:26:49 UTC
Nexus 5 with the beta version installed, Fedora 22 with plasma 5.4

I see my phone in the system tray, I see battery dicharging and so on, however when I click on the "browser" icon, the result is a empty dolphin window (see the screenshot).
Shouldn't I see the phone directories?

Reproducible: Always

Steps to Reproduce:
1. click the phone icon on the system tray
2. click on the browser icon 
3. see the empty dolphin window

Actual Results:  
an empty dolphin window

Expected Results:  
a dolphin window that list my phone directories

Screenshot:
http://i.imgur.com/meabEV4.png
Comment 1 PeGa! 2015-10-26 15:14:10 UTC
Created attachment 95139 [details]
Shell examination of the situation
Comment 2 PeGa! 2015-10-26 15:14:34 UTC
Comment on attachment 95139 [details]
Shell examination of the situation

Same here. kdeconnect 0.8 in Gentoo GNU/Linux (latest available in official repository being 0.8-r1), kdeconnect 0.9c in a Samsung i9300 / SlimKat 4.4.4.

When I go by shell, I've got not an empty directory but one with very strange permissions and gives "permission denied".
Comment 3 PeGa! 2015-10-26 15:32:31 UTC
I stand corrected: By shell a ls gives "Operation not permitted"
Comment 4 Albert Vaca Cintora 2015-11-12 01:06:30 UTC

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