By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 564 - artsd cannot start
Summary: artsd cannot start
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: arts (show other bugs)
Version: 3.5.13 [Trinity]
Hardware: i386 Debian Squeeze
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-10-27 12:13 CDT by Nick Leverton
Modified: 2012-10-19 15:49 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Leverton 2011-10-27 12:13:31 CDT
artsd is not running, and .xsession-errors is logging the following every five seconds (the PID obviously changes):

kdeinit: Got EXEC_NEW '/opt/trinity/bin/artswrapper' from socket.
Could not load library! Trying exec....
kdeinit: PID 16781 terminated.
No such file or directory
>> synthesizer priority is 0 (which is unacceptable, try running as root)

Audio still seems to be working direct via alsa, for apps that support it, so it's no big deal apart from the log flood.  But kcontrol "test audio" cannot play as it cannot start the sound system.

strace says that artswrapper is trying to exec a null program, i.e. that EXECUTE is set or #defined to "":

27718 18:06:52.548739 execve("", ["", "-F", "10", "-S", "4096", "-a", "alsa", "-d", "-s", "60", "-m", "artsmessage", "-c", "drkonqi", "-l", "3", ...], [/* 44 vars */]) = -1 ENOENT (No such file or directory)

If I run /opt/trinity/bin/artsd by hand, then it remains running and kcontrol can test the audio.

Artsd was starting correctly in 3.5.12.
Comment 1 Timothy Pearson 2011-10-27 13:10:51 CDT
Fixed in SVN revision 1261050.

Thanks for reporting!