err:module:attach_process_dlls "krnl386.exe16" failed to initialize, aborting

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1327532/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1327532

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Jaime Cruz, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available (the one all the way at the top, and not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.15

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Jaime Cruz, the next step is to fully reverse commit bisect the kernel in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Just tested 3.13.11-03131103-generic, which is the latest kernel I found in the 3.13 branch. It failed.

And just confirmed it works with 3.14.0-031400-generic.

So it works with the 3.13 kernel up to 3.13.0-27-generic but is broken in every version I've tested of the 3.13 kernels. It works in both of the 3.14 kernels I've tested, so it looks like it got broken somewhere between 3.13.0-27-generic and 3.13.0-29-generic.

Pending results of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327532/comments/19 .

Problem still exists in latest Trusty kernel 3.13.0-30-generic.

I'm going to need some help here running that process outlined. I know the Win16 apps work with the 3.13.0-27-generic kernel, and that they were broken in the 3.13.0-29-generic kernel. I've solved MY problem by reinstalling the 3.13.0-27-generic kernel and "pinning" it so I doesn't get over-written by the automated update process. However, I WOULD like to see the problem fixed in an upstream kernel.

I'm a n00b, so the kernel names on that link you gave me mean nothing, really. How do I know which kernel corresponds to the GA 3.13.0-27-generic kernel, and which one corresponds to the 3.13.0-29-generic kernel and if I find the time I'll run through that process outlined above. Barring that, I'd be more than happy to provide the files to install a Win16 app so someone else can play with this problem. Let me know?

See https://lkml.org/lkml/2014/5/7/508 for a fix from Linus.

Did some research. That fix is not available in the 3.13 kernel, it is apparently only in the 3.14 kernel. I've pinned the 3.13 kernel at the "27" level so I'm good for the time being. I understand Linus and the WINE team are looking for a way around this issue so SOMETHING should be coming soon.

With latest linux from -updates, I can run apps under wine if I run:
sudo sysctl abi.ldt16=1

For this to be applied on boot, I've added a new /etc/sysctl.d/20-wine-ldt16.conf with:
abi.ldt16=1

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]