[Solved] Failed to initialize backend "pulse"

For discussion of ports to POSIX based systems, especially using GNUStep.

Moderators: winston, another_commander, Getafix

Neelix
---- E L I T E ----
---- E L I T E ----
Posts: 288
Joined: Sat May 31, 2014 9:02 pm
Location: Melbourne, Australia

[Solved] Failed to initialize backend "pulse"

Post by Neelix » Sat Jun 07, 2014 5:20 pm

I just tried to install and run the latest build but it segfaulted.

Code: Select all

neelix@nb-fezzik:~$ sudo ooliteinst/oolite-trunk-1.79.0.28d4ba6-dev.linux-x86.run 
[sudo] password for neelix: 
Verifying archive integrity... All good.
Uncompressing Oolite-trunk 1.79.0.28d4ba6 ...............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Installing Oolite-trunk in "/opt/Oolite-trunk"...
Copying oolite executable and resources... Done.
Extracting AddOns/Basic-debug.oxp... Done.
Extracting documentation... Done.
Extracting dependencies... Done.
Generating startup and wrapper scripts... Done.
Updating desktop menu... Done.
Cleaning up temporary folders... Done.
Finished!

A desktop menu entry "Oolite-trunk (oolite.org)" has been added under Games.
To start Oolite-trunk from a shell, run "oolite-trunk".
To uninstall Oolite-trunk, run "/opt/Oolite-trunk/uninstall".

neelix@nb-fezzik:~$ oolite-trunk
AL lib: (WW) alc_initconfig: Failed to initialize backend "pulse"
Segmentation fault

Erk. It looks like Oolite-trunk died with an error. When making an error
report, please copy + paste the log above into the report.

(Press Ctrl-C to continue)
The only thing I can think of is that my pulseaudio version might be too old as I'm still running Ubuntu 10.04.

Code: Select all

neelix@nb-fezzik:~$ pulseaudio --version
pulseaudio 0.9.21-63-gd3efa-dirty
Other than upgrading to a whole new OS, any suggestions as to how I might get it working?

- Neelix
Last edited by Getafix on Tue Jun 10, 2014 10:10 am, edited 1 time in total.
Reason: Marked as "Solved".
Talaxian Enterprises: [wiki]Vacuum Pump[/wiki] [wiki]Waypoint Here[/wiki]

User avatar
cim
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 4018
Joined: Fri Nov 11, 2011 6:19 pm

Re: Failed to initialize backend "pulse"

Post by cim » Sun Jun 08, 2014 7:56 am

It might not be pulseaudio - could you post your Latest.log as well, please?
Last edited by Getafix on Tue Jun 10, 2014 10:17 am, edited 1 time in total.
Reason: Updated title following "split" operation

User avatar
spara
---- E L I T E ----
---- E L I T E ----
Posts: 2552
Joined: Wed Aug 15, 2012 4:19 am
Location: Finland

Re: Failed to initialize backend "pulse"

Post by spara » Sun Jun 08, 2014 8:28 am

cim wrote:It might not be pulseaudio - could you post your Latest.log as well, please?
Yes. Sounds a lot like the problem I had with nvidia drivers a while ago. It was complaining about PA in too.
Last edited by Getafix on Tue Jun 10, 2014 10:18 am, edited 1 time in total.
Reason: Updated title following "split" operation

Neelix
---- E L I T E ----
---- E L I T E ----
Posts: 288
Joined: Sat May 31, 2014 9:02 pm
Location: Melbourne, Australia

Re: Failed to initialize backend "pulse"

Post by Neelix » Sun Jun 08, 2014 12:35 pm

I didn't even think about checking that for some reason. Here's the contents, though I don't see anything useful except perhaps to see where it ends...

Code: Select all

