User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050702 Problem also occurs Firefox, Firefox(latest nightly build), but not IE. Clicking on print on this complex maths page brings up the PRINT window; clicking on [OK] causes a complete reboot, as if power cycled. Evn the screen goes off. 100% repeatable every time. Completely virgin load of Mozilla no setting altered. Nothing funny about the OS or printer settings etc. More details available about printer drivers etc if needed. Reproducible: Always Steps to Reproduce: 1. http://mathworld.wolfram.com/MoebiusFunction.html 2. Click on [PRINT] 3. Click on [OK}
Could you install with talkback and get a talkback ID for the crash? http://kb.mozillazine.org/Talkback
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20051230 SeaMonkey/1.5a Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 checked File->Print Preview, all was fine checked File->Print, all was fine, error message came after some time because I don't have a printer connected. Printer driver: Canon BJ-330 ink jet printer, monochrome. Paul, what does happen if you just select File->Print Preview? What Printer do you use, a windows only Laser Printer?
Talkback was not triggered. Just (hardware) rebooted again. Interestingly Windows does not show a "Windows was not shutdown correctly" msg after reboot. Printer is Hewlett Packard OfficeJet G85 with Factory Settings. I've never seen this problem before except on this page with Mozilla+-Firefox. Print Preview is OK. I'll try printing via the Print Preview screen in just a minu...
Print to file also crashes. No file created.
Maybe related to Core bug 212829 comment 2?
Your agent string says Firefox but you filed this as a mozilla suite problem. Please clarify your setup. print to file uses installed printer's drivers, so not surprising you get the same error. The reboot really suggests it's not a mozilla problem, but here's some items to try: copy entire web page, paste into a new Word document and print different driver newer HP driver a trunk build. different driver, for example generic text add>local>UseTheFollowingPort=file>Manufacture=generic>etc or the free http://pdf995.com/download.html There are printer bugs fixed on trunk so you might try a trunk build http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ Perhaps HP does not have a god reputation for their all in one drivers http://groups.google.com/group/microsoft.public.windowsxp.perform_maintain/browse_thread/thread/ba6af1331af5ba79/d77d4c4c5dbe59d7?lnk=st&q=G85+crash+%7C+reboot+%7C+hang+%7C+blue+windows+%7C+XP+HP+OR+OfficeJet+%22Hewlett+Packard+%22+-blue-tape&rnum=1&hl=en#d77d4c4c5dbe59d7 http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=798272 http://www.cio.com/blog_view.html?CID=21694 [mac]http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0xdebfcf38d6bdd5118ff10090279cd0f9%2C00.html&admit=-682735245+1152809806230+28353475 see also Bug 198094 comment 2
Summary: Crash, causing complete reboot whilst trying to print → Crash, causing complete reboot whilst trying to print via HP G85
Bug first found with Firefox, but the FAQ recommends reproducing the bug on Mozilla and then reporting against Mozilla. "copy entire web page, paste into a new Word document and print" Doesn't crash. I will try the other suggestions.
ispiked: sounds like a blue screen, don't suggest talkback. reporter: start>settings>control panel>administration>event viewer does your system list an unexpected reboot? we have pieces of a howto foating around. this is a copy from bug 307535 which is about a bluescreen bsod (keywords listed here so that gmail will find it faster, i'm tired of not finding this text): bug 340626 is one of the later ones, probably the best read is bug 307577 since while it's not fixed it does include a complete dialog with a happy customer (we helped him track his problem to a bad font) the initial steps are: 1. right click my computer 2. select properties 3. go to advanced. 4. startup and recovery settings. 5. change write debugging information to Complete memory dump. 6. grab windbg from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx 7. install it 8. run it 9. file>open crash>browse to the .dmp file 10. !analyze -v -f remember that you only get one .dmp and it costs as much as you have memory, so you'll want to rename it as soon as your system reboots (if you have space to store a couple). There are some instructions at http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg but basically what i've list above is sufficient (hopefully someone will work to integrate these)
timeless, can you this bug reproduce with SeaMonkey v1.1.9?
> timeless, can you this bug reproduce with SeaMonkey v1.1.9? lenochod: I think you meant to address this to the original reporter (Paul Landon)
Nothing substantive since 2006-07-14. Changing resolution to INCOMPLETE unless the reporter can confirm with the latest SeaMonkey/Firefox branch or even trunk.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
Sorry, I don't work at that location any more, so can't reproduce.
You need to log in before you can comment on or make changes to this bug.