Different encoding within files

Bug #1314379 reported by David Peters
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
owncloud-client (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description: Ubuntu 14.04 LTS
Release: 14.04
owncloud-client:
  Installed: 1.5.0+dfsg-4ubuntu1
  Candidate: 1.5.0+dfsg-4ubuntu1
  Version table:
 *** 1.5.0+dfsg-4ubuntu1 0

When syncing with owncloud-client it creates random encodings within the sync folder on the server.

If used webdav it does not occur.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: owncloud-client 1.5.0+dfsg-4ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Apr 29 15:37:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/owncloud
InstallationDate: Installed on 2013-10-09 (202 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: owncloud-client
UpgradeStatus: Upgraded to trusty on 2014-04-03 (26 days ago)

Revision history for this message
David Peters (daveshow) wrote :
Revision history for this message
David Peters (daveshow) wrote :

Thats odd why would a restart of the system. Fix the issue, here are the steps to the scenario.

1. installed a owncloud server.
2. Installed the certificate in the gnome key manager.
3. installed ownclient sudo apt-get install owncloud-client
4. Connected the ownclient to the server then trusted the cert through the client.
5. Was getting the sync issues with the random chars even tried different directories outside the home directory.
6. installed ownclient builddeps sudo apt-get build-dep owncloud-client
7. Same error as step 5
8. During the reboot process I did see something about a error due to encfs but there were no logs saved from this process. <== Unknown message
9. System start up and sync'd more files through the client no the issue has gone.

Now unable to replicate the issue. Since this issue is not occurring any more. Does this mean you must restart the system for this client to work? Does that make sense to anyone?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.