WineHQ
Wine Forums

Board index » WineHQ » Wine Help » Linux

It is currently Tue Feb 19, 2019 5:30 am
All times are UTC - 6 hours [ DST ]
View unanswered posts | View active topics
 



 Page 1 of 1 [ 8 posts ] 
Post a new topic">
Post a reply



fsutil unsupported command

  Previous topic Previous topic | Next topic Next topic
 

fsutil unsupported command

Author Message
hiigaran
 Post Posted: Wed Jan 09, 2019 2:06 am 
Offline
Level 2
Level 2

Joined: Fri Sep 22, 2017 12:41 am
Posts: 32
One of the programs I run under Wine has a seemingly random chance of successfully opening and running. Looking over the terminal output, there is a line that only appears when the program fails to start correctly, which is shown below:

Code:
006d:fixme:fsutil:wmain unsupported command L"dirty"


The program in question is Vortex, a mod manager for games. During normal operation, a splash screen shows up, which is just a white rectangular window, before the program fully loads. When the program does not work, that same splash screen comes up, but it never gets further than that. The line above also appears at the same time, forcing me to Ctrl+C out of the terminal.

What baffles me is that this isn't a consistent problem, and I can't figure out what triggers it. I've had successful and unsuccessful operation of the program with 11 days uptime, directly after a reboot, and between various routine system updates. winecfg has not changed.

System info:

Ubuntu 18.10
nVidia 415.25
Wine 4.0-rc5 (also tried successfully and unsuccessfully on rc4)

winecfg overrides:

DXVK (installed as per instructions from git)
dotnet40/45/46/461 (through winetricks)

Running with Windows 10 settings, though tried XP as well. Both gave successful and unsuccessful operations of program).

This isn't a major or urgent issue, of course. Usually I just wait an hour or so and the problem seems to go away. Just a curious oddity.
Top 
Bob Wya
 Post Posted: Sun Jan 13, 2019 8:11 am 
Offline
Level 12
Level 12
User avatar

Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2419
Location: Cambridge
@hiigaran

That error is a bit puzzling.
Looking at the syntax for Fsutil, it should require more arguments, as in:
Code:
fsutil dirty {query | set} <VolumePath>


E.g. on native Windows 7:
Code:
.\fsutil.exe dirty
---- DIRTY Commands Supported ----

query           Query the dirty bit
set             Set the dirty bit

.\fsutil.exe dirty query C:
Volume - C: is NOT Dirty


So I'm puzzled why you are seeing that output, unless it is to do with a .Net wrapper for the command.
E.g.
Code:
wine fsutil.exe dirty
0009:fixme:fsutil:wmain stub: L"C:\\windows\\system32\\fsutil.exe" L"dirty"

with Wine 4.0-rc6.
Any further arguments to fsutil should also be dumped to the terminal.

Currently fsutil is 100% stubbed in Wine, and does nothing.

See: wine 4.0-rc6: /programs/fsutil/main.c

Bob
Top 
hiigaran
 Post Posted: Sun Jan 13, 2019 8:57 am 
Offline
Level 2
Level 2

Joined: Fri Sep 22, 2017 12:41 am
Posts: 32
Next time it happens, I'll post the entire terminal output in case there's something else.

Either way, I figured I'd just post in case it's useful information for someone.
Top 
hiigaran
 Post Posted: Wed Jan 16, 2019 12:04 pm 
Offline
Level 2
Level 2

Joined: Fri Sep 22, 2017 12:41 am
Posts: 32
Right, so it happened again. See anything useful in the terminal output?

Code:
hiigaran@hiigaran:~$ wine .wine/drive_c/Program\ Files/Black\ Tree\ Gaming\ Ltd/Vortex/Vortex.exe
000b:fixme:winediag:start_process Wine Staging 4.0-rc6 is a testing version containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
0012:fixme:wer:WerSetFlags (2) stub!
0012:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
001c:fixme:heap:RtlSetHeapInformation 0x240000 0 0x23e740 4 stub
001c:fixme:wer:WerSetFlags (2) stub!
001c:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0036:fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0x00000000>
0036:fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0x00000000>
0036:fixme:msvcrt:_configure_wide_argv (1) stub
0036:fixme:msvcrt:_initialize_wide_environment stub
0036:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0036:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x23f460 1 C) semi-stub