Opening log for Oolite development version 1.79.0.5789-140607-28d4ba6 (x86-32 test release) under Linux 2.6.32-57-generic at 2014-06-08 07:31:50 -0500.
2 processors detected.
Build options: OpenAL, new planets, JavaScript console support, OXP verifier, localization tools, debug GraphViz support, JavaScript profiling.

Note that the contents of the log file can be adjusted by editing logcontrol.plist.

07:31:50.352 [dataCache.notFound]: No data cache found, starting from scratch.
07:31:50.354 [paths.debug]: (AddOns, "/home/neelix/.Oolite/AddOns")
- Neelix
Last edited by Getafix on Tue Jun 10, 2014 10:18 am, edited 1 time in total.
Reason: Updated title following "split" operation
Talaxian Enterprises: [wiki]Vacuum Pump[/wiki] [wiki]Waypoint Here[/wiki]

User avatar
cim
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 4018
Joined: Fri Nov 11, 2011 6:19 pm

Re: Failed to initialize backend "pulse"

Post by cim » Sun Jun 08, 2014 1:06 pm

Could you try running it again with the --nosplash command-line parameter, please?
Last edited by Getafix on Tue Jun 10, 2014 10:18 am, edited 1 time in total.
Reason: Updated title following "split" operation

Neelix
---- E L I T E ----
---- E L I T E ----
Posts: 288
Joined: Sat May 31, 2014 9:02 pm
Location: Melbourne, Australia

Re: Failed to initialize backend "pulse"

Post by Neelix » Sun Jun 08, 2014 1:09 pm

No change.

Code: Select all

neelix@nb-fezzik:~$ oolite-trunk --nosplash
AL lib: (WW) alc_initconfig: Failed to initialize backend "pulse"
Segmentation fault

Erk. It looks like Oolite-trunk died with an error. When making an error
report, please copy + paste the log above into the report.

(Press Ctrl-C to continue)
^C
neelix@nb-fezzik:~$ cat .Oolite/Logs/Latest.log 
Opening log for Oolite development version 1.79.0.5789-140607-28d4ba6 (x86-32 test release) under Linux 2.6.32-57-generic at 2014-06-08 08:07:46 -0500.
2 processors detected.
Build options: OpenAL, new planets, JavaScript console support, OXP verifier, localization tools, debug GraphViz support, JavaScript profiling.

Note that the contents of the log file can be adjusted by editing logcontrol.plist.

08:07:46.834 [dataCache.notFound]: No data cache found, starting from scratch.
08:07:46.834 [paths.debug]: (AddOns, "/home/neelix/.Oolite/AddOns")
neelix@nb-fezzik:~$ 
- Neelix
Last edited by Getafix on Tue Jun 10, 2014 10:19 am, edited 1 time in total.
Reason: Updated title following "split" operation
Talaxian Enterprises: [wiki]Vacuum Pump[/wiki] [wiki]Waypoint Here[/wiki]

User avatar
cim
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 4018
Joined: Fri Nov 11, 2011 6:19 pm

Re: Failed to initialize backend "pulse"

Post by cim » Sun Jun 08, 2014 1:28 pm

Okay - what's the Latest.log output like if you run the 1.77.1 release?
Last edited by Getafix on Tue Jun 10, 2014 10:19 am, edited 1 time in total.
Reason: Updated title following "split" operation

Neelix
---- E L I T E ----
---- E L I T E ----
Posts: 288
Joined: Sat May 31, 2014 9:02 pm
Location: Melbourne, Australia

Re: Failed to initialize backend "pulse"

Post by Neelix » Sun Jun 08, 2014 1:44 pm

