For other pages, please let us know via email, we will check and give you a reply. I'm using GNOME Flashback, so the file manager is Nautilus. Among pages recommended for Can't Sign Into Adobe Acrobat Dc, if the not-working page is the official login page, it may be because the site is temporarily suspended. Use the format radio buttons to select the desired file type, and click Export. You can also save as Rich Text Format (RTF), plain text, image formats, HTML web page, and other file formats. I ran update-desktop-database, logged out and back in from the DE.īTW. Then choose a file format, such as Microsoft Word, Spreadsheet, or Microsoft PowerPoint. Which I guess should cause Adobe Reader be displayed among applications suitable to open a PDF file - but it isn't.Įven after I manually changed the line in /usr/share/applications/defaults.list to application/pdf= and removed the same from my ~/.config/mimeapps.list, it didn't change anything. i thought that its because the highres pdfs file size was around 200mb but it also occures when. However, my ~/.config/mimeapps.list contains in section the lineĪs I have set the default app back to Evince, and it also contains in the line if i open pdf files (with highres pictures in it, cause it´s for print publishing), then acrobat dc is loading the images very slowly - like first it shows a part on the top and the rest of the page is blank, then the next part and so on.Which must have been added during Adobe Reader installation. I checked /usr/share/applications/defaults.list (actually a symlink to /etc/gnome/defaults.list) and it contains the line After I did this, Adobe Reader does no more appear in the "Open with another application" menu, so I cannot use it with right-click - I have to open Adobe Reader from the main menu and use File/Open in the application or drag-and-drop. So on my new Ubuntu 20.04 I installed Adobe Reader from the latest available Linux version (AdbeRdr9.5.5-1_i386linux_enu.deb) to be able to open these files.Īfter installation, Adobe Reader set itself as the default application for PDF files, so I set the default application back to Evince. Citrix or Terminal Server) please review the guidelines for using the plug-in in server environments.I have a few strange PDF files (that I received once from my bank) that open correctly only in Adobe Reader. If you encounter this error on a server environment (e.g. Once you have verified that the FileOpenBroker64.exe is running as a process in your Task Manager, you should be able to open protected documents for which you have permission. After creating the shortcut you can start FileOpenBroker64.exe manually by double-clicking either on the original. To do this you can create a shortcut toĬ:\ProgramFiles\FileOpen\Services\FileOpenBroker64.exeĬ:\Users\ YOUR USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startupįor launching the FileOpenBroker64.exe at login time. You will also want the FileOpenBroker64.exe to start every time you log in to the machine. If you just installed the FileOpen client plug-in and this is your first time trying to open a protected file, then you need to get the FileOpenBroker64.exe running.If a reboot does not solve the problem, please request technical support. The easiest way to get the broker process running again is to simply reboot. You can follow the question or vote as helpful, but you cannot reply to this thread. If you wait a couple seconds it unfreezes but after another couple seconds it freezes again. Any suggestions pertaining to getting Adobe Acrobat DC (not Reader) to work on a Windows 10 machine with Office 365 installed would be valued Many thanks, Microsoft Consumer Post moved by the moderator to the appropriate forum category. If you have been able to view protected documents until recently, then the broker process was running and has stopped for some reason. (Latest Update) When they Open a PDF File with Acrobat DC it works fine for a couple seconds and afterwards it continuesly starts to freeze and the Window is in a 'not responding' state. What we want to do is get the broker process running again. These error messages are displayed when a companion process, FileOpenBroker64.exe, is not running.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |