This is still a thing. As mentioned here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901931#58 you just need to
remove timidity from the audio group -- go to your /etc/group file and find the
line
audio:
and remove timidity. Save & restart.
--
You received this bug notification becaus
** Changed in: timidity (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Pulseaudio fails to detect sound card, while timidity is installed
T
sudo setfacl -m u:user:rw /dev/snd/*
solved the problem as solution found on https://www.toolbox.com/tech
/operating-systems/question/no-sound-at-all-in-lubuntu-1404-103114/ and
somewhere on Ask ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
@h1bymask
Seems cleaner to share the audio group between the two daemon processes
rather than trying to merge the two separate uids.
/etc/group already seems to do this (on 18.04):
$ grep audio /etc/group
audio:x:29:pulse,timidity
Given that the devices under /dev/snd/ are all read-writ
TL;DR: It is enough to update the config of the timidity daemon instead
of purging the timidity-daemon package in order to make pulseaudio work
together with timidity daemon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Managed to make TiMidity++ work together with PulseAudio just fine on
Focal 20.04.1. The idea is just to start both pulseaudio and timidity
under the same user. One-liner for the current desktop user:
sudo sed -E "s,^(SERVER_NAME)=(.*)$,\1=$(id --user --name $USER) #\2,"
-E "s,^(SERVER_GROUP)=(.*
On 20.04 at least it seems sufficient to only purge timidity-daemon and
still timidity could be used to play midi files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Pulseaudio fails
Hit this issue when upgrading from Kubuntu 18.04 to 20.04.
Solution was to "sudo apt purge timidity timidity-daemon" and the audio
devices immediately were recognized by the system, didn't need to
reboot.
This happened on a bog-standard 2015 era Intel-based laptop, nothing
exotic.
--
You receiv
Started happening to me on upgrade from 18.04 LTS to 19.10.
KDE shows only "dummy" device, until
# sudo apt remove timidity-daemon
# pulseaudio -k && sudo alsa force-reload
and suddenly audio is back. I still have timidity itself installed
--
You received this bug notification because you are
In case this helps anybody:
I solved the MIDI issue by installing fluidsynth instead of timidity according
to this guide:
https://blog.geierb.de/debian-fluidsynth-als-systemd-service/
What's missing though is the connection of fluidsynth server to pulsaudio
DISPLAY.
you have to add DISPLAY=:0 t
I upgraded from 18.04 to focal and had the same problem. Purging
timidity got audio back for me as well.
** Tags added: champagne focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
** Changed in: timidity (Debian)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Pulseaudio fails to detect sound card, while timidity is installed
T
I have unarchived / reopened and commented debian bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Pulseaudio fails to detect sound card, while timidity is installed
To manage noti
I removed timidity (without even purging) and my sound satarted working
normally, even though my audio group still contains two users: pulse and
timidity. This group is supposed to be empty?
I reinstalled timidity and timidity-daemon and the problem returned. I
removed timidity from the audio gr
I confirm that timidity works after removing the timidity user. So
instead of removing timidity all together, another workaround for this
bug is to remove the timidity user and make sure the audio group is
empty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Sending email to 901...@bugs.debian.org bounces because the bug is
archived and cannot be modified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Pulseaudio fails to detect sound card
I have tested on Kubuntu 19.04:
1. After installing timidity-daemon, the timidity user is automatically created
and added to the audio group. After reboot, the primary audio output device is
inaccessible in PulseAudio.
2. After removing timidity user from audio group and rebooting, PulseAudio is
A user in that bug already verified that it works. What I'm pointing out
is that the user/group fix is not implemented in the Debian or Ubuntu
package, and as long as that bug is closed it's not likely become
implemented.
--
You received this bug notification because you are a member of Ubuntu
Bu
Try the user/group fix mentioned there first:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901931
If that works then we know what kind of fix to propose to Ubuntu or
Debian.
If that doesn't work then please email 901...@bugs.debian.org pointing
out it is not fixed and to reopen the bug.
--
Can the Debian bug be reopened? Otherwise, I'm afraid, we'll never see
it fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Pulseaudio fails to detect sound card, while timidity is
I think that "Fix Released" status is misleading. Even the Debian bug
mentions the problem is in 2.14.0-8 and that's the latest version in
Ubuntu and Debian.
It looks like the Debian bug was closed prematurely without a fix being
released. I was going to unlink it here but maybe not... Let's just
I think that "Fix Released" status is misleading. It's showing as fixed
in the same version where we still have the bug.
I'm going to remove that bug link since its of limited relevance here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
It does not seem to have landed in ubuntu yet :
https://changelogs.ubuntu.com/changelogs/pool/universe/t/timidity/timidity_2.14.0-8/changelog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Titl
Does "fix release" mean this bug has been fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Pulseaudio fails to detect sound card, while timidity is installed
To manage notificati
** Changed in: timidity (Ubuntu)
Importance: Undecided => High
** Changed in: timidity (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
P
** Changed in: timidity (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Pulseaudio fails to detect sound card, while timidity is installe
>From the discussion in bug 210472 and in the Debian bug, it looks more
like a configuration or intergration issue in timidity packages rather
than a genuine upstream bug.
Also, forums and mailing lists are a way to report bugs, too. Even
though not as convenient as bug trackers.
--
You received
OK, maybe just not with many releases or much active development. The
latest version was released August 2018 and the latest commit was
October 2018:
https://sourceforge.net/p/timidity/git/ci/master/tree/
I was also thrown by the latest news item on the main project page being
dated 2004 :)
Daniel, why do you say it is unmaintained? I see an active Debian
maintainer:
https://tracker.debian.org/pkg/timidity
and in Sourceforge there is a new upstream version from October 2018.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I do use it, to play midi files and to convert them to other formats.
But if it is an abandoned project, I will have to look for alternatives.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Tit
It doesn't appear Timidity is being maintained upstream anymore. If you
can, please just uninstall it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Pulseaudio fails to detect sound c
** Also affects: timidity (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901931
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
T
I still have this problem in Ubuntu 19.04 develpment version. Here is a
Debian bug about this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901931
** Bug watch added: Debian Bug tracker #901931
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901931
--
You received this bug notificatio
Same thing on a Lenovo L520 with Intel chipset, attaching some info
just in case it helps.
** Attachment added: "SoundProblemInfo.txt"
https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640/+attachment/5250999/+files/SoundProblemInfo.txt
--
You received this bug notification becau
34 matches
Mail list logo