Well that worked at least. :-) (first time I've ever successfully started oolite on this machine)

Code: Select all

neelix@nb-fezzik:~$ cat .Oolite/Logs/Latest.log
Opening log for Oolite version 1.77.1 (x86-32) under Linux 2.6.32-57-generic at 2014-06-08 08:38:16 -0500.
2 processors detected.
Build options: spoken messages, mass/fuel pricing.

Note that the contents of the log file can be adjusted by editing logcontrol.plist.

08:38:16.277 [dataCache.notFound]: No data cache found, starting from scratch.
08:38:18.604 [display.mode.list.native]: X11 native resolution detected: 1024 x 600
08:38:21.117 [joystick.init]: Number of joysticks detected: 0
08:38:21.123 [rendering.opengl.version]: OpenGL renderer version: 1.4.0 ("1.4 Mesa 7.7.1"). Vendor: "Tungsten Graphics, Inc". Renderer: "Mesa DRI Intel(R) 945GME GEM 20091221 2009Q4 x86/MMX/SSE2".
08:38:21.125 [rendering.opengl.extensions]: OpenGL extensions (105):
GL_EXT_abgr, GL_ARB_texture_env_crossbar, GL_EXT_texture, GL_ARB_shadow, GL_IBM_texture_mirrored_repeat, GL_EXT_texture_edge_clamp, GL_EXT_separate_specular_color, GL_EXT_blend_minmax, GL_EXT_texture_object, GL_ARB_texture_env_add, GL_INGR_blend_func_separate, GL_ARB_shading_language_120, GL_NV_texture_env_combine4, GL_EXT_texture_cube_map, GL_EXT_blend_logic_op, GL_ARB_draw_elements_base_vertex, GL_EXT_texture_env_dot3, GL_IBM_rasterpos_clip, GL_EXT_framebuffer_blit, GL_ARB_texture_env_dot3, GL_NV_light_max_exponent, GL_EXT_framebuffer_object, GL_EXT_blend_subtract, GL_EXT_copy_texture, GL_3DFX_texture_compression_FXT1, GL_MESA_window_pos, GL_ARB_multitexture, GL_EXT_stencil_wrap, GL_ARB_texture_border_clamp, GL_NV_vertex_program, GL_ARB_texture_env_combine, GL_SGIS_texture_edge_clamp, GL_EXT_packed_pixels, GL_EXT_texture_env_add, GL_SGIS_texture_lod, GL_ARB_depth_texture, GL_ARB_transpose_matrix, GL_NV_texgen_reflection, GL_NV_packed_depth_stencil, GL_EXT_stencil_two_side, GL_ARB_shading_language_100, GL_EXT_rescale_normal, GL_EXT_gpu_program_parameters, GL_ARB_map_buffer_range, GL_ARB_provoking_vertex, GL_ARB_pixel_buffer_object, GL_EXT_secondary_color, GL_SUN_multi_draw_arrays, GL_OES_read_format, GL_ARB_texture_mirrored_repeat, GL_ARB_copy_buffer, GL_EXT_polygon_offset, GL_EXT_draw_range_elements, GL_EXT_blend_equation_separate, GL_ARB_half_float_pixel, GL_EXT_texture_lod_bias, GL_EXT_texture_filter_anisotropic, GL_SGIS_texture_border_clamp, GL_SGIS_generate_mipmap, GL_NV_texture_rectangle, GL_ARB_texture_rectangle, GL_ARB_texture_non_power_of_two, GL_ARB_point_sprite, GL_EXT_packed_depth_stencil, GL_ARB_vertex_shader, GL_ARB_vertex_buffer_object, GL_ARB_sync, GL_ARB_shader_objects, GL_EXT_provoking_vertex, GL_IBM_multimode_draw_arrays, GL_MESA_ycbcr_texture, GL_ATI_separate_stencil, GL_EXT_texture_rectangle, GL_ARB_fragment_shader, GL_EXT_texture3D, GL_EXT_fog_coord, GL_EXT_subtexture, GL_ARB_window_pos, GL_EXT_point_parameters, GL_ARB_fragment_program, GL_EXT_texture_env_combine, GL_ARB_vertex_program, GL_EXT_bgra, GL_ARB_texture_cube_map, GL_ARB_point_parameters, GL_EXT_compiled_vertex_array, GL_EXT_vertex_array, GL_ARB_multisample, GL_APPLE_client_storage, GL_ARB_vertex_array_object, GL_ARB_draw_buffers, GL_EXT_multi_draw_arrays, GL_ARB_texture_compression, GL_APPLE_vertex_array_object, GL_EXT_cull_vertex, GL_ATI_texture_env_combine3, GL_APPLE_packed_pixels, GL_EXT_blend_func_separate, GL_MESA_pack_invert, GL_EXT_shadow_funcs, GL_ATI_blend_equation_separate, GL_EXT_blend_color, GL_NV_vertex_program1_1, GL_NV_blend_square, GL_EXT_pixel_buffer_object
08:38:21.308 [rendering.opengl.gpuSpecific]: Matched GPU configuration "Intel GMA 900/950 family".
08:38:21.326 [rendering.opengl.shader.support]: Shaders are supported.
08:38:21.328 [dataCache.notFound]: No data cache found, starting from scratch.
08:38:21.329 [searchPaths.dumpAll]: Unrestricted mode - resource paths:
    /opt/Oolite/oolite.app/Resources
    AddOns
08:38:23.543 [shipData.load.begin]: Loading ship data.
08:38:24.747 [script.javascript.init]: JavaScript reset successful.
08:38:24.978 [script.load.world.listAll]: Loaded 9 world scripts:
    oolite-cloaking-device 1.77.1
    oolite-constrictor-hunt 1.77.1
    oolite-contracts-cargo 1.77.1
    oolite-contracts-helpers 1.77.1
    oolite-contracts-parcels 1.77.1
    oolite-contracts-passengers 1.77.1
    oolite-nova 1.77.1
    oolite-thargoid-plans 1.77.1
    oolite-trumbles 1.77.1
08:38:29.713 [startup.complete]: ========== Loading complete in 13.41 seconds. ==========
08:38:38.265 [gnustep]: 2014-06-08 08:38:38.264 oolite[4178] Defaults path '/home/neelix/GNUstep/Defaults' did not exist - created it

08:38:38.266 [gnustep]: 2014-06-08 08:38:38.266 oolite[4178] Creating empty user defaults database

08:39:10.291 [exit.context]: Exiting: Exit Game selected on options screen.
08:39:10.291 [gameController.exitApp]: .GNUstepDefaults synchronized.

Closing log at 2014-06-08 08:39:10 -0500.
neelix@nb-fezzik:~$ 

- Neelix
Last edited by Getafix on Tue Jun 10, 2014 10:19 am, edited 1 time in total.
Reason: Updated title following "split" operation
Talaxian Enterprises: [wiki]Vacuum Pump[/wiki] [wiki]Waypoint Here[/wiki]

User avatar
cim
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 4018
Joined: Fri Nov 11, 2011 6:19 pm

Re: Failed to initialize backend "pulse"

Post by cim » Sun Jun 08, 2014 1:59 pm

Okay, that all looks normal. Slightly long-shot: what happens if you try to start the nightly build now? (I expect the Latest.log to be marginally different even if it does crash)
Last edited by Getafix on Tue Jun 10, 2014 10:20 am, edited 1 time in total.
Reason: Updated title following "split" operation

Neelix
---- E L I T E ----
---- E L I T E ----
Posts: 288
Joined: Sat May 31, 2014 9:02 pm
Location: Melbourne, Australia

Re: Failed to initialize backend "pulse"

Post by Neelix » Sun Jun 08, 2014 2:08 pm

I thought the same thing, but the only difference is in the timestamps. Otherwise it's identical to what I posted earlier.

- Neelix
Last edited by Getafix on Tue Jun 10, 2014 10:20 am, edited 1 time in total.
Reason: Updated title following "split" operation
Talaxian Enterprises: [wiki]Vacuum Pump[/wiki] [wiki]Waypoint Here[/wiki]

User avatar
cim
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 4018
Joined: Fri Nov 11, 2011 6:19 pm

Re: Failed to initialize backend "pulse"

Post by cim » Sun Jun 08, 2014 2:24 pm

Hmm... strange, then, though that does at least rule out some possibilities.

Could you try the following, please:
1) Install gdb if it's not already installed
2) Edit the "oolite.app/oolite-wrapper" file to replace ./oolite.app/oolite "$@" with gdb ./oolite.app/oolite "$@"
3) Run oolite-trunk again. At the gdb prompt, type "run", and then when it crashes, type "bt".
4) Paste the entire output of gdb here.
Last edited by Getafix on Tue Jun 10, 2014 10:20 am, edited 1 time in total.
Reason: Updated title following "split" operation

