On 11/30/2012 03:45 AM, John Andersen wrote:

On 11/29/2012 8:21 PM, Jim Sabatke wrote:

...

1. Booting with the h390 plugged in results in the headset not working. 2. Booting with the h390 plugged I can login to a user, but then the keyboard is totally unresponsive. The mouse still works. 3. Booting with the h390 unplugged and then logging into a user, and THEN plugging the h390 in allows the h390 and keyboard to function properly. 4. After step 3, locking the computer, or going into the sleep mode, and then returning to the user still allows the h390 and keyboard to function. 5. After step 3, switching to another user disables the h390 and the keyboard. 6. After step 5, switching back to the original user enables the h390 and keyboard. Do you have more than one USB header on the mother board that you can use? Like maybe one on the back and one on the front of the box?

In the past, I've had USB devices conflict but was able to get them to behave by keeping the conflicting devices on different USB controllers.

It almost sounds like the headset is run out of the user's account, but surely the keyboard should not be.

I'm not sure I know enough about USB to answer that, but I've certainly been trying to learn for the past 12+ hours. Here is the output for lsusb if that helps at all. I could be wrong, but I wouldn't think the build-in laptop keyboard would be a USB device: ipley:/home/jim/software/usb-headset-button-0.9.2 # lsusb Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b1aa Chicony Electronics Co., Ltd Webcam-101 Bus 002 Device 004: ID 046d:0a0c Logitech, Inc. Clear Chat Comfort USB Headset Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Obviously the offending devices is Bus 002 Device 004 Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11/30/2012 03:59 AM, John Andersen wrote:

On 11/30/2012 1:51 AM, Jim Sabatke wrote:

...

On 11/30/2012 03:45 AM, John Andersen wrote:

...

On 11/29/2012 8:21 PM, Jim Sabatke wrote:

...

1. Booting with the h390 plugged in results in the headset not working. 2. Booting with the h390 plugged I can login to a user, but then the keyboard is totally unresponsive. The mouse still works. 3. Booting with the h390 unplugged and then logging into a user, and THEN plugging the h390 in allows the h390 and keyboard to function properly. 4. After step 3, locking the computer, or going into the sleep mode, and then returning to the user still allows the h390 and keyboard to function. 5. After step 3, switching to another user disables the h390 and the keyboard. 6. After step 5, switching back to the original user enables the h390 and keyboard. Do you have more than one USB header on the mother board that you can use? Like maybe one on the back and one on the front of the box?

In the past, I've had USB devices conflict but was able to get them to behave by keeping the conflicting devices on different USB controllers.

It almost sounds like the headset is run out of the user's account, but surely the keyboard should not be.

I'm not sure I know enough about USB to answer that, but I've certainly been trying to learn for the past 12+ hours. Here is the output for lsusb if that helps at all. I could be wrong, but I wouldn't think the build-in laptop keyboard would be a USB device:

ipley:/home/jim/software/usb-headset-button-0.9.2 # lsusb Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b1aa Chicony Electronics Co., Ltd Webcam-101 Bus 002 Device 004: ID 046d:0a0c Logitech, Inc. Clear Chat Comfort USB Headset Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse

Obviously the offending devices is Bus 002 Device 004

Jim

Try swapping the ports that the webcam and the headset are plugged into. Where is the keyboard plugged in?

I only have 3 USB ports available on the laptop. If I can switch the ports for the built-in camera and keyboard, I am not aware of how to do that. I have tried the mouse and the headset in each of the available ports and it makes no difference. I am now totally exhausted and will look into reassigning ports for built-in peripherals after I get some sleep. I know there is nothing in bios for that. Thanks, Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11/30/2012 04:15 AM, John Andersen wrote:

On 11/30/2012 2:11 AM, Jim Sabatke wrote:

...

I only have 3 USB ports available on the laptop.

I see, I wasn't aware it was a laptop. So it appears all the devices you plug in are going to be on Bus 002. Sounds like your best bet is as Philipp says, with a bug report.

Bug report filed. Took me a while to go through the previously filed ones to make sure this was new, which it appears to be. Thanks, Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, 02 Dec 2012 00:46:41 -0600, Jim Sabatke wrote:

Bug report filed.

In such cases please always post the bug number so that others can see the bug and it's possible resolution later on, even when they search the mailing list archive. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11/30/2012 04:03 AM, Philipp Thomas wrote:

On Fri, 30 Nov 2012 03:51:37 -0600, Jim Sabatke wrote:

...

1. Booting with the h390 plugged in results in the headset not working. 2. Booting with the h390 plugged I can login to a user, but then the keyboard is totally unresponsive. The mouse still works. 3. Booting with the h390 unplugged and then logging into a user, and THEN plugging the h390 in allows the h390 and keyboard to function properly. 4. After step 3, locking the computer, or going into the sleep mode, and then returning to the user still allows the h390 and keyboard to function. 5. After step 3, switching to another user disables the h390 and the keyboard. 6. After step 5, switching back to the original user enables the h390 and keyboard. I'd recommend opening a bug report in https://bugzilla.novell.com. That way it will reach our USB guru and you might get helpful advice.

Philipp

I will certainly do that if I can't work this out with the port switching advice. Thanks, Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, Nov 30, 2012 at 8:17 AM, Anton Aylward wrote:

Jim Sabatke wrote:

...

I needed a headset that doesn't use the standard headphone jack which has worn to the point where it is intermittent and will soon need pretty expensive service to work. So, I bought a Logitech h390 USB headset hoping that it would work on my openSuse 12.2 laptop (HP G72-B60US). I have all updates installed as of today.

[snip]

Hello, I have the same USB headset and got it working by installing pavucontrol. This solution assumes that you are using PulseAudio, # zypper in pavucontrol Then run pavucontrol and you should be able to find/configure your headset there. If not, run through the yast sound module and go through the configuration wizard for the headset once. Then pavucontrol again to enable. A bit of an annoyance to have to add another program to handle sound control, but it does work. - James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org