Bug 67 - Backend cannot start on Win2k / XP
Summary: Backend cannot start on Win2k / XP
Status: CLOSED FIXED
Alias: None
Product: LinuxSampler
Classification: Unclassified
Component: other (show other bugs)
Version: 0.5.1
Hardware: PC Windows 2000
: P2 blocker
Assignee: Benno Senoner
URL:
: 69 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-12-13 13:26 CET by bipll
Modified: 2009-11-01 18:01 CET (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bipll 2007-12-13 13:26:52 CET
Hello. I've just tried downloading and installing the Windows build (Windows
2000 SP4, Athlon XP 2200+, SB Live! Value CT4832 with kX ASIO). I've been using
Win2K for five years, but I've never before seen such an intriguing error message:

Application failed to initialize. Click 'OK' to terminate.

It's written on a dialogue popup; if trying to start the backend from a console,
no messages are printed in it.
Comment 1 Christian Schoenebeck 2007-12-13 19:47:22 CET
Did you install all components coming with the installer (linuxsampler, 
jsampler, qsampler and gigedit)?

If so, did the installer ask you whether to install a) gtkmm? b) gtk+? c) JRE?

Just to be sure: completely deinstall LS, reinstall it, but this time without 
the "gigedit" component and try again to start the backend (LinuxSampler).
Comment 2 Christian Schoenebeck 2007-12-13 20:50:16 CET
See also: http://linuxsampler.org/windows.html#houston
Comment 3 bipll 2007-12-14 13:04:52 CET
> Did you install all components coming with the installer
> (linuxsampler, jsampler, qsampler and gigedit)?

Yes, I did.

> If so, did the installer ask you whether to install a) gtkmm? b)
> gtk+? c) JRE?

No, as I've installed gtkmm and updated JRE prior to installing LS; and gtk+ was
installed some time ago (last spring). Could it be a rather old version of gtk+?

> Just to be sure: completely deinstall LS, reinstall it, but this
> time without the "gigedit" component and try again to start the
> backend (LinuxSampler).

OK, I'll try it tonight.
As for deinstalled previous versions, it could not the case, since it's just
once that I installed gtk+ and left it alone (I need it for winbuild of GIMP),
and I had never had gtkmm before.
Comment 4 Christian Schoenebeck 2007-12-14 14:39:39 CET
Yeah, I assume you have a binary incompatible version of either gtkmm and / or 
Gtk+. That's why I suggested to deinstall LS and reinstall it without 
the "gigedit" component, because gigedit is the only component that has that 
gtkmm & gtk+ dependency. If you can then start the backend, you know for sure 
that it's a gtkmm / gtk+ issue.

The current release requires gtkmm and gtk+, both of version 2.10.11:

http://downloads.sourceforge.net/gladewin32/gtk-2.10.11-win32-1.exe?modtime=1175123376&big_mirror=0
http://ftp.gnome.org/pub/gnome/binaries/win32/gtkmm/2.10/gtkmm-win32-runtime-2.10.11-1.exe
Comment 5 bipll 2007-12-17 11:18:24 CET
Humm... I don't quite get, how gigedit issues could stop the backend from
loading... Anyway reinstall (even with no components other than backend) did
solve nothing.
Here's how it looks (6KB png-screenshot):
http://forum.b.gz.ru/user/upload/file6670.png
And qsampler says:
02:14:31.595 Client connecting...
02:14:32.717 Server is starting...
02:14:32.717 linuxsampler
02:14:32.787 Server was started with PID=15226968.
02:14:32.797 Server was stopped with exit status 0.
02:14:35.991 Client connecting...
02:14:36.953 Server is starting...
02:14:36.963 linuxsampler
02:14:36.983 Server was started with PID=4189712.
02:14:36.993 Server was stopped with exit status 0.
02:14:40.197 Client connecting...
02:14:41.169 Server is starting...
02:14:41.179 linuxsampler
02:14:41.199 Server was started with PID=15303888.
02:14:41.219 Server was stopped with exit status 0.
02:14:44.424 Client connecting...
Comment 6 Christian Schoenebeck 2007-12-17 16:05:20 CET
*** Bug 69 has been marked as a duplicate of this bug. ***
Comment 7 Christian Schoenebeck 2007-12-17 16:17:00 CET
(In reply to comment #5)
> Humm... I don't quite get, how gigedit issues could stop the backend from
> loading...

Because when you select the "gigedit" application for installation, it will 
also install a plugin DLL for the LS backend. This plugin DLL is needed by LS 
to actually cooperate with gigedit, that is launching the gigedit application 
when a frontend application (i.e. JSampler, QSampler) requested to edit an 
already loaded .gig instrument and to be able to share the already loaded 
instrument between the LS backend and the gigedit instrument editor 
application and making all modifications by gigedit audible in realtime with 
the LS backend.

Please also check the remarks I left on the duplicate Bug #69
Comment 8 Christian Schoenebeck 2007-12-18 01:50:58 CET
*** Bug 69 has been marked as a duplicate of this bug. ***
Comment 9 Christian Schoenebeck 2007-12-18 02:16:03 CET
Jake, could you please also tell us the exact hardware you are using 
(especially CPU, Mainboard, BIOS version and RAM)?
Comment 10 Jake 2007-12-18 02:37:01 CET
(In reply to comment #9)
> Jake, could you please also tell us the exact hardware you are using 
> (especially CPU, Mainboard, BIOS version and RAM)?


Intel desktop board D815EEA  P3 733, 512mb.  Using onboard sound and Creative 
ES1370.    I need to restart to see my bios ver. right?   I'm sure it is the 
latest. 

Comment 11 Christian Schoenebeck 2007-12-18 14:11:13 CET
Please would you try the following replacement binaries:

    http://download.linuxsampler.org/dev/win32_probs/ls686_20071207.zip

Just download the .zip file, extract it and copy the files manually into your 
LS installation directory, that is overwrite the binaries with the three ones 
from the zip file and try again if you can launch the LS backend.

These binaries are probably a bit suboptimal regarding performance, but we're 
quite optimistic that it will solve this issue for you.
Comment 12 Jake 2007-12-18 19:45:42 CET
That worked! : )   Now I need to get some sound out of this thing hehe.

Comment 13 Christian Schoenebeck 2007-12-18 23:23:48 CET
I appreciate it solved the issue. This is of course just a temporary 
workaround. We'll fix it accurately with the next LinuxSampler release.

I just updated the trouble shooting section of the Windows HOWTO with this 
workaround solution.
Comment 14 bipll 2007-12-20 12:56:53 CET
Yeah, replacement bins worked, at least I've been able to start both back- and
frontends and loaded a gig bank into it. Now, please wait for more bug reports. :)
Comment 15 Christian Schoenebeck 2008-12-14 14:13:50 CET
Marking this one as blocker, as it should be handled for the upcoming release.
Comment 16 Christian Schoenebeck 2009-11-01 18:01:45 CET
Closing this report now, since this issue is fixed in the latest Windows
release of LinuxSampler (2009-08-03).