Bug Reports

Installed OS-X Sierra and now Photoshop 15.5.1 crashes when attempting to print. Print dialogue opens and settings can be modified, but when attempting to print PS crashes perhaps 9 out of 10 attempts. Most frustrating. I'm printing to an Epson 7890, but I have seen the same issue cited for Canon. Adobe support told me that Photoshop has not been tested on Sierra, but in reality Adobe has had Sierra for months and have even published known issues. I pay a ton of money for this thing to work and this nonsense from support is very annoying.

Hi, I am using PS CC 2015.1.1 (latest version) on an Eizo ColorEdge monitor with a FirePro W8100 (latet driver 15.201.2401). When configured to use 10 bit, I get the following in the Liquify filter: If I turn off 10 bit support, it works just fine. These are supposed to be professional products but they are full of bugs. I just created this other case related to color banding in 10 bit. Teo

Photoshop CC 2017 -Displacement Effects can neither be applied nor modified. This will result in the following error screen, no change can be made.I have changed the physical disc out, yet the bug still persists. CC 2015.5 did not yet show it. I have some error logs, if anybody is interested.

Photoshop CC 2017:   Steps: 1) Have files in an open folder layer.2) Select the layer in the folder.3) Clicking on the down-arrow on the folder to close it.Expected result: The folder will close.Actual result:Selecting the folder layer.----If I'm not mistaken, in the new update (Photoshop CC 2017) you now select the folder even if you click on the down arrow directly. Super annoying having to do it in two steps instead of one. Navigation between layers slows down a lot.

Since upgrading to CC17 I have experienced various weird-looking documents. Something seems to be wrong with alpha levels in preview composition.For instance, a document which looked fine 2 days ago, now exhibits layers that, even when set to 100% opacity, are only visually 20-30% opaque.Investigated a bit further, and as feared, the bug seems to be caused by overlaying a blended group (see attached images) Notice that hiding the group (which only contains various dark overlays being Linear Dodge'd onto the underlaying document) "fixes" the transparency issue.In a different instance, the background layer in a Smart Object would not render unless the top layer blending with it was 100% filled (ie somehow it "masked" the underlaying background).It's clear to me that there's something wrong with the composition engine, and blending, in CC17 — Mac only though. We tested for the issue on our Windows machines, and nothing wrong there.Experienced with Mac (El Capitan, CC 17 18.0.0).Pleas

In order to rename a layer or layer group I have to double-click, pause, and then click again to be able to rename the layer in the layers palette. Note: The double-click to rename a layer works correctly if you're using tabs for your documents, or if you are in "Full Screen Mode" or "Full Screen Mode with Menu Bar". I can only reproduce this bug when using floating documents in "Standard Screen Mode", which is how I work. Running: iMac (27-inch, Late 2013) Mac OS X 10.11.1 (El Capitan) Photoshop 2015.1

Just updated to the new Photoshop CC 2017, and the Blending Options just stopped working on artboards.Previous files that I had blending options applied to artboards lost its properties and nothing happens when I right click it and click on "Blending options". Paste layer style is also disabled on this version.(Using windows 7)

This has been frustrating me for a while (I think it was introduced in 2015.5), but there still isn't a fix:When you are painting with the brush tool and you use the icon in the toolbar to toggle pen pressure, that value is no longer synced with the Shape Dynamics toggle in the Brush panel. it used to be, and the Opacity toggle still is, it's just the Pressure toggle that's broken. It'll turn on but it won't ever turn off unless I open up the Brush panel and do it there, very cumbersome and annoying.Below is a video of the problem. Happens either when you click the toggle buttons or use the newly-added keyboard shortcut option.  

I have a script, which basicly changes activeDocument to doc_a, then it changes activeDocument back do doc_b and tries to check activeDocument.activeHistoryState here. It always stops executing here and I get "General Photoshop error occured. This functionality may not be available in this version of Photoshop.". Any ideas how to solve this? The code for reproducing this bug: (I'm using CC 2015.5.1, but it doesn't work on CC 2014 either) app.activeDocument = app.documents[0];  app.activeDocument = app.documents[1];  $.writeln(app.activeDocument.activeHistoryState);  

I just updated to Photoshop CC(2015) version 2015.1. Adobe changed the UI to the flat look you see on phones and tablets. I do not see any way to select the classic interface, which I'm sure many desktop users of PS prefer. This feels yet another attempt by Adobe to be trendy without caring about what users want or need. Didn't they learn anything from the dumbed-down Lightroom import fiasco?

Photoshop CC 2017: The Batch tool "Source - File Finder" window is acting a bit weird in Photoshop 2017 / in MacOS Sierra. Normally when you have the "Source" folder opened to the Mac filesystem folder section, when you switch away from Photoshop to another application like Finder.app, for instance, it sticks the Photoshop "Batch" window on top of every other application that is actually in the foreground. This can't be disengaged until switching back to Photoshop and choosing a folder for the "Source", or canceling out of the source selection. I run into this issue when I want to batch a folder, by choosing the "Source" folder selector, cmd+Tab to Finder, select / click-hold a folder and then cmd+Tab back to Photoshop while still "dragging" the folder selected in Finder to load it into the Batch "Source" as the targeted folder to be used in the Batch.This process is faster and easier than targeting the folder within Photoshop, because most of the time, I already have the folder open i

I have a Photoshop script written by Copyright (c) 2006 Rags Gardner.   With his permission I reworked his script to generate Photo Collage Template compatible with my Photo Collage Toolkits populating scripts.  The Script work with Photoshop CS2 through CC 2014. The script will also work in CC 2015 if launched by the JSX Launcher extension.  However if launch via menu File>Scripts>CollageTemplateBuilder in CC 2015 and CC 2015.5 the script dialog briefly flashes in Photoshop window  and Photoshop is hung and must be terminated via the windows task manager.  Is there a ScriptUI expert that is willing to help find where the problem is? http://www.mouseprints.net/old/dpr/CollageTemplateBuilder.jsx

I have an irritating problem with Adaptive Wide Angle filter. I have never had this problem before nor other problems. Ps has been working OK until now.The constraint tool flickers my whole adaptive wide angle window back and forth to my Ps working window behind, while I try to move the "change angle" pin / dot. It does this to all my panorama raw files and to any other file. The problem isn't constant, sometimes it works, sometimes not. It has all started yesterday after I saved my work as a PSD file. I wanted to return to my smart object layer with adaptive wide angle to modify some of the lines again to fix my photo and suddenly my whole window started to flicker like in my video below.I have tried to reset Ps preferences from Edit menu and reset Ps settings according to this video by J Kost https://www.youtube.com/watch?v=VXNrI6YKJIM&feature=youtu.beIt did not work. Nothing works 😞Ihave contacted Chat support a moment ago where I was told to move the Adobe Photoshop CC

This started a couple versions ago, shame on me for not reporting it sooner.Previously I could edit a mask in quick mask mode if that mask was disabled. This allowed me to see the original data beneath the red overlay for edge refinements. When I do this now, it does not register any brush marks at all, and some times will give a glitch, half-affected area where my brush was that doesn't in turn edit the actual mask until I turn quick mask off.Would love some help problem solving this or having the bug acknowledged! Thanks

Hi,using the latest Photoshop CC 2015.5.1 with the latest Windows 10 64bit (Build 14393), I noticed that the toolbar at the bottom no longer disappears in Photoshop's full screen mode. I tried all "flavours" of the full screen mode by toggling through them with the "F" key and.The Windows toolbar seems to be overlaid at an opacity of around 50% on top of the image displayed in Photoshop. In other words, I can still see the image which I'm editing shine through, but it's not usable. Here's a screenshot:A work-around is to manually disable the Windows 10 toolbar prior to opening Photoshop and then enable it again once I'm done with Photoshop work. This is not ideal.It would be great if someone from Adobe could create a bug report for this, or could let me know how I can do so myself. Happy to supply screenshots and system information.ThanksChris

I updated to the most recent version of Photoshop CC (2015.5). I noticed that the strokes in compound paths/shapes are suddenly disappearing. Sometimes I need to toggle different modes of stroke alignment in Stroke Options for the stroke to appear again.Device:iMac 4K RetinaPhotoshop CC (2015.5) - Updated June 23, 2016

Hi there, Since Photoshop CS6 the functionality of the smudge tool seem to have been altered. I am still on Photoshop CS5 at work, because of that exact issue. I don't know why this problem has been ignored by Adobe and carried on even to the latest CC 2014 subscription. Apparently not many people use the smudge tool at 100% pressure. As a concept artist at Warner Bros I have several concept artists in my team that report similar issues and we tried it out on different wacom devices on Windows 7 platforms (cintiq 24 HD, intuos 5 touch medium and large) showing the same behaviours. On my side I practically use this feature almost on a daily base and I find it extremely useful - feel free to visit my portfolio: www.inetgrafx.com to see the smudge tool in action 🙂 It would be very much appreciated if a developer could fix this tool as shown here: in short: it works perfectly fine in CS5 and I wished I had exactly the same functionality back again for a future version of Photoshop

Photoshop 2015.5: in 2 of my machines photoshop appears to hang idefinitely using mixer brush on a 16bit document with the latest version: steps:create new document: file->new ->okchange mode to 16bit image->mode->16bit/channelselect mixer brush, alt click to sample the background of the new document (or just sample something), then make a stroke in the document.create another document: file->new->ok photoshop hangs indefinitely. also happens if you have the second document already open and you switch to it with the mixer brush active (instead of the last step of creating a new document) another similar way to crash photoshop: create new documentselect mixer brush, sample the background and make a stroke in the documentchange mode to 16 bit imagephotoshop hangs.

Pictures about 3000*2000 pixels. 50 layers, SmartFilter, PuppetWarp on whole picture, correction on layers due to puppet warp. Top layers are correction layers. 1 text layer. Animation sequence ( 1 fps ) . from left to right, bottom layer to top layer.After editing all 50 layers, including positioning (tween) manual of text layer ( horizontal shift)Export ->Video Rendering -> JPG 1fps All layers are exported to sequenced pictures in designated directory: except ALL puppet warp changes ( what is was all about ) are not rendered into the new jpg images.Interim solution: every layer: layer convert to pixels.Set back is of course: destructive layersPlease solve problem.

This script works in prior versions of Windows Photoshophttp://www.mouseprints.net/old/dpr/La...CC 2015 will loop not respond when you move a slider back and forth, The scroll bar stop functioning Photosho is looping and is nor responding. Has to be terminated usinf Task Manager.

I use smart objects all the time, and as of recently, I've been noticing problems with how they render. See the image here http://i.imgur.com/fzbzs9q.pngThis is a PSD file placed into another PSD (as an external smart object). You can see the dotted pattern that occurs in it. If you look at the extra-zoomed pic on the left, you can make out that some of the pixels are actually translucent (you can see Photoshop's checkered pattern underneath them).That's the problem - not all pixels are rendered as 100% opaque, even though the pixels in the source image are opaque. And the ones that are rendered as translucent are done so in some sort of pattern, resulting in these visual artifacts. If I create a layer of solid color underneath the smart object, the problem is no longer visible. I'm not sure what this problem is caused by. It might be something I'm doing wrong, though I can't think of anything new in my routine to have caused it (and I've us

When I use "quick export as PNG", it saves the file, but then opens a file explorer window for some reason. No other save-as/export feature in PS or anything else does this in Windows. Maybe this was implemented by an OSX developer (some applications do this there), but this is really annoying in Windows.

Lasso crash on macOS Sierra

The ~ ( tilde ) shortcut to view mask as grayscale stopped working. I can see the layer mask as a 50% red overlay by pressing \ (backslash), but not as a garyscale. and I usually go around both view modes when working on masks. I have already reset photoshop settings but it did nothing.

Example: https://bsshop.cz/screenshots/2016-10-17_154601.pngResult is bad and it makes no sense crop image like this.Layer below is for expected result