Issue 117675

Summary:	Selecting menu Format/Cells.... crashes on Snow Leopard 10.6
Product:	Calc	Reporter:	peter.teeson
Component:	editing	Assignee:	AOO issues mailing list <issues>
Status:	UNCONFIRMED ---	QA Contact:	RottenEogat <RottenEogat>
Severity:	Normal
Priority:	P2	CC:	firezyra, issues
Version:	OOo 3.3
Target Milestone:	---
Hardware:	Mac
OS:	Mac OS X 10
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description peter.teeson 2011-04-03 21:25:51 UTC

This has been a problem ever since I upgraded to 3.0

How to reproduce:
Create new SS. Enter a number. Select the cell. From Format menu select Cells....
Crash.

Here are the console log entires.
11-04-03 4:44:22 PM	[0x0-0x30030].org.openoffice.script[745]	Sun Apr  3 16:44:22 Gandalf.local soffice[745] <Error>: kCGErrorIllegalArgument: CGSOrderWindowList
11-04-03 4:44:22 PM	[0x0-0x30030].org.openoffice.script[745]	Sun Apr  3 16:44:22 Gandalf.local soffice[745] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
11-04-03 4:44:22 PM	com.apple.launchd.peruser.501[272]	([0x0-0x30030].org.openoffice.script[745]) Tried to setup shared memory more than once

P.S.
OO 3.3.0 ooo330m20 (Build 9567)
Mac OS X 10.6.6 MacPro

Comment 1 Marcus 2011-04-15 08:44:18 UTC

please can you try to reproduce this?

Comment 2 peter.teeson 2011-04-15 13:39:17 UTC

As you can see from the description when I filed the bug I can reproduce it at will. I documented how to do it -----

"How to reproduce:
Create new SS. 
Enter a number. 
Select the cell. 
From Format menu select Cells....
Crash."

and provided the console logs and my environment.

What else do you need?

respect...

Peter

Comment 3 Oliver-Rainer Wittmann 2012-06-13 12:18:03 UTC

getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.

Comment 4 Rob Weir 2013-07-30 02:15:39 UTC

Reset assignee on issues not touched by assignee in more than 2000 days.

Comment 5 firezyra 2013-11-13 02:11:10 UTC

I tried it in 4.0.1 and nothing happened.  The bug has probably been fixed by now.