Technical Support

136 readers
1 users here now

Tech support for technical people.

You can ask all technology related support questions here. This is inspired by r/techsupport but we're striving to be professionals here. Don't ask stuff you can answer in a few seconds just by googling and be sure to follow this guide on how to ask questions the smart way.

founded 3 years ago
1
 
 

I'm posting this here because it took forever for me to figure out how to fix it and I want to potentially save hassle for others who may have this issue.

Expected result: Acrobat working as intended and not completely breaking when using basic UI functions.

Actual result: Constant errors and crashing to desktop.

Context: Adobe released a silent update that automatically updated Adobe Acrobat DC to 64-bit last year and slowly rolled out to all users. This update broke my installation. I was getting constant errors when clicking on “File” or “Edit” which yielded “An internal error has occurred.” It was also having issues displaying icons, printing, consistent freezing and crashing on opening any PDF file. This was a gradual roll-out made the error occur at different times on different machines.

I believe this caused some issues with Adobe Creative Cloud since it wasn't recognizing my user profile and tried to load my files with the default profile. I don't know why this would break the software but it did.

The way to get around this was to uninstall the 64 but version and install the 32 but solution in its place. Adobe does have a "clean" uninstall tool but it didn't work, so I had to uninstall it through Creative Cloud.

Solution:

  1. Uninstalled Adobe Acrobat DC Pro via Adobe Creative Cloud
  2. Rebooted
  3. Downloaded the old 32-bit Adobe Acrobat Pro DC from here.
  4. Unzipped the .zip file, ran Setup.exe in administrator mode
  5. Disabled the automatic update to 64-bit by editing in the Registry Editor: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\
  6. Created new key called “Feature Lockdown”
  7. Added a new DWORD (32-bit) value
  8. Set the value to 0, hexadecimal
  9. Rebooted
  10. Relaunched Adobe Acrobat Pro DC
  11. Tested it by opening up a PDF, watermarking, and printing to ensure that editing/printing functionality works
2
 
 

I resized my LVM LV with lvextend -L +32G -r root because lvextend -r doesn't work with btrfs apparently. This seems to have worked because I got Size of logical volume desktop/root changed from 32,00 GiB (8192 extents) to 64,00 GiB (16384 extents). and lvdisplay shows the correct size (64GiB).

Then I did btrfs filesystem resize max / which told me Resize device id 1 (/dev/mapper/root) from 31.98GiB to max – it's still 32GB when I do findmnt -sD or btrfs fi sh / though.

What am I doing wrong?