Bug#408941: artsd fails to start if you call it from command line using fvwm2 as window manager
Package: arts
Version: 1.5.5-1
Severity: serious
Hello,
I used arts a lot on debian woody in the following way:
window 1:
artsd
window 2:
artsdsp -m /path/to/first/application/with/oss_interface
window 3:
artsdsp -m /path/to/second/application/with/oss_interface
Since the update to etch artsd doesn't work anylonger in this way. When
I try to start artsd in my environment which doesn't uses kde it fails
in the following way:
(faui00w) [~] artsd
Creating link /home/cip/adm/sithglan/.kde/socket-faui00w.
can't create mcop directory
(faui00w) [~] ls -al /home/cip/adm/sithglan/.kde/socket-faui00w
ls: /home/cip/adm/sithglan/.kde/socket-faui00w: No such file or directory
(faui00w) [~] ls -al ~/.kde/
total 30
drwx------ 2 sithglan icipguru 512 Oct 3 18:20 ./
drwxr-xr-x 197 sithglan immdstud 29184 Jan 29 14:38 ../
What do I have to do to get it back working?
Thomas
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (1050, 'testing'), (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.2
Locale: LANG=C, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Versions of packages arts depends on:
ii libarts1c2a 1.5.5-1 aRts sound system core components
ii libartsc0 1.5.5-1 aRts sound system C support librar
arts recommends no packages.
-- debconf-show failed
Reply to: