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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1305699 Title: upowerd crashed with SIGSEGV in service_client_free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
