Bug in Adobe Reader

Oracle has informed us that their Outside In product's PDF output doesn't render (converted MS Word documents containing Cyrillic converted into PDF) in Reader because Reader has a font-choice-related bug: "This is a tricky issue in which one of the Adobe-defined character sets claims support for the Cyrillic characters, but the characters do not render properly in Acrobat Reader when we use that character set."
Can someone confirm this is a Reader bug, and will it be fixed?

Appears to be a printer driver issue.
Printer is a Lexmark Optra E312.
The problem occurred when printing in non-Postscript mode.
If I print in Postscript mode, all's well.
I'll check whether Lexmark has any updated drivers.

Similar Messages

Bug in Adobe Reader when displaying lines?

Hi there!
I'm creating a complex document with Apache FOP, using tables with visible and hidden borders. Although, all lines have the same attributes, Adobe Reader renders them in different thikness. In the FOP forum, there has been a lot of discussions about this issue. Conclusion is, that it is not supposed to be a FOP bug. Some other readers render the created documents well. You might want to read about it here: http://apache-fop.1065347.n5.nabble.com/Cell-border-rendering-error-thicker-with-number-co lumn-spanned-tp17999p37229.html. Displaying on screen, it is possible to avoid this by not using "Enhance thin lines". However, printed documents allways show these lines in different thikness. To avoid this being a FOP bug, there is a simple example document, producing the bug with Adobe Reader. It can be found here: http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201211.mbox/raw/%3c5095C97A .[email protected]%3e/2. The document is hand crafted. To see the issue, turn on "Enhance thin lines" and try different zoom values. If this document contains incorrect contents, I'll be happy, if you let me know.
Regards.

You will not get a response from the bug report but they DO read the reports and use them to make future updates.
I notice a lot of the other issues reported here have not been responded to either.
Is that the normal process?
I haven't noticed that at all. In fact, most posts here get results as long as the poster gives enough details. Keep in mind that the answers are coming from fellow users and it is not an official avenue to contact Adobe personnel.

Unresolved bug in adobe reader x with non-default windows zoom level

This seems to have already been brought up here about a year ago: http://forums.adobe.com/thread/776060.
I am using Windows 7 Professional 64-bit with Firefox 12.0 and Adobe Reader 10.1.3. Here is a description of the problem:
Whenever I open any PDF file in a browser (firefox or IE) using the adobe reader I am unable to select text, save the file or interact with the content in any meaningful way because the plugin does not recognise my cursor position. If I click on some text in a PDF document, the reader will immediately highlight a region of text between where I clicked and where it thinks I started clicking from (above 20% of the screen above and to the left of where I actually clicked on the page). If I roll my mouse over the region where the dashboard normally appears, the dash does appear as intended and the cursor changes in response to hover over buttons, as if everything were working, but I am unable to click on anything (clicking does nothing). If I click and hold the dashboard when it appears, it immediately jumps to another region of the page, as if it thinks I moved the mouse (20% up and to the left again). I have recently reformatted and am now using a fresh install, and the issue remains. My desktop zoom level in windows is 150%. The problem appears only inside the browser; viewing PDFs directly in Acrobat Reader X works without issue.
I can resolve the problem either of two ways:
a) Reverting back to the default windows zoom level (125%).
b) right-clicking on the Adobe Reader X icon, navigating to the compatibility tab and clicking "Disable Display Scaling on high DPI settings"
The workaround is easy but it's disappointing that adobe hasn't fixed this. Please consider that it would mostly affect individuals who are vision impaired and might not have the know-how to resolve the problem or check for solutions online, let alone post comments such as this. As far as I can tell this problem severely impaires the functionality of adobe in any browser on any non-standard zoom windows installation.

Please be sure to post your issue in the following Feature Request/Bug Report Form.

Bug in Adobe Reader when opening PDF's in a sharepoint library

