https://bugs.documentfoundation.org/show_bug.cgi?id=116679
--- Comment #15 from V Stuart Foote <vstuart.fo...@utsa.edu> ---
(In reply to Leo from comment #14)
> So it's quite obvious now that the problem is caused by the Ricoh printer
> driver. What do you recommend? I'm a bit reluctant to try a different driver
> because I've had to spent a lot of time to get it working (we're in a shared
> office, and the printer driver was provided by the office management, but
> otherwise not much support). Besides it works OK for other applications.
>
I would probably give up on the printer specific driver, and at least check a
current "Universal Print" driver. Ricoh has fairly active support page, and
PCL6 and PS driver packages for Windows 10, 8.1, 7 both 64-bit and 32-bit.
http://support.ricoh.com/bb/html/dr_ut_e/rc3/model/p_i/p_i.htm?lang=en
Larger projects (e.g. for Autodesk, Adobe) have been able to get custom driver
work done, but I think LibreOffice is going to be left hanging. Of course, it
also depends on how old the printer in question is.
> Long shot: I use Visual Studio for .NET development, but I think that I can
> also build and debug C/C++, so I could try to download the source code and
> try to reproduce the exception in the debugger...
Possibly, but a lot of work and you still may end up with the same non-helpful
pointers into the Ricoh drivers DLL. Without symbols from Ricoh don't think
you'll get anything helpful. If you look at the URL linked in comment 13 any of
the reports there will have a breakpad delivered stack trace annotated from
LibreOffice and Microsoft debug symbols. The missing piece is the Ricoh code.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
