On Sat, Jun 20, 2015 at 8:19 PM, Cristian Rodríguez wrote:

I just looked at the suspiciuos failures of apps linking to libusb.. This is a bug introduced by https://build.opensuse.org/package/view_file/hardware/libusb-compat/libusb-c... and has nothing to do with the compiler switch. That patch is going to break something else sooner or later anyway all to please a buggy proprietary tool..:-|

Christian, indeed, Stanislav and me came to the same conclusion on Friday - that patch will temporarily be disabled until Stanislav can find a better approach of fixing this - hopefully next time around without the negative impact. For now, the biggest worry I have in Tumbleweed is the fact that p11-kit no longer passed the test suite (make check, which, sadly enough, is not enabled in the package). It seems to have issues with libffi, resulting in a lot of fails, as soon as certificates are involved (most of the java failures, KDE3 failures, many more) This has been logged as https://bugzilla.opensuse.org/show_bug.cgi?id=935510 Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Sun, Jun 21, 2015 at 4:50 AM, Ilya Chernykh wrote:

...

I just looked at the suspiciuos failures of apps linking to libusb.. This is a bug introduced by https://build.opensuse.org/package/view_file/hardware/libusb-compat/libusb-c... and has nothing to do with the compiler switch. That patch is going to break something else sooner or later anyway all to please a buggy proprietary tool..:-|

I am sure this package is not involved. I made a patch to what actually causes the failures in file named "libusb": https://build.opensuse.org/request/show/312876

In this sample, you're right: libusb is not involved... but if you check the status overview [0] then this one was also not tagged to be affected by libusb at all. The patch in libusb-compat keeps on being the source for a problem; SR#312910 currently disables this patch, giving Stanislav the time to find an actual fix to the problem. Cheers, Dominiquee [0] https://goo.gl/7EuFdQ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Sun, Jun 21, 2015 at 1:31 PM, Cristian Rodríguez wrote:

On Sun, Jun 21, 2015 at 7:37 AM, wrote:

...

* libusb-compat: a patch that attempted to fix closed source softare has some negative effects. An SR, disabling the patch for now, is pending against the devel prj (SR#312910)

In the meanwhile I have reduced the number of packages that (build)require this library. some components have already migrated to libusb1 since the rpm specs were written, others do not use it and so on..

From the "important things" only plasma 5 (!!) and gpg still uses the old libusb..the other packages are secondary concerns. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Monday, July 06, 2015 01:41:16 AM Stefan Bruens wrote:

On Sunday 05 July 2015 16:05:31 Cristian Rodríguez wrote:

...

On Sun, Jun 21, 2015 at 1:31 PM, Cristian Rodríguez

wrote:

...

On Sun, Jun 21, 2015 at 7:37 AM, wrote:

...

* libusb-compat: a patch that attempted to fix closed source softare has some negative effects. An SR, disabling the patch for now, is pending against the devel prj (SR#312910)

In the meanwhile I have reduced the number of packages that (build)require this library. some components have already migrated to libusb1 since the rpm specs were written, others do not use it and so on..

From the "important things" only plasma 5 (!!) and gpg still uses the old libusb..the other packages are secondary concerns.

Plasma uses it for the mouse configuration panel. It is used for configuration of older Logitech mice, the code is probably derived from LoMoCo.

1. It is used to configure some "advanced" functionality, e.g. sensor resolution, but nothing basic 2. It only works for quite old mice (one of the newest, MX1000 cordless laser, is from 2004) [1] 3. It does not work out of the box anyway, due to unsufficient permissions for direct device access:

terminal output: kcmshell5: Error opening usbfs file: Keine Berechtigung strace output: [pid 13231] open("/dev/bus/usb/002/010", O_RDWR) = -1 EACCES (Permission denied)

"You have a Logitech Mouse connected, and libusb was found at compile time, but it was not possible to access this mouse. This is probably caused by a permissions problem - you should consult the manual on how to fix this."

So, lets just disable it.

Follow up, after Stefan's submit request i've sent 2 patches upstream to remove logitech/libusb related code, and allow rest of the kcm to build. So with plasma 5.4, this code is no more. Cheers, Hrvoje

Kind regards,

Stefan

[1] http://quickgit.kde.org/?p=plasma-desktop.git&a=blob&f=kcms%2Finput%2Fmous e.cpp