This headset works fine with twinkle on Fedora 16 and it shows up in KDE multimedia settings.

Does the headset have sound in any other apps? Music players, etc?

Ie, is it only twinkle, or does the headset just not output any sound for you?

I am using the Fedora 17 Live KDE x64 spin.

When i run (as root): authconfig --updateall 
then i am able to see the USB headset in phonon (kde multimedia) and it plays sound fine when you test it.

however there is still no sound in twinkle.

If you: 

a) install pavucontrol
b) start playing sound 
c) run pavucontrol and look in it what streams it sees, does it see the output? 
d) Can you switch the output to the headset?

Also, what audio settings do you have in twinkle? What output and input devices?

i installed pavucontrol

it does not see the C-Media USB Headphone Set at all.  Twinkle sees it and is configured to use it (speaker, ring tone and microphone).

I have another USB headset from Logitech. I plugged it in and pavucontrol sees it fine.
dmesg for the Logitech

[ 1363.272110] usb 5-2: new full-speed USB device number 4 using ohci_hcd
[ 1363.429152] usb 5-2: New USB device found, idVendor=046d, idProduct=0a0c
[ 1363.429162] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1363.429170] usb 5-2: Product: Logitech USB Headset
[ 1363.429175] usb 5-2: Manufacturer: Logitech
[ 1363.459171] ALSA sound/usb/mixer.c:846 6:0: cannot get min/max values for control 2 (id 6)
[ 1363.459191] ALSA sound/usb/mixer.c:846 1:0: cannot get min/max values for control 2 (id 1)
[ 1363.459207] ALSA sound/usb/mixer.c:846 2:0: cannot get min/max values for control 2 (id 2)
[ 1363.465308] input: Logitech Logitech USB Headset as /devices/pci0000:00/0000:00:13.0/usb5/5-2/5-2:1.3/input/input17
[ 1363.465871] generic-usb 0003:046D:0A0C.0006: input,hidraw2: USB HID v1.00 Device [Logitech Logitech USB Headset] on usb-0000:00:13.0-2/input3

however neither device works in twinkle. Also now, I get this error in twinkle after running pavuctonrol:

Critical: Cannot open ALSA driver for PCM playback: Device or resource busy

ok, next thing to try: 

yum remove alsa-plugins-pulseaudio
logout and back in
make sure pulseaudio isn't running 
run twinkle

Does it work in this case?

thinkpad:~ -> ps auxwww | grep pulseaudio
veillard 12046  0.1  0.2 618476  8676 ?        S<l  00:08   0:00 /usr/bin/pulseaudio --start --log-target=syslog
veillard 12221  0.0  0.0 109400   904 pts/3    S+   00:11   0:00 grep --color=auto pulseaudio
thinkpad:~ -> rpm -q alsa-plugins-pulseaudio
package alsa-plugins-pulseaudio is not installed
thinkpad:~ -> 

  pulseaudio gets restarted, even if I manually kill it, and no the sound 
still doesn't seems to go through,

Daniel

I did: 

yum remove alsa-plugins-pulseaudio
logged out / back in
had to kill pulseaudio (as it was still running)
so it is not running now

still no sound in twinkle

I installed Fedora 17 from the x86_64 DVD to the hard drive on a different machine and did :

yum -y update
yum install twinkle

plugged in the C-Media USB headset and still the same problem. So any updates as of today did not fix it either. Also tried with and without alsa-plugins-pulseaudio with no success.

I also tried to boot the old kernel 3.3.7-1.fc16.x86_64 same result as
3.3.7-1.fc17.x86_64 ... It was working on fc16 so it seems a problem higher
in the stack. Trying to rebuild the older twinkle twinkle-1.4.2-16.fc16
from sources also failed on F17 because it looks for libccrtp1 and it's
ccrtp-2.0.2 which is available (and the configure lookup fails).

Sounds works just fine with rythmnbox.
Twinkle also tend to not exit cleanly it get stuck and only kill -9
stops it. It is stuck there:

(gdb) where
#0  0x000000348260ddcd in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x000000348260b478 in _L_lock_33 () from /lib64/libpthread.so.0
#2  0x000000348260b39c in pthread_cond_destroy@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
#3  0x0000003b70643629 in ucommon::Conditional::~Conditional() ()
   from /lib64/libucommon.so.5