I can consistently reproduce this problem.
A document library containing pdf's where the number of items exceeds the list view threshold.
The documents are locked and checked out to another user.
When a non-admin user clicks the pdf link, the following CAML query is sent to the server (presumably to see which user has the document checked out) - *However this CAML query fails because the list view threshold is exceeded*
Here is an example of the caml query adobe generates
<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><GetListItems xmlns="http://schemas.microsoft.com/sharepoint/soap/"><listName>{27277C40-B0FD-4E3C-9709-93434DDCCB95}</listName>
<query><Query><Where><Eq><FieldRef Name="FileLeafRef"/>
<Value Type="File">32977 - NZ2942.pdf</Value>
</Eq>
</Where>
</Query>
</query>
<queryOptions><QueryOptions><IncludeMandatoryColumns>FALSE</IncludeMan datoryColumns>
<Folder>Account Documents</Folder>
</QueryOptions>
</queryOptions>
<viewFields><ViewFields><FieldRef Name="IsCheckedoutToLocal"/>
<FieldRef Name="CheckoutUser"/>
</ViewFields>
</viewFields>
<viewName></viewName>
</GetListItems>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
HTTP 500 - List view threshold exceeeded.
This is a bug in adobe and needs to be fixed.
The final error is "The URL you have provided cannot be reached".
Expected behavior - the document opens in read only mode because it is locked (and also because we are using reader and can't edit it)
I see no reason for Reader to send a query to determine who has the document checked out.

You will not get a response from the bug report but they DO read the reports and use them to make future updates.
I notice a lot of the other issues reported here have not been responded to either.
Is that the normal process?
I haven't noticed that at all. In fact, most posts here get results as long as the poster gives enough details. Keep in mind that the answers are coming from fellow users and it is not an official avenue to contact Adobe personnel.

May 19 bug fix adobe reader app

since the bug fix, May 19 2014, I am unable to fill out pdf forms on my ipad, please help

Have you added handwritten signatures to your PDF forms in an older version of Adobe Reader for iOS before?
If so, your PDF forms were partially (and incorrectly) flattened due to a bug in Reader. The bug has been fixed in the latest version 11.3.0 (which was released on May 18, 2014).
Do you have the original PDF forms (in the state before adding the handwritten signatures)? Please fill out forms and re-apply your signatures in Reader 11.3.0. Then it should all work.
Sorry for the inconvenience.

E72 V31.023 firmware-BUG in Adobe Reader LE 2.50

E72 NEW Firmware V 31.023 BUG : Cant open password protected pdf files in the updated adobe reader 2.5 LE....previous version LE 1.5 (FW Version 21.024) used to do that perfectly.Got confirmation from other users that its not working.What is the point of a firmware update ? Bringing in more bugs????
Can Nokia Revert on this...?

Its embedded, yes, but Nokia did not design the software. On further notice, since it is firmware embedded, user files, or systems files which change with usage of the phone has an effect on firmware updates.
Note that many bugs which occur after firmware updates are fixed by a hard reset+installation, meaning these bugs are user inflicted upon themselves. Files they have created, or system files created as they use the phone are apparently incompatible with the new update, rendering the installation of the update faulty.
Also firmware have been tested in Nokia labs before being send, what Nokia has no control over is the status of your phone, your PC and whatever occurs in the internet connection and lines as the data travels from the servers to your phone.
You can try to have the phone reformatted and firmware reinstalled in a Nokia Care Center as they usually get the updates in CD format, meaning these files they have are completely fine.
If you find my post helpful please click the green star on the left under the avatar. Thanks.

Can anyone help solve this frustrating drop down bug in Adobe Reader 8?

Has anyone encountered drop downs in their PDF form that don't work in Adobe Reader 8?
A simple example is my form (stripped back) here:
http://www.wikski.com/misc/test.pdf
I've built a form with 22 sections in it, some 1800 lines of code, and now every single drop down has decided to not work in Adobe Reader 8.
The behaviour is when you select a drop down, it immediately deselects itself and you can't use the element at all.
I previously had this occur, and by simply deleting the element in LiveCycle Designers ES2 (which is what I've used to create the entire form) and recreating it exactly the same; seemed to fix it. However, I am so far past the point of being able to recreate every drop down this time, I need to actually know what's causing the bug.
Any help would be greatly appreciated!
Cheers,

xfa.layout.relayout(); is required to re-render the entire form in order to have the field change color on Enter event. Without this, the field won't change color in Adobe Reader 8, this goes for all fields not just drop downs. Instead it'll just flicker the color change, xfa.layout.relayout(); makes the color change stick.
Thanks for your help, I've decided to take the set_focus() event off drop downs and keep it in place just for other field types such as the text input field.

Auto-Complete bugs in Adobe Reader X / Acrobat X

When I open a PDF that has fillable forms, and auto-complete is enabled, it does a terrible job of managing it's suggestions and how it handles my desire to 'type through' the suggestions that it's offering.
To test this, you'll need a PDF with multiple fillable form fields. it seems to have the hardest time with numerical data. Spend a couple minutes entering in a lot of numerical data into the fields. Delete some of it, put in different numbers, and eventually you'll see what I'm talking about. I suggest that, because in some cases I'm able to reproduce it immediately, and in others it takes a few tries or a few different PDFs. If you have typed in an address, say '1234 main', then in a later field, type in a zip code of '12345', then in yet another field start typing 12345 then hit the spacebar, it autofills "12345main". Note how 12345main does not match anything I previously entered, but the auto-complete database thinks that it does. The 'ain' part of "12345main" stays highlighted, like that's what it's now suggesting. If you backspace back so that it shows "12345" again, and then hit space, it will auto-fill to '12345main' again. I can't simply 'Type through' thie suggestion, because it leaves the 'm' there.
What's odd, is that for the sake of this demonstration, you type in multiple items that begin with 1234, then enter '1234 ' (note the space) on another field, it actually won't suggest to you the items you previously entered that begin with 1234 . Example: in 3 fields, type in 1234 Main St, 1234 Downtown Rd., and then in the 3rd field start type 1234 followed by space. You'd think you'd be offered suggestions by Auto-complete that contain both 1234 Main St. and 1234 Downtown Rd, but you don't. If you type something like '12345' now, you'll be back to the problem i outlined above where it automatically selects an item from the list and grabs an unwanted letter from the first word after the space. Interestingly enough, if you keep typing '1234 Ma' for example, you still don't see the Auto-complete suggestions unless you start hitting the 'Backspace' key, at which point the proper suggestions are displayed.
For our users that send out a lot of correspondence to clients, this is a huge inconvenience. The only workaround is to completely disable the Auto-complete option under 'Forms'. If they do not, then they can end up with incorrect information going out to cilents, and some of them have sent printed forms to cilents containing characters that didn't make sense or numerical data that was not correct because it had picked up unwanted characters from auto-complete.
Additional information:
I'm able to duplicate this problem on multiple workstations.
OS: Windows 7 32-bit Enterprise SP1, Windows XP 32-bit Professional SP3
I'm able to duplicate the problem with Adobe Reader X and Adobe Acrobat X
The problem also occurs whether I select either 'Advanced' or 'Basic' for the Auto-Complete setting

Hello All,
The issue has been fixed in latest version of Acrobat i.e. 10.1.9 or 11.0.6.
Please see the release notes for Acrobat 10.1.9 below:
http://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotes/10/10.1.9.html
To update the product please go to Help -> Check for updates.
Regards,
Anoop
[link fixed by moderator]

Strange bug in Adobe Reader X

While I was still using Adobe Reader X, the following problem has occured, more than once: I was reading an ebook, and as I was reading, I was selecting text and scrolling down (the text was deselected automatically, it seems), reading again then selecting text and scrolling down (so the text I was reading would have always been in the center of the screen). And after a while, Adobe Reader stops responding, it's menu and toolbars remain with no icon and no text, only that shade of gray the bars are drawn, is drawn on the menu bar, toolbar, and the view draws the text (of the document) awfully. Because this problem did not get solved in Adobe Reader 10.1 and I need to read ebooks, I have returned to Adobe Reader 9.4.

I have a similar issue, the update to 10.1.0 didn't help. Maybe it's to do with being a 64bit system or it's my Intel graphics driver. Going back to reader 9.4...
Scrolling while selecting corrupts the screen, then if the PDF is large (a few megs), the reader will crash after a couple of operations more.
OMG...

Livecycle ES Form bug with Adobe Reader 9

My firm is currently upgrading certain people to Adobe Reader 9. I have created fillabe forms using Livecycle ES (Adobe Professional 8) and distribute these forms using the "distribute" function in Adobe Professional 8. The forms are sent back using a submit button with a "mailto" script. When the users send the form back to me using this submit button (and using Adobe Reader 8), the form was submitted automatically without opening new email message box. Now, the updraded users (adobe 9) are hitting the submit button and it is opening up a new email message box instead of sending the form automatically through the email server (outlook). What can I do to make the submit button work correctly with Adobe 9? or is there a default setting in Adobe 9 that needs to be changed? I have already tried extending user rights and that did not change the way the form was sent back to me. Thanks, Jen

Actually, this was an upgrade when the users were upgraded to Adobe Reader 8. I distribute the form via Adobe 8 Professional. I have 2 submit buttons on my form. The 1st submit button is visible and the users click. If all required fields are filled out, then the 2nd submit button (which is invisible) sends the form back to me via email (using the script mailto:[email protected]). This is done so that the form cannot be sent without filling out the required fields. Also, I distribute the form via the distribution function in Adobe Professional 8, so that a Dataset file is set up for returned forms. I really like this function, but now Adobe Reader 9 doesn't allow it.
If anyone has a fix for this, please help.
Thanks,
Jen

How can I open the right URL in PDF?It's like a bug in adobe reader.

In my case, the PDF in our company always have a DOI on it, which is a URL can lead the reader to the article’s website page. But we found out that the URL in the PDF wouldn't show the link completely, If the URL is http://dx.doi.org/10.6310/jog.2009.4(3).3 in PDF, and I click the link, it will link to http://dx.doi.org/10.6310/jog.2009.4 . It is a big problem that would take the reader to the meaningless page. And it seems a bug, because the url is Ok if I use PDF-Viewer to open it. Can you help us to deal with this problem? Thank you.

Parsing parentheses in a URL is a problem for Reader and Office as well. It's not a good idea to use parentheses in URLs for that reason. Some older browsers will even have trouble with them.
The URL I get from that link is: http://www.airitilibrary.com/Publication/alDetailedMesh?DocID=P20140124001-200912-20140128 0011-201401280011-93-102
Why not just use that?

Is there a bug in Adobe Reader for Unix?

I have the most recent version of Reader as of November 2010 (I think it's 9.4.3). PDFs downloaded from the Federal Direct Loan Servicing Center (student loans) are not working right. (This affects students in the United States.) I don't know if it's their mistake or a bug, but the DL center is not answering emails!
So I hope someone can tell me if this is a bug:
When I open the PDF, there is a *toolbar* to Show/Hide forms.
I choose to *Show forms*.
Only *some* fields are fillable, others are not!
Also, when I *tab* though the fields, it tabs in a completely *mixed-up order*.
Does anyone know if this is a bug? Or do you know if the DL center makes their forms wrong?
Thanks!

Hi Terry,
For step 3, the reason might be that certain fields in the PDF is not being recognized as form fields by Acrobat/Reader or their properties make them non-fillable.
For step 4, I can comment more in case I get the pdf
Can the PDF form in question be shared?
If yes, please email it to adharATadobeDOTcom
Regards
Atanu Dhar

Adobe Reader X cosmetic bug - browser integration scrollbars do not move

There appears to be a cosmetic bug in Adobe Reader X (10.0.0) browser integration. When you open a PDF in a browser window, the scroll bar remains at the top of the window when you scroll the PDF using page up / page down, or the mousewheel. If you mouse over the scroll bar, it moves to the correct place in the PDF.
This bug is consistent across IE 8, Chrome 7.0.517.44, and Mozilla Firefox 3.6.12 (running on Windows 7 Enterprise x86).

*PUSH*
Please fix this. Its just ridiculus to provide a plugin like _THE_ Adobe Acrobat Reader and not be able to implement a proper scroll behavior. Come on it can't be _that_ hard .
Thanks

PDF annotation with link, image doesn't show, only in print or Google Chrome, not Adobe Reader main

We are creating PDF files with annotations, we are using the O2 Solutions PDF Library for C#. We used to create PDFStampAnnotations, but now we want to make the images clickable, to navigate to the URL belonging to the image.
Therefore, we are now using PDFLinkAnnotations, with a PDFImageAppearance.
We set the flags of the annotation to Print.
However, the annotation won't show in the PDF in Adobe Reader. It does show in the Google Chrome inline PDF viewer.
It also shows in the print preview window in Adobe Reader.
But it does not show in the normal view in Adobe Reader. What we do see is, when hovering over the rectangle that should contain our image, our mouse cursor becomes a hand and a tooltip with the link is displayed. If we click, everything works as expected. But we don't see an image!
What can we do about this? This is really annoying, as I don't have a clue why it won't work. Actually, to me, this looks like a bug in Adobe Reader?
Old (working, without link):
=================================================================================
15 0 obj
<</Contents (DEV-1)
/M (D:20130222103743+01'00')
/Subj (TigrisTag)
/Subtype /Stamp
/F 4
/Name /Custom
/AP <</D 16 0 R
/N 16 0 R
>>
/CreationDate (D:20130222103743+01'00')
/Rect [560.349976 10.000023 601.999977 51.650024 ]
/NM (97c87adc-5494-440a-b0b4-eb606e358169)
/T (name)
/P 4 0 R
/Type /Annot
>>
endobj
16 0 obj
<</Resources <</XObject <</ImageStamp 17 0 R
>>
/ProcSet [/PDF /Text /ImageB /ImageC ]
>>
/BBox [0 0 39.20008 39.20008 ]
/Name /Form_4943204746964B4C8B728A4CBD79B339
/FormType 1
/Length 41
/Src (XO:/Form_4943204746964B4C8B728A4CBD79B339)
/Type /XObject
/Subtype /Form
/Matrix [1 0 0 1 0 0 ]
>>
stream
39.2001 0 0 39.2001 0 0 cm
/ImageStamp Do
endstream
endobj
17 0 obj
<</Width 245
/ColorSpace [/Indexed /DeviceRGB 1 18 0 R ]
/BitsPerComponent 1
/Filter /FlateDecode
/Length 471
/Subtype /Image
/Height 245
>>
stream
(stream contents)
=================================================================================
New (not working, with link):
=================================================================================
18 0 obj
<</Resources 4 0 R
/Type /Page
/Group <</CS /DeviceRGB
/S /Transparency
/I true
>>
/Annots [19 0 R ]
/MediaBox [0 0 595 842 ]
/Contents 23 0 R
/Parent 3 0 R
>>
endobj
19 0 obj
<</Contents (TigrisTag)
/A <</S /URI
/URI (http://localhost:50830/publications/code/DEV-8)
>>
/M (D:20130225170939+01'00')
/Subtype /Link
/F 4
/NM (6a41409d-b8fb-44b6-8a7c-ab1c73088869)
/Name /Image
/AP <</D 20 0 R
/N 20 0 R
>>
/Rect [544.506958 9.999985 585.000015 50.493042 ]
/BS <</W 0
>>
/CreationDate (D:20130225170939+01'00')
/H /I
/P 18 0 R
/Type /Annot
>>
endobj
20 0 obj
<</Resources <</XObject <</ImageStamp 21 0 R
>>
/ProcSet [/PDF /Text /ImageB /ImageC ]
>>
/BBox [0 0 39.20008 39.20008 ]
/Name /Form_119A6CEBB1C8452D962814D585C640CC
/FormType 1
/Length 41
/Src (XO:/Form_119A6CEBB1C8452D962814D585C640CC)
/Type /XObject
/Subtype /Form
/Matrix [1 0 0 1 0 0 ]
>>
stream
39.2001 0 0 39.2001 0 0 cm
/ImageStamp Do
endstream
endobj
21 0 obj
<</Width 245
/ColorSpace [/Indexed /DeviceRGB 1 22 0 R ]
/BitsPerComponent 1
/Filter /FlateDecode
/Length 467
/Subtype /Image
/Height 245
>>
stream
(stream)
endstream
endobj
=================================================================================

Thank you for your reply.
Indeed, I tried saving a PDF that had the "default appearance", it shows exactly the same. So it looks like it "can't" show the image.
However, of course, I do want the image to be shown. How can I achieve this? How can I tell Adobe Reader (and other PDF viewers) I really really realllyyyyy want to see that image there? I believe I'm not doing anything really exotic, right? There must have been tons of other people that wanted to do the same thing, I guess?
                    var annotation = new PDFLinkAnnotation
                                Action = new PDFUriAction(this.GetCodeUrl(code)),
                                Contents = AnnotationIdentifier,
                                Appearance = new PDFImageAppearance(bitmapImage),
                                DisplayRectangle =
                                    new DisplayRectangle(
                                    barcodeLocationInfo.X,
                                    barcodeLocationInfo.Y,
                                    barcodeLocationInfo.Tsw,
                                    barcodeLocationInfo.Tsh),
                                Flags = Flags
                    pdfPage.Annotations.Add(annotation);

In Adobe Reader 10.1.4 my signatures are valid, in version 11.0.10 they are not?

I have a PDF document with two signatures.
If I open it in Adobe Reader 10.1.4 the signatures are ok.
If I open the same document in Adobe Reader 11.0.10 the first signature is marked invalid: "Document has been altered or corrupted since it was signed".
Does anybody understand why this is?
I have the feeling this is a bug in Adobe Reader 11.
Thanks,
Corné
You can find the PDF here: WeTransfer

Can you please try repairing the application from the Control Panel.
Also, could you please let me know if this issue was happening with Reader 10.1.3 as well.

Bug in Adobe Reader

Similar Messages

Maybe you are looking for