Arch Linux

MadCat_X

Member

Registered: 2009-10-08

Posts: 189

[SOLVED] Problems syncing iPod Touch - possible permissions issue

Hello,

I got my iPod Touch 1G repaired, loaded a fresg FW 3.1.3 on it and attempted to sync it using ifuse and gtkpod. However, when i ran "ifuse ~/iPod", I got

(gtkpod:3459): GLib-CRITICAL **: g_io_channel_write_chars: assertion `channel != NULL' failed

(gtkpod:3459): GLib-CRITICAL **: g_io_channel_shutdown: assertion `channel != NULL' failed

(gtkpod:3459): GLib-CRITICAL **: g_io_channel_unref: assertion `channel != NULL' failed
Segmentation fault

errors in the terminal and obviously nothing mounted. There were also

[   52.965344] ifuse[865]: segfault at 0 ip 00007f0b940b50b4 sp 00007ffff2e9b3b0 error 4 in libc-2.15.so[7f0b9404c000+199000]
[   67.813656] ifuse[867]: segfault at 0 ip 00007f2d1ecfe0b4 sp 00007fffdd51a1b0 error 4 in libc-2.15.so[7f2d1ec95000+199000]

lines in dmesg.

I was confused as this used to work perfectly before and after a bit of experimentation I added a new udev rule according to the Arch Wiki and gtkpod finally picked my iPod up.  Now when I tried to copy some music to my iPod, gtkpod crashed as well giving me the same error as ifuse. An interesting plottwist was when I tried to run gtkpod as root through kdesu - to my surprise everything worked. Running ifuse as root also mounts the iPod fine.

"lsusb -v | grep iSer" told me something about libusb needing write access to the device when it attempted to read the serial of the iPod. I'm quite sure this is some weird permission issue, but I have no idea where to look for it. Anybody of you guys have an idea?

Thanks.

Last edited by MadCat_X (2012-05-09 09:41:04)

MadCat_X

Member

Registered: 2009-10-08

Posts: 189

Re: [SOLVED] Problems syncing iPod Touch - possible permissions issue

I know it's a bit late, but I think I finally sorted this out. It turned out that ~/.config/libimobiledevice/RootPrivateKey.pem was owned by root instead of me and therefore couldn't be opened even for reading. This particular situation isn't handled by libimobiledevice so it just crashes at calling fwrite() giving very obscure errors in dmesg and gdb. Changing the ownership back to me fixed the problem.

(Anybody knows if the imobiledevice dev team has a bugzilla or mailing list? I reckon this is worth reporting...)