Gentoo Archives: gentoo-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] dev-libs/libusbx:1 the default provider for virtual/libusb:1 (for ~arch)
Date: Mon, 28 May 2012 20:51:58
In Reply to: Re: [gentoo-dev] dev-libs/libusbx:1 the default provider for virtual/libusb:1 (for ~arch) by Pacho Ramos
On 05/28/2012 02:02 AM, Pacho Ramos wrote:
> El dom, 27-05-2012 a las 17:16 -0700, Zac Medico escribió: >> On 05/27/2012 11:12 AM, Samuli Suominen wrote: >>> Fedora rawhide and ArchLinux switched to libusbx and followed suit in >>> our virtual/libusb:1. >>> Debian is considering the switch also. We'll see... >>> >>> I've been in contact with the new maintainer, and he assured me the >>> compability will be kept for libusb-compat. >>> >>> Happy testing, >>> >>> # emerge -C dev-libs/libusb:1 >>> # emerge -1 dev-libs/libusbx:1 >> >> I've tried this on my laptop, and afterwards it wouldn't suspend to ram >> when it was supposed to. I didn't do any real troubleshooting, so I'm >> just mentioning it here in case it helps someone else recognize the >> source of the problem. This was with sys-power/upower-0.9.16 and >> dev-libs/libusbx-1.0.11 (I didn't try to rebuild upower after switching >> from dev-libs/libusb-1.0.9 to dev-libs/libusbx-1.0.11). > > Maybe you should open a bug report for it to not forget that problem > (now that finally my laptop suspends even with upstream kernel and > without TOI wouldn't like to see it magically failing again without > remember the real culprit ;))
I've got it working now. The first time, when I had the suspend to ram issue, I did `emerge -1 dev-libs/libusbx:1` without unmerging libusb:1 first. The second time, I unmerged libusb:1 first (like Samuli's instructions said), and since then suspend to ram works fine. -- Thanks, Zac