Problem with file explorer within application

Questions about Wine on Linux
Locked
weatherman2
Newbie
Newbie
Posts: 4
Joined: Wed Jul 16, 2014 7:47 pm

Problem with file explorer within application

Post by weatherman2 »

I use a Windows photo browsing/editing program called BreezeBrowser Pro in Ubuntu. It has worked pretty well in the last few versions. In Ubuntu 12.04 it works with just a few quirks using Wine 1.4.

Unfortunately, in Wine 1.5 and higher, there is an annoying problem that makes it almost unusable. BreezeBrowser has an embedded "file browser" in it to browse different folders of images. For some reason, in Wine 1.5 and newer the file browser shows nothing - just +Desktop that can't be expanded. In older Wine versions, the file explorer shows Desktop, My Computer, etc. I've attached a screen shot of what it should look like , with My Documents, My Computer, etc. showing (and can be expanded). The Desktop is "-" here meaning the tree is expanded underneath. In Wine 1.5, all I have is "+ Desktop" that will not expand.

The application is still functioning - I can still open folders if I know the exact folder path/name but obviously that's a bit impractical for regular use.

Why am I not just using Wine 1.4 then? Because I'm building a new server with Ubuntu 14.04 (64 bit), and I have spent several hours already trying to build Wine 1.4.1 (it is not in the repos so I tried building from source, which was a bit rocky). Then I discovered PlayOnLinux which can build many versions of Wine but I still had problems: I can install my application with Wine 1.4.1 but it won't start at all, something to do with being unable to open the display so it re-opens BreezeBrowser many times/many processes. I found a few google hits with similar issues but nothing that seemed to solve my problem. (If I wanted to continue down this path I should probably start a separate thread.)

It would be nice of course if I didn't have to rely on an old version of Wine anyway. Any ideas on how I might try to get the file explorer functioning so I can see the whole directory structure/tree? Thank you!
Attachments
BreezeBrowser_Wine141.png
BreezeBrowser_Wine141.png (15.07 KiB) Viewed 3118 times
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: Problem with file explorer within application

Post by dimesio »

You keep mentioning 1.5 as if it were current, which makes me wonder if you you've even tried the current development release, 1.7.22. If you haven't, do that. Older releases are no longer supported.

If the problem is present in current Wine, post terminal output from plain Wine (no POL).

This could be a regression, but the fact that it doesn't work in the older version of Wine on the new system suggests the problem may be something else in the host system. You may be missing a needed library, or some library may have changed in a way that is causing the problem.

Note that POL is not supported here, so if you want help with your problems with Wine built through POL, ask for it on the POL forum.
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: Problem with file explorer within application

Post by dimesio »

Is this the app, and does the trial version have the same problem on your system? http://www.breezesys.com/downloads.htm
weatherman2
Newbie
Newbie
Posts: 4
Joined: Wed Jul 16, 2014 7:47 pm

Re: Problem with file explorer within application

Post by weatherman2 »

Thank you for your reply. Yes, that is my application that you found on breezesys.com.

To clarify: I first noticed this problem with wine 1.5 which is why I mentioned that particular version. 1.4.1 was the last version in which it worked. But I have tried several other wine versions including 1.7.22 and the problem persists in each of them too.

The problem is the same whether I use the trial option or activate the software.

Here is the terminal output from Wine 1.7.22:

Code: Select all

fixme:exec:SHELL_execute flags ignored: 0x00000100
fixme:exec:SHELL_execute flags ignored: 0x00004100
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessShutdownParameters (00000100, 00000001): partial stub.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
fixme:wbemprox:client_security_SetBlanket 0x7db3e388, 0x13f548, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0x7db3e388
fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0)
fixme:wbemprox:client_security_SetBlanket 0x7db3e388, 0x140140, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0x7db3e388
fixme:win:RegisterDeviceNotificationA (hwnd=0x2003a, filter=0x33e5b4,flags=0x00000000) returns a fake device notification handle!
fixme:msvcrt:__clean_type_info_names_internal (0x782bc940) stub
(That last line appeared only when I excited the application.)

For reference, here is the output where the problem does not occur, from Wine 1.4.1 (on a different Ubuntu installation however):

Code: Select all

fixme:exec:SHELL_execute flags ignored: 0x00000100
fixme:exec:SHELL_execute flags ignored: 0x00004100
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessShutdownParameters (00000100, 00000001): partial stub.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
fixme:wbemprox:wbem_locator_ConnectServer 0x139ec0, L"ROOT\\CIMV2", (null), (null), (null), 0x00000000, (null), (nil), 0x10be9f4)
fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS
fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0)
fixme:wbemprox:wbem_locator_ConnectServer 0x13b1f8, L"ROOT\\CIMv2", (null), (null), (null), 0x00000000, (null), (nil), 0x11be9fc)
fixme:wbemprox:wbem_locator_ConnectServer 0x13b1f8, L"ROOT\\CIMv2", (null), (null), (null), 0x00000000, (null), (nil), 0x10be9fc)
fixme:wbemprox:wbem_locator_ConnectServer 0x13b1f8, L"ROOT\\CIMv2", (null), (null), (null), 0x00000000, (null), (nil), 0x11be9fc)
fixme:wbemprox:wbem_locator_ConnectServer 0x13b1f8, L"ROOT\\CIMv2", (null), (null), (null), 0x00000000, (null), (nil), 0x10be9fc)
fixme:wbemprox:wbem_locator_ConnectServer 0x13b220, L"ROOT\\CIMv2", (null), (null), (null), 0x00000000, (null), (nil), 0x11be9fc)
fixme:reg:RegSetKeySecurity :(0x70,4,0xf90040): stub
fixme:win:RegisterDeviceNotificationA (hwnd=0x10062, filter=0x33e5c4,flags=0x00000000) returns a fake device notification handle!
fixme:win:UnregisterDeviceNotification (handle=0xcafecafe), STUB!
fixme:win:RegisterDeviceNotificationA (hwnd=0x20062, filter=0x33d858,flags=0x00000000) returns a fake device notification handle!
fixme:ntdll:server_ioctl_file Unsupported ioctl 24000 (device=2 access=1 func=0 method=0)
fixme:win:UnregisterDeviceNotification (handle=0xcafecafe), STUB!
mogorva
Level 4
Level 4
Posts: 107
Joined: Fri Oct 16, 2009 10:27 am

Re: Problem with file explorer within application

Post by mogorva »

This is indeed a regression, reported in this bug report
weatherman2
Newbie
Newbie
Posts: 4
Joined: Wed Jul 16, 2014 7:47 pm

Re: Problem with file explorer within application

Post by weatherman2 »

Thanks very much! I tried the recommended work-around:

'winetricks comctl32' + mfc80.dll are needed to work around the problem.

but after running "winetricks comctl32" I'm having a conflict with mfc80.dll

Code: Select all

Cannot find import.  DLL may be missing, corrupt, or wrong version, MFC80.DLL Error 126.
and now BreezeBrowser won't start. I guess I don't know what I'm supposed to do after that to fix mfc80.dll - thoughts?
weatherman2
Newbie
Newbie
Posts: 4
Joined: Wed Jul 16, 2014 7:47 pm

Re: Problem with file explorer within application

Post by weatherman2 »

Never mind - copied a mfc80.dll from Windows 8 and replaced the old one in Wine and it worked, fixed the problem.

Thank you!!!
Locked