#4  0x0000003b71e3bbb0 in ost::AppLog::~AppLog() ()
   from /lib64/libccext2-1.8.so.0
#5  0x0000003482238f9a in __cxa_finalize () from /lib64/libc.so.6
#6  0x0000003b71e21ff3 in ?? () from /lib64/libccext2-1.8.so.0
#7  0x00007fffc43882c0 in ?? ()
#8  0x0000003481a0f4e7 in _dl_fini () from /lib64/ld-linux-x86-64.so.2

 It also crashes sometimes when attempting a call, but I didn't managed
to get a stack dump yet,

Daniel

Adding Rex here to see if he has any ideas from a kde side of things...

I just installed ekiga (an alternative SIP client to Twinkle) and tried with the C-media head/hand set. Ekiga works fine. It recognizes the headset and the sound is working fine. 

So i'd surmise that we have a problem with Twinkle itself?

I have the same problem with Twinkle under F17. I'm using an Audigy 2 ZS without pulseaudio. I have selected the correct sound device in the Twinkle preferences.

I can hear the ringing on incoming calls, hear the "dialing"-sound generated by twinkle on outgoing calls and the microphone is working correctly during phone calls, but during phone calls nothing can be heard. Sound is working perfectly in other applications.

I have also observed the crashes and twinkle not exiting properly, that are mentioned in Comment 10.

BTW linphone works well as a replacement for twinkle on F18, but that doesn't
fix the problem :-)

Daniel

Created attachment 593390 [details]
twinkle binary and some extra shared libs to make it run on f17. this binary works fine!

I have the same problem but with an internal mic/speaker
of my laptop. Works fine on fedora 15.

I copied the twinkle binary from f15.
That would not run as it requires some old shared
libraries. So I also copied the missing shared library.
I ended up with the following files from f15,
which I pout under $HOME/bin/twinkle-f15:

[mst@robin twinkle-f15]$ ls -l
total 23152
-rwxr-xr-x. 1 mst mst   997428 Jun 21 11:27 libboost_regex.so.1.46.0
-rwxr-xr-x. 1 mst mst   259264 Jun 21 11:26 libccext2-1.7.so.0
-rwxr-xr-x. 1 mst mst   293692 Jun 21 11:26 libccgnu2-1.7.so.0
-rwxr-xr-x. 1 mst mst   165412 Jun 21 11:26 libccrtp1-1.7.so.0
-rwxr-xr-x. 1 mst mst 14941824 Jun 21 11:27 libicudata.so.44
-rwxr-xr-x. 1 mst mst  1858032 Jun 21 11:27 libicui18n.so.44
-rwxr-xr-x. 1 mst mst  1316064 Jun 21 11:27 libicuuc.so.44
-rwxr-xr-x. 1 mst mst   174156 Jun 21 11:25 libzrtpcpp-1.4.so.0
-rwxr-xr-x. 1 mst mst  3682884 Jun 21 11:24 twinkle

if I now run 
LD_LIBRARY_PATH=$HOME/bin/twinkle-f15 $HOME/bin/twinkle-f15/twinkle

old twinkle starts and there I can hear sound fine.

I attached the tarball (32 bit fedora).

Note: this is 32 bit userspace. Is your architecture 32 bit too?

I also observed that twinkle binary copied from f15 exits fine.
Twinkle f17 does not exit when I select file/quit.

Ah, sounds like a similar issue as bug #830618  (kdelibs3), do folks experiencing this have 
https://admin.fedoraproject.org/updates/FEDORA-2012-9346/kdelibs3-3.5.10-37.fc17
or not?

and if not, maybe a simple rebuild of twinkle against a newer gcc may help as well, here's a scratch build to try out:

http://koji.fedoraproject.org/koji/taskinfo?taskID=4183506

Neither kdelibs3-3.5.10-37.fc17 nor twinkle-1.4.2-17.fc17.1.x86_64 do help. I also tried to rebuild arts and tried the i686-Version of twinkle, arts and kdelibs3, but to no avail.

I am experiencing the same problem and I am not running KDE, but Cinamon on F17, so the problem is probably not kde related.

