Description of problem:
Just charging the iPhone battery.
Version-Release number of selected component:
Thread no. 1 (4 frames)
#0 __strlen_sse2_pminub at ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:38
#1 plist_get_string_val at /usr/src/debug/libplist-1.8/src/plist.c:541
#2 read_sysinfo_extended_by_uuid at ipod-lockdown.c:81
#3 write_sysinfo_extended at iphone-callout.c:15
Created attachment 710383 [details]
Created attachment 710384 [details]
Created attachment 710385 [details]
Created attachment 710386 [details]
Created attachment 710387 [details]
Created attachment 710388 [details]
Created attachment 710389 [details]
Created attachment 710390 [details]
Created attachment 710391 [details]
Created attachment 710392 [details]
Created attachment 710393 [details]
Created attachment 710394 [details]
Can you run 'ideviceinfo -x -k SerialNumber' from a terminal with your iPhone plugged and paste what appears on the terminal (feel free to replace the SerialNumber value with XXXXXX)? It's possible that it will return without displaying anything, in which case that's also useful info :)
*** Bug 955709 has been marked as a duplicate of this bug. ***
libgpod-0.8.3-1.fc20 has been submitted as an update for Fedora 20.
libgpod-0.8.3-1.fc19 has been submitted as an update for Fedora 19.
libgpod-0.8.3-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libgpod-0.8.3-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
libgpod-0.8.3-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
libgpod-0.8.3-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
libgpod-0.8.3-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.