Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 133400 - timidity++-2.13.2-r2 can't find timidity.cfg file
Summary: timidity++-2.13.2-r2 can't find timidity.cfg file
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Sound Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-15 10:44 UTC by Niko Efthymiou
Modified: 2007-01-10 19:35 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
strace -o log timidity (log,45.17 KB, text/plain)
2006-05-16 09:16 UTC, Niko Efthymiou
Details
second strace (log,48.16 KB, text/plain)
2006-10-16 07:23 UTC, Leo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Niko Efthymiou 2006-05-15 10:44:26 UTC
timidity randomly complaines about missing configuration file. The error message is:

current/timidity.cfg: No such file or directory
timidity: Can't read any configuration file.
Please check /usr/share/timidity/timidity.cfg

The /usr/share/timidity/timidity.cfg is there and is a simlink to /etc/timidity.cfg which exitst and is world readable.

This only happens some times and I was not able to find a condition under which it reproduces. It also happens with earlier versions.

The useflags I use are: X alsa -esd flac gtk gtk2 ncurses portaudio vorbis -ao -arts -emacs -jack -motif -nas -oss -slang -speex -tcltk
Comment 1 Stian Skjelstad 2006-05-15 23:27:51 UTC
How does your filesystem layout look like? (the output from #mount)
Comment 2 Niko Efthymiou 2006-05-16 00:01:39 UTC
nothing unusual:

/dev/hda3 on / type ext3 (rw,noatime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
udev on /dev type tmpfs (rw,nosuid)
devpts on /dev/pts type devpts (rw)
/dev/hda1 on /boot type ext2 (rw,noatime)
shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
usbfs on /proc/bus/usb type usbfs (rw,devmode=0664,devgid=85)
/dev/sda3 on /mnt/usb type ext3 (ro)
Comment 3 Stian Skjelstad 2006-05-16 00:07:35 UTC
Does this problem ever occure of you start/stop the service by hand, or does it just occure when it is ran during normal bootup from init?
Comment 4 Niko Efthymiou 2006-05-16 00:09:25 UTC
I don't understund your question. I use timidity only to some times play a midi file not as a service or anything.
Comment 5 Stian Skjelstad 2006-05-16 07:38:18 UTC
I see. Then you can this simple thing:

strace -o log timidity mymidifil.mid

and you can see all then kernel calls being stored in the file log, and you can submit a log file here, where timidity fails to find its config
Comment 6 Niko Efthymiou 2006-05-16 09:16:32 UTC
Created attachment 86860 [details]
strace -o log timidity

atleast /user/share/current/timidity.cfg and ~/.timidity/current/timidity.cfg exist, although ENOENT ist returned from the stat64 syscall. Timidity is the only programm where I experience such behaviour. Strange..
Comment 7 Stian Skjelstad 2006-05-18 00:51:23 UTC
Have you configured your system correctly?

At my system, it is configured like this:

gentoo-2 .timidity # pwd
/root/.timidity
gentoo-2 .timidity # ls -l
total 0
lrwxrwxrwx 1 root root 27 Aug  2  2005 current -> /usr/share/timidity/current



gentoo-2 timidity # pwd
/usr/share/timidity
gentoo-2 timidity # ls -l
total 8
lrwxrwxrwx  1 root root   30 Aug  2  2005 current -> /usr/share/timidity/eawpatches
drwxr-xr-x 11 root root 8192 Aug  2  2005 eawpatches
lrwxrwxrwx  1 root root   17 Feb  7 10:36 timidity.cfg -> /etc/timidity.cfg
Comment 8 Leo 2006-10-16 07:23:34 UTC
Created attachment 99810 [details]
second strace
Comment 9 Leo 2006-10-16 07:25:15 UTC
Comment on attachment 99810 [details]
second strace

I'm experiencing the same problem... here is my strace if it can be usefull
strace -o log timidity /var/www/localhost/htdocs/musica.mid
Comment 10 Niko Efthymiou 2006-10-16 07:35:27 UTC
I somehow had fixed this a while ago... it was somethin in the /etc/timidity.cfg but I don't excactly remember what it was. Anyway  here is what my tymidity.cfg look like now:

dir /usr/share/timidity
dir ~/.timidity
source ~/.timidity/current/timidity.cfg

hope this helps
Comment 11 reisio 2006-10-26 13:31:01 UTC
For me, the symlink from 'current' to 'eawpatches' (or whatever) was missing; adding it resolved the issue.
Comment 12 Diego Elio Pettenò (RETIRED) gentoo-dev 2007-01-10 19:35:06 UTC
I'll consider this resolved as this is fixed in -r3, that by using eselect-timidity now always have the current symlink proper.

I'll see to get a stabilisation request open soon.