For what it is worth, since the powers that be have deemed the bug

iPhone handling on Ubuntu 14.04 LTS is quite broken. You plug in an
iPhone, upowerd crashes. You plug it out, then back in, and you get an
error message that the iPhone is already mounted. You unplug the iPhone,
reboot, and upowerd crashes. Not nice. :-(

The patch from comment #7 is obviously correct. It has been accepted
upstream. It is very small. Pretty please with sugar on top, backport
this fix (i.e. just apply the patch and rebuild the package!) for


You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.

  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
  ProcCmdline: /usr/lib/upower/upowerd
   Segfault happened at: 0xb74e9919 <service_client_free+25>:   mov    
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e0000) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
   service_client_free () from /usr/lib/i386-linux-gnu/
   property_list_service_client_free () from 
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to