Description of problem:
I have an unsupported Windows application (Unit Manager Express) that always
worked fine. I don't use it often, maybe once a week or less. All of the sudden,
it stopped launching. Not sure if it was a new Fedora kernel or the upgrade to
6.0.0 that broke it. I have tried uninstalling/reinstalling CrossOver and Unit
Manager Express, but it still won't launch. I can provide the Unit Manager
Express installation package.
I booted with the previous kernel (2.6.18-1-2869.fc6.x86_64) and UME works
again. It was running 2.6.19-1-2895.fc6.x86_64.
From Codeweavers: "Please report this issue to the Fedora developers. If they
need any feedback from me put this ticket in the bug report as well as my email
Version-Release number of selected component (if applicable):
Update kernel from 2.6.18-1-2869.fc6.x86_64 to 2.6.19-1-2895.fc6.x86_64
Steps to Reproduce:
1. Install CrossOver 6.0.0
2. Install Unit Manager Express
3. Update kernel to 2.6.19-1-2895.fc6.x86_64
Do any messages appear in the syslog when you try to run the app?
Created attachment 147564 [details]
syslog running 2.6.18 (good)
Created attachment 147565 [details]
syslog running 2.6.19 (bad)
I have attached syslog messages while launching Unit Manager Express under both
2.6.18 and 2.6.19.
App loaded OK under 2.6.18, didn't launch at all under 2.6.19.
it's surprising it works at all with those SELinux denials (or are you in
does booting with exec-shield=0 make any difference ?
(Also give the 2.6.20 kernel from updates-testing a shot)
I know what caused this. Previous kernels returned -ENOTTY (IOCTL
not available) when trying Windows IOCTLs on native Linux filesystems.
David Howells's patch allowing network filesystems without CONFIG_BLOCK
also changed the behavior of ioctl() so it now returns -EINVAL. This
causes applications to error out because they get a return they don't
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.