Neelix
---- E L I T E ----
---- E L I T E ----
Posts: 288
Joined: Sat May 31, 2014 9:02 pm
Location: Melbourne, Australia

Re: Failed to initialize backend "pulse"

Post by Neelix » Sun Jun 08, 2014 2:38 pm

First I ran the uninstaller on my systemwide installation of oolite-trunk and reinstalled it in my Home folder.
then I changed the wrapper script as specified, and gave it another go, this was the result:

Code: Select all

neelix@nb-fezzik:~$ GNUstep/Applications/Oolite-trunk/oolite-trunk
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/neelix/GNUstep/Applications/Oolite-trunk/oolite.app/oolite...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/neelix/GNUstep/Applications/Oolite-trunk/oolite.app/oolite 
[Thread debugging using libthread_db enabled]
[New Thread 0xb7eaeb70 (LWP 4810)]
[New Thread 0xb35f3b70 (LWP 4811)]
[Thread 0xb35f3b70 (LWP 4811) exited]
AL lib: (WW) alc_initconfig: Failed to initialize backend "pulse"
[New Thread 0xb35f3b70 (LWP 4813)]

Program received signal SIGSEGV, Segmentation fault.
0x00db4fd8 in ?? () from /usr/lib/libasound.so.2
(gdb) bt
#0  0x00db4fd8 in ?? () from /usr/lib/libasound.so.2
#1  0x00d729f6 in snd_pcm_hw_refine () from /usr/lib/libasound.so.2
#2  0x00d6f8f1 in snd_pcm_hw_params_any () from /usr/lib/libasound.so.2
#3  0x008b25e3 in ?? () from /home/neelix/GNUstep/Applications/Oolite-trunk/oolite-deps/lib/libopenal.so.1
#4  0x008a2463 in alcCreateContext () from /home/neelix/GNUstep/Applications/Oolite-trunk/oolite-deps/lib/libopenal.so.1
#5  0x0824252a in ?? ()
#6  0x082424a2 in ?? ()
#7  0x082454bf in ?? ()
#8  0x0829bafe in ?? ()
#9  0x08293568 in ?? ()
#10 0x08293ce2 in ?? ()
#11 0x0829a440 in main ()
- Neelix
Last edited by Getafix on Tue Jun 10, 2014 10:21 am, edited 1 time in total.
Reason: Updated title following "split" operation
Talaxian Enterprises: [wiki]Vacuum Pump[/wiki] [wiki]Waypoint Here[/wiki]

