iphone-set-info crashed with SIGSEGV in lockdownd_start_service()

Bug #1212546 reported by Michael Tinsay
120
This bug affects 12 people
Affects Status Importance Assigned to Milestone
libgpod (Ubuntu)
Fix Released
High
Loïc Minier

Bug Description

Connected my iPod Touch device and this error happened.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: libgpod-common 0.8.2-7ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
Date: Wed Aug 14 14:45:15 2013
ExecutablePath: /lib/udev/iphone-set-info
InstallationDate: Installed on 2012-06-26 (414 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /lib/udev/iphone-set-info
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7faccc04ce66 <lockdownd_start_service+438>: jl 0x7faccc04ce8c <lockdownd_start_service+476>
 PC (0x7faccc04ce66) ok
 source "0x7faccc04ce8c" (0x7faccc04ce8c) ok
 SP (0x7fff14a50670) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: libgpod
Stacktrace:
 #0 0x00007faccc04ce66 in lockdownd_start_service () from /usr/lib/libimobiledevice.so.4
 No symbol table info available.
 #1 0x0000000000401690 in _start ()
 No symbol table info available.
StacktraceTop:
 lockdownd_start_service () from /usr/lib/libimobiledevice.so.4
 _start ()
Title: iphone-set-info crashed with SIGSEGV in lockdownd_start_service()
UpgradeStatus: Upgraded to saucy on 2013-07-11 (35 days ago)
UserGroups:

Revision history for this message
Michael Tinsay (tinsami1) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 lockdownd_start_service (client=<optimized out>, identifier=identifier@entry=0x40199d "com.apple.afc", service=service@entry=0x7fff14a506ba) at lockdown.c:1598
 iphone_write_sysinfo_extended (uuid=uuid@entry=0x7fff14a50e8e "eedb91984e6399634dfc557a3decadeacf7a1ca8", xml=xml@entry=0x1e78290 "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<!DOCTYPE plist PUBLIC \"-//Apple//DTD PLIST 1.0//EN\" \"http://www.apple.com/DTDs/PropertyList-1.0.dtd\">\n<plist version=\"1.0\">\n<dict>\n\t<key>64Bit</key>\n\t<integer>3"...) at ../../../tools/ipod-lockdown.c:153
 write_sysinfo_extended (uuid=0x7fff14a50e8e "eedb91984e6399634dfc557a3decadeacf7a1ca8") at ../../../tools/iphone-callout.c:21
 main (argc=<optimized out>, argv=<optimized out>) at ../../../tools/iphone-callout.c:63

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in libgpod (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libgpod (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
Revision history for this message
Loïc Minier (lool) wrote :

This is probably fixed with upstream e620b2f "Adjust to latest libimobiledevice API changes", as seen in http://sourceforge.net/p/gtkpod/libgpod/ci/master/tree/.

Loïc Minier (lool)
Changed in libgpod (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Loïc Minier (lool)
importance: Medium → High
Loïc Minier (lool)
information type: Private → Public
Revision history for this message
Loïc Minier (lool) wrote :

libgpod (0.8.2-7ubuntu3) saucy; urgency=low

  * New patch, 70_adjust-to-latest-libimobiledevice-API-changes, cherry-pick
    e620b2f from upsteam to fix breakage with libimobiledevice 1.1.5.
 -- Loic Minier <email address hidden> Mon, 02 Sep 2013 10:24:40 +0200

Changed in libgpod (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

seems like that's still an issue (looking to errors.ubuntu.com reports)

Revision history for this message
Sebastien Bacher (seb128) wrote :

ignore that, the issue is in libimobiledevice

Revision history for this message
Loïc Minier (lool) wrote :

I personally had this issue in the past, and it went away with the fix; I can't reproduce the issue by just plugging a device (just checked again with final saucy packages)

I suspect there might be another issue, probably crashing in the same place (init path) with specific iOS / device combinations, or perhaps specific data or Ubuntu apps; would be good to get one of the new crashes retraced to diagnose this.

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.