Gtick doesn't work with Karmic at all (pulseaudio)

Bug #455485 reported by Michal Pěnka
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
gtick (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: gtick

After an upgrade to Karmic (which uses new version of pulseaudio and is more dependent on it) gtick doesn't produce any sound at all.

This bug is crucial as the application is TOTALLY useless.

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

I get sound, but it's horribly distorted.

'pasuspender gtick' does not fix the problem

Changed in gtick (Ubuntu):
status: New → Confirmed
Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

It seems that this was a problem for a while in Jaunty. Gtick uses OSS, and uses the sound hardware directly, not through Pulseaudio. Since the PA suspender did not work, this is an OSS problem. I installed the alsa-oss package and ran 'aoss gtick' through a terminal, but it did not work either.

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

Hi, I'm running Karmic Final and it works fine for me. No problems whatsoever.

Are you still having a problem?

Changed in gtick (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Michal Pěnka (michal-penka) wrote :

You're right! It works...probably some update. I'm happy now. Thanks a lot.

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

Great, glad that this is resolved.

Changed in gtick (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Carsten Agger (agger) wrote :

I'm having this problem too, and the previous communication on this bug did not actually describe any fix. I've changed the status back to "Confirmed", as I'm still seeing it on my fully updated Karmic system.

Changed in gtick (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

Carsten: What happens when you type 'gtick' in a terminal?

Have you installed the alsa-oss package and tried running the program with 'aoss gtick'?

Revision history for this message
Carsten Agger (agger) wrote :

Chauncellor:

------------------------

agger@lakshmi:~$ gtick
/dev/dsp: Device or resource busy

------------------------

and I get the error message.

Hmm... if I use "/dev/adsp" instead of "dsp" in "Preferences", it claims to be running, but there is no sound. (Actually, I succeeded getting sound this way once, but I don't know how to reproduce it - some intermittent thing with the sound server.)

If I write "aoss gtick" in a terminal, it works fine. Yay, thanks! :-)

I don't consider this a satisfactory solution to the bug, though - gtick should be able to handle this by itself, or it should wrapped somehow. Installed programs should be able to be run from the GU by default.

Since there is a workaround, this may affect the priority of the bug, though. But I wouldn't consider it fixed.

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

Of course, I wasn't implying that that was the "fix". Workaround first, fix next :).

I don't know where to go from here, so maybe this will help you find your problem:

https://wiki.ubuntu.com/DebuggingSoundProblems

Revision history for this message
Koen (gorgabal) wrote :

this bug is not fixed yet.

it is clear that it us pulseaudio and gtick fighting for the sound-device.

aaos gtick results in gtick not functionoing properly, it's resets the metronome about 0,1sec after the first "tick"

should i report a new bug?

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

I would say no, as it seems to be related to our own issue. Do you have any terminal output?

Also, I sent an email to the mailing list about the problem, but I received no reply. I'm not in a comfortable enough position to do this again. Would someone mind nudging them again?

Revision history for this message
Stéphane List (slist) wrote :

Hi,

I've sent a mail to Roland (the author of gtick) this morning.
I'm waiting for his reply.

I've asked him if there was a plan to support pulseaudio in gtick.

Regards

Stephane

Revision history for this message
Mario Splivalo (mariosplivalo) wrote :

WFIW, I needed to change default sound device from /dev/dsp to /dev/dsp1 in gtick properties.

Using it on ubuntu 9.04.

Revision history for this message
Wolter HV (wolterh) wrote :

This bug affects me. I am using Ubuntu 9.10 fully updated as of [2010 february 22]. I have tried with:
- gtick (default settings)
- aoss gtick (default settings)
- gtick (/dev/adsp as sound device)
- aoss gtick (/dev/adsp as sound device)
But no success..

Revision history for this message
Stéphane List (slist) wrote :

gtick still doesn't work for me, and it will need a big work to make it compatible with pulseaudio.

So, I've wrote a little metronome compatible with pulseaudio.
It's not accurate like gtick, and especially if the PC is loaded.

Choose your language at the bottom of the page :
http://slist.lilotux.net/linux/qmetronome/

Revision history for this message
Michal Pěnka (michal-penka) wrote :

Thank you Stéphane! Really nice metronome which has almost everything I need.

Still plenty of work to reach the gtick features state, however as I said, it's enough for me.

Looking forward to see it in repositories soon (how about 10.04 Lucid Lynx? :))

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

This program looks great. I hope it flourishes as the development looks completely stagnant on gtick's side.

Revision history for this message
launchpad@flum.net (d-launchpad-flum-net) wrote :

None of the tips mentioned above helped me in Karmic.

Just upgraded to 10.04 Lucid and aoss gtick now works.

Revision history for this message
gfxcoder (gfxcoder) wrote :

Thanks, Stéphane! Running fully updated 9.10, and aoss gtick just wasn't working. Your program is just right.

Revision history for this message
TomasHnyk (sup) wrote :

This has long been fixed, right? It worked for me both on 12.04 and 12.10 out of the box with PulseAudio. Thus closing this.

Changed in gtick (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.