touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #42435
[Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()
After reading the patch, why patch upowerd to compensate for the idevice
client libraries not doing their full job in the first place? Of course,
upowerd should be able to handle memory handling exceptions regardless,
but I'd like to think that it would be bit more abstracted - like for
instance: "if mobileclient is not free, then free mobileclient." Are
their similar conditionals in the daemon for each individual mobile
device type (Android/Windows Phone/Blackberry)?
I do agree that the Ubuntu maintainers should probably have done
something before now for an LTS release though - even if it is only
applying the daemon patch that plays more nicely with a naughty client
library.
In the spirit of sharing, I hope I have at least given some who stumble
onto this in their search results a bit of relief. All I know is that
before the one package install, this bug was 100% reproducible and 0%
afterward. I should also note: I am running in an amd64 environment, so
32-bit user feedback could be helpful.
Potential solutions for end users:
1. Install related package via apt and provide feedback (it may not solve it for you - won't know without feedback)
2. Install developer packages, download upowerd source package, apply patch, compile source, and install new package
3. Wait on the developers to patch upowerd to assist client libraries that are not doing their job, and just ignore that constant core dump pop-up without any feedback
Thanks...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1305699
Title:
upowerd crashed with SIGSEGV in service_client_free()
Status in upower package in Ubuntu:
Confirmed
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 (20140326)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0xb74e9919 <service_client_free+25>: mov (%esi),%eax
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
StacktraceTop:
service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
property_list_service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
?? ()
g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: upowerd crashed with SIGSEGV in service_client_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+subscriptions