I have the same problem with gnome-fallback on F17.  Rythmbox works fine.  IMPORTANT: In addition,  when I run twinkle from the gnome menu and attempt to dial a call, I hear about a seconds worth of dialing sound, then twinkle goes away!  No abrt.  However, when I run twinkle from the command line (hoping to get some diagnostics for you), then I hear nothing, and twinkle is stuck, requiring kill -9 (similar to other reporters).

Here is my lsusb:

Bus 001 Device 003: ID 04f2:a133 Chicony Electronics Co., Ltd Gateway Webcam
Bus 002 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 003 Device 002: ID 0d8c:000e C-Media Electronics, Inc. Audio Adapter (Planet UP-100, Genius G-Talk)
Bus 003 Device 003: ID 03f0:4f11 Hewlett-Packard OfficeJet 5600 (USBHUB)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


The C-Media are my USB headphones - which work great in F16.

In reply to comment#19

I have kdelibs3-3.5.10-37.fc17.i686 on F17 on gnome3 w/ noveau here.  Same problem.  I hear a second or two of the call, then twinkle goes away.

(In reply to comment #22)
> I am experiencing the same problem and I am not running KDE, but Cinamon on
> F17, so the problem is probably not kde related.

KDE apps still use kdelibs when running under gnome, so it could still be KDE related.

Ekiga (gnome based) works using diamondcard.us, so that makes it more likely to be a kde problem.  Unfortunately, ekiga does not work with my companies VOIP provider.  twinkle and empathy work, but empathy does not support a separate sound device for audio, and twinkle crashes when you use a separate sound device.

Tried setting twinkle audio to "Alsa default" and changing default output to USB headset in sound config.  Still crashes.

I have the same problem.

- twinkle-1.4.2-17.fc17.x86_64
- Fedora 17
- Gnome3
- Hardware: Lenovo T520

No sound can be heard in twinkle, neither with the internal speakers
(as in comment#16) nor with a headset plugged to the dockingstation
nor with a headset plugged to the T520 directly (non-USB headset,
“normal” headset).

Sound in other apps works fine, linphone also works fine.

I can also reproduce that twinkle doesn’t stop running when
I select file/quit and it has to be killed with “kill -9”

I confirm that I can't hear anything in speakers when a call is established, ringing is audible though (with F17's twinkle)

(In reply to comment #15)
> Created attachment 593390 [details]
> twinkle binary and some extra shared libs to make it run on f17. this binary
> works fine!

Thanks a lot Michael for finding that F15's twinkle version with some libraries works without the problem on F17.
I'm attaching binaries for those who use a 64bit system. More info is in comment #16.

Created attachment 610251 [details]
f15's twinkle binary and some extra shared libs to make it run on f17. 64-bit version

Use instruction in #comment 16 to run this version.

kdelibs3-3.5.10-38.fc17.i686 just updated - same problem.

Ok, so I thought if I configured twinkle to use the internal sound card, and rhythmbox to use the USB sound, everyone could play together.  Nope.  The mere presence of a USB sound card makes twinkle crash when placing or receiving a call.

I don't even have a USB headset and twinkle audio stopped working for me some weeks back.

(In reply to comment #33)
> I don't even have a USB headset and twinkle audio stopped working for me
> some weeks back.

Any USB audio device on the bus will prevent twinkle from working.  In fact, after connecting a USB audio for testing, I find I have to reboot (without the USB device) for twinkle to work again.  This is a really frustrating bug that destroys an other wise very good and useful piece of software.

(In reply to comment #34)
> (In reply to comment #33)
> > I don't even have a USB headset and twinkle audio stopped working for me
> > some weeks back.
> 
> Any USB audio device on the bus will prevent twinkle from working.  In fact,
> after connecting a USB audio for testing, I find I have to reboot (without
> the USB device) for twinkle to work again.  This is a really frustrating bug
> that destroys an other wise very good and useful piece of software.

I don’t have an USB audio device at all, at least I believe
I don’t have something like this.

Nevertheless sound does not work for me in twinkle, see comment#28.

Just as a FYI here, twinkle upstream has been dead for 3-4 years, and I haven't had to the time to dig
deeper into fixing this issue. 

Patches welcome or patience as I try and find time/energy to look deeper.

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.