Changing this environment variable makes no difference on Debian i386/testing.
I do have a copy of iceweasel (Debian rebadged firefox) running, but acroread
fails on the console:
: nr@homedog 5103 ; r /us
terminate called after throwing an instance of 'RSException'
: nr@homedog 5104 ; set | grep GTK
We at Adobe are trying to resolve this issue at earliest. We would like to share private build(s) with probable fix with users facing this issue.If you are willing to help us and be part of private pre-release programme kindly send in your email-ids to vaibhavp at adobe dot com.
Thanks again for reporting the issue and for helping us in resolving this.
Thanks for participating in pre-release program and reporting the issue. We have now fixed the issue at our end and would release the fix in the next dot release.
Thus, pre-release program is now closed.
Thanks again for helping us on this.
Do you have a release date for a version of acroread which does not crash on printing? Or perhaps a workaround for the problem? Right now, the only workaround is to switch to another PDF reader.
The crashes are very similar to the ones described in this thread. Most, maybe all of the crashes involve a Xerox colour printer PPD. Acroread crashes when changing options or when clicking "Ok" to print. The machines (multiple users are affected) run Ubuntu 8.04 with Acroread 9.1.0.
I have attached one of the print PPD files.
The issue here seems to be because of the large number of options in the ppd file, typically a Xerox color ppd(we have it reproduced and we are working on it).
It seems the ppd is not attached with your post. Please mail the ppd file to rishi at adobe dot com.
I will confirm the issue once I get the ppd file.
As a workaround you may use a ppd file from the CUPS package for your printer.
Thanks & Regards,
Whilst I have no issues with 8.1.5, I see this identical message with all versions of 9.x.
Any progress on this one, as my work document review/control process has switched to 9.x and eventually I'll need to do the same at home....
Both the issues covered in this post (RSException, and PPD with large number of parameters) are being worked on and the fix will be available in the next patch/dot release of the Reader. Please stay tuned to the Adobe Reader for Unix Blog (http://blogs.adobe.com/acroread) for the release announcement.
I'm getting the exact same symptom, but I didn't try to print from Adobe. I did try to add some annotations to a document, that's the oddest thing I've done.
Adobe opens, stays up for about 3 secs (I have a fast machine), then crashes. Whether it open acroread by itself or with a document doesn't seem to make a difference. "export GTK_IM_MODULE=xim" didn't make a difference.
terminate called after throwing an instance of 'RSException'
Ubuntu 9.04 32bits in a Intel Quad Core, tried both the latest 9.1.1 deb from Adobe and the default 9.1 that ships in the partner repository in Ubuntu.
As I mentioned in my comment above, this fix is being worked on and will be available in the upcoming dot release (9.1.2) of Adobe Reader. Stay tuned the blog (http://blogs.adobe.com/acroread) for the release announcement.
This bug has been fixed in Adobe Reader 9.1.2 on linux , this can be downloaded from ftp://ftp.adobe.com/pub/adobe/reader/unix/9.x/9.1.2/ .
For details please visit http://blogs.adobe.com/acroread/2009/06/912_and_816_security_updates.h tml
Were you facing the same issue with the earlier versions(8.1.x or 9.1.1) of acroread too.
As you mentioned the crash is happening when you try to print duplex. Is this the only scenario that is causing the crash?
Are you facing the crash with any other printer?
Please attach the ppd file that you are using to print to the HP 2605 printer.
I did have this issue after upgrading to 9.1.1 but with our new Xerox
printers NOT the HP 2605's - so I downloaded from the ftp site the 9.1.2
which fixed the issue with the Xerox printers but broke the working HP
If I use the 8.1.2 I have no issues - attached is the ppd file I am using.
I am afraid I do not find any ppd attached with the post.
If you are facing problem attaching the ppd file, please mail it to rishi at adobe dot com.
Also, as I asked you before is the issue only when you set the duplex option on. Thus with all other settings you do not face a crash. Please confirm.
You said using lpr solves the problem. Is it that you are printing it through the custom route( choosing "Custom" in the Printer name dropdown) or are you using the "print to file" route to create a postscript file. Please specify.
The default printer command used to send the job to the printer is "lpr".
Currently we are having the same issue with the latest Acroread 9.2-1 on Ubuntu 8.04LTS.
Acroread crashes on printer settings dialog.
Open a document
go to file/print
open printer preferencies, change something, press ok
it makes acroread crash without any error messages
I attached the PPD file used to print.
Printer is Xerox Workcentre 7232.
Could anybody please take a look at it?
We are having the exact same problem on the latest Reader 9.3 on Opensuse 11.1 and Cups remote printers:
Open PDF File
Chose File-> Print
Chose Properties on the Default printer
Click "OK" in the Properties Dialog
--> CRASH without notice!
Attached please find the crashlog.
This problem persisted in 9.0, 9.1, 9.2 and 9.3, no problem in the 8.x releases!
I can provide the PPD files if neccessary.
Thanks for reporting the issue. We are trying to reproduce the problem but haven't been able to do it yet with the steps you mentioned in your post (by launching acroread after firefox 3.1 Beta 3).
Please let us know in case you find anything else.
Adobe Reader 9.3/9.3.1 crash after clicking the "OK" button of the printer properties dialog (with or without changing any option).
With ACRO_CRASHLOG=1 it only shows "segfault".
Using also a remote printer (HP C5180). Tried different cups version (1.3.x and 1.4.x) and driver version (hplip), same problem.
It's still possible to print without accessing the printer properties dialog.
Btw I have no problem when using my laptop (software setup is similar) : could it be a hardware compatibility problem ?
I'm using Gentoo Linux.