Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Torrent containing folder with ñ gives error in transmission (only in xbian, encoding related?) #512

Closed
trumanbaltar opened this issue Mar 16, 2014 · 11 comments

Comments

@trumanbaltar
Copy link

Running Transmission 2.82 installed from xbian-config in Xbian 1.0 Beta 1.1.

When I add a torrent to Transmission that would download a folder containing files and the folder name contains an ñ. As soon as it tries to create the folder it fails and gives an Invalid Argument (Path to file).
Posted in the Transmission forum https://forum.transmissionbt.com/viewtopic.php?f=8&t=9913 (last post on that page and following). Told me must be related to Xbian cause usually Transmission deals well with special characters (and Transmission on a Mac downloads with the ñ fine).

@mk01
Copy link
Member

mk01 commented Mar 16, 2014

@trumanbaltar

you will have nice pingpong now as XBian uses by default UTF-8 as Debian and ñ is no problem in directory name nor file name nor anything else. locale is set to en_US.UTF-8 by default as well.

you can see that if running "env" from console.

@trumanbaltar
Copy link
Author

I see. To be honest I'm not a big ping pong fan. Maybe you could try
replicating the error? Any torrent with the word Español would suffice.
That ought to shed some light on the problem.

On 17/03/2014, at 00:03, Matus Kral notifications@github.com wrote:

@trumanbaltar https://github.com/trumanbaltar

you will have nice pingpong now as XBian uses by default UTF-8 as Debian
and ñ is no problem in directory name nor file name nor anything else.
locale is set to en_US.UTF-8 by default as well.

you can see that if running "env" from console.

Reply to this email directly or view it on
GitHubhttps://github.com//issues/512#issuecomment-37774528
.

@mk01
Copy link
Member

mk01 commented Mar 17, 2014

@trumanbaltar

agree with ping-pong not being popular. in between I was checking the transmission package (the xbian changes to upstream) for any possible causes but there are none. actually XBian put no changes to code itself, only bundling service stop / start scripts and default confs.

I can grap and recompile upstream and rebudle into new XBian package, will get back to you and ask for test. If you end up then with the same problem, I will install & test myself - but this will last step. fine?

@trumanbaltar
Copy link
Author

Agreed! Thanks!

On 17/03/2014, at 10:53, Matus Kral notifications@github.com wrote:

@trumanbaltar https://github.com/trumanbaltar

agree with ping-pong not being popular. in between I was checking the
transmission package (the xbian changes to upstream) for any possible
causes but there are none. actually XBian put no changes to code itself,
only bundling service stop / start scripts and default confs.

I can grap and recompile upstream and rebudle into new XBian package, will
get back to you and ask for test. If you end up then with the same problem,
I will install & test myself - but this will last step. fine?

Reply to this email directly or view it on
GitHubhttps://github.com//issues/512#issuecomment-37798892
.

@mk01
Copy link
Member

mk01 commented Mar 24, 2014

@trumanbaltar

package to test

http://xbian.brantje.com/others/xbian-package-transmission2.82.deb

sudo -i
wget http://xbian.brantje.com/others/xbian-package-transmission2.82.deb
dpkg -i xbian-package-transmission2.82.deb

@trumanbaltar
Copy link
Author

@mk01

Thank you so much for your effort.
So I've tested it. During dpkg it demanded libminiupnpc5 as a missing dependency. I installed it and ran again.
And again I get the same error when Transmission is about to create the folder with the ñ name.
So I kindly ask you to try and replicate the error.
One last thing, do you think if I were to upgrade to Beta 2.0 I would get the same error?

Thanks a lot again!

@mk01
Copy link
Member

mk01 commented Mar 25, 2014

yes. there is no reason to be handled this differently on 2.0, 1.1 or RC1. but my test scenario will be RC1. anyhow what is your filesystem ?

and can you provide config files?

@trumanbaltar
Copy link
Author

I've tried downloading in /home/xbian, which would be btrfs, and to an external drive formated as FAT32. Same result in both.
And the config file for transmission you can find it here:
http://pastebin.com/jwucHCLG

Anything else?

@mk01
Copy link
Member

mk01 commented Mar 26, 2014

no that will be enough. if you of course also sent magnet link to the special torrent.

@trumanbaltar
Copy link
Author

It was that indeed. Adding in fstab the option utf8=true to mount the vfat
partition fixed the problem.
What I don't understand is why it wouldn't work in the root file system. Or
does it also need a special option when mounting?

On 26/03/2014, at 03:46, Matus Kral notifications@github.com wrote:

no that will be enough. if you of course also sent magnet link to the
special torrent.

Reply to this email directly or view it on
GitHubhttps://github.com//issues/512#issuecomment-38644945
.

@mk01
Copy link
Member

mk01 commented Apr 3, 2014

@trumanbaltar

root as xbian's root so btrfs filesystem? that would be weird.
and of course mount options of that type are not general - valid across all filesystems.

PM me on xbian forum. I have a setup to test.

@mk01 mk01 closed this as completed Apr 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants