error 'Transport endpoint is not connected' after last ubuntu update of ulib

[ipovalyaev]

Seems after last update of udev and related libraries from ubuntu repository

from /var/log/apt/history.log

Upgrade: udev:amd64 (237-3ubuntu10.29, 237-3ubuntu10.33), libudev1:amd64 (237-3ubuntu10.29, 237-3ubuntu10.33), libudev-dev:amd64 (237-3ubuntu10.29, 237-3ubuntu10.33)

cli client started to raise error on accessing any file

cp: error reading 'file name from mount point': Transport endpoint is not connected

downgrading back to previous versions using

sudo apt install libudev-dev=237-3ubuntu10.29 udev=237-3ubuntu10.29 libudev1=237-3ubuntu10.29 

temporary addressed the issue and client is working.

Haven't done any further investigation what's gone wrong, however didn't found anything useful in neither pcloud nor system logs

[ceefour]

This happens with Ubuntu 20.04.3 , but there's no workaround:

$ sudo apt install libudev-dev=237-3ubuntu10.29 udev=237-3ubuntu10.29 libudev1=237-3ubuntu10.29 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Version '237-3ubuntu10.29' for 'libudev-dev' was not found
E: Version '237-3ubuntu10.29' for 'udev' was not found
E: Version '237-3ubuntu10.29' for 'libudev1' was not found

[tommythorn]

Doesn't work on Ubuntu 21.10 either. This is a major concern, please fix.

[tommythorn]

Ah, but building it from source fixes it. Seems like they just need to make a new release.

[edlutz]

The error is back. Ubuntu 22.04.

[davidcbenson]

I have some additional information. While I also get this same error, the files still seem to be syncing. The syncing is happening unusually slowly for the connection I have, but the syncing is happening nonetheless. I have also been able to fix the error by restarting the computer. When I have restarted the computer and the error is gone, all files are correctly synced. I currently have the error, and have several files syncing with incredibly long wait times, so I am trying to see if the completed sync removes the error or not.

Ubuntu 22.04 (btw)

EDIT: I deleted syncs until I had no files left to sync, and then restarted the computer. That fixed the problem, but obviously not super helpful as a workaround.

EDIT 2: After no more than a few hours, the client terminated, and I get the error again. Restarting the client restarts syncing of local folders, but not interaction with pCloudDrive.

[jirilebl]

I get the same issue on Debian 11. Restarting the computer helps for a few hours but that is extremely annoying.

[jirilebl]

killing pcloud for a moment and doing "fusermount -u -z ~/pCloudDrive" and then restarting pcloud seems a workaround that's less painful than rebooting.

[newptcai]

killing pcloud for a moment and doing "fusermount -u -z ~/pCloudDrive" and then restarting pcloud seems a workaround that's less painful than rebooting.

Wonderful. I got this problem on Ubuntu 22.04 this morning. Perhaps I updated something on Friday.

[diplodocuslongus]

fusermount -u -z ~/pCloudDrive

Well, I get a: fusermount: entry for ~/pCloudDrive not found in /etc/mtab with that, and the Transport endpoint is not connected remains, even after a reboot...

[burnsaustin145]

Currently having this problem on Ubuntu 22.04 . It started after I accidentally tried to install the Haskell IDE Engine from/on my drive. Unmounting with various umount and fusermount commands & rebooting don't fix. Still searching for a solution which doesn't involve becoming a cloud expert

[burnsaustin145]

I was able to fix my issue by deleting .pcloud from my home directory and rerunning ./pcloud.