Bug#806324: qgis: FTBFS on testing (unrecognized relocation in linking stage)

2015-11-29 Thread Olivier MATZ 
Hello,

I confirm Yorik's analysis: I have the same issue while compiling
Freecad from mainstream sources on my testing.

I downgraded the following packages to these versions:

libqt4-dbus_4.8.7+dfsg-3_amd64.deb
libqt4-declarative_4.8.7+dfsg-3_amd64.deb
libqt4-designer_4.8.7+dfsg-3_amd64.deb
libqt4-dev_4.8.7+dfsg-3_amd64.deb
libqt4-dev-bin_4.8.7+dfsg-3_amd64.deb
libqt4-help_4.8.7+dfsg-3_amd64.deb
libqt4-network_4.8.7+dfsg-3_amd64.deb
libqt4-qt3support_4.8.7+dfsg-3_amd64.deb
libqt4-script_4.8.7+dfsg-3_amd64.deb
libqt4-scripttools_4.8.7+dfsg-3_amd64.deb
libqt4-sql_4.8.7+dfsg-3_amd64.deb
libqt4-svg_4.8.7+dfsg-3_amd64.deb
libqt4-test_4.8.7+dfsg-3_amd64.deb
libqt4-xml_4.8.7+dfsg-3_amd64.deb
libqt4-xmlpatterns_4.8.7+dfsg-3_amd64.deb
libqtcore4_4.8.7+dfsg-3_amd64.deb
libqtdbus4_4.8.7+dfsg-3_amd64.deb
libqtgui4_4.8.7+dfsg-3_amd64.deb
qdbus_4.8.7+dfsg-3_amd64.deb
qt4-linguist-tools_4.8.7+dfsg-3_amd64.deb
qt4-qmake_4.8.7+dfsg-3_amd64.deb

And after that the build worked.

Regard,
Olivier

Bug#664068: USB MIDI keyboard fails to initialize

2013-01-06 Thread Olivier MATZ 
Hi Jonathan,

I'm running a 3.7.1 kernel. I first checked that the issue was still
present in this kernel: it failed 4 times among 5 tests.

Then I applied the 2 patches that you provided on top of the same
kernel (3.7.1), and I can confirm that it worked 5 times among 5.

Let me know if you need more info or tests.

Regards,
Olivier


On 12/29/2012 11:18 AM, Jonathan Nieder wrote:
 # approximating (3.6.5 upstream)
 found 664068 linux/3.6.4-1~experimental.1
 # v3.8-rc1~29^2~45 (ALSA: usb-audio: Fix missing autopm for MIDI
 # input, 2012-12-03), which is part of 3.2.36-rc1
 tags 664068 + upstream patch fixed-upstream moreinfo
 quit
 
 Olivier MATZ wrote:
 
 Here are the results of the tests, done on a kernel 3.6.5.

 1/ vanilla kernel, AUTOSUSPEND_USBID_BLACKLIST=

0% of success among 5 tests
 
 Thanks again for the quick testing.
 
 Please test the attached patch series against a 3.2.y or 3.7.y kernel,
 for example following the instructions from [1].
 
 Regards,
 Jonathan
 
 [1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2
 or the corresponding page from the debian-kernel-handbook package


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#664068: USB MIDI keyboard fails to initialize

2012-11-25 Thread Olivier MATZ 
Hi Jonathan,

 Gentle ping.

Thank you for the reminder, it was in my todo list since a long time
and your message increased the priority :)

Here are the results of the tests, done on a kernel 3.6.5.

1/ vanilla kernel, AUTOSUSPEND_USBID_BLACKLIST=

   0% of success among 5 tests

2/ vanilla kernel, AUTOSUSPEND_USBID_BLACKLIST=0763:019b

   100%  of success among 5 tests

3/ apply 0002-usb-add-USB_QUIRK_RESET_RESUME-for-M-Audio-49.patch,
   AUTOSUSPEND_USBID_BLACKLIST=

   0% of success among 5 tests

   I did not apply the first patch because it is already present in
   the kernel.

4/ apply the attached patch (a slightly modified version of yours),
   AUTOSUSPEND_USBID_BLACKLIST=

   100%  of success among 5 tests

   So, I think it validates the attached patch.

I also attached lsusb and the output of also-info.sh in case you still
want to see them. Let me know if you need more tests or debug outputs.

Regards,
Olivier
From b581fcd59bcdb1e116682dbbcdc42db55a3609bc Mon Sep 17 00:00:00 2001
From: Jonathan Nieder jrnie...@gmail.com
Date: Tue, 8 May 2012 13:06:41 -0500
Subject: [PATCH] usb: add USB_QUIRK_RESET_RESUME for M-Audio 49

Some USB MIDI keyboards fail to operate after a USB autosuspend.  The
device is recognized by ALSA, but no events are received and the
device goes quiet.

	$ amidi -l
	Dir DeviceName
	IO  hw:1,0,0  Oxygen 49 MIDI 1
	$ amidi -p hw:1,0,0 -d
	... play some notes ...
	^C
	0 bytes read

A workaround is to disable USB autosuspend for these devices by
putting AUTOSUSPEND_USBID_BLACKLIST=0763:2027 in
/etc/laptop-mode/conf.d/usb-autosuspend.conf.  In the spirit of commit
166cb70e97bd (usb: add USB_QUIRK_RESET_RESUME for M-Audio 88es),
reset the device on resume so this workaround is not needed any more.

Addresses http://bugs.debian.org/664068

