Closed Bug 187127 Opened 22 years ago Closed 21 years ago

Mozilla quits if printing message is impossible because printer is not selected in Chooser

Categories

(MailNews Core :: Printing, defect, P2)

PowerPC
Mac System 9.x
defect

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: michael.graubart7, Assigned: john)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.3b) Gecko/20021229
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.3b) Gecko/20021229

Four times, when I tried to print e-mail messages, Mozilla quitted. See Talkback
reports TB15608727H, TB15608768W, TB15608824X and TB15608937X. Then I discovered
that owing to a change I had made in the extensions selected as active, a
non-existent printer was selected in Chooser; when I rectified this, printing
proceeded normally. But surely my Mac should have been allowed to show me a
message about an incorrect printer being selected, but Mozil;la should not have
crashed?

Reproducible: Always

Steps to Reproduce:
1. In Extensions Manager, activate printer software for a printer that is not
available.
2. In Chooser, select the non-existent printer (or select no printer?)
3. Go to Mozilla Mail inbox, select an e-mail and try to print.

Actual Results:  
Instead of the usual printing messages, followed by the printer window, being
seen, items (such as Launcher) that would have been on the desktop behind the
Mozilla window were briefly visible; then Mozilla quitted (though without
crashing the computer).

Expected Results:  
A message like 'No valid printer has been selected' should appear, and Mozilla
should remain open. (This would allow one at once to rectify the situation in
Chooser and get on with printing, etc.)

Mac G3 (old beige tower); OSD 9.2.2. Modern theme.
is this bug 167459 ?
Don't think it is the same as 167459. The reporter of 167459 complained about
getting a dialog about no printer being selected - but that is just what SHOULD
happen. I complained that I did NOT get the dialog, but that Mozilla quitted
(for no apparent rerason).
0x00000008
nsMsgPrintEngine::FireThatLoadOperationStartup() [nsMsgPrintEngine.cpp, line 507]
nsMsgPrintEngine::StartNextPrintOperation() [nsMsgPrintEngine.cpp, line 469]
nsMsgPrintEngine::StartPrintOperation() [nsMsgPrintEngine.cpp, line 353]
CODE.10
XPTC_InvokeByIndex() [xptcinvoke_mac.cpp, line 145]
XPCWrappedNative::CallMethod() [xpcwrappednative.cpp, line 2015]
XPC_WN_CallMethod() [xpcwrappednativejsops.cpp, line 1292]
js_Invoke() [jsinterp.c, line 839]
js_Interpret() [jsinterp.c, line 2803] 
Status: UNCONFIRMED → NEW
Ever confirmed: true
See Talkback reports: TB 15735844G and TB15735937K.

These two crashes turned out to be further examples of Mozilla quitting instead
of  displaying a 'No printer' warning, but the circumstances were slightly
different:
1. I was trying to print from a web-site, not an e-mail.
2. It was not a wrong selection in 'Chooser' that resulted in the printer not
cooperating, but another application (namely Palm HotSynch) that somewhat
mysteriously, and without human agency, got itself switched to using the printer
port between my printing from the web-site and my trying to print one page again
with a different colour profile setting. 
-> jkeiser
Assignee: dcone → jkeiser
Priority: -- → P2
Target Milestone: --- → Future
This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.

I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".
Since Mozilla is no longer supported on Mac OS X pre-OS X I am attepting to test
the remaining open bugs (all 175 of them).

The test client will be the Mozilla (SeaMonkeys) 1.6.

Result/Status: Not valid for OS X
Mac Classic specific bug. This platform is dead. Not valid on other OS. Marking
WONTFIX.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.