Adobe Photoshop

What works

Photoshop CS2 works, but it's slow.

What does not

All the other CS2 components, like Adobe Bridge. They give me a licensing restriction error. Note that the same license works under Windows.

Workarounds

What was not tested

Adobe Bridge and all the other components (can't even get past that error).

Hardware tested

Graphics:

• GPU:
• Driver:

Additional Comments

Tips for UI Quirks:

• Windows-->Workspace-->Reset Palette Locations is your friend
• Keeping Photoshop in it's own desktop can prevent some of the overlapping windows issues with other programs. (Bug #11412)
  
• If Photoshop keeps ignoring the filename you type in while saving as a jpeg, select the filename field again and press Home on the keyboard. You should be able to proceed with the correct filename. 
• If Save For Web... doesn't work, use Save As.. and set the filetype to jpeg or png.
  

• You shouldn't have to copy Photoshop from Windows; just install it under Wine by running its "setup.exe" into Photoshop CS2 (R) Directory. "Setup.exe" don't work for Wine's Versions > 1.0. (To run a .exe under wine, you have to doubleclick it, right click and choose "Run with Wine", or run it from the commandline using the 'wine' command, depending on how your Linux distribution integrates Wine.)

• Never use a cracked version of Photoshop.
• Never run Wine as root.
• Use a recent version of Wine (1.0.1 or later). 1.1.0 recommended.

• Before installing Photoshop, install the Times32 font by downloading and running one of the corefont installers, e.g. http://heanet.dl.sourceforge.net/sourceforge/corefonts/times32.exe , else Photoshop will abort with a "hardware error" [see bug 9623]

• Some UI elements might use a too-small font. In CS2, you can fix this with Edit / Preferences / General, and change UI Font Size from Small to Medium. Restart Photoshop.
  

• The Clone tool uses the ALT key in a way that conflicts with many window managers. Here's how to fix that:
  • Ubuntu: System / Windows / Movement Key, and pick "Super" instead of "Alt".
  • Kubuntu: K / System Settings / Look and Feel / Windows / Movement Key, and pick "Super" instead of "Alt"
  • Suse with Gnome: Computer / Control Center / Look and Feel / Windows / Movement Key, and pick "Super" instead of "Alt"
  • Fedora 8 Gnome: System / Preferences / Look and Feel / Windows / Movement Key, and pick "Super" instead of "Alt
  • Suse with KDE: Gecko / Favorites / Configure Desktop / Desktop / Window Behavior / Window Actions / "Inner Window, Titlebar & Frame" , and pick "Meta" instead of "Alt"
  • Earlier KDE: KDE Control Center / Desktop / Window Behavior / Window Actions / turn off the alt-combos.
  • Earlier Gnome: Destop Preferences / Keyboard Layout / Options / Alt/Win key behavior [expand tree]; select new behavior for modifier keys


• If photoshop was working and now you get this message: "You are not allowed to continue because your accountdoes not have the proper privileges. Please log in using an account with administrator privileges and try again." Restarting your computer usually fixes this. If photoshop gives you this message the first time you run it, you probably have a different issue. (To explore further, read this, this, and this.)

Thanks to earther for the following email:

I was having problems with the Photoshop 7 ALT-Click keybinding in a new Debian install running Compiz.  I did the standard window manager tweak but it still didn't work properly.  Then I discovered an ALT-Click keybinding in the Compiz Window Management > Move Window > Initiate Window Move settings. I changed it to 'super' like in Gnome window management and voila, it seemed to get it working again in Photoshop. You might want to add that bit of info to the clone tool info on the Photoshop 7 page.

earther

Admin note: the following information was extracted from a user comment posted on July 13th 2008, and may not be relevant to current Wine.

Symptoms: After loading plugins, tools, brushes, etc., the program halts with the error message "Unable to continue because of a hardware or system error. Sorry, but this error is unrecoverable." Clicking OK results in hard crash.

Diagnosis: This problem is related to a settings file that is created and modified each time Photoshop runs and exits.

Quick Fix: You can force Photoshop CS2 to start by holding down CTRL+ALT+SHIFT while starting the application Linux or Command+Option+Shift in Mac OSX. You will be presented with a dialog box that asks if you wish to delete the settings file. Selecting Yes will delete the file, and allow the application to start as normal.

PERMANENT FIX: The permanent fix is actually very simple. The problematic file is the General Settings file, "Adobe Photoshop CS2 Prefs.psp", which references the default fonts Adobe expects to be installed. If for any reason these fonts, or any other files, are not installed or not functioning as expected, the application will terminate to the desktop. This settings file is located here:

/home/[USER PROFILE]/.wine/drive_c/windows/profiles/[USER PROFILE]/Application Data/Adobe/Photoshop/9.0/Adobe Photoshop CS2 Settings/Adobe Photoshop CS2 Prefs.psp

Naturally, replace [USER PROFILE] with the user name you are working under.

Now, if you've encountered this error, you've already run CS2 twice, and the settings file has already been created and corrupted. Although deleting it will allow you to start CS2, it will again store a corrupted file when you exit the application, and next time you start the application, you'll repeat the same fatal error as usual.

So, having located this file, perform the following steps:

(1) Rename or delete the corrupted file
(2) Start CS2. It should start just fine.
(3) IMMEDIATELY after it has started, change the permissions on the newly re-created settings file (Adobe Photoshop CS2 Prefs.psp) to READ ONLY. You can do this in your file browser, or, if you are at the command line, use the following command:

chmod -w ./Adobe\ Photoshop\ CS2\ Prefs.psp

(4) Rejoice. Your work here is done.

Now, whenever CS2 exits, it will no longer overwrite the fresh, working settings file, and you will always be able to start it without the annoying error and subsequent crash.