| Summary: | I can't use KDE Connect to view or load files to the phone. | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | Quantos <quantos> |
| Component: | plasmoid | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | bugs.kde.org, swipe650 |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| URL: | http://imgur.com/WntENCI | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Quantos
2016-06-03 17:08:54 UTC
I'm getting the same problem Jun 04 09:41:51 Nuc kdeconnectd[1356]: kdeconnect.plugin.sftp: Unmount QObject(0x0)
Jun 04 09:41:51 Nuc kdeconnectd[1356]: kdeconnect.plugin.sftp: Destroy mounter
Jun 04 09:41:51 Nuc plasmashell[830]: New Notification: "Motorola Moto G" "Failed to mount filesystem: device not responding" -1 & Part of: 0
Jun 04 09:41:51 Nuc plasmashell[830]: Guessing partOf as: 0
Jun 04 09:41:51 Nuc plasmashell[830]: Currrent active notifications: QHash()
Jun 04 09:41:51 Nuc kdeconnectd[1356]: kdeconnect.plugin.sftp: Timeout: device not responding
Jun 04 09:41:40 Nuc kdeinit5[3614]: kdeconnect.kio: Stat: QUrl("kdeconnect://2954d72373634ec2/")
Jun 04 09:41:40 Nuc kdeinit5[3614]: kdeconnect.kio: Setting host: "2954d72373634ec2"
Jun 04 09:41:40 Nuc kdeconnectd[1356]: kdeconnect.plugin.sftp: Starting loop to wait for mount
Jun 04 09:41:40 Nuc kdeconnectd[1356]: kdeconnect.plugin.sftp: Created mounter
Jun 04 09:41:40 Nuc kdeconnectd[1356]: kdeconnect.plugin.sftp: Mount device: "Motorola Moto G"
Jun 04 09:41:40 Nuc kdeinit5[3612]: kdeconnect.kio: ListDevice "2954d72373634ec2"
Jun 04 09:41:40 Nuc kdeinit5[3612]: kdeconnect.kio: Listing... QUrl("kdeconnect://2954d72373634ec2/")
Jun 04 09:41:40 Nuc kdeinit5[3612]: kdeconnect.kio: Setting host: "2954d72373634ec2"
Did this problem appear after the android app was upgraded to version 1.0? Possible duplicates: 364084, 364072, 364070, 363947. Yes, it was working fine for me a couple of weeks ago *** This bug has been marked as a duplicate of bug 363947 *** |