If USE=motif many other ./configure options get over-ridden. Most importantly, "--with-default-output=alsa --enable-alsaseq", which normally get enabled with USE=alsa. Without these two configure options /etc/init.d/timidity start fails because -iA support does not get compiled in. Error in the ebuild at line 82: myconf="--enable-motif --with-x" should be: myconf="${myconf} --enable-motif --with-x" Updated ebuild incoming. Reproducible: Always
Created attachment 106908 [details] Updated ebuild with USE=motif problem fixed.
*** Bug 162216 has been marked as a duplicate of this bug. ***
This bug is almost a week old, is in a newly stabilized package, breaks major functionality and is trivial to fix. Can someone commit this already?
oops
*** Bug 163027 has been marked as a duplicate of this bug. ***
I'm sorry about the duplicate.. About the second part of the other bug: >I'm also having troubles playing midi files with normal user. Root can play >files fine with # timidity midi.file but the same command by the user gives: >Probable source loop in configuration files >timidity: Can't read any configuration file. >Please check /usr/share/timidity/timidity.cfg > >The /etc/timidity.cfg file is still the original. > >Already run eselect a couple of times as this was an already mentioned and >solved bug, but still doesn't work. I found that the problem was the symlink in /usr/share/timidity/ current->/usr/share/timidity/ The strange thing is that eselect tool doesn't change the symlink. I tried deleting it and eselect didn't make another. Can this be a problem is the eselect timidity module? As far as I understood the "current" symlink is what defines if eawpatches, shompatches or freepats is used in timidity.
Sorry for being late, fixed now.
