LMMS • Forums

I compiled lmms myself, and although its works fine, it also crashes.

A few things I noticed. Lmms does not seem to like me running the chrome browser and skype at the same time.
I suspect it to be vst related, but I am not sure about that.

When I have a problem with a program on Linux, I always start the program from the command line, to see if there are any use full errors.

What I learned from this is that when lmms crashes there is a segmentation error. ( but that's all)

When I googled what that error means, I found it can be related to a memory problem. ( or bad coding )
I do trust the people who build lmms, so I doubt it to be bad coding.

When I start lmms however, it tells me something about vst support and shared memory.

I don't understand anything about his, but was wondering if there are people who do.
Can I ignore these massages or should I try to fix them.

Here is the output from the comand line when I start lmms.

Looks to me that your missing something in LMMS, Because your missing RemotePluginClient.
Reason for failed getting shared memory. It's crashing because it needs the shared memory.

Skype, and Chromium uses some of the same libraries, as Skype, and Chromium don't like to share nicely.

Richard Stallman mode: proprietary software sucks.

I love Linux, but from the first day I used it, I noticed the closed source programs causing the most issues.

Just worked with lmms for over two hours without a crash, but was not using a vst.
Before this I had two crashes with a song that used vst.
So its safe to assume its vst related, and getting that message says it all prob.

Lets see if google is my friend, to find solutions.

I installed something and I got rit of this message:

lmms(21383) KMimeTypePrivate::ensureXmlDataLoaded: Missing <comment> field in "application/x-msdownload.xml"

So making progress.

It seems I get stuck.

I tried installing, a newer wine version, but that broke vst completely.
They are working again, because I reinstalled the previous version of wine.

I cant find anything use full about shmget. (RemotePluginClient::shmget: No such file or directory)
Except that this has to do with shared memory.
shmget and openSUSE give me some hits in google, but those are all old articled form years ago.

I also installed another mesalib, because that seemed related.

When I start lmms however, it tells me something about vst support and shared memory.

I don't understand anything about his, but was wondering if there are people who do.
Can I ignore these massages or should I try to fix them.

Here is the output from the comand line when I start lmms.

Some investigation into these messages is done here: #1468

(scroll down to curlymorphic's comments)

I cant find anything use full about shmget. (RemotePluginClient::shmget: No such file or directory)
Except that this has to do with shared memory.
shmget and openSUSE give me some hits in google, but those are all old articled form years ago.

No, you won't get much except from the lmms development team because that is our code:
RemotePlugin.h#L798.

This code was mostly written by Toby (who is mostly idle and only chimes in occasionally on the project currently) so your mileage in troubleshooting this with the LMMS team may vary. You may want to tag him @tobydox in a new GitHub bug report explaining how VST support seems to be broken/instable in your distribution.

The way I understand shared memory is that C++ has shared memory support -- something that allows two independent processes to talk back and forth. Win32 VSTs (the only type we currently support) require this shared memory to be available and to work in order to function properly with LMMS. "shmem" is the message channel for exchanging information between native C++ and winegcc compiled C++ (our RemoteVstPlugin/RemotePluginClient instance).

What I'm not sure of is.... How long Wine historically has had support for this... Whether or not all version of Wine have support for this... or even how volatile this shared memory are is is to change.

So... I would recommend building and running against the same wine version if possible to eliminate that as a cause.

Furthermore, from research, there are very (VERY) few open source projects which even attempt to do what LMMS does from a native C++ to Wine perspective, so even if you get the buzzwords right in a search engine such as Google, you'll keep landing on the same 3-5 projects that have even attempted this in the FOSS world. Good luck and please post your progress.

-Tres

Thank you, and I did find this. A talk between a wine dev and a lmms dev.
its why I tried a newer wine version.

https://bugs.winehq.org/show_bug.cgi?id=35347

Tobias Doerffel 2014-01-23 09:52:53 CST

Hi,

as the original main developer of LMMS and its VST support layer, I'm joining. First of all thanks for your efforts to fix this issue! Regarding your questions:

The source code of the application which is launched externally using WINE can be found here:

https://github.com/LMMS/lmms/blob/stabl ... Plugin.cpp

At line 692 you can find the code which retrieves the X11 window ID. This code always has been working. Is there any other recommended method?


Inside LMMS we use QX11EmbedContainer to embed the window inside our MDI sub window:

https://github.com/LMMS/lmms/blob/stabl ... Plugin.cpp

at line 245 ff. So basically we don't do any magic here.

its a small world sometimes. Maybe I should ask about this at Wine Hq too.
Because it says in the end:
Closing bugs fixed in 1.7.12.

But I am using 1.7.2, so unless they have a weird numbering system, I should have a newer version.

Will keep you guys informed, and now will look at the topics you mentioned.

Gps wrote:It seems I get stuck.

I tried installing, a newer wine version, but that broke vst completely.
They are working again, because I reinstalled the previous version of wine.

I cant find anything use full about shmget. (RemotePluginClient::shmget: No such file or directory)
Except that this has to do with shared memory.
shmget and openSUSE give me some hits in google, but those are all old articled form years ago.

I also installed another mesalib, because that seemed related.

If you got rid of the shared memory issue, you should not get the shmget error anymore.
When it comes to wine I can help much.
But if you are having X session errors with wine, you can look at .xsession-errors log in your home directory, for the error related to wine.

I am still battle-ling and investigating the issue.
I am getting help from the openSUSE forum too.

I suddenly realized, that years ago there was a special version of openSUSE, which had a real time kernel.

But a real time kernel doesn't seem to be used much anymore.
I found ubuntu topics about this too. Somebody asks about a real time kernel, and then they tell him, you don't need that.
So that first message might not go away, but the openSUSE forum is trying to help me with the shmget part.

Through a fedora page I found this:

To see all shared memory settings, execute: That gives me