Pages & Preview crash when printing

Hi folks,

System: iMac G5, OS X 10.5.1 with all updates;
Printer: an old Laserwriter IIg attached via Ethernet to my network;
iWork (Pages) '08

Ever since upgrading to Leopard, both Preview and Pages crash after a
document is sent to be printed. The document prints successfully, but
the apps crash with the following message:

"The Application Preview quit unexpectedly.

"OS Version: Mac OS X 10.5.1 (9B18)
"Report Version: 6

"Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c2247fef
Crashed Thread: 0"

The crash report has been sent to Apple

This never happened before updating to Leopard and I'm hopeful someone
might have a possible solution.

Many thanks in advance,

LKR

--
Loie
.

Relevant Pages

  • Re: MacBook Pro: accidentally logged out from Dock?
    ... crash report for process loginwindow ... The loginwindow crash log will tell us even more about why loginwindow ... crash report for loginwindow reported by your system: ... The battery was about half full, ...
    (comp.sys.mac.system)
  • Re: Mac fanboys tell the truth about OS X updates
    ... Apple store in San Francisco to buy it immediately but got spiked ... And the applications themselves seemed to crash far less. ... Leopard update weeks after the launch. ... compromises that Apple made to get Leopard out the door by their self- ...
    (comp.sys.mac.advocacy)
  • Re: Leopard - slowwwww and strange issues
    ... installation seemed to go right, it sure did take forever. ... Major - my main user will crash the system everytime, ... Overall I like the look and feel of Leopard, but it is slower than Tiger ...
    (comp.sys.mac.advocacy)
  • RE: [Full-Disclosure] SCO Web Site Vulnerable to Slapper?
    ... software and not bother with upgrading the version number. ... willing to crash one's server with a live test. ... With binary protocols and major upgrades there tends to be more of a ...
    (Full-Disclosure)
  • Re: VS hangs frequently ...
    ... Crash problems may not be the major problems to my associates although we did have more of them after upgrading from VC++ 6 to VS 2005. ... Most times the studio requires me to do a full rebuild, meaning stopping the debugger and hit F5 to restart. ... I'm working with unmanaged MFC code. ...
    (microsoft.public.vc.mfc)