Description of problem: Gtick does not make any sound out of the box Version-Release number of selected component (if applicable): gtick 0.4.2-6.fc17 How reproducible: always Steps to Reproduce: 1. yum install gtick 2. start gtick 3. Actual results: error, no sound Expected results: sound Additional info: This is an old bug. Why not simply fix this in the RPM packaging: In gtick.spec we need to add: Requires: alsa-oss An also change the file gtick.desktop: #Exec=gtick Exec=aoss gtick This should fix the problem that has existed in Fedora since I don't know when.
FYI, I won't get around to this before I go on vacation: http://fedoraproject.org/wiki/Vacation Feel free to apply this change, and submit an update.
Can you verify that the following build performs as expected? Thanks http://koji.fedoraproject.org/koji/buildinfo?buildID=359174
I rebuild and installed your src.rpm on Fedora 17 and it seems to work. I am getting sound right out of the box. Thanks. aoss is a useful workaround. But someone upstream should do a real fix and make gtick alsa, jack and pulseaudio compatible. You can't use gtick in combination with DAW software for example. Wouldn't that be great: gtick used as an external metronome clock master or slave synchronized in combination with ardour or rosegarden ... I'll see if I can drop a request upstream.
gtick-0.5.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gtick-0.5.1-1.fc18
gtick-0.5.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/gtick-0.5.1-1.fc17
I think gtick 0.5.1 does not need the aoss workaround anymore. In 0.5.0 pulseaudio support was added upstream. I tested this by starting gtick not using the desktop file but from the commandline (without using aoss). I was even able to start 2 instances of gtick with different BPM values :-) This was not possible with the 0.4.x version and the aoss workaround. So I think the workaround using aoss in the desktop file can and should be removed. BTW: I had another problem. I could not install/update from 0.4.2 to 0.5.1-1. I got a lot of errors (conflicting files). I first had to "yum remove" my older gtick version before I could install and test this new one.
(In reply to comment #6) > BTW: I had another problem. I could not install/update from 0.4.2 to > 0.5.1-1. I got a lot of errors (conflicting files). I first had to "yum > remove" my older gtick version before I could install and test this new one. I tried again: reinstalled the old stable version 0.4.2-7 and then updated to 0.5.1-1. No problem. I could not reproduce these install/update errors I got first.
Package gtick-0.5.1-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gtick-0.5.1-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3264/gtick-0.5.1-1.fc17 then log in and leave karma (feedback).
(In reply to comment #6) > So I think the workaround using aoss in the desktop file can and should be > removed. I've left it in for people actually wanting to not use PA -- they still need aoss to use ALSA instead of OSS.
gtick-0.5.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.