You are not logged in.

#1 2013-02-18 01:35:13

Jindur
Member
Registered: 2011-09-29
Posts: 184

[SOLVED] Accidentally ran Wine as root - how to unbrick?

I accidentally ran Wine as root because I issued the command in the wrong terminal where I was logged in as root.. oops.
As a result, wine apps (Steam!) no longer start correctly, it seems as if they can't get network access of any kind, not sure. Also, winecfg now freezes when I click on "Audio" tab.
I tried running wine steam via sudo, and then it actually worked. But I don't really want to run it as root. Also, running winecfg as root still freezes up when clicking on "Audio".
I also tried running Guild Wars 2 in Wine, and it brings up the game but it freezes at 0% update (hence I think some networking stuff is bricked at least).
I already did a chown -R user:group * on .wine to set all permissions back to my normal user and his group, but that didn't help.
Does anyone know how to unbrick Wine from this state?.

Here's what wine spits out when I try to run for example steam.exe - it takes like a minute and then I have to manually terminate it because nothing seems to happen:

$ wine Steam.exe -no-dwrite
fixme:service:scmdatabase_autostart_services Auto-start service L"UMWdf" failed to start: 2
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:advapi:EventRegister {47a9201e-73b0-42ce-9821-7e134361bc6f}, 0x3f0054c0, 0x3f036b40, 0x3f036b38
fixme:advapi:EventRegister {58a9201e-73b0-42ce-9821-7e134361bc70}, 0x3f0054c0, 0x3f036b78, 0x3f036b70
fixme:advapi:EventRegister {3fa9201e-73b0-43fe-9821-7e145359bc6f}, 0x3f0054c0, 0x3f036b08, 0x3f036b00
fixme:advapi:EventRegister {1432afee-73b0-42ce-9821-7e134361b433}, 0x3f0054c0, 0x3f036bb0, 0x3f036ba8
fixme:advapi:EventRegister {4372afee-73b0-42ce-9821-7e134361b519}, 0x3f0054c0, 0x3f036be8, 0x3f036be0
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
Looks like steam didn't shutdown cleanly, scheduling immediate update check
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:advapi:EventRegister {47a9201e-73b0-42ce-9821-7e134361bc6f}, 0x3f0054c0, 0x3f036b40, 0x3f036b38
fixme:advapi:EventRegister {58a9201e-73b0-42ce-9821-7e134361bc70}, 0x3f0054c0, 0x3f036b78, 0x3f036b70
fixme:advapi:EventRegister {3fa9201e-73b0-43fe-9821-7e145359bc6f}, 0x3f0054c0, 0x3f036b08, 0x3f036b00
fixme:advapi:EventRegister {1432afee-73b0-42ce-9821-7e134361b433}, 0x3f0054c0, 0x3f036bb0, 0x3f036ba8
fixme:advapi:EventRegister {4372afee-73b0-42ce-9821-7e134361b519}, 0x3f0054c0, 0x3f036be8, 0x3f036be0
fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub.
fixme:iphlpapi:NotifyAddrChange (Handle 0x5a8d69c, overlapped 0x58a4a70): stub
fixme:winsock:WSALookupServiceBeginW (0x5a8d79c 0x00000ff0 0x5a8d7e4) Stub!
[0218/020119:ERROR:network_change_notifier_win.cc(111)] WSALookupServiceBegin failed with: 8
fixme:advapi:EventUnregister deadbeef: stub
fixme:advapi:EventUnregister deadbeef: stub
fixme:advapi:EventUnregister deadbeef: stub
fixme:advapi:EventUnregister deadbeef: stub
fixme:advapi:EventUnregister deadbeef: stub

Last edited by Jindur (2013-02-18 02:13:11)

Offline

#2 2013-02-18 01:56:54

hiciu
Member
Registered: 2010-08-11
Posts: 78

Re: [SOLVED] Accidentally ran Wine as root - how to unbrick?

Try this:

chown -R jindur:users ~/.wine

(edit: I see you did "chmod -R user:group". Chmod can change permissions, chown can change owner. I'm not sure if that was typo.)

Last edited by hiciu (2013-02-18 01:58:37)

Offline

#3 2013-02-18 02:03:18

Jindur
Member
Registered: 2011-09-29
Posts: 184

Re: [SOLVED] Accidentally ran Wine as root - how to unbrick?

Oh thank you, but that was a typo on my part, sorry. I did chown, not chmod.

Also I tried renaming my .wine folder and then calling winecfg, so it generates a fresh .wine folder.
However, winecfg would STILL freeze when clicking on Audio tab!! What's going on?

Last edited by Jindur (2013-02-18 02:04:26)

Offline

#4 2013-02-18 02:12:49

Jindur
Member
Registered: 2011-09-29
Posts: 184

Re: [SOLVED] Accidentally ran Wine as root - how to unbrick?

-_- sorry, apparently a reboot fixed it. I'm just not used to rebooting..

Offline

Board footer

Powered by FluxBB