Comment 11 for bug 1480651

Re 10:

Prism 6 few people are going to have, but it may be that the copy command from PowerPoint keeps the graphics commands in EMF. Could the OP test if pasting that into Inkscape is a problem?

Re 1:

The EMF/WMF import/export code I maintain does not support EMF+ at all in Inkscape. The functions exist in libUEMF, but Inkscape never calls them. If the contents of the clipboard really are EMF+ and they are getting into Inkscape, then it must be through a call out to native Windows libraries somewhere in devlibs.

I have never heard of WMF+ before. Unless it differs in only tiny ways from WMF, it would not be supported by my code either.

EMF+ files are an extension of EMF where comments are pressed into service to carry an entirely new set of information. "EMF" files usually contain mixes of the old EMF and the new EMF+ descriptions of the same document. These are not always complete, PowerPoint, for instance, just drops all the text out of the EMF+ description. (Really, hard to believe, but true.) However, even the purest EMF+ file still contains a couple of the old EMF record types at the ends. Some of the size values in the first EMF record might even be garbage, because the real values would come later in the EMF+ records, which do not use anything from the old EMF. If a file like this hit Inkscape it would most likely not crash, just insert nothing.

In any case, we need this data as a file to see what is going on. If the OP wants to poke around in that file, get libUEMF (sourceforge), build it, and run the "reademf" tool against the problem EMF(+) file. It will show both the EMF and EMF+ records, and usually in a case like this, it is obvious where the issue is. (It might work best with a simpler test file though!)
Otherwise, post the EMF(+) file and I will look at it.