0036:fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x14033cb00, 0x143cf2170, 0x143d5be38) stub.
0036:fixme:dwrite:get_name_record_codepage encoding 20 not handled, platform 1.
0036:fixme:dwrite:get_name_record_codepage encoding 20 not handled, platform 1.
0036:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x23e500 1 C) semi-stub
0036:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x23dfb0 1 C) semi-stub
0036:fixme:ntdll:NtQueryVolumeInformationFile 0x13c: faking volume info
info: steam not found error=File not found. 'Software\Valve\Steam'
0036:fixme:nls:GetThreadPreferredUILanguages 00000038, 0x23f554, (nil) 0x23f550
0036:fixme:nls:get_dummy_preferred_ui_language (0x38 0x23f554 (nil) 0x23f550) returning a dummy value (current locale)
0036:fixme:nls:GetThreadPreferredUILanguages 00000038, 0x23f554, 0x25cede0 0x23f550
0036:fixme:nls:get_dummy_preferred_ui_language (0x38 0x23f554 0x25cede0 0x23f550) returning a dummy value (current locale)
0036:fixme:winsock:WSALookupServiceBeginW (0x23eee0 0x00000ff0 0x23eed8) Stub!
0036:fixme:iphlpapi:NotifyAddrChange (Handle 0x23f180, overlapped 0x25a1af8): stub
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
0036:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
004d:fixme:wlanapi:WlanEnumInterfaces (0x1, (nil), 0xbf1f188) semi-stub
0036:fixme:win:RegisterDeviceNotificationW (hwnd=0x10060, filter=0x23f230,flags=0x00000000) returns a fake device notification handle!
0036:fixme:win:RegisterDeviceNotificationW (hwnd=0x10060, filter=0x23f230,flags=0x00000000) returns a fake device notification handle!
0036:fixme:msg:ChangeWindowMessageFilterEx 0x10062 4a 1 (nil)
004d:fixme:wlanapi:WlanEnumInterfaces (0x1, (nil), 0xbf1e768) semi-stub
0036:fixme:dwmapi:DwmIsCompositionEnabled 0x23d3a0
0036:fixme:win:RegisterTouchWindow (0x10068 00000002): stub
0036:fixme:wtsapi:WTSRegisterSessionNotification Stub 0x30046 0x00000000
0036:fixme:explorerframe:taskbar_list_DeleteTab iface 0xc7bb240, hwnd 0x10068 stub!
0036:fixme:shcore:GetCurrentProcessExplicitAppUserModelID 0x23bd28: stub
0036:fixme:combase:RoGetActivationFactory (L"Windows.UI.ViewManagement.UIViewSettings", {3694dbf9-8f68-44be-8ff5-195c98ede8a6}, 0x23b9e8): semi-stub
0036:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ViewManagement.UIViewSettings"
0036:fixme:combase:RoGetActivationFactory (L"Windows.UI.ViewManagement.UIViewSettings", {3694dbf9-8f68-44be-8ff5-195c98ede8a6}, 0x23b9e8): semi-stub
0036:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ViewManagement.UIViewSettings"
0036:fixme:win:RegisterTouchWindow (0x1006e 00000002): stub
0036:fixme:process:GetProcessMitigationPolicy (0xffffffffffffffff, 4, 0x23e8f0, 4): stub
005a:fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0x00000000>
005a:fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0x00000000>
005a:fixme:msvcrt:_configure_wide_argv (1) stub
005a:fixme:msvcrt:_initialize_wide_environment stub
005a:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
005a:fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x14033cb00, 0x143cf2170, 0x143d5be38) stub.
005a:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x23f2e0 1 C) semi-stub
005a:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x23ed60 1 C) semi-stub
005a:fixme:gdi:GdiInitializeLanguagePack stub
005a:fixme:ntdll:NtQueryVolumeInformationFile 0x244: faking volume info
0036:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x22a000 1 C) semi-stub
0036:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x229f80 1 C) semi-stub
006e:fixme:fsutil:wmain unsupported command L"dirty"


This is from the start of the program, to the point where it hangs. No further output is seen no matter how long I wait.

Two questions: What's with all the fixme lines, and what's a stub?
Top 
DarkShadow44
 Post Posted: Wed Jan 16, 2019 12:17 pm 
Offline
Level 6
Level 6
User avatar

Joined: Tue Nov 22, 2016 5:39 pm
Posts: 651
Can you try to run it with WINEDEBUG=+fsutil and post the log when it happens? I guess it wants to query the dirty bit, maybe it helps when we just return an OK value. But since there is no way to reliably trigger that issue it'll be hard to test...

Regarding your questions:
A fixme is a message that there is functionality missing, but most of the time you can just ignore that.
A stub is a function that doesn't do anything, it just exists so the program doesn't crash trying to use it.
Top 
hiigaran
 Post Posted: Fri Jan 18, 2019 3:05 pm 
Offline
Level 2
Level 2

Joined: Fri Sep 22, 2017 12:41 am
Posts: 32
I see this line:

Code:
006e:trace:fsutil:wmain  L"fsutil" L"dirty" L"query" L"c:"


Though this was a successful startup of the program. Will let you know what I get when it fails.
Top 
DarkShadow44
 Post Posted: Fri Jan 18, 2019 10:24 pm 
Offline
Level 6
Level 6
User avatar

Joined: Tue Nov 22, 2016 5:39 pm
Posts: 651
You got
Code:
006e:trace:fsutil:wmain  L"fsutil" L"dirty" L"query" L"c:"

but not a
Code:
006e:fixme:fsutil:wmain unsupported command L"dirty"
?

This shouldn't be possible.
Top 
hiigaran
 Post Posted: Sat Jan 19, 2019 3:31 am 
Offline
Level 2
Level 2

Joined: Fri Sep 22, 2017 12:41 am
Posts: 32
Actually, I got that one on the line afterwards. This seems to suggest the problem lies elsewhere when it fails to start.
Top 
Display posts from previous:  Sort by  
 
 Page 1 of 1 [ 8 posts ] 




Board index » WineHQ » Wine Help » Linux

It is currently Tue Feb 19, 2019 5:30 am
All times are UTC - 6 hours [ DST ]
View unanswered posts | View active topics
 

Who is online

Users browsing this forum: Google [Bot] and 9 guests

 
 

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: