| Summary: | sys-power/upower deadlocks with dev-libs/libusbx | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Bartosz Brachaczek <b.brachaczek> |
| Component: | [OLD] Core system | Assignee: | Peter Stuge <peter> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | base-system, freedesktop-bugs |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | dead locked upowerd stacktrace | ||
|
Description
Bartosz Brachaczek
2013-08-09 23:26:46 UTC
-r3 is already applying 2 patches for different deadlocks wrt https://bugzilla.redhat.com/show_bug.cgi?id=985484 0001-linux-Use-a-separate-lock-to-serialize-start-stop-vs.patch 0002-hotplug-Remove-use-of-pthread_cancel-from-linux_udev.patch I haven't been able to reproduce this despite using UPower with libusbx-1.0.16-r3 all the time, but maybe I just haven't noticed so I'd prefer if you would push it yourself to the upstream mailing list at, https://lists.sourceforge.net/lists/listinfo/libusbx-devel Mention you already have those two patches from above applied so they don't confuse this issue. And you can also try USE="-udev" in dev-libs/libusbx if you want to avoid the issue. No, I'm not sure if that will work or not. Okay, now that I think about that, I'm not really sure which version of libusbx was actually being used by upowerd when it dead locked, as I didn't reboot/restart the daemon in a couple of days. I'll see if it happens again and then hit upstream if it does. (In reply to Bartosz Brachaczek from comment #2) > Okay, now that I think about that, I'm not really sure which version of > libusbx was actually being used by upowerd when it dead locked, as I didn't > reboot/restart the daemon in a couple of days. I'll see if it happens again > and then hit upstream if it does. I'll close this bug now, please simply reopen it if you still see the need. Thanks! |