chromeos-filesystem-webdav icon indicating copy to clipboard operation
chromeos-filesystem-webdav copied to clipboard

Unable to write to WebDAV volume doing a print to PDF

Open dnikkel opened this issue 9 years ago • 2 comments

Hi,

I've encountered a second issue. From the browser, I was trying to do a print to PDF and save the PDF on my Synology NAS. When I hit the save button, nothing happened - the PDF was not written, the dialog did not dismiss, there was no error reported. I switched to saving in the download folder and it worked as expected. I could then copy the file to the Synology NAS from within the file manager. So the basics of saving a file are there, it's just not working from the print to PDF feature.

Dave

dnikkel avatar Apr 14 '15 18:04 dnikkel

I have the same problem with storing to a owncloud-webdav implementation running on top of nginx&php5-fpm and lighttpd-webdav behind a nginx as reverse proxy. I think it is not special to printing to PDF as I encountered the same problem (storing directly to webdav does not work; storing to Download and then copying to webdav works) when doing something else (sad thing is I don't remember what it was).

matthias11-21 avatar Jul 21 '15 07:07 matthias11-21

Same issue over here, the problem occurs with owncloud via webdav. /var/log/ui/ui.LATEST records the following errormessages once the save button via cloud print is triggered:

[27324:27500:1224/144217:ERROR:private_api_file_system.cc(110)] Cannot statvfs() the name length limit for: /provided/hmckflbfniicjijmdoffagjkpnjgbieh:webdavfs:%2F%2Fme%2Fhttps:%2F%2Ffff%2Emydomain%2Ecom:10000%2Fremote%2Ephp%2Fwebdav:d6265d427ca6160a488b9dac671946d47d580387
[27324:27324:1224/144219:ERROR:private_api_util.cc(98)] NOTREACHED() hit.

vdagamb avatar Dec 24 '15 14:12 vdagamb