gxine doesn't start (frozes) if there are no audio device
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gxine (Baltix) |
New
|
Undecided
|
Unassigned | ||
| gxine (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: gxine
gxine doesn't start (frozes) if there are no audio device - I've just tried on computer which have ISA PNP sound card, for which Ubuntu Feisty doesn't load kernel modules automatically and just after starting there are no /dev/dsp and /dev/snd
When I trying to start gxine on this computer it shows splash, but doesn't start and I get these messages in terminal output:
ubuntu@ubuntu:~$ gxine --verbose /mnt/home/
load_plugins: skipping unreadable plugin directory /home/ubuntu/
load_plugins: plugin /usr/lib/
[..]
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
snd_pcm_open() failed:-19:No such device
>>> Check if another program already uses PCM <<<
audio_oss_out: audio.device.
audio_oss_out: Auto probe for audio device failed
And gxine frozes forever untill I kill it. If I start without video file parameter then get almost the same situation, just no need to kill manually :
ubuntu@ubuntu:~$ gxine --verbose
load_plugins: skipping unreadable plugin directory /home/ubuntu/
load_plugins: plugin /usr/lib/
[..]
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
snd_pcm_open() failed:-19:No such device
>>> Check if another program already uses PCM <<<
audio_oss_out: audio.device.
audio_oss_out: Auto probe for audio device failed
gxine: killed by watchdog bite
Aborted
ubuntu@ubuntu:~$
I only can start gxine if I manually set audio output to NONE - then gxine starts fine I get these messages in terminal:
ubuntu@ubuntu:~$ gxine --verbose -A none
load_plugins: skipping unreadable plugin directory /home/ubuntu/
load_plugins: plugin /usr/lib/
[..]
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
load_plugins: plugin /usr/lib/
gtkvideo: failed to get a proxy for gnome-screensaver
engine: > executing ‘if (__js.v != 1) callback ('widget.
engine: > executing ‘if ((__js.v & ~1) != 2) callback ('widget.
engine: > executing ‘if ((__js.v & ~3) != 4) callback ('widget.
engine: > executing ‘if ((__js.v & ~7) != 8) callback ('widget.
video_out_dxr3: Failed to open control device /dev/em8300-0 (No such file or directory)
video_out_xv: using Xv port 64 from adaptor Savage Streams Engine for hardware colorspace conversion and scaling.
video_out_xv: this adaptor supports the yuy2 format.
video_out_xv: this adaptor supports the yv12 format.
lirc: cannot initialise - disabling remote control
lirc: maybe lircd isn't running or you can't connect to the socket?
video_out_xv: VO_PROP_
video_out_xv: VO_PROP_
video_out_xv: VO_PROP_
video_out_xv: VO_PROP_
video_out_xv: VO_PROP_
video_out_xv: VO_PROP_
av_offset=0 pts
engine: > executing ‘widget.
engine: > executing ‘widget.
engine: > executing ‘widget.
engine: > executing ‘widget.
xine: found input plugin : file input plugin
xine: found demuxer plugin: image demux plugin
video_out_xv: VO_PROP_
Btw, xine-ui also doesn't start in the same situation, so, maybe this is xine-lib bug, because mplayer, which doesn't use libxine, starts fine...
| Ioannis Ramfos (isr81) wrote Totem and gxine freeze on startup if there are no audio devices | #1 |
| Changed in gxine: | |
| status: | New → Confirmed |
Happens with totem (xine backend) also. The error message shows:
ALSA lib confmisc.
ALSA lib conf.c:
ALSA lib confmisc.
ALSA lib conf.c:
ALSA lib confmisc.
ALSA lib conf.c:
ALSA lib conf.c:
ALSA lib pcm.c:2145:
Tried both gxine and totem(xine) on vmware with no soundcard setup for the VM. When enabling the soundcard totem works.
gxine also passes this point, enters it's initial setup and after the final step it restarts the system (the virtual machine) -- however, this might be another issue.