| Summary: | Cannot share file between phone And computer | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | zyf0330 <zyf034100> |
| Component: | android-application | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | lpcornel, mike.cloaked, prahal |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
zyf0330
2021-09-26 05:47:51 UTC
Confirmed. Flagged out of date at https://archlinux.org/packages/extra/x86_64/kdeconnect/ Upgrade of openssh (8.7p1-2 -> 8.8p1-1) causes kdeconnect to fail connect. (In reply to lpcornel from comment #1) > Confirmed. Flagged out of date at > https://archlinux.org/packages/extra/x86_64/kdeconnect/ > > Upgrade of openssh (8.7p1-2 -> 8.8p1-1) causes kdeconnect to fail connect. But why kdeconnect on Ubuntu is still 20.12.3 This discussion on the Arch Linux forum is pertinent to this bug: https://bbs.archlinux.org/viewtopic.php?pid=1995116 (In reply to zyf0330 from comment #2) > (In reply to lpcornel from comment #1) > > Confirmed. Flagged out of date at > > https://archlinux.org/packages/extra/x86_64/kdeconnect/ > > > > Upgrade of openssh (8.7p1-2 -> 8.8p1-1) causes kdeconnect to fail connect. > > But why kdeconnect on Ubuntu is still 20.12.3 The version referenced (8.8p1-1) is for openssh (in Arch), not kdeconnect. kdeconnect has not been revised to be compatible with the new version of openssh. I don't know what version of openssh applies to Ubuntu. (In reply to lpcornel from comment #4) > The version referenced (8.8p1-1) is for openssh (in Arch), not kdeconnect. > kdeconnect has not been revised to be compatible with the new version of > openssh. I don't know what version of openssh applies to Ubuntu. Sorry, I misunderstand. I use Ubuntu 21.04 and my openssl version is 8.4p1-5 The original report concerns kdeconnect not transferring files to an android phone in Ubuntu - which does not have the latest version of openssl, but the later report refers to a working system in Arch Linux where kdeconnect worked fine until the new version of openssl broke kdeconnect. Perhaps that should be a new separate bug report where kdeconnect can be fixed to work with the new openssl, or possibly sshfs which depends on openssl. Either way it was the change in openssl to version 8.8p1-1 that broke functionality of kdeconnect. I have entered a new report at https://bugs.kde.org/show_bug.cgi?id=443155 @zyf0330 your issue is most likely with android permission for storage. Note that on Android, in kdeconnect you have to click on the three dots menu on the top right, then select "Plugins Settings", then in "Share and Receive" click on "Target Folder" to select a folder. That open the android file selector (left top hamburger menu to change section in the file selector, ie internal storage, recent files, etc) in which you go to your folder in the storage and click at the bottom of the page on "Authorize access to xxx". This is required even to send files from a folder. You have to authorize the application to send files from a folder on android 11. This way I am able to send files from the Debian computer to the Android tablet and from tablet to computer. ssh is 1:8.4p1-5 (Debian stable). Currently I have issues with my computer mount phone folder option (ie "Expose filesystems" in "Plugins Settings"). Telling your android version might help narrow the issue in case it is another one. Also, look at your firewall, https://fitzcarraldoblog.wordpress.com/2014/02/10/kde-connect-link-your-android-device-to-your-kde-desktop/ tells the rules for ufw. At now, I can send files from android phone to Ubuntu successfully. And I don't need to do filesystem expose. I think Filesystem expose is needed for browser files in the phone from computer. And I don't know why I cannot set Download folder as storage location, just folders inside Download. Sorry I am lost. Do you mean you tried to set download folder as and authorize it i. "Share and receive". I only talked about "Filesystem Expose" because it is the only area where I jave issue with kdeconnect (and only on Android 11, 10 is fine). To send from or to the phone this is not related. Only authorize in "Share and receive" does. Do you mean you the authorize access button at the bottom is greyed out when you select the download folder in "Share and receive" folder location ? (In reply to Alban BROWAEYS from comment #10) > Sorry I am lost. Do you mean you tried to set download folder as and > authorize it i. "Share and receive". > I only talked about "Filesystem Expose" because it is the only area where I > jave issue with kdeconnect (and only on Android 11, 10 is fine). > To send from or to the phone this is not related. Only authorize in "Share > and receive" does. > Do you mean you the authorize access button at the bottom is greyed out when > you select the download folder in "Share and receive" folder location ? Yes (In reply to Alban BROWAEYS from comment #10) > Sorry I am lost. Do you mean you tried to set download folder as and > authorize it i. "Share and receive". > I only talked about "Filesystem Expose" because it is the only area where I > jave issue with kdeconnect (and only on Android 11, 10 is fine). > To send from or to the phone this is not related. Only authorize in "Share > and receive" does. > Do you mean you the authorize access button at the bottom is greyed out when > you select the download folder in "Share and receive" folder location ? Sorry. I read it wrong. I mean Download is grayed out in Filesystem expose. Anyway, the original isue is resolved. |