Launchpad has imported 23 comments from the remote bug at
https://bugs.winehq.org/show_bug.cgi?id=25762.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2011-01-13T03:37:32+00:00 Dimesio wrote:

Opening a new bug now that it's clear bug 25754 is not the same problem.

All versions of Excel that I tested (97, 2003, 2007, and 2010) crash
trying to run a macro.

To reproduce, go to Tools, Macro (in 97 and 2003) or View, Macro (in
2007 and 2010) and select record. Type something in a cell and press
enter, then click the stop button. Go back to the Macro menu and run the
macro that was recorded.

Regression test results:

c0f120db5d6b72917dd9bb1e4630f2b6ff6960a6 is first bad commit
commit c0f120db5d6b72917dd9bb1e4630f2b6ff6960a6
Author: Andrew Eikum <[email protected]>
Date:   Tue Nov 9 16:04:10 2010 -0600

    oleaut32: Search inherited interfaces again in ITypeComp::Bind.

:040000 040000 3b22bce11b0e5dc9df0c30658009c45a0bae7955
add823888e853fc234e1991a6aed674b456c56e8 M      dlls

Reverting that commit fixes the crash.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/0

------------------------------------------------------------------------
On 2011-01-13T14:34:04+00:00 Andrew Eikum wrote:

Okay, I spent some time looking at this this morning and I think it's
not actually a regression.

There are two commits involved here. The first, 3173305e, modifies
ITypeComp::Bind to not return an error code if it fails to find the
member being requested. However, a mistake in the patch introduced a
problem, where parent interfaces were no longer being searched when
looking for that member. This was fixed a couple of months later in
c0f120db.

Before 3173305e, this sequence would cause Excel to crash. Between
3173305e and c0f120db, Excel no longer crashes because it's returning a
failure code and not searching parent interfaces. This is "less correct"
than the crash. After c0f120db it's back to the original behavior of
searching the parent interfaces and subsequently crashing.

So, this isn't a regression caused by that commit. Obviously still a
bug, though :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/1

------------------------------------------------------------------------
On 2011-09-18T12:05:44+00:00 Dimesio wrote:

Still present in 1.3.28.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/2

------------------------------------------------------------------------
On 2012-01-09T15:34:26+00:00 Dimesio wrote:

Still present in 1.3.36.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/3

------------------------------------------------------------------------
On 2012-03-18T15:00:00+00:00 Frenchman20 wrote:

Created attachment 39439
Problem remains in 1.5.0

Wine does not support this command from VBA: Range("A1").Select, where
A2 represents any cell. When a macro runs, Excel will freeze once it
gets to this command.

Hope this helps!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/4

------------------------------------------------------------------------
On 2012-03-18T15:03:53+00:00 Frenchman20 wrote:

