Closed
Bug 313062
Opened 19 years ago
Closed 6 years ago
Printing on HP Laserjet 8150 stops printer - Error 79.01FE
Categories
(Core :: Printing: Output, defect, P2)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: ppsli, Unassigned)
References
()
Details
(Keywords: regression)
Attachments
(1 file)
9.97 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1 FF 1.5 beta2 MacOS 10.3.9 HP Laserjet 8150 Series Printing some Web pages (mainly with graphics) stops(crashes) the printer. The printer shows Error 79.01FE and has to be restarted. (Kill reponsible print job before that!) Examples Clean keyboard etc hardware maintenance http://www.sterpin.net/uk/dossiersuk.htm http://www.sterpin.net/uk/2silentuk.htm http://www.sterpin.net/uk/prokeyboarduk.htm http://www.sterpin.net/uk/usbkeyboarduk.htm http://java.about.com/od/beginningjava/a/beginjavatutor_p.htm (not this page but at least the lessons from 3 onward ) The pages print fine in Safari 1.3.1 and MSIE Some more: FontExplorer X Help http://spanish.about.com : About: In the Mood: The Subjunctive Part 2,3 - Spanish Language http://spanish.about.com/library/weekly/aa110899.htm (Installing) PhpGedView - Online genealogy at its best Silver ADSL:Home: Silverserver Silver ADSL:Office: Silverserver David Christensen - Putting Logic in its Place: Formal Constraints on Rational Belief - Reviwed by William J. Talbott.University of Washington - Philosophical Reviews -… 10/07/05 How much cooling and power is enough for my computer? Community Newsletter: Q&A - CNET Forums Reproducible: Always Steps to Reproduce: 1.Open Web page 2.Print 3. Actual Results: Printer comes to a halt with Error 79.01FE (The print monitor hangs - one has to hold or delete the print-job such that it does not stop the printer again after restarting it) Usually no data are lost but you have to find the page you printed again (if you remember what you did) Expected Results: Print page. Printer undisturbed. You never know when it prints correctly. I have not switched back to FF 1.0.7 (which I used only for short time) and it never happened in FF1.0.3 The error 79.01FE was reported as a HP defect in this series but was corrected by a previous firmware update. It is not present with the other browsers or on PCs (I am the only MacUser in the deparment of about 12 users)
Reporter | ||
Comment 1•19 years ago
|
||
Manual HP Laserjet 8150: PRINTER ERROR The printer detected an error. The numbers (xxxx) indicate the specific type of error. Turn the printer off, and then turn the printer on. If the message appears only with a specific software application or print job, simplify the job, or print from a different application. If the message persists, contact the software vendor for assistance. If the message is not related to a specific file or software application, turn the printer off, disconnect the power cable and reseat the formatter, EIO cards, or memory DIMMs. Reconnect the power cable and turn the printer on. If the message persists, contact HP Customer Care for assistance. (All not too helpful) Compare Firmware advice: http://ftp.hp.com/pub/printers/software/lj8150lbreadmefw.txt Hewlett-Packard LaserJet 8150 Series Printers Firmware Update/Download Release/Installation Notes ... Improvements provided with firmware revision 20020311 MB7.104. ... * ----> The printer will generate a 79.01FE Service Error on the control panel when printing Duotones EPS files. ... * Some PDF files may generate 79.XXXX ("X" may represent any hex number) service errors on the control panel of the printer. ( see also http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bpm01340 http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=615599 )
Version: unspecified → 1.5 Branch
Reporter | ||
Comment 2•19 years ago
|
||
Last comment should have started Manual HP Laserjet 8150: 79.xxxx PRINTER ERROR The printer detected an error. The numbers (xxxx) indicate the specific type of error.
reporter: could you verify that this happens using camino?
Assignee: nobody → printing
Component: General → Printing
Product: Firefox → Core
QA Contact: general
Version: 1.5 Branch → 1.8 Branch
Reporter | ||
Comment 4•19 years ago
|
||
I am not a user of Camino. However I found an older version on my machine 0.8b+ (on a non-system-disk) prints ok http://www.sterpin.net/uk/usbkeyboarduk.htm (I repeat: I never had problems on Firefox 1.0.3, only after installing FF 1.5beta2 I have not yet recovered printing page numbers and URL of origin as headers/footers. Firefox also crashes occasionally /twice a month or so?/ or freezes. I have not yet tried re-installing FirefoxBeta. Wating for beta3) Downloaded Camino 0.8.4 : prints also everything http://www.silverserver.at/produkte/internet/silveradsl/bestellungsilveradsl/nocache/ http://www.sterpin.net/uk/prokeyboarduk.htm but it crashes repeatedly (including a version on the startup disk): Oct 20 06:51:49 Sint... crashdump: Started writing crash report to: /Users/.../Library/Logs/CrashReporter/Camino.crash.log Oct 20 06:52:10 Sint... crashdump: Finished writing crash report to: /Users/.../Library/Logs/CrashReporter/Camino.crash.log Host Name: Sint... .local Date/Time: 2005-10-20 06:51:33 +0200 OS Version: 10.3.9 (Build 7W98) Report Version: 2 Command: Camino Path: /Applications/Camino.app/Contents/MacOS/Camino Version: 0.8.4 (0.8.4) PID: 899 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000020 Thread 0 Crashed: 0 org.mozilla.navigator 0x004ac0b4 nsBlockFrame::SplitPlaceholder(nsIPresContext&, nsIFrame&) + 0x44 1 org.mozilla.navigator 0x004abe94 nsBlockFrame::ReflowInlineFrame(nsBlockReflowState&, nsLineLayout&, nsLineList_iterator, nsIFrame*, unsigned char*) + 0x234 2 org.mozilla.navigator 0x004aba74 nsBlockFrame::DoReflowInlineFrames(nsBlockReflowState&, nsLineLayout&, nsLineList_iterator, int*, unsigned char*, int, int) + 0x1a4 3 org.mozilla.navigator 0x004ab848 nsBlockFrame::DoReflowInlineFramesAuto(nsBlockReflowState&, nsLineList_iterator, int*, unsigned char*, int, int) + 0x88 4 org.mozilla.navigator 0x004ab6cc nsBlockFrame::ReflowInlineFrames(nsBlockReflowState&, nsLineList_iterator, int*, int, int) + 0x8c 5 org.mozilla.navigator 0x004aa48c nsBlockFrame::ReflowLine(nsBlockReflowState&, nsLineList_iterator, int*, int) + 0x3f0 6 org.mozilla.navigator 0x004a9be8 nsBlockFrame::ReflowDirtyLines(nsBlockReflowState&) + 0x1e8 7 org.mozilla.navigator 0x004a866c nsBlockFrame::Reflow(nsIPresContext*, nsHTMLReflowMetrics&, nsHTMLReflowState const&, unsigned int&) + 0x3f0 8 org.mozilla.navigator 0x0053f0bc nsBlockReflowContext::ReflowBlock(nsRect const&, int, nsCollapsingMargin&, int, nsMargin&, nsHTMLReflowState&, unsigned int&) + 0x510 9 org.mozilla.navigator 0x004ab248 nsBlockFrame::ReflowBlockFrame(nsBlockReflowState&, nsLineList_iterator, int*) + 0x2d0 10 org.mozilla.navigator 0x004aa138 nsBlockFrame::ReflowLine(nsBlockReflowState&, nsLineList_iterator, int*, int) + 0x9c 11 org.mozilla.navigator 0x004a9be8 nsBlockFrame::ReflowDirtyLines(nsBlockReflowState&) + 0x1e8 12 org.mozilla.navigator 0x004a8e08 nsBlockFrame::ComputeFinalSize(nsHTMLReflowState const&, nsBlockReflowState&, nsHTMLReflowMetrics&) + 0x21c 13 org.mozilla.navigator 0x004a88fc nsBlockFrame::Reflow(nsIPresContext*, nsHTMLReflowMetrics&, nsHTMLReflowState const&, unsigned int&) + 0x680 14 org.mozilla.navigator 0x0053f0bc nsBlockReflowContext::ReflowBlock(nsRect const&, int, nsCollapsingMargin&, int, nsMargin&, nsHTMLReflowState&, unsigned int&) + 0x510 15 org.mozilla.navigator 0x004ad9b8 nsBlockFrame::ReflowFloat(nsBlockReflowState&, nsPlaceholderFrame*, nsFloatCache*, unsigned int&) + 0x298 16 org.mozilla.navigator 0x0053dfa4 nsBlockReflowState::FlowAndPlaceFloat(nsFloatCache*, int*, unsigned int&) + 0x110 17 org.mozilla.navigator 0x0053dcac nsBlockReflowState::AddFloat(nsLineLayout&, nsPlaceholderFrame*, int, unsigned int&) + 0x94 18 org.mozilla.navigator 0x00536304 nsLineLayout::ReflowFrame(nsIFrame*, unsigned int&, nsHTMLReflowMetrics*, int&) + 0x570 19 org.mozilla.navigator 0x004abcd8 nsBlockFrame::ReflowInlineFrame(nsBlockReflowState&, nsLineLayout&, nsLineList_iterator, nsIFrame*, unsigned char*) + 0x78 20 org.mozilla.navigator 0x004aba74 nsBlockFrame::DoReflowInlineFrames(nsBlockReflowState&, nsLineLayout&, nsLineList_iterator, int*, unsigned char*, int, int) + 0x1a4 21 org.mozilla.navigator 0x004ab848 nsBlockFrame::DoReflowInlineFramesAuto(nsBlockReflowState&, nsLineList_iterator, int*, unsigned char*, int, int) + 0x88 22 org.mozilla.navigator 0x004ab6cc nsBlockFrame::ReflowInlineFrames(nsBlockReflowState&, nsLineList_iterator, int*, int, int) + 0x8c 23 ... ... (deleted by me) 62 org.mozilla.navigator 0x003e038c nsContainerFrame::ReflowChild(nsIFrame*, nsIPresContext*, nsHTMLReflowMetrics&, nsHTMLReflowState const&, int, int, unsigned int, unsigned int&) + 0x98 63 org.mozilla.navigator 0x004eca60 ViewportFrame::Reflow(nsIPresContext*, nsHTMLReflowMetrics&, nsHTMLReflowState const&, unsigned int&) + 0x118 64 org.mozilla.navigator 0x00276524 PresShell::InitialReflow(int, int) + 0x1fc 65 org.mozilla.navigator 0x0040bc30 nsPrintEngine::ReflowPrintObject(nsPrintObject*, int) + 0x980 66 org.mozilla.navigator 0x0040b1e4 nsPrintEngine::ReflowDocList(nsPrintObject*, int, int) + 0xfc 67 org.mozilla.navigator 0x0040ab98 nsPrintEngine::SetupToPrintContent(nsIDeviceContext*, nsIDOMWindow*) + 0xa0 68 org.mozilla.navigator 0x00409e84 nsPrintEngine::DocumentReadyForPrinting() + 0x40 69 org.mozilla.navigator 0x00407440 nsPrintEngine::Print(nsIPrintSettings*, nsIWebProgressListener*) + 0xf74 70 org.mozilla.navigator 0x002c0a3c DocumentViewerImpl::Print(nsIPrintSettings*, nsIWebProgressListener*) + 0x2fc 71 org.mozilla.navigator 0x00020214 -[CHBrowserView printDocument] + 0xcc 72 com.apple.AppKit 0x92f276fc -[NSApplication sendAction:to:from:] + 0x6c 73 com.apple.AppKit 0x92f5cf48 -[NSMenu performActionForItemAtIndex:] + 0x188 74 com.apple.AppKit 0x92fa17f4 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 0x68 75 com.apple.AppKit 0x92fa8124 -[NSMenu performKeyEquivalent:] + 0x104 76 com.apple.AppKit 0x92f871dc -[NSApplication _handleKeyEquivalent:] + 0x124 77 com.apple.AppKit 0x92ea4840 -[NSApplication sendEvent:] + 0xa5c 78 com.apple.AppKit 0x92ead0d0 -[NSApplication run] + 0x240 79 com.apple.AppKit 0x92f697bc NSApplicationMain + 0x1d0 80 org.mozilla.navigator 0x0000a308 _start + 0x17c 81 org.mozilla.navigator 0x0000a188 start + 0x30 Thread 1: 0 libSystem.B.dylib 0x9490546c select + 0xc 1 libnspr4.dylib 0x00e247d8 poll + 0x188 2 libnspr4.dylib 0x00e21024 _pr_poll_with_poll + 0x32c 3 org.mozilla.navigator 0x000ad854 nsSocketTransportService::Run() + 0x198 4 libxpcom.dylib 0x05043ae0 nsThread::Main(void*) + 0x38 5 libnspr4.dylib 0x00e2246c _pt_root + 0xac 6 libSystem.B.dylib 0x9491e990 _pthread_body + 0x28 and more... (available by mail)
hrm, that crash was probably bug 284434. unfortunately camino 0.8 is based on 1.7 which isn't what i was hoping to have you test.
Comment 6•19 years ago
|
||
Peter: If you can download and test with the latest nightly of Camino[1], that will help us track down where this bug is. [1] http://www.caminobrowser.org/download/releases/nightly/
Reporter | ||
Comment 7•19 years ago
|
||
Unfortunately I have the same problem F79.01FE with Camino 1.0A (nightly build 2005101904 (v1.0a1+) ) using: 10/07/05 How much cooling and power is enough for my computer? Community Newsletter: Q&A - CNET Forums http://reviews.cnet.com/5208-10149-0.html?forumID=7&threadID=129274&messageID=1460170&tag=nl.e497 David Christensen - Putting Logic in its Place: Formal Constraints on Rational Belief - Reviwed by William J. Talbott.University of Washington - Philosophical Reviews -… http://ndpr.nd.edu/review.cfm?id=4181
Reporter | ||
Comment 8•19 years ago
|
||
Still present in 1.5RC1 (1.0.7 still ok)
Reporter | ||
Comment 9•19 years ago
|
||
Error 79.01FE (stops HP Laserjet 8150) still present in FF 1.5RC2
Comment 10•19 years ago
|
||
This problem also occurs on HP Laserjet 5100tn printers. Printing will produce error using OS 10.3.9 and Firefox 1.5.x or Camino build 2005122909; and, OS 10.4.4 and Safari 2.2 or Firefox 1.5.x Printing will function properly using OS 10.3.9 from Firefox 1.0.7, Mozilla 1.7.12, and Safari 1.3.1. I've found cnn.com to be an easy test page to use.
Comment 11•18 years ago
|
||
If it helps, this problem appeared somewhere between Mac versions of Moz 1.7.12 and SeaMonkey 1.0. I'll see if I can test the intermediate builds.
Comment 12•18 years ago
|
||
I didn't test every build but did a binary search and here's where it appears to show up. These are the folder names from the nightly builds. These are all done on Mac OS X 10.4.6. 2005-08-01-11 ok 2005-08-15-12 ok 2005-08-16-11 ok 2005-08-17-13 problem 2005-08-20-12 problem 2005-08-25-11 problem 2005-09-01-11 problem
Comment 13•18 years ago
|
||
David, I assume this is still a problem?
Comment 14•18 years ago
|
||
(In reply to comment #13) > David, I assume this is still a problem? > Yes. I just tried released v1.0.2 and from: ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk the 6/6/06 build. Both lock up the printer.
Comment 15•18 years ago
|
||
Hmm. So looking at the checkin range: http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-08-16+11&maxdate=2005-08-17+13&cvsroot=%2Fcvsroot the only thing that looks like it _might_ be relevant is the checkin for bug 295737. Could that cause this bug? David, do you build by any chance?
Comment 16•18 years ago
|
||
(In reply to comment #15) > Hmm. So looking at the checkin range: > > http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-08-16+11&maxdate=2005-08-17+13&cvsroot=%2Fcvsroot > > the only thing that looks like it _might_ be relevant is the checkin for bug > 295737. > > Could that cause this bug? David, do you build by any chance? > Sorry. No.
Comment 17•18 years ago
|
||
(In reply to comment #16) > (In reply to comment #15) > > Hmm. So looking at the checkin range: > > > > http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-08-16+11&maxdate=2005-08-17+13&cvsroot=%2Fcvsroot > > > > the only thing that looks like it _might_ be relevant is the checkin for bug > > 295737. > > > > Could that cause this bug? David, do you build by any chance? > > > > Sorry. No. > While I might be able to test something built by you or someone else Thursday (east coast US time), I'll be out of town after that till Sunday or Monday. Let me know if there's something to test and I'll see what I can do.
Comment 18•18 years ago
|
||
Could a kind Mac soul post a build with bug 295737 backed out for David to test?
Updated•18 years ago
|
Flags: blocking1.9a2?
Flags: blocking1.8.1?
Comment 19•18 years ago
|
||
David, I've put a test build equivalent to Firefox 1.5.0.4 without the patch from bug 295737 at http://jackassofalltrades.com/tmp/firefox-1504-no295737.dmg .
Comment 20•18 years ago
|
||
(In reply to comment #19) > Created an attachment (id=224718) [edit] > Patch to back out bug 295737 > > David, I've put a test build equivalent to Firefox 1.5.0.4 without the patch > from bug 295737 at http://jackassofalltrades.com/tmp/firefox-1504-no295737.dmg > . > Great. I should be able to get to it tomorrow afternoon, EDT/US. If not I have someone lined up to try it Friday.
Comment 21•18 years ago
|
||
(In reply to comment #20) > (In reply to comment #19) > > Created an attachment (id=224718) [edit] > > Patch to back out bug 295737 > > > > David, I've put a test build equivalent to Firefox 1.5.0.4 without the patch > > from bug 295737 at http://jackassofalltrades.com/tmp/firefox-1504-no295737.dmg > Just tested 4 cases. The test build does NOT have the problem. FF 1.5.03, FF 1.5.04, SM 1.0.2 all HAVE the problem. OS 10.4.6 with all the the very recent QT update. Laser Jet 8150 with Ethernet connection. Latest firmware into the JetDirect print server. New HP printing downloaded as of a few weeks ago. Thanks for the effort.
Updated•18 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 22•18 years ago
|
||
OK, so sounds like bug 295737 regressed this. :(
Comment 23•18 years ago
|
||
When a fix is made, it should probably get on the 1.8.0 branch as well. Requesting blocking for 1.8.0.6 (since there's no patch yet).
Flags: blocking1.8.0.6?
Updated•18 years ago
|
Keywords: regression
Updated•18 years ago
|
Flags: blocking1.8.1? → blocking1.8.1+
Comment 24•18 years ago
|
||
Mark/Josh can you either take a look or bounce to the appropriate owner? Seems like we'd like to either fix or backout the original bug...
Assignee: printing → joshmoz
Comment 25•18 years ago
|
||
This really feels like an HP problem, but there's not much I can do without a printer that shows the bug. Do we know anyone at HP? It would be a step in the right direction if someone there could at least tell us what about our output is causing the hang. Their public information isn't exactly illuminating on this point.
Comment 26•18 years ago
|
||
The patch that supposedly caused this problem helps in a lot of cases, while this problem is rare it seems. I don't think backing out 295737 is a good idea right now. We need more information since this is hard to fix without being able to reproduce. Like Mark said, I wouldn't be surprised if this was an HP problem.
Comment 27•18 years ago
|
||
I agree; seems like a printer driver bug.
Comment 28•18 years ago
|
||
...although we could maybe disable the troublesome image tiling code for printing.
Comment 29•18 years ago
|
||
(In reply to comment #28) > ...although we could maybe disable the troublesome image tiling code for > printing. > Please do! I'm the one who did the version testing a few weeks back. And yes I truly beleive that this is an Apple/HP bug as there are reports of it happening to a few Quark and InDesign users on later versions of OS 10.4.x. But the architects and others I work with only see it as a SeaMonkey bug. And are clamoring for us to switch as that's the only time they see it. In the mind of users slow and working always is infinitely better than faster and working mostly. And they don't care if it's Apple's or HP's fault. If the issue goes away if we switch browsers, that what they want to do.
Comment 30•18 years ago
|
||
I don't think it is a good idea to back out the tiling speedup patch because that fixes a lot of sites for a lot of users and this bug is relatively rare. We're not going to fix this without backing out the patch unless we have more information, so I recommend taking this off the blocker list.
Comment 31•18 years ago
|
||
I'm seeing lots of other problems with the 8150 and MacOSX 10.4: http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=964573 Given this and the perf improvements in this patch misusing for 1.8.1.
Flags: blocking1.8.1+ → blocking1.8.1-
Comment 32•18 years ago
|
||
If it's not baked in 1.8.1 it's not going in 1.8.0.x
Flags: blocking1.8.0.7? → blocking1.8.0.7-
Flags: blocking1.9a2? → blocking1.9-
Whiteboard: [wanted-1.9][reanalyze after cocoa and cairo landings]
Comment 33•18 years ago
|
||
(In reply to comment #30) > I don't think it is a good idea to back out the tiling speedup patch because > that fixes a lot of sites for a lot of users and this bug is relatively rare. Josh, if I understand Simon's comment correctly, he was simply saying we could turn off the tiling speedup patch for printing only, not for everything. Would that be possible?
Comment 34•18 years ago
|
||
I just ran into this in my shop on Macs running OS X 10.3.9 and Firefox 1.5.0.7. Printing the page http://www.informationweek.com/news/showArticle.jhtml?articleID=193100650 from any Mac with that OS crashes any HP LJ 8150DN every time. No Mac running OS X 10.4.7 or later has the problem with any released Mozilla browser. (Fixing this specific HP crash is mentioned in the release notes of the OS X 10.4.7 update.) Also tested under OS X 10.3.9: Firefox 2.0rc3 (20061010) -- crashes the printer with 79.01FE Firefox latest nightly "Minefield 3.0a1" (20061014) crashes while printing, printer is okay Camino 1.03 -- crashes the printer, as above Camino 1.1a1+ (2006102401) -- crashes the printer as above.
Updated•17 years ago
|
Flags: wanted1.9+
Whiteboard: [wanted-1.9][reanalyze after cocoa and cairo landings] → [reanalyze after cocoa and cairo landings]
Comment 35•16 years ago
|
||
I had banned Firefox from my shop because of this bug. I just revisited that. Printing this same URL http://www.informationweek.com/news/showArticle.jhtml?articleID=193100650 from a Mac running OS X 10.4.11 fully updated, and Firefox 3.0.4 freshly updated, crashed an HP 8150DN with a 79.00FE error. The ban stands.
Comment 36•16 years ago
|
||
For what it's worth, according to http://answers.yahoo.com/question/index?qid=1006012802827 this might be a firmware issue. I assume the relevant printers do have up-to-date firmware?
Comment 37•16 years ago
|
||
Didn't have the latest firmware, updated it just now with the latest file direct from HP, no change.
Comment 38•16 years ago
|
||
Josh, any answer to comment 33? It's only been two years. ;) Also, if comment 35 is right, this is likely a problem all around, not just on the 1.8 branch.
QA Contact: printing
Whiteboard: [reanalyze after cocoa and cairo landings]
Version: 1.8 Branch → Trunk
Comment 39•16 years ago
|
||
Philip, I assume you've also reported this to HP, right? Josh, I think Samuel is right. If we can work around this on our end, we really should.
Flags: blocking1.9.1?
Comment 40•16 years ago
|
||
I agree we should work around this, but I just don't see justification for blocking. This is not a regression from the last release, it is not a high visibility problem, and nothing about it suggests to me we couldn't software update it if a developer did the work. I don't see us holding up a release for this.
Flags: blocking1.9.1? → blocking1.9.1-
Comment 41•16 years ago
|
||
Should it be wanted+, then?
Comment 42•12 years ago
|
||
Is this still a problem ?
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•