Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 225055 - wine use causes shutdown problem
Summary: wine use causes shutdown problem
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: 6
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-28 09:40 UTC by Mike
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-04-16 15:37:39 UTC

Attachments (Terms of Use)

Description Mike 2007-01-28 09:40:44 UTC
Description of problem:
running Fedora Core6 on a modern PC.
Any time I invoke wine, either running a windows program or winecfg, (which run
fine), when I go to "System" "Shutdown" the panels and icons dissapear, the
keyboard becomes inactive but I'm left with the desktop wallpaper and an active
mouse cursor, then I have to turn the power off.
However if I do "poweroff" at a terminal, initially I get the same wallpaper and
mouse, but after several seconds the computer does shutdown.

I've checked in system monitor that no wine programs are still running after I
terminate the windows app

Also running core4 on this PC, that doesn't have this problem, but it's wine
version  0.9.27

How reproducible: every time

Steps to Reproduce:
1. use wine in some way
2. shutdown computer
Actual results:
don't get a terminal screen with the shut down progress on it.
get desktop wallpaper and an active mouse cursor.
If shutdown initated from gnome or kde that's how it stays.
If shutdown initiated from terminal with "poweroff", after a while the mouse
becomes inactive, then system shuts down.

Expected results:
Normal shutdown sequence

Additional info:

I sent this to wine bugzilla earlier today, but got a reply from them saying it
was more likely a FC6 problem.

Comment 1 Andreas Bierfert 2007-01-28 11:21:35 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?

Comment 2 Mike 2007-01-29 09:57:49 UTC
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.

Comment 3 Mike 2007-01-29 13:30:12 UTC
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.


Comment 4 Andreas Bierfert 2007-01-29 14:12:43 UTC
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.

Comment 5 Mike 2007-01-30 11:35:54 UTC
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.


Comment 6 Mike 2007-02-03 12:46:14 UTC
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.

Comment 7 Mike 2007-02-09 11:31:05 UTC
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

tomorrow I get a new data alocation so I'll completely update the system. If
that fixes problem I'll report back.


Comment 8 Andreas Bierfert 2007-04-16 15:37:39 UTC
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.

Comment 9 Mike 2007-04-17 08:48:19 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.