Bug 225055
Summary: | wine use causes shutdown problem | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mike <mikelayzell> |
Component: | wine | Assignee: | Andreas Bierfert <andreas.bierfert> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-04-16 15:37:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike
2007-01-28 09:40:44 UTC
Can you please try to upgrade to 0.9.29 and start with a clean ~/.wine directory and see if it still is an issue? Sorry Andreas, somehow I missed saying that I have version 0.9.29 in core6. It's 0.9.27 in core4 were I have no problem. I'll completely uninstall wine and start again, and report back. OK used yumex to uninstall all wine components listed. Deleted ~/.wine directory. Installed wine, wine core and their depedencies with yumex, from FC6 extras repo. Typed winecfg in terminal, that reported creating ~/.wine successfully. I then set audio driver to alsa in the wine configure gui. Terminated all applications. Did "poweroff" in terminal. Problem is still there. Not sure if this will help, but I've just had an email from a person with a similar sounding problem in a slackware installation, his was caused by compiling the exec-shield patch into his kernel. Mike Thanks the information. Exec shield is part of the fedora kernel as well. Look at /proc/sys/kernel/exec-shield. Here it is enabled on both my amd64 and my i386 box and both work fine but if you want try setting its value to 0 and retry if the problem still exists. Yes it's enabled on mine as well, with just a 1. I tried changing that to a 0 as root but it won't let me. I get this message I've never seen before. Warning the file has changed since reading it!! Do you want to write to it (y/n)? I type y and get this. E667: Esync failed. Press enter or type command to continue. Problem does still exist. Mike Uninstalled wine 0.9.29.fc6 today with rpm -e Even that caused shutdown problem. I'm in the process of reinstalling the version that works in core4 (0.9.27.fc4) to see if that makes any difference, but I have a few dependency problems to resolve first. I'll get back with any results. Mike Used openoffice today and that also caused problem. tried writer, impress and spreadsheet, all of them cause the problem. Wine has been unistalled for over a week, haven't been able to install core4 version. tomorrow I get a new data alocation so I'll completely update the system. If that fixes problem I'll report back. Mike If it is the same with open office or other apps and wine is not installed I'd say it is not a wine bug. Since there has been no activity I will close this bug. Feel free to reopen if the issue still occurs. Just returned from a 2 month holiday, when I applied the latest updates it sorted the problem. Now running wine and open office no problems. |