Reported-by: David Banks amoe...@gmail.com
Reported-by: Olivier MATZ z...@droids-corp.org
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
 drivers/usb/core/quirks.c |4 
 1 file changed, 4 insertions(+)

diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index e77a8e8..dd8dba4 100644
--- a/drivers/usb/core/quirks.c
+++ b/drivers/usb/core/quirks.c
@@ -105,6 +105,10 @@ static const struct usb_device_id usb_quirk_list[] = {
 	/* Midiman M-Audio Keystation 88es */
 	{ USB_DEVICE(0x0763, 0x0192), .driver_info = USB_QUIRK_RESET_RESUME },
 
+	/* Midiman M-Audio Oxygen 49 */
+	{ USB_DEVICE(0x0763, 0x2027), .driver_info = USB_QUIRK_RESET_RESUME },
+	{ USB_DEVICE(0x0763, 0x019b), .driver_info = USB_QUIRK_RESET_RESUME },
+
 	/* M-Systems Flash Disk Pioneers */
 	{ USB_DEVICE(0x08ec, 0x1000), .driver_info = USB_QUIRK_RESET_RESUME },
 
-- 
1.7.10.4

upload=truescript=truecardinfo=
!!
!!ALSA Information Script v 0.4.61
!!

!!Script ran on: Sun Nov 25 20:33:42 UTC 2012


!!Linux Distribution
!!--

Debian GNU/Linux wheezy/sid \n \l PRETTY_NAME=Debian GNU/Linux wheezy/sid 
NAME=Debian GNU/Linux ID=debian


!!DMI Information
!!---

Manufacturer:  Sony Corporation
Product Name:  VPCZ12C5E
Product Version:   J0049V6X
Firmware Version:  R2074C3


!!Kernel Information
!!--

Kernel release:3.6.5+
Operating System:  GNU/Linux
Architecture:  x86_64
Processor: unknown
SMP Enabled:   Yes


!!ALSA Version
!!

Driver version: 1.0.25
Library version:1.0.25
Utilities version:  1.0.25


!!Loaded ALSA modules
!!---



!!Sound Servers on this system
!!

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - Yes

ESound Daemon:
  Installed - Yes (/usr/bin/esd)
  Running - No

Jack:
  Installed - Yes (/usr/bin/jackd)
  Running - Yes


!!Soundcards recognised by ALSA
!!-

 0 [Intel  ]: HDA-Intel - HDA Intel
  HDA Intel at 0xb642 irq 41
 1 [K49]: USB-Audio - KeyRig 49
  M-Audio KeyRig 49 at usb-:00:1d.0-1.5, full speed


!!PCI Soundcards installed in the system
!!--

00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)


!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!---

00:1b.0 0403: 8086:3b56 (rev 05)
Subsystem: 104d:905a


!!Modprobe options (Sound related)
!!

snd_pcsp: index=-2
snd_usb_audio: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_hda_intel: model=sony-assamd


!!Loaded sound module options
!!---


!!HDA-Intel Codec information
!!---
--startcollapse--

Codec: Realtek ALC889
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0889
Subsystem Id: 0x104d4400
Revision Id: 0x15
No Modem Function Group found
Default PCM:
rates

Bug#664068: USB MIDI keyboard fails to initialize

2012-06-07 Thread Olivier MATZ 
Hi Jonathan,

 I tested your patches on a 3.3.6 kernel and they work fine.

 Weird --- those patches don't do anything for 0763:019b.  Could you
 attach lsusb -v and alsa-info.sh --no-upload output[1]?

Indeed this is weird. I first tested it with a 3.4.0 kernel that without
the patch and it was not working. Then I rebooted on a patched 3.3.6
kernel and the midi keyboard was working. Of course, in both case, I
took care to revert /etc/laptop-mode/conf.d/usb-autosuspend.conf

But I agree with you that this is very surprising when we look at
patch as it does not match my vendor/device ID. Maybe it was just
luck, as the issue described initially by David seems to occur for
90% of tests. Or perhaps I was too fast and I hit a key before the
keyboard switched in powersave mode ?

Unfortunately I won't be able to do the test again before weeks as the
keyboard is currently not at my home (that's also why I took time to
answer and I was not able to test it more deeply). As soon as I can do
the test again, I will post requested info (lsusb and alsa-info).

Regards,
Olivier



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#664068: USB MIDI keyboard fails to initialize

2012-06-04 Thread Olivier MATZ 
Hello Jonathan,

I tested your patches on a 3.3.6 kernel and they work fine.

Thank you !
Olivier



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#664068: USB MIDI keyboard fails to initialize

2012-05-03 Thread Olivier MATZ 
Hello,

I have the same issue with my laptop and the same midi keyboard (M-Audio
KeyRig 49).

I think I found a workaround for this problem: if I disable power
management just after the midi keyboard is plugged, it seems it always
work:

1/ plug the keyboard
2/ wait less than 1 second
3/ then type as root: echo on  /sys/bus/usb/devices/2-1.1/power/control
   (the 2-1.1 has to be replaced by the ID on your USB bus)

I tested it 5 times and it was always working. I hope it can help
to understand the root cause of the problem. There is probably a way
to do that automatically when the device is plugged, I will post it
here if I find it.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#664068: USB MIDI keyboard fails to initialize

2012-05-03 Thread Olivier MATZ 
I found a clean way to disable power management for this device:

in /etc/laptop-mode/conf.d/usb-autosuspend.conf, I added:
AUTOSUSPEND_USBID_BLACKLIST=0763:019b

Seems to work well now.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org