User avatar
cim
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 4018
Joined: Fri Nov 11, 2011 6:19 pm

Re: Failed to initialize backend "pulse"

Post by cim » Sun Jun 08, 2014 2:54 pm

Okay, so that is in OpenAL - looks like some conflict between OpenAL and ALSA (libasound) on your system. You might have some luck by changing the "drivers=" line in /etc/openal/alsoft.conf to exclude the "alsa" driver.
Last edited by Getafix on Tue Jun 10, 2014 10:21 am, edited 1 time in total.
Reason: Updated title following "split" operation

Neelix
---- E L I T E ----
---- E L I T E ----
Posts: 288
Joined: Sat May 31, 2014 9:02 pm
Location: Melbourne, Australia

Re: Failed to initialize backend "pulse"

Post by Neelix » Sun Jun 08, 2014 3:28 pm

That got it started alright, but now I have no sound. (the sound worked just fine in 1.77.1)

Code: Select all

neelix@nb-fezzik:~$ echo drivers = pulse,oss,solaris,dsound,winmm,port,wave > .alsoftrc
neelix@nb-fezzik:~$ GNUstep/Applications/Oolite-trunk/oolite-trunk
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/neelix/GNUstep/Applications/Oolite-trunk/oolite.app/oolite...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/neelix/GNUstep/Applications/Oolite-trunk/oolite.app/oolite 
[Thread debugging using libthread_db enabled]
[New Thread 0xb7eaeb70 (LWP 4955)]
[New Thread 0xb34c4b70 (LWP 4956)]
AL lib: (WW) alc_initconfig: Failed to initialize backend "pulse"
AL lib: (EE) oss_open_playback: Could not open /dev/dsp: No such file or directory
[Thread 0xb34c4b70 (LWP 4956) exited]
[New Thread 0xb34c4b70 (LWP 4957)]
[New Thread 0xb69ffb70 (LWP 4958)]
AL lib: (EE) oss_open_playback: Could not open /dev/dsp: No such file or directory
[New Thread 0xb59ffb70 (LWP 4960)]
[Thread 0xb59ffb70 (LWP 4960) exited]
[New Thread 0xb59ffb70 (LWP 4961)]
[Thread 0xb59ffb70 (LWP 4961) exited]
[New Thread 0xb59ffb70 (LWP 4962)]
[Thread 0xb59ffb70 (LWP 4962) exited]
[New Thread 0xb59ffb70 (LWP 4963)]
[Thread 0xb59ffb70 (LWP 4963) exited]
[New Thread 0xb59ffb70 (LWP 4964)]
[Thread 0xb59ffb70 (LWP 4964) exited]
[New Thread 0xb59ffb70 (LWP 4965)]
[New Thread 0xb51feb70 (LWP 4966)]
[New Thread 0xb45ffb70 (LWP 4967)]
[New Thread 0xb3dfeb70 (LWP 4968)]
[Thread 0xb7eaeb70 (LWP 4955) exited]
AL lib: (EE) oss_open_playback: Could not open /dev/dsp: No such file or directory
10:13:57.133 [sound.initialization.error]: Failed to open default sound device
[Thread 0xb45ffb70 (LWP 4967) exited]
[Thread 0xb51feb70 (LWP 4966) exited]
[Thread 0xb59ffb70 (LWP 4965) exited]
[Thread 0xb69ffb70 (LWP 4958) exited]
[Thread 0xb34c4b70 (LWP 4957) exited]
[Thread 0xb3dfeb70 (LWP 4968) exited]

Program exited normally.
(gdb) quit
(alsa was second on the list in the example drivers= line in etc/openal/alsoft.conf)

- Neelix
Last edited by Getafix on Tue Jun 10, 2014 10:21 am, edited 1 time in total.
Reason: Updated title following "split" operation
Talaxian Enterprises: [wiki]Vacuum Pump[/wiki] [wiki]Waypoint Here[/wiki]

User avatar
cim
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 4018
Joined: Fri Nov 11, 2011 6:19 pm

Re: Failed to initialize backend "pulse"

Post by cim » Sun Jun 08, 2014 3:38 pm

You might need to install the OSS sound library - liboss4 package, perhaps?

Alternatively it may be that there's some misconfiguration of the pulseaudio set up which is stopping Oolite from talking to it - is it definitely installed, running and being used successfully by other programs?
Last edited by Getafix on Tue Jun 10, 2014 10:22 am, edited 1 time in total.
Reason: Updated title following "split" operation

Post Reply