Closed
Bug 335353
Opened 20 years ago
Closed 19 years ago
printing crashes [@ libfreetype.so.6 + 0xe2de] [@ nsFontMetricsPS::~nsFontMetricsPS]
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 294879
People
(Reporter: a_geek, Unassigned)
Details
(Keywords: crash)
Crash Data
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060417 MultiZilla/1.8.1.1d SeaMonkey/1.5a
Hello,
trying to print a web page, I get a dialogue where I can specify the printing options, like paper size. On that dialogue, I click "Print". The next thing I see immediately after pressing 'Print' is an alert box saying "An unknown error occurred while printing." If I click "OK" on that alert box, a new box raises saying "Printing" in the title, and in the contents it says: "Title: (page title here)" and in a line below it says "Progress: Preparing...", with various values for the page title. The "Cancel" button is grayed out, and at that point, nothing happens anymore. I can use the window manager's controls to close that dialogue box, but it doesn't ever print anything. This effect happens also if I select "Print to file", so it's not dependend on the print system, and with a Firefox on the same machine, and this build id:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2
I have no trouble printing the same pages at all.
Reproducible: Always
Steps to Reproduce:
1. Open a web page
2. click the printer icon (or press Ctrl-P)
3. follow the steps above
Actual Results:
The printing subprocess hangs and does not ever produce a result.
Expected Results:
The page(s) should get printed, with no hangs in the UI.
I just checked with an empty profile and no extensions loaded, same thing. On the command line I see this message:
(Gecko:4788): libgnomevfs-WARNING **: Cannot load module `/usr/lib/gnome-vfs-2.0/modules/libfile.so' (libstdc++.so.6: cannot handle TLS data)
I don't know if that's relevant, though.
Using Debian unstable on i386 here.
Comment 1•20 years ago
|
||
Please try a clean profile
Assignee: general → printing
Component: General → Printing
Product: Mozilla Application Suite → Core
QA Contact: general
Version: unspecified → Trunk
Comment 2•19 years ago
|
||
I have the same problem on XP Professional Service Pack 2.
I can print fine from Explorer or any other program, but cannot print from Firefox. I also cannot access printer properties.
Hello Andrew, I did this, and it resulted in the same sort of crash. Here are the results:
/usr/local/stow/firefox/run-mozilla.sh: line 131: 4939 Segmentation fault
This is the appropriate talkback ID: TB25059278Z
Comment 4•19 years ago
|
||
OK, thanks. it looks like bug 294879 was perhaps not actually fixed
Severity: major → critical
Keywords: crash
Summary: printing does not work → printing crashes [@ libfreetype.so.6 + 0xe2de] [@ nsFontMetricsPS::~nsFontMetricsPS]
Comment 5•19 years ago
|
||
(In reply to comment #3)
> Hello Andrew, I did this, and it resulted in the same sort of crash.
a_geek, your talkback report is from a copy of Firefox built in September. This should have been fixed in early October. There hasn't been a release of FF 1.5 with this fix yet, but it should be fixed in Firefox 2.0. Could you try that?
Comment 6•19 years ago
|
||
You could also grab a Firefox 1.5.0.8 candidate build to test with: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/1.5.0.8-candidates/rc2/.
Incident ID: 25059278
Stack Signature libfontconfig.so.1 + 0xbd17 (0xb7393d17) a9ba79d0
Product ID Firefox15
Build ID 2006090918
Trigger Time 2006-10-26 01:54:39.0
Platform LinuxIntel
Operating System Linux 2.6.18-1-xen-686
Module libfontconfig.so.1 + (0000bd17)
URL visited http://www.map24.de
User Comments printed a map
Since Last Crash 0 sec
Total Uptime 64 sec
Trigger Reason SIGSEGV: Segmentation Fault: (signal 11)
Source File, Line No. N/A
Stack Trace
libfontconfig.so.1 + 0xbd17 (0xb7393d17)
nsFontMetricsPS::~nsFontMetricsPS() [mozilla/gfx/src/ps/nsFontMetricsPS.cpp, line 111]
nsFontMetricsPS::Release() [mozilla/gfx/src/ps/nsFontMetricsPS.cpp, line 135]
nsFontCache::Flush() [mozilla/gfx/src/nsDeviceContext.cpp, line 715]
nsFontCache::~nsFontCache() [mozilla/gfx/src/nsDeviceContext.cpp, line 580]
nsFontCachePS::~nsFontCachePS()
DeviceContextImpl::~DeviceContextImpl() [mozilla/gfx/src/nsDeviceContext.cpp, line 88]
nsDeviceContextPS::~nsDeviceContextPS() [mozilla/gfx/src/ps/nsDeviceContextPS.cpp, line 102]
DeviceContextImpl::Release() [mozilla/gfx/src/nsDeviceContext.cpp, line 54]
nsCOMPtr_base::~nsCOMPtr_base() [mozilla/xpcom/build/nsCOMPtr.cpp, line 81]
nsPrintData::~nsPrintData() [mozilla/layout/printing/nsPrintData.cpp, line 159]
nsPrintEngine::Destroy() [mozilla/layout/printing/nsPrintEngine.cpp, line 283]
DocumentViewerImpl::OnDonePrinting() [mozilla/layout/base/nsDocumentViewer.cpp, line 4142]
HandlePLEvent() [mozilla/layout/printing/nsPrintEngine.cpp, line 4549]
PL_HandleEvent() [mozilla/xpcom/threads/plevent.c, line 689]
PL_ProcessPendingEvents() [mozilla/xpcom/threads/plevent.c, line 623]
nsEventQueueImpl::ProcessPendingEvents() [mozilla/xpcom/threads/nsEventQueue.cpp, line 421]
event_processor_callback() [mozilla/widget/src/gtk2/nsAppShell.cpp, line 67]
libglib-2.0.so.0 + 0x54c7f (0xb790dc7f)
libglib-2.0.so.0 + 0x2b731 (0xb78e4731)
libglib-2.0.so.0 + 0x2e7a6 (0xb78e77a6)
libglib-2.0.so.0 + 0x2eb67 (0xb78e7b67)
libgtk-x11-2.0.so.0 + 0x129281 (0xb7baf281)
nsAppShell::Run() [mozilla/widget/src/gtk2/nsAppShell.cpp, line 141]
nsAppStartup::Run() [mozilla/toolkit/components/startup/src/nsAppStartup.cpp, line 151]
XRE_main() [mozilla/toolkit/xre/nsAppRunner.cpp, line 2376]
main() [mozilla/browser/app/nsBrowserApp.cpp, line 62]
libc.so.6 + 0x14ea8 (0xb73daea8)
Hello,
wrt. comment #5, I have tried both FF 2.0 and the RC for 1.5.0.8, and both don't crash anymore. At least, I was able to print moderately complex pages (eg. routes by map24) or newspaper pages without a problem.
This bug should then probably be made a duplicate of bug 294879, right?
Comment 8•19 years ago
|
||
Thanks for your help testing. Yep, the fact that this doesn't occur in 1.5.0.8 would point to the fact that bug 294879 fixed this.
*** This bug has been marked as a duplicate of 294879 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Updated•15 years ago
|
Crash Signature: [@ libfreetype.so.6 + 0xe2de]
[@ nsFontMetricsPS::~nsFontMetricsPS]
You need to log in
before you can comment on or make changes to this bug.
Description
•