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

Bug #1214370 reported by Igor Zubarev
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libgpod (Ubuntu)
New
Undecided
Unassigned

Bug Description

iphone 5 insert

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: libgpod-common 0.8.2-7ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-3.6-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 20 09:37:32 2013
ExecutablePath: /lib/udev/iphone-set-info
InstallationDate: Installed on 2013-04-26 (116 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /lib/udev/iphone-set-info
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f0b4d6bcce6 <lockdownd_start_service+54>: movb $0x0,0x2(%rax)
 PC (0x7f0b4d6bcce6) ok
 source "$0x0" ok
 destination "0x2(%rax)" (0x6270000000000002) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: libgpod
Stacktrace:
 #0 0x00007f0b4d6bcce6 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-09 (41 days ago)
UserGroups:

Revision history for this message
Igor Zubarev (igor.zubarev) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1212546, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.