(In reply to comment #4)
> Created attachment 39439 [details]
> Problem remains in 1.5.0
> 
> Wine does not support this command from VBA: Range("A1").Select, where *A1
> represents any cell. When a macro runs, Excel will freeze once it gets to this
> command.
> 
> Hope this helps!

*A2 should be A1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/5

------------------------------------------------------------------------
On 2012-05-12T17:13:41+00:00 David Sempsrott wrote:

Here's another scenario that might give some leads. I created a macro in
Excel 2010 (using the 2003 file format .xls), and then tried to run it
in Excel 2007 under Wine 1.4. It ran fine until it got to a statement
that was supposed to copy a range of data:

MySheet1.Range("A1").CurrentRegion.Copy MySheet2.Range("A1")

At this point Excel crashed. I reopened the workbook and modified the
statement as follows:

MySheet1.Cells(1, 1).CurrentRegion.Copy MySheet2.Cells(1, 1)

That worked. But then it came to the following code:

With MySheet2.Range("K1").Cells
    .Offset(0, -2).Value = "Status"
    .Offset(0, -1).Value = "Coverage"
    .Value = "Test case(s)"
    .EntireColumn.AutoFilter Field:=1, VisibleDropDown:=True
End With

And Excel crashed at the autofilter statement. Then I changed the
Range("K1").Cells to Cells(1, 11) and again it worked flawlessly. So it
seems fairly clear to me that the Range part is where the problem is --
although apparently it's only methods, and not properties, that don't
work.

I did get a complaint from Wine several times about not finding Windows Common 
Controls:
fixme:actctx:parse_depend_manifests Could not find dependent assembly 
L"Microsoft.Windows.Common-Controls" (6.0.0.0)

Sorry I'm not very experienced with Wine or VBA, but I hope that might
give a few hints as to where the problem might be.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/6

------------------------------------------------------------------------
On 2012-05-12T17:23:33+00:00 mr.larch wrote:

Please attach +ole,+typelib,+tid log as a text file running current dev.
version 1.5.4.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/7

------------------------------------------------------------------------
On 2012-05-13T01:37:24+00:00 Dimesio wrote:

The log, even compressed, is too big to attach. I've uploaded it here:
https://docs.google.com/open?id=0B98fpwZrfFafdVVNTXFoWW12S0U

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/8

------------------------------------------------------------------------
On 2013-01-12T23:20:12+00:00 Modestas Vainius wrote:

Just in case somebody needs to get macros working quickly, the
workaround for this bug is use native oleaut32.dll (e.g. from Windows XP
installation). It helped for me on wine 1.4.1.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/9

------------------------------------------------------------------------
On 2013-01-26T23:40:16+00:00 Andrew Steffey wrote:

In wine-1.5.22 I was having some trouble with VBA in Excel.
Specifically, Excel would crash whenever it tried to autocomplete any of
the built-in excel add-ons.

Fixed the problem by using winetricks riched20

The issue seems to be related to
http://bugs.winehq.org/show_bug.cgi?id=12458

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/10

------------------------------------------------------------------------
On 2013-07-20T11:03:34+00:00 Ubrammer wrote:

Created attachment 45340
The file contains the debuglog wine.log from calling the macro to the crash.

I made another log of the error with +ole,+typelib,+tid. The log just
starts with the call of the Macro1, which moves one cell down.

It was made with wine 1.6 and excel from Office 2000.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/11

------------------------------------------------------------------------
On 2013-08-18T12:38:18+00:00 Dimesio wrote:

*** Bug 34287 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/18

------------------------------------------------------------------------
On 2013-08-18T14:16:40+00:00 Christopher M. Penalver wrote:

Excel Macro crashing reproducible in wine 1.7 on Linux and Mac OSX as
per my duplicate http://bugs.winehq.org/show_bug.cgi?id=34287 .

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/19

------------------------------------------------------------------------
On 2013-08-19T12:48:16+00:00 Andrew Eikum wrote:

Christopher, could you please email the spreadsheet to me at
<[email protected]>? I'd like to confirm that this is the same
issue. Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/20

------------------------------------------------------------------------
On 2013-09-03T16:11:39+00:00 Piotr-caban wrote:

This bug is caused by incorrect FUNCDESC structure returned for
IRange::Select function (defined in typelib inside EXCEL.EXE).

In this case both calling convention and number of parameters is
incorrect. In order to make EXCEL working only calling convention needs
to be changed to FUNC_DISPATCH.

I'll try to find why it's incorrect.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/22

------------------------------------------------------------------------
On 2013-09-04T16:48:40+00:00 Andrew Eikum wrote:

Created attachment 45863
oleaut32: Apply TKIND_DISPATCH changes to FUNCDESC results from ITypeComp::Bind

Good find, Piotr! This patch lets the macro run. I'm working on tests.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/23

------------------------------------------------------------------------
On 2013-09-07T08:33:26+00:00 Piotr-caban wrote:

It works for me now. Marking as fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/24

------------------------------------------------------------------------
On 2013-09-09T12:04:33+00:00 Andrew Eikum wrote:

If you have an Excel spreadsheet with macros that are still failing,
please file a new bug and add me to the CC list. Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/25

------------------------------------------------------------------------
On 2013-09-13T18:20:04+00:00 Alexandre Julliard wrote:

Closing bugs fixed in 1.7.2.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/26

------------------------------------------------------------------------
On 2014-10-01T20:43:18+00:00 Wcrfrench wrote:

How do you apply this fix? I am getting a similar sounding error when I
call a worksheet function utilising a named range....

Excel just freezes and then must be forced closed.

For instance:

Sub Run()

Dim Num1 As Integer

Num1 = WorksheetFunction.Counta(Range(Range("A1"),Range("A100")))

End Sub

I am new to Linux and wine btw.

Very grateful for any help, determined not to go back to windows, but
desperately need VBA for work!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/27

------------------------------------------------------------------------
On 2014-10-02T12:30:11+00:00 Andrew Eikum wrote:

(In reply to wcrfrench from comment #20)
> How do you apply this fix? I am getting a similar sounding error when I call
> a worksheet function utilising a named range....
> 

Please be sure you're using the latest version of Wine (currently
1.7.27). If you are, you are probably encountering a different bug.
Please open a new bug report with details on how to reproduce.

Feel free to add my email to the CC list. I like to be informed of
typelib bugs.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/28

------------------------------------------------------------------------
On 2014-10-02T18:26:36+00:00 Wcrfrench wrote:

Updating Wine fixed the problem. Many Many Thanks

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1213557/comments/29


** Changed in: wine
       Status: Unknown => Fix Released

** Changed in: wine
   Importance: Unknown => Medium

** Bug watch added: Wine Bugzilla #12458
   https://bugs.winehq.org/show_bug.cgi?id=12458

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213557

Title:
  Excel 2010 32-bit crashes in .xls with Macros

To manage notifications about this bug go to:
https://bugs.launchpad.net/wine/+bug/1213557/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to