Export to GitHub

winezeug - issue #191

comctl32(.ocx) crashes dialogs


Posted on Oct 21, 2010 by Massive Kangaroo

What steps will reproduce the problem? 1. Install excel 2003 2. install comctl32(and/or comctl32.ocx) 3. open the external data import dialog in excel 4. the whole thing will crash

What is the expected output? What do you see instead? I expect the dialog to open, instead the whole excel crashes.

What version of the product are you using? On what operating system? Currently wine 1.3.5, excel 2003, Debian Squeeze.

Please provide any additional information below. Well, I have some other winetricks packages installed (msxml3-4, corefonts mfc40-42), but neighter of those crash excel. I installed them one by one and tested excel after which package it crashes. It was the comctl32. I have a feeling that accented letters might affect this crash, like á, é, ó and others. I noticed that this only happens when you open a dialog where there are accented letters. ASCII letters don't have any negative effects so far. The fontfix package doesn't fix the problem.

And finally, not only excel crashes, but any app that has accented letters in dialogs. One more important info: Accented letters have to be in a kind of "changeble field" to crash the app (like the replace dialog in word 2003, or a hungarian office 2003 installer where you can customize which parts install).

Comment #1

Posted on Oct 21, 2010 by Quick Rabbit

Can you attach the backtrace?

Comment #2

Posted on Oct 21, 2010 by Massive Kangaroo

OK. First of all that is what it writes at every app: "The program DW20.EXE has encountered a serious problem and needs to close. We are sorry for the inconvenience." Second: here's the backtrace attached.

Attachments

Comment #3

Posted on Oct 21, 2010 by Happy Giraffe

that's btall, which is only appropriate for hangs, I think.

Can you do 'winetricks nocrashdialog', let the program crash, and send the log? That should have a nice backtrace.

Comment #4

Posted on Oct 21, 2010 by Happy Giraffe

that's btall, which is only appropriate for hangs, I think.

Can you do 'winetricks nocrashdialog', let the program crash, and send the log? That should have a nice backtrace.

Comment #5

Posted on Oct 21, 2010 by Massive Kangaroo

OK. Here's another try. Now I used the command found here: http://wiki.jswindle.com/index.php/Debugging_Wine#Faster_debugging

The command was: WINEDEBUG=+ddraw,+d3d7 wine EXCEL.EXE > ExcelCrash.log 2>&1

I hope that suits more than the previous one.

If you need something else, just reply, and I'll try to send the needed output.

Attachments

Comment #6

Posted on Nov 21, 2010 by Swift Kangaroo

The problem with comctl32 seems quite basic. With a fresh wine and winetricks comctl32:

  • regedit shows its icons on a black background.
  • winetricks mdac28 will fail with "installation program appears to be damaged", a FIXME ntdll:NtQueryInformationProcess Unimplemented information class ProcessWx86Information is thrown on the command line (calling mdac_typ directly works, must be an interference with version=win98)
  • a commercial app throws several access violations

The update described here http://code.google.com/p/winezeug/issues/detail?id=194 won't make any difference: the installer fails, manually copying 5.82.2800 or 5.82.2900 doesn't help.

Comment #7

Posted on Nov 21, 2010 by Swift Kangaroo

Copying all DLLs from the SP2QFE-Folder of KB923191 to the system32 folder fixed the commercial app I've been testing with, regedit will still show its icons on black background.

Comment #8

Posted on Nov 22, 2010 by Quick Rabbit

Can someone find a downloadable app I can test this with? Does wine notepad have the same problem?

Comment #9

Posted on Nov 23, 2010 by Swift Kangaroo

I don't see a problem with Notepad (native or wine), depends.exe works well too. The treeview in regedit (wine AND native version) has the icon display problem using native comctl32, both are ok with builtin.

Comment #10

Posted on Nov 23, 2010 by Quick Rabbit

The black display problem has always been there, that seems to be a microsoft bug, but it's non-fatal. The crash is the one I'm worried about.

Status: New

Labels:
Type-Defect Priority-Medium